The other night I was on a panel discussion on Python Deployment at the Django-NYC meetup. The discussion was very good and I think everyone there got a lot out of it (I did). But the format wasn’t really suitable for going into great detail, showing actual code fragments or demos. I’ve written about aspects of our deployment strategy in the past on my personal blog and in comments on other sites, but it’s a continuing work in progress and I’m well overdue for an update. We also have a web-base deployment tool that, while the code has been open and available for a while, we really haven’t officially announced or publicized until now.

There are two angles to Python/Django deployment that I want to discuss. First, there’s deploying Django apps. Then there’s how we use a Django app to deploy Django (and other) apps. They are closely intertwined so I think I can’t really talk about one without talking about the other.

Last night Sky and I presented MediaThread at a Django meetup in NYC. We were invited to give a full presentation after a lighting talk back a few months ago. The event was held at Huge with about 20 people attending from a variety of backgrounds. The participants were engaged and involved, asking questions about our implementation, process, and student usage. We also heard a report back on the European DjangoCon and broke bread (and beer) with local Djangonaughts.

Here are some belated highlights from PyCon2010, straight from the Ministry of Silly Talks. The talks are all published on the PyCon website and all the video are now posted and organized at http://python.mirocommunity.org.

Everything is speeding up these days, even the authoring of books. Some information society researchers we know (including some of our friends from Eyebeam, Creative Commons and Shift Space) locked themselves up for a week in Berlin, and came out the other end with a print-ready book on the future of collaboration - Collaborative Futures.

Even though I didn't travel to Berlin, the authorship of the book was radically distributed and some of my writing made it into the final cut. A portion of essay I wrote last fall for a sociology seminar on the future on a (brief) history of version control systems and the significance of distributed version control systems made the cut.

The book will be released under a creative commons license, but they are also doing a print run of hard copies which will be available starting at the launch party, March 4th. Pre-order hard copy here (digital copy is available here).

There is alot of buzz right now around the latest version of Firefox which finally implemented the native <video> tag specified in html5 .

These developments were a hot topic at the Open Video Conference, which was about a whole lot more than just the video tag, but the timing was really perfect. For more about the OVC, see Jonah and Mark Phillipson's reports, as well as the announcement of our Open Sourcing of VITAL .

The introduction of the <video> tag is a pretty big deal. Up until now, to display video in a browser, you needed to use third party plugins embedded in object tags. This allowed for the video to be seen in the browser, but the video wasn't really part of the web page - it was trapped inside a box.

Jonah told me he had a spare ticket to yesterday's geo API hackathon at the Google headquarters last Thursday afternoon. I'd long been curious to see the fabled interior of the New York Googleplex, and the event also offered a chance to catch up with how NYC developers have been using with geospatial data. New York is, after all, a location-obsessed town.

I spent my weekend at HOPE, a hacker convention run by the good folks at 2600 Magazine. There were many interesting (and occasionally hilarious) talks on a variety of subjects, from the weirdest things you can send via the postal service to the basics of hacking DNA to a discussion of the GPS technology in NYC taxi cabs.

One of my favorites was called "Evil Interfaces: Violating the User". It was a taxonomy of manipulative UI methods that result from a situation where the goals of the designer are not the same as the goals of the user (for instance, they want you to pay attention to the advertising). The speaker, Gregory Conti, talked about how the most successful "attacks" result from an inversion of traditional UI design rules. So in some sense, it was a manual of "what not to do": distract the user from the content with motion or color, disguise non-content as content, add extra barriers between the user and the content he wants to see (interstitial ads), exploit user errors, set bad defaults, etc. However, it gave me some food for thought about our projects.