Newsletters Select newsletters below and click the button to sign up!
Internetnews BloggersRecent Entries
ArchivesMonthly ArchivesSearch The Blog
« Irreconcilable conflict between $ and Open Source ?! |
Sean Michael Kerner Blog
| EnterpriseDB nabs former Red Hat exec as CEO »
CPAL is not an Open Source poison pill for Facebook From the 'holier than thou' files:A pair of my colleagues forwarded me a pitch today titled, " Disappointing: Facebook Does Open Source like Microsoft." It's an 'interesting' email pitch -- it's a pity I wasn't contacted directly. Essentially what the pitch (which came from Bob Bickel "The poison pill in this license agreement is that anyone using the Facebook code as part of something else, and puts that up on a website, would need to make all of the code open source," Bickel wrote in his email pitch.First off the CPAL is a bona fide Open Source license approved by the OSI. It fulfills the requirements of the Open Source Definition as determined by the OSI and it is the Real Deal. The ideal of contributions is pivotal to the success and long term survival of the Open Source community, and that shouldn't be thought of as a poison pill in my view. That said not everything that Open Source touches should in turn become Open Source itself. The risk of infection from GPL licensed code (and the GPL is significantly more reciprocal in nature than the CPAL) is significantly higher. I'm not a lawyer - and I don't pretend to be one - but just because I use Linux doesn't mean that anything I use Linux with (and the Linux kernel itself is GPL) automatically becomes Open Source -- It just doesn't work that way. Yes the LGPL (Lesser GPL) that companies like Ringside use has additional protections and it doesn't necessarily require attribution (which is the issue that some have trouble with). The CPAL attribution basically means that users need to attribute where the code came from (I've heard this referred to as 'badgeware' sometimes). The holier than thou - My License is More Open Than Your License - debate is one that doesn't serve Open Source in my opinion, it's one that only serves to fuel the commercial closed source vendor FUD fire. (Though I do think there is a need and a use case for both reciprocal and BSD-type licenses as well as CPAL -- where usage depends on circumstances and one size does not fit all). Frankly and practically, I think it's a marvelous thing that the Facebook Platform is under a real Open Source license - arguing about the semantics of reciprocity and attribution - diminish the fact that it is an open platform that anyone (without the need for special agreements or licenses) can use/extend and deploy. That's the promise of Open Source and it's one that Facebook is now embracing. 0 TrackBacksListed below are links to blogs that reference this entry: CPAL is not an Open Source poison pill for Facebook. TrackBack URL for this entry: https://swarm.jupitermedia.com/mt-tb.cgi/3650 2 CommentsLeave a comment |
||
Sean - you are right on. I made a mistake based on info from another blog. As you can see from my blog post, I retracted and clarified after talking with Ami Vora of Facebook. - http://bobbickel.blogspot.com/
Thanks,
Bob
I don't think the majority of the criticism is that the license is somehow not "open source" - that's obviously false, as you've demonstrated.
It's just that the badgeware clause discourages adoption. For example, in order for MySpace to implement the platform, they'd have to carry around a Facebook badge on their website.
(Facebook won't even let people mentioned other social networks on ads on their network!
http://www.techcrunch.com/2008/06/04/facebook-is-blocking-ads-from-myspace-friendster-hi5-orkut-and-3jam/
)
Doesn't that discourage other networks from actually adopting the platform? It seems counter-productive, if their actual intent is to free up the software.
I'm a big Facebook fan, but this is disappointing.