If I think about an example, let's say someone who works as a programmer at a for-profit open source company, say Groundwork Open Source, makes a contribution to the expressly non-commercial Open Source project Nagios that includes code that talks to Microsoft's stuff. As long as that piece of code is distributed in a non-commercial way, no problem. But if Groundwork decides to include that bit of functionality in their commercial solution (which may or may not be Open Source), then Groundwork needs to get a license (which Microsoft promises to provide in a non-discriminatory way and at a fair rate - and btw, I agree wholeheartedly with the skeptics here - proof will be in the pudding). I struggle to see what's unfair about this or how it differs substantially from the stance taken by commercial open source companies that have different license terms for different versions / uses of their product - companies like MySQL, and Alfresco. Alfresco's licensing page puts it this way:
Alfresco Software Ltd. provides its software (enterprise content management system, web content management system) under a number of flexible licenses, designed to meet the particular requirements of different types of users:
For Open Source Projects
-
If you are developing and distributing open source software under the GNU General Public License (“GPL”), then you are free to use Alfresco under the GPL License. More Info
- If you are developing and distributing open source software under an OSI-Approved License, but not the GPL, and want to link Alfresco’s GPL software with yours, Alfresco provides the GPL License with a FLOSS Exception. More Info
For Commercial OEMs, ISVs and VARs
For OEMs, ISVs, and VARs who distribute Alfresco with their proprietary products, and do not wish to license and distribute their source code under the GPL, Alfresco provides a flexible OEM Commercial License. For more details please see our OEM Program Information.
No comments:
Post a Comment