3 ms·
The more likely scenario is that you start an open source project. Put it under the BSD. Great. Two years later someone comes and says, remember dev X, Y, an
by kenjackson 16y ago
The more likely scenario is that you start an open source project. Put it under the BSD. Great. Two years later someone comes and says, remember dev X, Y, and Z. They were using some GPL code in your project. We've found at least 50 instances of it.
Now here's where it gets ugly, because everyone who picked up your project thinking it was a BSD project, just picked up a GPL project. They may be using your code in very intertwined, fully in compliance with the BSD license, but you must now inform them that the must comply with the GPL or cease using this code, or pay damages.
That doesn't seem like a great situation to be in.
Although it is ironically a good argument for the GPL... "sure the license may say MIT/BSD, but it might be GPL"
- SwellJoe 16y agoSo, now we get the to heart of it: You don't care about the clarity of the license, or the availability of clear information about what it means, or the fact that the FSF recommends every project that is under the GPL include a complete copy of the GPL in every distributed copy of the code so that it is not inadvertently used by someone that might not know the license. You only care that it's not the license you prefer. "The more likely scenario is that you start an open source project. Put it under the BSD. Great. Two years later someone comes and says, remember dev X, Y, and Z. They were using some GPL code in your project. We've found at least 50 instances of it." I've been an Open Source developer for more than a dozen years, on projects in use by millions of people, and under more than a dozen different licenses including BSD and GPL. Some of those projects span hundreds of thousands of lines of code and hundreds of contributors, in both purely commercial and purely non-profit organizations and everything in between. I've never once seen an incident of GPL code being accidentally used in a situation where it caused a license problem. I have seen people try to get away with not following the license, but that's not the same thing, and it was not a misunderstanding or inadvertent. In short: He (or she) who writes the code, determines the license. Deal with it. If you're using the code it's your responsibility to understand the terms under which it is made available to you. You can't make it the author's responsibility to choose a license that meets your desires. The author of the code presumably has their own desires, and they supercede yours.
- kenjackson 16y agoHe (or she) who writes the code, determines the license. I don't think anyone disagrees with this. I think some people feel that they're not comfortable with GPL code. It's odd because I've literally had devs at conferences yell at me because I've said, "nah, I'll pass, I don't use GPL". Just as the author of said code determines the license, I'm free to pick software that uses a license I prefer. I'm 100% fine with people using a GPL license. I'm just not fine for me using it in my code. And I think its fair to say that no one should be abused for using a license of their choosing, and likewise one shouldn't be abused because they don't use software/code that uses a specific license.
- skore 16y ago>>He (or she) who writes the code, determines the license. >I don't think anyone disagrees with this. You picked a minor point that was just a part of his train of thought to get to his real point? Really? >I think some people feel that they're not comfortable with GPL code. It's odd because I've literally had devs at conferences yell at me because I've said, "nah, I'll pass, I don't use GPL". Just as the author of said code determines the license, I'm free to pick software that uses a license I prefer. I'm 100% fine with people using a GPL license. I'm just not fine for me using it in my code. You are having an argument that nobody started (except yourself). >And I think its fair to say that no one should be abused for using a license of their choosing, and likewise one shouldn't be abused because they don't use software/code that uses a specific license. You are argueing against your own experiences - which are not the topic of this discussion, are not verifiable for us and don't add anything but saying "I didn't like this one time when somebody was rude to me". Actually, I have no idea what you're trying to say at all.
- kenjackson 16y agoYou literally dedicate half your post to this issue. Your first large paragraph is about me "prefering a license". Then you go on to give your OS qualifications. Then your conclusion is this point. Here's a hint. If it's a "minor point" don't open with it and then conclude with "In short:" -- and finish it off with the same point. Whatever.
- jasonlotito 16y agoI mentioned above, but I'll briefly mention it again: this problem is not limited to GPL. Proprietary code being distributed in a BSD app is just as likely. It's not an issue with licenses. The code might not even have a license, in which case it can't be distributed. > They were using some GPL code in your project. We've found at least 50 instances of it. You can replace GPL with any license out there, and it could apply. Heck, you can even violate BSD code by putting it into a GPL app and have the exact same problem.