4 ms·
More FUD. "If I inadvertently infringed, I might have peppered that GPL code throughout miles of my own code." Really? You "inadvertently" used miles of code
by SwellJoe 16y ago
More FUD.
"If I inadvertently infringed, I might have peppered that GPL code throughout miles of my own code."
Really? You "inadvertently" used miles of code copyrighted by other people without bothering to understand the license under which you obtained said code? That's a stretch. Even if you don't understand the GPL, as a developer with knowledge enough to locate the code you must understand that copyrighted code is probably made available to you under some terms that you must comply with.
Whether you buy a license to use the code, or received a license for free, you can't possibly be a computer programmer with zero notion of what "license" or "copyright" means.
"Just saying, the article seems to confirm that the FUD isn't FUD after all."
The FUD is that once you've introduced GPL code into your software, no matter how small a piece or for what reason, you could be forced to GPL all of your proprietary code. That's simply not true. If, on the other hand, you used so much GPL code that your product can't exist without it and you can't possibly rewrite the violating code, and you did so without putting forth any effort to understand or comply with the license under which you received the code, the best result I can think of would be for your company to go out of business.
- hughw 16y agoDon't address these rhetorical questions to me, using me as a straw man. I didn't assert people are spreading FUD about "inadvertent" infringement. The author did.The author uses "inadvertently" right in the first sentence, as the very premise of the article. So get out of my face with your lecturing. It's all there in the first sentence of the article. : his definition of "FUD" , the "inadvertent" infringing premise. My criticism is that the article fails as a self contained piece of reasoning. It convinces me the FUD spreaders could be right.
- jbri 16y agoYou don't "inadvertently" spread GPL'd code all throughout your codebase, unless you're one of those people who just copy-paste code from the internet everywhere.
- hughw 16y agoAnd your point is, people shouldn't do that? Well, you're not convincing me that the GPL doesn't spread virally and inadvertently then.
- jbri 16y agoIf all you've done is copy-paste stuff from the internet everywhere, then you haven't actually written any code. Regardless, that's not the point. Including GPL code doesn't magically obligate you to release the rest of your source code free to the world - you always have the option of, say, not distributing your program until you've removed and rewritten all the GPL-licensed stuff. I'm really not sure what you're getting at with your 'viral and inadvertent' comment - it almost seems like you're willfully ignoring the points being made in reply to your comments.
- hughw 16y agoThe responses all have the theme, "Inadvertent? Who would do that? Only irresponsible ninnies would do that." So they ignore the premise of the article, which presumes that inadvertent inclusion does happen. Additionally, I posted a few examples below where otherwise responsible contributors to a codebase might leak some GPLd material into the codebase. Over a long enough time, with enough developers contributing to your codebase, it's inevitable. "Not distributing your program", for a business, may mean a lot of money. It might mean bankruptcy. How do you know it will be affordable to replace the offending code? The author said "inadvertent", not "tiny". That's the viral part. GPL source code is all over the net. Any developer on your staff could look at something on line and derive some code from it, and drop it into your codebase. You'll never know about 99.9% of it.
- rbanffy 16y ago> Only irresponsible ninnies would do that Incompetent programmers do that too. > You'll never know about 99.9% of it. Too bad if it's your job knowing it.
- 16y ago
- SwellJoe 16y agoYou've picked apart the use of one word, "stolen", used seemingly in place of "inadvertent" earlier in the article. You haven't refuted the logical premise of the article in any meaningful way. This isn't a smoking gun refuting the point of the article. The fact is that inadvertent infringement, such as someone copy/pastes a few lines of code from GPLed code without awareness of its origin, does not impose a requirement on the entire work. It merely means you either rewrite the offending code (call it "stolen", "borrowed", "misplaced", "inadvertently copied", whatever you want), obtain the code under a different license from the original author (this is entirely plausible, and I've sold licenses in the past in this way on code I held the copyright to and licensed under the GPL), disable that feature, stop distributing the code entirely, or whatever you want to do. You simply are not forced to GPL your code, and it's FUD to suggest that a license would somehow force you to do so. I'm not saying the article is the best written or most coherent defense of the GPL ever, but its primary premise is correct. You can't "accidentally" GPL your codebase by incorporating a piece of GPL code.
- j_baker 16y agoThe article isn't a self-contained piece of reasoning. It's an analysis of society's reasoning. Any reasoning errors it contains don't change the law.