-
Notifications
You must be signed in to change notification settings - Fork 29
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
REUSE compatibility #693
Comments
I discussed this with @mkroening, and we decided not to use copyright headers.
|
I don't think we should move the license files. There is no precedent in the Rust community that I am aware of, but to the best of my knowledge, having |
Totally agree that this should not be done on its own, as this would be a "partial implementation" of a greater set of standards that is not otherwise seen anywhere, whereas REUSE includes moving the licenses to a I'll just work on something less bureaucratic instead. =) |
REUSE (reuse.software) is a standard by the Free Software Foundation Europe that is a superset of the SPDX-styled copyright headers that you see in the Linux kernel.
They make reusing source code across separate projects (or entirely different projects) much easier, as you can just copy and paste segments across different projects (or an entirely different project, with different "copyright owners" or even different, but compatible licensing models) without caring too much about the whole compliance part.
In short, the following changes would have to be theoretically made, given that there's interest:
LICENSES/
(as projects, such as this one, can have more than one license or consist of components that have more than one license).reuse
folder declaring the license information for e.g. binary files, where adding a text header is not possible or practicalI estimate that this would take approximately 90 minutes, give or take.
The text was updated successfully, but these errors were encountered: