Need open source policy? Ask the DoD.

It’s coming up on a couple of years since I wrote about the reasonable approach toward open source software adoption put forth by the U.S. Department of Defense, which was ready and willing to use open source, but was not requiring a less-realistic all-open source or only-open source approach.

Today, we see that measured consideration of open source and its adoption has served the DoD well, given it just published a guide (PDF) regarding its experience with policy and adoption of open source software. This provides a valuable lesson to enterprise organizations considering use of, participation, increased adoption of open source software. Based on our findings that more than 60% of open source users and customers have no policies or guidelines for contributing to open source software (November 2009 survey of 1,711 open source users and customers), it is also needed.

Some highlights from the guide, titled ‘Open Technology Deployment – Lessons Learned and Best Practices for Military Software,’ which was nicely released under the open source Creative Commons Attribution ShareAlike 3.0 License, include:

*The guide begins with a nice explanation of ‘off-the-shelf’ software, a common phrase for commercial software purchased/procured by governments, as well as explaining open source software.
*It also walks through some of the fundamentals of open source that are often overlooked or lowered in priority in favor of cost, flexibility or other advantages of open source. This includes intellectual property rights, reuse, governance, forking and licensing.
*In addition to some more technical, government-related infrastructure needs and demands, the guide does a wonderful job covering some of the more aesthetic components of open source software development and community management, including the need to be inclusive, avoiding private conversations, practice of conspicuous code review, awareness and communication of roles and dealing with rude or poisonous members of communities. One key phrase in the report that sums up the wisdom here: ‘Community first, technology second.’
*Interestingly, the guide touches on practices associated with ‘devops,’ – the confluence of application development and application deployment via IT operations. In particular, it focuses on continuous development and delivery, more rapid development and release cycles, testing, transitioning to operations and maintenance. This is another indicator of how significant open source software can be to devops, and also of how pervasive the trend is becoming.
*Finally, the guide cuts through some FUD that may persist in some circles and verticals, including the public sector, regarding open source software, indicating nearly all open source software is backed commercially and available as Commercial-off the shelf (COTS), an important classification for government adoption. The guide also differentiates open source from freeware and shareware, which are often limited both perceptually and legally in government use.

The DoD guide — which similar to its memo on open source a year and a half ago represents a pragmatic, realistic approach to adopting and using open source software — is also another indicator of the drivers, advantages and challenges of open source software, which have typically been about cost, flexibility and avoiding vendor lock-in. We are tracking changes in those drivers, advantages and challenges as well with our take on the recent Future of Open Source Survey.

It’s encouraging to see this happening with the DoD and government, which has long had procurement, procedure and policy that was typically mismatched for open source software. The situation has now changed with vendors providing more support, certification, listings and adjustment to government adoption and use. Governments, led by organizations such as the DoD, are also adapting their way of doing things so that open source, cost savings, collaboration, avoiding vendor lock-in and all of the other benefits of open source are things they too can leverage.

My coverage of the first DoD memo on open source software in October 2009 also included the idea that this policy was taking shape amid more official, above-board adoption of open source software by both governments and enterprises. This means that rather than sneaking into organizations through developers, administrators, teams and divisions — largely under the door and through the cracks — open source software is now being adopted as part of official procurement and use. This trend, which we see continuing, also means a larger opportunity for paid support, services, components and other products from vendors focused on open source software.

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

1 comment so far ↓

#1 Hook’s Humble Homepage :: Free Software & law related links 23. V. 2011 - 29. V. 2011 on 09.26.12 at 3:45 pm

[…] 451 CAOS Theory: Need open source policy? Ask the DoD. […]