- REUSE - FSFE Mailinglists

"exclusive-use license" for a project logo
by c.buhtz＠posteo.jp 29 Aug '24

29 Aug '24

Hello, my question has two parts. First I am asking about which licence to choose how to express in SPDX manner for a specific situation. Second is about which alternative situations are imaginable. We are a FLOSS project (GPL-v2-or-later) now having an extern author offering us a logo for free. He is not very interested in licensing issues. We want to use (and modify) the logo for our project but also want to prevent other projects to use that logo in other contexts. To my understanding this could be achieved if the author grant the project an exclusive-use license with rights to modify in perpetuity. But this is not a FLOSS license. How can I express such a license with SDPX? If you have another idea how we could achieve our goals please let me know. Best, Christian Buhtz https://github.com/bit-team/backintime/issues/215

2 2

Accessing https://reuse.software/ fails from various browsers
by Hoeppler Christian (CR/ASD2) 27 Aug '24

27 Aug '24

Hi all, I currently fail to access the website https://reuse.software/ from various browsers (Firefox & Chrome on Windows, Safari on iOS) which claim that a secure connection cannot be established (Firefox provides the error code an SSL_ERROR_INTERNAL_ERROR_ALERT). Is this a problem on my end, or some certificate or other issue at the website? Thanks, Chris Mit freundlichen Grüßen / Best regards Dr. Christian Hoeppler Open Source Officer (CR/ASD2) Robert Bosch GmbH | Renningen | 70465 Stuttgart | GERMANY | www.bosch.com Tel. +49 711 811-43624 | christian.hoeppler(a)de.bosch.com<mailto:christian.hoeppler@de.bosch.com> Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 14000; Chairman of the Supervisory Board: Prof. Dr. Stefan Asenkerschbaumer; Managing Directors: Dr. Stefan Hartung, Dr. Christian Fischer, Dr. Markus Forschner, Stefan Grosch, Dr. Markus Heyn, Dr. Frank Meyer, Dr. Tanja Rückert

4 4

Good practice for Markdown-files?
by Kurzmann Marcel (BD/TOA-IDE2) 19 Aug '24

19 Aug '24

