Matt, Am 08.03.2013 um 04:06 schrieb Matt Shaver:
> On Fri, 8 Mar 2013 00:18:07 +0100 > Michael Haberler <mai...@mah.priv.at> wrote: > >> An extremely valuable non-technical contribution to this whole effort >> would be to tackle the licensing issue with an angle to results in a >> realistic timeframe, and I would really appreciate if somebody else >> could take the lead on this, and actually deliver. This can be done >> in parallel, that is - now. > > I need you to be more specific about exactly what you would like to > change about the current licensing. Here's what I think that you think > the problem is: > > 1. You want to use 0MQ, and that is licensed under the LGPLv3. > > 2. Some parts of EMC/linuxcnc have notices in the code that say, > "License: LGPL Version 2", without the "or later" post script. > > 3. According to this: > http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility > using a library from a GPLv3 project like 0MQ is not permissible for a > presumably "GPLv2 only" project like linuxcnc. > > 4. According to this page: > http://www.zeromq.org/area:licensing > they say: > *************************************************************** > Static linking exception. The copyright holders give you permission > to link this library with independent modules to produce an executable, > regardless of the license terms of these independent modules, and to > copy and distribute the resulting executable under terms of your > choice, provided that you also meet, for each linked independent > module, the terms and conditions of the license of that module. An > independent module is a module which is not derived from or based on > this library. If you modify this library, you must extend this > exception to your version of the library. > > ØMQ for Commercial Applications > > ØMQ is safe for use in close-source applications. The LGPL > share-alike terms do not apply to applications built on top of ØMQ. > > You do not need a commercial license. The LGPL applies to ØMQ's own > source code, not your applications. Many commercial applications > use ØMQ. > *************************************************************** This description is spot on. > If this is the problem, let's figure out which are the actual > "roadblock" files. If this is not the problem, or if there are other > licensing issues, please let me know. yes, that is what needs to be done. > > Thanks, > Matt the only remarks I have: 1) affects not just me, and not just the ZeroMQ package. Folks are routinely bitten by it, and several packages which would be attractive for use with LinuxCNC are off limits, for instance the excellent Kivy touch screen UI project, or the RPCz layer ontop of ZeroMQ. Those can be worked without; the story on equivalent replacements for ZeroMQ is short and lacking a wide range of language bindings in particular. And I simply do not have the time and energy to work around by re-coding such completely generic tools just because of the licensing status of LinuxCNC. Other examples are libmodbus and OpenSCAM; in these cases I could work around the issue by convince the authors to relicense _their_ package. This does not scale - it only works for rather small projects, and those are not the ones which are a huge boost in such an effort. 2) Given JMK's expressed willingness to relicense along these lines and fact that the list of folks who contributed to RTAPI/HAL is rather short, this seems to be the easy part. Since e.g. task and motion must tie into the middleware by linking to ZeroMQ, and both are GPL2only, it is one of the hot spots. Same goes for UI components which will need to tie in. This is a bit ironic given the fact that task hasnt changed all that much since it came out of NIST with a public domain status. I would be very grateful if that work item were picked up. I am happy to help, and I know others will too. 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 Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
