-
Notifications
You must be signed in to change notification settings - Fork 2
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
nest2D
is not Open Source
#4
Comments
Thx, for feed back. |
This is about intent on your part and what type of license you want for your work. It looks like there's some ambiguity of which portions are libre/free/open. For example, there's a FOSS license under the You can refer to "How to Use GNU Licenses for Your Own Software" on gnu.org. Both gnu.org and opensource.org have FAQs to help answer some questions about licensing (gnu.org FAQ, opensource.org FAQ). Further, as I linked above, it looks like there's pretty restrictive wording in the "Terms and Conditions" page, which you might want to review. As stated, to me, it looks like you're not only restricting the software but also any digital artifacts downloaded from |
From your project description, you say
but you do not provide a license for the project, making the project "closed source" (at least here in the USA) since there is no indication what license the project falls under.
Additionally, looking at the nest2d.online terms and conditions page, there is the following verbiage:
Which explicitly prohibits reproduction, reuse or resale.
"Open Source" has a generally accepted meaning of being able to use the digital artifacts for commercial purposes. The OSI and Wikipedia's entry on open-source licensing both articulate that commercial re-use is a (generally accepted) requirement of an "open source" license.
The term "free and open source" is especially misleading in your project as this is generally considered to encompass the ideas of "free software" and "open source".
If you mean free as in gratis, then you should say "free of charge". If your intent was to be transparent about your code by publishing it, you should say "source available", not "open source". As stated, this is misleading as someone casually looking at your project would mistake it for a free and open source project that they could reproduce, alter and repackage/resell if they desired.
The text was updated successfully, but these errors were encountered: