theupdateframework / theupdateframework/specification
TUF metadata terminology pet peeves and rename suggestions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 405
- Forks
- 59
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 1
Description
Some of the terminology used in TUF metadata is not ideal. Given that no single rename justifies the consequential migration effort, this issue shall collect terminology pet peeves and rename suggestions (plus rationale), until we have accumulated enough to warrant a flag day...
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 issue #149 and its existing terminology pet peeves and rename suggestions. The issue does not identify files, tests, or a specific terminology change, and completion is not defined beyond collecting enough proposals to justify a future migration.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100