Explicitly including reliability in scope
Open
Nobody has claimed this yet.
admin
- Dominant language
- HTML
- Stars
- 430
- Forks
- 81
- Avg merge
- 2h 50m
- Merged PRs (30d)
- 2
Description
There's no clear ownership for potential specifications/incubations around web reliability, such as Crash Reporting. There are already a couple areas owned by WebPerf WG (NEL and Reporting) that are more aligned with reliability than performance, and the scope of the charter should make that clear.
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
Locate the repository charter and review how NEL and Reporting are currently described, then compare that scope with the Crash Reporting example mentioned in the issue. Done means the charter clearly includes web reliability and makes ownership of related specifications or incubations explicit.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100