Open Source Software Trials in Government Final Report - Costkiller
Open Source Software Trials in Government Final Report - Costkiller
Open Source Software Trials in Government Final Report - Costkiller
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
provider should be asked to outl<strong>in</strong>e their own use of L<strong>in</strong>ux to support their IT<br />
<strong>in</strong>frastructures. When mak<strong>in</strong>g a decision on the selection of a future service provider,<br />
the user organisation should satisfy itself that the proposed provider can deliver<br />
capability on OSS and the L<strong>in</strong>ux platform; even if these are not a def<strong>in</strong>ed requirement<br />
today it would be wise to ensure the service provider contract has this capability as an<br />
option.<br />
Many service providers are realis<strong>in</strong>g the significant commercial benefits to both<br />
themselves and their customers of deploy<strong>in</strong>g OSS and <strong>in</strong>frastructure based on L<strong>in</strong>ux.<br />
The structure of some exist<strong>in</strong>g contracts might make the adoption of OSS desktops or<br />
L<strong>in</strong>ux-based <strong>in</strong>frastructure unpalatable for some providers today. User organisations<br />
should be aware of whether their service provider might fall <strong>in</strong>to this category. In one<br />
example a server consolidation of 180 W<strong>in</strong>dows NT servers <strong>in</strong>to 6 Intel/L<strong>in</strong>ux servers<br />
was possible; user organisations should consider whether their server topology would<br />
enable a similar consolidation, and what effect this would have on their current<br />
outsourc<strong>in</strong>g contract.<br />
5.3 Legal issues<br />
Organisations should be aware of a number of legal issues when consider<strong>in</strong>g <strong>Open</strong><br />
<strong>Source</strong> products.<br />
(a) The <strong>Open</strong> <strong>Source</strong> Licence<br />
Under <strong>Open</strong> <strong>Source</strong> licens<strong>in</strong>g an organisation can, if it wishes, modify the software<br />
and release the modified version <strong>in</strong>to the public doma<strong>in</strong>. The licence may require that<br />
the source code of the modification is also made available.<br />
This may not be necessary if modified software is used with<strong>in</strong> an organisation only,<br />
but the licence should be checked to ensure that this is the case.<br />
(b) The SCO suit<br />
SCO owns the rights to the ma<strong>in</strong> Unix operat<strong>in</strong>g system, Unix System 5 release 4, and<br />
claim that IBM, who licensed Unix from them, had copied a substantial amount of<br />
code <strong>in</strong>to the L<strong>in</strong>ux operat<strong>in</strong>g system and are <strong>in</strong> breach of SCO’s copyright. SCO<br />
launched a lawsuit aga<strong>in</strong>st IBM <strong>in</strong> 2003 which is still ongo<strong>in</strong>g.<br />
If proven, SCO’s claim might enable them to claim royalties from some L<strong>in</strong>ux users<br />
and they have entered <strong>in</strong>to a number of suits aga<strong>in</strong>st companies us<strong>in</strong>g both L<strong>in</strong>ux and<br />
Unix. In the only case to be resolved, at time of writ<strong>in</strong>g, aga<strong>in</strong>st DaimlerChrysler, the<br />
suit was substantially rejected.<br />
Organisations consider<strong>in</strong>g us<strong>in</strong>g L<strong>in</strong>ux should consider the risk from this case and act<br />
accord<strong>in</strong>gly – some suppliers offer <strong>in</strong>demnification aga<strong>in</strong>st legal action on systems<br />
supplied from them, this should be checked dur<strong>in</strong>g the procurement process.<br />
(c) Patents<br />
The European Union is consider<strong>in</strong>g changes to the EU directive on software patent<strong>in</strong>g<br />
which could have an impact on exist<strong>in</strong>g <strong>Open</strong> <strong>Source</strong> <strong>Software</strong>. Aga<strong>in</strong> the risk should<br />
be taken <strong>in</strong>to account when consider<strong>in</strong>g <strong>Open</strong> <strong>Source</strong> solutions. The implementation<br />
14