Predictix has agreed to help me host a TurboGears 2 + WSGI Components
sprint this November.  The sprint will be centered at the
predictix offices in Midtown Atlanta on on the 15th and 16th of
November imediately following the PyWorks conference.

But we've already got a satellite sprint in Atlanta, and I'm hoping
for others in London, Paris, or whichever other cities have the most
python web hotness.  ;)

Please join us and help us to do some cool stuff by signing up on:

http://docs.turbogears.org/SprintSeries2008#november-participants

I'm very excited about this sprint because we have a number of new
features in TG2 including a very nice new set of tools for
Authentication and Authorization, and Django Admin style automatic
CRUD generator, as well as our automatic transaction handler, an
updated config system, and a new soon-to-be released set of docs and
developer guides.

There are a couple of un-announced new pieces of WSGI awesomeness that
i'm hoping we can start to play with at the sprint too.

We'll also likely have a very close to stable release of the core
TurboGears 2 server and quickstart framework, so we'll have a very
solid basis to work on TG2 components, and on adding some shiny new
coolness to the TG2 ToolBox.

We will also have free pizza, and some the opportunity to improve the
python web development scene, even for those who don't use TurboGears
since the majority of our components are independently useful.

And don't forget to sign up at:

http://docs.turbogears.org/SprintSeries2008

if you can come.

-- 
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 Trunk" 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-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to