WhiteHouse.gov Goes Open Source; Runs on Drupal
The great Drupal switch came about after the Obama new media team, with a few months of executive branch service (and tweaking of WhiteHouse.gov) under their belts, decided they needed a more malleable development environment for the White House web presence. They wanted to be able to more quickly, easily, and gracefully build out their vision of interactive government. General Dynamics Information Technology (GDIT), the Virginia-based government contractor who had executed the Bush-era White House CMS contract, was tasked by the Obama Administration with finding a more flexible alternative. The ideal new platform would be one where dynamic features like question-and-answer forums, live video streaming, and collaborative tools could work more fluidly together with the site's infrastructure. The solution, says the White House, turned out to be Drupal. That's something of a victory for the Drupal (not to mention open-source) community. [...]
Let's really try to extract the last drop of possible meaning from a choice over a CMS. Squint a bit, and it's possible to see the White House's move to open-source software as a move towards the idea that collaborative programming can inspire -- or at least, support -- a more distributed politics. [...] This idea, that a politics crafted by the people could be a powerful thing indeed, emerged in a slightly mutated way during the Obama presidential campaign, but has arguably receded below the surface during the first nine months of the Obama Administration. First the WhiteHouse.gov CMS gets more open, then the White House OS? Perhaps.
Recent blog posts
- Trends for 2010?
- Administration Launches Comprehensive Open Government Plan
- Social Web Counter
- Promising Practices Presentation at eCitizenship Institute
- Participatory Budgeting in Cologne, Germany
- Collaborative Architecture in Second Life
- WhiteHouse.gov Goes Open Source; Runs on Drupal
- Use of Social Media in Urban Planning