3 ms·
>> I want anyone to be able to do whatever they want to with my code. That includes developers wanting to create a proprietary application. Telling them they ca
by phkahler 10y ago
>> I want anyone to be able to do whatever they want to with my code. That includes developers wanting to create a proprietary application. Telling them they can't is not freedom.
You emphasized anyone but by allowing developers to take the code proprietary, their users (which are using your code) are being denied the freedom you promote. This is of course the distinction between GPL and BSD-type licenses. One gives developers all the freedom they want while the other ensures that all users (including those using derivative works) are given those freedoms.
>> I feel we've lost ourselves in the freedom of users and forgotten about the people that make the applications for the users.
No, we have not. One form of license ensures all users have the right to do whatever they want with the code. The other form (which some call permissive) grants the right to deny others those freedoms. I understand both stances, but I believe calling the right to deny others rights "permissive" is rather misleading.
- mook 10y agoDon't forget the weak-copyleft licenses like the MPL, where it's perfectly fine to use it in commercial projects, but all users are guaranteed access to the copyleft source code (but not the proprietary code on top).
- thesuitonym 10y agoThis is exactly what MIT and BSD licenses do.
- arglwarg 10y agoNope (also that would imply there is not functional difference between non-reciprocal licenses like MIT/BSD and a reciprocal one like MPLv2). The original article highlights LibreOffice and its success using the reciprocal MPLv2 not without reason. [Edit: mixed up the first paragraph.]
- snovv_crash 10y agoFalse. If I take a BSD/MIT library and fork it, I don't need to contribute the changes back. The MPL(v2) forces forks to be open source, but any files added to the project can remain closed source allowing it to be used as a library for closed source applications.
- thesuitonym 10y agoOkay but that's not what I was replying to. The post I replied to made no mention of reciprocity, only saying that the original code was available.
- eropple 10y agoHe explicitly calls out "copyleft source code." That means reciprocity.
- quadrangle 10y agoCopyleft is about pay-it-forward not reciprocity. There's zero reciprocity in copyleft besides the incidental fact that updates paid-forward to others might be discovered and accessed by the original person who gave you the software (or that you could share the updates back in reciprocity, but that's not part of the license, it's just something you might do).
- bonzini 10y agoNo, MIT and BSD allow proprietary derivatives of any kind, throwing away any expectations of reciprocity. MPL and LGPL draw a line between code that is allowed to be distributed under a proprietary license, and code where the copyleft applies.
- joshuamorton 10y ago>You emphasized anyone but by allowing developers to take the code proprietary, their users (which are using your code) are being denied the freedom you promote. This is of course the distinction between GPL and BSD-type licenses. One gives developers all the freedom they want while the other ensures that all users (including those using derivative works) are given those freedoms. Their users are not being denied the freedom to use my code, their users are being denied the freedom to use their code, which is their right. The cynic in me really thinks its important to wonder why there exists a GNU, and not an organization formed around and sustained by the MIT license.
- phkahler 10y ago>> Their users are not being denied the freedom to use my code, their users are being denied the freedom to use their code, which is their right. Unless they know it came from you and where to get it (which will not be advertised), they are. Also, after you die and your source code is gone, the derivative work could still go on to whatever success and none of the users of your code will have access to it except for that developer of the derivative work.
- joshuamorton 10y ago>Unless they know it came from you and where to get it (which will not be advertised), they are. And almost all licenses require attribution. >Also, after you die and your source code is gone, the derivative work could still go on to whatever success and none of the users of your code will have access to it except for that developer of the derivative work. This makes no sense. The source code of what I did will still be around, and still be attributed. Dying doesn't make my work disappear into the ether.
- phkahler 10y ago>> This makes no sense. The source code of what I did will still be around, and still be attributed. Dying doesn't make my work disappear into the ether. Yes it does, unless someone keeps it online or somehow available. But again, just because it technically exists somewhere doesn't mean a user of the derived work will know how to find it, nor what parts that work are actually covered by your code prior to finding it. You are starting to sound like someone deliberately not getting the point of this. I see a valid need for "permissive" licenses, but the legitimate reasons are rarely cited by proponents of the licenses.
- yellowapple 10y ago> their users (which are using your code) are being denied the freedom you promote. This is often asserted, but unless those proprietary software developers are somehow able to magically erase your own claim to copyright, the user is no less free when using your original version. My code is not denying anyone's freedom. Someone downstream might be denying their users' freedom, but those are their users, not mine. Downstream use of my code for evil purposes is outside of the scope of my own development. What is in scope, however, is the idea that a downstream developer should either contribute code back to me (whether privately or via license reciprocation) or not claim one's own product to be equivalent to my code. The Artistic License 2.0 does a decent job at that.