FarmData2 is a Free Cultural Work. This document outlines the licenses that apply to FarmData2 and the agreement which governs contributions. Complete copies of these documents can be be found in the licenses directory. All copies and forks of FarmData2 must be maintained in compliance with those licenses.
All contributions to FarmData2 will, as a part of FarmData2, be licensed under the applicable license agreements as described below. Thus, before any contribution will be accepted the contributor must certify that they have the right to grant FarmData2 a license to use, modify and redistribute (with or without further modification) the contributed intellectual property under the applicable license agreement. This is done explicitly when when a contributor submits a Pull Request. Every pull request automatically contains a "Licensing Certification" section stating that the contributor certifies that the contribution satisfies the terms of the Developer Certificate of Origin. When posting content to any public forums of the project (for example, but not limited to, issue trackers, message boards or discussion areas), the act of posting is here in defined as an implicit certification by the contributor that their contribution satisfies the terms of the Developer Certificate of Origin.
As described above, contributors license their intellectual property to FarmData2. Thus, they always retain the copyright to their intellectual property.
The code and documentation in FarmData2 are licensed using the following license agreements.
All code in the FarmData2 project is licensed under the GNU General Public License v3 (GPL-3.0).
All other content, including documentation, commit messages, issue tickets, pull request text and postings in Zulip, is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License (CC-BY-SA-4.0).
Attribution of contributions to the FarmData2 repository are maintained in the logs of the git version control system.
Attribution of content in public forums is typically maintained by the appropriate forum (e.g. threads, usernames, cross linked issues, etc). If not however, it is the contributor's responsibility to ensure that proper attribution is made based.