Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: Global default .license file #605

Closed
lofidevops opened this issue Oct 12, 2022 · 3 comments
Closed

Suggestion: Global default .license file #605

lofidevops opened this issue Oct 12, 2022 · 3 comments
Labels
wontfix This will not be worked on

Comments

@lofidevops
Copy link

Problem statement:

I've encountered some resistance to per-file notices. And I'd like to generally ease adoption :)

Suggested solution:

Declare a file called .license at the root of the project/repo. If any file is missing a copyright declaration, assume that .license applies. (It is the responsibility of the maintainer to make sure this holds true.)

@carmenbianca
Copy link
Member

I've encountered some resistance to per-file notices.

This is recurring, but the per-file notices are also the entire foundation of REUSE. They're the idea upon which REUSE is founded.

If you're doing REUSE by putting a glob on the entire project that says 'Copyright: The Project Contributors; SPDX-License-Identifier: My-License' (which you can already do in .reuse/dep5), then you're doing REUSE wrong. You're just satisfying the linter instead of putting in the work of getting copyright and licensing right, when the entire point of the linter is to help you get copyright and licensing right.

Closing WONTFIX. #534 and #68 combined would somewhat address this issue by automagically populating every file with headers on every commit, using default values.

@carmenbianca carmenbianca added the wontfix This will not be worked on label Oct 12, 2022
@lofidevops
Copy link
Author

@carmenbianca Thanks for the clarification! The tickets you pointed to are helpful. Perhaps the lesson I should take away is not suggesting reuse to someone who doesn't like per-file notices 😭

@seabass-labrax
Copy link
Contributor

I sympathise, @lofidevops - there are still those who are yet to be convinced, but bravo for giving it a go 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants