Max Mehl comments

Results 226 comments of


                                            Max Mehl

Alter CC0-1.0 recommendation for uncopyrightable files

Unpopular opinion: we could also allow NONE which just was enabled by the latest SPDX release. But well, that's not really what REUSE wants to procure...

More explicit discussion of the .reuse and LICENSES directories

Thank you for the suggestion, very helpful! Just to be clear, the `.reuse` directory is no mandatory. It's just a place for the DEP5 file (if one wants to use...

Alter CC0-1.0 recommendation for uncopyrightable files

> The goal of REUSE is to have valid and useful info in all source code, not which licenses must be used. Very right, thank you for the reminder. What...

Snippet documentation seems to contradict example

Good catch, indeed. It's also wrong in the FAQ, we should fix that before 3.2 spec.

Cover +/-or-later/-only

Is this still relevant? Shall we tweak the FAQ to explain the whole -or-later/-only/+ thingy, or has that become already clear enough?

Explain the namespace use in SPDX 3.0 for custom licenses

Thanks! Indeed, the FAQ seems to be the most appropriate place to add this info. I don't see it touching the REUSE spec since it's under the License-Ref hood.

uncopyrightable files - give info how to handle files with unknown authors but uncopyrightable

Thanks @silverhook! Would it make sense to add a sentence or two to the section in the FAQ? https://github.com/fsfe/reuse-docs/blob/master/faq.md#what-to-do-with-uncopyrightable-files-uncopyrightable

Document how to work with several projects in the same repository

From what you write, the basic problem is that `.reuse/dep5` is only respected on the root of the project, not in subfolders. That is intended to limit the places where...

Document how to work with several projects in the same repository

I understand your use case. However, I am afraid that we won't tinker with allowing more than the current location of the dep5 file at the root of the project...

Define precedence of information with REUSE.yaml

> I like #3. I've been doing REUSE compliance for some repositories which import multiple other repos which are not REUSE-compliant and aren't likely to be, so globbing is important....