[riot-devel] openthread and riot - license issues?

MATTIA ANTONINI mattia.antonini1 at studenti.unipr.it
Mon Oct 24 09:43:30 CEST 2016

Hi all,
I have the same problem (I'm preparing the IoTivity Pkg) and I asked to
Emmanuel how can I solve it. He answered:

- any code destined (PRed) to be included in RIOT master should be LGPLv2.1
- any code that is not destined to go into RIOT master follows other
applicable license policy

The OpenThread RIOT Pkg is composed by Makefiles and some code released
under  LGPLv2.1 license. The OT code is downloaded during the compilation
phase. I guess there is not any license issue because the PRed code is
compliant with the RIOT license.

Have a nice day,


2016-10-22 22:49 GMT+02:00 Alexander Aring <aar at pengutronix.de>:

> Hi,
> On 10/22/2016 05:11 PM, Martine Lenders wrote:
> > Hi Alex,
> > we include openthread's source code as a package so as far as we are
> > concerned (but we are not lawyers) there is no licensing issue. If you
> know
> > anything different, please let us know!
> >
> I am also not a lawyer. I think I got confused because
> from [0]. But RIOT is not an "APACHE PRODUCT"... , :-)
> but then I still don't get something - there was a discussion about
> jerryscript in RIOT at riot-summit. Jerryscript is also apache license
> and the discussion was about license issues between jerryscript and RIOT.
> I don't see a difference here now. Maybe somebody knows more? :-/
> - Alex
> [0] http://www.apache.org/legal/resolved.html
> _______________________________________________
> devel mailing list
> devel at riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/devel/attachments/20161024/d2aa09f6/attachment.html>

More information about the devel mailing list