Describe what feature you'd like. Pseudo-code, mockups, or screenshots of similar solutions are encouraged!
Background
The project currently uses a CC BY 4.0 license, which is excellent for data and documentation. However, for the codebase, a more appropriate license like AGPL could provide better protection and clarity.
Suggested Changes
Add a new LICENSE-AGPL file in the root directory, specifying that the code is licensed under AGPL.
Update the README.md to mention the dual licensing strategy.
Update any headers in source code files to reflect the dual license.
Benefits
AGPL offers better protection against proprietary use of the code.
Dual licensing provides clarity on how different project components can be used.
Tasks
[ ] Add LICENSE-AGPL with AGPL text.
[ ] Update README.md.
[ ] Update source code headers.
What type of pull request would this be?
Enhancement
Any links to similar examples or other references we should review?
Describe what feature you'd like. Pseudo-code, mockups, or screenshots of similar solutions are encouraged!
Background
The project currently uses a CC BY 4.0 license, which is excellent for data and documentation. However, for the codebase, a more appropriate license like AGPL could provide better protection and clarity.
Suggested Changes
LICENSE-AGPLfile in the root directory, specifying that the code is licensed under AGPL.README.mdto mention the dual licensing strategy.Benefits
Tasks
LICENSE-AGPLwith AGPL text.README.md.What type of pull request would this be?
Enhancement
Any links to similar examples or other references we should review?
No response