Definitely agree on MIT’s simplicity. I think GPL flavors may be a bit too restrictive so I’m digging the Mozilla Public License 2.0 more and more.
Here is a FAQ with some good info: https://choosealicense.com/licenses/mpl-2.0/
My main concerns as they relate to the community specifically:
- Must use an existing open source certified license, no custom anything
- Will any of these licenses keep devs from not getting involved
- Allow people to create apps/plugins(commercial or free) for Mugsy in whatever license they wish
MIT, LGPL and Mozilla all cover the first concern. As for the second, it’s probably going to be impossible to satisfy 100% of devs but I don’t want to use something that is inherently a turn off to large portion of them. GPL flavored licenses seems to have the largest amount critics due to the difficulty in satisfying all of the restrictions. The third is covered by allowing closed source Mugsy apps to interact at the API level instead of integrating with the runtime.
I think MPL is a good middle ground:
- Simple language(mostly)
- Allows easy integration with closed source code or projects
- everybody has the freedom to use the code as they please, but any enhancements to the open-source code that are distributed publicly have to be shared back.
So that’s pretty much we’re I’m at. If community members have specific concerns with MPL2, I would love to hear them. I want to have this wrapped up in the next week or so.