Difference between revisions of "Contributor Agreement"
(Update contributor agreement link) |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[Main Page]] > [[Development]] > [[Contribute code]] > Archivematica Contributor's Agreement | [[Main Page]] > [[Development]] > [[Contribute code]] > Archivematica Contributor's Agreement | ||
| − | In order for the Archivematica development team to accept any patches or code commits, contributors must first sign this '''[ | + | In order for the Archivematica development team to accept any patches or code commits, contributors must first sign this '''[[Media:Archivematica-CLA-firstname-lastname-YYYY.pdf|Contributor Agreement]]'''. |
==Why do I have to sign a Contributor's Agreement?== | ==Why do I have to sign a Contributor's Agreement?== | ||
| Line 12: | Line 12: | ||
Examples from other projects include: [https://www.irods.org/index.php/iRODS_Contributor%E2%80%99s_Agreement iRODS] and [http://www.canonical.com/sites/default/files/active/images/Canonical-HA-CLA-ANY-I.pdf Ubuntu] (Canonical). | Examples from other projects include: [https://www.irods.org/index.php/iRODS_Contributor%E2%80%99s_Agreement iRODS] and [http://www.canonical.com/sites/default/files/active/images/Canonical-HA-CLA-ANY-I.pdf Ubuntu] (Canonical). | ||
| + | |||
| + | |||
| + | [[Category:Process documentation]] | ||
Latest revision as of 10:39, 24 April 2023
Main Page > Development > Contribute code > Archivematica Contributor's Agreement
In order for the Archivematica development team to accept any patches or code commits, contributors must first sign this Contributor Agreement.
Why do I have to sign a Contributor's Agreement?[edit]
One of the key challenges for open source software is to support a collaborative development environment while protecting the rights of contributors and users over the long-term. Unifying Archivematica copyrights through contributor agreements is the best way to protect the availability and sustainability of Archivematica over the long-term as free and open-source software. In all cases, contributors who sign the Contributor's Agreement retain full rights to use their original contributions for any other purpose outside of Archivematica, while enabling Artefactual Systems, any successor Foundation which may eventually take over responsibility for Archivematica, and the wider Archivematica community to benefit from their collaboration and contributions in this open source project.
Artefactual Systems has made the decision and has a proven track record of making our intellectual property available to the community at large. By standardizing contributions on these agreements the Archivematica intellectual property position does not become too complicated. This ensures our resources are devoted to making our project the best they can be, rather than fighting legal battles over contributions.
Do you have examples of Contributor's Agreements from other projects?[edit]
The Archivematica contributor's agreement is based almost verbatim on the Apache Foundation's individual contributor license.
Examples from other projects include: iRODS and Ubuntu (Canonical).