-
Notifications
You must be signed in to change notification settings - Fork 34
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
Discussion about licenses #4
Comments
I am not so sure about that.
The actual difference between free and open source software is much more nuanced (if existent at all): It is expected by the FSF that all free software should also considered OSS by the OSI. For the other way round, there may be cases where this is not true, but most of the OSS should be free software as well. If requiring free software over OSS is not so much about the amount of software matching that criteria, what else is it about? Free software is about protecting the user's freedom. From this perspective, nonfree software is a social problem. OSS instead has a more pragmatic approach, it is centered around the product being better in the end. Nonfree software just cuts efficiency on that road. This makes clear that requiring free software instead of OSS is about spreading freedom as a value. |
Thank you for your comment; but I do think that it would be impossible to distribute (or sell) GPL'ed software without its source code. |
The
The OP's point is that you are incorrectly using terminology in a way makes your article spread confusion. To me it sounds like your article is really about restrictive vs n ok non-restrictive open source licenses |
I agree. But whether distribution of source code is required when distributing software is a question of the specific license terms and not one of OSD-conformance vs. FSF-freedom. I agree with @bokov that your article – which I do find valuable as it discusses licensing in the R community 😀 – concerns the distinction between permissive vs. copyleft licenses, but not open source vs. free. |
No description provided.
The text was updated successfully, but these errors were encountered: