Note: this is just a preliminary write up. I need to sit down and touch on some specific goals and run them by some other developers. This isn't my first sprint, but the first one I've been working on in an organizational capacity, so bear with me.

Zopeskel is awesome, but it needs some work. :)

Primarily:

• Everything Martin Aspeli said in this thread (will break out and elaborate soon): http://www.nabble.com/Things-we-need-to-do-to-ZopeSkel-td15580583s6741.html
• Testing - As illustrated in some recent e-mail threads (will post links soon).
• ZopeSkel is hard to test - there's no easy way to simulate interactivity
  
• Polish/Enhance Existing Template
• atschema - I've done some work on this already, but it could use more enhancements
• plone - doesn't add localcommands (for things like adding views)
  
• New Templates
• New Localcommands
• Database settings utility + SQLAlchemy tables/mappers (as illustrated in Professional Plone Development, chapter 12
  
• R&D
• Figure out plausability of branching questions
• Figure out plausability of skipping questions if not applicable
• Documentation
• Document template use somewhere
• Document localcommands
  

Team

• Josh Johnson (josh under johnson at unc dot edu )
• Clayton Parker [claytron] (clayton at sixfeetup dot com) 

Communications

I've registered #zopeskel on irc.freenode.net.  Please join us there for planning prior to the sprint and communications during the sprint.