Skip to content

Conversation

@jafingerhut
Copy link
Contributor

This does not change any licenses of any files -- it only adds their SPDX license id names to files that already have them.

This does not change any licenses of any files -- it only adds their
SPDX license id names to files that already have them.

Signed-off-by: Andy Fingerhut <andy.fingerhut@gmail.com>
@jafingerhut
Copy link
Contributor Author

For comparison if you are curious, here is the SPDX description of the FSF All Permissive (FSFAP) license: https://spdx.org/licenses/FSFAP.html

Copy link
Member

@antoninbas antoninbas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jafingerhut for these .m4 files, I would actually recommending not modifying them at all. We copy them verbatim from gnu.org, and I personally don't think it makes sense to add the SPDX-License-Identifier to them ourselves.

@jafingerhut
Copy link
Contributor Author

Closing this, as my leading contender for adding copyright and license info for files that cannot support them directly in comments (e.g. JSON data files) is the REUSE project, which stores the copyright and license info for such files in a separate project-wide file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants