GPL, Copyleft On the Rise
paxcoder writes "Contrary to earlier analyses that predicted a decline of copyleft software share to as little as 50% this year, John Sullivan, the executive director of the Free Software Foundation, claims the opposite has happened: In his talk at FOSDEM 2012 titled 'Is Copyleft Being Framed?,' Sullivan presented evidence (PDF) of a consistent increase of usage of copyleft licenses in relation to the usage of permissive licenses in free software projects over the past few years. Using publicly available package information provided by the Debian project, his study showed that the number of packages using the GPL family in that distribution this year reached a share of 93% of all packages with (L)GPLv3 usage rising 400% between the last two Debian versions."
IMO, if you're writing or releasing software, the GPL is preferrable. You benefit from patches, even being able to take those people don't intentionally contribute. You keep your code unusuable to those competitors who follow a closed management model. You also get to use it as advertisement if you're willing to offer an alternate license for money.
If you're looking to use somebody else's software though, of course the BSD is best. But the thing is that once you spent a few months working on code, a BSD license can be a bit of a hard sell for anything important, because you have nothing of the above. I think for most people some degree of attachment and desire of control develops after spending a lot of time on something.
I've seen so many developers just slap the GPL on their code because it's perceived as the "default" choice. When asked why they chose to use the GPL, they can't even explain its basic provisions. When told how it works, many of those same developers will say "oh, that's not really my intent." Sadly, because of the original "default" perception, a ton of code gets licensed this way.
I aggressively support the right to license something any way creators see fit, and happen to license my most of my stuff under the BSD and Artistic licenses. That said, people really need to understand what different licenses provide before they run off using them. When in any doubt whatsoever regarding any of it, it wouldn't be a terrible idea to pay for an hour of a lawyer's time (if possible).
Write failed: Broken pipe
And doesn't Debian actually actively work for make sure the packages it distributes are GPL?
So, not only is he cherrypicking but he picked a project that strives to use Copyleft.
http://www.debian.org/News/2012/20120219
The actual study mentioned in the talk came out last month and was written up here.
http://www.itwire.com/business-it-news/open-source/52838-gpl-use-in-debian-on-the-rise-study
John Sullivan even called picking only one distribution as "scientific". I'm not sure he knows what the word means.
Who would have thought?
Your point was funny and well illustrated, but I'm not sure it's correct. Is Debian actually biased toward the GPL over other F/OSS licenses? Their Debian Free Software Guidelines and Software License FAQ explicitly suggests the BSD and MIT licenses for authors who want their code to be useable by everyone. They also call out the Artistic License by name in the "What Does Free Mean?" section of the "Introduction to Debian".
I've never thought of Debian as particularly pro-GPL in particular so much as pro-Free Software in general.
Dewey, what part of this looks like authorities should be involved?