Hi all,
+1 to slowly deprecate dep5, for all reasons given before +1 to store folder specific licensing info *inside* the folders (I guess we all agree in fact)
While it is true that information will be scattered, it will also be easily collected by any tool (to build an SPDX file for ex.)
Another point to make clear, is the precedence between the identification mechanisms: For ex.: dep5 < Folder licensing < cat.jpg.license style < in-file header style
The formalism discussed in the other 'repurpose central LICENSE file' thread could be also applied at every folder level, so that we have a very nice recursive way of licensing files down the tree.
Nico
On 10/03/2020 10:32, Carmen Bianca Bakker wrote:
Je mar, 2020-03-10 je 07:14 +0000, Geyer-Blaumeiser Lars (IOC/PDL4) skribis:
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.
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 REUSE@lists.fsfe.org https://lists.fsfe.org/mailman/listinfo/reuse
This mailing list is covered by the FSFE's Code of Conduct. All participants are kindly asked to be excellent to each other: https://fsfe.org/about/codeofconduct