theupdateframework / theupdateframework/specification
Clean-up/clarify how targets are fetched
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 405
- Forks
- 59
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 1
Description
5.7 Fetch target could do with some clarification improvements:
- 5.7.1. states what we are doing in all of 5.7
- 5.7.3. includes multiple actions in one step of the specification
The whole section lacks specificity in how the targets metadata are used when performing the required actions.
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 section 5.7, especially steps 5.7.1 and 5.7.3, in the linked specification. Clarify the scope of the section, separate the multiple actions in 5.7.3, and make the use of targets metadata during the required actions specific enough to follow.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100