-
Notifications
You must be signed in to change notification settings - Fork 149
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
Please allow for a hidden REUSE.toml file #1054
Comments
Hi @mlramd, I am closing this WONTFIX. From #779:
The importance here is the visibility of licensing. We could have gone with an 'unbranded' |
In my experience, a sizeable proportion of those who do FOSS licence compliance have a legal background, and not always a technical one. Having the files hidden by default would add an impediment (admittedly, a small one) to their task. Given that the primary reason for REUSE is to make licence compliance easier, I don't personally think it's the right trade-off to make. |
If you want to force this on people, I can understand that, but I'm not going to be checking the REUSE.toml file into my projects, and I imagine that there will be others that agree. In my mind, reuse is a tool to make sure that we have the licensing in the project correct, and honestly that's all it is. If the licensing isn't correct unless there's an advertisement for your tool in the root of the project, I think that's a problem. Regardless, your projects choices are up to you - All I can say is that I'm not going to be forced into having the file at the root of my projects. Take care. |
I like the idea of using reuse to check my projects, but I don't want the REUSE.toml file in the root directory. It seems like an advertisement for the reuse project. For now I'm just going to keep local copies of the file instead of committing it to the repo.
Could you make reuse work with .REUSE.toml or .reuse/REUSE.toml please? Even giving reuse an option for a config file name, rather than having it hardcoded would work.
Thanks.
The text was updated successfully, but these errors were encountered: