High Quality
Open the downloaded document, and select print from the file menu (PDF reader required).
DEPARTMENTOFDEFENSE
6000
DEFENSE
PENTAGON
WASHINGTON,
DC
20301-6000
OCT
16
2009
CHIEFINFORMATIONOFFICER
MEMORANDUMFORSECRETARIESOFTHEMILITARYDEPARTMENTSCHAIRMANOFTHEJOINTCHIEFSOFSTAFFUNDERSECRETARIESOFDEFENSEDEPUTYCHIEFMANAGEMENTOFFICERCOMMANDERSOFTHECOMBATANTCOMMANDSASSISTANTSECRETARIESOFDEFENSEGENERALCOUNSELOFTHEDEPARTMENTOFDEFENSEDIRECTOR,OPERATIONALTESTANDEVALUATIONINSPECTORGENERALOFTHEDEPARTMENTOFDEFENSEASSISTANTSTOTHESECRETARYOFDEFENSEDIRECTOR,ADMINISTRATIONANDMANAGEMENTDIRECTOR,COSTASSESSMENTANDPROGRAMEVALUATIONDIRECTOR,NETASSESSMENTDIRECTORSOFTHEDEFENSEAGENCIESDIRECTORSOFTHEDODFIELDACTIVITIESCHIEFINFORMATIONOFFICERSOFTHEMILITARYDEPARTMENTSSUBJECT:ClarifyingGuidanceRegardingOpenSourceSoftware(OSS)References:SeeAttachmentIToeffectivelyachieveitsmissions,theDepartment
of
Defensemustdevelopandupdateitssoftware-basedcapabilitiesfasterthanever,toanticipatenewthreatsandrespondtocontinuouslychangingrequirements.Theuse
of
OpenSourceSoftware(OSS)canprovideadvantagesinthisregard.Thismemorandumprovidesclarifyingguidanceontheuse
of
OSSandsupersedesthepreviousDoDCIOmemorandumdated
May
28,2003(reference(a)).OpenSourceSoftwareissoftwareforwhichthehuman-readablesourcecodeisavailableforuse,study,reuse,modification,enhancement,andredistribution
by
theusers
of
thatsoftware.Inotherwords,OSSissoftwareforwhichthesourcecode
is
"open."
o
Thereare
many
OSS
programs
in
operationaluse
by
theDepartmenttoday,inbothclassifiedandunclassifiedenvironments.Unfortunately,therehavebeenmisconceptionsandmisinterpretations
of
theexistinglaws,policiesandregulationsthatdealwithsoftwareandapplyto
OSS
,
thathavehamperedeffectiveDoDuseanddevelopment
of
OSS
.
Attachment2containsclarifyingguidancetoaddresssome
of
thoseissues.IhaveaskedtheDirector,EnterpriseServices
&
Integration,to
work
withyourstaffsandidentifyotherbarrierstotheeffectiveuse
of
opensourcesoftwarewithintheDepartment,sowecancontinuetoincreasethebenefitsfromtheuse
of
OSS
.
AdditionalinformationtoclarifyhowexistingDoDpoliciesrelatetoopensourcesoftwarewillbepostedathttp://www.defenselink.mil
/
cio-nii/cio/oss/.Questionsconcerningthismemorandumshould
be
directedtoDanielRisacher,EnterpriseServices
&
Integration,at(703)602-1098
or
email.
address redacted for spam reason
avidM.WennergrenPerformingtheDuties
of
theASD(NII)/DoD
CIa
Attachments:Asstated2
3 Attachment 1ATTACHMENT 1REFERENCES(a) DoD Chief Information Officer (CIO) Memorandum, “Open Source Software (OSS)in the Department of Defense (DoD),” May 28, 2003 (superseded)(b) Title 10, United States Code (USC), Section 2377(c) Federal Acquisition Regulation (FAR), Sections 2.101, 12.000, 12.101(d) Defense Federal Acquisition Regulation Supplement (DFARS), Section 227.7203-5(e) Title 41, United States Code (USC), Section 253a(f) Federal Acquisition Regulation (FAR), Section 10.001(g) DoD Instruction 8500.2, “Information Assurance (IA) Implementation,” February 6,2003(h) DoD Directive 8320.02, “Data Sharing in a Net-Centric Department of Defense,”December 2, 2004(i) DoD Directive 5230.24, “Distribution Statements on Technical Documents,” March18, 1987
Add a Comment