W3C Process Community Group - Activity in 2024
No matches.
Past meetings
GitHub
w3c/process
-
6 issues opened.
-
Remnant of Proposed Recommendation w3c/process#965, by @vivienlacourba.
-
Exclusion Documents can be Recommendations, not just Drafts w3c/process#963, by @svgeesus.
-
URIs to W3C Process and Patent Policy docs w3c/process#962, by @vivienlacourba.
-
The Team should be able to initiate AC Review of charter draft w3c/process#959, by @plehegar.
-
Automatic Extension of Nomination Period due to Insufficient Candidates w3c/process#949, by @fantasai.
-
Change participation requirements for editors w3c/process#948, by @cwadamsoforacle.
-
-
11 issues closed.
-
Candidate Recommendation Draft vs "return to Working Draft" w3c/process#726.
-
Are TAG Appointments mandatory for the Team to fill? w3c/process#811.
-
Clarify deadline for nominations w3c/process#464.
-
Visibility of FO handling w3c/process#870.
-
Remnant of Proposed Recommendation w3c/process#965.
-
Align with Bylaws changes w3c/process#849.
-
Do we need a procedural track for "disclosure" documents? w3c/process#460.
-
24 issues received 63 new comments.
-
Change participation requirements for editors w3c/process#948 (20 comments by @alastc, @chaals, @csarven, @fantasai, @frivoal, @iadawn, @michael-n-cooper, @nigelmegitt, @plehegar, @rigow, @swickr, @TallTed, @xfq)
-
Open up Registries to IG, TAG, AB w3c/process#902 (8 comments by @fantasai, @frivoal, @jyasskin, @nigelmegitt)
-
Feedback on Charter refinement draft text w3c/process#934 (4 comments by @css-meeting-bot, @fantasai, @ianbjacobs)
-
URIs to W3C Process and Patent Policy docs w3c/process#962 (2 comments by @frivoal, @vivienlacourba)
-
Are TAG Appointments mandatory for the Team to fill? w3c/process#811 (2 comments by @fantasai, @plehegar)
-
Closing a group prior to the date specified in the charter should be a "Team Decision", not a "W3C Decision" w3c/process#797 (2 comments by @fantasai, @plehegar)
-
Candidate Recommendation Draft vs "return to Working Draft" w3c/process#726 (2 comments by @frivoal, @plehegar)
-
Chair appointment community involvement, transparency, enabling objections and handling them w3c/process#281 (2 comments by @frivoal, @plehegar)
-
Member submissions: can anyone else object, and if so, can they object to acceptance? w3c/process#639 (2 comments by @fantasai, @frivoal)
-
Confusing inconsistencies between stages of the REC track for documents and for amendments w3c/process#938 (1 comment by @frivoal)
-
The Team should be able to initiate AC Review of charter draft w3c/process#959 (1 comment by @frivoal)
-
Proposed addition to "9. Liaisons" to address delays in PAS Submissions to ISO w3c/process#946 (1 comment by @fantasai)
-
Strip section 6.2.2.1 “wide review” of the mailing list currently mentioned w3c/process#815 (1 comment by @frivoal)
-
The sentence about affiliation change causing a seat to be vacated is in the wrong place w3c/process#770 (1 comment by @fantasai)
-
-
8 pull requests opened.
-
Decrease emphasis on FO to charter rejection w3c/process#964, by @frivoal.
-
Fix links (2nd batch) w3c/process#961, by @vivienlacourba.
-
Fix links w3c/process#960, by @vivienlacourba.
-
Be more specific about when the council composition is locked down w3c/process#955, by @frivoal.
-
Introduce Good Standing w3c/process#954, by @frivoal.
-
Require documentation of how FOs get resolved w3c/process#953, by @frivoal.
-
Defer to /Guide for specific mailing lists to send review requests to w3c/process#952, by @frivoal.
-
Allow for some amount of leeway at the close of nomination periods w3c/process#950, by @frivoal.
-
-
6 pull requests merged.
-
Allow for some amount of leeway at the close of nomination periods w3c/process#950.
-
Require documentation of how FOs get resolved w3c/process#953.
-
Introduce Good Standing w3c/process#954.
-
Fix links (2nd batch) w3c/process#961.
-
Fix links w3c/process#960.
-
-
7 pull requests received 11 new comments.
-
Be more specific about when the council composition is locked down w3c/process#955 (3 comments by @frivoal, @plehegar, @TallTed)
-
Limit the involvement of Tim Berners-Lee to the TAG proper w3c/process#792 (2 comments by @frivoal, @torgo)
-
Defer to /Guide for specific mailing lists to send review requests to w3c/process#952 (1 comment by @plehegar)
-
Allow for some amount of leeway at the close of nomination periods w3c/process#950 (1 comment by @plehegar)
-
Generalizing AC Appeals and using this procedure for recall. w3c/process#888 (1 comment by @frivoal)
-
Past meetings
GitHub
w3c/process
-
3 issues opened.
-
Mathematical Error in Composition of the AB section w3c/process#942, by @wareid.
-
10 issues closed.
-
Typical group duration is not six months to two years w3c/process#918.
-
Inaccurate text about Membership Agreements w3c/process#879.
-
Charter creation w3c/process#650.
-
Simplify member submissions w3c/process#421.
-
Who convenes Workshops? w3c/process#649.
-
Registry report requirements w3c/process#725.
-
Should member submissions be removed from the Process? w3c/process#648.
-
Charter Approval w3c/process#651.
-
-
14 issues received 22 new comments.
-
Good standing w3c/process#935 (5 comments by @chrisn, @css-meeting-bot, @fantasai, @frivoal, @mgendler)
-
Confusing inconsistencies between stages of the REC track for documents and for amendments w3c/process#938 (3 comments by @fantasai, @frivoal)
-
Mathematical Error in Composition of the AB section w3c/process#942 (2 comments by @frivoal, @wareid)
-
How do I suggest a specification without making a whole draft about it? This specification will save lives. w3c/process#947 (1 comment by @frivoal)
-
Typical group duration is not six months to two years w3c/process#918 (1 comment by @css-meeting-bot)
-
Define charter review process to require addressing comments as in CR transitions w3c/process#182 (1 comment by @fantasai)
-
-
2 pull requests merged.
-
Simplify the section Member Submissions w3c/process#936.
-
fix id attr typo lifecyle->lifecycle w3c/process#939.
-
-
1 pull request closed.
-
Reference w3c-ac-forum policy which defines list access policy w3c/process#912.
-
-
2 pull requests received 8 new comments.
-
Reference w3c-ac-forum policy which defines list access policy w3c/process#912 (1 comment by @css-meeting-bot)
Past meetings
GitHub
w3c/process
-
7 issues opened.
-
Good standing w3c/process#935, by @frivoal.
-
Feedback on Charter refinement draft text w3c/process#934, by @caribouW3.
-
Ambiguity in many voting rules w3c/process#933, by @martinthomson.
-
Update references to "CEPC" and "Code of Ethics and Professional Conduct" w3c/process#922, by @koalie.
-
Forbid holding multiple leadership positions w3c/process#921, by @martinthomson.
-
7 issues closed.
-
Charter review process w3c/process#580.
-
Clarify changes allowed during CR->REC transition w3c/process#919.
-
Multiple possible outcomes of a successful AC Appeal w3c/process#844.
-
Invited Experts without Member-only access w3c/process#900.
-
Closing the loop on resolving Formal Objections w3c/process#755.
-
Anonymous input for offline debate w3c/process#469.
-
-
20 issues received 59 new comments.
-
Forbid holding multiple leadership positions w3c/process#921 (27 comments by @chaals, @chrisn, @cwilso, @dwsinger, @fantasai, @frivoal, @igarashi50, @jyasskin, @martinthomson, @michaelchampion, @nigelmegitt, @rigow, @torgo, @wareid)
-
Confusing inconsistencies between stages of the REC track for documents and for amendments w3c/process#938 (4 comments by @fantasai, @frivoal)
-
Ambiguity about the formation time of a Council, and through that, about its composition w3c/process#926 (3 comments by @fantasai, @TallTed, @ylafon)
-
Multiple possible outcomes of a successful AC Appeal w3c/process#844 (2 comments by @css-meeting-bot, @fantasai)
-
Clarify changes allowed during CR->REC transition w3c/process#919 (2 comments by @css-meeting-bot, @fantasai)
-
Update references to "CEPC" and "Code of Ethics and Professional Conduct" w3c/process#922 (2 comments by @frivoal, @koalie)
-
Link for "W3C Horizontal Groups" doesn't describe W3C horizontal groups w3c/process#769 (1 comment by @frivoal)
-
Simplify Process 2021 (candidate|proposed) (change|addition|correction) terminology w3c/process#590 (1 comment by @frivoal)
-
-
8 pull requests opened.
-
fix id attr typo lifecyle->lifecycle w3c/process#939, by @tantek.
-
Simplify the section Member Submissions w3c/process#936, by @frivoal.
-
update BYLAWS reference to 2024 adopted revision w3c/process#930, by @tantek.
-
Forbid the Team from AB/TAG service w3c/process#929, by @martinthomson.
-
Require resignation from AB/TAG/BoD as a condition of service w3c/process#928, by @martinthomson.
-
Close review loopholes from dropping Proposed Recommendation w3c/process#927, by @frivoal.
-
Streamline Council formation and provide safeguards w3c/process#925, by @frivoal.
-
-
3 pull requests merged.
-
update BYLAWS reference to 2024 adopted revision w3c/process#930.
-
Streamline Council formation and provide safeguards w3c/process#925.
-
Close review loopholes from dropping Proposed Recommendation w3c/process#927.
-
-
2 pull requests closed.
-
Intro: State some high-level goals related to WGs and their specs w3c/process#894.
-
Allow Tim Berners-Lee to abstain in Unanimous Short Circuit votes w3c/process#793.
-
-
11 pull requests received 36 new comments.
-
Streamline Council formation and provide safeguards w3c/process#925 (6 comments by @css-meeting-bot, @frivoal, @TallTed)
-
Forbid the Team from AB/TAG service w3c/process#929 (5 comments by @cwilso, @dwsinger, @fantasai, @martinthomson)
-
Reference w3c-ac-forum policy which defines list access policy w3c/process#912 (5 comments by @css-meeting-bot, @fantasai, @frivoal, @koalie)
-
Intro: State some high-level goals related to WGs and their specs w3c/process#894 (5 comments by @chaals, @fantasai, @frivoal, @sideshowbarker, @TzviyaSiegman)
-
Require resignation from AB/TAG/BoD as a condition of service w3c/process#928 (4 comments by @cwilso, @martinthomson, @TallTed)
-
Adjust the status of Tim Berners-Lee in the TAG w3c/process#791 (4 comments by @frivoal, @martinthomson)
-
Close review loopholes from dropping Proposed Recommendation w3c/process#927 (3 comments by @fantasai, @frivoal, @TallTed)
-
Synchronize Advisory Committee representative and Consortium Member Representative w3c/process#937 (1 comment by @TallTed)
-
Add back language about substantive changes invalidating previous review w3c/process#887 (1 comment by @frivoal)
-
Allow Tim Berners-Lee to abstain in Unanimous Short Circuit votes w3c/process#793 (1 comment by @frivoal)
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Tzviya Siegman (W3C) joined.
-
-
2 participants left.
-
David Singer (Apple Inc.) left.
-
Tzviya Siegman (W3C) left.
-
GitHub
w3c/process
-
3 issues opened.
-
Clarify changes allowed during CR->REC transition w3c/process#919, by @fantasai.
-
Typical group duration is not six months to two years w3c/process#918, by @svgeesus.
-
Be consistent with terms "non-normative" and "informative" w3c/process#914, by @nigelmegitt.
-
-
4 issues closed.
-
Recommendation track diagram does not show Rec maintenance w3c/process#596.
-
Dealing with procedural disagreements within the Council w3c/process#843.
-
Determining AC Consensus of Post-Review Changes w3c/process#825.
-
REC track diagram does not reflect normative text w3c/process#638.
-
-
9 issues received 22 new comments.
-
"Candidate Recommendation" is no longer an accurate term w3c/process#402 (8 comments by @nigelmegitt, @rossberg, @sideshowbarker)
-
Open up Registries to IG, TAG, AB w3c/process#902 (4 comments by @dwsinger, @frivoal, @jyasskin, @nigelmegitt)
-
Recommendation track diagram does not show Rec maintenance w3c/process#596 (2 comments by @css-meeting-bot, @svgeesus)
-
Dealing with procedural disagreements within the Council w3c/process#843 (2 comments by @css-meeting-bot, @frivoal)
-
Be consistent with terms "non-normative" and "informative" w3c/process#914 (2 comments by @frivoal, @TallTed)
-
Should member submissions be removed from the Process? w3c/process#648 (1 comment by @css-meeting-bot)
-
-
3 pull requests merged.
-
Tighten the how sustantive changes are handled post AC-Review w3c/process#910.
-
Explicitly mark figures as non-normative w3c/process#911.
-
Add REC maintenance to diagram w3c/process#908.
-
-
1 pull request closed.
-
Deal with procedural disagreements within the Council w3c/process#909.
-
-
3 pull requests received 7 new comments.
-
Reference w3c-ac-forum policy which defines list access policy w3c/process#912 (5 comments by @chrisn, @frivoal)
-
Tighten the how sustantive changes are handled post AC-Review w3c/process#910 (1 comment by @TallTed)
-
Past meetings
-
1 meeting.
GitHub
w3c/process
-
3 issues closed.
-
Diagram should clarify that it's possible to go from REC back to CR w3c/process#775.
-
a role should be a role, not a task w3c/process#615.
-
-
6 issues received 12 new comments.
-
Diagram should clarify that it's possible to go from REC back to CR w3c/process#775 (1 comment by @frivoal)
-
Proposed Recommendations aren't useful in the same way other maturity stages are w3c/process#861 (1 comment by @css-meeting-bot)
-
6 pull requests opened.
-
Reference w3c-ac-forum policy which defines list access policy w3c/process#912, by @tobie.
-
Explicitly mark figures as non-normative w3c/process#911, by @frivoal.
-
Tighten the how sustantive changes are handled post AC-Review w3c/process#910, by @frivoal.
-
Deal with procedural disagreements within the Council w3c/process#909, by @frivoal.
-
Add REC maintenance to diagram w3c/process#908, by @frivoal.
-
short-circuit drop Team-related votes w3c/process#906, by @tantek.
-
-
2 pull requests merged.
-
Introduce an appendix cataloging old terminology w3c/process#898.
-
Retire Proposed Recommendation w3c/process#868.
-
-
1 pull request closed.
-
Meetings of new groups are 8 weeks from charter approval w3c/process#434.
-
-
8 pull requests received 60 new comments.
-
Allow Tim Berners-Lee to abstain in Unanimous Short Circuit votes w3c/process#793 (18 comments by @dwsinger, @frivoal, @TallTed, @tantek)
-
Introduce an appendix cataloging old terminology w3c/process#898 (8 comments by @css-meeting-bot, @fantasai, @frivoal)
-
Adjust the status of Tim Berners-Lee in the TAG w3c/process#791 (8 comments by @frivoal, @TallTed, @tantek)
-
Tighten the how sustantive changes are handled post AC-Review w3c/process#910 (3 comments by @TallTed)
-
Intro: State some high-level goals related to WGs and their specs w3c/process#894 (3 comments by @TallTed)
Past meetings
GitHub
w3c/process
-
5 issues opened.
-
Glossaries: a different pattern needed? w3c/process#904, by @cwilso.
-
Suboptimal wording about "License Grants from Non-Participants" w3c/process#903, by @frivoal.
-
Open up Registries to IG, TAG, AB w3c/process#902, by @frivoal.
-
Invited Experts without Member-only access w3c/process#900, by @jyasskin.
-
Phrasing disagreement w3c/process#899, by @frivoal.
-
-
5 issues closed.
-
Adjust AC appeal vote threshold based on participation w3c/process#886.
-
Who can initiate and prepare a Charter? w3c/process#560.
-
Phrasing disagreement w3c/process#899.
-
Making the Council's short circuit a little more flexible w3c/process#852.
-
Remove section of the Process on Workshop and Symposia w3c/process#419.
-
-
9 issues received 23 new comments.
-
Grace period for contributing to specifications? w3c/process#672 (3 comments by @dwsinger, @jyasskin, @OrKoN)
-
Enhancing the W3C REC Update Process for Greater Efficiency and Engagement w3c/process#866 (2 comments by @frivoal, @sideshowbarker)
-
Suboptimal wording about "License Grants from Non-Participants" w3c/process#903 (1 comment by @chaals)
-
2 pull requests opened.
-
Set up progressive vote threshold depending on participation w3c/process#901, by @frivoal.
-
Introduce an appendix cataloging old terminology w3c/process#898, by @frivoal.
-
-
4 pull requests merged.
-
Set up progressive vote threshold depending on participation w3c/process#901.
-
Introduce a formal Charter Refinement phase w3c/process#851.
-
Relax the criteria for short-circuit w3c/process#885.
-
Shift most discussion of Workshops to /Guide w3c/process#876.
-
-
7 pull requests received 81 new comments.
-
Retire Proposed Recommendation w3c/process#868 (34 comments by @fantasai, @frivoal, @nigelmegitt, @plehegar, @TallTed)
-
Generalizing AC Appeals and using this procedure for recall. w3c/process#888 (15 comments by @chaals, @dwsinger, @frivoal, @TallTed)
-
Introduce an appendix cataloging old terminology w3c/process#898 (15 comments by @frivoal, @TallTed)
-
Introduce a formal Charter Refinement phase w3c/process#851 (13 comments by @chrisn, @dontcallmedom, @fantasai, @frivoal, @swickr, @TallTed)
-
Set up progressive vote threshold depending on participation w3c/process#901 (2 comments by @chrisn, @TallTed)
-
GitHub
w3c/process
-
2 issues opened.
-
Adjust AC appeal vote threshold based on participation w3c/process#886, by @frivoal.
-
Recall procedures for TAG and AB w3c/process#882, by @mnot.
-
-
2 issues closed.
-
Use Alias rather than Redirect for /Consortium/Process w3c/process#729.
-
repo name nit: it'd be nice if this were simply w3c/process w3c/process#871.
-
-
1 issue reopened.
-
"Candidate Recommendation" is no longer an accurate term w3c/process#402, by @fantasai.
-
-
6 issues received 44 new comments.
-
"Candidate Recommendation" is no longer an accurate term w3c/process#402 (18 comments by @caribouW3, @dwsinger, @frivoal, @hober, @liamquin, @nigelmegitt, @sideshowbarker, @TallTed)
-
Use Alias rather than Redirect for /Consortium/Process w3c/process#729 (9 comments by @deniak, @frivoal, @koalie, @plehegar, @vivienlacourba)
-
repo name nit: it'd be nice if this were simply w3c/process w3c/process#871 (5 comments by @frivoal, @plehegar, @vivienlacourba)
-
Enhancing the W3C REC Update Process for Greater Efficiency and Engagement w3c/process#866 (1 comment by @dontcallmedom)
-
-
8 pull requests opened.
-
Intro: State some high-level goals related to WGs and their specs w3c/process#894, by @sideshowbarker.
-
Candidate Recommendation → Working Group Publication w3c/process#890, by @sideshowbarker.
-
Generalizing AC Appeals and using this procedure for recall. w3c/process#888, by @frivoal.
-
Add back language about substantive changes invalidating previous review w3c/process#887, by @sideshowbarker.
-
Relax the criteria for short-circuit w3c/process#885, by @frivoal.
-
Rationalize/streamline/modernize some core terminology w3c/process#883, by @sideshowbarker.
-
1 pull request merged.
-
Remove note about AC consensus assessment w3c/process#875.
-
-
2 pull requests closed.
-
Candidate Recommendation → Working Group Publication w3c/process#890.
-
2 pull requests reopened.
-
13 pull requests received 67 new comments.
-
Generalizing AC Appeals and using this procedure for recall. w3c/process#888 (23 comments by @frivoal, @TallTed)
-
Candidate Recommendation → Working Group Publication w3c/process#890 (6 comments by @cwilso, @sideshowbarker, @TallTed)
-
Add back language about substantive changes invalidating previous review w3c/process#887 (3 comments by @dwsinger, @frivoal, @sideshowbarker)
-
Note that “Candidate” means “eligible” for further-advancement consideration w3c/process#895 (2 comments by @nigelmegitt, @TallTed)
-
Rationalize/streamline/modernize some core terminology w3c/process#883 (2 comments by @frivoal, @sideshowbarker)
-
Add note reminding that the first stage of REC track is WD w3c/process#877 (2 comments by @frivoal, @TallTed)
-
Note that “Candidate” means “eligible” for further-advancement consideration w3c/process#893 (1 comment by @sideshowbarker)
-
Past meetings
Participants
-
1 participant joined.
-
Jennifer Meier (Digital Contract Design) joined.
-
-
1 organization joined.
-
Digital Contract Design joined.
-
GitHub
w3c/process
-
6 issues opened.
-
Inaccurate text about Membership Agreements w3c/process#879, by @hober.
-
repo name nit: it'd be nice if this were simply w3c/process w3c/process#871, by @hober.
-
Visibility of FO handling w3c/process#870, by @frivoal.
-
FPWD and joint deliverables—the process may be missing an exclusion opportunity w3c/process#869, by @hober.
-
Enhancing the W3C REC Update Process for Greater Efficiency and Engagement w3c/process#866, by @marcoscaceres.
-
Switching tracks **and back** w3c/process#864, by @frivoal.
-
-
6 issues closed.
-
CRD may be followed by a Proposed Recommendation w3c/process#450.
-
Switching tracks **and back** w3c/process#864.
-
Chair should be required in charter w3c/process#823.
-
Process should say how W3T can update NOTES w3c/process#120.
-
Representing the W3C w3c/process#582.
-
-
16 issues received 42 new comments.
-
Making the Council's short circuit a little more flexible w3c/process#852 (7 comments by @css-meeting-bot, @dwsinger, @frivoal, @hober, @tantek)
-
Switching tracks **and back** w3c/process#864 (5 comments by @caribouW3, @css-meeting-bot, @dwsinger, @frivoal)
-
FPWD and joint deliverables—the process may be missing an exclusion opportunity w3c/process#869 (5 comments by @dwsinger, @fantasai, @frivoal, @plehegar)
-
Proposed Recommendations aren't useful in the same way other maturity stages are w3c/process#861 (5 comments by @chaals, @css-meeting-bot, @frivoal)
-
repo name nit: it'd be nice if this were simply w3c/process w3c/process#871 (4 comments by @frivoal, @plehegar)
-
Should member submissions be removed from the Process? w3c/process#648 (2 comments by @dwsinger, @frivoal)
-
Use Alias rather than Redirect for /Consortium/Process w3c/process#729 (2 comments by @frivoal, @plehegar)
-
Council Composition requirements include Tim Berners-Lee, TAG life member w3c/process#784 (1 comment by @hober)
-
Enhancing the W3C REC Update Process for Greater Efficiency and Engagement w3c/process#866 (1 comment by @marcoscaceres)
-
-
9 pull requests opened.
-
Consolidate similar parts of REC revision w3c/process#878, by @frivoal.
-
Add note reminding that the first stage of REC track is WD w3c/process#877, by @frivoal.
-
Shift most discussion of Workshops to /Guide w3c/process#876, by @frivoal.
-
Remove note about AC consensus assessment w3c/process#875, by @frivoal.
-
Require listing chair(s) in charters w3c/process#874, by @frivoal.
-
[Editorial] Rephrase what CRDs are for w3c/process#873, by @frivoal.
-
Retire Proposed Recommendation w3c/process#868, by @frivoal.
-
Consolidate similar parts of REC revision w3c/process#865, by @frivoal.
-
[Editorial] Give context for candidate amendments when revising a REC w3c/process#862, by @frivoal.
-
-
6 pull requests merged.
-
[Editorial] Rephrase what CRDs are for w3c/process#873.
-
Consolidate similar parts of REC revision w3c/process#878.
-
Add note reminding that the first stage of REC track is WD w3c/process#877.
-
Require listing chair(s) in charters w3c/process#874.
-
Consolidate maintenance by the Team of technical reports w3c/process#860.
-
-
1 pull request closed.
-
Consolidate similar parts of REC revision w3c/process#865.
-
-
11 pull requests received 45 new comments.
-
Introduce a formal Charter Refinement phase w3c/process#851 (18 comments by @chrisn, @css-meeting-bot, @frivoal, @hober, @TallTed)
-
Shift most discussion of Workshops to /Guide w3c/process#876 (7 comments by @css-meeting-bot, @fantasai, @frivoal)
-
[Editorial] Give context for candidate amendments when revising a REC w3c/process#862 (4 comments by @css-meeting-bot, @TallTed)
-
Limit the involvement of Tim Berners-Lee to the TAG proper w3c/process#792 (2 comments by @frivoal, @hober)
-
Allow Tim Berners-Lee to abstain in Unanimous Short Circuit votes w3c/process#793 (1 comment by @frivoal)
-
Consolidate maintenance by the Team of technical reports w3c/process#860 (1 comment by @css-meeting-bot)
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Nicklas Pousette (Stiftelsen for internetinfrastruktur (IIS)) joined.
-
-
1 organization joined.
-
Stiftelsen for internetinfrastruktur (IIS) joined.
-
GitHub
w3c/process
-
8 issues opened.
-
Proposed Recommendations aren't useful in the same way other maturity stages are w3c/process#861, by @frivoal.
-
Retire the "Streamlined Publication Approval" system w3c/process#856, by @frivoal.
-
Creating a more visible banner for old process documents w3c/process#855, by @egekorkan.
-
Member Associations to Liaison Relationships w3c/process#853, by @mnot.
-
Making the Council's short circuit a little more flexible w3c/process#852, by @frivoal.
-
Align with Bylaws changes w3c/process#849, by @fantasai.
-
Multiple possible outcomes of a successful AC Appeal w3c/process#844, by @frivoal.
-
Dealing with procedural disagreements within the Council w3c/process#843, by @frivoal.
-
-
7 issues closed.
-
TAG appointment ambiguity about ratification by both AB and TAG w3c/process#836.
-
Retire the "Streamlined Publication Approval" system w3c/process#856.
-
Identify and (explain or change) W3C jargon words w3c/process#456.
-
Whistle blower w3c/process#481.
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779.
-
Addressing formal objections before requesting advancement w3c/process#737.
-
1 issue reopened.
-
Addressing formal objections before requesting advancement w3c/process#737, by @frivoal.
-
-
20 issues received 44 new comments.
-
Process should say how W3T can update NOTES w3c/process#120 (3 comments by @css-meeting-bot, @frivoal)
-
Ambiguity about (super) majority thresholds: of those voting, or of those eligible to vote? w3c/process#838 (3 comments by @css-meeting-bot, @frivoal)
-
Retire the "Streamlined Publication Approval" system w3c/process#856 (3 comments by @css-meeting-bot, @fantasai, @nigelmegitt)
-
Identify and (explain or change) W3C jargon words w3c/process#456 (3 comments by @css-meeting-bot, @fantasai, @frivoal)
-
Addressing formal objections before requesting advancement w3c/process#737 (3 comments by @frivoal, @jyasskin)
-
Have the normal, default, decision policy for charters in the process w3c/process#425 (3 comments by @frivoal, @svgeesus)
-
Should member submissions be removed from the Process? w3c/process#648 (3 comments by @frivoal, @nigelmegitt)
-
TAG appointment ambiguity about ratification by both AB and TAG w3c/process#836 (2 comments by @css-meeting-bot, @frivoal)
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779 (2 comments by @css-meeting-bot, @frivoal)
-
Creating a more visible banner for old process documents w3c/process#855 (2 comments by @frivoal, @plehegar)
-
Making the Council's short circuit a little more flexible w3c/process#852 (2 comments by @chaals, @frivoal)
-
Multiple possible outcomes of a successful AC Appeal w3c/process#844 (2 comments by @fantasai, @TallTed)
-
7 pull requests opened.
-
Consolidate maintenance by the Team of technical reports w3c/process#860, by @frivoal.
-
Link "Advisory Committee Review" in the Statement section. w3c/process#858, by @jyasskin.
-
Retire the Streamlined Publication Approval system w3c/process#857, by @frivoal.
-
Introduce a formal Charter Refinement phase w3c/process#851, by @frivoal.
-
Editorial rewrite of section on charter approval w3c/process#850, by @frivoal.
-
Clarifies Council votes w3c/process#842, by @frivoal.
-
Eliminate potential ambiguity in dismissal w3c/process#841, by @frivoal.
-
-
7 pull requests merged.
-
Disambiguate what "each" means in TAG appointment ratification w3c/process#837.
-
Eliminate potential ambiguity in dismissal w3c/process#841.
-
Clarifies Council votes w3c/process#842.
-
Retire the Streamlined Publication Approval system w3c/process#857.
-
Editorial rewrite of section on charter approval w3c/process#850.
-
Link "Advisory Committee Review" in the Statement section. w3c/process#858.
-
-
1 pull request closed.
-
Confidentiality Levels and Redactions w3c/process#722.
-
-
4 pull requests received 26 new comments.
-
Introduce a formal Charter Refinement phase w3c/process#851 (13 comments by @caribouW3, @fantasai, @frivoal, @TallTed)
-
Editorial rewrite of section on charter approval w3c/process#850 (10 comments by @css-meeting-bot, @fantasai, @frivoal, @TallTed)
-
Consolidate maintenance by the Team of technical reports w3c/process#860 (2 comments by @frivoal, @TallTed)
-
Past meetings
Participants
-
1 participant left.
-
Chaals Nevile (Consensys) left.
-
GitHub
w3c/process
-
4 issues opened.
-
TAG appointment ambiguity about ratification by both AB and TAG w3c/process#836, by @frivoal.
-
Description of the role of the AB w3c/process#833, by @dwsinger.
-
Determining AC Consensus of Post-Review Changes w3c/process#825, by @fantasai.
-
3 issues closed.
-
Are the rules for updating Registry Definitions appropriate? w3c/process#800.
-
Run link checker on Process Drafts w3c/process#824.
-
-
11 issues received 83 new comments.
-
Chair should be required in charter w3c/process#823 (29 comments by @chaals, @chrisn, @csarven, @css-meeting-bot, @cwilso, @dwsinger, @frivoal, @nigelmegitt, @plehegar, @samuelweiler)
-
TAG appointment ambiguity about ratification by both AB and TAG w3c/process#836 (12 comments by @css-meeting-bot, @cwilso, @frivoal, @martinthomson, @TallTed, @torgo)
-
Determining AC Consensus of Post-Review Changes w3c/process#825 (8 comments by @css-meeting-bot, @dwsinger, @frivoal, @plehegar, @TallTed)
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779 (6 comments by @dwsinger, @fantasai, @frivoal, @shawna-slh, @TallTed)
-
Ambiguity about (super) majority thresholds: of those voting, or of those eligible to vote? w3c/process#838 (5 comments by @css-meeting-bot, @fantasai, @TallTed)
-
Are the rules for updating Registry Definitions appropriate? w3c/process#800 (4 comments by @css-meeting-bot, @fantasai, @frivoal, @nigelmegitt)
-
Use Alias rather than Redirect for /Consortium/Process w3c/process#729 (3 comments by @fantasai, @frivoal, @plehegar)
-
Chair appointment community involvement, transparency, enabling objections and handling them w3c/process#281 (3 comments by @chaals, @csarven, @michaelchampion)
-
Ground the different types of groups / maturity stages in Problem Statements w3c/process#813 (1 comment by @michaelchampion)
-
-
6 pull requests opened.
-
Disambiguate what "each" means in TAG appointment ratification w3c/process#837, by @frivoal.
-
Clarify confidentiality requirements w3c/process#835, by @frivoal.
-
Create SECURITY.md w3c/process#834, by @Angelaaa0609.
-
Clarify definition of the REC-track w3c/process#831, by @frivoal.
-
Update compile.yml w3c/process#830, by @DawallAZllon91.
-
NUEVA IMPLEMENTACIÓN w3c/process#829, by @DawallAZllon91.
-
-
3 pull requests merged.
-
Clarify confidentiality requirements w3c/process#835.
-
Clarify definition of the REC-track w3c/process#831.
-
Clarify what a registry is made of w3c/process#818.
-
-
3 pull requests closed.
-
Create SECURITY.md w3c/process#834.
-
Update compile.yml w3c/process#830.
-
NUEVA IMPLEMENTACIÓN w3c/process#829.
-
-
7 pull requests received 26 new comments.
-
Clarify definition of the REC-track w3c/process#831 (10 comments by @chaals, @css-meeting-bot, @dwsinger, @fantasai, @frivoal, @sideshowbarker)
-
Disambiguate what "each" means in TAG appointment ratification w3c/process#837 (6 comments by @cwilso, @fantasai, @martinthomson, @TallTed)
-
Confidentiality Levels and Redactions w3c/process#722 (4 comments by @css-meeting-bot, @frivoal, @joshco, @nigelmegitt)
-
Improve consistency of document status names that use the word "Draft" w3c/process#819 (1 comment by @TallTed)
-
GitHub
w3c/process
-
2 issues opened.
-
Run link checker on Process Drafts w3c/process#824, by @plehegar.
-
Chair should be required in charter w3c/process#823, by @cwilso.
-
-
3 issues received 12 new comments.
-
Chair should be required in charter w3c/process#823 (7 comments by @cwilso, @frivoal, @nigelmegitt, @plehegar, @samuelweiler)
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779 (4 comments by @frivoal, @nigelmegitt)
-
Use Alias rather than Redirect for /Consortium/Process w3c/process#729 (1 comment by @vivienlacourba)
-
-
1 pull request received 1 new comment.
-
Allow Tim Berners-Lee to abstain in Unanimous Short Circuit votes w3c/process#793 (1 comment by @frivoal)
-
Past meetings
-
1 meeting.
GitHub
w3c/process
-
2 issues opened.
-
Affiliation constraints on TAG membership w3c/process#817, by @martinthomson.
-
Strip section 6.2.2.1 “wide review” of the mailing list currently mentioned w3c/process#815, by @koalie.
-
-
1 issue closed.
-
Requirement to publish formal objections should include a timeline w3c/process#735.
-
-
8 issues received 68 new comments.
-
TAG Appointment Process Shortcomings w3c/process#809 (24 comments by @chrisn, @cwilso, @dwsinger, @frivoal, @LeaVerou, @martinthomson, @mnot)
-
Are the rules for updating Registry Definitions appropriate? w3c/process#800 (10 comments by @darobin, @dwsinger, @frivoal, @nigelmegitt)
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779 (7 comments by @chrisn, @frivoal, @nigelmegitt, @TallTed)
-
Strip section 6.2.2.1 “wide review” of the mailing list currently mentioned w3c/process#815 (1 comment by @frivoal)
-
-
3 pull requests opened.
-
Improve consistency of document status names that use the word "Draft" w3c/process#819, by @frivoal.
-
Clarify what a registry is made of w3c/process#818, by @frivoal.
-
Create google.yml w3c/process#814, by @ScorpiusDraconis83.
-
-
2 pull requests merged.
-
Reduce confusion wrt registry sections #800 w3c/process#807.
-
Clarify FO publication timing #735 w3c/process#808.
-
-
1 pull request closed.
-
Create google.yml w3c/process#814.
-
-
3 pull requests received 7 new comments.