Content-derived resource IDs
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 70
- Forks
- 16
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 30
Description
https://github.com/ietf-wg-ppm/draft-ietf-ppm-dap/pull/781
Handle what wasn't already done for server-selected IDs. Audit all the HTTP Handlers.
Note that the spec also suggests aggregate-share ID == collection job ID.
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 draft-ietf-ppm-dap pull request and auditing all HTTP Handlers in the Janus repository. Identify which server-selected resource IDs remain unhandled, including the suggested aggregate-share ID and collection job ID relationship; done means the remaining handlers follow the specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100