On Fri, Jul 31, 2020 at 4:11 PM Ondrej Mosnacek <omosnace@xxxxxxxxxx> wrote: > > On Fri, Jul 31, 2020 at 7:33 PM <bill.c.roberts@xxxxxxxxx> wrote: > > From: William Roberts <william.c.roberts@xxxxxxxxx> > > > > License the ci scripts with a permissive, OSI approved license, such as > > Apache 2.0. > > Thanks! On second thought though, I guess any open source license > would be fine, since the scripts don't "link" with the rest of the > testsuite (which is GPLv2). So if you prefer some more permissive (or > shorter... :) license or just public domain, you can probably use > that, too. I can do MIT, does that work? > > > > > Signed-off-by: William Roberts <william.c.roberts@xxxxxxxxx> > > --- > > scripts/ci/LICENSE | 202 +++++++++++++++++++++++++++++++ > > scripts/ci/fedora-test-runner.sh | 2 +- > > scripts/ci/travis-kvm-setup.sh | 2 +- > > 3 files changed, 204 insertions(+), 2 deletions(-) > > create mode 100644 scripts/ci/LICENSE > > > > <snip> > > > diff --git a/scripts/ci/fedora-test-runner.sh b/scripts/ci/fedora-test-runner.sh > > index 569723387f6b..8d6a572eb094 100755 > > --- a/scripts/ci/fedora-test-runner.sh > > +++ b/scripts/ci/fedora-test-runner.sh > > @@ -1,5 +1,5 @@ > > #!/usr/bin/env bash > > - > > +# SPDX-License-Identifier: Apache-2.0 > > I think you should also add a copyright line alongside the SPDX header. See: > https://matija.suklje.name/how-and-why-to-properly-write-copyright-statements-in-your-code#why-have-the-copyright-statement > > > set -ev > > > > # > > diff --git a/scripts/ci/travis-kvm-setup.sh b/scripts/ci/travis-kvm-setup.sh > > index 8d4cfb79f7d7..275d05299971 100755 > > --- a/scripts/ci/travis-kvm-setup.sh > > +++ b/scripts/ci/travis-kvm-setup.sh > > @@ -1,5 +1,5 @@ > > #!/usr/bin/env bash > > - > > +# SPDX-License-Identifier: Apache-2.0 > > Ditto. > > > set -ev > > > > TEST_RUNNER="scripts/ci/fedora-test-runner.sh" > > -- > > 2.17.1 > > > > -- > Ondrej Mosnacek > Software Engineer, Platform Security - SELinux kernel > Red Hat, Inc. >
