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 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
