Bundle licenses with binary artifacts
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 2h 41m
- Merged PRs (30d)
- 66
Description
We should do something similar to https://github.com/divviup/janus/issues/3229 for divviup-api. The hangup is that as of recently, we distribute binaries of divviup-cli as well as container images, and it's not obvious how to bundle licenses with those. Perhaps shipping the license text files to each divviup-cli release alongside the binaries would work? Or we could make each release include a link to all the relevant licenses.
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
Start by reading the linked janus issue 3229, then inspect how divviup-cli releases and container images are published. Identify the relevant license texts and artifact entry points before choosing whether releases should ship the files or link to them. Done means users can access all relevant licenses for each distributed binary and image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100