Are 68 Open Source Licenses Enough? Or Too Many?
Feb 07, 2012, 12:04 (1 Talkback[s])
(Other stories by Robin 'Roblimo' Miller)
Full Text Search: The Key to Better Natural Language Queries for NoSQL in Node.js
[ Thanks to Lee
Schlesinger for this link. ]
"Why does the number of open source licenses matter?
Compatibility. If your company?s code is distributed under The
Apple Public Source License 2.0, is it compatible with code
distributed under The Ricoh Source Code Public License?
"What if you downloaded code distributed under the Ricoh
license, which includes this wording: ?The contents of this file
are subject to the Ricoh Source Code Public License Version 1.0
(the ?License?); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.risource.org/RPL.? That URL is dead and gone. So, it
seems, is the Ricoh license, although no license completely dies.
There are surely some code snippets still out there somewhere that
carry the Ricoh Source Code Public License Version 1.0, which means
it is possible that someone, somewhere, will need to test its
compatibility with, for example, the widely used Apache
- How Open Source Licenses Affect Your Business and Your Developers(Jan 26, 2012)
- Starting A FOSS Project? Then Know Your Licenses(Jun 01, 2011)
- Open Source Licenses: Greater Rights, Different Responsibilities(Apr 17, 2011)
- Are Mobile Apps Violating Open Source Licenses?(Mar 08, 2011)
- Telstra frees T-Hub open source code (finally complies with licenses)(Feb 22, 2011)
- A CIO's Quick Guide To Open Source Licenses(Aug 03, 2010)
- Proprietary Licenses Are Even Worse Than They Look(Apr 08, 2010)
- Understanding licenses, bit by bit (2)(Dec 18, 2009)