Survey Says GPLv3 Is Shunned 382
willdavid writes in to note a survey of open source developers conducted by Evans Data that indicates a real rift in the community over GPLv3. The survey was based on in-depth interviews with 380 open source developers and no estimated margin of error was given. "Just 6 percent of developers working with open-source software have adopted the new GNU General Public License version 3... Also, two-thirds say they will not adopt GPLv3 anytime in the next year, and 43 percent say they will never implement the new license. Almost twice as many would be less likely to join a project that uses GPLv3 than would be likely to join... [Evans Data's CEO said] 'Developers are confused and divided about [the restrictions GPLv3 imposes], with fairly equal numbers agreeing with the restrictions, disagreeing with them, or thinking they will be unenforceable.'"
Maybe I want my code to be used Commercially! (Score:1, Interesting)
Re:Slow adoption is to be expected (Score:3, Interesting)
Is there a clause in the GPLv3 that makes the "or later" mandatory? If that's the case, might as well sign it all over to the FSF or better yet just put "This software is released in whatever manner RMS decides at any time now or in the future".
Still, I wonder about the legality of enforcing a license that doesn't exist or didn't exist when you first got the source. "This software is released under a future license which we will let you know about when we get around to it" doesn't sound very legal.
Re:Confused... M$? (or not) (Score:4, Interesting)
http://www.evansdata.com/company/clients.php [evansdata.com]
Re:Not quite (Score:3, Interesting)
The basic issue has to do with whether or not the BSD code can be "relicensed" (in RMS and Eben Moglen's words) as GPL code without making any changes. While it is clear that copyright-worthy changes can be under any license, the question is whether the original code licensed under the BSD license can be. IMHO (IANAL) this talk of "relicensing" seems like legal mumbo-jumbo devoid of any accepted meaning.
The problem is that the GPL 3 is only compatible with licenses which allow this "relicensing" *independant of* other copyrights being enforced. This is clear in the Rationale documents, and in the opinions of both RMS and Mr Moglen. In other words, it requires that I can extend the requirements of the GPL3 to any and all parts of the code and any dependencies not specifically excluded from the Corresponding Source requirements without enforcing any of my own copyrights in the process.
I think that the BSDL always follows copyrighted elements released under that license and cannot be removed because this would require removing the permission grant from the code. Hence the additional permissions cannot meaningfully be removed without adding substantive code to the file. Because the GPL 3 requires that this is possible by merely conveying the software, it seems to me that this is a big problem. The authors of many of our dependencies agree and out of respect for them, I won't support moving the license.
Re:Slow adoption is to be expected (Score:3, Interesting)