It doesn’t yet show up on the front page, but if you look at the CherryPy downloads, you see that CherryPy 2.1 is out! Congrats to the CP team!
I’ve changed the svn version of TurboGears to use CherryPy 2.1 final, so TurboGears users will automatically get the update with 0.9.
Also of note, Ronald Jaramillo has released CatWalk 0.9 and has produced a spiffy survey application tutorial. Good work, Ronald!
I don’t have any statistics to share on this, but something that has just occurred to me is that there have been several instances over the past couple of weeks where people have mentioned that they’re new to Python while they’re asking questions about TurboGears.
Python has been my language of choice for a decade, and I’m happy to be contributing in some way to growing Python’s usage.
TurboGears 0.8a1 is available now!
This is a brief summary. The complete information about what’s
new can be found here: http://www.turbogears.org/about/changelog.html
* API improvements based on feedback and patches from the first public release. Seven people contributed patches to TurboGears directly, and there’s been quite a bit going on in the other projects.
* Easier production of XML output from controller methods
* Static file directories are set up in new quickstarted projects
* Updates to all of the main included projects
* IPython is used as the shell, if IPython is available
* Bonjour support on the Mac
* New getting started guide, and command line tool and configuration references and a new site template by Sebastian Jansson.
* Several bug fixes
After the slashdotting, Ian Landsman wondered what the extended effect of the slashdotting would be. Certainly, after serving more than 13,000 views of the screencast on Monday, things have tapered off. The 20 Minute Wiki is still getting 1,000 views a day! (That’s 80GB per day, for those watching their
waistline bandwidth usage). I haven’t had a chance to do a total tally, but I’m guessing that the screencast is up to 25,000 views.
The main TurboGears discussion Google Group has added about 100 people since Monday, crossing 350 earlier today. The announcements list crossed 100 today. Mailing list traffic is increasing, and people are coming up with some cool stuff. Interesting things are taking shape for 0.9!
Thanks to all of the people putting their energy into TurboGears!
Uchi Ogbuji spotted a Slashdot comment by Ian Bicking explaining why TurboGears is not a Rails clone. I don’t think I’ve come out and said it, but what Ian said sums things up quite well. TurboGears is every bit as compelling as Rails, but it’s not a clone. It’s built as an integration of preexisting components, to give you the full front-to-back development stack. We have lots of good tools and ideas to choose from and Rails is not the only idea well from which we’ll be drinking.
Though the parts of TurboGears are not clones of Rails features, David Heinemeier Hansson deserves huge credit for showing what a full stack web application framework could look like at a time when most tools, open source ones in particular, were designed to tackle only one piece of the puzzle.
Ronald Jaramillo has put together CatWalk, a simple model browser for TurboGears. I haven’t tried it yet, but from the screenshots it looks like it could be the start of something quite nice.
A Slashdotting can be very interesting if the thing most slashdotters are looking at is an 80MB file. I have no idea how many people (if any) were served up by the Coral cache. I don’t know how many people downloaded the file via BitTorrent.
I can see a thing or two by looking at my access log, and speaking with Jason I got some other fun facts.
About twice as many people viewed the 20 Minute Wiki screencast today as they did in the previous 23 days. It looks like over 13,500 now. The screencast was using an alarming 80-95Mbps for quite a bit of the day. Apache reports that TextDrive served up more than 1.2 terabytes for me today. Wow! Thanks, TextDrive!
As of now, my server at GoDaddy has served up another 67GB. Bob Ippolito has once again stepped up with capacity, this time on two different servers. Charlie Moad also provided a server. So, the load is now split up among four servers, which helps us all out I think.
As I write this, there are still quite a few people watching, so I’m guessing we’ll tack on another 1,000 views by morning.
Thanks to the folks who kept all of turbogears.org up and available for the whole day!
This is the kind of morning I like to wake up to. A very interesting one. The first thing I noticed was email saying my blog was down. (That’s due to a problem with my MySQL start up script… I guess the server rebooted but MySQL didn’t come back.)
Then I saw the mention that TurboGears has been slashdottted! Thanks to Guillem Cantallops Ramis for getting us on the front page!
And, I was really excited to see a message from Ned Batchelder letting me know that the first TurboGears job posting is now up at Python.org.
Wow. All of this on what is a weekend day for me.
Today, we had the first TurboGears Mad Dash. I figured that calling it a “sprint” is probably not accurate, given that most sprints last several times the length of today’s mad dash.
Including myself, we had 10 participants. Given that I had announced my desire to hold a sprint just a few days after TurboGears’ public release, the turnout was very good. Most of the people there were members of michipug (including two that I hadn’t met before), and we also had two hearty travelers from Cleveland.
I thought the day went well! Given that TurboGears is a three-week-old project (built on much older projects, of course), I hadn’t expected that we were going to generate thousands of lines of code (and we didn’t, of course). But, I had expected that people would get a chance to dive in a bit and learn what makes things tick and to collaborate and generate ideas.
On those counts, the day was exactly what I had hoped for. We’ve got some good direction planned for some TurboGears’ 0.9 features, and 9 more people have now had some experience working inside various parts of TurboGears. We also spotted a bug in the forthcoming 0.8 release… it’s always a bonus to be able to stop a bug before the software ships.
A few people expressed interest in doing another sprint, possibly for a longer time than this one (less mad dash-like). The next one will also get moving faster, given that people have more familiarity than they did before. On IRC yesterday, there was talk about a “remote sprint”, which sounds a bit trickier to pull off. We’ll have to see about the remote one, but I’m sure there will be another Ann Arbor in person sprint sometime in the not-too-distant future.
Here’s an interesting bit of trivia. Sawmill reports that the top browser at turbogears.org is… Python urllib 2.4!
6,500 eggs served.
(Of course, the 600MB used for serving up all of those eggs is nothing compared to the 400GB used for serving up the quicktime…)