Implementation guide for the Standard for Public Code

Publish with an open license This criterion in the Standard for Public Code

Requirements

All source code and documentation MUST be licensed such that it may be freely reusable, changeable and redistributable.

Tools

Resources

Software source code MUST be licensed under an OSI-approved or FSF Free/Libre license.

All source code MUST be published with a license file.

This may be impossible for civil servants in some jurisdictions so if that is a requirement they are effectively prohibited from contributing.

Note that there are some competing standards regarding machine-readable license info:

  • The Licensee tool is used by GitHub, GitLab, and others.
  • The REUSE spec seems to conflict with Licensee becuase it “consciously and opinionatedly breaks from convention” by looking in the LICENSES directory for licenses named after their SPDX identifier and does not take in to account the COPYING or LICENSE files which are the common convention by overwhelming majority.

Can we find good real-world examples of navigating this?

Examples

Having multiple licenses for different types of source code and documentation is OPTIONAL.

Examples

  • Docusaurus is using MIT for code and CC BY 4.0 for documentation

Tools

Further reading

  • License Compatibility, by Free Software Foundation Europe is a short video giving an introduction to what to think about for code with different licenses.