Plone Castle sprint, 11th to 15th of September 2003.

Teams will organize around specific tasks. The tasks will center around the development and preparation of the Plone 2.0 beta release. We are going to focus clearly on the work at hand to ensure Plone 2.0 is released by the Plone Conference. Plone development has slowed down because everyone is busy with customer projects. This is the time to focus on getting all the major work for Plone 2.0 complete.

Work on versioning is still scheduled, but a simpler version than initially planned.

Teams can be broken up into groups if required. Groups can be headed by Group Leaders. Alan Runyan and Alexander Limi will talk to the Team Leaders. This way we can dissiminate the information as fast as possible. Having Alan and Alex jumping directly from group to group does not work with large groups of people.

There needs to be specific tasks outlined, groups to assign tasks to - and Team Leaders that ensure the tasks are fulfilled (or can explain why they were not fulfilled).

All participants will be online in the #plone-sprint channel on irc.freenode.net. Remote participants are welcome - include your name on the relevant team - and remember to give us your email address. (Unless you're one of the "regulars" on irc :)

All people at the sprint should now have access to the Plone CVS, contact Limi if not.

Team leaders needed

• Zope/CMF, someone who can be the lead regarding the inner workings of Zope and CMF.
• Documentation, someone who has a wide perspective on the current state of documentation and knows the quick wins and can co-ordinate with the other leads.

The Teams

FormController Team (24 hours)

• Goal: To make all forms in Plone use the FormController validation and controller framework, write documentation along the way.
• Requires: explanation of the FormController framework (read the existing documentation)
• Team leader: Helge Tesdal
• Members: Maik Röder, Lukas Auersperg
• Remote Participants (include email): Kevin Teague (kevin@bud.ca)

Workflow Te (20 hours)

• Goal: To create Simple Workflow definition, change the existing workflows to be more usable, and (hopefully) make a simple workflow selector Control Panel. Also make submit/publish workflow the default.
• Requirements: Limi will explain the general concepts, you should be familiar with DCWorkflow.
• Team leader: Vincenzo Di Somma
• Members: Ulrich Eck, Francesco Ciriaci
• Remote Participants (include email):

Collector Cleanup Team (40 hours)

• Goal: Clear out the Collector - filter collector items into buckets: i18n, zope/cmf/plone, html/css/javascript, verify that the bugs exist, fix trivial bugs and bugs that have patches attached.
• Requirements: Organizational skills and efficiency. This is an ideal task if you want to help the Plone Team, but don't have any particular preference for a team
• Team leader: None yet, please consider volunteering
• Members: Michael Zeltner (eaon), Jensens, Pascal Habegger
• Remote Participants (include email):

Subclassing Team (4 hours)

• Goal: Wiring up the subclasses of CMFCore?/Default tools and Test, Test, Test!
• Requirements: Basic knowledge of Python and how tools work.
• Team leader: None yet, please consider volunteering
• Members:
• Remote Participants (include email):

Migrations Team (10 hours)

• Goal: Testing Migrations
• Requirements: Patience :)
• Team leader: None yet, please consider volunteering
• Members:
• Remote Participants (include email):

Control Panel Team (30 hours)

• Goal: Complete Control Panel Infrastructure and UI, add the most basic Control Panels
• Requirements: Some DTML reading (not coding ;) is valuable for porting existing CMF functionality from the ZMI. This is an excellent bite-sized task for those wanting to complete something very visual and useful
• Team leader: Alexander Limi
• Members: Lorenzo Musizza, Giorgio Pieretti, Tiziano Lattisi, Vincenzo Barone, Giuseppe Masili
• Remote Participants (include email):

Groups Team (10 hours)

• Goal: Ensure GRUF is sensibly integrated into Control Panel
• Requirements: Some experience with user folder, especially exUserFolder and LDAPUserFolder? is an advantage.
• Team leader: None yet, please consider volunteering
• Members:
• Remote Participants (include email):

Unit Test Team (20 hours)

• Goal: Get a unit testing framework into Plone using ZopeTestCase, set up basic unit tests using ZopeTestCase of the construction of a Plone site.
• Requirements: Knowledge of Unit Testing methodology
• Team leader: Stefan Holek
• Members:
• Remote Participants (include email):

Archetypes Team

• Goals: Get a stable Archetypes release that will ship with Plone 2.0, work on APE/ArchGenXML integration.
• Requirements: Archetypes experience
• Team leader: None yet, please consider volunteering
• Members: Sidnei, Phil, Ben, Riccardo
• Remote Participants (include email): Sylvain (syt@logilab.fr)

Versioning Team

• Goals: Give Plone a simple versioning mechanism that allows one version of an item to be worked on while the other is published.
• Requirements: Some knowledge about versioning, especially the ZopeVersionControl product.
• Team leader: Grégoire, if no other volunteers
• Members: Alberto (azazel), Grégoire (gregweb)
• Remote Participants (include email):

Documentation Team

• Document FormController and How it Works with Plone (8-16 hours)
• Document the different workflows from the WorkflowTe (10 hours)
• Document CAVEATS (upgrading of Plone 2.0) (8 hours)
• Document Collective (20 hours)
• Document ArcheTypes?
• Document ArchGenXML
• Team leader: Maik Röder
• Members: Jensens, Nate Aune, Daniel Nouri, Lorenzo Rizzatto, Georg Pleger
• Remote Participants (include email):

UI Cleanup Team (20 hours)

• Goal: Finish most of the Usability Cleanup list?
• Requirements: XHTML/CSS/Javascript skills - and the ability to take orders from Limi ;)
• Team leader: Limi
• Members: Michael Zeltner (eaon), Bernhard Buehlmann
• Remote Participants (include email): Tom Croucher (tcroucher@netalleynetworks.com)

Translations Team

• Goal: Clean up .pot file and the associated .po files, assorted i18n tasks (detailed inside), clean up Collector.
• Team leader: Jodok Batlogg is volunteering
• Members: Daniel Nouri, Georg Pleger, Lilli Taferner, Dominik Bartenstein, Thomas Bechter (remote)
• Remote Participants (include email):arthur@soqhome.com

Discussions / Other efforts

[Subversion Integration]?

For a Document Management backend

EduZope

Zope and Plone in a learning environment

Leader: Jodok Batlogg, Georg Pleger

Participants: Jensens, Nate Aune, Daniel Nouri, Lorenzo Rizzatto, Dominik Bartenstein, Thomas Geiger (remote)

[Relations Support in Plone]?

RDF, Topic Maps, Zope Topic Maps Archetypes - a discussion

Participants: Nate Aune, Jensens

[Epoz Rewrite]?

Epoz will be the default editor in Plone 2.0, and it's recently gone through an extensive rewrite. What remains?

[Portlets Discussion]?

The Portlets (aka. boxes/slots) in Plone need to work better with the site - the way it's done right now isn't very flexible. Workflows should govern permissions, and they should be easier to add (and not have layout code in the definition itself).