Hi all
The REUSE FAQ states that some people "miss the long legal blurbs at the
tops of files, miss the |COPYING|/|LICENSE| file in the root of the
repository, think that |.license| files clutter the directory, or find
it very strange that even insignificant non-code files get licensing
headers. The different-ness of REUSE can seem peculiar in that way."
I definitely don't miss those blurbs. In that way, REUSE automation is
an excellent thing.
However, I wonder if this might cause people to fail to apply the MPL
2.0 license. Section 1.4 of the MPL 2.0 license[2] states that
"Covered Software" "means Source Code Form to which the initial
Contributor has attached the notice in Exhibit A, the Executable Form of
such Source Code Form, and Modifications of such Source Code Form, in
each case including portions thereof."
Exhibit A is this statement: "This Source Code Form is subject to the
terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was
not distributed with this file, You can obtain one at
https://mozilla.org/MPL/2.0/."
Normally, this is interpreted as meaning that this statement should be
included in headers, however "if it is not possible or desirable to put
the notice in a particular file, then You may include the notice in a
location (such as a LICENSE file in a relevant directory) where a
recipient would be likely to look for such a notice".
If you attach the SPDX headers indicating "MPL 2.0", however, this
notice appears exactly NOWHERE in the repository except in the license
file itself, where it only serves the purpose of specifying the
requirement and thus cannot be said to be attached to each file in the
repository. There's a question on StackExchange discussing a similar
issue.[3]
The question is if this particular requirement in MPL 2.0, that actively
*demands* the inclusion of a specific text in order to apply, means
that REUSE's current standard check is insufficient for the MPL and that
the MPL Exhibit A text should be included somewhere? (Like, in a file
called ".reuse/MPL2.0-Exhibit-A.txt".
Best,
Carsten
[1]: https://reuse.software/faq/#tradition
[2]: https://www.mozilla.org/en-US/MPL/2.0/
[3]:
https://opensource.stackexchange.com/questions/7736/is-question-25-from-mpl…
Hi,
I am using the maillist as there is no way to register on the git page
to open an issue.
The current JSON api (for example
https://api.reuse.software/status/github.com/erooster-mail/erooster.json
) includes the spdx output and the lint output as verbatism in text form.
This in my opinion is not really in any way machine readable at this
time. The spdx I guess is fine considering it's a standard in itself.
However the lint output seems weird to me.
Is there any reason why the values are not included as keys? Whats the
reasoning to only include the data as markdown?
---
Marcel Radzio
Hi everyone,
We have great news!
The German Aerospace Center (DLR) has adopted the
REUSE(https://reuse.software) specification in some of its projects. We
have talked to Tobias Schlauch, research software engineer at the DLR,
about the role of Free Software for research, innovation, and the
importance of a clear understanding and displaying of the legal
information of software projects.
You can read the whole interview here, as well as check the short video
where he talks about what he likes the most about REUSE.
https://fsfe.org/news/2023/news-20231102-01.html
Best,
Lina
--
Lina Ceballos - Policy Project Manager
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