Licenses

OpenTEAM resources span software, documents, templates, and datasets. Clear licensing makes it easier to re-use and steward shared work. This page provides a practical starting point you can adapt for your project.

How to choose

  • Code: pick a permissive OSS license (e.g., Apache-2.0 or MIT) unless you need stronger reciprocity.
  • Content: use a Creative Commons license to communicate how text, slides, and graphics may be shared.
  • Data: make data licensing explicit (and include provenance, consent, and stewardship constraints where relevant).
  • Traditional knowledge / sensitive data: licensing alone is not sufficient—use governance and protocols.
Note: This is guidance, not legal advice. If you have questions about compliance or rights, consult counsel.

Software (code)

Common choices for open-source software:

  • Apache License 2.0 — permissive, includes an explicit patent grant.
  • MIT — permissive, simple, widely used.
  • GPLv3 — strong copyleft; derivatives must remain open under the same license.

Include a LICENSE file in your repository and add SPDX identifiers (e.g., Apache-2.0).

Written materials (content)

For reports, guides, slides, and documentation:

  • CC BY 4.0 — share and adapt with attribution.
  • CC BY-SA 4.0 — attribution + share-alike for derivatives.
  • CC0 — dedicate to the public domain (when appropriate).

If you include third-party images or text, ensure you have rights to relicense them.

Data

For datasets, schemas, and derived indicators:

  • ODC-By — attribution for database rights (commonly used in open data contexts).
  • CC BY 4.0 — often used for data releases when database-rights language is not required.
  • CC0 — maximum re-use; pair with clear citation guidance.

Always include metadata: who created it, when, how collected, and any constraints.

Practical checklist

  1. Identify the asset type (code, content, data, mixed).
  2. Pick a license aligned with intended re-use and reciprocity.
  3. Add a clear notice (LICENSE file, footer, or dataset README).
  4. Document provenance, attribution, and stewardship responsibilities.

More context

This page is inspired by the way open data communities describe licensing options and trade-offs. For a deeper dive, explore the Open Environmental Data Project’s licensing guidance.

View OEDP licenses page ↗