Consider defining what a technical plenary is and setting requirements related to it
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 262
- Forks
- 194
- PR merge metrics
- No merged PRs in 30d
Description
(This is essentially the counterpoint to w3c/process#1094)
It's probably a bit surprising to a casual reader of the Process document that the concept of a technical plenary, or of TPAC, nowhere appears in the document. I suspect many members expect part of their annual dues to be used to fund W3C's premier annual event, so perhaps the Process document should make that expectation explicit.
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 by reading the W3C Process document and compare its treatment of technical plenaries and TPAC with the concerns in this issue and w3c/process#1094. The work is done when the document explicitly defines a technical plenary and states the related requirements or expectations.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100