Note that this page is about the 2004 Chandler sprint. See also ChandlerSprint2005.

Preliminaries

For introductory information and information about the other sprints going on at PyConDC2004, please see SprintPlan2004.

More details will appear here over time.

Duration

The sprints at PyConDC2004 are to be held from March 20 (Saturday) through March 23 (Tuesday), for a total of 4 days. We're going to be there for all 4 sprint days, so we invite sprinters to join in.

Please voice your opinions here or email Ted.

Cost

There is no cost to attend the sprints beyond registering for PyCon (and being present, of course).

Sprinters

Everyone is welcome! No prior Chandler hacking experience is required. Participants should either be experienced Python programmers, or interested in Chandler.

Please email Ted AND edit this page directly if you'd like to participate.

• Ted Leung (coach) send Ted email

• Jeffrey Harris (coach) (22-23 only) mailto:jeffrey@skyhouseconsulting.com

• Ben Laurie (22-23 only) - Ted suggests I spend time with Andi on security of repository sharing mailto:ben@algroup.co.uk

• Mike Taylor (20-21 only) mailto:bear@code-bear.com

• Philip Gaudette (21-23) mailto:philip_gaudette@fanniemae.com

• Roger Eaton mailto:rogereaton@brandx.net See Chandler and Mitch Kapor and Chandler/AntWeb Discussion

• Kapil Thangavelu mailto:kapil@plone.org - Splitting Time w/ Distutils Sprint

Sponsorship

This sprint is being sponsored by the Open Source Applications Foundation

Sprint Topic Ideas

What would participants like to accomplish? Choose from among the ideas below or add new ones. Register your votes below, and feel free to comment.

Right now we have a pair of topics:

• Dump/Restore data in the Chandler Repository as XML to allow backups and version upgrades
• Implement a remote repository using WebDAV as the protocol layer.
• Build a Chandler app/package

We plan to do technical introductions so that people have an idea of how things work in the Repository.

Comments

Please feel free to add any comments you like. Include your name for feedback; anonymous comments OK too. We hope to see you at PyCon!