OSI Hopes To Decrease Number of Licenses
Noksagt writes "Various outlets report that the OSI may cut down the increasing number of Open Source licenses. Right now there are about 50 approved licenses; incompatible licenses confuse and impede developers and end users alike. The OSDL has been pushing hard for this at LinuxWorld. Sam Greenblatt, a member of the OSDL board, said 'Eventually there should be three licenses: The GPL, a commercial version of the GPL, and, of course, there will be the BSD because you can't rid of it.'"
What about LGPL and CreativeCommons licenses? Libraries and artwork (books, websites, etc) still ought to have their open-source licenses available...
My Systems
I think they're going to run into the same problem that DRM manufacturers have: there's no benefit to the people who are untimately in charge.
In this case, it isn't the 'paying customers', it's the developing free software engineers. The proliferation of licenses comes directly from the fact that developers have found some aspect of the GPL or LGPL to be too onerous to release under. And there is no way you're going to get them to alter their license just because Stallman thinks they should.
So here's a different idea. Instead of trying to reduce the number of Open Source licenses, people should instead come up with a comparison chart. Much like the Unix rosetta stone except for legalese, identifying general contract features in common (or different) between them.
That way developers can see the difference in a single place, and pick the best license for their particular purpose.
I don't know if you comment is a troll or not.
It's fairly well established that some people believe something is more free if it has a license that restricts users ability to make versions of the software non-free whilst some people believe that software is more free if you have the right to make non-free versions.
I think regardless of how you define "free" both the BSD and GPL style licenses have different purposes.
When you say that if something was 100% free it wouldn't need a license that might be true if the world had no laws or commercial interests. That extra waft in the GPL that makes it longer than the BSD license is to make it clear that the software can't be moved from the category of "free" software to the category of "non-free" software by commercial interests.
Imagine another world (as Stallman problably does) where the law by default rather than supporting commercial interests supported freedom of software. In this world the GPL would be short and the BSD license long because the BSD license would need to explain that future versions of the software could be taken by private companies and changes withheld unlike "normal software" where future versions of the free software must remain free by default.
Matt.
Sam Greenblatt, a member of the OSDL board, was quoted as saying something very unclear: "Eventually there should be three licenses: The GPL, a commercial version of the GPL...". The GNU General Public License (GPL) allows one to distribute copies of covered works for a fee. Many people have turned GCC (the GNU Compiler Collection), one noteworthy GPL-covered program, into a commercial work by distributing copies of it for a fee, some have also based for-hire consulting services on GCC. These consultants develop GCC as a business activity.
Most of the time when people say "commercial" in this context, they don't mean that. That word was just a poor choice which may stem from not fully understanding what software freedom entails. What they really meant to say was "proprietary", which is something different. In this case, I don't know what that other meaning would be; a proprietary GPL would not be the GPL, it would be a perverse opposite of what the GPL stands for and accomplished long before the open source movement existed. Thus I'm left thinking Greenblatt's statement is at best unclear, non-sensical at worst.
Digital Citizen
BSD and GPL have a *very* different spirit. The first one is strongly academic (making the source available with no strings attached, just requiring the user to give credits where they're due), the latter is strongly political (anti-proprietary, and openly communistic since it aims to abolish private property as far as software is concerned).
I don't know about Sam Greenblatt, but the fact that you can't get rid of BSD makes most professional developers very happy.
--
Requiem for the FUD