TurboGears 1.1 Sprint May 26th
I’m trying to help organize a globally distributed TurboGears sprint for may 26th. And it would be a great place to get your feed wet with developing for the TurboGears core. So, if you’re up for a learning experience, and you’ve got some time it would be great if you could lend a hand.
If anybody is willing to show up in Ann Arbor, I can provide food, a place to hack, and some good clean post-sprint debauchery. For, unfortunately those sprinting outside of the Ann Arbor area will have to provide their own space, food, and most of all their own debauchery.
If you’re interested in participating in the sprint, please join the Sprint Coordination mailing list.
We’ve got folks committed to:
- Migrating test infrastructure to CherryPy 3
- Finalizing the TurboGears 1.1 configuration system, and implementing what we decide on
- Workiing on the turbogears SQLAlchemy integration to make it easier to use multiple databases
- Doing some general clean up of open tickets
My personal goal is to help get the trunk into a usable state, which means tackling the configuration issue. Once people can run their existing projects on the trunk, TG developers (like me) will be able to do our daily work on turbogears projects on the trunk. Which in turn should help us to attract more developers and testers and continue to make TurboGears a great tool for rapid web application development.
Sorry - where’s the Sprint Coordination mailing list? Making it up to Ann Arbor is a long shot this time, but just might be possible…
Oops, I thought I linked it up in the blog post, but here it is:
http://groups.google.com/group/turbogears-sprint
Sounds good, I was there for a little while at the pycon sprints, and I have been meaning to keep my hand in. This will be a good way to get my hands dirty again.