ietf-tools / ietf-tools/dev-planning-dispatch
define API for managing subscriptions
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Define the subscription-management API contract (agreed jointly with the Pink team). A signed-in user can list, add, and remove their subscriptions across the subscribable entity types (subseries, stream, topic, all-new, individual RFC). Agree auth (bearer access token), the entity/identifier scheme, payload shapes, and idempotent list/add/remove semantics. Red calls this API; Pink stores the subscriptions and sends the emails.
Contributor guide
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 from the issue text and map the five subscribable entity types, bearer-token authentication, identifier scheme, payload shapes, and list/add/remove semantics. Coordinate the contract with the Red and Pink teams; done means the API definition is jointly agreed, including idempotency and the boundary between calling and storage/email responsibilities.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100