-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using in commercial project #723
Comments
If I'm not mistaken you can do this under both licenses. The difference being that under GPL you need to make your code available to the customer, where as under BSD you don't. |
Hi, So basically I can choose whatever license I want to use be it GPL or BSD. Well, currently I don't want to make the code available to a customer. But plans might change and maybe project will be open sourced it is not yet final. In case it is open sourced do I have to keep my code under BSD or can I use for example Apache License or any other license? I guess I would have to provide Apache and BSD license text file with the source code or can I use dual licensing? Thanks. |
Again I stand under correction here but I think that if you choose RichTextFX under GPL then your code also needs to be GPL, whereas if you choose RichTextFX under BSD then your code can be licensed however you want - so yes then you could use or change to Apache. |
Thanks for the info. I will try to study both GPL and BSD. |
See Tomas' comment in #351. |
Hi,
This is more question about licensing than a bug. RIchTextFX is Dual-licensed under BSD 2-Clause License and GPLv2 with the Classpath Exception.
This is a bit confusing for me since am not so familiar with these two licenses. But could you please answer some of my questions.
I have a project that I am planning to sell probably on the yearly subscription plan.
Since it is commercial project am I allowed to use RichTextFX in that kind of project with subscription plan or one of those licenses does not allow that?
Btw I don't want to redistribute source code of my project.
Thanks.
The text was updated successfully, but these errors were encountered: