Licensing is the easy part
Posted Jul 30, 2007 17:50 UTC (Mon) by
jsarets (guest, #39560)
Parent article:
Microsoft trying to get code open-source certification (LinuxWorld)
It will be interesting to watch as the free software community begins to
do things Microsoft's code. Will Microsoft accept patches? Will they
care if we use the code in collaboration with Microsoft's rivals to
produce competing solutions? Will there be a lot of forking, and how
will they respond?
My amateur assessment of the "Shared Source" licenses suggests that OSI
and even FSF approval seems likely for Ms-PL and Ms-CL. The permissive
license is Apache-like. It doesn't require corresponding source, doesn't
allow relicensing, and provides patent grant and non-aggression clauses.
The community license is MPL-like. It's a weak copyleft (file-granular)
version of the permissive license.
Both of these come in limited versions: Ms-LPL and Ms-LCL, which limit
covered works to the Windows platform. There is also a reference license
(Ms-RL) that doesn't allow modification or redistribution outside of your
company. None of these appear to qualify as free and/or open-source
licenses.
Actually, I'm rather impressed by these two licenses. They're concise,
well-written, and they don't have any obvious trickery. Then again, if
you do anything that Microsoft doesn't like, you won't be dealing with
gpl-violations.org, but the most resourceful software law practice in the
world.
(
Log in to post comments)