Hi all, I am new to that list but I have an urgent question. We are using Docusaurus as Website-Framework (https://docusaurus.io/) and plan to share assets in Markdown via our new community website. While adding a copyright header in markdown sounds trivial, we would prefer to not mess up the generated website with all the copyright headers on each page. Thus we need to have a way to “comment” in markdown. Are there already any good-practices in the reuse-community how to handle this best and that also the reuse-tool is satisfied? Here is a thread for potential “comments in markdown”: https://stackoverflow.com/questions/4823468/comments-in-markdown An example reuse-header could then look like e.g. : [comment]: <> (SPDX-FileCopyrightText: 2024 copyright owner) [comment]: <> (SPDX-License-Identifier: GPL-3.0-or-later) Or [//]: # (SPDX-FileCopyrightText: 2024 copyright owner) [//]: # (SPDX-License-Identifier: GPL-3.0-or-later) Any recommendations? Would that also work with the reuse-tool? In parallel I try to setup the reuse-tool in order to check how the tool would handle this. Mit freundlichen Grüßen / Best regards Marcel Kurzmann Center of Excellence Open Source and InnerSource (BD/TOA-IDE2) Senior Expert Robert Bosch GmbH | Ziegelei 7 | 88090 Immenstaad | GERMANY | www.bosch.com Tel. +49 7545 202-279 | Mobil +49 172 1499942 | Telefax +49 7545 202-301 | Marcel.Kurzmann(a)bosch.com<mailto:Marcel.Kurzmann@bosch.com> Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000; Aufsichtsratsvorsitzender: Prof. Dr. Stefan Asenkerschbaumer; Geschäftsführung: Dr. Stefan Hartung, Dr. Christian Fischer, Dr. Markus Forschner, Stefan Grosch, Dr. Markus Heyn, Dr. Frank Meyer, Dr. Tanja Rückert

3 2

REUSE Specification v3.2 released
by Carmen Bianca BAKKER 03 Jul '24

03 Jul '24

Hi REUSE mailing list, Today, version 3.2 of the REUSE Specification has been released. It can be found at <https://reuse.software/spec-3.2>. Version 3.2 contains many small improvements compared to the previous version released in 2019[^1], but the biggest change is an adjustment to order of precedence of information, and a new format (REUSE.toml) to replace DEP5 as used in REUSE. The new format is easier to write and parse, and is better at disambiguating certain corner cases. Alongside the update of the spec, there have been many improvements to the Frequently Asked Questions[^2] to help new adopters. The release of the specification is accompanied by version 4.0 of the tool[^3]. It implements REUSE.toml and has a wealth of other improvements, including comprehensive man pages[^4]. Many thanks for the submitted feedback in advance of this release! Yours with kindness, Carmen [^1]: <https://github.com/fsfe/reuse-website/blob/main/CHANGELOG.md#32---2024-07-03 > [^2]: <https://reuse.software/faq/> [^3]: <https://github.com/fsfe/reuse-tool/blob/main/CHANGELOG.md#400---2024-07-03> [^4]: <https://reuse.readthedocs.io/en/v4.0.1/man/index.html>

1 0

REUSE and license compatibility
by Carsten Agger 02 Jul '24

02 Jul '24

Is it correctly understood that the REUSE linting doesn't address license compatibility? I tried, as a experiment, to place the "models.py" in a Django app under GPL-3.0-only and the "views.py" under GPL-2.0-only, which is definitely an incompatible usage, and the linting passed. Are there any plans to consider license compatibility in REUSE, or is that considered out of scope? (That would, of course, be fair enough.) Best, Carsten

6 8

Option to remove headers with the REUSE tool?
by Gabriel Ku Wei Bin 27 Jun '24

27 Jun '24

Hi all, Hope everyone's well! Quick question: can the REUSE tool remove comment headers? One of the projects with NGI0 is quite keen on having this functionality, but I've never actually had to remove headers (or actually thought about it). I notice that this was also brought up a few years back, was this ever implemented? (https://github.com/fsfe/reuse-tool/issues/330) Thanks! Gabriel -- Gabriel Ku Wei Bin (he/him) - Programme Manager (Legal) Free Software Foundation Europe Schönhauser Allee 6/7, 10119 Berlin, Germany | t +49-30-27595290 Registered at Amtsgericht Hamburg, VR 17030 | https://fsfe.org/support

1 0

REUSE alpha release: v3.1.0a1
by Carmen Bianca BAKKER 28 May '24

28 May '24

Hi REUSE mailing list, Today we have released v3.1.0a1 of the REUSE tool. This is an alpha release which contains the new REUSE.toml functionality that replaces .reuse/dep5 (which is soft-deprecated). The purpose of the alpha release is to gather feedback on REUSE.toml. Specifically: - Does REUSE.toml solve real problems? - Does .reuse/dep5 solve any problems that REUSE.toml doesn't? - Are there any problems that REUSE.toml doesn't solve, but could solve? - Is REUSE.toml sufficiently documented? The main purpose of REUSE.toml is to disambiguate .reuse/dep5 scenarios as written in <https://github.com/fsfe/reuse-tool/issues/779>: if a file has a header and is also covered by .reuse/dep5, and the two sources of information disagree about the licence, which licence applies? Because this is an alpha release, the accompanying documentation is not yet easily discoverable, but it is (in the process of being) written. Below some links, and I have also attached some documents for ease of reading. - The new REUSE Specification v3.2 <https://reuse.software/spec-3.2/> - An updated FAQ (under construction) <https://github.com/carmenbianca/reuse-website/blob/3.2-improvements/site/co…> - The tool documentation <https://reuse.readthedocs.io/en/v3.1.0a1/> - New man pages <https://reuse.readthedocs.io/en/v3.1.0a1/man/index.html> - The change log <https://reuse.readthedocs.io/en/v3.1.0a1/history.html> - The alpha release on PyPI <https://pypi.org/project/reuse/3.1.0a1/> If you have time to check it out, we would love to receive your feedback. You can write to this mailing list, to the reuse-tool[1] repository for tool-related issues, and to the reuse-website[2] repository for spec/FAQ/documentation-related issues. Yours with kindness, Carmen [1]: <https://github.com/fsfe/reuse-tool> [2]: <https://github.com/fsfe/reuse-website>

1 1

v3.0 not fit for good first impression of a Free Software component
by Bernhard Reiter 14 May '24

14 May '24

Hello, in https://github.com/fsfe/reuse-docs/issues/147 How to determine "overall" license I've asked for the use case to be considered that I want my Free Software component to be attractive for others. Especially to those that look for something they can integrate into their product and is compatible with their current licenses. As there are many Free Software products, I'll need a first indication to either look elsewhere or to take a deeper look. If a repository indicates the license that everything will be compatible under a license, which usually is the one with the highest freedom protection, that is the needed info. However REUSE 3.0 cannot indicate such a license (at least I do not know how). Thus a repository which is fully REUSE compatible currently is at a disadvantage compared to other repos on popular code platforms. Some platforms do not understand the information per file coming from Reuse. And even if those platforms could deal with the more complex information provided by a REUSE compatible repos, they still could not display this important summary info about licensing in a repo, as it is not expressed. Is Matija's closing of the issue 147 showing that this use case is irrelevant to REUSE? Regards, Bernhard -- www.intevation.de/~bernhard +49 541 33 508 3-3 Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter

3 3

Spec 3.1 is in main, but not released?
by Bernhard Reiter 02 May '24

02 May '24

Hi, https://git.fsfe.org/reuse/docs/src/branch/main/CHANGELOG.md has 3.1 - 2023-06-21 and there is https://github.com/fsfe/reuse-docs/pull/133 to prepare 3.2 of the spec _but_ https://reuse.software/spec/ has Version 3.0 and https://github.com/fsfe/reuse-docs/tags latest tag is 3.0 which confuses me. So is version 3.1 of the specification released and the website and git tag should be fixed to reflect this? Best, Bernhard -- https://intevation.de/~bernhard +49 541 33 508 3-3 Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter

4 7

How to set "packageVersion" in Python code
by c.buhtz＠posteo.jp 25 Mar '24

25 Mar '24

Hello, I am quite new to SPDX and REUSE. In only one file of my project I need to set explicit the version of the package in context of SPDX. I read about "packageVersion" in the specs: <https://spdx.github.io/spdx-spec/v2.3/package-information/#73-package-versi…> My problem is that I don't know how to use this in Python code. I tried this with two variantes o package version. # SPDX-FileCopyrightText: © 2023 Christian BUHTZ <c.buhtz(a)posteo.jp> # PackageVersion: 1.2.3 # SPDX-PackageVersion: 1.2.3 # SPDX-License-Identifier: GPL-3.0-only # # This file is part of the program "Hyperorg" which is released under GNU # General Public License v3 (GPLv3). # See folder LICENSES or go to <https://www.gnu.org/licenses/#GPL>. Then "reuse lint" didn't mentioned an error. Then I used "reuse spdx" and check the output for that file: FileName: ./src/hyperorg/exporter.py SPDXID: SPDXRef-53df60eaa649de974734329cc7c77625 FileChecksum: SHA1: 7224b16f4bf06c8465cce8013b4cb9900cf063fe LicenseConcluded: NOASSERTION LicenseInfoInFile: GPL-3.0-only FileCopyrightText: <text>SPDX-FileCopyrightText: © 2023 Christian BUHTZ <c.buhtz(a)posteo.jp></text> You see here the version is missing. That is why I think I do something wrong. But I don't know how to fix this, or if even "reuse spdx" is not working correct? (see <https://github.com/fsfe/reuse-tool/issues/935>) Thanks in advance, Christian Buhtz

2 2

2024

2023

2022

2021

2020

2019

2018

REUSE