The Whitehouse.gov does Drupal!

Jan 22, 2010
Oshyn Labs
There is much debate in the webosphere about the White House's switch to Drupal

Tim O'Reilly's article offers insight into the project if you first need a little background info.

Slate's Chris Wilson titles his article, "Message Error: Why Running the White House Web site on Drupal is a political disaster waiting to happen."

Some tweeple oppose Wilson's view:
 
A rather ridiculous anti-#Drupal screed from Slate after WhiteHouse.gov migrates to it: jr.ly/x2em
Running the White House Web site on Drupal is a political disaster. - By Chris Wilson...

And more tweeple share insight from Stephen Shankland of CNET:
 
RT: @limonadephp: RT @imehesz: the White House goes Open Source! bit.ly/3xMKLp #php #drupal
White House Web site makes open-source move


Oshyn's Software Engineer / PHP Developer Andres Torres answers some Drupal questions

Does the White House's switch legitimize open source?

Andres: Definitely, this kind of software adoption creates an opportunity to educated more about the idea of open source software and what it is capable of doing. People will easily discover through web sites such as these, all the benefits and advantages they can get using open source applications or developing with them. And of course they have access to the Drupal software for free!
 
Is using open source in a government agency a good idea?

Andr's: Yes, from both a developer perspective and an open-source defender.
Drupal is not only a content management system but, in short words, an API to build custom websites as well, which makes Drupal a very strong tool for Web 2.0. I agree, Drupal users can have some bad user-experience when describing content creation, but is this an issue at the end? I mean what you really care about is that your site is strong and that it can keep all the info you want to share/publish, and of course, it has to be secure and scalable; that's Drupal's strength! Most of the time, when developing with a privative software tool you are tied to a specific platform meaning that if you what to implement a feature that's not provided by that software, you'll have to pay for it to be implemented. Using open source software means that you can modify your software to fit your needs since you have complete control over the source code. In terms of costs, you can find in the long term equilibrium between paying for privative platform which means paying for licensing, support, etc.., and maintain a open-source platform which does not offer any warranty because of its licensing terms (see GPL). Given all these reasons I can conclude that any site that has to be built strong, secure, and scalable, can use Drupal.