Advisory Board - Activity in 2022
No matches.
Participants
-
1 participant left.
-
Jeff Jaffe left.
-
GitHub
w3c-cg/PWETF
-
6 issues opened.
-
CEPC: How to politely correct someone? w3c-cg/PWETF#226, by @dbooth-boston.
-
CEPC: Assume that the audience is "intelligent but uninformed" w3c-cg/PWETF#225, by @dbooth-boston.
-
CEPC: Missing word in sentence w3c-cg/PWETF#224, by @dbooth-boston.
-
CEPC lacks a code of ethics w3c-cg/PWETF#223, by @dbooth-boston.
-
Child Care w3c-cg/PWETF#222, by @ErlindaEsco.
-
-
2 issues closed.
-
Child Care w3c-cg/PWETF#222.
-
Issues w3c-cg/PWETF#220.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Delete index.html w3c-cg/PWETF#221, by @Jillia174.
-
-
1 pull request closed.
-
Delete index.html w3c-cg/PWETF#221.
-
w3c/PWETF
-
6 issues opened.
-
CEPC: How to politely correct someone? w3c/PWETF#226, by @dbooth-boston.
-
CEPC: Assume that the audience is "intelligent but uninformed" w3c/PWETF#225, by @dbooth-boston.
-
CEPC: Missing word in sentence w3c/PWETF#224, by @dbooth-boston.
-
CEPC lacks a code of ethics w3c/PWETF#223, by @dbooth-boston.
-
Child Care w3c/PWETF#222, by @ErlindaEsco.
-
-
2 issues closed.
-
Child Care w3c/PWETF#222.
-
Issues w3c/PWETF#220.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Delete index.html w3c/PWETF#221, by @Jillia174.
-
-
1 pull request closed.
-
Delete index.html w3c/PWETF#221.
-
w3c/process
-
4 issues opened.
-
Incomplete Term Assignment Choices w3c/process#694, by @fantasai.
-
Should we create an Emeritus status for prior AB/TAG/BoD members w3c/process#689, by @tobie.
-
Should W3C continue to stagger AB/TAG elections ? w3c/process#688, by @michaelchampion.
-
Reintroduce the conditions for closure of a group w3c/process#685, by @nigelmegitt.
-
-
6 issues closed.
-
Mid-term Chair Appointment for TAG and AB w3c/process#641.
-
TAG chair selection timing w3c/process#310.
-
Chair appointments w3c/process#652.
-
The team should not be expected to recommend a disposition of an FO w3c/process#629.
-
Broken link to suspension guidelines. w3c/process#684.
-
13 issues received 118 new comments.
-
Charter Approval w3c/process#651 (28 comments by @cwilso, @dwsinger, @fantasai, @frivoal, @michaelchampion, @mnot, @nigelmegitt, @palemieux)
-
Possibly dismissing a Formal Objection before it goes to full Council? w3c/process#678 (20 comments by @chaals, @dwsinger, @frivoal, @mnot, @nigelmegitt, @palemieux, @TzviyaSiegman)
-
Should W3C continue to stagger AB/TAG elections ? w3c/process#688 (17 comments by @agreiner, @chaals, @chrisn, @cwilso, @dwsinger, @frivoal, @igarashi50, @marcoscaceres, @michaelchampion, @mprorock, @npdoty, @tobie, @wareid)
-
Ensuring charters fit the mission and values of W3C w3c/process#620 (17 comments by @chrisn, @dwsinger, @frivoal, @michaelchampion, @mnot, @nigelmegitt, @palemieux, @TzviyaSiegman)
-
Reintroduce the conditions for closure of a group w3c/process#685 (12 comments by @css-meeting-bot, @dwsinger, @fantasai, @frivoal, @nigelmegitt, @palemieux, @TallTed)
-
Should we create an Emeritus status for prior AB/TAG/BoD members w3c/process#689 (9 comments by @chaals, @dwsinger, @michaelchampion, @mnot, @tobie)
-
TAG and AB should be able to formally review charters w3c/process#328 (5 comments by @dwsinger, @michaelchampion, @nigelmegitt, @QingAn, @TzviyaSiegman)
-
The team should not be expected to recommend a disposition of an FO w3c/process#629 (2 comments by @css-meeting-bot, @frivoal)
-
“Member Consortium” vs “Member Association”—Synchronize with the Bylaws w3c/process#666 (1 comment by @css-meeting-bot)
-
-
1 pull request opened.
-
Clarify what the CR review period is w3c/process#691, by @frivoal.
-
-
3 pull requests merged.
-
Rename Member Consortia to Member Associations w3c/process#677.
-
Clarify timing of TAG and AB chair selection w3c/process#675.
-
Clarify what can be formally objected to w3c/process#674.
-
-
4 pull requests received 6 new comments.
-
Clarify timing of TAG and AB chair selection w3c/process#675 (2 comments by @css-meeting-bot, @cwilso)
-
Clarify that AC appeal requests and rationale can be shared with the Membership w3c/process#676 (1 comment by @css-meeting-bot)
-
Make the Team responsible for Group creation and Closure w3c/process#585 (1 comment by @nigelmegitt)
w3c/AB-public
-
5 issues opened.
-
Put support of human rights into our Vision? w3c/AB-public#34, by @dwsinger.
-
Don't refer to people as "other things" w3c/AB-public#32, by @cwilso.
-
Create a clearer structure for the Vision document w3c/AB-public#27, by @cwilso.
-
Trim the Introductory section of the Vision w3c/AB-public#26, by @cwilso.
-
W3C's vision should not only be "Vision on Web", but also "Vision for W3C" w3c/AB-public#25, by @dennis-dingwei.
-
-
5 issues received 6 new comments.
-
Improve Vision language to avoid colloquial or complex expressions w3c/AB-public#23 (2 comments by @dennis-dingwei, @michaelchampion)
-
W3C's vision should not only be "Vision on Web", but also "Vision for W3C" w3c/AB-public#25 (1 comment by @cwilso)
-
-
4 pull requests opened.
-
Break up a complicated bullet w3c/AB-public#31, by @mnot.
-
Finer-grained refactoring of Vision document restructuring w3c/AB-public#30, by @cwilso.
-
Cwilso refactor2 w3c/AB-public#29, by @cwilso.
-
DO NOT MERGE: Refactor sections w3c/AB-public#28, by @cwilso.
-
-
3 pull requests closed.
-
Don't refer to people as "other things" w3c/AB-public#21.
-
DO NOT MERGE: Refactor sections w3c/AB-public#28.
-
Cwilso refactor2 w3c/AB-public#29.
-
-
4 pull requests received 41 new comments.
-
Finer-grained refactoring of Vision document restructuring w3c/AB-public#30 (20 comments by @cwilso, @dwsinger)
-
DO NOT MERGE: Refactor sections w3c/AB-public#28 (16 comments by @cwilso, @dwsinger, @michaelchampion)
-
GitHub
w3c/process
-
7 issues opened.
-
Broken link to suspension guidelines. w3c/process#684, by @jyasskin.
-
[Editorial] Adjust grounding of RF distribution of specifications w3c/process#681, by @ianbjacobs.
-
[editorial] Council composition statement spends too much time on exceptions w3c/process#679, by @fantasai.
-
Possibly dismissing a Formal Objection before it goes to full Council? w3c/process#678, by @dwsinger.
-
Grace period for contributing to specifications? w3c/process#672, by @jyasskin.
-
-
11 issues closed.
-
Inconsistency in managing dissent w3c/process#624.
-
Grace period for contributing to specifications? w3c/process#672.
-
AB liaisons to the Board w3c/process#668.
-
Limit the scope of FO Council deliberations w3c/process#628.
-
Proposal for a Directorate w3c/process#457.
-
Consensus in the TAG Appointment Committee - Formal Objections w3c/process#314.
-
What can the Objection Decision Committee actually decide? w3c/process#279.
-
Generalize FO-handling w3c/process#276.
-
Deadline for the council to process FOs w3c/process#491.
-
20 issues received 52 new comments.
-
Increase size of the TAG? w3c/process#465 (9 comments by @cwilso, @darobin, @michaelchampion, @mnot, @plinss)
-
Grace period for contributing to specifications? w3c/process#672 (7 comments by @fantasai, @frivoal, @jyasskin, @TallTed)
-
AB liaisons to the Board w3c/process#668 (4 comments by @chaals, @css-meeting-bot, @dwsinger, @frivoal)
-
Clarify AC and BoD priority when signing MoUs and similar contracts w3c/process#670 (3 comments by @dwsinger, @tobie)
-
Proposal for a Directorate w3c/process#457 (3 comments by @css-meeting-bot, @fantasai, @michaelchampion)
-
Possibly dismissing a Formal Objection before it goes to full Council? w3c/process#678 (2 comments by @chaals, @dwsinger)
-
MoUs need splitting between formal contractual relationships, and true memoranda of understanding w3c/process#673 (2 comments by @dwsinger, @frivoal)
-
[meta] Eliminate role of The Director and redistribute authority from The Team to W3C members & community w3c/process#393 (2 comments by @fantasai, @frivoal)
-
“Member Consortium” vs “Member Association”—Synchronize with the Bylaws w3c/process#666 (1 comment by @fantasai)
-
Consensus in the TAG Appointment Committee - Formal Objections w3c/process#314 (1 comment by @fantasai)
-
-
4 pull requests opened.
-
Rename Member Consortia to Member Associations w3c/process#677, by @fantasai.
-
Clarify that AC appeal requests and rationale can be shared with the Membership w3c/process#676, by @frivoal.
-
Clarify timing of TAG and AB chair selection w3c/process#675, by @frivoal.
-
Clarify what can be formally objected to w3c/process#674, by @frivoal.
-
-
1 pull request merged.
-
Set up AB-BoD liaisons w3c/process#669.
-
-
5 pull requests received 8 new comments.
-
Clarify that AC appeal requests and rationale can be shared with the Membership w3c/process#676 (4 comments by @dontcallmedom, @dwsinger, @frivoal, @TallTed)
-
w3c/AB-public
-
1 issue opened.
-
Improve Vision language to avoid colloquial or complex expressions w3c/AB-public#23, by @dennis-dingwei.
-
-
3 issues received 7 new comments.
-
Define the purpose of Vision document w3c/AB-public#22 (5 comments by @dwsinger, @michaelchampion, @rigow)
-
Be more explicit about how to improve web's "integrity" w3c/AB-public#13 (1 comment by @michaelchampion)
-
-
1 pull request opened.
-
PR in preparation of Nov 30 AB meeting w3c/AB-public#24, by @avneeshsingh.
-
-
1 pull request closed.
-
PR in preparation of Nov 30 AB meeting w3c/AB-public#24.
-
-
2 pull requests received 10 new comments.
-
PR in preparation of Nov 30 AB meeting w3c/AB-public#24 (8 comments by @chrisn, @cwilso, @dwsinger, @michaelchampion, @TzviyaSiegman)
-
w3c-cg/PWETF
-
1 issue opened.
-
Child care w3c-cg/PWETF#217, by @tattman5787.
-
-
2 issues received 4 new comments.
-
1 pull request merged.
-
Update Definition of Diversity w3c-cg/PWETF#214.
-
w3c/PWETF
-
1 issue opened.
-
Child care w3c/PWETF#217, by @tattman5787.
-
-
2 issues received 4 new comments.
-
1 pull request merged.
-
Update Definition of Diversity w3c/PWETF#214.
-
GitHub
w3c/process
-
4 issues opened.
-
Clarify AC and BoD priority when signing MoUs and similar contracts w3c/process#670, by @frivoal.
-
AB liaisons to the Board w3c/process#668, by @fantasai.
-
“Member Consortium” vs “Member Association”—Synchronize with the Bylaws w3c/process#666, by @frivoal.
-
editorial: textual inconsistencies in basic-rec-track.svg w3c/process#661, by @TallTed.
-
-
17 issues closed.
-
Process details that should NOT be owned by W3M/Team/CEO w3c/process#392.
-
Director-less issues w3c/process#360.
-
The Elephant in the Director-free Room w3c/process#316.
-
Team-Appointed TAG Chair(s) w3c/process#313.
-
discipline and CEO recusal w3c/process#275.
-
Recusal from FO handling w3c/process#278.
-
Speed of resolving formal objections for new charters w3c/process#523.
-
Terminology for team support of the W3C Council w3c/process#588.
-
Recording council disagreements w3c/process#605.
-
Allow CEO to delegate position on the Council w3c/process#633.
-
What to do when there's no consensus in the Council w3c/process#280.
-
Continuity of TAG appointments w3c/process#613.
-
Clarify usage of types of CR in Rec Track Diagram w3c/process#636.
-
Improving the definition of consensus w3c/process#634.
-
27 issues received 78 new comments.
-
AB liaisons to the Board w3c/process#668 (18 comments by @chaals, @cwilso, @dwsinger, @fantasai, @frivoal, @jeffjaffe, @TzviyaSiegman)
-
What to do when there's no consensus in the Council w3c/process#280 (15 comments by @chaals, @cwilso, @fantasai, @michaelchampion, @nigelmegitt, @palemieux, @plehegar)
-
Clarify AC and BoD priority when signing MoUs and similar contracts w3c/process#670 (4 comments by @dwsinger, @frivoal, @jeffjaffe)
-
Recording council disagreements w3c/process#605 (3 comments by @css-meeting-bot, @frivoal, @plehegar)
-
Improving the definition of consensus w3c/process#634 (3 comments by @fantasai, @nigelmegitt, @palemieux)
-
Allow CEO to delegate position on the Council w3c/process#633 (2 comments by @css-meeting-bot, @plehegar)
-
“Member Consortium” vs “Member Association”—Synchronize with the Bylaws w3c/process#666 (2 comments by @dwsinger, @jeffjaffe)
-
Substantive changes undefined for Charter, Process reviews, and things other than specifications w3c/process#28 (1 comment by @frivoal)
-
Sufficient time for Council Members to give decisions their full attention w3c/process#581 (1 comment by @frivoal)
-
The team should not be expected to recommend a disposition of an FO w3c/process#629 (1 comment by @chaals)
-
-
9 pull requests opened.
-
Set up AB-BoD liaisons w3c/process#669, by @frivoal.
-
fix punc, spelling, inconsistent labels, etc. w3c/process#667, by @TallTed.
-
The council may report vote totals w3c/process#665, by @frivoal.
-
Allow the CEO to delegate their seat on the Council w3c/process#664, by @frivoal.
-
Mo u notice w3c/process#663, by @jackromo888.
-
Broaden who may propose group closure w3c/process#660, by @frivoal.
-
Clarify expectations about FO mitigations w3c/process#659, by @frivoal.
-
Remove references to the Hosts, replace with BoD w3c/process#658, by @frivoal.
-
-
12 pull requests merged.
-
The council may report vote totals w3c/process#665.
-
Remove references to the Hosts, replace with BoD w3c/process#658.
-
Clarify expectations about FO mitigations w3c/process#659.
-
Remove the Director w3c/process#644.
-
Replace the role of the Director in concluding AC Review w3c/process#646.
-
Allow the CEO to delegate their seat on the Council w3c/process#664.
-
Define CRS/CRD abbreviations, fixes #636 w3c/process#654.
-
Define editorial vs substantive changes for non-REC-track documents. w3c/process#647.
-
Refactor Group/Chair Decision Appeal and Formal Objection sections w3c/process#643.
-
Address necessary mitigations for sustained objections w3c/process#645.
-
Improving the definition of consensus w3c/process#635.
-
-
2 pull requests closed.
-
Mo u notice w3c/process#663.
-
Host-free w3c/process#657.
-
-
16 pull requests received 76 new comments.
-
fix punc, spelling, inconsistent labels, etc. w3c/process#667 (12 comments by @fantasai, @frivoal, @TallTed)
-
Adopt the W3C Council for handing Formal objections and related matters w3c/process#642 (10 comments by @chaals, @css-meeting-bot, @fantasai, @frivoal, @wseltzer)
-
Improving the definition of consensus w3c/process#635 (10 comments by @css-meeting-bot, @dwsinger, @fantasai, @frivoal, @nigelmegitt)
-
Clarify expectations about FO mitigations w3c/process#659 (8 comments by @css-meeting-bot, @fantasai, @frivoal, @nigelmegitt)
-
Rename Acknowledgement to Acceptance (for Member submission requests) w3c/process#640 (8 comments by @css-meeting-bot, @dwsinger, @jeffjaffe, @nigelmegitt, @swickr, @TallTed)
-
Remove references to the Hosts, replace with BoD w3c/process#658 (3 comments by @dwsinger, @fantasai, @frivoal)
-
Replace the role of the Director in concluding AC Review w3c/process#646 (2 comments by @css-meeting-bot)
-
Refactor Group/Chair Decision Appeal and Formal Objection sections w3c/process#643 (2 comments by @css-meeting-bot, @plehegar)
-
Define editorial vs substantive changes for non-REC-track documents. w3c/process#647 (1 comment by @css-meeting-bot)
-
Address necessary mitigations for sustained objections w3c/process#645 (1 comment by @css-meeting-bot)
-
w3c/AB-public
-
1 issue opened.
-
Define the purpose of Vision document w3c/AB-public#22, by @avneeshsingh.
-
-
1 issue received 2 new comments.
-
Is a Community Group the right place to develop our own Process? w3c/AB-public#295 (2 comments by @fantasai, @mnot)
-
Participants
-
1 participant left.
-
Tantek Çelik left.
-
GitHub
w3c/process
-
19 issues opened.
-
Closing Groups w3c/process#653, by @mnot.
-
Chair appointments w3c/process#652, by @mnot.
-
Charter Approval w3c/process#651, by @mnot.
-
Charter creation w3c/process#650, by @mnot.
-
Who convenes Workshops? w3c/process#649, by @mnot.
-
Should member submissions be removed from the Process? w3c/process#648, by @frivoal.
-
Mid-term Chair Appointment for TAG and AB w3c/process#641, by @fantasai.
-
REC track diagram does not reflect normative text w3c/process#638, by @gsnedders.
-
What is the CR Review Period? w3c/process#637, by @gsnedders.
-
Clarify usage of types of CR in Rec Track Diagram w3c/process#636, by @gsnedders.
-
Improving the definition of consensus w3c/process#634, by @frivoal.
-
Allow CEO to delegate position on the Council w3c/process#633, by @fantasai.
-
Sustaining an FO should always require super-majority support w3c/process#631, by @palemieux.
-
FO Council should not be allowed to delegate its responsibility w3c/process#630, by @palemieux.
-
The team should not be expected to recommend a disposition of an FO w3c/process#629, by @palemieux.
-
Limit the scope of FO Council deliberations w3c/process#628, by @palemieux.
-
Favoring weakest objections w3c/process#625, by @dontcallmedom.
-
Inconsistency in managing dissent w3c/process#624, by @dontcallmedom.
-
-
20 issues closed.
-
Anonymous formal objections w3c/process#497.
-
Editorial Changes are ill-defined outside of REC-track documents w3c/process#536.
-
Link to document on formal objection processing w3c/process#337.
-
TAG appointment should be via IETF style nomcom w3c/process#230.
-
CEO recusal while handling FOs w3c/process#277.
-
How does W3C Council handle membership turnover? w3c/process#290.
-
"W3C Council" may have to hear information in confidence w3c/process#291.
-
TAG Appointment Committee composition w3c/process#315.
-
W3C Council should be limited to one vote per member organization w3c/process#327.
-
Please reconsider director-free formal objection handling w3c/process#331.
-
Setup document management for director-free matters w3c/process#366.
-
TAG appointed participants announcement by Director w3c/process#368.
-
Who handles discipline when it isn't the Director? w3c/process#458.
-
Director responsibilities in the technical development process w3c/process#578.
-
FO Council should not be allowed to delegate its responsibility w3c/process#630.
-
Sustaining an FO should always require super-majority support w3c/process#631.
-
-
51 issues received 251 new comments.
-
Limit the scope of FO Council deliberations w3c/process#628 (30 comments by @caribouW3, @chaals, @dwsinger, @frivoal, @nigelmegitt, @palemieux, @plehegar)
-
Ensuring charters fit the mission and values of W3C w3c/process#620 (25 comments by @chaals, @css-meeting-bot, @dwsinger, @frivoal, @jeffjaffe, @michaelchampion, @mnot, @palemieux, @plehegar)
-
The team should not be expected to recommend a disposition of an FO w3c/process#629 (25 comments by @chaals, @dwsinger, @fantasai, @frivoal, @mnot, @nigelmegitt, @palemieux, @plehegar)
-
Inconsistency in managing dissent w3c/process#624 (22 comments by @annevk, @chaals, @dontcallmedom, @dwsinger, @frivoal, @jan-ivar, @jeffjaffe, @nigelmegitt, @TallTed)
-
What to do when there's no consensus in the Council w3c/process#280 (18 comments by @caribouW3, @chaals, @dbaron, @dwsinger, @fantasai, @hober, @mnot, @nigelmegitt, @palemieux)
-
Member submissions: can anyone else object, and if so, can they object to acceptance? w3c/process#639 (13 comments by @dwsinger, @fantasai, @frivoal, @jeffjaffe, @michaelchampion, @mnot, @palemieux)
-
Improving the definition of consensus w3c/process#634 (11 comments by @dwsinger, @fantasai, @frivoal, @jeffjaffe, @LJWatson, @michaelchampion, @palemieux)
-
Allow CEO to delegate position on the Council w3c/process#633 (11 comments by @chaals, @cwilso, @dwsinger, @fantasai, @hober, @palemieux)
-
Who convenes Workshops? w3c/process#649 (9 comments by @caribouW3, @dwsinger, @frivoal, @jeffjaffe, @mnot, @plehegar, @TallTed)
-
Should member submissions be removed from the Process? w3c/process#648 (9 comments by @dwsinger, @frivoal, @michaelchampion, @mnot, @palemieux, @TallTed)
-
REC track diagram does not reflect normative text w3c/process#638 (7 comments by @fantasai, @frivoal, @LJWatson, @plehegar)
-
FO Council should not be allowed to delegate its responsibility w3c/process#630 (6 comments by @dwsinger, @palemieux, @plehegar)
-
Favoring weakest objections w3c/process#625 (5 comments by @chaals, @jan-ivar, @jeffjaffe, @TallTed)
-
Mid-term Chair Appointment for TAG and AB w3c/process#641 (4 comments by @cwilso, @fantasai, @hober)
-
What is the CR Review Period? w3c/process#637 (4 comments by @caribouW3, @dwsinger, @frivoal, @plehegar)
-
Deadline for the council to process FOs w3c/process#491 (4 comments by @chaals, @frivoal, @jeffjaffe)
-
Speed of resolving formal objections for new charters w3c/process#523 (3 comments by @chaals, @frivoal)
-
TAG Appointment Committee composition w3c/process#315 (3 comments by @dwsinger, @fantasai, @frivoal)
-
Substantive changes undefined for Charter, Process reviews, and things other than specifications w3c/process#28 (2 comments by @fantasai, @frivoal)
-
Process details that should NOT be owned by W3M/Team/CEO w3c/process#392 (2 comments by @dwsinger, @frivoal)
-
Editorial Changes are ill-defined outside of REC-track documents w3c/process#536 (1 comment by @frivoal)
-
[director-free] Should the Council be all TAG+AB, or smaller and separately elected? w3c/process#293 (1 comment by @frivoal)
-
Consensus in the TAG Appointment Committee - Formal Objections w3c/process#314 (1 comment by @dwsinger)
-
W3C Council should be limited to one vote per member organization w3c/process#327 (1 comment by @frivoal)
-
[meta] Eliminate role of The Director and redistribute authority from The Team to W3C members & community w3c/process#393 (1 comment by @frivoal)
-
Should we make it explicit that participation in the Council does not require travel? w3c/process#492 (1 comment by @frivoal)
-
TAG appointment committee should exclude those also up for re-appointment w3c/process#498 (1 comment by @frivoal)
-
Director responsibilities in the technical development process w3c/process#578 (1 comment by @frivoal)
-
Sufficient time for Council Members to give decisions their full attention w3c/process#581 (1 comment by @frivoal)
-
Does the Council need the ability to defer decisions to someone else under some (rare) circumstances? w3c/process#618 (1 comment by @frivoal)
-
Sustaining an FO should always require super-majority support w3c/process#631 (1 comment by @fantasai)
-
CEO is part of the AB, and ex-officio participant in Objection Decision Committee w3c/process#284 (1 comment by @css-meeting-bot)
-
-
9 pull requests opened.
-
Define CRS/CRD abbreviations, fixes #636 w3c/process#654, by @fantasai.
-
Define editorial vs substantive changes for non-REC-track documents. w3c/process#647, by @fantasai.
-
Replace the role of the Director in concluding AC Review w3c/process#646, by @frivoal.
-
Address necessary mitigations for sustained objections w3c/process#645, by @frivoal.
-
Remove the Director w3c/process#644, by @frivoal.
-
Refactor Group/Chair Decision Appeal and Formal Objection sections w3c/process#643, by @frivoal.
-
Adopt the W3C Council for handing Formal objections and related matters w3c/process#642, by @frivoal.
-
Rename Acknowledgement to Acceptance (for Member submission requests) w3c/process#640, by @frivoal.
-
Improving the definition of consensus w3c/process#635, by @frivoal.
-
-
1 pull request merged.
-
Director-free TAG w3c/process#611.
-
-
1 pull request closed.
-
Change from recusal to dismissal/renunciation w3c/process#623.
-
-
5 pull requests received 33 new comments.
-
Change from recusal to dismissal/renunciation w3c/process#623 (24 comments by @chaals, @chrisn, @dwsinger, @frivoal, @nigelmegitt, @plehegar, @TallTed)
-
Define editorial vs substantive changes for non-REC-track documents. w3c/process#647 (2 comments by @dwsinger, @plehegar)
-
Adopt the W3C Council for handing Formal objections and related matters w3c/process#642 (1 comment by @dwsinger)
-
w3c-cg/PWETF
-
2 issues opened.
-
Childcare at TPAC w3c-cg/PWETF#216, by @wareid.
-
sensory rooms at TPAC w3c-cg/PWETF#213, by @TzviyaSiegman.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Update Definition of Diversity w3c-cg/PWETF#214, by @jspellman.
-
-
3 pull requests merged.
-
added personal attacks to unacceptable w3c-cg/PWETF#184.
-
threats w3c-cg/PWETF#206.
-
Adjust order + content of identity characteristics w3c-cg/PWETF#209.
-
-
1 pull request received 3 new comments.
-
Update Definition of Diversity w3c-cg/PWETF#214 (3 comments by @michael-n-cooper, @nigelmegitt, @TzviyaSiegman)
-
w3c/PWETF
-
2 issues opened.
-
Childcare at TPAC w3c/PWETF#216, by @wareid.
-
sensory rooms at TPAC w3c/PWETF#213, by @TzviyaSiegman.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Update Definition of Diversity w3c/PWETF#214, by @jspellman.
-
-
3 pull requests merged.
-
added personal attacks to unacceptable w3c/PWETF#184.
-
threats w3c/PWETF#206.
-
Adjust order + content of identity characteristics w3c/PWETF#209.
-
-
1 pull request received 3 new comments.
-
Update Definition of Diversity w3c/PWETF#214 (3 comments by @michael-n-cooper, @nigelmegitt, @TzviyaSiegman)
-
w3c/AB-public
-
1 issue received 10 new comments.
-
Is a Community Group the right place to develop our own Process? w3c/AB-public#295 (10 comments by @dwsinger, @jeffjaffe, @mnot, @palemieux, @plehegar, @TallTed)
-
-
1 pull request opened.
-
Don't refer to people as "other things" w3c/AB-public#21, by @dwsinger.
-
-
1 pull request merged.
-
Re-organize, simplify, and de-duplicate w3c/AB-public#20.
-
-
1 pull request received 3 new comments.
-
Don't refer to people as "other things" w3c/AB-public#21 (3 comments by @dwsinger, @frivoal, @tantek)
-
GitHub
w3c-cg/PWETF
-
2 pull requests opened.
-
Adjust order + content of identity characteristics w3c-cg/PWETF#209, by @jenstrickland.
-
Use "participant" rather than "member" w3c-cg/PWETF#208, by @swickr.
-
-
1 pull request merged.
-
Use "participant" rather than "member" w3c-cg/PWETF#208.
-
-
1 pull request received 3 new comments.
w3c/PWETF
-
2 pull requests opened.
-
Adjust order + content of identity characteristics w3c/PWETF#209, by @jenstrickland.
-
Use "participant" rather than "member" w3c/PWETF#208, by @swickr.
-
-
1 pull request merged.
-
Use "participant" rather than "member" w3c/PWETF#208.
-
-
1 pull request received 3 new comments.
w3c/process
-
4 issues opened.
-
Ensuring charters fit the mission and values of W3C w3c/process#620, by @michaelchampion.
-
a role should be a role, not a task w3c/process#615, by @TallTed.
-
4 issues closed.
-
Include Membership input ahead of MoU decision w3c/process#606.
-
What is and can be Member-Confidential w3c/process#601.
-
Maturity Level is a weird term w3c/process#455.
-
11 issues received 58 new comments.
-
TAG and AB should be able to formally review charters w3c/process#328 (23 comments by @chaals, @chrisn, @css-meeting-bot, @dwsinger, @frivoal, @koalie, @michaelchampion, @mnot, @plehegar)
-
Continuity of TAG appointments w3c/process#613 (12 comments by @chaals, @dwsinger, @frivoal, @plinss)
-
Does the Council need the ability to defer decisions to someone else under some (rare) circumstances? w3c/process#618 (8 comments by @css-meeting-bot, @dwsinger, @fantasai, @frivoal, @jwrosewell, @TallTed)
-
Consensus in the TAG Appointment Committee - Formal Objections w3c/process#314 (6 comments by @cwilso, @dwsinger, @frivoal, @nigelmegitt, @plehegar)
-
Should potential appointees to the TAG be required to stand for election, to be eligible for another term? w3c/process#622 (2 comments by @fantasai, @TallTed)
-
CEO is part of the AB, and ex-officio participant in Objection Decision Committee w3c/process#284 (2 comments by @dwsinger, @plehegar)
-
-
4 pull requests opened.
-
Change from recusal to dismissal/renunciation w3c/process#623, by @dwsinger.
-
Enable the Council to delegate ruling of specific FOs w3c/process#621, by @frivoal.
-
Provide an explicit advance notice period for MoUs w3c/process#619, by @frivoal.
-
editorial: rm undefined COO from informal Note w3c/process#614, by @tantek.
-
-
4 pull requests merged.
-
Enable the Council to delegate ruling of specific FOs w3c/process#621.
-
Provide an explicit advance notice period for MoUs w3c/process#619.
-
editorial: rm undefined COO from informal Note w3c/process#614.
-
Rename "maturity level" into "maturity stage" w3c/process#612.
-
-
5 pull requests received 45 new comments.
-
Director-free TAG w3c/process#611 (22 comments by @css-meeting-bot, @dwsinger, @fantasai, @frivoal, @mnot, @TallTed)
-
Enable the Council to delegate ruling of specific FOs w3c/process#621 (5 comments by @dwsinger, @frivoal, @TallTed)
-
Provide an explicit advance notice period for MoUs w3c/process#619 (4 comments by @css-meeting-bot, @frivoal, @TallTed)
-
editorial: rm undefined COO from informal Note w3c/process#614 (4 comments by @css-meeting-bot, @plehegar, @TallTed, @tantek)
-
w3c/AB-public
-
17 issues opened.
-
Add a principle of "Origin Sovereignty"? w3c/AB-public#17, by @cwilso.
-
Recognizing the value provided by the wide diversity of publishers w3c/AB-public#16, by @cwilso.
-
Clarify how web technology alone or with government aid can protect people from harm w3c/AB-public#15, by @cwilso.
-
Increase input and positivity? w3c/AB-public#14, by @cwilso.
-
Be more explicit about how to improve web's "integrity" w3c/AB-public#13, by @cwilso.
-
Strategic goals needs a revision w3c/AB-public#12, by @cwilso.
-
Add to principle around centralization w3c/AB-public#11, by @cwilso.
-
Define "industry" w3c/AB-public#10, by @cwilso.
-
Needs editorial work to reduce redundancy w3c/AB-public#9, by @cwilso.
-
Add 'industries into 3rd bullet of principles? w3c/AB-public#7, by @cwilso.
-
Extract useful points from AB discussion w3c/AB-public#6, by @cwilso.
-
Values need further specificity w3c/AB-public#5, by @cwilso.
-
Split W3C and Web principles w3c/AB-public#4, by @cwilso.
-
Purpose should encompass public at large w3c/AB-public#3, by @cwilso.
-
Vision should consider old '7 points' document w3c/AB-public#2, by @cwilso.
-
Vision should have a Glossary w3c/AB-public#1, by @cwilso.
-
-
1 issue closed.
-
Vision should consider old '7 points' document w3c/AB-public#2.
-
-
8 issues received 20 new comments.
-
Consider making thresholds relative to active participation w3c/AB-public#296 (4 comments by @dwsinger, @fantasai, @vivienlacourba)
-
Vision should have a Glossary w3c/AB-public#1 (4 comments by @cwilso, @jeffjaffe, @LJWatson, @tantek)
-
-
3 pull requests opened.
-
Re-organize, simplify, and de-duplicate w3c/AB-public#20, by @dwsinger.
-
add public to Purpose per #3 w3c/AB-public#19, by @tantek.
-
swap Strategic Goals and Identity sections w3c/AB-public#18, by @tantek.
-
-
2 pull requests merged.
-
add public to Purpose per #3 w3c/AB-public#19.
-
swap Strategic Goals and Identity sections w3c/AB-public#18.
-
-
1 pull request received 2 new comments.
GitHub
w3c/AB-public
-
1 issue received 8 new comments.
-
Consider making thresholds relative to active participation w3c/AB-public#296 (8 comments by @chaals, @css-meeting-bot, @dwsinger, @fantasai, @frivoal, @jeffjaffe)
-
w3c/process
-
2 issues opened.
-
Continuity of TAG appointments w3c/process#613, by @fantasai.
-
"approval" vs "verification" w3c/process#609, by @frivoal.
-
-
4 issues closed.
-
"approval" vs "verification" w3c/process#609.
-
Appeal process for proposals w3c/process#478.
-
Cite Horizontal Review in Sec. 6.4.3 w3c/process#587.
-
-
7 issues received 41 new comments.
-
Have the normal, default, decision policy for charters in the process w3c/process#425 (23 comments by @chaals, @dwsinger, @frivoal, @LJWatson, @nigelmegitt, @plehegar, @svgeesus)
-
"approval" vs "verification" w3c/process#609 (12 comments by @chrisn, @dwsinger, @frivoal, @nigelmegitt, @TallTed)
-
We need a process for handling registries, APIs and other 'enumerations' w3c/process#168 (2 comments by @gsnedders, @plehegar)
-
-
3 pull requests opened.
-
Rename "maturity level" into "maturity stage" w3c/process#612, by @frivoal.
-
Director-free TAG w3c/process#611, by @frivoal.
-
Use "verification" rather than "approval" w3c/process#610, by @frivoal.
-
-
1 pull request merged.
-
Use "verification" rather than "approval" w3c/process#610.
-
-
1 pull request closed.
-
Let the Team rather than the Director handle progression on TR w3c/process#586.
-
-
4 pull requests received 11 new comments.
-
Let the Team rather than the Director handle progression on TR w3c/process#586 (5 comments by @dwsinger, @frivoal, @plehegar)
-
Rename "maturity level" into "maturity stage" w3c/process#612 (2 comments by @css-meeting-bot, @dwsinger)
-
w3c-cg/PWETF
-
1 pull request opened.
-
Adding Update cadence text w3c-cg/PWETF#207, by @wareid.
-
w3c/PWETF
-
1 pull request opened.
-
Adding Update cadence text w3c/PWETF#207, by @wareid.
-
Participants
-
1 participant joined.
-
Wei Ding joined.
-
GitHub
w3c/process
-
1 issue opened.
-
Simplifying TAG Appointment Committee w3c/process#608, by @fantasai.
-
-
5 issues closed.
-
Simplifying TAG Appointment Committee w3c/process#608.
-
Stronger emphasis on reaching Recommendation w3c/process#443.
-
Superfluous information requirement in 4.5 “Charter extension” w3c/process#598.
-
Allow Chairs to suspend an individual temporarily w3c/process#592.
-
-
10 issues received 17 new comments.
-
Maturity Level is a weird term w3c/process#455 (3 comments by @css-meeting-bot, @fantasai, @plehegar)
-
Include Membership input ahead of MoU decision w3c/process#606 (3 comments by @jeffjaffe, @npdoty, @plehegar)
-
Community Groups and Business Groups should be incorporated into the Process w3c/process#409 (2 comments by @css-meeting-bot, @plehegar)
-
Allow Chairs to suspend an individual temporarily w3c/process#592 (2 comments by @frivoal, @jeffjaffe)
-
Superfluous information requirement in 4.5 “Charter extension” w3c/process#598 (1 comment by @plehegar)
-
-
1 pull request merged.
-
Simplify announcements of charter extensions w3c/process#602.
-
-
4 pull requests received 20 new comments.
-
Let the Team rather than the Director handle progression on TR w3c/process#586 (9 comments by @css-meeting-bot, @dwsinger, @frivoal, @mnot, @plehegar)
-
Issue 574, order of precedence w3c/process#599 (6 comments by @dwsinger, @fantasai, @nigelmegitt, @plehegar, @TallTed, @wseltzer)
-
Clarify integration (and potential conflicts) between the Process and its normative references w3c/process#572 (3 comments by @fantasai, @nigelmegitt, @TallTed)
-
w3c-cg/PWETF
-
2 issues opened.
-
TPAC Inclusion Fund 2022 w3c-cg/PWETF#205, by @wareid.
-
[Project] Chairs Training w3c-cg/PWETF#204, by @wareid.
-
-
1 issue closed.
-
Disinformation as unacceptable behaviour w3c-cg/PWETF#200.
-
-
3 issues received 3 new comments.
-
2 pull requests opened.
-
threats w3c-cg/PWETF#206, by @TzviyaSiegman.
-
Update "editor's draft" URI in index.html w3c-cg/PWETF#203, by @swickr.
-
-
3 pull requests merged.
-
Update "editor's draft" URI in index.html w3c-cg/PWETF#203.
-
misinfo w3c-cg/PWETF#201.
-
[glossary] make "Bullying" easier to find w3c-cg/PWETF#194.
-
-
1 pull request closed.
-
Add link for latest adopted CEPC w3c-cg/PWETF#144.
-
-
1 pull request received 1 new comment.
w3c/PWETF
-
2 issues opened.
-
TPAC Inclusion Fund 2022 w3c/PWETF#205, by @wareid.
-
[Project] Chairs Training w3c/PWETF#204, by @wareid.
-
-
1 issue closed.
-
Disinformation as unacceptable behaviour w3c/PWETF#200.
-
-
3 issues received 3 new comments.
-
2 pull requests opened.
-
threats w3c/PWETF#206, by @TzviyaSiegman.
-
Update "editor's draft" URI in index.html w3c/PWETF#203, by @swickr.
-
-
3 pull requests merged.
-
Update "editor's draft" URI in index.html w3c/PWETF#203.
-
misinfo w3c/PWETF#201.
-
[glossary] make "Bullying" easier to find w3c/PWETF#194.
-
-
1 pull request closed.
-
Add link for latest adopted CEPC w3c/PWETF#144.
-
-
1 pull request received 1 new comment.
w3c/AB-public
-
1 issue received 1 new comment.
-
Consider making thresholds relative to active participation w3c/AB-public#296 (1 comment by @frivoal)
-
GitHub
w3c/process
-
3 issues opened.
-
Include Membership input ahead of MoU decision w3c/process#606, by @dontcallmedom.
-
Recording council disagreements w3c/process#605, by @frivoal.
-
Should appeal request be shared with the Membership? w3c/process#603, by @dontcallmedom.
-
-
4 issues received 12 new comments.
-
Allow Chairs to suspend an individual temporarily w3c/process#592 (3 comments by @brewerj, @frivoal, @jeffjaffe)
-
Include Membership input ahead of MoU decision w3c/process#606 (3 comments by @dwsinger, @frivoal, @OR13)
w3c-cg/PWETF
-
1 issue opened.
-
Disinformation as unacceptable behaviour w3c-cg/PWETF#200, by @csarven.
-
-
2 issues received 3 new comments.
-
Is it possible for the CEPC to apply to bullying behaviors at an organizational level? w3c-cg/PWETF#196 (1 comment by @TzviyaSiegman)
-
2 pull requests opened.
-
Creating folder for TPAC Inclusion docs w3c-cg/PWETF#202, by @wareid.
-
misinfo w3c-cg/PWETF#201, by @TzviyaSiegman.
-
-
3 pull requests merged.
-
Creating folder for TPAC Inclusion docs w3c-cg/PWETF#202.
-
Response to feedback from PWE meeting w3c-cg/PWETF#180.
-
INCITS inclusive terminology guidelines w3c-cg/PWETF#179.
-
-
1 pull request closed.
-
Chaals patch rrs3 w3c-cg/PWETF#166.
-
-
2 pull requests received 2 new comments.
w3c/PWETF
-
1 issue opened.
-
Disinformation as unacceptable behaviour w3c/PWETF#200, by @csarven.
-
-
2 issues received 3 new comments.
-
Is it possible for the CEPC to apply to bullying behaviors at an organizational level? w3c/PWETF#196 (1 comment by @TzviyaSiegman)
-
2 pull requests opened.
-
Creating folder for TPAC Inclusion docs w3c/PWETF#202, by @wareid.
-
misinfo w3c/PWETF#201, by @TzviyaSiegman.
-
-
3 pull requests merged.
-
Creating folder for TPAC Inclusion docs w3c/PWETF#202.
-
Response to feedback from PWE meeting w3c/PWETF#180.
-
INCITS inclusive terminology guidelines w3c/PWETF#179.
-
-
1 pull request closed.
-
Chaals patch rrs3 w3c/PWETF#166.
-
-
2 pull requests received 2 new comments.
w3c/AB-public
-
1 issue opened.
-
Consider making thresholds relative to active participation w3c/AB-public#296, by @cwilso.
-
-
1 issue received 8 new comments.
-
Consider making thresholds relative to active participation w3c/AB-public#296 (8 comments by @chaals, @dwsinger, @frivoal, @jeffjaffe, @plehegar)
-
GitHub
w3c/process
-
1 issue opened.
-
What is and can be Member-Confidential w3c/process#601, by @mnot.
-
-
4 issues received 7 new comments.
-
Superfluous information requirement in 4.5 “Charter extension” w3c/process#598 (1 comment by @koalie)
-
1 pull request opened.
-
Simplify announcements of charter extensions w3c/process#602, by @frivoal.
-
GitHub
w3c/process
-
3 issues received 6 new comments.
-
Superfluous information requirement in 4.5 “Charter extension” w3c/process#598 (2 comments by @plehegar)
-
[patent policy] Exclusion opportunity when work leaves a Working Group w3c/process#518 (1 comment by @plehegar)
w3c-cg/PWETF
-
3 issues opened.
-
[ombuds] disqualifying conflicts of interest w3c-cg/PWETF#199, by @samuelweiler.
-
[ombuds] requirement to attend TPAC? w3c-cg/PWETF#198, by @samuelweiler.
-
-
1 pull request opened.
-
editorial suggestions w3c-cg/PWETF#197, by @samuelweiler.
-
-
1 pull request merged.
-
editorial suggestions w3c-cg/PWETF#197.
-
w3c/PWETF
-
3 issues opened.
-
[ombuds] disqualifying conflicts of interest w3c/PWETF#199, by @samuelweiler.
-
[ombuds] requirement to attend TPAC? w3c/PWETF#198, by @samuelweiler.
-
-
1 pull request opened.
-
editorial suggestions w3c/PWETF#197, by @samuelweiler.
-
-
1 pull request merged.
-
editorial suggestions w3c/PWETF#197.
-
GitHub
w3c/process
-
2 issues opened.
-
Superfluous information requirement in 4.5 “Charter extension” w3c/process#598, by @koalie.
-
Require registries to include "enough" standardized entries w3c/process#597, by @jyasskin.
-
-
6 issues received 22 new comments.
-
Superfluous information requirement in 4.5 “Charter extension” w3c/process#598 (9 comments by @chaals, @dwsinger, @Jotr38487, @koalie, @plehegar)
-
[patent policy] Exclusion opportunity when work leaves a Working Group w3c/process#518 (6 comments by @frivoal, @plehegar, @wseltzer)
-
Order of precedence of Membership Agreement, Process document and normative references w3c/process#574 (3 comments by @dwsinger, @nigelmegitt, @wseltzer)
-
Require registries to include "enough" standardized entries w3c/process#597 (1 comment by @dwsinger)
-
-
1 pull request opened.
-
Issue 574, order of precedence w3c/process#599, by @wseltzer.
-
-
1 pull request received 1 new comment.
GitHub
w3c/process
-
2 issues opened.
-
Recommendation track diagram does not show Rec maintenance w3c/process#596, by @svgeesus.
-
Allow Chairs to suspend an individual temporarily w3c/process#592, by @plehegar.
-
-
4 issues closed.
-
Requirements for advancement to Recommendation w3c/process#496.
-
Archiving discussion attachments w3c/process#552.
-
Moving from Draft Registry to Candidate Registry w3c/process#584.
-
-
11 issues received 34 new comments.
-
Allow Chairs to suspend an individual temporarily w3c/process#592 (16 comments by @brewerj, @chaals, @cwilso, @dwsinger, @frivoal, @jeffjaffe, @michael-n-cooper, @nigelmegitt, @plehegar, @rachaelbradley, @TallTed)
-
The 2021 "Revising a Recommendation Process" is painful for WGs w3c/process#589 (7 comments by @frivoal, @jyasskin, @marcoscaceres, @msporny, @plehegar)
-
Ensure all specs & standards have published user research? [from TAG process repo] w3c/process#551 (1 comment by @dwsinger)
-
Are certain (categories of) members entitled to AB/TAG representation? w3c/process#495 (1 comment by @dwsinger)
-
-
1 pull request opened.
-
Expect supporting materials to be archived w3c/process#591, by @frivoal.
-
-
2 pull requests merged.
-
Make the Team responsible for Group creation and Closure w3c/process#585.
-
Expect supporting materials to be archived w3c/process#591.
-
-
2 pull requests received 4 new comments.
-
Expect supporting materials to be archived w3c/process#591 (3 comments by @frivoal, @samuelweiler, @TallTed)
-
w3c-cg/PWETF
-
1 issue received 1 new comment.
w3c/PWETF
-
1 issue received 1 new comment.