ietf-tools / ietf-tools/dev-planning-dispatch
Define how we measure popularity
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Current proposal is to keep a short, fixed, manually managed list of "most popular" RFCs, created by periodically (weekly?) reviewing matomo, making a judgement call to discard obvious bot overload traffic. The resulting list can just be captured as json at the backend and that json served by the API.
Questions:
- are these in order or are they just "popular".
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
The issue names no files, tests, or entry points. Start by clarifying how Matomo traffic should be reviewed and filtered, whether the resulting RFC list is ordered, and how the manually maintained JSON should be served by the backend API; done means these decisions are documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- analytics, api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100