Carsten Senger <sen...@rehfisch.de> writes:

> Hi Jens,
> Hi Ross,
> Hi all,
>
> I'm missing the initial mail, so I answer to this one.
>
> The most vital info source is http://live.gnome.org/GnomeWeb/CmsSetupand the 
> documentation of the buildout and the wgo.* packages.
>
> Ross Patterson schrieb:
>> "Jens W. Klein" <j...@bluedynamics.com> writes:
>>
>>> The project to implement www.gnome.org needs reanimation.
>>>
>>> I try to summarize:
>>>
>>> Plone people who want to help (please define your role): * Jens
>>> Klein (coordination and technical work, participate at sprint)
>>> * Ross Patterson (take some technical tasks, ...)
>>> * Tim Knapp (take some technical tasks, ...)
>>> * Roberto Allende (take some technical tasks, ...)
>
> Jonathan Wilde (Speedbreeze) wrote the wgo.theme and worked on it
> during this month and said he would work further on the theme in the
> "wwww.gnome.org redesign status" thread:
> http://dev.plone.org/old/collective/browser/gnomeweb-plone/wgo.theme/branches
>
>>>  (more may follow if there are concrete todos)
>>>
>>> David Sapiro with Pilot Systems offered hosting for the site!
>>>
>>> At Gnome we have:
>>>
>>> invloved gnome people (please define your role)
>>> * Murray Cumming
>>> * Paul Cutler
>>> * Vincent Untz
>>> * David Bain (organizing sprint if funds raised)
>>> who else?
>>>
>>> technical we have
>>> * Plone 2.5 site + buildout + integration (almost finished)
>>> * all content for the new site already in an data.fs
>>> * as i understood some visuals/ graphics are missing
>
> The buildout is an 3.1.7 buildout
> http://dev.plone.org/old/collective/browser/gnomeweb-plone/buildout/trunk/buildout.cfg
>
> There is an installation script that creates a new plone site and
> imports the old content via gsxml. Read the readme of the buildout.
>
> The theme needs some polishing. I did not look at the speedbreeze
> branch what bugs he resolved in his recent work.
>
>>> In my opinion tasks are:
>>> 1 form a new group of gnome+plone people driving this project to
>>> success.
>>> 2 synchronize requirements with all participants
>>> 3 update to Plone 3.2/3.3 (recent stable)
>
>>
>> I'm happy to start updating a buildout to Plone 3 and doing the research
>> for any dependency/add-on compatibility whenever the time is right.
>> Just let me know.  :)
>>
>> Ross
>>
>>> 4 setup a public testing environment
>
> I installed a public site so people can have a look. It's available at
> http://gnome.rehfisch.de. Until the dns record has propagates, it's
> reachable through http://rehfisch.de:8090/gnome20090430_105004
>
> It's build with the speedbreeze branch. username and password are 'admin'.
>
>>> 5 make it work / fix bugs if any
>
> As said before:
> - Theme fixes and additions
> - LinguaPlone configuration (especially showing english texts in the
>   navigation if another language is choosen and an object is not
>   availabel in that language.)
> - Update to 3.3
> - Cache-Fu configuration
>
> The only other item on the list for a public release is an editing
> link for anonymous users that puts the article into a staging areas so
> it can be accepted by editors:
>
> http://bugzilla.gnome.org/show_bug.cgi?id=118291#c3
>
> But this is considered optional and a non blocker at this point and it
> should not be reconsidered before there's a site that is ready to go
> live.
>
> The list of current bugs can be found here:
> http://bugzilla.gnome.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=website&component=www.gnome.org&version=beta&long_desc_type=allwordssubstr&long_desc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=VERIFIED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&query_based_on=gnomeweb-plone&field0-0-0=noop&type0-0-0=noop&value0-0-0=(If
>  the link is screwed up, go to
> http://live.gnome.org/GnomeWeb/CmsSetup and search for
> "View all active bugs for gnomeweb-plone")
>
>>> 6 polish content and visuals
>>> 7 setup live hosting
>>> 8 go-live
>>> 9 have a party ;-)
>>>
>>> Methods/Tools to reach the goal;
>>>
>>> * online coordination (mailinglists, probably IRC)
>>> * wiki * bug tracker * sprint
>
> The gnome infrastructure has to be used for that, especially the wiki
> and the bugtracker. The complete current source is located in the
> collective so plone folks can start hacking away.
>
>>> Sprint:
>>> David Bain offered to organize a sprint at Jamaica. From my
>>> experience its a real good idea to have a sprint to push
>>> forward. This needs fundraising to pay travel- and other
>>> expenses. Who can organize fundraising?
>
> Until then we can do a virtual sprint.

Or if there's anyone with a clear enough overview to delegate, I can
start work now on whatever is appropriate for me to do.  Just let me
know what tasks I can safely tackle!

Ross


_______________________________________________
Evangelism mailing list
Evangelism@lists.plone.org
http://lists.plone.org/mailman/listinfo/evangelism

Reply via email to