OSI To Crack Down On "Open Source" Abusers
munchola sends us word that the Open Source Initiative is getting tough on any vendors who claim to be open source despite not actually using a license approved by the OSI. In his blog post, OSI president Michael Tiemann writes: "Enough is enough. Open Source has grown up. Now it is time for us to stand up. I believe that when we do, the vendors who ignore our norms will suddenly recognize that they really do need to make a choice: to label their software correctly and honestly, or to license it with an OSI-approved license that matches their open source label."
Open source is about exposing your code to the general public. This enables third-party developers to more easily analyze and make use of your software. It enhances the academic community's ability to experiment with, research, and just generally make "fair use" of software.
Free software is about exposing the intellectual property contained within the code - the copyrights and patents attached to the code. It enhances the public's access to software, and hence their ability to take full advantage of their computers. More importantly, it prevents waste. For example, can you imagine the extra cost to the economy if every developer had to implement public key cryptography from the ground up?
Free software implies open source; open source does not imply free software. Please, let's not confuse the two. It would be wonderful (and arguably sensible) if Microsoft made its code open source. It would be absurd for Microsoft to release its copyright of said code.
We need some standards. Letting companies attach any meaning they please to a common term makes the term useless.
open source = you can see the source
Except that isn't alone the definition - as I understand it, this was a term introduced by the OSI, and not one which preexisted.
Whether they have a legal right to enforce it depends on trademark law, but I don't think it's right for companies to use false or misleading advertising, by trying to pretend a term applies to their software, when it doesn't.
Bruce
Bruce Perens.
Read the current registration for Open Source. It has no relation to software, so I do not think an existing registration in this case should have any bearing. Trademarks are such a convoluted device that the USPTO requires all Trademark examiners to be lawyers.
You are correct. The current registration would not interfere with a registration for a certification mark for software licensing.
Bruce Perens.
Thank you, Bruce. Like many here, I was trying to figure out what Tiemann found so objectionable about SugarCRM's license. Being based on the Mozilla Public License, it looks very much like a lot of open-source licenses out there. It took a while to spot the "badgeware" clause hiding down at the very bottom:
However, in addition to the other notice obligations, all copies of the Covered Code in Executable and Source Code form distributed must, as a form of attribution of the original author, include on each user interface screen (i) the "Powered by SugarCRM" logo and (ii) the copyright notice in the same form as the latest version of the Covered Code distributed by SugarCRM, Inc. at the time of distribution of such copy. In addition, the "Powered by SugarCRM" logo must be visible to all users and be located at the very bottom center of each user interface screen. Notwithstanding the above, the dimensions of the "Powered By SugarCRM" logo must be at least 106 x 23 pixels. When users click on the "Powered by SugarCRM" logo it must direct them back to http://www.sugarforge.org./ In addition, the copyright notice must remain visible to all users at all times at the bottom of the user interface screen. When users click on the copyright notice, it must direct them back to http://www.sugarcrm.com/And suddenly that's no longer open source, because "open" doesn't just mean you can see it. It means you can use it and modify it for any purpose you want, including making new software for distribution, without jumping through hoops. As a developer, that's always been my understanding. This is "available, but branding-encumbered" source.
Thanks
Bruce
Bruce Perens.
"Official" definition? I think that's the problem people are having with this: you (and your organization) aren't the "official" definers of phrases.
Bruce
Bruce Perens.
OSI Certified:a rk.php
http://opensource.berlios.de/docs/certification_m
The GPL doesn't restrict your use of the code -- just redistribution of it.