<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.18.1">
</HEAD>
<BODY>
It's been a long time coming, but here it is. The DoD acting-CIO, Dave Wennergren, has signed an Open Source Guidance Memo which will hopefully provide a bit more clarity in the DoD's continued efforts to utilize open source solutions.<BR>
<BR>
Here's the link.<BR>
<BR>
<A HREF="http://www.oss-institute.org/index.php?option=com_content&task=view&id=363&Itemid=47">http://www.oss-institute.org/index.php?option=com_content&task=view&id=363&Itemid=47</A><BR>
<BR>
<BR>
The memo itself is pretty straight forward. It states:<BR>
<BR>
<BLOCKQUOTE>
<I>To effectively achieve its missions, the Department of Defense must develop and update its software-based capabilities faster than ever, to anticipate new threats and respond to continuously changing requirements. The use of Open Source Software (OSS) can provide advantages in this regard. This memorandum provides clarifying guidance on the use of OSS and supersedes the previous DoD CIO memorandum dated May 28, 2003 (reference (a)).</I><BR>
<BR>
<I>Open Source Software is software for which the human-readable source code is available for use, study, reuse, modification, enhancement and redistribution by the users of that software. In other words, OSS is software for which the source code is “open.”</I><BR>
<BR>
<I>There are many OSS programs in operational use by the Department today, in both classified and unclassified environments. Unfortunately, there have been misconceptions and misinterpretations of the existing laws, policies and regulations that deal with software and apply to OSS, that have hampered effective DoD use and development of OSS. Attachment 2 contains clarifying guidance to address some of those issues.</I><BR>
<BR>
<I>I have asked the Director, Enterprise Services & Integration, to work with your staffs and identify other barriers to the effective use of open source software within the Department, so we can continue to increase the benefits from the use of OSS. Additional information to clarify how existing DoD policies relate to open source software will be posted at <A HREF="http://www.defenselink.mil/cio-nii/cio/oss">http://www.defenselink.mil/cio-nii/cio/oss</A> . Questions concerning this memorandum should be directed to Daniel Risacher, Enterprise Services & Integration, at (703) 602-1098 or email, <A HREF="mailto:Daniel.risacher@osd.mil">Daniel.risacher@osd.mil</A></I><BR>
<BR>
</BLOCKQUOTE>
Take the time to review this document. It is a Guidance Memo (not a policy document) which means that it provides "guidance and clarification" on issues regarding open source within DoD. But it is very significant in that it states (in writing) that open source is a viable option and must be considered...and should be dismissed out of hand, as it has been by some.<BR>
<BR>
Congrats, btw, to all those men and women who have worked so hard and for so long to see this next step become a reality.<BR>
<BR>
Well done.<BR>
jmw<BR>
<BR>
<BR>
<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
=================================================<BR>
<BR>
<IMG SRC="cid:1256760805.7452.274.camel@localhost" ALIGN="bottom" BORDER="0"><BR>
<BR>
from the desk of<BR>
<B>John M. Weathersby, Jr.</B><BR>
Executive Director, OSSI<BR>
Voice: 202.683.7524<BR>
Cell: 601.818.7161<BR>
<BR>
<B><I>Ad maiorem Dei gloriam </I></B><BR>
<BR>
=================================================<BR>
<BR>
<BR>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>