Hi REUSE mailing list,
Today we have released v3.1.0a1 of the REUSE tool. This is an alpha
release which contains the new REUSE.toml functionality that replaces
.reuse/dep5 (which is soft-deprecated). The purpose of the alpha
release is to gather feedback on REUSE.toml. Specifically:
- Does REUSE.toml solve real problems?
- Does .reuse/dep5 solve any problems that REUSE.toml doesn't?
- Are there any problems that REUSE.toml doesn't solve, but could
solve?
- Is REUSE.toml sufficiently documented?
The main purpose of REUSE.toml is to disambiguate .reuse/dep5 scenarios
as written in <https://github.com/fsfe/reuse-tool/issues/779>: if a
file has a header and is also covered by .reuse/dep5, and the two
sources of information disagree about the licence, which licence
applies?
Because this is an alpha release, the accompanying documentation is not
yet easily discoverable, but it is (in the process of being) written.
Below some links, and I have also attached some documents for ease of
reading.
- The new REUSE Specification v3.2 <https://reuse.software/spec-3.2/>
- An updated FAQ (under construction)
<https://github.com/carmenbianca/reuse-website/blob/3.2-improvements/site/co…>
- The tool documentation <https://reuse.readthedocs.io/en/v3.1.0a1/>
- New man pages
<https://reuse.readthedocs.io/en/v3.1.0a1/man/index.html>
- The change log
<https://reuse.readthedocs.io/en/v3.1.0a1/history.html>
- The alpha release on PyPI <https://pypi.org/project/reuse/3.1.0a1/>
If you have time to check it out, we would love to receive your
feedback. You can write to this mailing list, to the reuse-tool[1]
repository for tool-related issues, and to the reuse-website[2]
repository for spec/FAQ/documentation-related issues.
Yours with kindness,
Carmen
[1]: <https://github.com/fsfe/reuse-tool>
[2]: <https://github.com/fsfe/reuse-website>
Hello,
in https://github.com/fsfe/reuse-docs/issues/147
How to determine "overall" license
I've asked for the use case to be considered that I want my Free Software
component to be attractive for others. Especially to those that look for
something they can integrate into their product and is compatible with
their current licenses.
As there are many Free Software products, I'll need a first indication to
either look elsewhere or to take a deeper look. If a repository indicates the
license that everything will be compatible under a license, which usually is
the one with the highest freedom protection, that is the needed info.
However REUSE 3.0 cannot indicate such a license (at least I do not know how).
Thus a repository which is fully REUSE compatible currently is at a
disadvantage compared to other repos on popular code platforms.
Some platforms do not understand the information per file coming from Reuse.
And even if those platforms could deal with the more complex information
provided by a REUSE compatible repos, they still could not display this
important summary info about licensing in a repo, as it is not expressed.
Is Matija's closing of the issue 147 showing that this use case
is irrelevant to REUSE?
Regards,
Bernhard
--
www.intevation.de/~bernhard +49 541 33 508 3-3
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter