ietf-tools / ietf-tools/dev-planning-dispatch
Define what can be subscribed to
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
From the project notes on Feb 19, 2026:
- We WILL have subscriptions to:
- subseries (STD, BCP, etc)
- stream (IETF is huge, but other streams may be of interest)
- topic
- all new RFCs (email already exists)
- individual RFCs
- We will NOT have subscriptions to:
- new rfc from working group
- new rfc with this status
- new rfc from this area
Confirmed for the MVP: subscriptions are signed-in only. Subscribable entities: subseries (STD, BCP, …), stream, topic, all new RFCs, and individual RFCs. Explicitly out of scope: by working group, by status, and by area. This set drives the subscribe UI and the subscription-management API.
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 with the Feb 19, 2026 project notes, then trace the subscribe UI and subscription-management API entry points mentioned in the issue. Confirm how signed-in access and the five included subscribable entities are represented. Done means the UI and API follow the stated inclusions and exclude working group, status, and area subscriptions.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100