Thanks Paul! Could you put the info about your local group on:
http://docs.turbogears.org/SprintOrganization I'll try to set some direction, write up some provisional "tg2 overview docs" this weekend which describe the way I expect things to fit together and work. Plain SA is the order of the day since elixir does not yet interoperate with plain SA in all cases, which was the deciding factor for me. ToscaWidgets will be the thing to handle forms, if and only if we can get them appropriately documented. I've talked the Repoze people into ripping out the dependency on ZODB out of their WSGI transactional middleware, and hopefully someone from that group will be available to help on one of the sprint days. I like their middleware because it handles transactions for multiple databases, two phase commit, and other slightly more complicated things for us, but still should provide a simple api for the simple one db one transaction per request case. --Mark Ramm On Dec 22, 2007 7:20 AM, Paul Johnston <[EMAIL PROTECTED]> wrote: > > Hi, > > >So, here's my crazy idea. Let's throw a giant TG2 sprint/party one > >weekend in January, and do it at various places all around the world > >on the same weekend. > > > > > Ok, I've put word around in my local area and got four people > interested. Hopefully we can get access to a room at Leeds university to > work in. > > We've got two Python programmers new to TG, I expect we'll get them to > create sample apps, document the process, challenge the existing > documentation and generally just give us a fresh pair of eyes on things. > > I'm probably best placed to look at transactional middleware, if that's > still in the plan. We've also got someone who's a whizz with TG widgets; > I wonder if best job for him is to look through ToscaWidgets, do some > docs, close off some tickets, etc. > > Thanks for kicking this off Mark. One thing you could do to help is give > a high-level steer on some issues. There has been some debate on whether > we should stick with dodgy Pylons conventions for compatibility, or take > the opportunity to tidy these up. The list seems to be evenly split, so > a high-level steer would help. I think we've settled on plain SA with > scoped_session as the default, with Elixir being a non-standard option. > > Regards, > > Paul > > > > > -- 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 -~----------~----~----~----~------~----~------~--~---
