web-platform-tests / web-platform-tests/rfcs
Make a list of major stakeholders/users to notify
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 110
- Forks
- 90
- PR merge metrics
- No merged PRs in 30d
Description
In the wake of https://github.com/web-platform-tests/rfcs/pull/40#issuecomment-583661073 (no one recalled Bikeshed used the manifest, too), I think we should document some institutional knowledge, namely a list of major stakeholders/users of various components so that we can notify them of potential breaking changes.
Contributor guide
No contributing guide indexed for this repository
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 issue body and the linked RFC #40 discussion, especially the note about Bikeshed using the manifest. Identify the components and major stakeholders to document, then confirm that the resulting list would support notification of potential breaking changes.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100