Community Group Program Community Group - Activity in 2026
No matches.
GitHub
w3c/cg-program
-
2 issues closed.
-
On handling the copyright statement in snapshots (of the 2026 redesign) w3c/cg-program#51.
-
Broken link on FAQ page w3c/cg-program#53.
-
-
5 issues received 10 new comments.
-
CG workflow as state machine with transitions w3c/cg-program#52 (5 comments by @elf-pavlik, @ianbjacobs)
-
Existing and potential new horizontal groups w3c/cg-program#54 (2 comments by @elf-pavlik, @ianbjacobs)
-
Make it easier for people not involved in W3C to join Community Group w3c/cg-program#17 (1 comment by @ianbjacobs)
-
On handling the copyright statement in snapshots (of the 2026 redesign) w3c/cg-program#51 (1 comment by @ianbjacobs)
-
Participants
-
1 participant joined.
-
Jennifer Strickland joined.
-
GitHub
w3c/cg-program
-
4 issues opened.
-
Existing and potential new horizontal groups w3c/cg-program#54, by @elf-pavlik.
-
Broken link on FAQ page w3c/cg-program#53, by @NoWorries.
-
CG workflow as state machine with transitions w3c/cg-program#52, by @elf-pavlik.
-
On handling the copyright statement in snapshots (of the 2026 redesign) w3c/cg-program#51, by @ianbjacobs.
-
GitHub
w3c/cg-program
-
1 issue closed.
-
What is the full lifecyle of a CG specification? w3c/cg-program#20.
-
-
1 issue received 1 new comment.
GitHub
w3c/cg-program
-
1 issue opened.
-
Community Group Notes w3c/cg-program#50, by @NiklasMerz.
-
-
2 issues closed.
-
Set "Move up or move out" expectation w3c/cg-program#22.
-
Community Group Notes w3c/cg-program#50.
-
-
3 issues received 4 new comments.
-
CG Draft maturity indicator should depend on maturity of draft's normative references w3c/cg-program#49 (1 comment by @ianbjacobs)
Participants
-
1 chair stepped down.
-
Dominique Hazaël-Massieux stepped down as a chair.
-
-
1 participant left.
-
Dominique Hazaël-Massieux (W3C) left.
-
GitHub
w3c/cg-program
-
1 issue opened.
-
CG Draft maturity indicator should depend on maturity of draft's normative references w3c/cg-program#49, by @elf-pavlik.
-
Participants
-
1 participant joined.
-
zanira maryam joined.
-
-
1 participant left.
-
Chris Wilson (Google LLC) left.
-
GitHub
w3c/cg-program
-
1 issue opened.
-
Simplify CG report creation from Github markdown document w3c/cg-program#48, by @dontcallmedom.
-
-
1 issue closed.
-
Contrast on section numbers of Table of Contents when hovering w3c/cg-program#44.
-
-
2 issues received 2 new comments.
-
Should we have a default license for software created by a CG w3c/cg-program#29 (1 comment by @ianbjacobs)
-
Contrast on section numbers of Table of Contents when hovering w3c/cg-program#44 (1 comment by @isaaclowe)
-
-
2 pull requests opened.
-
update assets to add dark mode support w3c/cg-program#47, by @deniak.
-
Stylesheet updates w3c/cg-program#46, by @deniak.
-
-
2 pull requests merged.
-
update assets to add dark mode support w3c/cg-program#47.
-
Stylesheet updates w3c/cg-program#46.
-
-
1 pull request closed.
-
editorial in changes section: report->specification w3c/cg-program#36.
-
Past meetings
GitHub
w3c/cg-program
-
1 issue opened.
-
Contrast on section numbers of Table of Contents when hovering w3c/cg-program#44, by @dontcallmedom.
-
-
1 issue received 1 new comment.
-
Contrast on section numbers of Table of Contents when hovering w3c/cg-program#44 (1 comment by @deniak)
-
-
8 pull requests opened.
-
Add link to MDN BCD in adopter guidance w3c/cg-program#45, by @dontcallmedom.
-
adding sentence to clarify that there's no endorsement from W3C w3c/cg-program#43, by @deniak.
-
Add dev signals from Chrome Platform Status w3c/cg-program#42, by @dontcallmedom.
-
Document the model behind implementation traction w3c/cg-program#41, by @dontcallmedom.
-
Add WebDX developer signals w3c/cg-program#40, by @dontcallmedom.
-
Mark a/b testing specs as robots-noindex w3c/cg-program#39, by @dontcallmedom.
-
Add more structure to implementation traction w3c/cg-program#38, by @dontcallmedom.
-
specs for A/B testing w3c/cg-program#37, by @deniak.
-
-
8 pull requests merged.
-
Add link to MDN BCD in adopter guidance w3c/cg-program#45.
-
Document the model behind implementation traction w3c/cg-program#41.
-
adding sentence to clarify that there's no endorsement from W3C w3c/cg-program#43.
-
Add dev signals from Chrome Platform Status w3c/cg-program#42.
-
Add WebDX developer signals w3c/cg-program#40.
-
Mark a/b testing specs as robots-noindex w3c/cg-program#39.
-
Add more structure to implementation traction w3c/cg-program#38.
-
specs for A/B testing w3c/cg-program#37.
-
-
7 pull requests received 56 new comments.
-
Document the model behind implementation traction w3c/cg-program#41 (14 comments by @cwilso, @deniak, @dontcallmedom, @ianbjacobs, @tidoust)
-
adding sentence to clarify that there's no endorsement from W3C w3c/cg-program#43 (2 comments by @ianbjacobs)
Past meetings
GitHub
w3c/cg-program
-
3 issues closed.
-
Suggestion for Community Group Reports w3c/cg-program#8.
-
Revisit copyright commitments for CGs w3c/cg-program#9.
-
Input from PDF to 3rd Sept meeting w3c/cg-program#31.
-
-
5 issues received 7 new comments.
-
Consider making WBS questionnaire more widely accessible to CGs w3c/cg-program#24 (2 comments by @csarven, @elf-pavlik)
-
1 pull request opened.
-
editorial in changes section: report->specification w3c/cg-program#36, by @tantek.
-
-
1 pull request received 1 new comment.
Participants
-
1 participant joined.
-
Seva Dolgopolov joined.
-
GitHub
w3c/cg-program
-
1 issue opened.
-
Using gh projects feat. for repos in @w3c-cg org w3c/cg-program#35, by @elf-pavlik.
-
-
2 issues closed.
-
Using gh projects feat. for repos in @w3c-cg org w3c/cg-program#35.
-
Not obvious how to leave a CG w3c/cg-program#34.
-
-
4 issues received 8 new comments.
-
Using gh projects feat. for repos in @w3c-cg org w3c/cg-program#35 (4 comments by @dontcallmedom, @elf-pavlik, @ianbjacobs)
-
Should we have a default license for software created by a CG w3c/cg-program#29 (1 comment by @ianbjacobs)
-