theupdateframework / theupdateframework/taps
Discussion of Scale-out Architecture for High-volume Repositories TAP (TAP 21)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 37
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
TAP-21 originated with theupdateframework/specification/issues/309. Following discussion at the TUF community meeting on 2024-11-01, we've drafted TAP-21 and submitted a PR (#189).
In addition to broader discussions of TAP-21, we are specifically seeking feedback to:
- Validate our motivation and rationale
- Validate the calculations we undertook (See: TAP-21 metadata overhead calculator)
- Better understand how to approach the following sections (which are sparse, atm):
- Specification
- Backwards Compatibility
- Augmented Reference Implementation
We have thoughts on the sparse sections, but have not yet been able to articulate them clearly enough to include in the TAP.
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
Read the TAP-21 draft and linked PR #189 first, then review the motivation, rationale, and metadata overhead calculator. Focus discussion on the sparse Specification, Backwards Compatibility, and Augmented Reference Implementation sections; done means the proposal has validated calculations and clearer content for those sections.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100