On Tue, 19 Mar 2019 at 13:28, David P Grove <[email protected]> wrote: > We automate this by running a scancode program ( > https://github.com/apache/incubator-openwhisk-utilities/tree/master/scancode > ) as part of every TravisCI build (both PRs and on master). It can also be > run manually to verify a releases. This doesn't help if scancode is buggy > or the configuration is incomplete, but it does provide some level of > automatic enforcement.
Great! I see this is comparable to how typical ASF projects using Maven will use the rat plugin. I developed an sbt plugin a while ago to do the same, so I'm definitely familiar with the efforts to automate this. :) -- Matt Sicker <[email protected]>
