|
|
|
|
|
by jraph
543 days ago
|
|
Yeah, you probably don't want to license under MIT for proprietary use cases. You could take inspiration from the Qt project for how they do this. It takes one "non-commercial" project to release their code and people can use the MIT licensed version without restriction. The concept of non-commercial itself is shady: what if someone releases something non commercially, and then someone else uses it commercially? You probably want to get rid of this, it's complex to understand and to apply. You could have: - an AGPLv3 version that open source projects will be able to use (commercially or not, there are many successful commercial open source projects) - a custom proprietary license that someone can use only if they pay, and de facto their project cannot be open source Of course, this also means that your code can't be used by projects that want to be released under the MIT license. People will need to release under the AGPLv3. |
|