This Contributor License Agreement ("Agreement") documents the terms under which contributions are submitted to ORGII. It is intended for use with the repository's GitHub CLA Assistant integration.
This document is not legal advice. Maintainers should review and approve this text before enabling CLA enforcement.
- "You" means the individual or legal entity submitting a contribution.
- "Contribution" means any original work of authorship that you intentionally submit to ORGII, including code, documentation, tests, issues, pull requests, comments, designs, and other materials.
- "Submit" means any form of electronic, verbal, or written communication sent to ORGII or its maintainers for inclusion in the project.
- "Project" means the ORGII repository and any source, documentation, or assets maintained in it.
By signing as an individual contributor, you represent that:
- You are legally entitled to submit the Contribution.
- Each Contribution is your original creation, or you have the right to submit it under this Agreement.
- You grant ORGII and recipients of the Project a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute your Contribution and derivative works.
- You grant ORGII and recipients of the Project a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Contribution, where such license applies only to patent claims that you can license and that are necessarily infringed by your Contribution alone or by combination of your Contribution with the Project to which it was submitted.
- You understand that your Contributions may be distributed under the Project license, currently AGPL-3.0-or-later, or another license selected by the Project maintainers for the Project.
- You are not expected to provide support, warranty, indemnity, or liability for your Contribution unless you separately agree in writing.
If you submit a Contribution on behalf of an employer or another legal entity, you represent that:
- You are authorized to bind that entity to this Agreement.
- The entity is legally entitled to submit the Contribution.
- The entity grants the copyright and patent licenses described in the individual contributor agreement section.
- The Contribution does not intentionally include material that the entity does not have the right to submit.
- The entity understands that Contributions may be distributed under the Project license, currently AGPL-3.0-or-later, or another license selected by the Project maintainers for the Project.
If you are not authorized to bind your employer or organization, sign only as an individual contributor and submit only Contributions you are legally allowed to contribute as an individual.
By submitting a Contribution, you represent that a human contributor actively participated in the design and implementation process, that the Contribution was not authored entirely by artificial intelligence or other non-human intelligence, and that a human contributor reviewed the Contribution before submission.
You should not submit Contributions that include:
- Confidential information or trade secrets.
- Source code or assets copied from another project without a compatible license and attribution.
- Generated output, datasets, logs, credentials, or private user data that you are not permitted to publish.
- Work owned by an employer or client unless you have permission to contribute it.
The CLA Assistant signing flow should collect enough information to identify the signer and signing capacity, such as:
- GitHub username.
- Legal name.
- Email address.
- Signature type: individual or corporate.
- Company or organization name, when signing as a corporate contributor.
- Confirmation of authority to sign on behalf of that company or organization, when signing as a corporate contributor.
Maintainers may update this Agreement from time to time. If the Agreement changes materially, maintainers may require contributors to sign the updated version before merging future Contributions.