Rhizome is Open (Source) for Business
Stop reading. Go pull this post up on your mobile device. We'll wait.
Is the experience more enjoyable than you remember? These new mobile styles (*gestures encompassingly*) are courtesy Jason Huff. His April 27th pull request—a GitHub-centric way of submitting potential improvements to an open development project—was the first outside contribution to the site's code since we open-sourced earlier that same month. (If you still have display problems on your browser/device, create a new issue for us on Github).
There and Back (Again): Homebrew Computer Club at 38
Chuck Colby with Homebrew Computer Club wares (Credit: Amy Desiree Photography)
The buffet occupies two tables; the rest are covered with computer paraphernalia. In many ways, it feels like another tech meetup. Well-rehearsed elevator pitches are offered: "It's like Minecraft and The Sims smashed together and put on the web." One young programmer was attracted to the meeting because, "It's in the Bay Area, it's on Kickstarter, so why the fuck not?"
But this is the 38th Anniversary Reunion of the Homebrew Computer Club, the group that "launched the personal computing revolution," or so the story goes. Temporal and ideological anomalies abound. The hardware is all vintage, and while some participants are there in search of networking opportunities, others are still out to change the world, to put technological tools into the hands of the people. A veteran whips out his $90 paper tape reader, insisting no one can understand Homebrew unless they’ve hacked one. An Altair 8800 that famously produced music at an original meeting is here for an encore—no drastic restoration necessary, the thing just works. At serial inventor Chuck Colby's table, there's a stack of printouts which read:
Rackspace->Amazon migration status
Rackspace->Amazon migration status
Just wanted to keep everyone abreast of the latest developments.
As of last week:
I've completed the process of porting rhizome.org to Ubuntu 12.04. While doing so I dramatically simplified the underlying architecture of the site and cut down the number of files and software dependencies. I moved all site-related config files (previously scattered willy-nilly on the server's file system) into the code repository.
I've automated the processes of making changes live, as well as installing rhizome.org and its dependencies from scratch on any recent Ubuntu. (In other words, what I spent the last 4 months working on can now be accomplished in mere minutes--for the those curious I'm using the Fabric Python library)
We're now adhering to modern best practices! This will translate to greater speed and agility in all future site dev projects.
Next steps:
Before flipping the switch and canceling our Rackspace services, I've got to migrate archive.rhizome.org, 50k.rhizome.org and nymediaartsmap.org. 50k and the Media Arts Map will be challenging as they have databases and custom LAMP environments.
The migration must be completed before the site sprint, the productivity of that event depends on it. So the migration remains my top priority.
Thanks for putting up with my deferring of other requests during this process. Beginning in late June, a whirlwind of changes will be made to the user-facing website.