Re: wgo Status & Next Steps

[Sébastien Nicouleaud <sebastien nicouleaud gmail com>]

2009/5/6 Carsten Senger <senger rehfisch de>

* Clean up theme glitches, template work and customizations (such as
removing author from pages)
* Configuration for multilingual content

This is the major topic that needs an experienced developer. With Ross and Jens we have two possible candidates. Sébastien also mentioned that he had worked with LinguaPlone already.

The most recent description of the translation requirements is http://mail.gnome.org/archives/marketing-list/2006-October/msg00112.html

I've never used LinguaPlone so this is a bit like reading tealeaves, but it seems that several of the "better don't go below" requirements are not easy and fast to implement in Plone. If that's the case we should drop or postpone them.

Someone has to pick this up. Jens, Ross, Sébastien, what do you think?

I think LinguaPlone is already installed as a dependency.
Remaining tasks are (correct me if I'm wrong):
- Choosing an i18n content layout (e.g. http://www.gnome.fr/ ? http://fr.gnome.org/ ? http://www.gnome.org/fr/ ? I know how to do for the last one, but not the others)
- Generating the translation relationships when importing the initial content (I can work on this).

My opinion also is that the wiki page is a mess at the moment (which doesn't help to organize ourselves):
- Essential links (sandbox, code, tasks...) should be moved to the top
- The projet history should be moved to a separate page
I can help on this too...

CSS styling should be under the responsability of one person only, in order to maintain the theming code organization.
(Jonathan is probably this person)

Last but not least, I'm not very confident in the current code state.
As a not-so-experienced plone developer, I'm not sure what need to be tested, and how.
Maybe some more experienced developer can help on this ? (and maybe some rules should be put on the wiki ?)

I'll try to be available and connected to #webhackers this evening (8 hours remaining).

Seb