Re: [opnfv-tech-discuss] [infra] License checks in CI

2017-04-25 Thread Bryan Sullivan
fv-tech-discuss-boun...@lists.opnfv.org on behalf of Raymond Paik Sent: Friday, April 21, 2017 1:53 PM To: Luke Hinds Cc: opnfv-tech-discuss@lists.opnfv.org Subject: Re: [opnfv-tech-discuss] [infra] License checks in CI Bryan, "and others" isn't necessarily required but I have

Re: [opnfv-tech-discuss] [infra] License checks in CI

2017-04-21 Thread Raymond Paik
Bryan, "and others" isn't necessarily required but I have seen instances where people use it. I think it's helpful incase there are new contributors to the code in the future (who were not the original authors of the code) Thanks, Ray On Fri, Apr 21, 2017 at 1:36 AM, Luke Hinds wrote: >

Re: [opnfv-tech-discuss] [infra] License checks in CI

2017-04-21 Thread Luke Hinds
On Fri, Apr 21, 2017 at 5:34 AM, SULLIVAN, BRYAN L wrote: > Luke, is the “and others.” required? If only one contributor has > contributed to the code for a module, “and others” seems to be superfluous. > So far, I have not seen specific guidance that this is required. > > > I am using the text

Re: [opnfv-tech-discuss] [infra] License checks in CI

2017-04-21 Thread Luke Hinds
On Fri, Apr 21, 2017 at 4:44 AM, Raymond Paik wrote: > Thanks Luke. This is cool... > > In case people use the SPDX identifier, could you check for the following > as well? > This should be possible, I will try a few things out. > > ###

Re: [opnfv-tech-discuss] [infra] License checks in CI

2017-04-20 Thread SULLIVAN, BRYAN L
Luke, is the “and others.” required? If only one contributor has contributed to the code for a module, “and others” seems to be superfluous. So far, I have not seen specific guidance that this is required. Also, does the tool support the abbreviated license form? Thanks, Bryan Sullivan | AT&T

Re: [opnfv-tech-discuss] [infra] License checks in CI

2017-04-20 Thread Justin chi
Hi Yujun, I have merged your commits and add you as collaborators. Regards Justin 2017-04-21 8:25 GMT+08:00 Yujun Zhang (ZTE) : > Note that > >1. the script repository has been renamed to Justin-chi/License >2. people need to update the company list before using it, example in >[1]

Re: [opnfv-tech-discuss] [infra] License checks in CI

2017-04-20 Thread Raymond Paik
Thanks Luke. This is cool... In case people use the SPDX identifier, could you check for the following as well? ## # Copyright (c) 2017 Donald Duck [dd...@warnerbros.com] and others. # # All rights reserved. This

Re: [opnfv-tech-discuss] [infra] License checks in CI

2017-04-20 Thread Ash Young
Cool! I'm gonna check it out. Have a new version of PMD to also factor into this. On Thu, Apr 20, 2017 at 9:43 AM, Luke Hinds wrote: > We have licence checking code staged for CI. > > 2017-04-20 15:27:43,197 - anteater.src.scan_tasks - INFO - Running Licence > Check on: insecure-test-repo > 2017

Re: [opnfv-tech-discuss] [infra] License checks in CI

2017-04-20 Thread Yujun Zhang (ZTE)
Note that 1. the script repository has been renamed to Justin-chi/License 2. people need to update the company list before using it, example in [1] @Justin, could you check Github and review my pull request? [1]: https://github.com/Justin-chi/License/pull/1/files On Thu, Apr 20, 2017 at 1

[opnfv-tech-discuss] [infra] License checks in CI

2017-04-20 Thread Luke Hinds
We have licence checking code staged for CI. 2017-04-20 15:27:43,197 - anteater.src.scan_tasks - INFO - Running Licence Check on: insecure-test-repo 2017-04-20 15:27:43,198 - anteater.src.scan_tasks - INFO - Licence Check passed for: /home/luke/ant_repos/insecure-python/path_traversal.py 2017-04-2