ietf-tools / ietf-tools/dev-planning-dispatch
Define API for setting and retrieving ratings
Open
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 ratings API contract (agreed jointly with the Pink team):
- GET the aggregate rating for an RFC (public): average + count.
- GET the signed-in user's rating for an RFC (auth).
- PUT/POST the signed-in user's rating (auth), enforcing one per account (upsert).
Agree the auth mechanism (bearer access token), payload shapes, and logged-out behaviour. Part of the broader Pink-contract negotiation (no contract yet).
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 broader Pink-contract negotiation and agreeing the authentication mechanism, payload shapes, and logged-out behaviour; done means the ratings API contract is agreed for public aggregates and authenticated per-account upserts.
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
- Needs clarification
- Newbie friendliness
- 25/100