aligned with the NGI0 initiative, I'd like to propose the adoption of REUSE specifications for improvement of copyright and license displaying. The REUSE specifications intend to make licensing easier, setting one way to display all license and copyright information direct on source files in a way that can be human- and machine-readable.
REUSE Features
SPDX copyright and license comment headers for all relevant files
LICENSES directory with all licenses used on the repository
DEP5 file to bulk-license entire directories
Example of implementation
For the repository dat, the majority of the source files has no copyright and license information, although it is clear that the project is under the BSD-3 license.
In the file scr/extensions.js it is not clear who is the copyright holder. Therefore, I'd suggest adding the following comment headers:
// SPDX-FileCopyrightText: 2015 Max Ogden (or who else wrote the code)
// SPDX-License-Identifier: BSD-3-Clause
The headers could be added then for all relevant files.
Further REUSE compliance
In case you find REUSE useful, we offer a wide range of tools to help you to continuously check and display compliance with the REUSE guidelines.
In case you find REUSE useful for your workflow, you are most encouraged to adopt it. Feel free to follow up on that!
okdistribute
commented
4 years ago
Hello,
aligned with the NGI0 initiative, I'd like to propose the adoption of REUSE specifications for improvement of copyright and license displaying. The REUSE specifications intend to make licensing easier, setting one way to display all license and copyright information direct on source files in a way that can be human- and machine-readable.
REUSE Features
Example of implementation
For the repository dat, the majority of the source files has no copyright and license information, although it is clear that the project is under the BSD-3 license. In the file
scr/extensions.jsit is not clear who is the copyright holder. Therefore, I'd suggest adding the following comment headers:// SPDX-FileCopyrightText: 2015 Max Ogden(or who else wrote the code)// SPDX-License-Identifier: BSD-3-ClauseThe headers could be added then for all relevant files.
Further REUSE compliance
In case you find REUSE useful, we offer a wide range of tools to help you to continuously check and display compliance with the REUSE guidelines.
In case you find REUSE useful for your workflow, you are most encouraged to adopt it. Feel free to follow up on that!
Thanks for the amazing job!