kicad-developers team mailing list archive

[Martijn Kuipers <martijn.kuipers@xxxxxxxxx>]

Viva Miguel,

We should be fine, from https://www.gnu.org/licenses/gpl-faq.html#v3Notwithstanding: <https://www.gnu.org/licenses/gpl-faq.html#v3Notwithstanding:>

In AGPLv3, what counts as “interacting with [the software] remotely through a computer network?”

     If the program is expressly designed to accept user requests and send responses over a network, then it meets these criteria. Common examples of programs that would fall into this category include web and mail servers, interactive web-based applications, and servers for games that are played online.

    If a program is not expressly designed to interact with a user through a network, but is being run in an environment where it happens to do so, then it does not fall into this category. For example, an application is not required to provide source merely because the user is running it over SSH, or a remote X session.


BTW, I think it was an extremely generous parting gift from Dick Hollenbeck to allow the project-lead (or Jean Pierre) to relicense the code he provided under GPLv3.

Regards,
Martijn



> On 26 Mar 2015, at 09:48, Miguel Ángel Ajo <majopela@xxxxxxxxxx> wrote:
> 
> Not being able to use it for cloud services because of AGPL3+ (I haven’t looked
> at the license, I say it per your comments, cirilo) means that people could not 
> use Kicad scripting for automating the processing for manufacturing of Kicad files 
> (as an example) without publishing their scripts (I guess).  And that’s not necessarily
> a good thing.
> 
> 
> 
> Miguel Ángel Ajo
> 
> On Thursday, 26 de March de 2015 at 9:17, Javier Serrano wrote:
> 
>> On Thu, Mar 26, 2015 at 4:36 AM, Cirilo Bernardo
>> <cirilo.bernardo@xxxxxxxxx <mailto:cirilo.bernardo@xxxxxxxxx>> wrote:
>> [ snip ]
>>> The only really tricky part comes from the 'v3' bit - according to the FSF
>>> the AGPLv3 is not compatible with GPL2, and not even compatible with
>>> GPLv3 but OK to mix with GPLv3 (whatever that means - I can already
>>> hear some lawyers laughing).
>> 
>> [ IANAL, please take the following as the opinion of a non-expert. ]
>> 
>> This is why the '+' (i.e. the "or-later") in "GPL2+" is really
>> important. The KiCad sources are, to the best of my knowledge, GPL2+
>> (most) and GPL3+ (the P&S router). That means that the mix is
>> effectively GPL3+. SISL seems to be AGPL3+. I see no incompatibility
>> (see section 13 of both licenses), but mixing in AGPL3+ code is a step
>> in the "stronger copyleft" direction. This is a strategic decision to
>> be taken, IMHO by the project leader.
>> 
>>> Any thoughts on eventually having SISL as a dependency? What's the
>>> current status of licensing of KiCad source modules? I can remove
>>> the SISL dependency but this will cripple the IGES code by removing
>>> the ability to check the validity of some structures within an input file.
>> 
>> There is still the misleading COPYRIGHT.txt in the root of the KiCad
>> sources, which I think should just be removed. This is important, and
>> I hope it can be done before the stable release.
>> 
>> Cheers,
>> 
>> Javier
>> 
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
>> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>> Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
>> More help : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp