[GRASS-user] licensing question: calling GRASS GIS modules via the grass.script API in an MIT/Apache licensed script ?

[Nikos Alexandris]

Maybe useful to know, there is the European Intellectual Property
Helpdesk (www.iprhelpdesk.eu).  However *only* offered to beneficiaries
of EU-funded research projects and EU SMSes involved in transnational
partnership agreements (such as Horizon 2020 projects).

Nikos

* Moritz Lennert <mlennert at club.worldonline.be> [2019-08-14 08:18:07 +0200]:

>Ping.
>
>Anyone ?
>
>Or a pointer to whom I could ask ?
>
>Moritz
>
>On 7/05/19 10:42, Moritz Lennert wrote:
>>Hi,
>>
>>We work with a company on a project where we use GRASS GIS to calculate
>>accessibility indicators. The main output we provide is a Python script
>>which calls GRASS GIS modules via the grass.script API. The company is
>>willing to make this script free software, but would like to license it
>>with a permissive license such as MIT or Apache.
>>
>>I would think that calling GRASS GIS modules in a script does not
>>automatically imply the script has to be GPL, but what about the use of
>>the Python API ?
>>
>>I would think that this case falls in the grey area described at [1] and
>>have tendency to think that MIT/Apache license would be allowed.
>>
>>Does anyone have a more informed opinion ?
>>
>>Moritz
>>
>>
>>[1] https://www.gnu.org/licenses/gpl-faq.html#MereAggregation
>>
>
>
>_______________________________________________
>grass-user mailing list
>grass-user at lists.osgeo.org
>https://lists.osgeo.org/mailman/listinfo/grass-user

-- 
Nikos Alexandris | Remote Sensing & Geomatics
GPG Key Fingerprint 6F9D4506F3CA28380974D31A9053534B693C4FB3