SEGAS-00004 Open source licensing
Last updated: 24 May 2023
Open source code repositories maintained by the Home Office must be given an appropriate licence, this explains to users the terms under which that code can be used or modified.
This standard is broadly similar to the GDS Licensing Guidelines - it is in part based on that content, adopts the same convention on usage of the words ‘license’ and ‘licence’, and follows the UK Government Licensing Framework.
Requirement(s)
- Open source repositories MUST contain a licence file
- Open source repositories MUST have a licence that adheres to the Open Source Definition
- Open source repositories MUST state who owns the copyright
Open source repositories MUST contain a licence file
Ensure that there is a LICENCE or LICENCE.md file in the root of your repository. This should be included in the repository as early as possible. The LICENCE file should contain minimal or no other information beyond the licence itself and the copyright notice. See the LICENCE file for this site for an example.
Open source repositories MUST have a licence that adheres to the Open Source Definition
At the Home Office, you should in most cases use the MIT License for open source code.
If the MIT License is not appropriate for your code or project, you can select a different licence, provided it adheres to the Open Source Definition. The Open Source Initiative (OSI) maintains a list of approved licences that meet the definition.
Open documentation
Where repositories produce websites serving documentation, you should make it clear the documentation is licensed under the Open Government Licence (OGL). This is in addition to the LICENCE file and should be visible on the website, for example contained in the footer as on this website and the GOV.UK Design System.
Open source repositories MUST state who owns the copyright
The work that civil servants and contractors create for the Home Office is Crown Copyright. To declare this the copyright notice contained in your LICENCE file should read “Copyright © 2022 Crown Copyright (Home Office)”.
The year should be the year the code was first published. If the code is continually and substantially updated across several years, you can put the years between the first and its most recent update; for example, “2019‒2021”.