We're going to be doing parcel writing sprints, both here at OSAF next
week, as well as at PyCon in Dallas in late February. We'd love to have
people join us at PyCon.
What does it mean to do a "parcel writing sprint"? Two people pick a
small project, either to create a new extension parcel or extend an
existing one. They sit down and pair program for a few hours (or days)
to work on the project. Alternatively, a developer could work on a solo
project. By having several of these small projects going at the same
time, we have a group of people focusing on similar problems, raising
issues and learning from each other.
Even if you can't join the sprinting at PyCon, now would be a great time
to take 0.6 out for a spin and try writing some extension parcels. It
would be great to get feedback, both on what we've done so far
(including documentation), as well as what would be helpful next steps
to make Chandler more capable in supporting extensions.
If you are looking for inspiration, check out the list of parcels Morgen
put together (parcels that Morgen and others have started):
http://wiki.osafoundation.org/bin/view/Projects/ChandlerParcels
Also, a quick brainstorm the other day about parcels people would like
to write or see written yielded this list:
- query and get events from eventful/evdb
- calendar data sync with Apple iSync
- jabber client
- bugzilla interface
- exchange sync (talk directly to outlook exchange)
- backup and restore tool (back up data on collection by collection
basis)
- ups/fedex package tracker (a "parcel" parcel!)
- structural tension charting
- address book
- im presence manager
- irc client
- parcel manager (keep track of what extension parcels are installed)
We may not yet have good infrastructure to support each of these, but it
might be fun and productive to push and see where we fall down.
Cheers,
Katie
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
