Extensions/website/staging

There exists a staging server for OpenOffice.org extensions, where new versions of the website are evaluated.
The current motivation is to move the current first implementation of the website to a seperated drupal module - so the change should not show any differences.
(drupal: the framework, the website is based on: http://www.drupal.org)
The current implementation on http://extensions.services.openoffice.org modified some drupal modules directly instead of 'hooking' into it.
Main advantage would be a better version upgrade possibility of drupal and with a new version of drupal we'll get working localized pages, also for not logged in users.
The staging site may be down sometimes, or not accessible for everyone everytime.

Current state is: CLOSED: http://ooo-extensions.osuosl.org/

I did some testing and feel quite ok with it right now. If you find some inconsistency, do not hesitate to post a message: website@extensions.openoffice.org

Limitations:

• Not all binaries are available, due to space limit.

TBO: 30.02.2010: All binaries are available now and behave as expected from old site.

• Registration is not possible, use your existing account from the extension website - which is not your OOo website login.
• Database/ Website content is from about 11/2009.
• Caching of pages is currently deactivated, so it might feel a little slow on loading a page.

Changes:

• 'Lighter' frame around extensions
• UI translation selectable for everybody
• Colors update to be the same as on template site http://templates.services.openoffice.org
• Upload of an extension release changed;
• Data that will be put into the update feed for the Ooo extensionmanager is shown to the extension owner on the release page of his binary.
• Login via link on top of page.

Main Testing areas:

• Creating an extension, uploading a release, download.
• Browsing and downloading as a not logged in user.

Further steps:

• Put it onto the main site http://extensions.services.openoffice.org in the next weeks.
• Extract translation informations of the website UI and put/update on pootle server.
• Migrate login to use the OOo login credentials (as already working on the template site)
• Make extension description page translatable