WHAT IS WGO? We need to clearly define what is exactly wgo, which parts of the whole metasite are directly affected of the revamp project and this discussion. We could mark in bold those parts in the New Structure: http://live.gnome.org/GnomeWeb#head-414ca48c4650bea820c5caabf3a9c7bac9fc7878 EDITING WGO - The right contributors would get the right permissions to edit the right pages. We need to define "right" here, of course. Editing should be easy to those with edit permissions. - A good percentage of dynamic content will come from the subsites via rss etc. They decide what dynamic information is right for their subsites and their feeds should be right for us as well. - A wgo editorial team will edit the own contents of wgo. Editing tasks shouldn't mess with designing, programming or sysadmin. I.e. an average editor should not be able to change layout code. Doubts: - Claus, what is the problem with databases? - About events, what about "From guadec.org to events.gnome.org" - http://mail.gnome.org/archives/gnome-web-list/2005-November/msg00026.html - Olav, although I see feasible standard web solutions for projects, an integrated user management for web permissions, bugzilla, cvs is a (cmplex) project by itself, I wouldn't mess it with the current wgo revamp. -- Quim Gil - http://desdeamericaconamor.org
Attachment:
signature.asc
Description: OpenPGP digital signature