Before I talk about the future, I'd like to look at the past a little bit. TurboGears has a good history. It's one of the older web frameworks in the Python world, and it managed to have a decent following for a long time. You can see that by looking at the history of the message counts for this ML. They're over at http://groups.google.com/group/turbogears-trunk/about
The strongest period of time on the list was from Nov 2008 to Mar 2009. Ironically, Mar 2009 was when I first started looking at TurboGears. I'm not sure what happened, but traffic on the ML took a major dive that month. From there, a slow but steady decline is visible. In fact, most of 2010 shows traffic to be at an all time low, with May not even having a single post. My ultimate goal is to fix that. I want TG to become what it once was in popularity. I want to make TG into something people look at and say "Wow". As it stands right now, we're a long way from that. We can fix that, though. To that end, here's my current plan: First: Complete the migration from the current server onto beta.turbogears.org. Move the live tickets into SF.net's Allure platform. Give us a new face, and start using our own product. Second: Release 2.0.4. We have some bug fixes in place already, we just have to complete any remaining tickets and do the release. Third: Release 2.1.1. Same deal, we just have to complete the mandatory minimum tickets for it. I hope to have *all* of that done by the end of April. Once we've accomplished that, it's time to begin working towards 2.2.0. This is where the work will become difficult. I have a number of goals for 2.2.0. - Bring testing coverage to 100% - Improve documentation. Overall goal is to make docs into a book in a few major parts: Tutorial (take a project from idea to maintenance), alternatives and extensions (to help get projects moving quickly), and finally a reference section at the end. - Close out all bugs that can be closed without introducing backward incompatibility *or* deprecation warnings. - New features will be limited to things that don't introduce backward incompatibility *or* deprecation warnings I want to release 2.2.0 by the end of this year. Between now and then, I plan to release incremental improvements to 2.1, so that we can enjoy the benefits of the progress. I'm hoping that these releases will help to bring TG2 back onto the radar for python web developers. So, there you have it. That's my goals and plans. What do you all think? -- Michael J. Pedersen My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected] -- 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.
