36 lines
1.6 KiB
Markdown
36 lines
1.6 KiB
Markdown
Contributing To EpiphanyAgent
|
|
=============================
|
|
|
|
EpiphanyAgent is source-available and dual-licensed. That only works if the
|
|
project keeps clean rights to contributions.
|
|
|
|
Before sending anything non-trivial, read:
|
|
|
|
- `LICENSE`
|
|
- `CONTRIBUTOR_LICENSE_AGREEMENT.md`
|
|
|
|
By submitting a pull request, patch, commit, issue attachment, or other
|
|
contribution for inclusion in this project, you agree that your contribution is
|
|
submitted under the EpiphanyAgent Contributor License Agreement version 1.0,
|
|
unless the maintainers have accepted a different written agreement from you.
|
|
|
|
For small fixes, include this line in the pull request or patch submission:
|
|
|
|
```text
|
|
I agree that my Contributions to EpiphanyAgent are submitted under the
|
|
EpiphanyAgent Contributor License Agreement version 1.0.
|
|
```
|
|
|
|
For employer-owned, client-owned, organization-owned, generated, copied,
|
|
third-party, or otherwise legally complicated material, get explicit written
|
|
permission before submitting it. If you cannot grant the project broad
|
|
relicensing rights, do not submit the contribution.
|
|
|
|
Before accepting outside contributions at scale, the maintainers should record
|
|
the current Project Steward by legal name or formed entity in the repository or
|
|
signature records. The CLA already allows successor entities and assignments,
|
|
but boring paperwork now prevents expensive archaeology later.
|
|
|
|
The maintainers may reject or remove contributions when the rights are unclear.
|
|
That is not hostility. That is how the project avoids waking up years later
|
|
with one old patch holding the whole licensing plan hostage.
|