Closed mariha closed 2 years ago
Thanks for posting the reasoning around switching to a less permissive license. Agree it's valuable for the project to solve this.
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.
Fixed with Trustroots/trustroots#2481 and an update/sych with the upstream repo.
See: a4afd0d6392b85ee4487f841a42f80d74dd934de
Suggested solution: change license to AGPL.
Things to consider
reintegrating changes back to TR If we ever wanted to reintegrate our changes back to Trustroots, they would need to change their codebase to AGPL (or compatible) too, as MIT codebase can not contain AGPL licensed code.
updating our codebase with upstream changes Seems like we can, on the other side, pull up changes from MIT codebase even if our license is AGPL.
How to do it?
Please read the Open Source Guides, Legal - section 6: What if I want to change the license of my project?