3 ms·
I'm not sure what you want. Oversimplifying, there are three types of free licenses: * MIT/BSD: Everyone can use the code in any project, even in proprietary s
by gus_massa 4y ago
I'm not sure what you want. Oversimplifying, there are three types of free licenses:
* MIT/BSD: Everyone can use the code in any project, even in proprietary software. [1]
* GPL: You can use the code only in other GPL projects.
* AGPL: You can use the code only in other AGPL projects. If you use it in a server with real users, the code must be published.
What do you want:
1) If someone uses MIT/BSD code, then the new code must be MIT/BSD?
2) If someone uses MIT/BSD code, then the new code must be published?
3) If someone uses GPL code, then the new code must be published?
4) Now only the author can sue someone that is not following the license rules [2]. Do you want the government to be able to sue? Do you want anyone to be able to sue?
[1] Most of them have an attribution requisite, but let's ignore that.
[2] It's more complicated due to CLA and other legal stuff.
- thrwawy74 4y agoI want to make the far-reaching conclusion that even if something is MIT-licensed, because it was able to be developed and openly licensed and released to the public, at minimum the derived work must also be open (not MIT).
- gus_massa 4y agoNote that no every MIT-licensed project was developed by a big community or used public funds. Some are a minor project of a profesor in a private university, some are the code of an undergraduate thesis, some are just a weekend side project. In many cases people don't care too much about what other people does with the code and release it with a permissive license. If someone want their code to be used only in open source project, just use GPL or AGPL.