<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>Hello Max et al.,</p>
<p><br>
</p>
<p>I like the idea, but just a thought. There is the new yaml format in SPDX 2.2, and we are thinking around using this format to mark certain folders as open source component, so identifying components in a repository is eased for open source compliance management.
Might be worth to look into the standard whether this is also suitable for your proposed use case before deciding on a format. What do you think?<br>
</p>
<p><br>
</p>
<div id="x_Signature">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:rgb(0,0,0); font-family:Calibri,Arial,Helvetica,sans-serif,"EmojiFont","Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols">
<div name="x_divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div><span style="font-size:10pt">Mit freundlichen Grüßen / Best regards </span><br>
<br>
<b><span style="font-size:10pt">Dr. Lars Geyer-Blaumeiser</span></b><br>
<br>
<span style="font-size:10pt">Project Delivery - Open Source Services (IOC/PDL4) </span>
<br>
<span style="font-size:10pt">Bosch.IO GmbH | Stuttgarter Straße 130 | 71332 Waiblingen | GERMANY |
</span><span style="font-size:10pt"></span><span style="font-size:10pt">www.bosch.io
</span><br>
<span style="font-size:10pt">Mobil +49 172 4815079 | lars.geyer-blaumeiser@bosch.io
</span><br>
<br>
<span style="font-size:8pt">Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B</span><br>
<span style="font-size:8pt">Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr. Stefan Ferber, Dr. Aleksandar Mitrovic, Yvonne Reckling</span><br>
<br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Von:</b> REUSE <reuse-bounces@lists.fsfe.org> im Auftrag von Max Mehl <max.mehl@fsfe.org><br>
<b>Gesendet:</b> Montag, 20. Juli 2020 17:51:24<br>
<b>An:</b> FSFE REUSE<br>
<b>Betreff:</b> [REUSE] REUSE.yaml</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi all,<br>
<br>
I am starting a new thread, summarising a wild idea we've had when<br>
discussing how to combine the different ideas and expectations that have<br>
been raised in the threads regarding folder.license files and the<br>
deprecation of the DEP5 file.<br>
<br>
Our suggestion would be to implement a new file: REUSE.yaml.<br>
<br>
<br>
# Basic concept<br>
<br>
The purpose would be quite similar to what we already do with DEP5 files<br>
[^1]: communicate copyright/licensing information for a whole<br>
(sub)directory, or also just a certain pattern, e.g. all .png files in a<br>
directory. <br>
<br>
The first downside of DEP5 is that the tags are different from the<br>
normal SPDX/REUSE tags, and that it requires some other meta information<br>
out of REUSE's scope. The second downside is that the DEP5 file has to<br>
be stored in the .reuse/ folder, quite unintuitive and far away from the<br>
actual files.<br>
<br>
As the name suggests, REUSE.yaml would follow the YAML syntax which is<br>
easy to read and write for humans, but it also pretty easy to parse in<br>
tools.<br>
<br>
Another difference would be that there could be multiple REUSE.yaml<br>
files. Each one could only define the directory it is stored in, or also<br>
subdirectories or certain file patterns. So it can also serve as an<br>
alternative to the suggested folder.license files.<br>
<br>
This would make things easier for devs and reusers alike: given that a<br>
repo contains a directory with hundreds of binary files (e.g. images),<br>
the maintainers could create a REUSE.yaml file in it. This way,<br>
copyright and licensing information is close by, but the maintainers<br>
would not have to create $file.license files for every single image, or<br>
store the bulk-information in a far-away file.<br>
<br>
<br>
# Syntax<br>
<br>
Now, if we went that route, we would need a rather fool-proof and easy<br>
way how to mark the REUSE information for a directory, subdirectory, or<br>
pattern. Here are four variants how to do that in YAML, but only one<br>
should be mandated by REUSE in the end:<br>
<br>
<br>
1. Short Array:<br>
```<br>
- src/*:<br>
SPDX-FileCopyrightText: [ "2020 me", "© 2017 you" ]<br>
SPDX-License-Identifier: MIT<br>
```<br>
<br>
2. Short List:<br>
```<br>
- src/*:<br>
SPDX-FileCopyrightText:<br>
- 2020 Me<br>
- © 2017 You<br>
SPDX-License-Identifier: MIT<br>
```<br>
<br>
3. Short String:<br>
```<br>
- src/*: |<br>
SPDX-FileCopyrightText: 2020 Me<br>
SPDX-FileCopyrightText: © 2017 You<br>
SPDX-License-Identifier: MIT<br>
```<br>
<br>
4. Long:<br>
```<br>
- src/*:<br>
license:<br>
SPDX-License-Identifier: MIT<br>
copyright: |<br>
SPDX-FileCopyrightText: 2020 Me<br>
SPDX-FileCopyrightText: © 2017 You<br>
```<br>
<br>
Please help us here: what could possibly go wrong with any of these<br>
variants? Is there tooling for which you know that it would misbehave?<br>
What would make most sense to you as a user?<br>
<br>
<br>
Also, in general, I would be pleased to learn what you think about a<br>
REUSE.yaml file that would be a preferred way how to bulk-license files.<br>
<br>
<br>
Best,<br>
Max<br>
<br>
[^1]: See the one of reuse-tool here as an example:<br>
<a href="https://github.com/fsfe/reuse-tool/blob/master/.reuse/dep5">https://github.com/fsfe/reuse-tool/blob/master/.reuse/dep5</a><br>
<br>
-- <br>
Max Mehl - Programme Manager - Free Software Foundation Europe<br>
Contact and information: <a href="https://fsfe.org/about/mehl">https://fsfe.org/about/mehl</a> | @mxmehl<br>
Become a supporter of software freedom: <a href="https://fsfe.org/join">https://fsfe.org/join</a><br>
_______________________________________________<br>
REUSE mailing list<br>
REUSE@lists.fsfe.org<br>
<a href="https://lists.fsfe.org/mailman/listinfo/reuse">https://lists.fsfe.org/mailman/listinfo/reuse</a><br>
<br>
This mailing list is covered by the FSFE's Code of Conduct. All<br>
participants are kindly asked to be excellent to each other:<br>
<a href="https://fsfe.org/about/codeofconduct">https://fsfe.org/about/codeofconduct</a><br>
</div>
</span></font>
</body>
</html>