Define scope for w3c candidate recommendation
Open
Nobody has claimed this yet.
editors-agenda
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 194
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
The spec hasn't been evolving so rapidly in the past year and user agents are catching up on the implementation. This is probably a sign that we can move forward with candidate recommendation.
In order to do this, spec editors need to agree on the spec version for a candidate recommendation snapshot.
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
Start with the issue body and review the current WebCodecs specification and the user-agent implementation status it references. Determine which specification version could serve as the candidate recommendation snapshot and document the agreed scope. Done means the spec editors have agreed on both the snapshot version and its scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, web-dev
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100