ietf-tools / ietf-tools/dev-planning-dispatch
Design API for telling red what notifications to provide on the website
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 on-site notifications API contract (agreed jointly with the Pink team): how Pink tells Red which notification items to surface to a signed-in user on the website (e.g. an RFC they follow was published, obsoleted, or made historic). Agree auth (bearer), item shape (id, type, subject, timestamp, link/target), list/fetch semantics, and read/seen state if any. Red consumes; Pink produces.
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
No files, tests, or entry points are named. Start by reviewing the proposed bearer-authenticated contract and coordinating the Red and Pink responsibilities; done means the notification item shape, list/fetch semantics, and any read or seen state are jointly agreed.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100