It seems this sort of legal arrangement (open source + copyright assignment with rights to use proprietary licenses) is called "open core", which might warrant another article. Some links:
- —Darxus (talk) 23:25, 31 December 2010 (UTC)
- I think vendor lock-in is relevant. —Darxus (talk) 01:06, 3 January 2011 (UTC)
(Perhaps the first definition of open core) 'In this way, it is clear to customers that there is a "core" open source product that is GPL, and there is also additional high-value available as add-on features for purchase. So who is using "open-core licensing" successfully? Well, Sugar, Jaspersoft, Zimbra, and Talend to name a few of the rapidly growing list. Even MySQL may already be in that category' - http://alampitt.typepad.com/lampitt_or_leave_it/2008/08/open-core-licen.html —Darxus (talk) 01:26, 3 January 2011 (UTC)
I think one of the interesting things about open core is comparing it to GPL vs. BSD licensing. BSD means anybody can do anything they want with your code, including modifying it and releasing it as a commercial product (like MacOS X did with much of FreeBSD / NetBSD, and I remember noticing that OS/2 copied their TCP/IP stack from the BSDs). So people who like others to have the option to modify and sell their code release it under a BSD (like) license. People who don't, use the GPL, which basically means anybody can do anything they want with your code except modify it and sell it (without releasing the modified source also under the GPL). So an open core situation is similar to BSD, except only one entity, the one you assign copyright to, is capable of modifying and selling your code as a commercial product. So nothing nefarious, just a question of whether you want, for example, Canonical to be able to say "Thanks for helping to develop Uncomplicated Firewall, but if you want the Enterprise version you're going to need to pay us." —Darxus (talk) 01:39, 3 January 2011 (UTC)
- That IS an interesting comparison. Let's complete it: For one thing, "Open core" pretty much tells developers, "Don't contribute to this project if you're not willing to re-assign your copyright." The product I'm most familiar with as open-core is MindTouch, and they are absolutely not encouraging any kind of developer community - it's all in-house. For another thing, I may re-assign my copyright on my contributions, perhaps woo'ed by promises to "use them right", but who's to say the new assignee won't change their mind later about how they want to use (eg., distribute and license) the code? --188.8.131.52 (talk) 02:05, 19 May 2011 (UTC)
Why is FSFE's FLA mentioned??
There's a strange section titled "Non open core copyright assignment" - why is it there?
If the point is just to show that such things exist, a sentence would suffice. The details of the FLA aren't pertinent to an encyclopedia article about something which is isn't. Gronky (talk) 16:47, 17 May 2011 (UTC)
Why is Canonical’s contributor agreement mentioned?
I work for Canonical, so I won’t edit the article myself. But as far as I know, Canonical does not offer anything as open core, and has never suggested that it would. Bradley Kuhn accused Canonical of that, then realized he was mistaken. At most, you could say that Canonical’s contributor agreement doesn’t prevent open core, but that doesn’t justify it as an “example”.