Re: wgo Status & Next Steps

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

As discussed previously, I set up a page with essential information for the project:
http://live.gnome.org/GnomeWeb/PloneImplementation
I reused this existing page which was out-of-date. Previous content was backed-up as GnomeWeb/PloneImplementationOld, and should probably be deleted...

Some questions:
- Are all the tasks in bugzilla already ?
- Can we use bugzilla to maintain a roadmap (i.e. associate tickets to milestones) ?
- Once this is done, can I remove the "Tasks" section from the GnomeWeb/CmsSetup page ? (and also the "Archived Text", "Installing a local Sandbox" and "How to join gnomeweb-plone" sections ?)
- Where is the latest Data.fs ? (is it still needed ?)

I would also like to set up an up-to-date requirements list (in a page ? or as bugzilla tickets ?), since current requirements are defined in multiple, not always up-to-date pages...

Seb

Le 6 mai 2009 13:11, Carsten Senger <senger rehfisch de> a écrit :

Hi Sébastien :-)

Sébastien Nicouleaud schrieb:

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.

Yes, it's installed.

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).

The most important problem I see is that we need to show English content if there is no corresponding translation in the current language (navigation and search)

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...

Leaving just current information on the page would be good. You know the current state and can do some cleanup.
If we have clear next step, we will replace the tasks with an overview and create open tasks in bugzilla.

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

Yes, that's true.
At the moment we have the luxury of 3 skilled css/graphics people to make progress with the theme, and we have to make the most of it.
I have some issues in mind that I will put into bugzilla, but there are surely more. One person has to coordinate the theming work and make decisions about organization, cleanups etc.

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 ?)

Yes, with the most inconvenient - gnu changelog messages - on the top ;)

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

I'll be there to roughly at 19h CEST/17h GMT/UTC.

Thanks,

..Carsten