<div>Referência vista aqui:</div><div><br></div><div><a href="http://www.eejournal.com/archives/fresh-bytes/us-dod-gives-thumbs-up-to-open-source/">http://www.eejournal.com/archives/fresh-bytes/us-dod-gives-thumbs-up-to-open-source/</a></div>
<div><br></div><div>Documento aqui:</div><div><br></div><a href="http://www.oss-institute.org/OTD2011/OTD-lessons-learned-military-FinalV1.pdf">http://www.oss-institute.org/OTD2011/OTD-lessons-learned-military-FinalV1.pdf</a><div>
<br></div><div>Uma citação:</div><div><br></div><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
"Imagine if only the manufacturer of a rifle were allowed to clean, fix, modify or upgrade that rifle. The <br>military often finds itself in this position with taxpayer funded, contractor developed software: one <br>
contractor with a monopoly on the knowledge of a military software system and control of the software <br>source code. This is optimal only for the monopoly contractor, but creates inefficiencies and <br>ineffectiveness for the government, reduction of opportunities for the industrial base, severely limits <br>
competition for new software upgrades, depletes resources that can be used to better effect and wastes <br>taxpayer-provided funds."</blockquote>