Linux Today: Linux News On Internet Time.
Search Linux Today
search.internet.com
Linux News Sections:  Blog -  Developer -  High Performance -  Infrastructure -  IT Management -  Security -  Storage -
Linux Today Blog
Linux Today Navigation
LT Home
Preferences
Contribute
Link to Us
Search
Linux Jobs

Marketplace Partners

internet.commerce
Be a Commerce Partner

The Linux Channel at internet.com
Linux Today
Enterprise Linux Today
Apache Today
JustLinux.com
Linux Planet
PHPBuilder
All Linux Devices
Technology Jobs

searchcats.jpg

February 2009
Sun Mon Tue Wed Thu Fri Sat
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28

Would Dostoevsky Use the GPL?

| | Comments (3)

To GPL or not to GPL: What Would Dostoevsky Do?

"Thou wouldst go into the world, and art going with empty hands, with some promise of freedom which men in their simplicity and their natural unruliness cannot even understand, which they fear and dread- for nothing has ever been more insupportable for a man and a human society than freedom."
- The Grand Inquisitioner, Book 5, Chapter 5, The Brothers Karamazov

In "The Brothers Karamazov", Dostoevsky wrestles with many grand themes, including the above passage about freedom. The context of the above quote was a tale told through the eyes of Ivan Karamazov about the dangers of freedom and how it can ultimately result in enslavement. Without getting bogged down in details, I think it's pretty fair to say that Dostoevsky had some misgivings about modern perceptions of freedom.

You may be wondering what in God's green earth this has to do with the GPL. Lately, a few folks have written about the wonders of permissive licenses and the death of the GPL and how developers will migrate towards BSD-like licenses because of fewer limitations associated with it. Just as Dostoevsky warned us about the ultimate outcome of total freedom--oppression and totalitarian hegemony--I too worry about the ultimate outcome of permissive licenses like the BSD license. If you are not familiar with the basic differences between the BSD and GPL licenses, I encourage you to read them:

read the GNU GPL license
read the BSD license

To over-simplify the differences: the GPL has more downstream restrictions on how derivative works may be distributed, the primary one being that derivative works must also be licensed under the GPL.

I get nervous whenever large software shops talk up the virtues of a license with fewer protections of developer and user rights. In the linked articles above, there is talk of permissive licenses being the path of least resistance, with the premise that it's "easier" to gravitate towards them. My question is--easier for whom? Easier for the developers or easier for the companies who wish to make use of it without those annoying obligations to the greater free software ecosystem? As is often mentioned by others smarter than me, a scenario where developers gravitate towards permissive licenses makes it easier for companies to avoid community reciprocity.

A free software ecosystem works best when there are some limitations on what can happen downstream from the developer. In the case of the GPL, there are downstream limits on distribution of derivative works, among other things. No, it's not a perfect license, as the arguments over distribution and software as a service bear out. Really, the GPL serves to keep an honest person (or company) honest and is the best means available today for maintaining a vibrant, free software ecosystem over the long-term--and I include commercial as well as non-commercial projects in the mix. You see, as Dostoevsky attempted to show, the best kind of freedom is one with long-term viability, and that requires some restrictions to maintain order. It is with this in mind that I must respectfully disagree with those who proclaim the libertarian roots of free software. Certainly, I can see some libertarian elements of the free software ecosystem espousing the BSD license, but the GPL cannot be considered libertarian. Quite the contrary, it's designed to carry forward a moral framework by which users, developers, and companies can abide. That it seems to work out for commercial and non-commercial entities alike is testament to the genius of one RMS.

Personally, I think this is the right way to do business--and make money, to boot. If you didn't see it, you should definitely read about Marten Mickos' keynote from OSBC on why MySQL uses the GPL. Protecting developer rights isn't just some nebulous hippie ideology--those same rights extend to commercial free software projects, too.

So would Dostoevsky use the GPL? I have not a doubt :) I have written in the past about the long-term trends towards lower software prices and freely distributed software, but there is no such trend towards the protection of rights. That only occurs through the vigilance of the greater free software community.


For more of John Mark, visit his blog, There Is No Open Source Community.


3 Comments

Ted Swart said:

Well ssid Mark. The BSD style license simply encourages and results in theft. There is no need to wonder why M$ speaks well of the BSD license.


DostoevskyFan said:

This is a bit off the topic, but Doestoevsky didn't actually endorse the views of The Grand Inquisitor, he wrote it to contrast against his ultimate conclusion that freedom is worth the risks it implies.


Jose_x said:

[][][]The GPL offers a stronger (more responsive) feedback mechanism for the community of coders to maintain a check on each other than does the BSD.
[][][]
If a BSD codebase is taken and exploited to the detriment of numerous members of the community (eg, by being added to products that control a market), what can the members do to place a check on this while continuing to develop with the BSD license? There isn't much.
[][][]
Consider the same scenario with GPL code. In that case, the only way to close off the code is by the owner of the copyright (probably the commercial company hosting the project) or someone that received liberal licensing from the owner. Whether the monopoly position threatens the copyright owner or not (and acts or not), the rest of the community is threatened and they can respond by forking. A well-supported community fork will surpass and diverge from the original codebase thus significantly limiting the ability for the monopolist to continue to get a free ride with the (new) superior code base.
[][][]
The GPL's power comes in because it gives the copyright owner extra power. If this power is abused, the solution is to get new copyright owners (through a fork) and thereby leaving the original troublemaker cut off from the growing development. Yesterday's hot features just aren't enough to carry the day against today's new features and improvements.
[][][]
It's because the GPL reserves rights that it can be used to combat rogue members of the community by cutting off their ability to close things off. When members behave, however, the community generally backs them, even if they produce closed products.
[][][]
GPL is carrot and is stick. It is carrot to those that behave. It is stick to those that abuse.
[][][]
The BSD is just carrot no matter who you are and how much you misbehave (talk about bad parenting .. and I'm not implying that a *real* stick is needed by human parents "to maintain discipline").



Leave a comment








All times are recorded in UTC.
Linux is a trademark of Linus Torvalds.
Powered by Linux, Apache and PHP

internet.comearthweb.comDevx.commediabistro.comGraphics.com

Search:

Jupitermedia Corporation has two divisions: Jupiterimages and JupiterOnlineMedia

Jupitermedia Corporate Info

Legal Notices, Licensing, Reprints, Permissions, Privacy Policy.
Advertise | Newsletters | Tech Jobs | Shopping | E-mail Offers