mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: linux-kernel@vger.kernel.org
Subject: Licensing & copyright of kernel .config files (defconfig, *config)
Date: Sun, 1 Jun 2014 01:43:01 +0000	[thread overview]
Message-ID: <robbat2-20140601T012929-356267352Z@orbis-terrarum.net> (raw)

(Please CC me on replies, not subscribed to LKML)

Hi,

Somewhat of an odd question, but none of the files in question seem to
have a copyright header on them...

For a kernel .config file, either from one of the defconfig or any other
*config option that automates the answer:
1. What license does the file fall under?
2. Who are the copyright holders?

Naively, since the defconfigs are bundled with the kernel, that could
fall under GPLv2-only implicitly, but lacking any explicit copyright
headers makes this interesting (arch/*/configs/* contain lots of files,
no copyright headers on them).

If I manually write the names of some configuration options to a new
.config file, at that point I logically am the only author and have
copyright of it. My editor slaps a default license on it of BSD-2.
Thereafter I run olddefconfig, and now it's a combined work of the
kernel's defconfig and my manual settings. If GPL-2 was inherited from
the kernel tree, this is now a combined BSD-GPL2 work, or is it? The
kernel config tools did consider my file as input, possibly overrode the
settings if they didn't work with others, and re-output everything.

If the files are to be marked with a copyright header, who is the holder
of it that it should be attributed to?

Alternatively, is this a case where the work is not copyrightable, and
the files should have a notice to that effect?

Background:
Gentoo has a bunch of "stock" kernel configurations for release
engineering, our initramfs tool (genkernel), and other endeavors over
the years. These projects claim BSD, GPL2, LGPL2 on various pieces, and
I don't think they can all be correct. I'm working on getting them into
one place, because some of them have been getting stale, but the
differing licenses raised a red flag to me.

-- 
Robin Hugh Johnson
Gentoo Linux: Developer, Infrastructure Lead
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85

             reply	other threads:[~2014-06-01  1:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01  1:43 Robin H. Johnson [this message]
2014-06-01  1:52 ` David Lang
2014-06-01 23:01 ` Ken Moffat
2014-06-01 23:29   ` Robin H. Johnson
2014-06-02  4:18     ` David Lang

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=robbat2-20140601T012929-356267352Z@orbis-terrarum.net \
    --to=robbat2@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®