I've had a couple of major unexpected life changes in the past couple months, and haven't had as much time to work on TG2 as I had planned.
But thanks to various people in my life being flexible and helping out, I should have quite a bit more time over the next few months, so it's time to kick TG2 development up into high gear. I know at least one person who's using TG2 regularly, but it's not quite ready for widespread use. We are very close to having something usable, but there's a lot of things that we can do to make this release great. Sprint driven development: ------------------------------------- TG2 internals should be much easier to work with than TG1, but in spite of the fact that the user API is very similar to TG1, but the internals are very different, and I'd like to help some more people get up to speed on how hack on TG2. Partly because I know the current team can't do everything ourselves, and partly because I know more eyes on the code will be a good thing. I'd like to announce that I'll be organizing a sprint a month for the next several months. These sprints will be globally distributed, and we'll be using a Skype, IRC and other tools to make working together easier. But, there will be somebody hosting each of the sprints somewhere in the US. If others want to host sprints in their city/country I'd be glad to help make that happen (just e-mail me. My company (Compound Thinking) will host a sprint here in Ann Arbor Michigan on October 27th. Stanford University is planning to host a sprint in the Bay Area in November (we're still nailing down the exact date), and I think I may throw in a bonus sprint in Atlanta in November. I've created a page on the Wiki for Sprint Organization tasks: http://docs.turbogears.org/SprintOrganization TurboGears 2 Schedule: ---------------------------------- I'd really like to have a full TG 2 release before PyCon 08, so that means we need a release candidate in Febuary. Which means I'd like to see a preview release in November/December, and our first beta in early January. Of course, this is open source, we're all volunteers, and things can change very quickly so there's no promises. ;) TG2 Wishlist: ----------------- We have a working core system, which needs a bit of love to get in sync with the latest pylons code. Beyond that there are several features of TurboGears that I would like to see added into TurboGears 2 (as separate libraries that aren't in the core). * Configurable implicit transaction support * User account registration/authentication support libraries (like turnbogears.identity), but with support for user registration, etc. * a tg1 test compatibility layer, to aid user upgrades. * improved content negotiation * some automatic CRUD generation tool * a 1.0 version of ToscaWidgets with high quality docs. There's lots more that we can do if we have time and people to work on it. -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
