Well spotted; so it's even less of an issue than I imagined it could be. I hope everyone agrees that the SISL library can become a dependency pending testing on MSWin (and Mac if someone can help me out). I imagine this won't happen for quite a few months yet since I need to work on many other issues including a proposal for managing the various 3D models and the inevitable refactor. I would need to do all that work before I would even start on the IGES exporter code itself; for the time being the IGES library will stand on its own fully capable of a proof-of-concept work but with no link whatsoever to KiCad until the 3D plugin or whatever we call it is done.
- Cirilo On Fri, Mar 27, 2015 at 6:55 PM, Javier Serrano < javier.serrano.par...@gmail.com> wrote: > On Fri, Mar 27, 2015 at 12:20 AM, Cirilo Bernardo > <cirilo.berna...@gmail.com> wrote: > > My wording of the initial message must have been vague. AGPLv3 does not > > prohibit > > commercial use, but SINTEF as the copyright holder only allows AGPLv3 > use if > > the application is not a commercial cloud service. > > Sorry to be a PITA Cirilo, but this is still not correct. Look at one > example file, say [1]. It has a standard AGPL3 header. That means you > are fully free to do with it all the things people do with > AGPL-licensed files, including setting up a commercial cloud service. > Then, after the standard AGPL3 header, they write this: > > "Other Usage > You can be released from the requirements of the license by purchasing > a commercial license. Buying such a license is mandatory as soon as > you develop commercial activities involving the SISL library *without* > disclosing the source code of your own applications." > > Emphasis on "without" is mine. Also, the mentioning of commercial > activities is superfluous in their sentence. *Any* activity, > commercial or not, which breaches AGPL will need their permission. > > So people are completely free to set up a commercial cloud service > using KiCad with SISL in it. They just have to provide users with an > easy way to access all the sources of KiCad, including the SISL bits. > This is the behaviour we all want (I guess) anyway, so all is good. > > Cheers, > > Javier > > [1] https://github.com/SINTEF-Geometry/SISL/blob/master/src/construct.c >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp