mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonas Oberg <jonas@fsfe.org>
To: Charlemagne Lasse <charlemagnelasse@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	carmenbianca@fsfe.org,
	Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: Re: Adding LICENSES folder for REUSE
Date: Sat, 11 Nov 2017 16:21:59 -0500	[thread overview]
Message-ID: <20171111212159.GA25689@silk.coyote.org> (raw)
In-Reply-To: <CAFGhKbxxucnUgdw3Ot5gM5OXJ3tLVibiTK4o73kPbth7RhJmAg@mail.gmail.com>

Hi Charlemagne,

> Since some people started to add the SPDX headers to some files, it
> might now be the right time to ask to get a LICENSES folder which will
> contain the separate licenses.

I wouldn't do that now. Adding SPDX license identifiers is in most cases
quite sufficient and something which I would encourage first.

What you mention about the LICENSES/ folder and the License-Filename 
tag (which can be repeated) is an addition which is a bit more specific,
especially for BSD licenses where the SPDX license identifier alone does
not convey information about the specific "attribution requirement" of
each licensor.

Most often though, as you find the BSD licenses in the source code headers,
we wouldn't want the license text separated from them, and it would be
contrary to the REUSE principles to do so.

So for now, I would recommend to focus on the SPDX license identifiers and
then work out the other details later.


-- 
Jonas Öberg
Executive Director

FSFE e.V. - keeping the power of technology in your hands. Your
support enables our work, please join us today http://fsfe.org/join

  reply	other threads:[~2017-11-11 21:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-11 20:56 Charlemagne Lasse
2017-11-11 21:21 ` Jonas Oberg [this message]
2017-11-11 22:29   ` Charlemagne Lasse
2017-11-12 13:04     ` Carmen Bianca Bakker

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=20171111212159.GA25689@silk.coyote.org \
    --to=jonas@fsfe.org \
    --cc=carmenbianca@fsfe.org \
    --cc=charlemagnelasse@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yamada.masahiro@socionext.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

all inboxes | Powered by JetHome®