REUSE July 2023

reuse@lists.fsfe.org

6 participants
3 discussions

Handling of MPL 2.0 license?
by Carsten Agger 07 Feb '24

07 Feb '24

Hi all The REUSE FAQ states that some people "miss the long legal blurbs at the tops of files, miss the |COPYING|/|LICENSE| file in the root of the repository, think that |.license| files clutter the directory, or find it very strange that even insignificant non-code files get licensing headers. The different-ness of REUSE can seem peculiar in that way." I definitely don't miss those blurbs. In that way, REUSE automation is an excellent thing. However, I wonder if this might cause people to fail to apply the MPL 2.0 license. Section 1.4 of the MPL 2.0 license[2] states that "Covered Software" "means Source Code Form to which the initial Contributor has attached the notice in Exhibit A, the Executable Form of such Source Code Form, and Modifications of such Source Code Form, in each case including portions thereof." Exhibit A is this statement: "This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at https://mozilla.org/MPL/2.0/." Normally, this is interpreted as meaning that this statement should be included in headers, however "if it is not possible or desirable to put the notice in a particular file, then You may include the notice in a location (such as a LICENSE file in a relevant directory) where a recipient would be likely to look for such a notice". If you attach the SPDX headers indicating "MPL 2.0", however, this notice appears exactly NOWHERE in the repository except in the license file itself, where it only serves the purpose of specifying the requirement and thus cannot be said to be attached to each file in the repository. There's a question on StackExchange discussing a similar issue.[3] The question is if this particular requirement in MPL 2.0, that actively *demands* the inclusion of a specific text in order to apply, means that REUSE's current standard check is insufficient for the MPL and that the MPL Exhibit A text should be included somewhere? (Like, in a file called ".reuse/MPL2.0-Exhibit-A.txt". Best, Carsten [1]: https://reuse.software/faq/#tradition [2]: https://www.mozilla.org/en-US/MPL/2.0/ [3]: https://opensource.stackexchange.com/questions/7736/is-question-25-from-mpl…

4 8

LicenseRef Alternatives
by duluxoz 31 Jul '23

31 Jul '23

Hi All, A quick question: when using "|# SPDX-License-Identifier: LicenseRef-MyLicense|" does the next actually ***have*** to be that, or can it be something else, such as "|# SPDX-License-Identifier: LicenseRef-LicenseForExampleApp|" Cheers Dulux-Oz

2 2

Fwd: [pietervdvn/MapComplete] adding copyright and license SPDX comment headers for several files (PR #1495)
by Jithendra Palepu 27 Jul '23

27 Jul '23

Hello all! I just got this query from one of the Ngi clients. Would be great if anyone has a solution to this. Thanks much! -------- Forwarded Message -------- Subject: Re: [pietervdvn/MapComplete] adding copyright and license SPDX comment headers for several files (PR #1495) Date: Thu, 27 Jul 2023 05:13:54 -0700 From: Pieter Vander Vennet <notifications(a)github.com> Reply-To: pietervdvn/MapComplete <reply+BALM6FQC6KAJNZTGRON7ES6CZ6JAFEVBNHHGVIVIJQ(a)reply.github.com> To: pietervdvn/MapComplete <MapComplete(a)noreply.github.com> CC: Jit-p <jithendra(a)fsfe.org>, Author <author(a)noreply.github.com> Hi Jithendra, I have generated license files based on the already available license-info and fixed up information about all the other files (most of them through the dep5-file) Some questions remain: 1. Is there a way to add a pointer to the original source in SPDX? 2. A few files are logo's or used with permission and thus /not/ under a free license. I did add a clarifying license for this, but |reuse lint| still refuses those as 'bad licenses'. I understand that this makes the repo not completely free, but it will take a lot of work to separate out these parts. Is there a flag to ignore this? — Reply to this email directly, view it on GitHub <https://github.com/pietervdvn/MapComplete/pull/1495#issuecomment-1653495045>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BALM6FSZ4X55WNVONC6HDG3XS…>. You are receiving this because you authored the thread.Message ID: <pietervdvn/MapComplete/pull/1495/c1653495045(a)github.com>

1 0

2024

2023

2022

2021

2020

2019

2018

REUSE July 2023