I'd like to propose that we declare the next stable TG2 release 2.0 and that we work together to get a release candidate by the end of the year.
We're very close, but if the next release is going to be 2.0 there are a half dozen tickets that should be completed, and we need to polish some stuff up including docs, testing, and polishing up the TG2 index. Because it's critical that we get this stuff out the door, i'm hoping to recruit a few people to help. There are a lot of places where people with a few hours to help, and a desire to see a modern full-stack component based framework succeed. TurboGears 2 is somewhat uneque in the modern web framework space in that it attempts to provide solutions for the archetectual problems that limited sites like Pownce, Twitter, and TG1 sites, that I've worked on in the past. TG2 provides an industrial strength framework that solves real problems like multi-database support, supports for horizontal partitioning (sharding) and other database scaling strategies. I'm about to release my first TG2 site into production at Compound Thinking, and it's provided a great platform, even while it was in beta. But, It's time to make things happen, and get a release out there and start letting people know about all the great work that has gone into this by Florent, Gustavo, Luke, Dan, Jorge, Chris P, and many others, as well as the great work done by component developers like Mike Bayer, Ian Bicking, and Ben Bangert (to name just a few). The core development team has some work to do increasing test coverage and getting things ready for a release and anybody who wants to help out should jump in and let us know. But in order for the release to go as well as it should we need some help from the rest of the community. We need to provide the best possible experience for people who come to try TG2 out in the new year. And that means: 1) Great docs 2) Nice people on IRC and the mailing lists 3) Quick turnaround on bug reports To that end, I think we should put together a "support team" in place to help monitor IRC, the mailing list, and the doc-comments RSS feed to make sure that questions that get raised get answered -- and that the answers get put into the official docs. This doesn't mean that you need to have the answers to TG2 questions, nor does it mean that you have to hang out on IRC and answer questions all the time, just that you'll help to take the initiative to match up questions with developers who can answer them and ultimately to make sure that the answers get recorded. If you're interested in joining this support team, please let us know. If you think you can help get it organized and make sure that it runs smoothly defintely let us know. I'd also love to have a couple of people who are interested in helping out with the TG2 docs. I've put a lot of work into things myself, but sometimes it's hard to see what's missing when you're too close to the problem. So, someone who can point out the missing links is helpful, and it would be super helpful if we had some better docs for FormEncode schemas, and complex widget form stuff. So if you're interested in joining the docs team, let us know. -- 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 -~----------~----~----~----~------~----~------~--~---
