Re:GNU grep - A Cautionary Tale About GPLv3
by aidenn0 on Tuesday October 16, 2012 @07:38PM
(#4662480)
It can't happen. However, the plaintiff may offer to forgo monetary damages in exchange for you open-sourcing. So it becomes pay money, or open-source.
Re:GNU grep - A Cautionary Tale About GPLv3
by mikeash on Tuesday October 16, 2012 @07:37PM
(#4662477)
As far as I know, this can't happen. The author is being highly paranoid, presumably due to being misinformed.
Re:GNU grep - A Cautionary Tale About GPLv3
by saidajigumi on Tuesday October 16, 2012 @07:57PM
(#4662550)
Yeah. This company was about to distribute GNU grep, meaning that they would be obligated to provide source for that version of grep, and likewise for any modifications to grep they've made. Yawn.
Re:GNU grep - A Cautionary Tale About GPLv3
by rbanffy on Tuesday October 16, 2012 @10:59PM
(#4662992)
When a clever person is so completely misinformed about a subject that's the very core of their business, I would rather call it FUD.
And I'd also like to point out they aren't in the business of creating value, as an open source product offers more value than a black box: their want to create costs.
Re:GNU grep - A Cautionary Tale About GPLv3
by mikeash on Wednesday October 17, 2012 @09:53AM
(#4664385)
I think you're right about FUD, but it's probably not him. I imagine he fell victim to the FUD, rather than intentionally creating it.
Re:GNU grep - A Cautionary Tale About GPLv3
by rbanffy on Wednesday October 17, 2012 @11:26AM
(#4664843)
I always find it suspicious when someone clever falls victim of - and further spreads - FUD that is beneficial to his/her business. Remember they sell proprietary (actually, re-licensed) software that's not under one of those "dangerous" and "viral" licenses.
Re:GNU grep - A Cautionary Tale About GPLv3
by mikeash on Wednesday October 17, 2012 @12:01PM
(#4665028)
We're all biased towards ideas that suit us. If the FUD is beneficial to his business then he's likely to be highly receptive to it.
> A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. (GPLv3)
Using GNU grep, as GNU grep, and merely aggregating it with the whole, would seem, from the quote above, to not cause the whole to be GPLv3 covered.
The only slightly questionable part is the "combined with it such as to form a larger program" portion of GPLv3. Is using grep, to "grep", sufficient to say that grep is "combined ... to form a larger program"? If the answer is no, then yes, the author is simply misinformed.
Someone assist in my enlightenment: Under what sort of enforcement circumstances would that requirement to open-source a lot of code actually be likely? As opposed to some enforcement action where you remove the offending code.