From: Ondrej Mosnacek <omosnace@redhat.com>
To: William Roberts <bill.c.roberts@gmail.com>
Cc: SElinux list <selinux@vger.kernel.org>,
"Roberts, William C" <william.c.roberts@intel.com>
Subject: Re: [PATCH v2] scripts/ci: license as MIT
Date: Fri, 7 Aug 2020 14:28:21 +0200 [thread overview]
Message-ID: <CAFqZXNv1gKEXZ0yOasKV9nLxR6d3xs8GVTudVABzUn2qK-xVZA@mail.gmail.com> (raw)
In-Reply-To: <CAFftDdoye_BgA24w8R67x4NWTATovT5-4zdx-k3QR=J1gEypbQ@mail.gmail.com>
On Tue, Aug 4, 2020 at 4:36 PM William Roberts <bill.c.roberts@gmail.com> wrote:
> Sounds good.
>
> On Tue, Aug 4, 2020 at 9:35 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> >
> > On Mon, Aug 3, 2020 at 6:44 PM William Roberts <bill.c.roberts@gmail.com> wrote:
> > > On Mon, Aug 3, 2020 at 11:31 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> > > >
> > > > On Mon, Aug 3, 2020 at 5:14 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
> > > > > MIT.
> > > > >
> > > > > Signed-off-by: William Roberts <william.c.roberts@intel.com>
> > > > > ---
> > > > > v1: Apache 2.0
> > > > > v2: MIT
> > > > >
> > > > > scripts/ci/LICENSE | 7 +++++++
> > > > > scripts/ci/fedora-test-runner.sh | 2 +-
> > > > > scripts/ci/travis-kvm-setup.sh | 2 +-
> > > > > 3 files changed, 9 insertions(+), 2 deletions(-)
> > > > > create mode 100644 scripts/ci/LICENSE
> > > > >
[...]
> > > > > diff --git a/scripts/ci/fedora-test-runner.sh b/scripts/ci/fedora-test-runner.sh
> > > > > index 569723387f6b..0aaba87c421b 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: MIT
> > > >
> > > > As I said in the v1 thread, also the individual files should contain a
> > > > copyright line in addition to the SPDX line. See:
> > > > https://matija.suklje.name/how-and-why-to-properly-write-copyright-statements-in-your-code#why-have-the-copyright-statement
> > >
> > > You don't actually need them and they just clutter the code and as a
> > > policy, I don't participate in adding to the problem of these big
> > > blocks
> > > of copyright statements that need to be maintained and grow per
> > > contributor. I can just drop the SPDX identifiers, as the LICENSE file
> > > applies to everything.
> > >
> > > With version control, the issues as described by that author are less
> > > of a problem. We can easily
> > > trace from whom, by how and when code was modified for any legal
> > > issues if they were to arise.
> > >
> > > We can just keep the LICENSE file, drop the SPDX identifiers and I
> > > would be 100% in-line with that libselinux is currently doing.
> >
> > I tend to disagree, but I can live with it if you want to leave it
> > out. So let me ACK this patch and I'll just remove the template
> > "Copyright" line from the LICENSE file when applying.
> >
> > Acked-by: Ondrej Mosnacek <omosnace@redhat.com>
Patch applied.
--
Ondrej Mosnacek
Software Engineer, Platform Security - SELinux kernel
Red Hat, Inc.
prev parent reply other threads:[~2020-08-07 12:28 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
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 [this message]
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=CAFqZXNv1gKEXZ0yOasKV9nLxR6d3xs8GVTudVABzUn2qK-xVZA@mail.gmail.com \
--to=omosnace@redhat.com \
--cc=bill.c.roberts@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).