chore: make repository REUSE-compliant and improve copyright attribution#106
Open
PhenChua29 wants to merge 7 commits into
Open
chore: make repository REUSE-compliant and improve copyright attribution#106PhenChua29 wants to merge 7 commits into
PhenChua29 wants to merge 7 commits into
Conversation
…fication - Add REUSE.toml with per-file and glob licensing rules - Add required licenses under LICENSES/ - Add SPDX license headers to all 226 source files
Extend the copyright year range to cover active development through 2026.
Update copyright headers to attribute contributors by name alongside the organisation.
List project contributors as required by the Apache 2.0 license notice.
Fix incorrect year ranges in SPDX headers that were still referencing 2024 only.
Add a reuse-lint step to the CI workflow so REUSE compliance is enforced on every push and pull request.
Document the REUSE header requirement in CONTRIBUTING.md so contributors know to include SPDX headers or REUSE.toml entries when adding new files.
PhenChua29
force-pushed
the
chore/reuse-compliance
branch
from
988ea99 to
8a0e905
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR closes #105 by resolving all problems identified in that issue.
Type of Change
Changes Made
SPDX-FileCopyrightTextandSPDX-License-Identifierheaders to all ~230 source filesLICENSES/directory with the required licenses andREUSE.tomlfor binary/untaggable assetsCONTRIBUTORS.mdand updated copyright headers to attribute project contributors2024–2026across all files.github/workflows) to runreuse linton every pull requestRelated Issues
Fixes #105
Testing
make test)make lint)Checklist
Additional Notes
All changes are purely metadata/header additions. No production logic was modified.
Running
reuse lintafter this PR returns 781/784 files compliant:Full logs
MISSING COPYRIGHT AND LICENSING INFORMATION
The following files have no copyright and licensing information:
SUMMARY
Unfortunately, your project is not compliant with version 3.3 of the REUSE Specification :-(
RECOMMENDATIONS
cannot find copyright and/or licensing information. You typically do this by
adding 'SPDX-FileCopyrightText' and 'SPDX-License-Identifier' tags to each
file. The tutorial explains additional ways to do this:
https://reuse.software/tutorial/
The project is not yet fully passing due to 3 first-party Android APKs whose exact licensing provenance is currently unknown:
drivers/android/devicelab-android-driver.apkdrivers/android/devicelab-android-driver-test.apkdrivers/android/settings_apk-debug.apkThese are commented out in
REUSE.tomlpending clarification of their copyright owner and license. Once determined, they can be uncommented and annotated to bring the project to full REUSE compliance.Note
Please review the license and copyright annotations introduced by this PR carefully before merging. While reasonable efforts were made to determine the correct licensing information from upstream sources and file contents, maintainers should independently verify that the assigned licenses and copyright attributions are accurate and appropriate for this project.