Dear Foodsoft developers,
For a while now an issue has been open to move Foodsoft’s license from the GPL to the AGPL. Since Foodsoft provides a web service, the real benefits of the GPL are only available in the AGPL, where also hosting Foodsoft requires sharing the source code (the GPL requires that only for redistribution).
Because the AGPL is just a bit more strict than the GPL, there is no developer consent needed to make this change, as far as I understood (everything allowed within the AGPL is allowed within the GPL).
For configuration changes, I’d like to make an exception, so that people experimenting with ‘stock’ Foodsoft do not need to setup a server to host their source code. This makes it easier for new installations to get started. Any real code changes will need to be published.
Please see foodsoft#496 for more information.
Replace GPL with AGPL
Mark config/app_config.yml, config/database.yml and config/environments/* as public domain.
Add a note to the README for people somewhat newer to licensing:
Foodsoft is licensed under theÂ AGPLÂ license (version 3 or later). Practically this means that you are free to use, adapt and redistribute the software, as long as you publish any changes you make to the code.
For private use, there are no restrictions, but if you give others access to Foodsoft (like running it open to the internet), you must also share your changes under the same license. This can be as easy asÂ forking the project on Github.
To make it a little easier, configuration files are exempt, so you can just install and configure Foodsoft without having to publish your changes. These files are marked asÂ public domainÂ in the file header.
If you have any remaining questions, pleaseÂ open an issueÂ or contact theÂ mailing list.
Questions to you
- Are you ok with this?
- Will you be happy to release any future contributions under the AGPL?
- Was anything missed?
This question is open for 2 more weeks, until the 10th of November.