Examples
74 To illustrate the application of this guide, this section contains a number of examples.
Example One - Stand Alone Application
75 In this example, an agency wishes to license a stand-alone open source application under the GPL, without any warranties. The application is to be obtained free of charge via the web.
|
Recommendation |
Application |
Exception |
|
Only use approved licences |
GPL used. |
N/A |
|
Obtain warranties where relevant |
Warranties not expected for free-of-charge application. |
N/A |
Example Two - Internal Development
76 In this example, staff at a government department wish to use GPL components in a strictly confidential application, that will be distributed to other government departments and agencies. The components are available free of charge via the web, and will be dynamically linked to the application.
|
Recommendation |
Application |
Exception |
|
Only use approved licences |
GPL used. |
N/A |
|
Obtain warranties where relevant |
Warranties not expected for free-of-charge application. |
N/A |
|
Choose distribution strategy |
Limited distribution. |
N/A |
|
Manage the licence appropriately |
N/A |
Dynamic linking requires specific risk assessment and legal signoff. |
|
Avoid licence |
No conflicts, as only one open source licence. |
N/A |
Example Three - External Development
77 In this example, an external developer wants to use open source software under the GPL and a non-approved licence. The resulting application will be released by the agency on open source terms. The agency is paying market rates for the application. The developer wishes to use the new code for other customers.
|
Recommendation |
Application |
Exception |
|
Only use approved licences |
N/A |
Legal review shows alternative licence is weakly infectious and GPL compatible. |
|
Obtain warranties where relevant |
Warranties expected, as market rates paid. |
N/A |
|
Choose distribution strategy |
Open distribution. |
N/A |
|
Manage the licence appropriately |
Free to use. |
N/A |
|
Avoid licence |
No conflict, as licences compatible. |
N/A |
|
Prohibit open source in development contracts |
Consent given. |
N/A |
|
Permit with applicable contract provisions |
Permit GPL and other licence only. Developer owns new software, and licenses new and existing software to agency under GPL. Warranties apply equally to all licensed software. |
N/A |
|
Comply with distribution provisions |
Some redistribution requirements. |
N/A |
[ Previous ]