OpenHospitalityNetwork / fedi-trustroots

Next generation federated hospitality exchange platform
https://openHospitality.network
GNU Affero General Public License v3.0
23 stars 3 forks source link

The project is not protected from being incorporated in proprietary code #18

Closed mariha closed 2 years ago

mariha commented 3 years ago

Suggested solution: change license to AGPL.

Things to consider

How to do it?

Please read the Open Source Guides, Legal - section 6: What if I want to change the license of my project?

Switching to a new but compatible license for new releases and contributions is different from relicensing all existing contributions.

If your project’s existing license is compatible with the license you want to change to, you could just start using the new license. That’s because if license A is compatible with license B, you’ll comply with the terms of A while complying with the terms of B (but not necessarily vice versa). So if you’re currently using a permissive license (e.g., MIT), you could change to a license with more conditions, so long as you retain a copy of the MIT license and any associated copyright notices (i.e., continue to comply with the MIT license’s minimal conditions). But if your current license is not permissive (e.g., copyleft, or you don’t have a license) and you aren’t the sole copyright holder, you couldn’t just change your project’s license to MIT. Essentially, with a permissive license the project’s copyright holders have given permission in advance to change licenses.

weex commented 3 years ago

Thanks for posting the reasoning around switching to a less permissive license. Agree it's valuable for the project to solve this.

mariha commented 3 years ago

There is an organization Software Freedom Law Center which provides free legal services to free and open source projects, including licensing, copyrights, patents, trademarks, and nonprofit governance, as well as education, consulting, and training.

If anyone felt like consulting a lawyer.

mariha commented 2 years ago

Fixed with Trustroots/trustroots#2481 and an update/sych with the upstream repo.

See: a4afd0d6392b85ee4487f841a42f80d74dd934de