Re: Scapy licensing issue in FD.io projects [Was: TRex distribution and licensing of external libraries]
Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco)
Adding some technical details with quick links.
Scapy license  is GLP, not LGPL.
In python, using "import" statement amounts to linking,
which creates  a combined program, instead of
a mere aggregation of different programs.
FD.io projects apply Apache 2.0 license,
TRex , VPP  and CSIT .
The scapy code is imported, and the internal data structures
are used by TRex , VPP  and CSIT python code
(source code is in C), and the packaged Python code
is not related to scapy as far as I know.
which run the code containing (modified) scapy parts
and original VPP python parts linked together,
From: Maciek Konstantynowicz (mkonstan) <mkonstan@...>
Sent: Thursday, October 10, 2019 5:47 PM
To: tsc@...; Ed Warnicke (eaw) <eaw@...>; Kinsella, Ray <ray.kinsella@...>
Cc: Miroslav Los -X (mirlos - PANTHEON TECHNOLOGIES at Cisco) <mirlos@...>; Hanoch Haim (hhaim) <hhaim@...>; Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) <vrpolak@...>
Subject: Re: Scapy licensing issue in FD.io projects [Was: TRex distribution and licensing of external libraries]
Resending from Cisco email account as it’s back and cleared for sending emails to tsc mailer.
Adding Miroslav, Hanoh and Vratko who has been also involved here (Miroslav brought up the issue).
Per our discussion on FD.io TSC call few mins ago, pls advise on the next steps.
Specifically, how to articulate this case in a crisp and succinct manner for LF(N) legal advisor?