W3C Process Community Group - Activity in 2023
No matches.
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Juan Kruger (ASISBUSINESS ECI) joined.
-
-
1 participant left.
-
James Rosewell (51Degrees) left.
-
-
1 organization joined.
-
ASISBUSINESS ECI joined.
-
-
1 organization left.
-
51Degrees left.
-
GitHub
w3c/process
-
5 issues opened.
-
Are TAG Appointments mandatory for the Team to fill? w3c/process#811, by @martinthomson.
-
AB Role in TAG Appointment w3c/process#810, by @martinthomson.
-
TAG Appointment Process Shortcomings w3c/process#809, by @martinthomson.
-
What kind of Group is for what kind of work? w3c/process#804, by @frivoal.
-
4 issues closed.
-
What's the point of what the Process has to say about Liasons? w3c/process#422.
-
Remove normative keywords from non-normative sections w3c/process#745.
-
W3C Decision needs better cross-referencing w3c/process#802.
-
AC Review is missing a step to resolve formal objections w3c/process#739.
-
-
15 issues received 51 new comments.
-
AB Role in TAG Appointment w3c/process#810 (12 comments by @cwilso, @dwsinger, @frivoal, @martinthomson, @nigelmegitt, @plehegar, @TallTed)
-
What's the point of what the Process has to say about Liasons? w3c/process#422 (8 comments by @chrisn, @css-meeting-bot, @dwsinger, @frivoal, @joshco, @samuelweiler, @TallTed)
-
Remove normative keywords from non-normative sections w3c/process#745 (5 comments by @frivoal, @TallTed)
-
Addressing formal objections before requesting advancement w3c/process#737 (4 comments by @fantasai, @frivoal, @jyasskin)
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779 (4 comments by @csarven, @dwsinger, @fantasai, @frivoal)
-
Ground the different types of groups / maturity stages in Problem Statements w3c/process#813 (3 comments by @frivoal, @michaelchampion, @TallTed)
-
Closing a group prior to the date specified in the charter should be a "Team Decision", not a "W3C Decision" w3c/process#797 (3 comments by @chaals, @fantasai, @plehegar)
-
W3C Decision needs better cross-referencing w3c/process#802 (3 comments by @css-meeting-bot, @fantasai, @frivoal)
-
AC Review is missing a step to resolve formal objections w3c/process#739 (2 comments by @fantasai, @jyasskin)
-
Requirement to publish formal objections should include a timeline w3c/process#735 (2 comments by @fantasai)
-
Link for "W3C Horizontal Groups" doesn't describe W3C horizontal groups w3c/process#769 (1 comment by @fantasai)
-
Are the rules for updating Registry Definitions appropriate? w3c/process#800 (1 comment by @fantasai)
-
-
4 pull requests opened.
-
Clarify FO publication timing #735 w3c/process#808, by @fantasai.
-
Reduce confusion wrt registry sections #800 w3c/process#807, by @fantasai.
-
Improve headings in AC Review section #802 w3c/process#806, by @fantasai.
-
Eliminate a number of non-normative uses of rfc2119 language w3c/process#803, by @frivoal.
-
-
2 pull requests merged.
-
Eliminate a number of non-normative uses of rfc2119 language w3c/process#803.
-
Improve headings in AC Review section #802 w3c/process#806.
-
-
1 pull request closed.
-
Issue 574, order of precedence w3c/process#599.
-
-
4 pull requests received 45 new comments.
-
Reduce confusion wrt registry sections #800 w3c/process#807 (20 comments by @chrisn, @dwsinger, @fantasai, @frivoal, @nigelmegitt)
-
Eliminate a number of non-normative uses of rfc2119 language w3c/process#803 (17 comments by @chrisn, @css-meeting-bot, @dwsinger, @fantasai, @frivoal, @jyasskin, @TallTed)
-
Clarify FO publication timing #735 w3c/process#808 (7 comments by @css-meeting-bot, @cwilso, @fantasai, @frivoal, @jyasskin)
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Jan Stelovsky joined.
-
-
2 participants left.
-
Pierre-Anthony Lemieux (MovieLabs) left.
-
Muhammad bilal Khan left.
-
GitHub
w3c/process
-
2 issues opened.
-
W3C Decision needs better cross-referencing w3c/process#802, by @fantasai.
-
Are the rules for updating Registry Definitions appropriate? w3c/process#800, by @nigelmegitt.
-
-
3 issues closed.
-
Stop citing the "superseded" TAG charter w3c/process#794.
-
-
5 issues received 21 new comments.
-
Are the rules for updating Registry Definitions appropriate? w3c/process#800 (9 comments by @dwsinger, @fantasai, @nigelmegitt, @TallTed)
-
Order of precedence of Membership Agreement, Process document and normative references w3c/process#574 (6 comments by @fantasai, @jwrosewell, @plehegar)
-
Closing a group prior to the date specified in the charter should be a "Team Decision", not a "W3C Decision" w3c/process#797 (4 comments by @css-meeting-bot, @fantasai, @koalie, @plehegar)
-
Requirement to publish formal objections should include a timeline w3c/process#735 (1 comment by @css-meeting-bot)
-
-
1 pull request merged.
-
1 pull request closed.
-
3 pull requests received 4 new comments.
-
Enable Team to replace defunct registry custodians when no-one else can w3c/process#790 (2 comments by @css-meeting-bot, @TallTed)
-
Exclude TAG/AB from voting on their own decisions/proposals. #749 w3c/process#761 (1 comment by @nabilaljordan)
-
Clarify integration (and potential conflicts) between the Process and its normative references w3c/process#572 (1 comment by @frivoal)
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Nora R joined.
-
GitHub
w3c/process
-
3 issues opened.
-
Stop citing the "superseded" TAG charter w3c/process#794, by @jyasskin.
-
Disciplinary action w3c/process#786, by @mnot.
-
4 issues closed.
-
Conflict of Interest in Council composition w3c/process#749.
-
Dismissal voting w3c/process#748.
-
11 issues received 15 new comments.
-
Council Composition requirements include Tim Berners-Lee, TAG life member w3c/process#784 (2 comments by @css-meeting-bot, @frivoal)
-
Order of precedence of Membership Agreement, Process document and normative references w3c/process#574 (2 comments by @frivoal, @rigow)
-
Closing a group prior to the date specified in the charter should be a "Team Decision", not a "W3C Decision" w3c/process#797 (1 comment by @koalie)
-
AC Review is missing a step to resolve formal objections w3c/process#739 (1 comment by @css-meeting-bot)
-
"Regression on the REC track" should say what kind of approval is needed w3c/process#741 (1 comment by @css-meeting-bot)
-
Mandate default custodianship for Registries if the specified custodian is no longer available w3c/process#699 (1 comment by @css-meeting-bot)
-
living standard / candidate review snapshots need to address wide review issues w3c/process#781 (1 comment by @css-meeting-bot)
-
7 pull requests opened.
-
Allow Tim Berners-Lee to abstain in Unanimous Short Circuit votes w3c/process#793, by @frivoal.
-
Limit the involvement of Tim Berners-Lee to the TAG proper w3c/process#792, by @frivoal.
-
Adjust the status of Tim Berners-Lee in the TAG w3c/process#791, by @frivoal.
-
Enable Team to replace defunct registry custodians when no-one else can w3c/process#790, by @frivoal.
-
[editorial] More explicitly Trigger FO handling process w3c/process#789, by @frivoal.
-
Clarify approvals of TAG+AB for REC track regression w3c/process#788, by @frivoal.
-
Progress on issues w3c/process#787, by @frivoal.
-
-
5 pull requests merged.
-
[editorial] More explicitly Trigger FO handling process w3c/process#789.
-
Progress on issues w3c/process#787.
-
Clarify approvals of TAG+AB for REC track regression w3c/process#788.
-
Exclude TAG/AB from voting on their own decisions/proposals. #749 w3c/process#761.
-
Must report dismissal vote counts. #748 w3c/process#760.
-
-
7 pull requests received 27 new comments.
-
Enable Team to replace defunct registry custodians when no-one else can w3c/process#790 (15 comments by @dwsinger, @nigelmegitt, @TallTed)
-
Allow Tim Berners-Lee to abstain in Unanimous Short Circuit votes w3c/process#793 (4 comments by @dwsinger, @frivoal, @nigelmegitt)
-
Limit the involvement of Tim Berners-Lee to the TAG proper w3c/process#792 (4 comments by @chaals, @dwsinger, @frivoal, @nigelmegitt)
-
Exclude TAG/AB from voting on their own decisions/proposals. #749 w3c/process#761 (1 comment by @frivoal)
-
Past meetings
Participants
-
1 participant joined.
-
Benjamin Goering (Protocol Labs) joined.
-
-
1 organization joined.
-
Protocol Labs joined.
-
GitHub
w3c/process
-
1 issue opened.
-
Council Composition requirements include Tim Berners-Lee, TAG life member w3c/process#784, by @plehegar.
-
-
1 issue closed.
-
Define "joint deliverables" w3c/process#754.
-
-
11 issues received 24 new comments.
-
"Wide review" is too easy to confuse with "horizontal review" w3c/process#776 (5 comments by @dwsinger, @nigelmegitt, @plehegar)
-
living standard / candidate review snapshots need to address wide review issues w3c/process#781 (3 comments by @michaelchampion, @npdoty, @plehegar)
-
Council Composition requirements include Tim Berners-Lee, TAG life member w3c/process#784 (3 comments by @frivoal, @plehegar)
-
Order of precedence of Membership Agreement, Process document and normative references w3c/process#574 (2 comments by @plehegar)
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779 (2 comments by @dwsinger, @fantasai)
-
The 2021 "Revising a Recommendation Process" is painful for WGs w3c/process#589 (1 comment by @plehegar)
-
Clarify and simplify the sections regarding publication and process 2021 w3c/process#700 (1 comment by @wareid)
-
Chair appointment community involvement, transparency, enabling objections and handling them w3c/process#281 (1 comment by @jyasskin)
-
-
1 pull request opened.
-
update link to W3C submissions w3c/process#783, by @deniak.
-
-
1 pull request merged.
-
update link to W3C submissions w3c/process#783.
-
Participants
-
2 participants joined.
-
Rachel Yager (FortuneTimes Group) joined.
-
FELIPE Reviriego Calatrava joined.
-
-
2 participants left.
-
Lindsey Boynton (School Webmasters) left.
-
FELIPE Reviriego Calatrava left.
-
-
2 organizations joined.
-
FortuneTimes Group joined.
-
CUARTEL GENERAL (EMAD) MINISTERIO DE DEFENSA joined.
-
-
1 organization left.
-
School Webmasters left.
-
GitHub
w3c/process
-
2 issues opened.
-
living standard / candidate review snapshots need to address wide review issues w3c/process#781, by @npdoty.
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779, by @shawna-slh.
-
-
3 issues received 16 new comments.
-
living standard / candidate review snapshots need to address wide review issues w3c/process#781 (8 comments by @dwsinger, @frivoal, @michaelchampion, @npdoty)
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779 (3 comments by @fantasai, @koalie, @shawna-slh)
-
-
1 pull request received 1 new comment.
-
Clarify integration (and potential conflicts) between the Process and its normative references w3c/process#572 (1 comment by @TallTed)
-
Participants
-
1 chair appointed.
-
Elika Etemad became a chair.
-
-
1 participant joined.
-
FELIPE Reviriego Calatrava joined.
-
-
1 participant left.
-
Michael Cooper (W3C) left.
-
GitHub
w3c/process
-
3 issues opened.
-
Veto by inaction w3c/process#778, by @mnot.
-
"Wide review" is too easy to confuse with "horizontal review" w3c/process#776, by @marcoscaceres.
-
Diagram should clarify that it's possible to go from REC back to CR w3c/process#775, by @marcoscaceres.
-
-
1 issue closed.
-
Increase size of the TAG? w3c/process#465.
-
-
7 issues received 23 new comments.
-
Veto by inaction w3c/process#778 (10 comments by @dwsinger, @fantasai, @frivoal, @mnot, @nigelmegitt, @samuelweiler)
-
Clarify and simplify the sections regarding publication and process 2021 w3c/process#700 (5 comments by @frivoal, @marcoscaceres, @TallTed)
-
"Wide review" is too easy to confuse with "horizontal review" w3c/process#776 (2 comments by @nigelmegitt, @samuelweiler)
-
Diagram should clarify that it's possible to go from REC back to CR w3c/process#775 (1 comment by @frivoal)
-
-
1 pull request opened.
-
Update README.md w3c/process#777, by @Galbert01.
-
-
1 pull request merged.
-
Expand the TAG from 6+3 to 8+3 participants w3c/process#733.
-
-
1 pull request closed.
-
Update README.md w3c/process#777.
-
-
2 pull requests received 3 new comments.
-
Meetings of new groups are 8 weeks from charter approval w3c/process#434 (1 comment by @samuelweiler)
Past meetings
-
1 meeting.
Participants
-
1 chair stepped down.
-
Elika Etemad stepped down as a chair.
-
-
3 participants joined.
-
Elika Etemad (Apple Inc.) joined.
-
Muhammad bilal Khan joined.
-
Parampreet Singh joined.
-
-
1 participant left.
-
Elika Etemad (Apple Inc.) left.
-
GitHub
w3c/process
-
3 issues opened.
-
Link for "W3C Horizontal Groups" doesn't describe W3C horizontal groups w3c/process#769, by @jyasskin.
-
2 issues closed.
-
Japanese translation of Process 2021 w3c/process#767.
-
7 issues received 38 new comments.
-
Incumbent bias in elections / impose term limits? w3c/process#697 (16 comments by @cwilso, @dwsinger, @frivoal, @LJWatson, @michaelchampion, @mnot, @TzviyaSiegman)
-
Japanese translation of Process 2021 w3c/process#767 (6 comments by @frivoal, @xueyuanjia, @yonaomi, @ytakamu)
-
Clarify and simplify the sections regarding publication and process 2021 w3c/process#700 (5 comments by @dwsinger, @marcoscaceres, @nigelmegitt, @TzviyaSiegman, @wareid)
-
Can WGs request the W3C team to negotiate technical agreements with liaison organizations? w3c/process#773 (4 comments by @fantasai, @frivoal, @nigelmegitt, @TallTed)
-
Use Alias rather than Redirect for /Consortium/Process w3c/process#729 (3 comments by @koalie, @plehegar)
-
Link for "W3C Horizontal Groups" doesn't describe W3C horizontal groups w3c/process#769 (1 comment by @samuelweiler)
-
-
1 pull request merged.
-
informative role of chair/contact. fixes #765 w3c/process#766.
-
-
1 pull request received 1 new comment.
Past meetings
-
1 meeting.
Participants
-
2 participants left.
-
AHMED ALI left.
-
Pavlik elf left.
-
GitHub
w3c/process
-
5 issues opened.
-
Japanese translation of Process 2021 w3c/process#767, by @xueyuanjia.
-
Closing the loop on resolving Formal Objections w3c/process#755, by @plehegar.
-
Define "joint deliverables" w3c/process#754, by @frivoal.
-
-
9 issues closed.
-
Avoid using two different meanings of "sustain" w3c/process#746.
-
Editorial: dismissal w3c/process#747.
-
AC Review dissent requirement vs questionnaire options w3c/process#738.
-
Clarify where Submission Appeals go w3c/process#742.
-
editorial: textual inconsistencies in basic-rec-track.svg w3c/process#661.
-
Dissent in AC review w3c/process#750.
-
Minority Opinions w3c/process#752.
-
19 issues received 113 new comments.
-
Closing the loop on resolving Formal Objections w3c/process#755 (24 comments by @chaals, @dwsinger, @fantasai, @frivoal, @marcoscaceres, @nigelmegitt, @palemieux)
-
Council decision side effects w3c/process#751 (23 comments by @chrisn, @dwsinger, @fantasai, @frivoal, @mnot, @nigelmegitt, @othermaciej, @plehegar)
-
Define "joint deliverables" w3c/process#754 (9 comments by @anssiko, @dwsinger, @frivoal, @marcoscaceres, @nigelmegitt, @plehegar)
-
Dismissal voting w3c/process#748 (8 comments by @dwsinger, @fantasai, @frivoal, @mnot, @nigelmegitt)
-
Avoid using two different meanings of "sustain" w3c/process#746 (5 comments by @chrisn, @css-meeting-bot, @fantasai, @frivoal)
-
New W3C Council and updated TAG Composition section errantly only includes Tim Berners-Lee... w3c/process#764 (4 comments by @fantasai, @frivoal, @tantek)
-
Addressing formal objections before requesting advancement w3c/process#737 (2 comments by @frivoal, @jyasskin)
-
AC Review dissent requirement vs questionnaire options w3c/process#738 (2 comments by @fantasai, @jyasskin)
-
Normative prose for role of Chair / Team Contact cites informative reference for description w3c/process#765 (1 comment by @frivoal)
-
"Regression on the REC track" should say what kind of approval is needed w3c/process#741 (1 comment by @fantasai)
-
-
7 pull requests opened.
-
informative role of chair/contact. fixes #765 w3c/process#766, by @tantek.
-
Clarify 'formal contexts' for Formal Objections w3c/process#763, by @chrisn.
-
Disambiguate sustain w3c/process#762, by @frivoal.
-
Exclude TAG/AB from voting on their own decisions/proposals. #749 w3c/process#761, by @fantasai.
-
Must report dismissal vote counts. #748 w3c/process#760, by @fantasai.
-
Fix typo in description of Council formation w3c/process#759, by @chrisn.
-
Dismissal wording w3c/process#757, by @fantasai.
-
-
7 pull requests merged.
-
fix punc, spelling, inconsistent labels, etc. w3c/process#667.
-
Dismissal wording w3c/process#757.
-
Disambiguate sustain w3c/process#762.
-
Clarify 'formal contexts' for Formal Objections w3c/process#763.
-
Don't say that dissent goes away when it's overruled w3c/process#740.
-
Fix typo in description of Council formation w3c/process#759.
-
-
6 pull requests received 7 new comments.
-
fix punc, spelling, inconsistent labels, etc. w3c/process#667 (2 comments by @css-meeting-bot, @fantasai)
-
Exclude TAG/AB from voting on their own decisions/proposals. #749 w3c/process#761 (1 comment by @dwsinger)
-
Participants
-
1 participant joined.
-
AHMED ALI joined.
-
-
1 organization joined.
-
Massachusetts Institute of Technology (MIT) joined.
-
GitHub
w3c/process
-
18 issues opened.
-
Minority Opinions w3c/process#752, by @mnot.
-
Council decision side effects w3c/process#751, by @mnot.
-
Dissent in AC review w3c/process#750, by @mnot.
-
Conflict of Interest in Council composition w3c/process#749, by @mnot.
-
Dismissal voting w3c/process#748, by @mnot.
-
Editorial: dismissal w3c/process#747, by @mnot.
-
Avoid using two different meanings of "sustain" w3c/process#746, by @jyasskin.
-
Remove normative keywords from non-normative sections w3c/process#745, by @jyasskin.
-
Clarify where Submission Appeals go w3c/process#742, by @jyasskin.
-
"Regression on the REC track" should say what kind of approval is needed w3c/process#741, by @jyasskin.
-
AC Review is missing a step to resolve formal objections w3c/process#739, by @jyasskin.
-
AC Review dissent requirement vs questionnaire options w3c/process#738, by @jyasskin.
-
Addressing formal objections before requesting advancement w3c/process#737, by @jyasskin.
-
Requirement to publish formal objections should include a timeline w3c/process#735, by @jyasskin.
-
Broken link in changes section w3c/process#734, by @jyasskin.
-
Use Alias rather than Redirect for /Consortium/Process w3c/process#729, by @fantasai.
-
Editorial: "W3C" as a proper noun w3c/process#728, by @koalie.
-
-
2 issues closed.
-
Broken link in changes section w3c/process#734.
-
Editorial: "W3C" as a proper noun w3c/process#728.
-
-
10 issues received 19 new comments.
-
AC Review dissent requirement vs questionnaire options w3c/process#738 (4 comments by @frivoal, @jyasskin, @nigelmegitt)
-
Addressing formal objections before requesting advancement w3c/process#737 (4 comments by @chrisn, @jyasskin, @nigelmegitt)
-
FPWD → CRS transition has onerous change documentation requirements w3c/process#727 (2 comments by @dontcallmedom, @frivoal)
-
-
6 pull requests opened.
-
Say that Chair Decision Appeals were also merged with Formal Objections. w3c/process#743, by @jyasskin.
-
Don't say that dissent goes away when it's overruled w3c/process#740, by @jyasskin.
-
Expand the TAG from 6+3 to 8+3 participants w3c/process#733, by @frivoal.
-
Update SoTD w3c/process#732, by @swickr.
-
editorial change to harmonize "website"/"Web site" w3c/process#731, by @koalie.
-
Use “W3C”, not “the W3C” w3c/process#730, by @frivoal.
-
-
3 pull requests merged.
-
Update SoTD w3c/process#732.
-
Use “W3C”, not “the W3C” w3c/process#730.
-
editorial change to harmonize "website"/"Web site" w3c/process#731.
-
-
2 pull requests received 13 new comments.
-
Don't say that dissent goes away when it's overruled w3c/process#740 (11 comments by @dwsinger, @jyasskin, @nigelmegitt, @TallTed)
-
Past meetings
Participants
-
2 participants joined.
-
Sarven Capadisli joined.
-
Chris Needham (British Broadcasting Corporation) joined.
-
GitHub
w3c/process
-
6 issues opened.
-
FPWD → CRS transition has onerous change documentation requirements w3c/process#727, by @dontcallmedom.
-
Candidate Recommendation Draft vs "return to Working Draft" w3c/process#726, by @dontcallmedom.
-
Registry report requirements w3c/process#725, by @chrisn.
-
Ratification of TAG appointments w3c/process#715, by @mnot.
-
Rename Acknowledgement (for Member submission requests) w3c/process#714, by @frivoal.
-
-
4 issues closed.
-
"The W3C Council" should often be "A W3C Council" w3c/process#710.
-
Ratification of TAG appointments w3c/process#715.
-
export registry-related terms for ease of reference w3c/process#713.
-
22 issues received 77 new comments.
-
Rename Acknowledgement (for Member submission requests) w3c/process#714 (10 comments by @chrisn, @dwsinger, @fantasai, @frivoal, @koalie, @nigelmegitt)
-
Ratification of TAG appointments w3c/process#715 (8 comments by @css-meeting-bot, @cwilso, @dwsinger, @fantasai, @mnot, @swickr)
-
Appeal process for proposals w3c/process#478 (6 comments by @chaals, @fantasai, @frivoal, @jwrosewell)
-
Should a team-confidential formal objection lead to a team-confidential council report? w3c/process#717 (5 comments by @css-meeting-bot, @dwsinger, @frivoal, @swickr)
-
TAG appointment should be via IETF style nomcom w3c/process#230 (4 comments by @frivoal, @mnot, @nrooney)
-
Stronger emphasis on reaching Recommendation w3c/process#443 (3 comments by @chrisn, @frivoal, @plehegar)
-
The team should not be expected to recommend a disposition of an FO w3c/process#629 (3 comments by @frivoal, @palemieux)
-
Order of precedence of Membership Agreement, Process document and normative references w3c/process#574 (2 comments by @css-meeting-bot, @fantasai)
-
Setup document management for director-free matters w3c/process#366 (2 comments by @frivoal, @LJWatson)
-
Grace period for contributing to specifications? w3c/process#672 (2 comments by @frivoal, @jyasskin)
-
Sustaining an FO should always require super-majority support w3c/process#631 (2 comments by @frivoal, @palemieux)
-
FO Council should not be allowed to delegate its responsibility w3c/process#630 (2 comments by @frivoal, @palemieux)
-
export registry-related terms for ease of reference w3c/process#713 (2 comments by @frivoal, @nigelmegitt)
-
-
4 pull requests opened.
-
Confidentiality Levels and Redactions w3c/process#722, by @joshco.
-
Fix up inconsistencies in the confidentiality of FOs and Council Reports w3c/process#720, by @frivoal.
-
Speak of *a* Council, not *the* Council w3c/process#719, by @frivoal.
-
Change who ratifies the TAG appointees w3c/process#718, by @frivoal.
-
-
3 pull requests merged.
-
Speak of *a* Council, not *the* Council w3c/process#719.
-
Change who ratifies the TAG appointees w3c/process#718.
-
4 pull requests received 8 new comments.
-
Fix up inconsistencies in the confidentiality of FOs and Council Reports w3c/process#720 (4 comments by @dwsinger, @frivoal, @nigelmegitt)
-
Rename Acknowledgement to Acceptance (for Member submission requests) w3c/process#640 (1 comment by @frivoal)
-
Clarify integration (and potential conflicts) between the Process and its normative references w3c/process#572 (1 comment by @nigelmegitt)
-
Past meetings
Participants
-
4 participants joined.
-
Divya Mohan joined.
-
Chris O'Brien (Apple Inc.) joined.
-
Nick Doty (Center for Democracy and Technology) joined.
-
Jennifer Strickland joined.
-
-
1 participant left.
-
Wendy Seltzer (W3C) left.
-
-
2 organizations joined.
-
Center for Democracy and Technology joined.
-
MITRE Corporation joined.
-
GitHub
w3c/process
-
3 issues opened.
-
export registry-related terms for ease of reference w3c/process#713, by @nigelmegitt.
-
Are Statements fit for purpose? w3c/process#712, by @mnot.
-
"The W3C Council" should often be "A W3C Council" w3c/process#710, by @TallTed.
-
-
8 issues closed.
-
Clarify AC and BoD priority when signing MoUs and similar contracts w3c/process#670.
-
Should W3C continue to stagger AB/TAG elections ? w3c/process#688.
-
Ensuring charters fit the mission and values of W3C w3c/process#620.
-
[Editorial] Adjust grounding of RF distribution of specifications w3c/process#681.
-
11 issues received 26 new comments.
-
Are Statements fit for purpose? w3c/process#712 (13 comments by @chaals, @dwsinger, @frivoal, @michaelchampion, @mnot, @nigelmegitt, @TzviyaSiegman)
-
Mandate default custodianship for Registries if the specified custodian is no longer available w3c/process#699 (1 comment by @frivoal)
-
[Editorial] Where Formal Objection is defined, identify milder ways to express disagreement w3c/process#680 (1 comment by @frivoal)
-
[editorial] Council composition statement spends too much time on exceptions w3c/process#679 (1 comment by @css-meeting-bot)
-
Clarify AC and BoD priority when signing MoUs and similar contracts w3c/process#670 (1 comment by @css-meeting-bot)
-
Should there be good standing / supermajority criteria in authoritative ballots? w3c/process#76 (1 comment by @michaelchampion)
-
Possibly dismissing a Formal Objection before it goes to full Council? w3c/process#678 (1 comment by @frivoal)
-
-
2 pull requests opened.
-
Editorial cleanup regarding normative dependencies of the Process w3c/process#711, by @frivoal.
-
Enable changes of chair in a Council w3c/process#709, by @frivoal.
-
-
9 pull requests merged.
-
Clarify interactions between AC / Team / Board about MoUs w3c/process#704.
-
Editorial cleanup regarding normative dependencies of the Process w3c/process#711.
-
Simplify phrasing about council composition w3c/process#706.
-
Correct reference to W3C Document / Software licensing w3c/process#705.
-
Introduce path to shortcut the Council w3c/process#703.
-
Enable changes of chair in a Council w3c/process#709.
-
Include Council Team Contact in the confidence of the Council w3c/process#702.
-
Clarify role of Council Team Contact (and define the term) w3c/process#701.
-
-
9 pull requests received 69 new comments.
-
Simplify phrasing about council composition w3c/process#706 (20 comments by @chrisn, @css-meeting-bot, @cwilso, @dwsinger, @fantasai, @frivoal, @nigelmegitt, @TallTed)
-
Clarify interactions between AC / Team / Board about MoUs w3c/process#704 (18 comments by @css-meeting-bot, @cwilso, @dwsinger, @frivoal, @LJWatson, @nigelmegitt, @TallTed)
-
Rename Acknowledgement to Acceptance (for Member submission requests) w3c/process#640 (10 comments by @css-meeting-bot, @fantasai, @frivoal, @koalie, @nigelmegitt, @TallTed)
-
Editorial cleanup regarding normative dependencies of the Process w3c/process#711 (6 comments by @chrisn, @css-meeting-bot, @dwsinger, @TallTed)
-
Include Council Team Contact in the confidence of the Council w3c/process#702 (5 comments by @frivoal, @nigelmegitt, @TallTed)
-
Clarify integration (and potential conflicts) between the Process and its normative references w3c/process#572 (2 comments by @frivoal, @nigelmegitt)
-
Past meetings
-
1 meeting.
Participants
-
3 participants joined.
-
Andrew Somers joined.
-
Wendy Reid (Rakuten Group, Inc.) joined.
-
Qing An (Alibaba Group) joined.
-
-
2 participants left.
-
Judy Brewer (W3C) left.
-
Samuel Weiler (W3C) left.
-
-
2 organizations joined.
-
Rakuten Group, Inc. joined.
-
Alibaba Group joined.
-
GitHub
w3c/process
-
5 issues opened.
-
Clarify and simplify the sections regarding publication and process 2021 w3c/process#700, by @wareid.
-
Votes transparency w3c/process#698, by @marcoscaceres.
-
Incumbent bias in elections / impose term limits? w3c/process#697, by @marcoscaceres.
-
TAG charter needs revision for Director-free alignment w3c/process#695, by @ianbjacobs.
-
-
5 issues closed.
-
What is the CR Review Period? w3c/process#637.
-
Closing Groups w3c/process#653.
-
Reintroduce the conditions for closure of a group w3c/process#685.
-
Should appeal request be shared with the Membership? w3c/process#603.
-
TAG charter needs revision for Director-free alignment w3c/process#695.
-
-
20 issues received 74 new comments.
-
Incomplete Term Assignment Choices w3c/process#694 (16 comments by @chaals, @cwilso, @dwsinger, @frivoal, @TzviyaSiegman)
-
Incumbent bias in elections / impose term limits? w3c/process#697 (11 comments by @chaals, @cwilso, @dwsinger, @frivoal, @marcoscaceres, @michaelchampion)
-
TAG charter needs revision for Director-free alignment w3c/process#695 (10 comments by @chaals, @dwsinger, @fantasai, @ianbjacobs, @TzviyaSiegman)
-
Ensuring charters fit the mission and values of W3C w3c/process#620 (8 comments by @chaals, @cwilso, @dwsinger, @michaelchampion, @mnot)
-
Possibly dismissing a Formal Objection before it goes to full Council? w3c/process#678 (7 comments by @dwsinger, @fantasai, @frivoal, @michaelchampion, @mnot)
-
Mandate default custodianship for Registries if the specified custodian is no longer available w3c/process#699 (3 comments by @dwsinger, @frivoal, @TallTed)
-
[patent policy] Exclusion opportunity when work leaves a Working Group w3c/process#518 (2 comments by @dwsinger, @plehegar)
-
[Editorial] Where Formal Objection is defined, identify milder ways to express disagreement w3c/process#680 (1 comment by @frivoal)
-
Community Groups and Business Groups should be incorporated into the Process w3c/process#409 (1 comment by @plehegar)
-
Have the normal, default, decision policy for charters in the process w3c/process#425 (1 comment by @plehegar)
-
Should appeal request be shared with the Membership? w3c/process#603 (1 comment by @css-meeting-bot)
-
-
7 pull requests opened.
-
Simplify phrasing about council composition w3c/process#706, by @frivoal.
-
Correct reference to W3C Document / Software licensing w3c/process#705, by @frivoal.
-
Clarify interactions between AC / Team / Board about MoUs w3c/process#704, by @frivoal.
-
Introduce path to shortcut the Council w3c/process#703, by @frivoal.
-
Include Council Team Contact in the confidence of the Council w3c/process#702, by @frivoal.
-
Clarify role of Council Team Contact (and define the term) w3c/process#701, by @frivoal.
-
Update conditions for proposing closure of a group w3c/process#696, by @frivoal.
-
-
3 pull requests merged.
-
Clarify what the CR review period is w3c/process#691.
-
Update conditions for proposing closure of a group w3c/process#696.
-
-
3 pull requests closed.
-
Simplify the text on liaisons w3c/process#433.
-
Make it clear than any decision can be objected to w3c/process#299.
-
Broaden who may propose group closure w3c/process#660.
-
-
6 pull requests received 20 new comments.
-
Clarify role of Council Team Contact (and define the term) w3c/process#701 (5 comments by @frivoal, @TallTed)
-
Clarify interactions between AC / Team / Board about MoUs w3c/process#704 (2 comments by @frivoal, @TallTed)
-
Update conditions for proposing closure of a group w3c/process#696 (2 comments by @css-meeting-bot, @TallTed)