Murray's Blog

New Plone people needed

The plone-based replacement for struggles forward. But it won’t get much further unless we find some new Plone developers who can help make it happen.

I have a whole other blog post that I’ve been waiting to publish for about a year as things have crawled forwards, variously delayed by an svn account request (Olav’s mango system fixed that problem), an unstable test server, and our single Plone developer’s extreme lack of time. It’s called “New Test it now” and it has lots of great links to a test site, our design plans, and where to report bugs. Instead you get this, based on my email to gnome-web-list:


The Plone stuff is now in GNOME’s svn, in the gnomeweb-plone module. We also have a backup of the database with the content (Zope format).

However, the svn is not quite in the desired structure and the “buildout” system probably needs some work. See the README for hints from Ramon.

I had hoped that Ramon could get those done so we would be more ready for other people to contribute but that’s obviously not going to happen. He is now busy with his PhD and can’t help us much more. I’m posting this after talking to him.

So we need some Plone people who can do this for us. I personally have no experience of Plone so I wouldn’t trust me to do it even if I taught myself about Plone.

What to do

The first aim should be to make it possible for anyone to install it locally to test it. That includes instructions (hopefully simple) so that even I could deploy it and test it. I would like some reassurance that this “buildout” system is the best way to do that. Experienced Plone sysadmins should know the answer to that.

Then I would like the Plone experts to generally check it over and point out anything that we could do better.

Then we can deploy it as a beta on, fix the last few bugs, and see if it’s good enough.

Exit mobile version