[opnfv-tech-discuss] [vsperf] VSPERF weekly meeting - 24 June 2020 (ww137)

2020-06-23 Thread Sridhar K. N. Rao
Agenda: 1. Development Update 2. Updates from Interns - Issues. Time: Wednesday PT 8h00 [ GMT: 3PM, CET: 5PM, India Time 830PM] IRC: freenode https://freenode.net/ channel: #opnfv-vswitchperf; http://webchat.freenode.net/?channels=o

Re: [opnfv-tech-discuss] License Scans

2020-06-23 Thread Trevor Bramwell
Hey Mark, There is some form of license checking in Anteater[1] though I doubt anyone is looking closely at the reports, since we (Infra-WG/Anteater) could never get traction for people to address the issues. It appears that newer versions of Anteater no-longer do license scanning, and I'd guess t

Re: [opnfv-tech-discuss] License Scans

2020-06-23 Thread Mark Beierl
Thanks, Jack. From my vague memory, this was a separate exercise where all the pip, git clone, or other third party inclusions were scanned from their upstream source to ensure we were not pulling files in that would violate our license.  Does that sound familiar? Regards, Mark On 2020-06-2

Re: [opnfv-tech-discuss] License Scans

2020-06-23 Thread Jack Morgan
Mark On 6/23/20 10:13 AM, Mark Beierl wrote: > Hello, all. > > I remember we used to have license scans for new patches > (releng-anteater), but I also recall there were emails sent out about > the inclusion of third party libraries which may not have conformed to > OPNFV's licensing model.  Does

[opnfv-tech-discuss] License Scans

2020-06-23 Thread Mark Beierl
Hello, all. I remember we used to have license scans for new patches (releng-anteater), but I also recall there were emails sent out about the inclusion of third party libraries which may not have conformed to OPNFV's licensing model.  Does anyone remember how that was done?  The results were