Make repository REUSE compliant

[xsuchy]

See https://reuse.software/spec/

[kraih]

Thanks, i'll have to read up on that spec. Not familiar with it yet.

[kraih]

Ignoring the question if we want to use the REUSE spec for Cavil. The license declarations are actually in large parts incorrect. All code and tests are GPL-2.0-or-later. Test data is entirely synthetic and has license declarations (often incorrect ones) merely for testing purposes. One exception being the included tarball of a Mojolicious Perl package release (which has its own set of licensing information) used for testing the unpacker and indexer.

[kraih]

Given that openSUSE has not adopted the REUSE spec in any form (i'm not aware it has ever even been discussed), i'm not sure why we would want this metadata in the repo tbh.

[kraih]

Of course i can see why this information would be attractive to packagers. But realistically, it's not something you're going to convince many upstream projects of maintaining for you long term. This is for Linux distributions to take care of themselves.

[xsuchy]

It is an interesting question how we should interpret SPDX-License-Identifier: MIT in these headers. I asked our legal for insights.
It would be likely better if there were comments that the SPDX-License-Identifier declaration there is just for testing purposes and not declaring actually license.

i'm not sure why we would want this metadata in the repo tbh.

The purpose of REUSE is that you can disambiguate the licenses in project. If... err... When more projects will use it, then projects like Cavil can stop guessing what license projects are using and use this curated data that can be trusted.
And maintenance of this data is not big pain. In case of Cavil close to zero.