Consider documenting the path from standardization to incubation
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
For symmetry, have you considered documenting the transition of a specification from a Working Group to a Community Group?
If this direction would be well specified (signals to look for, policy/CLA considerations, etc.), I believe it might in fact encourage incubation efforts to transition to standardization in a timely manner knowing the conditions under which there's a path back to incubation within the W3C community.
I think this would help establish a CG <-> WG continuum and as such encourage broader participation in Working Groups when combined with the proposed Support for continued participation in a Working Group by CG contributors.
This would be especially helpful for Working Groups that have sister Community Groups that act as their domain-specific incubators (example) with good overlap in participation.
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 by reading proposals/continued-participation.md and the linked Web Machine Learning Community Group example to understand the existing participation context. The work is complete when the path from Working Group standardization to Community Group incubation is documented with the requested signals and policy or CLA considerations.
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
- Needs clarification
- Newbie friendliness
- 25/100