Am 11.03.2013 um 16:54 schrieb John Morris: > I'm worried about the published license. As it stands, we won't > be able to get this code into the big distributions. > > The distros' lawyers look at the published license, as included in or > pointed to by the software. They won't consider a separate license > granted in a mailing list thread.
This looks like an important goal for the relicensing effort to me which I hadnt thought of initially. It hasnt been tried afaict, but it looks even more realistic when we achieve the universal binary build which should simplify distribution logistics substantially. >> P.S. We are bound by the warranty, anti-tivoization, patent, and other >> terms of the (L)GPLv3 if we use 0MQ. > > This essentially says that we're relicensing LCNC. The existing > GPLv2-only license says that linked libraries must be 'conveyed' under > GPLv2. GPLv2 doesn't mention these restrictions, and explicitly states > that no additional restrictions may be applied. Some LCNC contributor > could try to sue if the project released binaries. Of course I don't > see this happening in real life (and they'd have to show damages if it > really did happen, something else I don't see), but I can guarantee the > lawyers will point this out if LCNC is packaged for the big distros. Would this then be the 'lazy lawyer' requirement? - "licenses published with LinuxCNC must be compatible with all dependent packages 'prima facie', that is without studying further license arrangements not specifically spelled out in the published licenses per se" it would translate into something like this statement: "The license(s) applicable to the LinuxCNC code is/are here: <link(s)>" "The dependent package licenses are here: <links>" "According to compatibility matrix entries <links>, these are compatible." - Michael ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
