<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font size="-1"><tt>Hi all,<br>
<br>
+1 to slowly deprecate dep5, for all reasons given before<br>
</tt></font><font size="-1"><tt><font size="-1"><tt>+1 to store
folder specific licensing info *inside* the folders (I guess
we all agree in fact)<br>
</tt></font></tt></font><br>
<font size="-1"><tt><font size="-1"><tt>While it is true that
information will be scattered, it will also be easily
collected by<br>
any tool (to build an SPDX file for ex.)<br>
</tt></font><br>
</tt></font><font size="-1"><tt><font size="-1"><tt>Another point
to make clear, is the precedence between the identification
mechanisms:<br>
For ex.: dep5 < Folder licensing < cat.jpg.license
style < in-file header style<br>
<br>
</tt></font>The formalism discussed in the other 'repurpose
central LICENSE file' thread<br>
could be also applied at every folder level, so that we have a
very nice recursive<br>
way of licensing files down the tree.<br>
<br>
Nico<br>
<br>
</tt></font><br>
<div class="moz-cite-prefix">On 10/03/2020 10:32, Carmen Bianca
Bakker wrote:<br>
</div>
<blockquote type="cite"
cite="mid:3aba4997f6fc55562152cafd371c4f30be9fe40a.camel@fsfe.org">
<pre class="moz-quote-pre" wrap="">Je mar, 2020-03-10 je 07:14 +0000, Geyer-Blaumeiser Lars (IOC/PDL4)
skribis:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Hi Carmen, all,
concerning your point if the equal mechanism between file.license and folder.license. As I understand it, the preferred solution is that the license information is IN the file, not at the side of the file in another file, right. This is only the compromise for not being able to add the license information into the file. But wouldn't it be closer to the original idea to add this folder license information IN the folder instead of at the side of the folder.
In addition to Jeffs remark, also zipping a subfolder is much easier, if the folder contains all necessary information.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Hi Lars,
Yes, sorry, my message hadn't made it clear. That is my fault. If we go
this route, I would be in favour of putting this file *inside* of the
folder, knowing that it wouldn't mesh elegantly with the existing
`file.license` method.
And you're also right: `file.license` is a fallback mechanism if you
can't put the information inside of the file. Technically so is the
file that is proposed in this thread.
Yours with kindness,
Carmen
_______________________________________________
REUSE mailing list
<a class="moz-txt-link-abbreviated" href="mailto:REUSE@lists.fsfe.org">REUSE@lists.fsfe.org</a>
<a class="moz-txt-link-freetext" href="https://lists.fsfe.org/mailman/listinfo/reuse">https://lists.fsfe.org/mailman/listinfo/reuse</a>
This mailing list is covered by the FSFE's Code of Conduct. All
participants are kindly asked to be excellent to each other:
<a class="moz-txt-link-freetext" href="https://fsfe.org/about/codeofconduct">https://fsfe.org/about/codeofconduct</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Nicolas Toussaint
OBS - Orange Business Services - Lyon, France
Tel: +33 608 763 559</pre>
</body>
</html>