All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Roberts <bill.c.roberts@gmail.com>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: SElinux list <selinux@vger.kernel.org>,
	William Roberts <william.c.roberts@intel.com>
Subject: Re: [PATCH] scripts/ci: license as Apache 2.0
Date: Fri, 31 Jul 2020 16:23:03 -0500	[thread overview]
Message-ID: <CAFftDdr6RQLX7odto1uC2SWHTO4ukHD7xHAo1Frr202kab5fiw@mail.gmail.com> (raw)
In-Reply-To: <CAFqZXNtnzP=F_-n_6VRuEnErqmFex0x0C7z5nP=970-n-4aurw@mail.gmail.com>

On Fri, Jul 31, 2020 at 4:11 PM Ondrej Mosnacek <omosnace@redhat.com> wrote:
>
> On Fri, Jul 31, 2020 at 7:33 PM <bill.c.roberts@gmail.com> wrote:
> > From: William Roberts <william.c.roberts@intel.com>
> >
> > 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@intel.com>
> > ---
> >  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.
>

  reply	other threads:[~2020-07-31 21:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-31 14:03 License of userspace CI scripts? Ondrej Mosnacek
2020-07-31 15:09 ` William Roberts
2020-07-31 17:33   ` [PATCH] scripts/ci: license as Apache 2.0 bill.c.roberts
2020-07-31 21:11     ` Ondrej Mosnacek
2020-07-31 21:23       ` William Roberts [this message]
2020-08-03  8:01         ` Ondrej Mosnacek
2020-08-03 15:14           ` [PATCH v2] scripts/ci: license as MIT bill.c.roberts
2020-08-03 16:31             ` Ondrej Mosnacek
2020-08-03 16:43               ` William Roberts
2020-08-04 14:34                 ` Ondrej Mosnacek
2020-08-04 14:36                   ` William Roberts
2020-08-07 12:28                     ` Ondrej Mosnacek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFftDdr6RQLX7odto1uC2SWHTO4ukHD7xHAo1Frr202kab5fiw@mail.gmail.com \
    --to=bill.c.roberts@gmail.com \
    --cc=omosnace@redhat.com \
    --cc=selinux@vger.kernel.org \
    --cc=william.c.roberts@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.