The GSA is currently planning forge.gov, which is widely assumed to be based on forge.mil, the much-discussed collaboration platform from the Defense Information Systems Agency, or DISA. forge.mil is a pretty incredible idea: a single destination for testing, certification, and software development in the Defense Department.
It sounds obvious, but the idea remains revolutionary. For the first time, there would be a single repository for source code that could be shared between the hundreds of agencies, commands, and programs in DOD. Developers would be able to share their work in a familiar, web-based environment. A previous version of forge.mil was pulled for unknown reasons, but the current iteration is based on the TeamForge product from CollabNet. If you’ve used SourceForge, you get the idea. The DOD is the largest consumer, and one of the largest developers of software in the world. Much of this software is redundant, locked up by vendors and integrators, can’t work with other software, and nobody remembers how to maintain it. There’s no doubt forge.mil was long overdue.
Continue reading... (1867 words, estimated 7:28 mins reading time)
Also tagged cac, collabnet, disa, forge, forge.gov, forge.mil, gsa, mcclure, No Category, open government, Open Source Software, pki, repository, teamforge, version control
|
Wednesday, August 18, 2010
I had a chance to talk with Matthew Burton, the former intelligence analyst turned open source cause celebre who just launched a tool that helps frame and understand arguments with imperfect evidence. It’s based on method called Analysis of Competing Hypotheses (ACH), which has been around for quite some time. Matthew and his friend Josh Knowles, though, have a tool that allows the ACH method to be used by multiple participants simultaneously. It’s fascinating stuff, so I’m grateful that he took the time to talk with me.
On a personal note: I’m delighted to see that Matthew is a fellow emdash enthusiast, as you’ll see below.
Continue reading... (1776 words, 1 image, estimated 7:06 mins reading time)
This is the ignite presentation I gave for the Mil-OSS WG2 conference today. It’s a tremendous group of sandal-shod revolutionaries who want to bring open source and the US Department of Defense together. You can sign up for the mailing list here. If you use your imagination and insert a lot of stumbling, fumbling, and false starts to this, you’ll have a pretty good idea of how it went. You can find the full presentation here. [Update: Josh posted a video of my presentation, so you don't have to imagine it.]
Continue reading... (1646 words, 16 images, estimated 6:35 mins reading time)
Also tagged community, dfar, dod, far, forks, gloss, gpl, military, miloss, Open Source Software, tivo, wenger
|
The adorably named “Snort” project has been the mainstay of open source intrusion detection systems for as long as I can remember. The success of Snort and its commercial wing, SourceFire, is one of the early successes of open source, especially in security. On July 5th, the Open Information Security Foundation, a consortium of companies and government agencies who want to experiment with new approaches to the IDS problem, released version 1.0 of their Suricata project. It’s great to see government agencies make use of the open source development process to collaborate with the private sector and advance technology in this important niche of the security ecosystem. But so far, the story is pretty boring.
But wait! It’s not boring at all, because at the same time as Suricata is released, the Washington Post’s Top Secret Nation series is running. A pall suddenly falls over every aspect of government, especially in security, and especially for Dana Blankenhorn of ZDNet. “Private open source security is not amused,” and neither is Blankenhorn, who is quickly becoming my favorite source of new material:
Continue reading... (840 words, estimated 3:22 mins reading time)
Brian Purchia of Burson-Marsteller has a post over on GovFresh about the value of open source to unions. His argument pivots on cost-savings. I think you could make a more expansive argument that includes risk mitigation and innovation, but describing the advantage to unions is an interesting angle I hadn’t seen before.
I noticed that Brian repeated the misunderstanding that San Francisco had the nation’s first open source policy. I don’t want to diminish his larger argument, but it’s important that we give credit where credit’s due. So for the record:
- May 28, 2003: DOD issues the “Stenbit memo,” which assures readers that open source is commercial software under the law, and can be used in the DOD.
- July 1, 2004: OMB issues OMB-04-16, making clear that open source can be used in the Federal Government
- September 30 2009: Portland, OR is the first city to issue an open source policy.
- October 16, 2009: The US Department of Defense CIO issues a memo reiterating that open source software is commercial software for procurement purposes, and encouraging DOD branches to include open source when they’re picking software.
- January 7, 2010: California‘s open source policy is published.
Continue reading... (290 words, estimated 1:10 mins reading time)
Courtesy CycleDog, Licensed CC-BY-NC
I was really pleased to read the announcement that Lockheed Martin’s social networking platform, EurekaStreams, was released as an open source project today. Lockheed is a very conservative company, and while they’re happy to use open source internally and on projects for their customers, this is their first experiment with actually running a project themselves. I think it’s a big deal, not just for Lockheed Martin, but for large corporations who are considering a more open, more innovative approach to software development. And yet, Dana Blankenhorn hates it:
I don’t see anything in Eureka Streams I can’t do in Drupal, or a number of other high-quality open source projects that have existed for years. Lockheed has reinvented the wheel — why?
So here’s the nice thing about the open source community: competition. If I think I’ve come up with a better way to solve a problem, it can easily compete with the incumbents. Low barrier to entry, we say. Let the best ideas win. Unless, apparently, the best ideas come from a company I don’t like.
Then things start going sideways:
Continue reading... (659 words, 1 image, estimated 2:38 mins reading time)
Gov 2.0 Expo is coming to Washington, DC next week. It’s the latest offering from the O’Reilly event machine, which is unmatched in its ability to generate buzz and get everyone excited about topics that they’ve never heard of.
I though I’d post the sessions that I plan to attend. You can subscribe to my calendar using this link. Below, I’ve included some highlights Hope to see you all there!
Apps for the Army Keynote Kickoff
5:10pm Tuesday, 05/25/2010, Location: Ballroom A
Lt. General Sorenson is the Army’s CIO. He has a deep understanding of how technology is shaping the armed forces, and that’s led him to launch the Apps for Army competition, which is a bold attempt to change the way the DoD innovates. Rather than relying on large contracts and central planning, he’s encouraging the folks at the “edge”, the end-users, to build apps that can solve their own problems. The awards are due in August, and I’m excited to get an update.
Continue reading... (722 words, estimated 2:53 mins reading time)
The Obama Administration’s Open Government Directive ordered Federal agencies to produce open government plans by April 7th, and while some advocates are disappointed, we have before us a bewildering number of initiatives to improve transparency, collaboration, and participation across the Government. It will not surprise you to learn that I spent some time looking for places where open source is being used in these plans.
I’m not sure I can recommend reading all of the plans cover to cover, but if you’re an advocate or have a vested interest in the future of a Federal agency, these plans are fascinating peek into each agency’s interior life. It’s not just the content of the plans, which run from exciting to comical to mundane. You can also learn a great deal about how agencies view themselves from the way these plans are presented and marketed. It will come as no surprise that the Department of Justice’s rather unlovely document spends a lot of time thinking about reducing its FOIA backlog. The Department of Energy clearly understands itself to be a first a research organization, based on its flagship data sets. The Department of Defense plan is crisp, to the point, and focuses on getting the behemoth to better collaborate and interact with other agencies, rather than the public.
Continue reading... (2771 words, estimated 11:05 mins reading time)
“Open source and open government are not the same,” I’ve been reading recently. When discussing the role of open standards in open government transparency projects, Bob Caudill at Adobe, is concerned that open source and open standards are being conflated. He likes open standards just fine, but:
“Open standards are driving for interoperability between systems or applications, while, the goal of open source is to make high-quality software available to the market free of charge.”
As an open source advocate, I’m surprised. What, I have to wonder, is so threatening about open source? Why the effort to take open source off the table? I’ve written on the topic before, and I didn’t think this was controversial — but apparently I was wrong. Andrea DiMaio at Gartner is more pointed:
“For those who have been following some of the vintage discussions about government and open source, this will probably sound like a déjà vu. I honestly thought that people had finally given up pushing the confusion between open source and open standards or open formats, but here we are again.”
Continue reading... (1667 words, estimated 6:40 mins reading time)
Earmarks are a notorious vehicle for pork, in part because they lay nestled inside opaque legislative prose. In the FY2010 budget, WashingtonWatch’s crowdsourcing effort identified 40,000 separate earmarks — about 75 for every elected official.
There was a lot of talk about earmark prohibitions earlier this week, and each party swears it will be responsible with earmarks this year. But how do we hold elected officials accountable to these pledges?
Well, we can start by ensuring that earmarks see the light of day. A coalition of transparency advocates, including Sunlight Foundation, Americans for Tax Reform, OMB Watch, and OpenRegs.com all call for earmark data to be published in a standard format, so they’re easy to find, easy to understand, and easy to analyze. You can show your support here: http://earmarkdata.org/petition/
And if you’re a developer, take a look at the schema. What kind of applications could we build on top of data like this? What if I could get an RSS feed of earmarks for my elected officials as they’re reported? What if we could automatically rank the worst earmark offenders? What if we could correlate earmarks with campaign contributions automatically? The mind reels.
I'm the Chief Technology Strategist for the Red Hat US Public Sector group, an open source and free culture advocate, a picky drinker, an amateur aesthete, and a dog enthusiast.
