Clarify the License FAQ regarding permissive licenses

cc https://github.com/sixtyfpsui/sixtyfps/issues/184
This commit is contained in:
Olivier Goffart 2021-03-04 08:51:22 +01:00 committed by GitHub
parent f4059ab3cf
commit aa4101cf13
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

7
FAQ.md
View file

@ -74,7 +74,6 @@ developing needs to be accounted for. However, support for bug fixes requires a
## I want to develop a free software product using SixtyFPS, but I don't like the GPL and prefer to use a non-copyleft license. ## I want to develop a free software product using SixtyFPS, but I don't like the GPL and prefer to use a non-copyleft license.
You can still release your own source code under a permissisive license such as BSD, MIT, or Apache license. You can still publish your own source code under a permissisive license compatible with the GPL, such as BSD, MIT, or Apache license.
Only binary distribution needs to comply to the terms of the GPL. It is up to those who want to distribute a The distribution of a binary or a package containing SixtyFPS still needs to be licensed under the GPL.
non-free version of the application to acquire a commercial license. It is up to those who want to distribute a non-free version of the application to acquire a commercial license.