Re: Gnome Web Plone Sprint
- From: Jonathan Wilde <jonathan wilde aton com>
- To: Murray Cumming <murrayc murrayc com>
- Cc: gnome-web-list gnome org
- Subject: Re: Gnome Web Plone Sprint
- Date: Sun, 26 Oct 2008 11:16:57 -0700
I'll investigate that error and get back to you with an answer on how to
fix it.
As for Plone 2 vs. Plone 3 regressions, I don't know. I haven't worked
at all with Plone 2--just Plone 3.
Jonathan
On Sun, 2008-10-26 at 18:05 +0100, Murray Cumming wrote:
> On Sat, 2008-10-18 at 19:59 +0200, Murray Cumming wrote:
> > On Fri, 2008-10-17 at 18:00 -0700, Jonathan Wilde wrote:
> > > Hi!
> > >
> > > Sorry for the late-ish response. I've been busy getting back up to
> > > speed with my classes after the sprints.
> > >
> > > At the sprints, most of my work was centered around applying (cutting,
> > > pasting, and changing classnames to work with Plone 3 from Christopher
> > > Warner's code) the existing CSS to the new theme directory that we
> > > created (which is pretty-much done, but needs some cleanup) and porting
> > > the Plone 2 templates to Plone 3 viewlets. The viewlet work is pretty
> > > much done.
> > >
> > > We have a buildout (which I'm pretty sure runs out-of-the-box) at:
> > > https://svn.plone.org/svn/collective/gnomeweb-plone/trunk/. The folder
> > > buildout that we're using is wgo.buildout-dev. Just bootstrap.py it and
> > > bin/buildout it and you'll be good to go.
> > >
> > > There's still a fair bit of work to do, though. In general, here's what
> > > we need to get done:
> > >
> > > 1. Cleanup and consolidation of stylesheets (remove !importants
> > > that I added during development and get rid of default Plone
> > > styles whenever possible).
> > > 2. Making portlets look more GNOME-ish and less Plone-ish
> > > 3. Styling of the secondary sidebar navigation. There's some code
> > > that displays the secondary navigation as a portlet. Right now,
> > > that portlet would need to get ported from Plone 2 to Plone 3.
> > > In Plone 3, the navigation portlet appears to be able to be
> > > customized (through the GUI) to do exactly what that code did.
> > > We may be able to cut development time by doing that.
> > > 4. Creating a custom homepage view that displays the RSS feeds.
> > > 5. Switching to a tableless layout. Plone 3 uses a table-based
> > > layout now. To maintain code continuity with the current GNOME
> > > site and improve the site's semantic-ness, we should probably
> > > make the layout tableless. Luckily, there's
> > > http://plone.org/products/plone-tableless which accomplishes
> > > that. A few members of the OOTB Plone Themes project have
> > > reported success with using the page templates from this theme
> > > in their own custom themes.
> >
> > Thanks.
> >
> > Which of these are regressions compared to the Plone 2 version that was
> > running on a test site once? I realise that you'll have to guess the
> > answer (based on your understanding of Plone 2 & 3) because you probably
> > never saw that site.
> >
> > > 6. Public test server, beta testing, etc.
> >
> > This is essential for us to even think about any planning beyond this.
>
> I'm still waiting (with ever less hope) for a reply.
>
>
> In the meantime I tried to do a "buildout" of this new fork, using the
> instructions here:
> http://live.gnome.org/GnomeWeb/PloneImplementation
> (Using wgo.buildout-dev instead of wgo.buildout. I guess you renamed
> that.)
>
> But when running the instance, and trying to look at it in a browser, I
> got this crash:
>
> murrayc murrayc-x61:~/checkouts/gnome224/gnomeweb-plone-fork2/wgo.buildout-dev$ ./bin/instance fg
> /home/murrayc/checkouts/gnome224/gnomeweb-plone-fork2/wgo.buildout-dev/parts/instance/bin/runzope -X debug-mode=on
> 2008-10-26 18:00:05 INFO ZServer HTTP server started at Sun Oct 26
> 18:00:05 2008
> Hostname: 0.0.0.0
> Port: 8080
> 2008-10-26 18:00:14 ERROR Application Couldn't install Five
> Traceback (most recent call last):
> File
> "/home/murrayc/checkouts/gnome224/gnomeweb-plone-fork2/wgo.buildout-dev/parts/zope2/lib/python/OFS/Application.py", line 786, in install_product
> initmethod(context)
> File
> "/home/murrayc/checkouts/gnome224/gnomeweb-plone-fork2/wgo.buildout-dev/parts/zope2/lib/python/Products/Five/__init__.py", line 28, in initialize
> zcml.load_site()
> File
> "/home/murrayc/checkouts/gnome224/gnomeweb-plone-fork2/wgo.buildout-dev/parts/zope2/lib/python/Products/Five/zcml.py", line 53, in load_site
> _context = xmlconfig.file(file)
> File
> "/home/murrayc/checkouts/gnome224/gnomeweb-plone-fork2/wgo.buildout-dev/parts/zope2/lib/python/zope/configuration/xmlconfig.py", line 579, in file
> include(context, name, package)
> File
> "/home/murrayc/checkouts/gnome224/gnomeweb-plone-fork2/wgo.buildout-dev/parts/zope2/lib/python/zope/configuration/xmlconfig.py", line 515, in include
> processxmlfile(f, context)
> File
> "/home/murrayc/checkouts/gnome224/gnomeweb-plone-fork2/wgo.buildout-dev/parts/zope2/lib/python/zope/configuration/xmlconfig.py", line 370, in processxmlfile
> parser.parse(src)
> File "/usr/lib/python2.4/xml/sax/expatreader.py", line 107, in parse
> xmlreader.IncrementalParser.parse(self, source)
> File "/usr/lib/python2.4/xml/sax/xmlreader.py", line 123, in parse
> self.feed(buffer)
> File "/usr/lib/python2.4/xml/sax/expatreader.py", line 207, in feed
> self._parser.Parse(data, isFinal)
> File "/usr/lib/python2.4/xml/sax/expatreader.py", line 348, in
> end_element_ns
> self._cont_handler.endElementNS(pair, None)
>
>
> >
> > > Here's my recommendations on how to finish up those tasks as fast as
> > > possible:
> > >
> > > 1. Create a publicly-visible task list of what needs to get done.
> > > We could use http://bugzilla.gnome.org/ or another hosted
> > > service, such as Remember the Milk.
> >
> > There's no reason to use anything other than bugzilla.gnome.org or
> > live.gnome.org.
> >
> > We had already been using the "beta" version in the website product in
> > bugzilla, with the Plone 2 site. Most of those bugs are probalby not
> > worth worrying about until the Plone 3 site is up and running. Again,
> > nothing should distract from getting that running - please don't
> > distract yourselves with attempts to add new features or improvements.
> >
> > To file a new bug:
> > http://tinyurl.com/34orvh
> >
> > All open beta bugs:
> > http://tinyurl.com/32e8d2
> >
> > > 2. Create a list of everything that needs to get done before
> > > launch. To make it easy for others to participate, we should
> > > make them very specific. ("Style the navigation portlet
> > > according to the styling in the mockup at ..." rather than
> > > "Finish CSS")
> > > 3. Come up with an estimate for how long each task will take.
> > > 4. Claim tasks. Try to complete tasks within the time estimate.
> > > This makes it easier to keep track of who's working on what and
> > > how far along they are.
> > >
> > > What are your thoughts on this? Did I leave anything out? Do you think
> > > a public task list would be helpful for coordinating our efforts?
> > >
> > > Cheers!
> > > Jonathan
> > >
> > > On Fri, 2008-10-17 at 13:05 +0200, Murray Cumming wrote:
> > > > On Wed, 2008-10-15 at 20:53 -0700, Alexander Limi wrote:
> > > > > On Fri, 10 Oct 2008 23:47:09 -0700, Ramon Navarro Bosch
> > > > > <ramon nb gmail com> wrote:
> > > > >
> > > > > > This saturday we are going to sprint on gnome web at the plone
> > > > > > conference sprint Arlington Career Center ( Washington D.C. )
> > > > > > http://www.openplans.org/projects/plone-conference-2008-dc/sprint . The
> > > > > > idea is to have a funcional site with the visual design and features of
> > > > > > www.gnome.org CMS site so every body can download a buildout and try it,
> > > > > > fix bugs, ... If anybody wants to goin us will be at 9 a.m. I'll inform
> > > > > > about the state of the sprint during the weekend.
> > > > >
> > > > > Since Ramon hasn't commented yet (he's probably en route to Barcelona),
> > > > > I'm happy to inform you that Jonathan Wilde did lots of great work on the
> > > > > theme + portlets, and he showed me a very nice-looking Plone 3.1 with the
> > > > > GNOME design.
> > > > >
> > > > > I'll let Ramon or Jonathan cover the details, but I just wanted to make
> > > > > sure that you know that it seemed to be a successful sprint. Now, it's
> > > > > time to fix the process issues around this. ;)
> > > >
> > > > Interesting, and well done, though I am not yet ready to be change our
> > > > plans back. I'll need to see real results to be convinced.
> > > >
> > > > Now it's time to get these changes into svn and to prove that it can be
> > > > deployed by someone else.
> > > >
> > > > If anyone has the ability to put up a reliable test site of this, before
> > > > gnome.org does, that would also be useful.
> > > >
> > > > Thanks.
> > > >
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]