Please check if the PR fulfills these requirements
[x] The branch naming convention follows our guidelines
[x] Docs have been added / updated (for bug fixes / features)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
This PR adds a License file based on GNU AGPL v3.
What is the current behavior? (You can also link to an open issue here)
The repository is not equipped with a proper license file.
What is the new behavior (if this is a feature change)?
Licensing is introduced to the repo, following the baseline of aGPL v3.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Yes, not in the technical aspect though. Users now need to comply to the rules and behaviors exported in the aGPLv3 license and use, edit and distribute the software accordingly.
Add License file based on GNU AGPL v3
Please check if the PR fulfills these requirements
[x] The branch naming convention follows our guidelines
[x] Docs have been added / updated (for bug fixes / features)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
This PR adds a License file based on GNU AGPL v3.
The repository is not equipped with a proper license file.
Licensing is introduced to the repo, following the baseline of aGPL v3.
Yes, not in the technical aspect though. Users now need to comply to the rules and behaviors exported in the aGPLv3 license and use, edit and distribute the software accordingly.
Thanks @imgios for this precious hint!