3 ms·
I think cheaper compliance means better compliance. A no-suit cure process is a win both for a company that inadvertently broke GPL provisions, and the bodies l
by nine_k 9y ago
I think cheaper compliance means better compliance. A no-suit cure process is a win both for a company that inadvertently broke GPL provisions, and the bodies like GNU who would point at it and require compliance. It also means that a small company can roll out a GPL-licensed solution with less fear of a non-compliance lawsuit.
Litigation is expensive; it makes sense against large and stubborn violators, but the proper process costs a lot for both sides.
Or maybe I'm missing something important here?
- jordigh 9y agoYes, I already agreed this is a good thing. Perhaps I wasn't clear, my apologies. It's good to be lenient, especially in cases of accidental non-compliance. This is an uncontroversial improvement of GPLv3 over GPLv2. I'm just bemoaning the larger context of copyleft non-adoption.
- ekidd 9y ago> I'm just bemoaning the larger context of copyleft non-adoption. I rarely bother to use copyleft for my personal open source work, because I'm not typically interested in hiring lawyers to try to enforce compliance. And if I wouldn't pay a lawyer to go after a violator, then I don't personally see much point in using anything more complicated than CC0 or a boring permissive license. Licensing adds overhead. If I use the GPL, then somebody has to stop and ask themselves, "Hey, can I use reuse 30 lines of this GPLed code in this MIT-licensed project? Do I need to change my project's license? Do I need to ask permission?" Usually I don't care. However, for certain projects, I am perfectly willing to enforce a copyleft license. In that case, I'm happy to use the GPL 3. It's a good license, and I'm very glad it exists. I don't feel like anybody else should feel obligated to take my approach. Part of my philosophy here comes from painful personal experience that successfully commercializing code requires years of sacrifice, and 99% of what I write in my free time will never be worth that effort.
- phkahler 9y ago>> Or maybe I'm missing something important here? Yeah, individual authors may not want someone else to specify how they enforce compliance. If a company wants to play nice that's fine, and I see Redhat and friends are agreeing to play nice with GPL2 code that they contribute to. FSF also has a history of playing nice - they prefer to get compliance rather than collect huge monetary awards. But that's my point, you don't have to encode being nice into the license itself. I found it rather off-putting when I first read it. It imposes restrictions on the original author of the code. Note that v2 imposed nothing on the original author.