DocOps Lab Contributor License Agreement (CLA)
This Contributor License Agreement (CLA or Agreement) sets the terms under which individuals may contribute to DocOps Lab projects. By adding your name or GitHub username to this document, you indicate agreement to it.
| By contributing to any DocOps Lab project that links prominently to this CLA document from its README file’s "Contributing" section, you assert that you have read and that you agree to the terms of this Agreement. |
1. Principles
DocOps Lab is a free as in freedom software organization. All projects are licensed under OSI-approved (typically MIT) or Creative Commons permissive licenses. We reaffirm alignment with open source community norms:
-
Transparency of terms
-
Permanence of license grants
-
Respect for contributor freedom
2. Scope
- Projects covered
-
All repositories under the DocOps Lab organization on GitHub are covered by this Agreement.
- Contributions covered
-
All source code, documentation, and related assets of or contributed to DocOps Lab are covered by this Agreement.
- Who it applies to
-
All contributors, including DocOps Lab members, maintainers, and users, are covered by relevant portions of this Agreement, to the extent it applies to their relationship with DocOps Lab.
3. Contributor Identity
- Capacity declaration
-
Upon contributing source code or content, contributors must specify whether they act:
-
in a personal capacity
-
as part of an employer’s work, with employer approval
-
under other constraints or conflicts
-
- Authority
-
Contributors affirm they have the legal right and authority to submit contributions, free of encumbrances or conflicting obligations.
- LLM usage declaration
-
Contributors must disclose use of large language models (LLMs), “AI agents”, “chat bots”, or similar tools in generating code or content that gets contributed. Private, behind-the-scenes usage of LLMs or similar tools to perform tasks that do not generate publishable code or content need not be disclosed.
See also DocOps Lab Generative "AI" Guidance for DocOps Lab’s policy on generative AI usage.
4. Licensing of Contributions
- Declared licenses
-
Contributions are licensed under the repository’s declared license or licenses.
- Acceptance
-
Contributors accept all licenses present in the repository.
- Permanence
-
DocOps Lab attests that all licenses are permanent. They will not be changed to more restrictive forms.
- Permissiveness
-
DocOps Lab attests that all licenses are permissive, in that they do not constrain fair-use or commercial reuse of the source code or its rendered artifacts.
- No Relicensing
-
DocOps Lab will not relicense or subvert contributions into restrictive or commercial forms.
5. Copyright
- Assignment
-
Contributors relinquish individual copyright in their contributions.
- Ownership
-
DocOps Lab holds sole copyright in all accepted contributions but instantly reissues permissively under an attribution-only license.
- Attribution
-
-
Individual attribution is preserved in Git commit history.
-
A byline may be preserved where such a byline exists in a document.
-
Downstream licensees are encouraged but not obligated to preserve individual attribution.
-
Licenses do require downstream attribution of DocOps Lab copyright.
-
6. Patents
- Non-assertion pledge
-
Contributors agree not to assert patents against DocOps Lab or downstream users for uses permitted under project licenses.
- Contributor freedom
-
Contributors remain free to patent or commercialize independent works based on contributions to DocOps Lab projects, provided that DocOps Lab’s licensed use and all downstream use under that license remain immune from liability or assertion.
7. Warranties
All parties affirm freely contributed original work.
- Contributor warranties
-
Contributions are affirmed as:
-
Original, OR
-
Properly licensed with DocOps Lab approval, AND
-
Not knowingly infringing third-party rights, AND
-
Provided without warranty
-
- DocOps Lab warranties
-
Existing and future source code are affirmed as:
-
Original or properly licensed
-
Not knowingly infringing third-party rights
-
Provided without warranty
-
8. Records
- Tracking
-
Contributor agreements will be publicly tracked in the DocOps Lab administrative repository.
- Methods
-
DocOps Lab may also use GitHub bots or commit sign-offs to automate agreement tracking.
- Confirmation NOT REQUIRED
-
Active signing is NOT required to constitute Agreement. See Acceptance below.
9. Amendments
- Versioning
-
CLA versions are tracked in Git.
- Notice
-
Contributors will be notified before their next contribution if the CLA is amended.
- New rights or obligations
-
Any amendment affecting contributors' rights, responsibilities, or warranties will result in a new version of this document. Contributors retain the prerogative to agree to or decline the new version before further contributions.
10. Code of Conduct
DocOps Lab adheres to a Code of Conduct that promotes a welcoming and inclusive environment for all contributors.
Contributors agree to respect these principles and to engage in constructive, respectful dialogue with other contributors.
11. Freedom of Association
- Voluntary
-
Contributors are free to associate or withdraw from contributing at any time. Past contributions remain under project license terms.
- Severable
-
This Agreement does not obligate future contributions.
12. Attribution & Recognition
- Documentation
-
Attribution appears in Git history.
- Code
-
Attribution appears in Git history.
- Recognition
-
DocOps Lab may feature contributors in credits, websites, or other venues outside the repositories themselves, at its discretion.
- Contributor identity
-
To indicate how they wish to be identified, contributors should append to this document by way of Git commit and pull request, their:
-
identifiers (optional)
-
name or alias
-
pronouns, titles, certs, etc
-
-
GitHub handle (required)
-
13. Dispute Resolution
- Preferred dispute process
-
Disputes are to be addressed first informally within the community.
- Mediation
-
If unresolved, disputes may be mediated by disinterested and mutually chosen members of the broader open-source community.
- Legal forum
-
Legal proceedings are a last resort. Jurisdiction defaults to the contributor’s home jurisdiction, if remote participation is permitted, or else the most convenient remote venue acceptable to all parties.
14. Acceptance
- Declaration of agreement (repeated)
-
By contributing to any DocOps Lab project that links prominently to this CLA document from its README file’s "Contributing" section, you assert that you have read and that you agree to the terms of this Agreement.