Problem
All Licenses need to be updated to the AGPL in the following Modrinth Released repositories:
There may be other repositories we may be interested in changing from MIT to AGPL but these are the most important as they are Modrinth Released.
Some of these have not been updated in a while. Maybe we consider updates and feature additions? Otherwise, perhaps we should strike-through them in the list.
Process
In order to get approval for license changes, we have to do the following:
- Get permission from all collaborators on the repository.
- RhythmicSys and Peashooter101 automatically give permission for these changes.
- Put a License section in the README.md that expresses what version AGPL begins and that MIT applies to the previous versions.
- Release a new version (any version is fine: major, minor, or patch).
- MIT will remain the license on prior versions as licenses cannot be retroactively applied.
- AGPL will become the license from that version onward.
We may also consider putting a license header on the top of files, but that may be a bit overkill?
Exceptions
Exceptions to the above rule changes are:
Problem
All Licenses need to be updated to the AGPL in the following Modrinth Released repositories:
There may be other repositories we may be interested in changing from MIT to AGPL but these are the most important as they are Modrinth Released.
Some of these have not been updated in a while. Maybe we consider updates and feature additions? Otherwise, perhaps we should strike-through them in the list.
Process
In order to get approval for license changes, we have to do the following:
We may also consider putting a license header on the top of files, but that may be a bit overkill?
Exceptions
Exceptions to the above rule changes are: