This is a pretty decent status to email, I think. it's short, but it feels pretty good.
*What Got Done* Well, the big thing we've all been waiting for finally happened: We're on the new server. We're running using tgext.pages as our CMS, and we've got something that looks pretty decent. We've put everything we can onto other servers, and our resources page reflects that. The old server is still getting some traffic, so we're not going to shut it down yet. Around the middle of the month, though, it will be time to close it out entirely. I've begun working on a buildbot setup for us. It's pretty basic, and we have errors right now, but we have something to show that things are at least moving. It's visible at http://buildbot.turbogears.org/ and once it's complete, I'll post the link on the resources page so people can find it easily. *Where Are We Now? *Alessandro continues his work as our resident ticket closing fiend. We have a couple of outstanding tickets that he is unable to reproduce. I haven't had the chance to confirm that they are already done, so am asking anybody who can help to do so. Once I'm happy with buildbot, I'll begin working on committing work to close out tickets, get releases done, etc. I want to have a way for us to see actual progress, and know that we haven't broken new things, so buildbot is pretty important. Finally, I looked at our traffic levels for the month of April. So far this year, the development ML has seen the most traffic in February. I think this is because that's when the project was more or less confirmed as "definitely not dead", but we kind of fell into too much of a holding pattern. We are picking up traffic and interest, though, and I'm pleased with that progress. With some work, we'll be back to a consistently high level of traffic by the end of the year. *What Will Get Done This Week?* I've begun setting up @turbogears.org email addresses. We'll be able to offer them up for a few people very shortly (probably by Wednesday). I've also focused on understanding buildbot. Turns out that you can do an awful lot with it, so even reading enough of the manual to make progress is slow going. Still, it's happening, and will be fully prepped by the middle of the week, I think. Right now, my big issue is setting up a buildslave to have a child virtualenvironment, so to speak. Actually, since I'm talking about it, let me ask: I'm running buildslave in its own virtualenvironment. I want the buildslave to create a virtualenvironment, and run all of its commands from that virtualenvironment, so that I can install programs and the like without introducing (possibly) conflicting packages into the buildslave's virtualenvironment. Has anybody else done this? Are there any tutorials on how to do it? I've not been able to find any yet, and that's my big holdup right now. That's all for this status report. Be seeing you during the week with more news as it develops :) -- Michael J. Pedersen My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected] My LinkedIn Profile: http://www.linkedin.com/in/michaeljpedersen -- 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.
