AdelPlex
this site the web

Whitehouse.gov switch to Drupal

The new media team at the White House announced via the Associated Press that whitehouse.gov is now running on Drupal, the open source content management system. That Drupal implementation is in turn running on a Red Hat Linux system with Apache, MySQL and the rest of the LAMP stack. Apache Solr is the new White House search engine.

This move is obviously a big win for The OpenSource Community.

WASHINGTON — A programming overhaul of the White House's Web site has set the tech world abuzz. For low-techies, it's a snooze – you won't notice a thing.

The online-savvy administration on Saturday switched to open-source code for – meaning the programming language is written in public view, available for public use and able for people to edit. http://www.whitehouse.gov

"We now have a technology platform to get more and more voices on the site," White House new media director Macon Phillips told The Associated Press hours before the new site went live on Saturday. "This is state-of-the-art technology and the government is a participant in it."

White House officials described the change as similar to rebuilding the foundation of a building without changing the street-level appearance of the facade. It was expected to make the White House site more secure – and the same could be true for other administration sites in the future.

"Security is fundamentally built into the development process because the community is made up of people from all across the world, and they look at the source code from the very start of the process until it's deployed and after," said Terri Molini of Open Source for America, an interest group that has pushed for more such programs.

Having the public write code may seem like a security risk, but it's just the opposite, experts inside and outside the government argued. Because programmers collaborate to find errors or opportunities to exploit Web code, the final product is therefore more secure.

0 comments:

 

. . . Social Networks . . .

Usage Policies