docker / docker/docker-ce-packaging
consider adding machine-readable `copyright` file (DEP5) file to deb packages
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 209
- Forks
- 164
- Avg merge
- 2h 24m
- Merged PRs (30d)
- 4
Description
A bit related to the discussion in https://github.com/docker/docker-ce-packaging/issues/1112
Debian introduced a machine-readable format for adding licensing information to packages and it looks like the proposal (https://dep-team.pages.debian.net/deps/dep5/) is accepted and now "1.0". Should we consider adding those?
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Some challenges may be to mark individual files? (i.e. there may be files having a different license).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is identified. Read the linked packaging discussion and DEP5 1.0 specification, then inspect the repository's Debian package-generation path; done means an agreed machine-readable copyright-file approach, including treatment of files with different licenses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100