From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751244AbdKLNK5 (ORCPT ); Sun, 12 Nov 2017 08:10:57 -0500 Received: from mail.fsfe.org ([217.69.89.162]:33504 "EHLO mail.fsfe.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750953AbdKLNK4 (ORCPT ); Sun, 12 Nov 2017 08:10:56 -0500 X-Greylist: delayed 395 seconds by postgrey-1.27 at vger.kernel.org; Sun, 12 Nov 2017 08:10:56 EST Message-ID: <1510491855.2742.2.camel@fsfe.org> Subject: Re: Adding LICENSES folder for REUSE From: Carmen Bianca Bakker To: Charlemagne Lasse , Jonas Oberg Cc: linux-kernel@vger.kernel.org, Greg Kroah-Hartman , Masahiro Yamada Date: Sun, 12 Nov 2017 14:04:15 +0100 In-Reply-To: References: <20171111212159.GA25689@silk.coyote.org> Organization: Free Software Foundation Europe e.V. Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-6k8Pl38Oiftk5uLgC4Wb" Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --=-6k8Pl38Oiftk5uLgC4Wb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Charlemagne, Charlemagne Lasse schreef op za 11-11-2017 om 23:29 [+0100]: > 1. SPDX license identifier first > 2. Full BSD/MIT/ISC license in source files is sufficient and don't > =C2=A0=C2=A0=C2=A0require License-Filename > 3. verbatim licenses which are not in source files (GPL, LGPL, MPL, ...) > =C2=A0=C2=A0=C2=A0should be in LICENSES/ > 4. License-Filename tag can be added later and multiple are allowed per > =C2=A0=C2=A0=C2=A0file Yes, that is all quite correct :)=C2=A0=C2=A0The REUSE recommendations are threefold, roughly: 1. Include verbatim licence text in repository. 2. Add licence information about each file. 3. (Optional-ish) Create an SPDX bill of materials that can be =C2=A0=C2=A0=C2=A0auto-generated. We also have some recommendations about _how_ you might go about doing this, e.g., putting the licences in a LICENSES folder or putting certain headers in code files, but the exact implementation is eventually up to the project itself. `SPDX-License-Identifier` and `License-Filename` do roughly the same thing, apart from the difference which Jonas mentioned.=C2=A0=C2=A0I know t= hat some kernel code files already use the SPDX-License-Identifier tag, and it seems to me that just satisfying that tag would be sufficient to start with. > If this understanding is correct then I would still propose that the > LICENSES folder is prepared with the previously identified long licenses > (which are currently not stored completely in the source files): If the kernel project did only this and stopped there, that would take you half the way there already.=C2=A0=C2=A0Just having (and distributing) t= he licence texts verbatim is reasonably important as far as legal responsibilities go. Yours sincerely, --=C2=A0 Carmen Bianca Bakker Technical Intern Free Software Foundation Europe e.V. --=-6k8Pl38Oiftk5uLgC4Wb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEaOz9p2Grh2PLV5z6duum9rbqLskFAloIRs8ACgkQduum9rbq LskOWxAAhkV2ktLlfCLLq41aoAvS5Hlr5mHRxl3QxvyJJyLQruq1g/2Giquoklww jUp4Iqw/Ts5TZ2kSl12PsbV9N1DH4ng6+OxcCcEkprc8/It6b8tXu3kbGDY9V7Ol QKMUOOPMAcnsmbsgRFhMVKVAfntMfOZGLVdG/GDivLXBLT3k+eDbgc40EtKHAVdY HNm43436H4IHqbCe/EfHejm9IbPfgXVpnPqCv5W7RPp8RmPEMcdgv3iCwf/vBElh BavqTTDE7WmZHAnovZ3fbbA0nWqa/y5G7X4wDp4/vjJaaSULL5uvLJsGN4+SiRfC 9JmEmzrDzlw/1lOfN5+Fez6IqBB8cPOTKhOY5L3S27ieKsdSkTy/xnbWqtRykjFC y5vG9DTDC0VLdOyYyrPYze/GXi3vXWtKnHBuOCHYhIc8VJg3TqJqHGGPX2S0O92z hJ8ilwSajKw0POqYchtNMQh9DlcT1eZ85nIHcNbbkYfpxPSChw9rhXAOXdY16A4f O3+fGsvJqtZRDk2+34fYeZQYN5oGufzfK6jMQJZnWtLKZhdk3dcHPbP/pNmADQjw 8MXCTvGdDEVpcnkj7Fs9pkQSb1tQv7TQxYS38z+xOdLwZ7P16qpFqyKGcjugISC1 Y7QXIiuU1mz+pwdzNhRO49NAilCvAqLcdPI+/Y4EO5fqntEubXw= =6eTQ -----END PGP SIGNATURE----- --=-6k8Pl38Oiftk5uLgC4Wb--