License
This document describes the standards for selecting the appropriate license for open source projects authored by Allianz. It provides clear guidance for determining which license to apply depending on the nature of the material.
Default: MIT
The default license for Allianz open source software projects is MIT. This license is widely accepted within the open source community and also the default license for many enterprises such as Microsoft. Its simplicity and ease of compliance make it the preferred choice.
- Add a LICENSE.md file with the MIT license text and the Allianz copyright notice. You can do this via the Github license picker or by copying the license text from https://choosealicense.com/licenses/mit
- Keep that LICENSE.md file and copyright notice in any modified versions.
Default: CC-BY-4.0
The default license for Allianz open source non-software content (e.g., documentation, media) is CC-BY-4.0. It's roughly equivalent to MIT in terms of being permissive and having good cultural acceptance, but is designed for non-software works (e.g., license notice can be provided with a link rather than including a copy of the license text).
- In the case an entire repository should be released under CC-BY-4.0: Add a LICENSE.md file with the CC-BY-4.0 license text. It is unlikely you will want to do this, and it is not facilitated by the web interface license picker. The license text is available at https://creativecommons.org/licenses/by/4.0/legalcode.txt.
- In the case particular files or parts of content (e.g., documentation or a media file) should be released under CC-BY-4.0, note this precisely in the repository's README.md (example).
- If the released material is rendered or published, e.g., as or in web pages, it can also be useful to include a CC-BY-4.0 notice there, e.g., "This documentation is released under CC-BY-4.0", with a link to https://creativecommons.org/licenses/by/4.0/.
Default: CC0-1.0
The default license for Allianz open source non-substantial works is CC0-1.0. The CC0-1.0 license waives all copyright restrictions but still reserves trademark and patent rights. This makes it an appropriate choice for certain types of content, such as sample code snippets, boilerplate material, or configuration templates that offer minimal expressivity and business value. In these cases, the burden of maintaining copyright notices outweighs any potential benefit, making CC0-1.0 the most suitable option.
- In the case an entire repository should be released under CC0-1.0: Add a LICENSE.md file with the CC0-1.0 license text. You can do this via the Github license picker or by copying the license text from https://choosealicense.com/licenses/cc0-1.0
- In the case particular files or parts of content (e.g., code snippets in documentation) should be released under CC0-1.0, note this precisely in the repository's README.md.
- If the released material is rendered or published, e.g., as or in web pages, it can also be useful to include a CC0-1.0 notice there, e.g., "Code samples in this documentation are released under CC0-1.0", with a link to https://creativecommons.org/publicdomain/zero/1.0/.
Based on "Licenses for GitHub open source projects" from open source guidelines by Github, licensed under CC-BY