Hi everyone, It's been 4 months already since I started working for Arbor Networks, after a year and a half of independent working. In those 4 months, I've finished working on the book with Mark, put on an entirely new presentation at GLSEC and settled into a routine. With the dust settling, I've had a good opportunity to think about the best way to allot my time and new ways to get all kinds of people involved in making TurboGears even better and even more compelling. I've also recently had a chance to whip up a new API that I hope to be talking more about very soon.
There are so many ways to help make the project better, and I want to streamline *whatever you want to do to contribute*. docs.turbogears.org has been very successful, in my opinion. Yes, it's not done, but it's come a long way. Karl Guertin has done quite a bit there, but we've also had lots of good contributions from others like Fred Lin, Adam Jones, Jorge Vargas and Lee McFadden. (And I'm sure there are others, sorry for not mentioning you specifically!) Here are some ideas on how others can get involved. Feel free to talk about other ways in which you might like to help out. 1) I'm going to move TurboGears.org to WebFaction. I don't have the time or the desire to sysadmin my own box. The folks at WebFaction know how to run servers, and they specifically know how to run servers that run CherryPy. Plus, they're offering free hosting for the project. And they can run Trac and subversion as well. I would love to have someone to act as the TG sysadmin. There will be less to administer at WebFaction, but we do need to get all of the stuff moved from the current server over to WebFaction. Once it's there, we still need to maintain the things that we have. This is a very sensitive position, because someone with the keys to turbogears.org has access to our software distribution, which is something we have to take very seriously. 2) Some more release-management assistance. It's been two months since 1.0b1 came out. That's *way* longer than I anticipated or wanted, but I haven't been in a position to do anything about it because of other commitments (and this has also been true for Elvelind). As we've broken TurboGears up into an increasing number of separate, but related, projects, making a release has become a bit more cumbersome. What I'd really like here is for someone to help script an easier way to put out a TG release. 3) More hands in the code. I have gathered that there are many people who would love to help out on TG itself, but aren't sure where to start (both in terms of what to do and how to do it). This problem is easily solved and is especially important, because we're going to be heading more firmly into the First Class development cycle, hopefully with alpha releases before too long. There are some specific ideas for what we want to do in that release, but there are no specs that would allow someone other than me and a small group of others to really work on it. I'm not talking about stupidly long requirements docs that you find at a BigCo. I'm talking about a simple, plain English overview with a little detail as to what the feature is plus, importantly, some thoughts on how to do it, where to look, etc. If I'm correct about there being people who want to help out with TG core code (and you're one of those people), speak up and let's get you the info you need to contribute. 4) Do you like to write? In addition to all of the great docs work going on, it's to revamp the marketing portion of turbogears.org. I've given quite a bit of thought to the message to send (which sprang out of my work on the GLSEC presentation). We've got a very compelling story. We just need to tell it. Finally, I want to give a big thanks to everyone who has been building up the project through code and support on the mailing list. I used to be the #1 poster on the list, and for the past month or two I haven't even been in the top 10! As much as I really do enjoy emailing with everyone here, I know that it is simply impossible for me to keep up my earlier message volume and still get other things done. And, while working on the GLSEC presentation and the book, I didn't even have time to work on code. And yet, the code has still been growing and improving. Thanks to all for making that happen! Our googlegroup has more than 2,300 members. I'd like to make sure that any one of those 2,300 people that is willing and able to help out can do so easily. Please reply either on-list or offline if you're interested in helping out or if there's something I can do to to make it easier for you to help. Thanks! Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
