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
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
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