W3C Process Community Group - Activity in 2025
No matches.
Participants
-
1 chair appointed.
-
Brent Zundel became a chair.
-
-
1 chair stepped down.
-
Brent Zundel stepped down as a chair.
-
-
1 participant joined.
-
Brent Zundel (Yubico) joined.
-
-
1 participant left.
-
Brent Zundel (Yubico) left.
-
-
1 organization joined.
-
Yubico joined.
-
GitHub
w3c/process
-
1 pull request opened.
-
Adjust language for getting patent policy comittments from non-participants w3c/process#1129, by @frivoal.
-
-
1 pull request received 11 new comments.
-
Adjust language for getting patent policy comittments from non-participants w3c/process#1129 (11 comments by @frivoal, @nigelmegitt, @TallTed)
-
Participants
-
2 participants joined.
-
Isaac Moon joined.
-
Ege Korkan (Siemens AG) joined.
-
-
1 organization joined.
-
Siemens AG joined.
-
GitHub
w3c/process
-
1 issue opened.
-
Say something about the difference between a Note and a Note Draft w3c/process#1116, by @jyasskin.
-
-
1 issue received 2 new comments.
-
Say something about the difference between a Note and a Note Draft w3c/process#1116 (2 comments by @frivoal)
-
-
2 pull requests opened.
-
Initial commit w3c/process#1124, by @rankvnq001.
-
Add SLSA generic generator workflow w3c/process#1117, by @rankvnq001.
-
-
1 pull request closed.
-
Initial commit w3c/process#1124.
-
Past meetings
Participants
-
1 participant joined.
-
Jennifer Strickland joined.
-
-
1 participant left.
-
Jennifer Strickland left.
-
GitHub
w3c/process
-
1 issue opened.
-
Consider adoption of PR #1051 for the main branch w3c/process#1108, by @frivoal.
-
-
11 issues closed.
-
Glossaries: a different pattern needed? w3c/process#904.
-
Be consistent with terms "non-normative" and "informative" w3c/process#914.
-
Community and Business Groups w3c/process#326.
-
Ambiguity in many voting rules w3c/process#933.
-
Mathematical Error in Composition of the AB section w3c/process#942.
-
Change participation requirements for editors w3c/process#948.
-
Exclusion Documents can be Recommendations, not just Drafts w3c/process#963.
-
Clarify that removal from AB/TAG does not affect councils once formed w3c/process#1006.
-
inconsistent terms for the 'Note' document type w3c/process#1064.
-
30 issues received 69 new comments.
-
Should the process include something about Testing? w3c/process#157 (8 comments by @brentzundel, @fantasai, @hober, @michaelchampion, @nigelmegitt)
-
Have the normal, default, decision policy for charters in the process w3c/process#425 (5 comments by @chrisn, @frivoal, @svgeesus)
-
Be consistent with terms "non-normative" and "informative" w3c/process#914 (5 comments by @brentzundel, @frivoal, @TallTed)
-
Exclusion Documents can be Recommendations, not just Drafts w3c/process#963 (4 comments by @brentzundel, @frivoal, @ID-iot-git, @svgeesus)
-
inconsistent terms for the 'Note' document type w3c/process#1064 (4 comments by @brentzundel, @frivoal)
-
Community Groups and Business Groups should be incorporated into the Process w3c/process#409 (3 comments by @css-meeting-bot, @frivoal, @TallTed)
-
The 2021 "Revising a Recommendation Process" is painful for WGs w3c/process#589 (2 comments by @css-meeting-bot, @TallTed)
-
Proposed addition to "9. Liaisons" to address delays in PAS Submissions to ISO w3c/process#946 (2 comments by @brentzundel, @frivoal)
-
Mathematical Error in Composition of the AB section w3c/process#942 (2 comments by @brentzundel, @frivoal)
-
Clarify that removal from AB/TAG does not affect councils once formed w3c/process#1006 (2 comments by @brentzundel, @frivoal)
-
What happens in Council votes when two members share the same affiliation? w3c/process#1018 (2 comments by @brentzundel, @frivoal)
-
6.3.12.2. Rescinding a Candidate Recommendation lacks good context w3c/process#1014 (2 comments by @frivoal, @nigelmegitt)
-
Require registries to include "enough" standardized entries w3c/process#597 (1 comment by @css-meeting-bot)
-
Organisation of 3.4 "Chartered Groups: Working Groups and Interest Groups" w3c/process#554 (1 comment by @css-meeting-bot)
-
[patent policy] Exclusion opportunity when work leaves a Working Group w3c/process#518 (1 comment by @brentzundel)
-
Suboptimal wording about "License Grants from Non-Participants" w3c/process#903 (1 comment by @brentzundel)
-
-
2 pull requests merged.
-
Constrain requests to fill vacated seats more precisely. w3c/process#1038.
-
Handle votes by >2 council members from the same affiliation w3c/process#1047.
-
-
1 pull request closed.
-
Extent excessively short terms w3c/process#1044.
-
-
8 pull requests received 10 new comments.
-
Generalizing AC Appeals and using this procedure for recall. w3c/process#888 (1 comment by @ID-iot-git)
-
Removal from AB/TAG does not impact Council membership #1006 w3c/process#1028 (1 comment by @frivoal)
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Lorenzo Lomartire joined.
-
-
1 participant left.
-
FELIPE Reviriego Calatrava left.
-
GitHub
w3c/process
-
7 issues opened.
-
Define new class of WG/IG participants for representing a non-Member company w3c/process#1105, by @fantasai.
-
State the purpose of AC meetings w3c/process#1096, by @hober.
-
Consider defining what a technical plenary is and setting requirements related to it w3c/process#1095, by @hober.
-
Consider dropping the entire section on AC meetings w3c/process#1094, by @hober.
-
Alternate AC Reps should always be allowed to attend the AC meeting w3c/process#1092, by @hober.
-
-
1 issue closed.
-
11 issues received 35 new comments.
-
Reconsider requirement for AC meetings to be face-to-face w3c/process#1084 (8 comments by @frivoal, @hober, @michaelchampion, @nigelmegitt, @reidmore-online)
-
Alternate AC Reps should always be allowed to attend the AC meeting w3c/process#1092 (5 comments by @chaals, @cwilso, @hober)
-
Reconsider, and perhaps combine, the definitions of "face-to-face meeting" and "distributed meeting" in §3.1.2. Meetings w3c/process#1093 (5 comments by @fantasai, @npdoty, @reidmore-online)
-
Enumerate the requirements for wide review w3c/process#130 (4 comments by @beedell-roke, @frivoal, @tidoust)
-
Ambiguity for Registries before reaching W3C Registry Status w3c/process#1085 (3 comments by @egekorkan, @nigelmegitt)
-
Ambiguity in new features for registries versus recommentations w3c/process#1073 (2 comments by @nigelmegitt, @plehegar)
-
Consider defining what a technical plenary is and setting requirements related to it w3c/process#1095 (2 comments by @chaals, @hober)
-
Consider dropping the entire section on AC meetings w3c/process#1094 (2 comments by @cwilso, @hober)
-
Consider normalizing the advance notice requirements between the AC meeting and all other kinds of meetings w3c/process#1091 (1 comment by @fantasai)
-
-
7 pull requests merged.
-
TAG/AB and CEO removal integration (Second Draft) w3c/process#1052.
-
Give the Chair suspension powers for emergencies w3c/process#1051.
-
Generalizing AC Appeals and using this procedure for recall. w3c/process#888.
-
Require attempted remediation before removal from the AB or TAG. w3c/process#1050.
-
Define removal hearings as private, and removal votes by secret ballot. w3c/process#1049.
-
Update link about HR Groups w3c/process#1083.
-
-
2 pull requests closed.
-
Require resignation from AB/TAG/BoD as a condition of service w3c/process#928.
-
Forbid the Team from AB/TAG service w3c/process#929.
-
-
8 pull requests received 11 new comments.
-
More explicitly allow removal of AB/TAG members for violation of the Code of Conduct w3c/process#1048 (2 comments by @frivoal)
-
Generalizing AC Appeals and using this procedure for recall. w3c/process#888 (1 comment by @frivoal)
-
Require attempted remediation before removal from the AB or TAG. w3c/process#1050 (1 comment by @frivoal)
-
Define removal hearings as private, and removal votes by secret ballot. w3c/process#1049 (1 comment by @frivoal)
-
Require resignation from AB/TAG/BoD as a condition of service w3c/process#928 (1 comment by @brentzundel)
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
François Daoust (W3C) joined.
-
-
3 participants left.
-
Tim Berners-Lee (W3C) left.
-
Sam Sneddon (Apple Inc.) left.
-
Elika Etemad (Apple Inc.) left.
-
GitHub
w3c/process
-
3 issues opened.
-
Ambiguity for Registries before reaching W3C Registry Status w3c/process#1085, by @egekorkan.
-
Reconsider requirement for AC meetings to be face-to-face w3c/process#1084, by @hober.
-
-
1 issue closed.
-
Approval Vote Experiment Questions w3c/process#521.
-
-
7 issues received 13 new comments.
-
Forbid holding multiple leadership positions w3c/process#921 (4 comments by @brentzundel, @cwilso, @martinthomson)
-
Missing requirement for "adequate implementation experience" plan in revised CR Snapshots w3c/process#1082 (2 comments by @jyasskin, @plehegar)
-
Link for "W3C Horizontal Groups" doesn't describe W3C horizontal groups w3c/process#769 (2 comments by @plehegar)
-
Member submissions: can anyone else object, and if so, can they object to acceptance? w3c/process#639 (1 comment by @brentzundel)
-
"Candidate Recommendation" is no longer an accurate term w3c/process#402 (1 comment by @css-meeting-bot)
-
-
1 pull request opened.
-
Update link about HR Groups w3c/process#1083, by @frivoal.
-
-
3 pull requests received 3 new comments.
-
Generalizing AC Appeals and using this procedure for recall. w3c/process#888 (1 comment by @brentzundel)
-
Require resignation from AB/TAG/BoD as a condition of service w3c/process#928 (1 comment by @css-meeting-bot)
-
Past meetings
-
1 meeting.
Participants
-
1 chair appointed.
-
Brent Zundel became a chair.
-
-
1 chair stepped down.
-
Elika Etemad stepped down as a chair.
-
-
1 participant left.
-
Nora R left.
-
GitHub
w3c/process
-
1 pull request opened.
-
Editorial reorg of text defining REC track statuses w3c/process#1079, by @frivoal.
-
-
3 pull requests merged.
-
Editorial reorg of text defining REC track statuses w3c/process#1079.
-
Editorial tweaks ac review w3c/process#1074.
-
Fix typo: teaks -> tweaks w3c/process#1075.
-
-
2 pull requests closed.
-
4 pull requests received 18 new comments.
-
Editorial reorg of text defining REC track statuses w3c/process#1079 (5 comments by @css-meeting-bot, @frivoal, @jyasskin, @TallTed)
-
Synchronize Advisory Committee representative and Consortium Member Representative w3c/process#937 (5 comments by @frivoal, @TallTed)
-
Fix typo: teaks -> tweaks w3c/process#1075 (3 comments by @css-meeting-bot, @daniel-montalvo, @plehegar)
-
Past meetings
Participants
-
3 participants joined.
-
Alan Law (TheChineseWriter Limited) joined.
-
Hidde de Vries (Logius) joined.
-
Brent Zundel (Yubico) joined.
-
-
1 participant left.
-
Léonie Watson (TetraLogical Services Ltd) left.
-
-
2 organizations joined.
-
TheChineseWriter Limited joined.
-
Logius joined.
-
-
1 organization left.
-
TetraLogical Services Ltd left.
-
GitHub
w3c/process
-
2 issues opened.
-
Ambiguity in new features for registries versus recommentations w3c/process#1073, by @astearns.
-
-
4 issues closed.
-
Republishing a CR Snapshot in order to start the AC Review w3c/process#1063.
-
Multi-point Multi-FO Councils w3c/process#1041.
-
Feedback on Charter refinement draft text w3c/process#934.
-
-
3 issues reopened.
-
inconsistent terms for the 'Note' document type w3c/process#1064, by @frivoal.
-
Multi-point Multi-FO Councils w3c/process#1041, by @frivoal.
-
inconsistent terms for the 'Note' document type w3c/process#1064, by @koalie.
-
-
6 issues received 32 new comments.
-
Use “Staff Contact” instead of “Team Contact” consistently in communications with external audiences w3c/process#1066 (13 comments by @fantasai, @frivoal, @ianbjacobs, @jean-gui, @koalie, @plehegar, @svgeesus, @vivienlacourba)
-
inconsistent terms for the 'Note' document type w3c/process#1064 (8 comments by @css-meeting-bot, @frivoal, @koalie, @xueyuanjia)
-
Republishing a CR Snapshot in order to start the AC Review w3c/process#1063 (6 comments by @css-meeting-bot, @frivoal, @plehegar)
-
Ambiguity in new features for registries versus recommentations w3c/process#1073 (2 comments by @astearns, @frivoal)
-
-
9 pull requests opened.
-
Fix typo: teaks -> tweaks w3c/process#1075, by @daniel-montalvo.
-
Editorial tweaks ac review w3c/process#1074, by @frivoal.
-
Correct council text pertaining to multiple objections / decisions w3c/process#1072, by @frivoal.
-
Create jekyll-docker.yml w3c/process#1071, by @Eriddle96.
-
Allow transition to REC from CRD in certain cases w3c/process#1070, by @frivoal.
-
Explain the reasons for the Council confidentiality requirements w3c/process#1069, by @fantasai.
-
Rename "Team Contact" into "Staff Contact" w3c/process#1068, by @frivoal.
-
Drop legacy aliases for Group Note from the definition w3c/process#1067, by @frivoal.
-
Remove a stray emdash. w3c/process#1065, by @jyasskin.
-
-
8 pull requests merged.
-
Allow transition to REC from CRD in certain cases w3c/process#1070.
-
Correct council text pertaining to multiple objections / decisions w3c/process#1072.
-
Explain the reasons for the Council confidentiality requirements w3c/process#1069.
-
Clarify council text in case of multiple objections to a single decision w3c/process#1045.
-
Clarify timing of Council being convened w3c/process#1046.
-
Rename "Team Contact" into "Staff Contact" w3c/process#1068.
-
Drop legacy aliases for Group Note from the definition w3c/process#1067.
-
Remove a stray emdash. w3c/process#1065.
-
-
1 pull request closed.
-
Create jekyll-docker.yml w3c/process#1071.
-
-
10 pull requests received 50 new comments.
-
Correct council text pertaining to multiple objections / decisions w3c/process#1072 (12 comments by @fantasai, @frivoal, @nigelmegitt)
-
Give the Chair suspension powers for emergencies w3c/process#1051 (12 comments by @css-meeting-bot, @fantasai, @frivoal, @ianbjacobs, @nigelmegitt, @TzviyaSiegman)
-
Allow transition to REC from CRD in certain cases w3c/process#1070 (9 comments by @fantasai, @frivoal, @nigelmegitt)
-
TAG/AB and CEO removal integration (Second Draft) w3c/process#1052 (6 comments by @fantasai, @frivoal, @nigelmegitt)
-
Clarify timing of Council being convened w3c/process#1046 (3 comments by @css-meeting-bot, @TallTed)
-
Handle votes by >2 council members from the same affiliation w3c/process#1047 (2 comments by @cwilso, @frivoal)
-
Explain the reasons for the Council confidentiality requirements w3c/process#1069 (2 comments by @css-meeting-bot, @fantasai)
-
Clarify council text in case of multiple objections to a single decision w3c/process#1045 (2 comments by @chrisn, @fantasai)
-
Past meetings
-
1 meeting.
Participants
-
3 participants left.
-
Benjamin Goering (Protocol Labs) left.
-
Natasha Rooney (GSMA) left.
-
Chris O'Brien (Apple Inc.) left.
-
-
2 organizations left.
-
Protocol Labs left.
-
GSMA left.
-
GitHub
w3c/process
-
3 issues opened.
-
inconsistent terms for the 'Note' document type w3c/process#1064, by @xueyuanjia.
-
Republishing a CR Snapshot in order to start the AC Review w3c/process#1063, by @plehegar.
-
Multi-point Multi-FO Councils w3c/process#1041, by @fantasai.
-
-
5 issues closed.
-
Do we need a no-change publication? w3c/process#1013.
-
Confusing wording wrt adding new features to RECs w3c/process#1004.
-
Charter Refinement and Rechartering w3c/process#1024.
-
Clean up 3-way decision w3c/process#1009.
-
11 issues received 32 new comments.
-
Clarify that removal from AB/TAG does not affect councils once formed w3c/process#1006 (8 comments by @chaals, @fantasai, @frivoal, @hober, @nigelmegitt)
-
Multi-point Multi-FO Councils w3c/process#1041 (6 comments by @css-meeting-bot, @dwsinger, @frivoal, @nigelmegitt)
-
Glossaries: a different pattern needed? w3c/process#904 (5 comments by @frivoal, @hober, @nigelmegitt)
-
inconsistent terms for the 'Note' document type w3c/process#1064 (2 comments by @frivoal, @plehegar)
-
What happens in Council votes when two members share the same affiliation? w3c/process#1018 (2 comments by @css-meeting-bot, @fantasai)
-
Automatic Extension of Nomination Period due to Insufficient Candidates w3c/process#949 (1 comment by @fantasai)
-
Republishing a CR Snapshot in order to start the AC Review w3c/process#1063 (1 comment by @plehegar)
-
-
11 pull requests opened.
-
TAG/AB and CEO removal integration (Second Draft) w3c/process#1052, by @frivoal.
-
Give the Chair suspension powers for emergencies w3c/process#1051, by @frivoal.
-
Require attempted remediation before removal from the AB or TAG. w3c/process#1050, by @frivoal.
-
Define removal hearings as private, and removal votes by secret ballot. w3c/process#1049, by @frivoal.
-
More explicitly allow removal of AB/TAG members for violation of the Code of Conduct w3c/process#1048, by @frivoal.
-
Handle votes by >2 council members from the same affiliation w3c/process#1047, by @frivoal.
-
Clarify timing of Council being convened w3c/process#1046, by @frivoal.
-
Clarify council text in case of multiple objections to a single decision w3c/process#1045, by @frivoal.
-
Extent excessively short terms w3c/process#1044, by @frivoal.
-
Drop expectation to republish document when there are no changes w3c/process#1043, by @frivoal.
-
Better define major/minor charter changes w3c/process#1042, by @frivoal.
-
-
3 pull requests merged.
-
Drop expectation to republish document when there are no changes w3c/process#1043.
-
Better define major/minor charter changes w3c/process#1042.
-
Tweaks to how charter refinement concludes w3c/process#1037.
-
-
1 pull request closed.
-
Reworking TAG/AB disciplinary removal w3c/process#1036.
-
-
13 pull requests received 78 new comments.
-
Reworking TAG/AB disciplinary removal w3c/process#1036 (21 comments by @chrisn, @cwilso, @fantasai, @frivoal, @martinthomson, @nigelmegitt, @plehegar)
-
Give the Chair suspension powers for emergencies w3c/process#1051 (15 comments by @chaals, @chrisn, @fantasai, @nigelmegitt, @TallTed)
-
Handle votes by >2 council members from the same affiliation w3c/process#1047 (10 comments by @chrisn, @fantasai, @frivoal, @nigelmegitt, @TallTed)
-
Better define major/minor charter changes w3c/process#1042 (8 comments by @css-meeting-bot, @cwilso, @frivoal, @nigelmegitt, @plehegar)
-
Clarify council text in case of multiple objections to a single decision w3c/process#1045 (7 comments by @chaals, @chrisn, @nigelmegitt, @TallTed)
-
Extent excessively short terms w3c/process#1044 (5 comments by @chaals, @cwilso, @fantasai, @frivoal)
-
TAG/AB and CEO removal integration (Second Draft) w3c/process#1052 (2 comments by @fantasai, @nigelmegitt)
-
Tweaks to how charter refinement concludes w3c/process#1037 (2 comments by @css-meeting-bot, @tantek)
-
Constrain requests to fill vacated seats more precisely. w3c/process#1038 (1 comment by @css-meeting-bot)
-
More explicitly allow removal of AB/TAG members for violation of the Code of Conduct w3c/process#1048 (1 comment by @nigelmegitt)
-
Generalizing AC Appeals and using this procedure for recall. w3c/process#888 (1 comment by @frivoal)
-
Past meetings
-
1 meeting.
Participants
-
1 participant left.
-
Wendy Reid (Rakuten Group, Inc.) left.
-
GitHub
w3c/process
-
6 issues opened.
-
Easy to Read in Accessibility of machine learning and generative AI w3c/process#1035, by @LuisMalhadas.
-
Time limits on AC Appeal process w3c/process#1034, by @martinthomson.
-
Special rules for excessively short terms w3c/process#1033, by @fantasai.
-
When does a Council publish its report? w3c/process#1029, by @fantasai.
-
Charter Refinement and Rechartering w3c/process#1024, by @fantasai.
-
What happens in Council votes when two members share the same affiliation? w3c/process#1018, by @TallTed.
-
-
2 issues closed.
-
Easy to Read in Accessibility of machine learning and generative AI w3c/process#1035.
-
-
1 issue reopened.
-
Be consistent with terms "non-normative" and "informative" w3c/process#914, by @frivoal.
-
-
8 issues received 29 new comments.
-
Easy to Read in Accessibility of machine learning and generative AI w3c/process#1035 (9 comments by @frivoal, @LuisMalhadas, @nigelmegitt)
-
When does a Council publish its report? w3c/process#1029 (5 comments by @fantasai, @hober, @jyasskin, @nigelmegitt, @npdoty)
-
Recall procedures for TAG and AB w3c/process#882 (5 comments by @chaals, @dbaron, @fantasai, @frivoal)
-
Time limits on AC Appeal process w3c/process#1034 (3 comments by @fantasai, @frivoal, @martinthomson)
-
Adjust AC appeal vote threshold based on participation w3c/process#886 (3 comments by @frivoal, @martinthomson)
-
What happens in Council votes when two members share the same affiliation? w3c/process#1018 (2 comments by @frivoal, @nigelmegitt)
-
-
10 pull requests opened.
-
Constrain requests to fill vacated seats more precisely. w3c/process#1038, by @jyasskin.
-
Tweaks to how charter refinement concludes w3c/process#1037, by @frivoal.
-
Reworking TAG/AB disciplinary removal w3c/process#1036, by @fantasai.
-
Removal from AB/TAG does not impact Council membership #1006 w3c/process#1028, by @fantasai.
-
Removal hearings are held by the group, not the chair. w3c/process#1027, by @fantasai.
-
Fix confusing wording wrt adding new features to RECs #1004 w3c/process#1026, by @fantasai.
-
Clarify role of the chair w3c/process#1025, by @fantasai.
-
Notify the AC when an AB or TAG member is removed. w3c/process#1023, by @fantasai.
-
[editorial] Collapse some wording wrt Council formation. w3c/process#1022, by @fantasai.
-
Give the Advisory Board a mission statement w3c/process#1021, by @fantasai.
-
-
11 pull requests merged.
-
[editorial] Collapse some wording wrt Council formation. w3c/process#1022.
-
Clean up 3-way decision w3c/process#1012.
-
Clarify role of the chair w3c/process#1025.
-
Refine Expiration of Charter Refinement w3c/process#1011.
-
Move details of how the Team evaluates charters to the guide w3c/process#1000.
-
Fix confusing wording wrt adding new features to RECs #1004 w3c/process#1026.
-
Removal from AB/TAG does not impact Council membership #1006 w3c/process#1028.
-
Removal hearings are held by the group, not the chair. w3c/process#1027.
-
Notify the AC when an AB or TAG member is removed. w3c/process#1023.
-
Make cross reference more obvious w3c/process#1010.
-
chore: replace informative with non-normative for consistency w3c/process#1015.
-
-
1 pull request closed.
-
Fixes some mistakes w3c/process#1017.
-
-
15 pull requests received 143 new comments.
-
Generalizing AC Appeals and using this procedure for recall. w3c/process#888 (39 comments by @cwilso, @fantasai, @frivoal, @hober, @jyasskin, @martinthomson, @TallTed)
-
Give the Advisory Board a mission statement w3c/process#1021 (18 comments by @frivoal, @hober, @nigelmegitt, @TallTed, @tantek)
-
Reworking TAG/AB disciplinary removal w3c/process#1036 (16 comments by @cwilso, @fantasai, @TallTed, @wareid)
-
Clean up 3-way decision w3c/process#1012 (8 comments by @css-meeting-bot, @fantasai, @frivoal, @plehegar, @TallTed)
-
Fix confusing wording wrt adding new features to RECs #1004 w3c/process#1026 (5 comments by @css-meeting-bot, @fantasai, @nigelmegitt, @tantek)
-
[editorial] Collapse some wording wrt Council formation. w3c/process#1022 (3 comments by @css-meeting-bot, @frivoal)
-
Move details of how the Team evaluates charters to the guide w3c/process#1000 (3 comments by @css-meeting-bot, @fantasai, @ianbjacobs)
-
chore: replace informative with non-normative for consistency w3c/process#1015 (1 comment by @frivoal)
-
Past meetings
Participants
-
2 participants joined.
-
Sam O'Hara joined.
-
Jill Schmidt (Apple Inc.) joined.
-
GitHub
w3c/process
-
7 issues opened.
-
6.3.12.2. Rescinding a Candidate Recommendation lacks good context w3c/process#1014, by @fantasai.
-
Do we need a no-change publication? w3c/process#1013, by @fantasai.
-
Clean up 3-way decision w3c/process#1009, by @frivoal.
-
More explicitly connect ability to revise a REC to section detailing the process. w3c/process#1008, by @fantasai.
-
Who is in a removal hearing? Is it publicized? w3c/process#1007, by @frivoal.
-
Clarify that removal from AB/TAG does not affect councils once formed w3c/process#1006, by @frivoal.
-
Confusing wording wrt adding new features to RECs w3c/process#1004, by @fantasai.
-
-
1 issue closed.
-
URIs to W3C Process and Patent Policy docs w3c/process#962.
-
-
7 issues received 16 new comments.
-
Confusing wording wrt adding new features to RECs w3c/process#1004 (6 comments by @fantasai, @frivoal, @nigelmegitt, @TallTed)
-
URIs to W3C Process and Patent Policy docs w3c/process#962 (3 comments by @frivoal, @plehegar, @vivienlacourba)
-
Clarify that removal from AB/TAG does not affect councils once formed w3c/process#1006 (3 comments by @fantasai, @nigelmegitt, @TallTed)
-
6.3.12.2. Rescinding a Candidate Recommendation lacks good context w3c/process#1014 (1 comment by @frivoal)
-
More explicitly connect ability to revise a REC to section detailing the process. w3c/process#1008 (1 comment by @frivoal)
-
-
16 pull requests opened.
-
Fixes some mistakes w3c/process#1017, by @Bashamega.
-
(Editorial) Typo fix w3c/process#1016, by @ianbjacobs.
-
chore: replace informative with non-normative for consistency w3c/process#1015, by @Bashamega.
-
Clean up 3-way decision w3c/process#1012, by @frivoal.
-
Refine Expiration of Charter Refinement w3c/process#1011, by @frivoal.
-
Make cross reference more obvious w3c/process#1010, by @frivoal.
-
Reframe the various kinds of Objection handling for charter refinement w3c/process#1005, by @frivoal.
-
Facilitator not explicitly chair w3c/process#1002, by @frivoal.
-
Drop wide review of charters from the Process w3c/process#1001, by @frivoal.
-
Move details of how the Team evaluates charters to the guide w3c/process#1000, by @frivoal.
-
Drop unnecessary detail w3c/process#999, by @frivoal.
-
Drop unnecessary remarks about optional communication w3c/process#998, by @frivoal.
-
Allow Team to step in when consensus cannot be found during Charter Refinement. w3c/process#997, by @fantasai.
-
Give some details about DoCs in charter refinement w3c/process#996, by @frivoal.
-
Require Team to reply with rationale for rejection w3c/process#995, by @frivoal.
-
Pick a number of weeks w3c/process#994, by @frivoal.
-
-
9 pull requests merged.
-
(Editorial) Typo fix w3c/process#1016.
-
Drop unnecessary remarks about optional communication w3c/process#998.
-
Enable AB/TAG to remove one of their members w3c/process#986.
-
Reframe the various kinds of Objection handling for charter refinement w3c/process#1005.
-
Facilitator not explicitly chair w3c/process#1002.
-
Improve markup/typography w3c/process#988.
-
Pick a number of weeks w3c/process#994.
-
Require Team to reply with rationale for rejection w3c/process#995.
-
Give some details about DoCs in charter refinement w3c/process#996.
-
-
3 pull requests closed.
-
Drop unnecessary detail w3c/process#999.
-
Drop wide review of charters from the Process w3c/process#1001.
-
-
16 pull requests received 86 new comments.
-
Enable AB/TAG to remove one of their members w3c/process#986 (15 comments by @css-meeting-bot, @cwilso, @fantasai, @frivoal, @koalie, @nigelmegitt, @plehegar, @swickr, @wareid)
-
Drop wide review of charters from the Process w3c/process#1001 (8 comments by @chaals, @css-meeting-bot, @fantasai, @ianbjacobs, @nigelmegitt, @plehegar, @TallTed)
-
chore: replace informative with non-normative for consistency w3c/process#1015 (7 comments by @Bashamega, @frivoal, @nigelmegitt, @TallTed)
-
Move details of how the Team evaluates charters to the guide w3c/process#1000 (4 comments by @fantasai, @frivoal, @TallTed)
-
Refine Expiration of Charter Refinement w3c/process#1011 (3 comments by @frivoal, @ianbjacobs, @TallTed)
-
Facilitator not explicitly chair w3c/process#1002 (3 comments by @css-meeting-bot, @frivoal, @ianbjacobs)
-
Allow Team to step in when consensus cannot be found during Charter Refinement. w3c/process#997 (2 comments by @frivoal, @ianbjacobs)
-
Drop unnecessary remarks about optional communication w3c/process#998 (2 comments by @css-meeting-bot, @fantasai)
-
Reframe the various kinds of Objection handling for charter refinement w3c/process#1005 (2 comments by @css-meeting-bot, @ianbjacobs)
-
Give some details about DoCs in charter refinement w3c/process#996 (2 comments by @css-meeting-bot, @ianbjacobs)
-
Require Team to reply with rationale for rejection w3c/process#995 (2 comments by @css-meeting-bot, @ianbjacobs)
Past meetings
Participants
-
1 participant joined.
-
Victor Lu joined.
-
-
1 participant left.
-
Vartika Pandey left.
-
GitHub
w3c/process
-
1 issue opened.
-
Update Process Document's abstract to match current languague for W3C Mission w3c/process#989, by @koalie.
-
-
3 issues closed.
-
Abandoning Charter Refinement should require Team to agree w3c/process#982.
-
Mention of dissent in recommendation resolution is unclear w3c/process#978.
-
6 issues received 13 new comments.
-
Update Process Document's abstract to match current languague for W3C Mission w3c/process#989 (4 comments by @css-meeting-bot, @fantasai, @koalie)
-
Incumbent bias in elections / impose term limits? w3c/process#697 (4 comments by @frivoal, @martinthomson, @mnot)
-
“Tooling for Discussions and Publications” should be “Tooling and Archiving for Discussions and Publications w3c/process#736 (1 comment by @jc23H2)
-
-
8 pull requests opened.
-
Phrasing / framing improvements on Chartering w3c/process#993, by @frivoal.
-
Enable members to push for resuming an abandoned charter refinement w3c/process#992, by @frivoal.
-
Use appeal vote as escalation path for rejecting charter refinement w3c/process#991, by @frivoal.
-
Update mission w3c/process#990, by @chaals.
-
Improve markup/typography w3c/process#988, by @frivoal.
-
Handle FOs, not mere dissent, after a REC's AC Review w3c/process#987, by @frivoal.
-
Enable AB/TAG to remove one of their members w3c/process#986, by @frivoal.
-
-
7 pull requests merged.
-
Update mission w3c/process#990.
-
Phrasing / framing improvements on Chartering w3c/process#993.
-
Enable members to push for resuming an abandoned charter refinement w3c/process#992.
-
Use appeal vote as escalation path for rejecting charter refinement w3c/process#991.
-
Handle FOs, not mere dissent, after a REC's AC Review w3c/process#987.
-
-
1 pull request closed.
-
Rationalize/streamline/modernize some core terminology w3c/process#883.
-
-
6 pull requests received 37 new comments.
-
Generalizing AC Appeals and using this procedure for recall. w3c/process#888 (27 comments by @cwilso, @frivoal, @martinthomson, @TallTed, @wareid)
-
Handle FOs, not mere dissent, after a REC's AC Review w3c/process#987 (3 comments by @frivoal, @TallTed)
-
Enable members to push for resuming an abandoned charter refinement w3c/process#992 (1 comment by @css-meeting-bot)
-
Use appeal vote as escalation path for rejecting charter refinement w3c/process#991 (1 comment by @css-meeting-bot)
-
Past meetings
Participants
-
1 participant joined.
-
Vartika Pandey joined.
-
GitHub
w3c/process
-
4 issues opened.
-
Abandoning Charter Refinement should require Team to agree w3c/process#982, by @fantasai.
-
Mention of dissent in recommendation resolution is unclear w3c/process#978, by @wareid.
-
Verification of charter refinement w3c/process#971, by @frivoal.
-
Can the Chartering Facilitator be replaced? w3c/process#969, by @frivoal.
-
-
9 issues closed.
-
Open up Registries to IG, TAG, AB w3c/process#902.
-
ambiguous statement for proxy in WG/IG w3c/process#373.
-
The Team should be able to initiate AC Review of charter draft w3c/process#959.
-
Can the Chartering Facilitator be replaced? w3c/process#969.
-
Verification of charter refinement w3c/process#971.
-
Good standing w3c/process#935.
-
Veto by inaction w3c/process#778.
-
-
11 issues received 17 new comments.
-
Glossaries: a different pattern needed? w3c/process#904 (3 comments by @chaals, @frivoal, @plehegar)
-
Abandoning Charter Refinement should require Team to agree w3c/process#982 (2 comments by @css-meeting-bot, @frivoal)
-
Mention of dissent in recommendation resolution is unclear w3c/process#978 (2 comments by @frivoal, @wareid)
-
Have the normal, default, decision policy for charters in the process w3c/process#425 (2 comments by @frivoal, @nigelmegitt)
-
Can the Chartering Facilitator be replaced? w3c/process#969 (2 comments by @css-meeting-bot, @plehegar)
-
The Team should be able to initiate AC Review of charter draft w3c/process#959 (1 comment by @frivoal)
-
Council Composition requirements include Tim Berners-Lee, TAG life member w3c/process#784 (1 comment by @frivoal)
-
-
7 pull requests opened.
-
Require decision by both the facilitator and team to abandon chartering w3c/process#983, by @frivoal.
-
Update links to the Guidebook following its redesign w3c/process#979, by @vivienlacourba.
-
Call out that the Team can share its views on proposals under AC review w3c/process#975, by @frivoal.
-
Chartering Facilitators are appointed by the Team, and can be replaced w3c/process#974, by @frivoal.
-
Add explicit Team verification of charter refinement w3c/process#973, by @frivoal.
-
Extend the ability to publish Registries to IG/AB/TAG w3c/process#972, by @frivoal.
-
Enable the Team (as well as the Group) to push charters forward w3c/process#970, by @frivoal.
-
-
9 pull requests merged.
-
Extend the ability to publish Registries to IG/AB/TAG w3c/process#972.
-
Update links to the Guidebook following its redesign w3c/process#979.
-
Limit the involvement of Tim Berners-Lee to the TAG proper w3c/process#792.
-
Add explicit Team verification of charter refinement w3c/process#973.
-
Be more specific about when the council composition is locked down w3c/process#955.
-
Enable the Team (as well as the Group) to push charters forward w3c/process#970.
-
Decrease emphasis on FO to charter rejection w3c/process#964.
-
-
2 pull requests closed.
-
short-circuit drop Team-related votes w3c/process#906.
-
Adjust the status of Tim Berners-Lee in the TAG w3c/process#791.
-
-
9 pull requests received 58 new comments.
-
Extend the ability to publish Registries to IG/AB/TAG w3c/process#972 (31 comments by @fantasai, @frivoal, @nigelmegitt, @TallTed)
-
Generalizing AC Appeals and using this procedure for recall. w3c/process#888 (11 comments by @frivoal, @martinthomson, @TallTed)
-
Be more specific about when the council composition is locked down w3c/process#955 (7 comments by @frivoal, @TallTed)
-
Chartering Facilitators are appointed by the Team, and can be replaced w3c/process#974 (4 comments by @fantasai, @frivoal, @TallTed)
-
Require decision by both the facilitator and team to abandon chartering w3c/process#983 (1 comment by @TallTed)
-
Call out that the Team can share its views on proposals under AC review w3c/process#975 (1 comment by @frivoal)
-