Slashdot Mirror

You'd think a defense contractor would know

They have a really good example.

Drupal OpenAtrium is more like a forum, (that can be subscribed to, with push-email notifications). In other words the source document/content stays securely archived on the Drupal discussion forum, with email notifications and links to source for stakeholders' direct access. This also helps security and access to the actual information.

Also, any document in a library might have its own discussion and commentary thread, (with subscriptions, etc.)

Here's links to the White House Github, and some more details:

http://github.com/whitehouse

http://www.whitehouse.gov/developers

http://www.whitehouse.gov/blog/2012/11/20/open-source-and-power-community

http://techpresident.com/news/23233/why-its-worth-noticing-white-houses-big-wet-kiss-drupal-and-github

http://www.linuxinsider.com/story/69839.html

http://techpresident.com/blog-entry/white-house-drupal-community-here-we-made-these

http://fedscoop.com/white-house-we-believe-in-using-and-contributing-back-to-open-source-software/

http://www.whitehouse.gov/blog/2011/02/11/whitehousegov-releases-second-set-open-source-code

To be fair, as a supplement to the President's memorandum, the U.S. CTO and CIO are leading programs to stop the proliferation of .gov sites and focus on converting all the PDF and static website content into machine-readable data so public/private services can communicate create content via APIs. Your sites won't need updating if the data coming from the government is being streamed into an embedded visualization app. You'd be able to consume whatever report or graph you need in whatever form you need it in, using the scope you want.

The video for the the CTO/CIO announcement (more for the Slashdot crowd): http://fedscoop.com/video-vanroekel-park-announce-new-government-digital-strategy/