W3C Process Community Group - Activity in 2021
No matches.
Past meetings
GitHub
w3c/process
-
4 issues received 36 new comments.
-
Recusal from FO handling w3c/process#278 (33 comments by @chaals, @cwilso, @dwsinger, @jeffjaffe, @msporny, @nigelmegitt, @OR13, @rxgrant)
-
Past meetings
-
1 meeting.
Participants
-
1 participant left.
-
Alan Bird (W3C) left.
-
GitHub
w3c/process
-
6 issues opened.
-
The 2021 "Revising a Recommendation Process" is painful for WGs w3c/process#589, by @msporny.
-
Terminology for team support of the W3C Council w3c/process#588, by @jeffjaffe.
-
Cite Horizontal Review in Sec. 6.4.3 w3c/process#587, by @JaninaSajka.
-
Moving from Draft Registry to Candidate Registry w3c/process#584, by @plehegar.
-
Unintentional definitite article "the group" w3c/process#583, by @SteveALee.
-
1 issue closed.
-
Unintentional definitite article "the group" w3c/process#583.
-
-
7 issues received 105 new comments.
-
Recusal from FO handling w3c/process#278 (72 comments by @chaals, @cwilso, @dwsinger, @fantasai, @jeffjaffe, @jwrosewell, @jyasskin, @michaelchampion, @mnot, @msporny, @nigelmegitt, @OR13, @rxgrant, @TzviyaSiegman)
-
The 2021 "Revising a Recommendation Process" is painful for WGs w3c/process#589 (17 comments by @chaals, @fantasai, @frivoal, @LJWatson, @marcoscaceres, @msporny)
-
Moving from Draft Registry to Candidate Registry w3c/process#584 (7 comments by @fantasai, @frivoal, @plehegar)
-
Terminology for team support of the W3C Council w3c/process#588 (5 comments by @cwilso, @dwsinger, @frivoal, @jeffjaffe, @plehegar)
-
Simplify Process 2021 (candidate|proposed) (change|addition|correction) terminology w3c/process#590 (2 comments by @frivoal, @jeffjaffe)
-
-
2 pull requests opened.
-
Let the Team rather than the Director handle progression on TR w3c/process#586, by @frivoal.
-
Make the Team responsible for Group creation and Closure w3c/process#585, by @frivoal.
-
-
2 pull requests received 24 new comments.
-
Make the Team responsible for Group creation and Closure w3c/process#585 (17 comments by @caribouW3, @chaals, @dwsinger, @frivoal, @jeffjaffe, @jwrosewell, @LJWatson, @mnot)
-
Let the Team rather than the Director handle progression on TR w3c/process#586 (7 comments by @chaals, @dwsinger, @jeffjaffe, @jwrosewell, @LJWatson)
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Michael Staub joined.
-
GitHub
w3c/process
-
5 issues opened.
-
Representing the W3C w3c/process#582, by @mnot.
-
Sufficient time for Council Members to give decisions their full attention w3c/process#581, by @jeffjaffe.
-
Charter review process w3c/process#580, by @mnot.
-
Director responsibilities in the technical development process w3c/process#578, by @jeffjaffe.
-
All previews are 404 w3c/process#577, by @darobin.
-
-
5 issues closed.
-
External facilitation w3c/process#467.
-
All previews are 404 w3c/process#577.
-
P2021 bug in description of Rec's Patent Commitments w3c/process#570.
-
Formalise HRG as mandatory by default w3c/process#394.
-
-
14 issues received 74 new comments.
-
Recusal from FO handling w3c/process#278 (33 comments by @chaals, @cwilso, @dwsinger, @jeffjaffe, @mnot, @msporny, @OR13, @rxgrant, @TallTed)
-
Charter review process w3c/process#580 (9 comments by @cwilso, @dwsinger, @jeffjaffe, @nigelmegitt, @OR13, @torgo, @wseltzer)
-
Chair appointment community involvement, transparency, enabling objections and handling them w3c/process#281 (6 comments by @cwilso, @dwsinger, @samuelweiler)
-
Director responsibilities in the technical development process w3c/process#578 (5 comments by @cwilso, @jeffjaffe, @michaelchampion)
-
TAG and AB should be able to formally review charters w3c/process#328 (4 comments by @dwsinger, @frivoal, @mnot, @OR13)
-
Identify and (explain or change) W3C jargon words w3c/process#456 (3 comments by @dwsinger, @frivoal, @nigelmegitt)
-
-
1 pull request opened.
-
Minor editorial fixes from Process 2021 w3c/process#579, by @plehegar.
-
-
5 pull requests merged.
-
Minor editorial fixes from Process 2021 w3c/process#579.
-
Make the CEO rather than the Director responsible for MoUs w3c/process#556.
-
Let the Team handle Member Submissions w3c/process#557.
-
Move disciplinary authority and power from the Director to the CEO w3c/process#558.
-
Make the Team handle various participation-related judgement calls w3c/process#559.
-
-
2 pull requests received 4 new comments.
-
Make the CEO rather than the Director responsible for MoUs w3c/process#556 (2 comments by @dwsinger, @jeffjaffe)
Past meetings
-
1 meeting.
GitHub
w3c/process
-
1 issue opened.
-
5 issues closed.
-
Why can AC comments on CR be ignored? w3c/process#339.
-
Should the process allow REC->WD transition directly? w3c/process#103.
-
Streamlining the Process Document w3c/process#356.
-
Clarify Process for Publishing Statements from the W3C w3c/process#429.
-
Horizontal/Wide review for IG/CG/BGs? w3c/process#447.
-
-
10 issues received 24 new comments.
-
Identify and (explain or change) W3C jargon words w3c/process#456 (10 comments by @dwsinger, @frivoal, @nigelmegitt, @tabatkins, @TallTed, @tobie)
-
Order of precedence of Membership Agreement, Process document and normative references w3c/process#574 (4 comments by @dwsinger, @nigelmegitt, @plehegar)
-
[patent policy] Exclusion opportunity when work leaves a Working Group w3c/process#518 (2 comments by @css-meeting-bot, @plehegar)
-
TAG and AB should be able to formally review charters w3c/process#328 (2 comments by @dwsinger, @samuelweiler)
-
-
4 pull requests merged.
-
Require document license to go through formal approval for updates w3c/process#571.
-
Use "allow new features" terminology consistently w3c/process#567.
-
Stop excluding AC rep comments from those that have to be addressed w3c/process#563.
-
Make it possible to transition from REC to WD w3c/process#562.
-
-
2 pull requests received 3 new comments.
-
Clarify integration (and potential conflicts) between the Process and its normative references w3c/process#572 (2 comments by @jwrosewell, @nigelmegitt)
-
Past meetings
-
1 meeting.
GitHub
w3c/process
-
2 issues opened.
-
P2021 bug in description of Rec's Patent Commitments w3c/process#570, by @wseltzer.
-
Who can initiate and prepare a Charter? w3c/process#560, by @dwsinger.
-
-
2 issues closed.
-
remove "adopted draft" w3c/process#500.
-
Allow AB to choose its own chair w3c/process#223.
-
-
22 issues received 36 new comments.
-
Who can initiate and prepare a Charter? w3c/process#560 (9 comments by @dwsinger, @frivoal, @jeffjaffe, @mnot, @plehegar, @wseltzer)
-
Have the normal, default, decision policy for charters in the process w3c/process#425 (3 comments by @dwsinger, @plehegar)
-
Clarify Process for Publishing Statements from the W3C w3c/process#429 (2 comments by @dwsinger, @tobie)
-
Ensure all specs & standards have published user research? [from TAG process repo] w3c/process#551 (1 comment by @dwsinger)
-
Substantive changes undefined for Charter, Process reviews, and things other than specifications w3c/process#28 (1 comment by @frivoal)
-
Community Groups and Business Groups should be incorporated into the Process w3c/process#409 (1 comment by @dwsinger)
-
-
13 pull requests opened.
-
Require document license to go through formal approval for updates w3c/process#571, by @frivoal.
-
Correct description of Rec patent commitments w3c/process#569, by @wseltzer.
-
Use "allow new features" terminology consistently w3c/process#567, by @tidoust.
-
Fix build scripts w3c/process#566, by @frivoal.
-
Build the process without deploying in forks and pull requests w3c/process#565, by @frivoal.
-
Don't attempt to deploy Pull Requests w3c/process#564, by @frivoal.
-
Stop excluding AC rep comments from those that have to be addressed w3c/process#563, by @frivoal.
-
Make it possible to transition from REC to WD w3c/process#562, by @frivoal.
-
Make the Team handle various participation-related judgement calls w3c/process#559, by @frivoal.
-
Move disciplinary authority and power from the Director to the CEO w3c/process#558, by @frivoal.
-
Let the Team handle Member Submissions w3c/process#557, by @frivoal.
-
Make the CEO rather than the Director responsible for MoUs w3c/process#556, by @frivoal.
-
4 pull requests merged.
-
Correct description of Rec patent commitments w3c/process#569.
-
Fix build scripts w3c/process#566.
-
Build the process without deploying in forks and pull requests w3c/process#565.
-
Don't attempt to deploy Pull Requests w3c/process#564.
-
-
5 pull requests received 24 new comments.
-
Require document license to go through formal approval for updates w3c/process#571 (9 comments by @dwsinger, @fantasai, @frivoal, @jeffjaffe)
-
Clarify integration (and potential conflicts) between the Process and its normative references w3c/process#572 (9 comments by @dwsinger, @frivoal, @jeffjaffe, @wseltzer)
-
Make the Team handle various participation-related judgement calls w3c/process#559 (3 comments by @dwsinger, @jeffjaffe)
-
Past meetings
GitHub
w3c/process
-
3 issues opened.
-
Introduction text w3c/process#555, by @mnot.
-
Organisation of 3.4 "Chartered Groups: Working Groups and Interest Groups" w3c/process#554, by @mnot.
-
Archiving discussion attachments w3c/process#552, by @fantasai.
-
-
3 issues closed.
-
qualify _unfinished_ technical reports in 6.2.12.1 w3c/process#453.
-
Clarify that tooling must be accessible for people with disabilities w3c/process#537.
-
W3C Statement Comment from APA Chairs w3c/process#535.
-
-
9 issues received 24 new comments.
-
Community Groups and Business Groups should be incorporated into the Process w3c/process#409 (6 comments by @chaals, @dwsinger, @frivoal, @jeffjaffe, @mnot)
-
Archiving discussion attachments w3c/process#552 (5 comments by @dwsinger, @fantasai, @samuelweiler)
-
Organisation of 3.4 "Chartered Groups: Working Groups and Interest Groups" w3c/process#554 (4 comments by @dwsinger, @frivoal, @mnot, @TallTed)
-
qualify _unfinished_ technical reports in 6.2.12.1 w3c/process#453 (2 comments by @frivoal, @plehegar)
-
Clarify that tooling must be accessible for people with disabilities w3c/process#537 (1 comment by @frivoal)
-
Ensure all specs & standards have published user research? [from TAG process repo] w3c/process#551 (1 comment by @fantasai)
-
-
2 pull requests merged.
-
Clarification about horizontal review w3c/process#541.
-
1 pull request closed.
-
Explicitly require tools be accessible to people with disability w3c/process#538.
-
-
2 pull requests reopened.
-
Make it clear than any decision can be objected to w3c/process#299, by @frivoal.
-
Meetings of new groups are 8 weeks from charter approval w3c/process#434, by @frivoal.
-
-
3 pull requests received 16 new comments.
-
Clarification about horizontal review w3c/process#541 (10 comments by @dwsinger, @frivoal, @nigelmegitt, @plehegar, @samuelweiler)
-
Minimal edit to put emphasis on people with disabilities rather than cost for tooling accessibility w3c/process#539 (5 comments by @dwsinger, @frivoal, @LJWatson, @samuelweiler, @TzviyaSiegman)
-
Explicitly require tools be accessible to people with disability w3c/process#538 (1 comment by @frivoal)
-
Participants
-
1 participant joined.
-
Shahaf Levi (Sl's Repository Ltd) joined.
-
-
1 organization joined.
-
Sl's Repository Ltd joined.
-
GitHub
w3c/process
-
3 issues opened.
-
Ensure all specs & standards have published user research? [from TAG process repo] w3c/process#551, by @torgo.
-
AB Composition tweaks w3c/process#540, by @plehegar.
-
Clarify that tooling must be accessible for people with disabilities w3c/process#537, by @brewerj.
-
-
2 issues closed.
-
AB Composition tweaks w3c/process#540.
-
Eliminate 'hanging paragraphs' w3c/process#424.
-
-
5 issues received 11 new comments.
-
W3C Statement Comment from APA Chairs w3c/process#535 (4 comments by @brewerj, @dwsinger, @plehegar)
-
Clarify that tooling must be accessible for people with disabilities w3c/process#537 (2 comments by @brewerj, @fantasai)
-
-
6 pull requests opened.
-
Use proper email address and other minor tweaks w3c/process#550, by @plehegar.
-
Use the username 'w3cbot' to interact with GitHub w3c/process#549, by @plehegar.
-
Convert from Travis CI to GitHub actions w3c/process#548, by @plehegar.
-
Clarification about horizontal review w3c/process#541, by @frivoal.
-
Explicitly require tools be accessible to people with disability w3c/process#538, by @chaals.
-
-
3 pull requests merged.
-
Use proper email address and other minor tweaks w3c/process#550.
-
Use the username 'w3cbot' to interact with GitHub w3c/process#549.
-
Convert from Travis CI to GitHub actions w3c/process#548.
-
-
5 pull requests received 20 new comments.
-
Minimal edit to put emphasis on people with disabilities rather than cost for tooling accessibility w3c/process#539 (9 comments by @brewerj, @chaals, @dwsinger, @fantasai, @nigelmegitt)
-
Clarification about horizontal review w3c/process#541 (5 comments by @dwsinger, @frivoal, @nigelmegitt, @plehegar)
-
Explicitly require tools be accessible to people with disability w3c/process#538 (4 comments by @dwsinger, @fantasai, @frivoal, @shawna-slh)
-
Past meetings
GitHub
w3c/process
-
5 issues opened.
-
Editorial Changes are ill-defined outside of REC-track documents w3c/process#536, by @frivoal.
-
W3C Statement Comment from APA Chairs w3c/process#535, by @JaninaSajka.
-
Updating a WG Note when a Group is closed w3c/process#532, by @plehegar.
-
Grace period for attending meetings w3c/process#527, by @fantasai.
-
[minor wording] accessibility = people with disabilities w3c/process#525, by @shawna-slh.
-
-
22 issues closed.
-
Grace period for attending meetings w3c/process#527.
-
Updating a WG Note when a Group is closed w3c/process#532.
-
Problematic requirement on specifications referencing registries w3c/process#507.
-
Section 1 (Introduction) should help navigate the document w3c/process#423.
-
Recording of meetings w3c/process#334.
-
Clarify the voting process w3c/process#60.
-
"Reference Draft" and "Other Charter" w3c/process#114.
-
Increasing voter turnout in AC reviews with incentives w3c/process#410.
-
Remove the Recommendation stage, and rename CR to Recommendation w3c/process#446.
-
Draft Registry and Candidate Registry Draft w3c/process#516.
-
Naming discussion: W3C Statements w3c/process#508.
-
Abandoning a Note w3c/process#501.
-
Streamlining horizontal reviews w3c/process#347.
-
Decisions w3c/process#338.
-
Suspension / Removal for cause w3c/process#312.
-
7.1.1 Charter reviews on a public communication channel? w3c/process#38.
-
Updates to sections 5.2.2 and 2.1.3.1 w3c/process#63.
-
Who publishes Technical Reports? w3c/process#351.
-
Does the process assume all WDs are on the Rec. Track? w3c/process#236.
-
What are the rules for where/how W3C publications are developed? w3c/process#322.
-
[minor wording] accessibility = people with disabilities w3c/process#525.
-
-
27 issues received 71 new comments.
-
Grace period for attending meetings w3c/process#527 (7 comments by @chaals, @dwsinger, @frivoal, @wseltzer)
-
Updating a WG Note when a Group is closed w3c/process#532 (7 comments by @dwsinger, @frivoal, @swickr)
-
Define a role of "Alternate AC Rep" & enable them to perform AC duties when necessary w3c/process#505 (7 comments by @dwsinger, @fantasai, @frivoal, @jeffjaffe, @wseltzer)
-
7.1.1 Charter reviews on a public communication channel? w3c/process#38 (4 comments by @dwsinger, @wseltzer)
-
Increasing voter turnout in AC reviews with incentives w3c/process#410 (3 comments by @dwsinger, @palemieux)
-
Remove the Recommendation stage, and rename CR to Recommendation w3c/process#446 (3 comments by @dwsinger, @frivoal)
-
Draft Registry and Candidate Registry Draft w3c/process#516 (3 comments by @css-meeting-bot, @dwsinger)
-
Section 1 (Introduction) should help navigate the document w3c/process#423 (2 comments by @css-meeting-bot, @fantasai)
-
Should the process allow REC->WD transition directly? w3c/process#103 (2 comments by @dwsinger, @jeffjaffe)
-
Speed of resolving formal objections for new charters w3c/process#523 (2 comments by @cwilso, @mnot)
-
Community Groups and Business Groups should be incorporated into the Process w3c/process#409 (1 comment by @dwsinger)
-
-
7 pull requests opened.
-
Improve the wording on normative requirements related to registry values w3c/process#534, by @frivoal.
-
Provide facilities for the Team to maintain orphaned Notes w3c/process#533, by @frivoal.
-
45-day rejoin window w3c/process#531, by @wseltzer.
-
Rename "Other Charter" w3c/process#530, by @frivoal.
-
Reorganize the Process document w3c/process#529, by @frivoal.
-
Clarifications in the suspension/removal text w3c/process#528, by @frivoal.
-
Acknowledge existence of public channels for charter comments w3c/process#526, by @frivoal.
-
-
10 pull requests merged.
-
Reorganize the Process document w3c/process#529.
-
45-day rejoin window w3c/process#531.
-
Provide facilities for the Team to maintain orphaned Notes w3c/process#533.
-
Rewrite the introduction w3c/process#520.
-
Rename "Other Charter" w3c/process#530.
-
Clarifications in the suspension/removal text w3c/process#528.
-
Alternate AC Rep w3c/process#524.
-
Generalize where decisions can be made w3c/process#519.
-
Acknowledge existence of public channels for charter comments w3c/process#526.
-
-
1 pull request closed.
-
Proposes changes to wide/horizontal review w3c/process#401.
-
-
1 pull request reopened.
-
Meetings of new groups are 8 weeks from charter approval w3c/process#434, by @frivoal.
-
-
9 pull requests received 32 new comments.
-
Rewrite the introduction w3c/process#520 (11 comments by @dwsinger, @fantasai, @frivoal, @jeffjaffe, @nigelmegitt)
-
Clarifications in the suspension/removal text w3c/process#528 (5 comments by @dwsinger, @fantasai, @frivoal)
-
Proposes changes to wide/horizontal review w3c/process#401 (3 comments by @dwsinger, @frivoal, @LJWatson)
-
Improve the wording on normative requirements related to registry values w3c/process#534 (1 comment by @dwsinger)
-
Past meetings
-
1 meeting.
GitHub
w3c/process
-
4 issues opened.
-
Speed of resolving formal objections for new charters w3c/process#523, by @jeffjaffe.
-
Approval Vote Experiment Questions w3c/process#521, by @fantasai.
-
[patent policy] Exclusion opportunity when work leaves a Working Group w3c/process#518, by @hober.
-
Draft Registry and Candidate Registry Draft w3c/process#516, by @plehegar.
-
-
9 issues closed.
-
Survivability of registries w3c/process#330.
-
Revising a Recommendation: Substantive Changes or New Features. w3c/process#358.
-
Switching Tracks w3c/process#509.
-
Tooling Requirements w3c/process#435.
-
Improve AB Chairing text w3c/process#514.
-
Define minutes w3c/process#511.
-
Stop staggering AB/TAG election cycles w3c/process#486.
-
Keep or remove Note about delegation from CEO/Director to Team w3c/process#513.
-
-
22 issues received 75 new comments.
-
Clarify Process for Publishing Statements from the W3C w3c/process#429 (6 comments by @frivoal, @jeffjaffe, @tobie)
-
Tooling Requirements w3c/process#435 (6 comments by @cwilso, @dwsinger, @jeffjaffe, @mallory, @samuelweiler)
-
Draft Registry and Candidate Registry Draft w3c/process#516 (5 comments by @dwsinger, @fantasai, @frivoal)
-
Approval Vote Experiment Questions w3c/process#521 (4 comments by @chaals, @dwsinger, @michaelchampion, @swickr)
-
Define a role of "Alternate AC Rep" & enable them to perform AC duties when necessary w3c/process#505 (3 comments by @css-meeting-bot, @dwsinger, @wseltzer)
-
Revising a Recommendation: Substantive Changes or New Features. w3c/process#358 (2 comments by @frivoal, @jeffjaffe)
-
Naming and maturities of separate documents holding registry tables only w3c/process#503 (2 comments by @cwilso, @frivoal)
-
What are the rules for where/how W3C publications are developed? w3c/process#322 (1 comment by @frivoal)
-
Keep or remove Note about delegation from CEO/Director to Team w3c/process#513 (1 comment by @frivoal)
-
3 pull requests opened.
-
Alternate AC Rep w3c/process#524, by @wseltzer.
-
Rewrite the introduction w3c/process#520, by @frivoal.
-
Generalize where decisions can be made w3c/process#519, by @frivoal.
-
-
1 pull request merged.
-
New section on tooling w3c/process#436.
-
-
2 pull requests received 4 new comments.
Past meetings
Participants
-
1 participant joined.
-
Ghhgj Hhjj joined.
-
-
1 participant left.
-
Ghhgj Hhjj left.
-
GitHub
w3c/process
-
11 issues opened.
-
Improve AB Chairing text w3c/process#514, by @cwilso.
-
Keep or remove Note about delegation from CEO/Director to Team w3c/process#513, by @frivoal.
-
Define minutes w3c/process#511, by @fantasai.
-
The Proposed Recommendation phase is _not_ eliminated w3c/process#510, by @nigelmegitt.
-
Switching Tracks w3c/process#509, by @frivoal.
-
Naming discussion: W3C Statements w3c/process#508, by @frivoal.
-
Problematic requirement on specifications referencing registries w3c/process#507, by @fantasai.
-
https://github.com/w3c/w3process w3c/process#504, by @hinoryu.
-
Naming and maturities of separate documents holding registry tables only w3c/process#503, by @frivoal.
-
Does W3C have a gender pay gap? w3c/process#502, by @chaals.
-
-
8 issues closed.
-
Enumerate the requirements for wide review w3c/process#130.
-
The Proposed Recommendation phase is _not_ eliminated w3c/process#510.
-
Elevating a TAG document to W3C Approved Status w3c/process#461.
-
Where are registries published? w3c/process#353.
-
Does W3C have a gender pay gap? w3c/process#502.
-
https://github.com/w3c/w3process w3c/process#504.
-
-
25 issues received 124 new comments.
-
Improve AB Chairing text w3c/process#514 (38 comments by @chaals, @cwilso, @dwsinger, @fantasai, @frivoal, @jeffjaffe, @LJWatson, @michaelchampion, @mnot, @nigelmegitt, @samuelweiler)
-
Define a role of "Alternate AC Rep" & enable them to perform AC duties when necessary w3c/process#505 (19 comments by @css-meeting-bot, @cwilso, @dwsinger, @fantasai, @frivoal, @hober, @jeffjaffe, @mnot, @plehegar, @TallTed, @TzviyaSiegman, @wseltzer)
-
Proposal for a Directorate w3c/process#457 (13 comments by @cwilso, @dwsinger, @jeffjaffe, @michaelchampion, @TzviyaSiegman)
-
Recording of meetings w3c/process#334 (10 comments by @cwilso, @dontcallmedom, @dwsinger, @fantasai, @frivoal, @jeffjaffe, @wilaw)
-
Keep or remove Note about delegation from CEO/Director to Team w3c/process#513 (5 comments by @chaals, @dwsinger, @jeffjaffe, @TallTed)
-
Problematic requirement on specifications referencing registries w3c/process#507 (4 comments by @chaals, @dwsinger, @nigelmegitt)
-
Enumerate the requirements for wide review w3c/process#130 (3 comments by @dwsinger, @LJWatson, @TallTed)
-
Naming and maturities of separate documents holding registry tables only w3c/process#503 (2 comments by @dwsinger, @frivoal)
-
We need a process for handling registries, APIs and other 'enumerations' w3c/process#168 (2 comments by @frivoal, @johnfoliot)
-
What are the rules for where/how W3C publications are developed? w3c/process#322 (1 comment by @dwsinger)
-
What aspects of Registries should/may/should-not be published together? w3c/process#354 (1 comment by @frivoal)
-
-
2 pull requests opened.
-
Define minutes w3c/process#512, by @frivoal.
-
Shorten registry intro and improve statements about Patent Policy w3c/process#506, by @frivoal.
-
-
4 pull requests merged.
-
Define minutes w3c/process#512.
-
Shorten registry intro and improve statements about Patent Policy w3c/process#506.
-
Registries w3c/process#335.
-
-
3 pull requests received 60 new comments.
-
New section on tooling w3c/process#436 (24 comments by @dontcallmedom, @dwsinger, @fantasai, @frivoal, @plehegar, @sideshowbarker)
-
Define minutes w3c/process#512 (20 comments by @chaals, @dwsinger, @fantasai, @frivoal, @jeffjaffe, @nigelmegitt, @TallTed, @wseltzer)
-
Shorten registry intro and improve statements about Patent Policy w3c/process#506 (16 comments by @dwsinger, @fantasai, @frivoal, @nigelmegitt)
-
GitHub
w3c/process
-
3 issues opened.
-
Abandoning a Note w3c/process#501, by @plehegar.
-
remove "adopted draft" w3c/process#500, by @samuelweiler.
-
TAG appointment committee should exclude those also up for re-appointment w3c/process#498, by @dwsinger.
-
-
4 issues closed.
-
Decoupling Notes and REC track w3c/process#342.
-
Registries Survey w3c/process#466.
-
TAG nomination and election period are at poor times of the year w3c/process#487.
-
Clarify Team Amendments w3c/process#493.
-
-
1 issue reopened.
-
"Reference Draft" and "Other Charter" w3c/process#114, by @samuelweiler.
-
-
21 issues received 97 new comments.
-
Recording of meetings w3c/process#334 (14 comments by @dwsinger, @fantasai, @frivoal, @jeffjaffe, @jspellman, @jwrosewell, @mnot)
-
Tooling Requirements w3c/process#435 (12 comments by @dontcallmedom, @dwsinger, @fantasai, @jeffjaffe, @nigelmegitt, @wseltzer)
-
Stop staggering AB/TAG election cycles w3c/process#486 (11 comments by @chaals, @dwsinger, @fantasai, @LJWatson, @TzviyaSiegman)
-
TAG appointment committee should exclude those also up for re-appointment w3c/process#498 (10 comments by @dwsinger, @fantasai, @nigelmegitt)
-
remove "adopted draft" w3c/process#500 (8 comments by @dwsinger, @frivoal, @jeffjaffe, @samuelweiler)
-
TAG nomination and election period are at poor times of the year w3c/process#487 (6 comments by @dwsinger, @jeffjaffe, @koalie)
-
Elevating a TAG document to W3C Approved Status w3c/process#461 (6 comments by @dwsinger, @frivoal, @jeffjaffe, @LeaVerou, @nigelmegitt, @torgo)
-
"Reference Draft" and "Other Charter" w3c/process#114 (4 comments by @dwsinger, @fantasai, @plehegar, @samuelweiler)
-
Are certain (categories of) members entitled to AB/TAG representation? w3c/process#495 (3 comments by @dwsinger, @fantasai, @frivoal)
-
Decoupling Notes and REC track w3c/process#342 (3 comments by @fantasai, @frivoal, @michael-n-cooper)
-
Filling appointed TAG seats that have been vacated w3c/process#311 (3 comments by @dwsinger, @mnot, @samuelweiler)
-
We need a process for handling registries, APIs and other 'enumerations' w3c/process#168 (2 comments by @msporny, @plehegar)
-
What aspects of Registries should/may/should-not be published together? w3c/process#354 (1 comment by @cwilso)
-
-
3 pull requests merged.
-
W3C Statements (formerly Memoranda) w3c/process#489.
-
Note track w3c/process#488.
-
Distinguish Team corrections from other candidate corrections w3c/process#494.
-
-
5 pull requests received 36 new comments.
-
New section on tooling w3c/process#436 (29 comments by @chaals, @dontcallmedom, @dwsinger, @fantasai, @frivoal, @plehegar, @samuelweiler)
-
Meetings of new groups are 8 weeks from charter approval w3c/process#434 (2 comments by @dontcallmedom, @dwsinger)
-
Distinguish Team corrections from other candidate corrections w3c/process#494 (1 comment by @frivoal)
-
GitHub
w3c/process
-
6 issues opened.
-
Anonymous formal objections w3c/process#497, by @jeffjaffe.
-
Requirements for advancement to Recommendation w3c/process#496, by @plehegar.
-
Are certain (categories of) members entitled to AB/TAG representation? w3c/process#495, by @chaals.
-
Clarify Team Amendments w3c/process#493, by @fantasai.
-
Deadline for the council to process FOs w3c/process#491, by @frivoal.
-
-
5 issues closed.
-
Enable pr-preview w3c/process#417.
-
Independence of chairs w3c/process#470.
-
Bias of W3C team members w3c/process#471.
-
Reconsider incubation w3c/process#479.
-
Relations with IETF w3c/process#441.
-
-
27 issues received 136 new comments.
-
Elevating a TAG document to W3C Approved Status w3c/process#461 (34 comments by @caribouW3, @chaals, @css-meeting-bot, @cwilso, @dwsinger, @fantasai, @frivoal, @LeaVerou, @nigelmegitt, @plehegar, @torgo)
-
Recusal from FO handling w3c/process#278 (16 comments by @chaals, @dwsinger, @frivoal, @jeffjaffe, @samuelweiler)
-
Registries Survey w3c/process#466 (15 comments by @css-meeting-bot, @dwsinger, @fantasai, @frivoal, @plehegar)
-
Who publishes Technical Reports? w3c/process#351 (11 comments by @chaals, @dwsinger, @fantasai, @frivoal, @jeffjaffe)
-
Enumerate the requirements for wide review w3c/process#130 (7 comments by @dwsinger, @fantasai, @nigelmegitt)
-
Reconsider incubation w3c/process#479 (5 comments by @cwilso, @dwsinger, @jwrosewell, @LJWatson, @mnot)
-
W3C Council should be limited to one vote per member organization w3c/process#327 (4 comments by @dwsinger, @fantasai, @frivoal, @jeffjaffe)
-
Should we make it explicit that participation in the Council does not require travel? w3c/process#492 (4 comments by @cwilso, @dwsinger, @TzviyaSiegman)
-
CEO is part of the AB, and ex-officio participant in Objection Decision Committee w3c/process#284 (3 comments by @chaals, @fantasai, @jeffjaffe)
-
Deadline for the council to process FOs w3c/process#491 (3 comments by @chaals, @dwsinger, @jeffjaffe)
-
Requirements for advancement to Recommendation w3c/process#496 (2 comments by @frivoal, @nigelmegitt)
-
Are certain (categories of) members entitled to AB/TAG representation? w3c/process#495 (2 comments by @dwsinger, @michaelchampion)
-
Does the process assume all WDs are on the Rec. Track? w3c/process#236 (2 comments by @frivoal, @nigelmegitt)
-
Consensus in the TAG Appointment Committee - Formal Objections w3c/process#314 (1 comment by @frivoal)
-
-
4 pull requests opened.
-
Distinguish Team corrections from other candidate corrections w3c/process#494, by @frivoal.
-
Create .pr-preview.json w3c/process#490, by @nigelmegitt.
-
W3C Statements (formerly Memoranda) w3c/process#489, by @frivoal.
-
Note track w3c/process#488, by @frivoal.
-
-
1 pull request merged.
-
Create .pr-preview.json w3c/process#490.
-
-
4 pull requests received 12 new comments.
-
Distinguish Team corrections from other candidate corrections w3c/process#494 (2 comments by @dwsinger, @frivoal)