I have been thinking about this for some time since TurboGears started to grow and expand its environment with tools like BackLash, Gearbox, Crank and so on.
TurboGears is a pretty big project that involves many components, which I'm currently maintaining or contributing to in some way. Even though I try to do my best gathering feedbacks, I'm sure I'm missing the priority or the needs for some of TG users out there. I thought that it might be a good idea to help anyone with a specific need or priority getting it resolved. For this reason if anyone wants to work on any side of a TurboGears component to solve one of his needs (from doc, to new features, to bugfixes) or just for fun I'll gladly help with guidance, explanations or reviews so that the changes you need can happen. Particularly the components that are part of TurboGears which I'm able to help with are: - tgext.crud & tgext.admin ( The Autogenerated Admin Backend ) - Sprox ( The DB abstraction layer and Forms for models generator ) - Ming ( MongoDB support ) - ToscaWidgets2 ( the Widgets, Forms and Validation framework ) - Beaker ( The Caching and Session storage framework ) - Crank ( the routing and dispatching system ) - Kajiki ( The Template Engine ) - Gearbox ( The toolbox that serves webapps, runs the tgshell and allows to write new commands ) - BackLash ( The debugger and error reporting ) - TurboGears2 itself So if there is any of those areas you are interested in working on or improving feel free to get in touch with me at [email protected] I'll gladly provided any help I can to setup your working environment and explain the code. -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/turbogears. For more options, visit https://groups.google.com/d/optout.
