theupdateframework / theupdateframework/specification
Properly describe hashed bin delegation in the specification
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 405
- Forks
- 59
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 1
Description
Hashed bin delegation is not well documented in the specification. One of the better/more frequently referenced descriptions is in PEP 458.
We might add this to the ~new repository operations section of the specification.
Originally posted by @joshuagl in https://github.com/theupdateframework/taps/pull/148#pullrequestreview-885846264
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 hashed bin delegation description in PEP 458 and reviewing the repository's new repository operations section. Determine how the behavior should be described in the specification, then update that section so hashed bin delegation is accurately and clearly documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100