Slashdot Mirror
Open-source Licensing: BSD or GPL?
BSDForums.org writes "Mark Brewer of Covalent Technologies argues BSD is better for the enterprise. As open source licensing models, both the Berkeley Software Distribution license and the General Public License have advantages and disadvantages. But in the end, the BSD offers more benefits to enterprise customers. Matt Asay of Novell makes the case for GPL. He says, no one open source license is ideal in every circumstance. Different licenses serve different ends. Berkeley Software Distribution-style licenses have been used to govern the development of exceptional open source projects such as Apache. Clearly, BSD has its strengths. However, all things being equal, he prefers the General Public License (GPL ). The GPL is one of the most exciting, innovative capitalist tools ever created. The GPL breaks down walls between vendors and customers while enabling strong competitive differentiation.
Which is a better licensing model for open-source applications: BSD or GPL? What do you think?"
The GPL license is perfect for developers.
The BSD license is perfect for everybody else.
Otherwise you're just doing free work for some software venture capitalist, which is stupid. I mean, if you want to help people, go spend time with sick children or something.
Apparently there are some mods who only read half of the comments.
So I suppose the Apache Foundation should just give up the work they've done? I suppose name-recognition for a popular BSD project isn't enough for you?
If anything, licensing under BSD instead of the GPL is the most selfless act a software developer can make. It means they are coding for the love of coding, not because of a political or philosophical agenda. Is there something wrong with that?
Likewise, is there something wrong with working for Habitat for Humanity, the Peace Corps, and The Hunger Project?
Your analysis is blindingly oversimplified. Most companies would rather GPL their own code than release it under a BSD license, but would rather have others release their code under a BSD license.
Which is one reason I am personally fond of the LGPL. It says, in essence, "MY code is Free and must stay that way. Do what you want with you parts." It also has the side-effect of encouraging good, modular, component-based design. That's a win-win for everyone. Why people keep forgetting the LGPL in these flamewars I don't know, as it is a perfectly reasonable compromise between the "do anything" BSD and the "hand of Midas" GPL. I am particularly fond of it for libraries, frameworks, APIs, etc.
That said, can we mod this entire story flamebait? I mean really, is the next Slashdot story going to be "Vi or Emacs, what does Slashdot think?"
--GrouchoMarx
Card-carrying member of the EFF, FSF, and ACLU. Are you?
Note that the author doesn't have the right to complain. People (companies?) are using the way he licenced it. The GP was giving an axample of why BSD style licences are bad for authors if they expect something (code) in return. Some company and other developpers might contribute back to BSD projects but that relies completely on their goodwill.
I've seen a bunch of projects that chose to go with the BSD style licence and it's bit them in the ass. People are using their code left and right, but hardly anyone is contributing back since they don't have to. [...] As long as there are human beings involved, there's going to be people taking advantage of you.
I don't get this. Surely he wanted everyone to use his code, without any further obligations? Since that's exactly the point of the license he used? How can you call that "biting him in the ass", or "taking advantage of"?
BSD is clearly too loose, if you don't want people to keep their changes for themselves. But well, duh, don't use that license then. Most people in the BSD projects are perfectly happy if there code is used somewhere, regardless of ever seeing anything back (or so I've heard - I'm a Linux weenie).
Anyway, in between GPL and BSD license, there's always the LGPL.
I believe posters are recognized by their sig. So I made one.