Last year I hosted my first ever sprint at PyCon when the original TurboGears sprint leader had to work at the last minute. It was a totally intense and somewhat humbling experience. But I learned a lot and I got to work with lots of smart people on TurboGears stuff. And equally importantly, we all had a lot of fun. So, it was definitely worth it.
Well, one year later, and I’ve somehow ended up leading the TurboGears 2 effort. And I’m planning to host another sprint again this year. There’s a lot of interesting TurboGears 2 projects moving which would be fun to hack on this year. Chris has written a automatic UI generation app that works with turbogears (+pylons, and eventually others) called dbsprockets which looks really promising.
I’ve also heard some rumblings about some flex/turbogears/silverlight integration work, as well as building some TurboGears site components.
But I’d like to focus some attention on a “working together on the web” sprint. Part of being a good neighbor is in the python web framework wold is building reusable components.
People have said in the past that Python’s diversity of web-tools is a problem, and they do have a point it makes it harder to choose a framework, but even more importantly — as long as frameworks are isolated, it means lots of duplication of effort.
But, I think our diversity can actually be a huge advantage if we learn how to work it better.
We are all exploring various solutions to a complex set of problems. Diversity brings creativity by bringing wide ranges of experience to the community pool. But that only works when there is a community pool, so we all need to be committed to living and working together and learning from one another.
And fortunately TurboGears and Pylons and Zope 3 have all been traveling down the same path. We are all, in our own ways in trying to explode our respective “frameworks” various components into reusable libraries. And with the help of WSGI, Paste, WebOb, and other defacto standards, we’ve all been bringing a lot of those components together around the same set of well defined interfaces.
The more this happens, the more we are able to turn our web framework diversity into an huge advantage. We can work together where it makes sense, innovate in our own areas, and learn from one another.
So, while we work on TurboGears stuff this year, let’s make sure that we’re doing what we can to learn from the rest of the python web framework world, and to contribute back in whatever ways we can.
I think with a little bit of creativity and effort we can find lots of new ways to work together on the web.