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?"

Comments

All depends on what you want.

[jon787]

The purpose of the GPL is to ensure that the code will always be open.

The purpose of the BSD license is to ensure the authors are given proper credit, not necessarily to keep the code open.

BTW

[AKAImBatman]

Furthermore, software containing embedded GPL-based code must be licensed under the GPL.

This is incorrect. The GPL does not require that derivitive works be GPLed. The key is that the restrictions placed on derivitive works (you must give up the source code and exclusive rights to redistribution) makes the resulting code effectively like the GPL. You can still use some other license for the derivitive code, and once you stop redistributing you can stop giving out the source code. Plus, nothing prevents you (as the copyright holder) from reusing the source that is yours in a non-GPL-derived product.

Clear as mud? Good.

Re:BTW

[ccady]

Unless I've misunderstood you, you've got the facts wrong yourself. You claim: The GPL does not require that derivitive works be GPLed. and You can still use some other license for the derivitive code

If you distribute your derivative work, b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. [section 2b of the GPL]

My experiences of an open source project release

[alanw]

Around Y2K, I worked for a company called Cyrano.com. It produced testing
software. We had done very well in the run-up to Y2K - lots of people wanted
to perform regression testing on their database applications. We were a small
company - much smaller than e.g. Rational.com (Now borged by IBM), but felt
that we had a good product. The management decided that the best way to help convince
customers to buy our product, in the face of arguments that Cyrano might not
be around in a couple of years time, was to open source the code. In these
circumstances, the obvious license to choose is the GPL: it ensures that
the company benefits from any changes anyone else makes.

I spent a very long time going through the files, adding the appropriate
header comments, and removing any comments naming individuals, especially
individuals who were no longer with the company, before setting up the
project at SourceForge: http://opensta.sourceforge.net/. There were
also OpenSTA.com and .org domains set up. The project is still running, and
I believe that several ex-employees, made redundant after the company went
tits-up, are now self-employed and using the application.

At the very least, open-sourcing the project meant that the codebase was not
lost when the company folded.

Re:Danger Will Robinson, Danger!

[toadlife]

First of all, is the author of ODE complaining about this? If not, then why would you bring it up as a "problem"?

Second of all, Microsoft *bought* a TCP stack from a Spider software when they were writing Win2k. Ironically, that TCP stack was taken from BSD - so you can be mad a spider software for 'stealing' the BSD tcp stack and laugh at Microsoft for paying for it.

Re:GPL helps programmers get paid

[unapersson]

"I would say that this is a great *problem* of the GPL. It's very easy in an open project to get spread, diluted copyright ownership. With the GPL, relicensing to a commercial customer can become impossible."

That really depends on whether or not you just accept random patches, or if you're planning to license the code commercially, whether you require copyright assignment to you before applying those patches.

Re:Danger Will Robinson, Danger!

[Tony Hoyle]

LGPL is a nice middle ground if you want people to actually use your software... they can add their own value and make money, but changes to your library must be published.

GPL is extremely hard to use as part of a commercial project, as it forces GPL on everything that links to it. That's fine if that's what the author wanted to achieve.. I do remember in my earlier years as a programmer GPLing everything without thinking though and it wouldn't surprise me if that still happened.

Re:Danger Will Robinson, Danger!

[rm69990]

The FSF (the people who wrote the GPL) don't agree with you on that matter.

How do you think Google gets away with modifying their software and deploying it on servers world-wide?

Some quotes from www.gnu.org from the GPL FAQ

Is making and using multiple copies within one organization or company "distribution"?

No, in that case the organization is just making the copies for itself. As a consequence, a company or other organization can develop a modified version and install that version through its own facilities, without giving the staff permission to release that modified version to outsiders.

Note : Notice the use of the word facilities, not facility.

However, when the organization transfers copies to other organizations or individuals, that is distribution. In particular, providing copies to contractors for use off-site is distribution.

If someone steals a CD containing a version of a GPL-covered program, does the GPL give him the right to redistribute that version?

If the version has been released elsewhere, then the thief probably does have the right to make copies and redistribute them under the GPL, but if he is imprisoned for stealing the CD he may have to wait until his release before doing so.

If the version in question is unpublished and considered by a company to be its trade secret, then publishing it may be a violation of trade secret law, depending on other circumstances. The GPL does not change that. If the company tried to release its version and still treat it as a trade secret, that would violate the GPL, but if the company hasn't released this version, no such violation has occurred.

I'm sorry, but I'm going to have to trust the FSF and the hundreds of other people who say what I say, as opposed to the handful who disagree, none of which have anything to do with the FSF

Re:Danger Will Robinson, Danger!

[alc6379]

If you look at the site itself (emphasis added):

The Benefits of an Open Source Physics Engine

* ODE's BSD license allows you to use the source code free of charge in your commercial products.
* ODE gives you more control over your product.
* ODE can be more easily integrated with your own software and tools.
* If you want to create your own physics engine, you can use the pieces of ODE as a reference!

It would appear to me that they're not too hurt people are doing this. In fact, the choice of the BSD license in this case seems pretty well thought out, in line with that one aim of using the software however you so choose.