This site has been retired. For up to date information, see handbook.gnome.org or gitlab.gnome.org.


[Home] [TitleIndex] [WordIndex] 

1. gnomeweb-plone Overview

This page documents an ongoing attempt to implement the http://www.gnome.org with Plone. For discussions use the gnome-web-list.

Contents

  1. gnomeweb-plone Overview
    1. Summary
      1. Requirements/Goals
    2. System Requirements
    3. How to join gnomeweb-plone
    4. Installing a local Sandbox
    5. Tasks
      1. 0 SandBox ( Done )
      2. 1 Basic Theme ( In Progress )
      3. 2 Main Page view ( In Progress )
      4. 3 I18n
      5. 4 Presentation/Configuration
      6. 5 Policy
      7. 6 Performance/Deployment
      8. Not needed (yet)
    6. Participants
      1. Actual participants
      2. Old participants
    7. Plone Configuration
      1. High Performance Plone
    8. Content
    9. Archived Text

1.1. Summary

Some people are attempting to revamp www.gnome.org (wgo) with the CMS Plone. We have a sandbox to show the current state. At some point a separate instance we will be created to build the wgo site. This instance will be hosted in a external server and at some point during the beta phase will be moved to the GNOME servers.

The Tasks that are done and need to be done are listed on this page in Tasks, but will be moved to bugzilla in the near future [2008-12-13 CarstenSenger].

1.1.1. Requirements/Goals

  1. All the implementation needs to follow GnomeWeb/WebPolicies

  2. Have in mind i18n requirements, although in principle the translation work won't start before the 2.18 release. See GnomeWeb/Localization (needs updating, see the Multilingual CMS for some reference.

  3. Everybody can access the sandbox. The wgo instance will be operated by the users that are going to work at the end with it, aka the web team.

This goal depends on:

1.2. System Requirements

The Sysadmin team in charge of the GNOME Infrastructure need to know the system requirements in order to prepare the migration and hosting of the wgo 2.18 beta. Please be as accurate as possible in terms of software requirements, permissions, etc.

1.3. How to join gnomeweb-plone

If you want to join gnomeweb-plone, you should checkout https://svn.plone.org/svn/collective/gnomeweb-plone/ . The Structure is documented in the README

Install a local Sandbox

The development is coordinated

Also we use #webhackers on irc.gnome.org.

1.4. Installing a local Sandbox

Every body can install a sandbox on their computer. The different parts are documented in buildout/README.txt, and if you want some more details wgo.installsite/wgo/installsite/README.txt.

For the impatient: 

svn co https://svn.plone.org/svn/collective/gnomeweb-plone/buildout/trunk wgo-buildout
cd wgo-buildout
python2.4 bootstrap.py
./bin/buildout -v
./bin/instance run src/wgo.installsite/wgo/installsite/installsite.py
./bin/instance fg

After these steps you can open the browser and you will see the site at http://localhost:8090/<Name of the Generated Plone site>. If you want to login as and Administrator, use the username and password "gnome".

1.5. Tasks

1.5.1. 0 SandBox ( Done )

1.5.2. 1 Basic Theme ( In Progress )

Here are screenshots of the previous plone beta site. For the parts that are not covered in the Screenshots or are not styled, you can take a look at Máirín Duffy's latest mockup (*.9nov.*) from 2006 (latest mockup). You can also find an SVG-File and archives with bits of the mockup exported to bitmaps in her Homedir.

1.5.3. 2 Main Page view ( In Progress )

1.5.4. 3 I18n

1.5.5. 4 Presentation/Configuration

1.5.6. 5 Policy

1.5.7. 6 Performance/Deployment

1.5.8. Not needed (yet)

The following items are not needed right now:

1.6. Participants

Please add your name here if you need permissions to work with the CMS for the wgo revamp. wgo testers are welcome.

If you just want to play with the sandbox you don't need to be listed here.

1.6.1. Actual participants

1.6.2. Old participants

1.7. Plone Configuration

1.7.1. High Performance Plone

For enabling a high performance on this implementation we will need to create different zeo servers (two?) as a backend and a reverse proxy as a frontend. We will use blobs as the way to store files . We are going to use Varnish that is well integrated with ZOPE/Plone using CacheFu. We will have to decide the HTTPProxy polices to make as fast as possible the new portal.

1.8. Content

The content of the website is discussed in the wgo sections goals (to be linked here as soon as they are created). We might use other instances to operate the new subdomains i.e. support.gnome.org. To be decided.

1.9. Archived Text

This section holds Text that isn't up to date, but can be of use for some time. Ignore it if you don't know surely that you need it.

Installinstructions until 2008-10-31: 

svn co http://svn.plone.org/svn/collective/gnomeweb-plone/trunk/wgo.buildout-dev/
cd wgo.buildout-dev
python2.4 bootstrap.py
./bin/buildout -v
cd var/filestorage
wget http://www.epsem.upc.edu/~ramon/Data.fs
cd ../..
./bin/instance fg

Other Installinstructions until 2008-10-31: GnomeWeb/PloneImplementation

2024-10-23 11:10