chore: added licensing section

This commit is contained in:
Jonathan Barrow 2024-05-30 10:32:10 -04:00
commit fa6f1a6ada
No known key found for this signature in database
GPG key ID: E86E9FE9049C741F

View file

@ -14,6 +14,7 @@ Thank you for showing interest in contributing to Pretendo Network! As an open s
- [Messages](#messages) - [Messages](#messages)
- [Pull Requests](#pull-requests) - [Pull Requests](#pull-requests)
- [Tests](#tests) - [Tests](#tests)
- [Licensing](#licensing)
# Prerequisites # Prerequisites
Before diving into the contribution process, we recommend familiarizing yourself with our project's existing repositories. By studying our existing codebases, issues, and pull requests you will get a better sense of direction of how we operate. Additionally, please review our [Code of Conduct](CODE_OF_CONDUCT.md) to ensure a respectful and inclusive environment for all participants. Before diving into the contribution process, we recommend familiarizing yourself with our project's existing repositories. By studying our existing codebases, issues, and pull requests you will get a better sense of direction of how we operate. Additionally, please review our [Code of Conduct](CODE_OF_CONDUCT.md) to ensure a respectful and inclusive environment for all participants.
@ -112,4 +113,7 @@ If a pull request requires any database migrations, describe them in detail and
We ask that you have patience with us as we review your pull request. Pretendo Network only has a single full time developer, all other work is done by volunteers on their own time. Due to the sheer number of issues and pull requests, alongside our other general work and research, it may take us some time to fully review and decide on whether or not to merge your changes. We ask that you have patience with us as we review your pull request. Pretendo Network only has a single full time developer, all other work is done by volunteers on their own time. Due to the sheer number of issues and pull requests, alongside our other general work and research, it may take us some time to fully review and decide on whether or not to merge your changes.
# Tests # Tests
We do not require 100% code coverage in any tests. We do not currently have strict rules regarding tests, however we may ask that tests be provided for large or complex changes. We do not require 100% code coverage in any tests. We do not currently have strict rules regarding tests, however we may ask that tests be provided for large or complex changes.
# Licensing
Unless otherwise specified all code is licensed under [GNU AGPLv3](https://choosealicense.com/licenses/agpl-3.0), including that of outside contributions. This license allows users many freedoms to use our code in their own applications, including private and commercial use, while ensuring that all derivatives remain under this same license and keeps the source available, even when used over a network. A repositories license may not be changed by outside contributions unless permitted by the core development team, with good reason, and the consent of all relevant contributors has been given.