Advisory Board - Activity in 2023
No matches.
Past meetings
GitHub
w3c/process
-
5 issues opened.
-
Are TAG Appointments mandatory for the Team to fill? w3c/process#811, by @martinthomson.
-
AB Role in TAG Appointment w3c/process#810, by @martinthomson.
-
TAG Appointment Process Shortcomings w3c/process#809, by @martinthomson.
-
What kind of Group is for what kind of work? w3c/process#804, by @frivoal.
-
4 issues closed.
-
What's the point of what the Process has to say about Liasons? w3c/process#422.
-
Remove normative keywords from non-normative sections w3c/process#745.
-
W3C Decision needs better cross-referencing w3c/process#802.
-
AC Review is missing a step to resolve formal objections w3c/process#739.
-
-
15 issues received 51 new comments.
-
AB Role in TAG Appointment w3c/process#810 (12 comments by @cwilso, @dwsinger, @frivoal, @martinthomson, @nigelmegitt, @plehegar, @TallTed)
-
What's the point of what the Process has to say about Liasons? w3c/process#422 (8 comments by @chrisn, @css-meeting-bot, @dwsinger, @frivoal, @joshco, @samuelweiler, @TallTed)
-
Remove normative keywords from non-normative sections w3c/process#745 (5 comments by @frivoal, @TallTed)
-
Addressing formal objections before requesting advancement w3c/process#737 (4 comments by @fantasai, @frivoal, @jyasskin)
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779 (4 comments by @csarven, @dwsinger, @fantasai, @frivoal)
-
Ground the different types of groups / maturity stages in Problem Statements w3c/process#813 (3 comments by @frivoal, @michaelchampion, @TallTed)
-
Closing a group prior to the date specified in the charter should be a "Team Decision", not a "W3C Decision" w3c/process#797 (3 comments by @chaals, @fantasai, @plehegar)
-
W3C Decision needs better cross-referencing w3c/process#802 (3 comments by @css-meeting-bot, @fantasai, @frivoal)
-
AC Review is missing a step to resolve formal objections w3c/process#739 (2 comments by @fantasai, @jyasskin)
-
Requirement to publish formal objections should include a timeline w3c/process#735 (2 comments by @fantasai)
-
Link for "W3C Horizontal Groups" doesn't describe W3C horizontal groups w3c/process#769 (1 comment by @fantasai)
-
Are the rules for updating Registry Definitions appropriate? w3c/process#800 (1 comment by @fantasai)
-
-
4 pull requests opened.
-
Clarify FO publication timing #735 w3c/process#808, by @fantasai.
-
Reduce confusion wrt registry sections #800 w3c/process#807, by @fantasai.
-
Improve headings in AC Review section #802 w3c/process#806, by @fantasai.
-
Eliminate a number of non-normative uses of rfc2119 language w3c/process#803, by @frivoal.
-
-
2 pull requests merged.
-
Eliminate a number of non-normative uses of rfc2119 language w3c/process#803.
-
Improve headings in AC Review section #802 w3c/process#806.
-
-
1 pull request closed.
-
Issue 574, order of precedence w3c/process#599.
-
-
4 pull requests received 45 new comments.
-
Reduce confusion wrt registry sections #800 w3c/process#807 (20 comments by @chrisn, @dwsinger, @fantasai, @frivoal, @nigelmegitt)
-
Eliminate a number of non-normative uses of rfc2119 language w3c/process#803 (17 comments by @chrisn, @css-meeting-bot, @dwsinger, @fantasai, @frivoal, @jyasskin, @TallTed)
-
Clarify FO publication timing #735 w3c/process#808 (7 comments by @css-meeting-bot, @cwilso, @fantasai, @frivoal, @jyasskin)
-
w3c/AB-public
-
1 issue closed.
-
The point of standards is to create and ensure interoperability w3c/AB-public#112.
-
-
4 issues received 14 new comments.
-
Making the Vision suitable for use by W3C Inc. w3c/AB-public#145 (4 comments by @cwilso, @michaelchampion, @mnot)
-
The point of standards is to create and ensure interoperability w3c/AB-public#112 (1 comment by @cwilso)
-
1 pull request received 4 new comments.
-
Clarify purpose and practice of ensuring interoperability. #120 w3c/AB-public#136 (4 comments by @cwilso, @dwsinger, @fantasai)
-
w3c-cg/PWETF
-
1 issue opened.
-
3.2.21 Intentionally or unintentional, unintentionally making assumptions w3c-cg/PWETF#363, by @lwolberg.
-
-
1 issue received 1 new comment.
-
3.2.21 Intentionally or unintentional, unintentionally making assumptions w3c-cg/PWETF#363 (1 comment by @wareid)
-
w3c/PWETF
-
1 issue opened.
-
1 issue received 1 new comment.
-
3.2.21 Intentionally or unintentional, unintentionally making assumptions w3c/PWETF#363 (1 comment by @wareid)
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Seth Dobbs joined.
-
GitHub
w3c-cg/PWETF
-
1 issue opened.
-
Regarding the Promotion of Racial Categorization in Pursuit of Diversity w3c-cg/PWETF#362, by @fantasai.
-
-
1 issue closed.
-
Regarding the Promotion of Racial Categorization in Pursuit of Diversity w3c-cg/PWETF#362.
-
-
2 issues received 27 new comments.
-
Regarding the Promotion of Racial Categorization in Pursuit of Diversity w3c-cg/PWETF#362 (24 comments by @chaals, @dbooth-boston, @dontcallmedom, @fantasai, @frivoal, @jenstrickland, @nigelmegitt, @npdoty, @torgo, @TzviyaSiegman, @wareid)
-
Revise definition of Diversity in the Glossary w3c-cg/PWETF#342 (3 comments by @chaals, @frivoal, @jenstrickland)
-
w3c/PWETF
-
1 issue opened.
-
1 issue closed.
-
2 issues received 27 new comments.
-
Regarding the Promotion of Racial Categorization in Pursuit of Diversity w3c/PWETF#362 (24 comments by @chaals, @dbooth-boston, @dontcallmedom, @fantasai, @frivoal, @jenstrickland, @nigelmegitt, @npdoty, @torgo, @TzviyaSiegman, @wareid)
-
Revise definition of Diversity in the Glossary w3c/PWETF#342 (3 comments by @chaals, @frivoal, @jenstrickland)
-
w3c/AB-public
-
2 issues opened.
-
Making the Vision suitable for use by W3C Inc. w3c/AB-public#145, by @mnot.
-
The Vision for the Web doesn't include growing its scope w3c/AB-public#143, by @dontcallmedom.
-
-
3 issues received 8 new comments.
-
Making the Vision suitable for use by W3C Inc. w3c/AB-public#145 (6 comments by @chaals, @cwilso, @dwsinger, @michaelchampion, @mnot)
-
-
1 pull request opened.
-
add link to latest published draft w3c/AB-public#144, by @tantek.
-
-
1 pull request merged.
-
add link to latest published draft w3c/AB-public#144.
-
w3c/process
-
2 issues opened.
-
W3C Decision needs better cross-referencing w3c/process#802, by @fantasai.
-
Are the rules for updating Registry Definitions appropriate? w3c/process#800, by @nigelmegitt.
-
-
3 issues closed.
-
Stop citing the "superseded" TAG charter w3c/process#794.
-
-
5 issues received 21 new comments.
-
Are the rules for updating Registry Definitions appropriate? w3c/process#800 (9 comments by @dwsinger, @fantasai, @nigelmegitt, @TallTed)
-
Order of precedence of Membership Agreement, Process document and normative references w3c/process#574 (6 comments by @fantasai, @jwrosewell, @plehegar)
-
Closing a group prior to the date specified in the charter should be a "Team Decision", not a "W3C Decision" w3c/process#797 (4 comments by @css-meeting-bot, @fantasai, @koalie, @plehegar)
-
Requirement to publish formal objections should include a timeline w3c/process#735 (1 comment by @css-meeting-bot)
-
-
1 pull request merged.
-
1 pull request closed.
-
3 pull requests received 4 new comments.
-
Enable Team to replace defunct registry custodians when no-one else can w3c/process#790 (2 comments by @css-meeting-bot, @TallTed)
-
Exclude TAG/AB from voting on their own decisions/proposals. #749 w3c/process#761 (1 comment by @nabilaljordan)
-
Clarify integration (and potential conflicts) between the Process and its normative references w3c/process#572 (1 comment by @frivoal)
-
TR publications
-
1 document published.
-
Vision for W3C published as a Draft Note. History of Vision for W3C
-
Past meetings
-
1 meeting.
GitHub
w3c/process
-
3 issues opened.
-
Stop citing the "superseded" TAG charter w3c/process#794, by @jyasskin.
-
Disciplinary action w3c/process#786, by @mnot.
-
4 issues closed.
-
Conflict of Interest in Council composition w3c/process#749.
-
Dismissal voting w3c/process#748.
-
11 issues received 15 new comments.
-
Council Composition requirements include Tim Berners-Lee, TAG life member w3c/process#784 (2 comments by @css-meeting-bot, @frivoal)
-
Order of precedence of Membership Agreement, Process document and normative references w3c/process#574 (2 comments by @frivoal, @rigow)
-
Closing a group prior to the date specified in the charter should be a "Team Decision", not a "W3C Decision" w3c/process#797 (1 comment by @koalie)
-
AC Review is missing a step to resolve formal objections w3c/process#739 (1 comment by @css-meeting-bot)
-
"Regression on the REC track" should say what kind of approval is needed w3c/process#741 (1 comment by @css-meeting-bot)
-
Mandate default custodianship for Registries if the specified custodian is no longer available w3c/process#699 (1 comment by @css-meeting-bot)
-
living standard / candidate review snapshots need to address wide review issues w3c/process#781 (1 comment by @css-meeting-bot)
-
7 pull requests opened.
-
Allow Tim Berners-Lee to abstain in Unanimous Short Circuit votes w3c/process#793, by @frivoal.
-
Limit the involvement of Tim Berners-Lee to the TAG proper w3c/process#792, by @frivoal.
-
Adjust the status of Tim Berners-Lee in the TAG w3c/process#791, by @frivoal.
-
Enable Team to replace defunct registry custodians when no-one else can w3c/process#790, by @frivoal.
-
[editorial] More explicitly Trigger FO handling process w3c/process#789, by @frivoal.
-
Clarify approvals of TAG+AB for REC track regression w3c/process#788, by @frivoal.
-
Progress on issues w3c/process#787, by @frivoal.
-
-
5 pull requests merged.
-
[editorial] More explicitly Trigger FO handling process w3c/process#789.
-
Progress on issues w3c/process#787.
-
Clarify approvals of TAG+AB for REC track regression w3c/process#788.
-
Exclude TAG/AB from voting on their own decisions/proposals. #749 w3c/process#761.
-
Must report dismissal vote counts. #748 w3c/process#760.
-
-
7 pull requests received 27 new comments.
-
Enable Team to replace defunct registry custodians when no-one else can w3c/process#790 (15 comments by @dwsinger, @nigelmegitt, @TallTed)
-
Allow Tim Berners-Lee to abstain in Unanimous Short Circuit votes w3c/process#793 (4 comments by @dwsinger, @frivoal, @nigelmegitt)
-
Limit the involvement of Tim Berners-Lee to the TAG proper w3c/process#792 (4 comments by @chaals, @dwsinger, @frivoal, @nigelmegitt)
-
Exclude TAG/AB from voting on their own decisions/proposals. #749 w3c/process#761 (1 comment by @frivoal)
-
w3c-cg/PWETF
-
3 issues opened.
-
Participation in mediation processes w3c-cg/PWETF#360, by @wareid.
-
Confidentiality policy for CoC violations w3c-cg/PWETF#359, by @wareid.
-
Outline for Dispute Resolution Document w3c-cg/PWETF#349, by @jenstrickland.
-
-
2 issues closed.
-
Revise definition of Diversity in the Glossary w3c-cg/PWETF#342.
-
2 issues received 5 new comments.
-
Separating dispute resolution from CoC violations w3c-cg/PWETF#348 (4 comments by @dbooth-boston, @nigelmegitt, @swickr)
-
Shorten "ombudspeople" to "ombuds", etc. and use consistent capitalization w3c-cg/PWETF#339 (1 comment by @dbooth-boston)
-
-
8 pull requests opened.
-
Update DraftOmbudsJobDescription.md w3c-cg/PWETF#358, by @TzviyaSiegman.
-
Editorial change to sustained disruption w3c-cg/PWETF#357, by @wareid.
-
Creating new conflict resolution document w3c-cg/PWETF#356, by @wareid.
-
Update change log with latest substantive changes w3c-cg/PWETF#355, by @wareid.
-
Editorial in CoC w3c-cg/PWETF#352, by @koalie.
-
QA in the CoC w3c-cg/PWETF#351, by @koalie.
-
fixed link in README.md w3c-cg/PWETF#350, by @koalie.
-
-
9 pull requests merged.
-
Creating new conflict resolution document w3c-cg/PWETF#356.
-
Update DraftOmbudsJobDescription.md w3c-cg/PWETF#358.
-
Editorial change to sustained disruption w3c-cg/PWETF#357.
-
Update change log with latest substantive changes w3c-cg/PWETF#355.
-
Editorial in CoC w3c-cg/PWETF#352.
-
QA on CoC w3c-cg/PWETF#353.
-
QA in the CoC w3c-cg/PWETF#351.
-
fixed link in README.md w3c-cg/PWETF#350.
-
Revised Definition for Diversity (Issue 342) w3c-cg/PWETF#345.
-
-
1 pull request received 51 new comments.
-
Creating new conflict resolution document w3c-cg/PWETF#356 (51 comments by @dbooth-boston, @jenstrickland, @rachelyager-nyc, @TzviyaSiegman, @wareid)
-
w3c/PWETF
-
3 issues opened.
-
Participation in mediation processes w3c/PWETF#360, by @wareid.
-
Confidentiality policy for CoC violations w3c/PWETF#359, by @wareid.
-
Outline for Dispute Resolution Document w3c/PWETF#349, by @jenstrickland.
-
-
2 issues closed.
-
Revise definition of Diversity in the Glossary w3c/PWETF#342.
-
2 issues received 5 new comments.
-
Separating dispute resolution from CoC violations w3c/PWETF#348 (4 comments by @dbooth-boston, @nigelmegitt, @swickr)
-
Shorten "ombudspeople" to "ombuds", etc. and use consistent capitalization w3c/PWETF#339 (1 comment by @dbooth-boston)
-
-
8 pull requests opened.
-
Update DraftOmbudsJobDescription.md w3c/PWETF#358, by @TzviyaSiegman.
-
Editorial change to sustained disruption w3c/PWETF#357, by @wareid.
-
Creating new conflict resolution document w3c/PWETF#356, by @wareid.
-
Update change log with latest substantive changes w3c/PWETF#355, by @wareid.
-
Editorial in CoC w3c/PWETF#352, by @koalie.
-
QA in the CoC w3c/PWETF#351, by @koalie.
-
fixed link in README.md w3c/PWETF#350, by @koalie.
-
-
9 pull requests merged.
-
Creating new conflict resolution document w3c/PWETF#356.
-
Update DraftOmbudsJobDescription.md w3c/PWETF#358.
-
Editorial change to sustained disruption w3c/PWETF#357.
-
Update change log with latest substantive changes w3c/PWETF#355.
-
Editorial in CoC w3c/PWETF#352.
-
QA on CoC w3c/PWETF#353.
-
QA in the CoC w3c/PWETF#351.
-
fixed link in README.md w3c/PWETF#350.
-
Revised Definition for Diversity (Issue 342) w3c/PWETF#345.
-
-
1 pull request received 51 new comments.
-
Creating new conflict resolution document w3c/PWETF#356 (51 comments by @dbooth-boston, @jenstrickland, @rachelyager-nyc, @TzviyaSiegman, @wareid)
-
w3c/AB-public
-
5 issues opened.
-
interoperability across our work - architectural "integrity" w3c/AB-public#141, by @chaals.
-
Clarify the role of Ethical Web Principles w3c/AB-public#140, by @chaals.
-
fine-grained anchors w3c/AB-public#139, by @frivoal.
-
Where to define *what* we do w3c/AB-public#137, by @frivoal.
-
How to publish, goals w3c/AB-public#135, by @TzviyaSiegman.
-
-
10 issues closed.
-
fine-grained anchors w3c/AB-public#139.
-
Laws then consensus w3c/AB-public#98.
-
emphasis on industry w3c/AB-public#75.
-
Vision: distinguish between vision as an org vs vision of our output w3c/AB-public#72.
-
Clarify intended use of the Vision document w3c/AB-public#53.
-
Recognizing the value provided by the wide diversity of publishers w3c/AB-public#16.
-
Define "industry" w3c/AB-public#10.
-
Publication of "History" w3c/AB-public#105.
-
The "History" is not agreed: empty the document and abandon the effort w3c/AB-public#130.
-
We should start the formatting of the Vision as a (Draft) Note w3c/AB-public#73.
-
-
21 issues received 65 new comments.
-
"supports truth over falsehood" may read like censorship w3c/AB-public#113 (10 comments by @darobin, @dwsinger, @mnot, @TzviyaSiegman)
-
Multiple implementations point w3c/AB-public#120 (8 comments by @chaals, @csarven, @fantasai, @igarashi50, @TzviyaSiegman)
-
shared values and consensus w3c/AB-public#129 (6 comments by @chaals, @dwsinger, @fantasai, @frivoal, @mnot, @TzviyaSiegman)
-
How to publish, goals w3c/AB-public#135 (6 comments by @chaals, @cwilso, @dwsinger, @fantasai, @michaelchampion)
-
The point of standards is to create and ensure interoperability w3c/AB-public#112 (6 comments by @cwilso, @dwsinger, @TzviyaSiegman)
-
smoke-testing the values... w3c/AB-public#126 (4 comments by @chaals, @dwsinger, @michaelchampion, @TzviyaSiegman)
-
The "History" is not agreed: empty the document and abandon the effort w3c/AB-public#130 (3 comments by @chaals, @cwilso, @michaelchampion)
-
Vision: distinguish between vision as an org vs vision of our output w3c/AB-public#72 (2 comments by @cwilso, @TzviyaSiegman)
-
Resolve issues associated with antitrust before progressing further w3c/AB-public#80 (1 comment by @chaals)
-
Recognizing the value provided by the wide diversity of publishers w3c/AB-public#16 (1 comment by @TzviyaSiegman)
-
-
4 pull requests opened.
-
Add anchors for each entry in the Operational Principles section w3c/AB-public#142, by @frivoal.
-
Capture what we do, not just how we do it, in the Vision for W3C #119 #118 w3c/AB-public#138, by @fantasai.
-
Clarify purpose and practice of ensuring interoperability. #120 w3c/AB-public#136, by @fantasai.
-
Writing from a position of greater humility w3c/AB-public#134, by @darobin.
-
-
3 pull requests merged.
-
Add anchors for each entry in the Operational Principles section w3c/AB-public#142.
-
Attempt to address #118 w3c/AB-public#128.
-
Discontinue the Editor's Draft of "History" w3c/AB-public#132.
-
-
2 pull requests closed.
-
Writing from a position of greater humility w3c/AB-public#134.
-
Add non-goals w3c/AB-public#133.
-
-
4 pull requests received 22 new comments.
-
Writing from a position of greater humility w3c/AB-public#134 (16 comments by @cwilso, @darobin, @dwsinger, @michaelchampion, @mnot, @TzviyaSiegman, @wareid)
-
Clarify purpose and practice of ensuring interoperability. #120 w3c/AB-public#136 (2 comments by @chaals)
-
Capture what we do, not just how we do it, in the Vision for W3C #119 #118 w3c/AB-public#138 (1 comment by @frivoal)
-
w3c/standards-track
-
1 issue opened.
-
Updates for Director-free process changes w3c/standards-track#30, by @svgeesus.
-
-
1 issue closed.
-
Updates for Director-free process changes w3c/standards-track#30.
-
-
1 issue received 1 new comment.
-
needs a README with short summary and link to actual readable document w3c/standards-track#28 (1 comment by @svgeesus)
-
-
2 pull requests opened.
-
add link per issue #28 w3c/standards-track#32, by @tantek.
-
Updates for Director-free process changes, fix #30 w3c/standards-track#31, by @svgeesus.
-
-
2 pull requests merged.
-
Updates for Director-free process changes, fix #30 w3c/standards-track#31.
-
fix typo w3c/standards-track#22.
-
-
1 pull request received 7 new comments.
-
Updates for Director-free process changes, fix #30 w3c/standards-track#31 (7 comments by @plehegar, @svgeesus)
-
Past meetings
-
1 meeting.
GitHub
w3c/process
-
1 issue opened.
-
Council Composition requirements include Tim Berners-Lee, TAG life member w3c/process#784, by @plehegar.
-
-
1 issue closed.
-
Define "joint deliverables" w3c/process#754.
-
-
11 issues received 24 new comments.
-
"Wide review" is too easy to confuse with "horizontal review" w3c/process#776 (5 comments by @dwsinger, @nigelmegitt, @plehegar)
-
living standard / candidate review snapshots need to address wide review issues w3c/process#781 (3 comments by @michaelchampion, @npdoty, @plehegar)
-
Council Composition requirements include Tim Berners-Lee, TAG life member w3c/process#784 (3 comments by @frivoal, @plehegar)
-
Order of precedence of Membership Agreement, Process document and normative references w3c/process#574 (2 comments by @plehegar)
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779 (2 comments by @dwsinger, @fantasai)
-
The 2021 "Revising a Recommendation Process" is painful for WGs w3c/process#589 (1 comment by @plehegar)
-
Clarify and simplify the sections regarding publication and process 2021 w3c/process#700 (1 comment by @wareid)
-
Chair appointment community involvement, transparency, enabling objections and handling them w3c/process#281 (1 comment by @jyasskin)
-
-
1 pull request opened.
-
update link to W3C submissions w3c/process#783, by @deniak.
-
-
1 pull request merged.
-
update link to W3C submissions w3c/process#783.
-
w3c/AB-public
-
6 issues opened.
-
[Vision] Remove the link to the History w3c/AB-public#131, by @chaals.
-
The "History" is not agreed: empty the document and abandon the effort w3c/AB-public#130, by @chaals.
-
shared values and consensus w3c/AB-public#129, by @mnot.
-
translating documents in development w3c/AB-public#127, by @chaals.
-
smoke-testing the values... w3c/AB-public#126, by @chaals.
-
“Vision for W3C” ↔ “Vision for the W3C” w3c/AB-public#121, by @j9t.
-
-
8 issues closed.
-
[Vision] Remove the link to the History w3c/AB-public#131.
-
Remove reference to the Ethical Web Principles w3c/AB-public#81.
-
Include a Reference to UN Declaration on Human Rights in Vision Doc w3c/AB-public#115.
-
Feedback on “different approaches” w3c/AB-public#108.
-
Awkward sentence w3c/AB-public#116.
-
Improve readability of the operational principles section w3c/AB-public#114.
-
Feedback on Vision document w3c/AB-public#104.
-
“Vision for W3C” ↔ “Vision for the W3C” w3c/AB-public#121.
-
-
1 issue reopened.
-
"supports truth over falsehood" may read like censorship w3c/AB-public#113, by @cwilso.
-
-
18 issues received 82 new comments.
-
"supports truth over falsehood" may read like censorship w3c/AB-public#113 (14 comments by @chaals, @cwilso, @darobin, @dontcallmedom, @dwsinger, @mnot, @swickr, @wareid)
-
smoke-testing the values... w3c/AB-public#126 (13 comments by @AramZS, @chaals, @chrisn, @darobin, @michaelchampion, @mnot, @TzviyaSiegman)
-
Multiple implementations point w3c/AB-public#120 (12 comments by @chaals, @cwilso, @dwsinger, @fantasai, @igarashi50, @michaelchampion, @TzviyaSiegman, @wareid)
-
The "History" is not agreed: empty the document and abandon the effort w3c/AB-public#130 (7 comments by @chaals, @cwilso, @dwsinger, @frivoal)
-
Include a Reference to UN Declaration on Human Rights in Vision Doc w3c/AB-public#115 (4 comments by @cwilso, @dwsinger, @torgo)
-
DRM/Copyright and our position in the Vision w3c/AB-public#96 (4 comments by @chaals, @cwilso, @igarashi50)
-
The point of standards is to create and ensure interoperability w3c/AB-public#112 (3 comments by @dwsinger, @frivoal, @swickr)
-
Vision: distinguish between vision as an org vs vision of our output w3c/AB-public#72 (2 comments by @dwsinger, @nigelmegitt)
-
-
7 pull requests opened.
-
Add non-goals w3c/AB-public#133, by @cwilso.
-
Discontinue the Editor's Draft of "History" w3c/AB-public#132, by @frivoal.
-
Attempt to address #118 w3c/AB-public#128, by @cwilso.
-
Facts over falsehood w3c/AB-public#125, by @cwilso.
-
Principles titling w3c/AB-public#124, by @cwilso.
-
First cut at titling operational principles w3c/AB-public#123, by @cwilso.
-
Horizontal review point w3c/AB-public#122, by @cwilso.
-
-
3 pull requests merged.
-
Horizontal review point w3c/AB-public#122.
-
Facts over falsehood w3c/AB-public#125.
-
Principles titling w3c/AB-public#124.
-
-
1 pull request closed.
-
First cut at titling operational principles w3c/AB-public#123.
-
-
3 pull requests received 17 new comments.
w3c-cg/PWETF
-
2 issues opened.
-
Separating dispute resolution from CoC violations w3c-cg/PWETF#348, by @dbooth-boston.
-
Scribe Training w3c-cg/PWETF#347, by @wareid.
-
-
1 issue received 1 new comment.
-
1 pull request received 7 new comments.
-
Revised Definition for Diversity (Issue 342) w3c-cg/PWETF#345 (7 comments by @cwilso, @dbooth-boston, @TzviyaSiegman, @wareid)
-
w3c/PWETF
-
2 issues opened.
-
Separating dispute resolution from CoC violations w3c/PWETF#348, by @dbooth-boston.
-
Scribe Training w3c/PWETF#347, by @wareid.
-
-
1 issue received 1 new comment.
-
1 pull request received 7 new comments.
-
Revised Definition for Diversity (Issue 342) w3c/PWETF#345 (7 comments by @cwilso, @dbooth-boston, @TzviyaSiegman, @wareid)
-
Vision Task Force
Past meetings
-
1 meeting of the Vision Task Force.
Past meetings
-
1 meeting.
Participants
-
1 chair appointed.
-
Wendy Reid became a chair.
-
-
1 chair stepped down.
-
Chris Wilson stepped down as a chair.
-
-
2 participants left.
-
Heejin Chung left.
-
Chaals Nevile left.
-
GitHub
w3c/process
-
2 issues opened.
-
living standard / candidate review snapshots need to address wide review issues w3c/process#781, by @npdoty.
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779, by @shawna-slh.
-
-
3 issues received 16 new comments.
-
living standard / candidate review snapshots need to address wide review issues w3c/process#781 (8 comments by @dwsinger, @frivoal, @michaelchampion, @npdoty)
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779 (3 comments by @fantasai, @koalie, @shawna-slh)
-
-
1 pull request received 1 new comment.
-
Clarify integration (and potential conflicts) between the Process and its normative references w3c/process#572 (1 comment by @TallTed)
-
w3c-cg/PWETF
-
23 issues opened.
-
Add "Micromanaging" under "Unacceptable Behavior" w3c-cg/PWETF#346, by @rachelyager-nyc.
-
PWE Procedures section does not describe procedures w3c-cg/PWETF#344, by @dbooth-boston.
-
Revise definition of Diversity in the Glossary w3c-cg/PWETF#342, by @jenstrickland.
-
Shorten "ombudspeople" to "ombuds", etc. and use consistent capitalization w3c-cg/PWETF#339, by @dbooth-boston.
-
Retaliation w3c-cg/PWETF#337, by @frivoal.
-
Discrimination does not need to be fact based to be problematic w3c-cg/PWETF#336, by @frivoal.
-
[editorial] Make hyperlinking easier w3c-cg/PWETF#335, by @frivoal.
-
Gatekeeping w3c-cg/PWETF#334, by @frivoal.
-
When shouldn't you raise an issue about a CoC violation? w3c-cg/PWETF#333, by @chaals.
-
Unwelcome sexual attention isn't necessarily "a pattern" w3c-cg/PWETF#332, by @chaals.
-
Argumentum ad nauseam is too narrowly defined w3c-cg/PWETF#331, by @chaals.
-
Is "race" too simplistic a description of an important but complex concept w3c-cg/PWETF#327, by @chaals.
-
What do we mean by "personal attacks"? w3c-cg/PWETF#326, by @chaals.
-
Update Process link w3c-cg/PWETF#324, by @chaals.
-
Comfort with physical displays of affection varies by person, not just "culture" w3c-cg/PWETF#321, by @chaals.
-
Do comments have to be raised in english? w3c-cg/PWETF#320, by @chaals.
-
redundant exhortation to follow the CoC w3c-cg/PWETF#318, by @chaals.
-
Clarify update cycle w3c-cg/PWETF#314, by @chaals.
-
Lost changes during merge commit w3c-cg/PWETF#311, by @fantasai.
-
Diversity cannot be a single point w3c-cg/PWETF#310, by @fantasai.
-
-
10 issues closed.
-
3.3 Safety vs. Comfort - editorial w3c-cg/PWETF#309.
-
Diversity cannot be a single point w3c-cg/PWETF#310.
-
Lost changes during merge commit w3c-cg/PWETF#311.
-
redundant exhortation to follow the CoC w3c-cg/PWETF#318.
-
Clarify bullets on "patronizing language or behavior" w3c-cg/PWETF#232.
-
Is disruptive behaviour a CEPC issue? w3c-cg/PWETF#307.
-
Clarify update cycle w3c-cg/PWETF#314.
-
Update Process link w3c-cg/PWETF#324.
-
1 issue reopened.
-
Is "race" too simplistic a description of an important but complex concept w3c-cg/PWETF#327, by @wareid.
-
-
12 issues received 26 new comments.
-
Revise definition of Diversity in the Glossary w3c-cg/PWETF#342 (9 comments by @a11ydoer, @dbooth-boston, @fantasai, @jenstrickland, @nigelmegitt, @wareid)
-
Is disruptive behaviour a CEPC issue? w3c-cg/PWETF#307 (5 comments by @chaals, @jwrosewell, @mnot, @TzviyaSiegman)
-
PWE Procedures section does not describe procedures w3c-cg/PWETF#344 (1 comment by @rachelyager-nyc)
-
Clarify bullets on "patronizing language or behavior" w3c-cg/PWETF#232 (1 comment by @dbooth-boston)
-
Comfort with physical displays of affection varies by person, not just "culture" w3c-cg/PWETF#321 (1 comment by @dbooth-boston)
-
Discrimination does not need to be fact based to be problematic w3c-cg/PWETF#336 (1 comment by @frivoal)
-
-
13 pull requests opened.
-
Revised Definition for Diversity (Issue 342) w3c-cg/PWETF#345, by @wareid.
-
edit ombuds description w3c-cg/PWETF#343, by @TzviyaSiegman.
-
Addressing issue 327 w3c-cg/PWETF#338, by @wareid.
-
Issue 322 - Refine physical contact w3c-cg/PWETF#330, by @wareid.
-
Safety vs Comfort Issue 309 w3c-cg/PWETF#329, by @wareid.
-
Editorial Changes w3c-cg/PWETF#328, by @wareid.
-
Update process link w3c-cg/PWETF#325, by @chaals.
-
remove redundant exhortation w3c-cg/PWETF#319, by @chaals.
-
Dimensions include... w3c-cg/PWETF#317, by @chaals.
-
say perceived reverse ism w3c-cg/PWETF#316, by @chaals.
-
Spanish translation w3c-cg/PWETF#315, by @chaals.
-
Clarify what PWE is w3c-cg/PWETF#313, by @chaals.
-
fix a broken link w3c-cg/PWETF#312, by @chaals.
-
-
8 pull requests merged.
-
Addressing issue 327 w3c-cg/PWETF#338.
-
Issue 322 - Refine physical contact w3c-cg/PWETF#330.
-
Safety vs Comfort Issue 309 w3c-cg/PWETF#329.
-
Editorial Changes w3c-cg/PWETF#328.
-
remove redundant exhortation w3c-cg/PWETF#319.
-
Clarify what PWE is w3c-cg/PWETF#313.
-
Update process link w3c-cg/PWETF#325.
-
fix a broken link w3c-cg/PWETF#312.
-
-
2 pull requests closed.
-
Dimensions include... w3c-cg/PWETF#317.
-
say perceived reverse ism w3c-cg/PWETF#316.
-
-
9 pull requests received 20 new comments.
-
Issue 322 - Refine physical contact w3c-cg/PWETF#330 (5 comments by @chaals, @dbooth-boston, @fantasai)
-
w3c/PWETF
-
23 issues opened.
-
Add "Micromanaging" under "Unacceptable Behavior" w3c/PWETF#346, by @rachelyager-nyc.
-
PWE Procedures section does not describe procedures w3c/PWETF#344, by @dbooth-boston.
-
Revise definition of Diversity in the Glossary w3c/PWETF#342, by @jenstrickland.
-
Retaliation w3c/PWETF#337, by @frivoal.
-
Discrimination does not need to be fact based to be problematic w3c/PWETF#336, by @frivoal.
-
[editorial] Make hyperlinking easier w3c/PWETF#335, by @frivoal.
-
Gatekeeping w3c/PWETF#334, by @frivoal.
-
When shouldn't you raise an issue about a CoC violation? w3c/PWETF#333, by @chaals.
-
Unwelcome sexual attention isn't necessarily "a pattern" w3c/PWETF#332, by @chaals.
-
Argumentum ad nauseam is too narrowly defined w3c/PWETF#331, by @chaals.
-
What do we mean by "personal attacks"? w3c/PWETF#326, by @chaals.
-
Update Process link w3c/PWETF#324, by @chaals.
-
Do comments have to be raised in english? w3c/PWETF#320, by @chaals.
-
redundant exhortation to follow the CoC w3c/PWETF#318, by @chaals.
-
Clarify update cycle w3c/PWETF#314, by @chaals.
-
Lost changes during merge commit w3c/PWETF#311, by @fantasai.
-
Diversity cannot be a single point w3c/PWETF#310, by @fantasai.
-
-
10 issues closed.
-
3.3 Safety vs. Comfort - editorial w3c/PWETF#309.
-
Diversity cannot be a single point w3c/PWETF#310.
-
Lost changes during merge commit w3c/PWETF#311.
-
redundant exhortation to follow the CoC w3c/PWETF#318.
-
Clarify bullets on "patronizing language or behavior" w3c/PWETF#232.
-
Is disruptive behaviour a CEPC issue? w3c/PWETF#307.
-
Clarify update cycle w3c/PWETF#314.
-
Update Process link w3c/PWETF#324.
-
1 issue reopened.
-
12 issues received 26 new comments.
-
Revise definition of Diversity in the Glossary w3c/PWETF#342 (9 comments by @a11ydoer, @dbooth-boston, @fantasai, @jenstrickland, @nigelmegitt, @wareid)
-
Is disruptive behaviour a CEPC issue? w3c/PWETF#307 (5 comments by @chaals, @jwrosewell, @mnot, @TzviyaSiegman)
-
Comfort with physical displays of affection varies by person, not just "culture" w3c/PWETF#321 (1 comment by @dbooth-boston)
-
Discrimination does not need to be fact based to be problematic w3c/PWETF#336 (1 comment by @frivoal)
-
-
13 pull requests opened.
-
Revised Definition for Diversity (Issue 342) w3c/PWETF#345, by @wareid.
-
edit ombuds description w3c/PWETF#343, by @TzviyaSiegman.
-
Addressing issue 327 w3c/PWETF#338, by @wareid.
-
Issue 322 - Refine physical contact w3c/PWETF#330, by @wareid.
-
Safety vs Comfort Issue 309 w3c/PWETF#329, by @wareid.
-
Editorial Changes w3c/PWETF#328, by @wareid.
-
Update process link w3c/PWETF#325, by @chaals.
-
remove redundant exhortation w3c/PWETF#319, by @chaals.
-
Dimensions include... w3c/PWETF#317, by @chaals.
-
say perceived reverse ism w3c/PWETF#316, by @chaals.
-
Spanish translation w3c/PWETF#315, by @chaals.
-
Clarify what PWE is w3c/PWETF#313, by @chaals.
-
fix a broken link w3c/PWETF#312, by @chaals.
-
-
8 pull requests merged.
-
Addressing issue 327 w3c/PWETF#338.
-
Issue 322 - Refine physical contact w3c/PWETF#330.
-
Safety vs Comfort Issue 309 w3c/PWETF#329.
-
Editorial Changes w3c/PWETF#328.
-
remove redundant exhortation w3c/PWETF#319.
-
Clarify what PWE is w3c/PWETF#313.
-
Update process link w3c/PWETF#325.
-
fix a broken link w3c/PWETF#312.
-
-
2 pull requests closed.
-
Dimensions include... w3c/PWETF#317.
-
say perceived reverse ism w3c/PWETF#316.
-
-
9 pull requests received 20 new comments.
-
Issue 322 - Refine physical contact w3c/PWETF#330 (5 comments by @chaals, @dbooth-boston, @fantasai)
-
w3c/AB-public
-
11 issues opened.
-
Multiple implementations point w3c/AB-public#120, by @cwilso.
-
"Recognize and embody principles" w3c/AB-public#119, by @cwilso.
-
Demonstrating core principles w3c/AB-public#118, by @cwilso.
-
Horizontal review w3c/AB-public#117, by @cwilso.
-
Awkward sentence w3c/AB-public#116, by @cwilso.
-
Include a Reference to UN Declaration on Human Rights in Vision Doc w3c/AB-public#115, by @torgo.
-
Improve readability of the operational principles section w3c/AB-public#114, by @wareid.
-
"supports truth over falsehood" may read like censorship w3c/AB-public#113, by @dontcallmedom.
-
The point of standards is to create and ensure interoperability w3c/AB-public#112, by @cwilso.
-
Why do you want to change the mission? w3c/AB-public#109, by @hsano1234.
-
Feedback on “different approaches” w3c/AB-public#108, by @fantasai.
-
-
2 issues closed.
-
refocus scope of vision w3c/AB-public#102.
-
Why do you want to change the mission? w3c/AB-public#109.
-
-
8 issues received 19 new comments.
-
Why do you want to change the mission? w3c/AB-public#109 (6 comments by @cwilso, @fantasai, @hsano1234)
-
Improve readability of the operational principles section w3c/AB-public#114 (2 comments by @cwilso, @michaelchampion)
-
-
2 pull requests opened.
-
Rewrite proposal w3c/AB-public#111, by @cwilso.
-
Test - DNM w3c/AB-public#110, by @cwilso.
-
-
2 pull requests merged.
-
Rewrite proposal w3c/AB-public#111.
-
Set up an automated glossary w3c/AB-public#107.
-
-
3 pull requests closed.
-
avoiding dupes, broader critical axes of diverse voices w3c/AB-public#89.
-
Proposal sketch in Markdown for discussion w3c/AB-public#103.
-
Test - DNM w3c/AB-public#110.
-
-
4 pull requests received 87 new comments.
-
Rewrite proposal w3c/AB-public#111 (49 comments by @amyvdh, @chrisn, @cwilso, @dontcallmedom, @fantasai, @jwrosewell, @wareid)
-
Proposal sketch in Markdown for discussion w3c/AB-public#103 (32 comments by @cwilso, @dontcallmedom, @koalie)
-
Advisory Board Elected Members
Participants
-
11 participants joined the Advisory Board Elected Members.
-
Song XU joined.
-
Chris Wilson joined.
-
Avneesh Singh joined.
-
Tzviya Siegman joined.
-
Florian Rivoal joined.
-
Wendy Reid joined.
-
Tatsuya Igarashi joined.
-
Elika Etemad joined.
-
Wei Ding joined.
-
Tantek Çelik joined.
-
Qing An joined.
-
Vision Task Force
Past meetings
-
1 meeting of the Vision Task Force.
TR publications
-
1 document published.
-
Vision for W3C published as a Draft Note. History of Vision for W3C
-
Past meetings
-
2 meetings.
Participants
-
1 Team contact appointed.
-
Amy van der Hiel became a Team contact.
-
-
1 Team contact stepped down.
-
Ralph Swick stepped down as a Team contact.
-
-
3 participants joined.
-
Heejin Chung joined.
-
Chaals Nevile joined.
-
Amy van der Hiel joined.
-
-
2 participants left.
-
Heejin Chung left.
-
Chaals Nevile left.
-
GitHub
w3c/process
-
3 issues opened.
-
Veto by inaction w3c/process#778, by @mnot.
-
"Wide review" is too easy to confuse with "horizontal review" w3c/process#776, by @marcoscaceres.
-
Diagram should clarify that it's possible to go from REC back to CR w3c/process#775, by @marcoscaceres.
-
-
1 issue closed.
-
Increase size of the TAG? w3c/process#465.
-
-
7 issues received 23 new comments.
-
Veto by inaction w3c/process#778 (10 comments by @dwsinger, @fantasai, @frivoal, @mnot, @nigelmegitt, @samuelweiler)
-
Clarify and simplify the sections regarding publication and process 2021 w3c/process#700 (5 comments by @frivoal, @marcoscaceres, @TallTed)
-
"Wide review" is too easy to confuse with "horizontal review" w3c/process#776 (2 comments by @nigelmegitt, @samuelweiler)
-
Diagram should clarify that it's possible to go from REC back to CR w3c/process#775 (1 comment by @frivoal)
-
-
1 pull request opened.
-
Update README.md w3c/process#777, by @Galbert01.
-
-
1 pull request merged.
-
Expand the TAG from 6+3 to 8+3 participants w3c/process#733.
-
-
1 pull request closed.
-
Update README.md w3c/process#777.
-
-
2 pull requests received 3 new comments.
-
Meetings of new groups are 8 weeks from charter approval w3c/process#434 (1 comment by @samuelweiler)
w3c/AB-public
-
5 issues opened.
-
Publication of "History" w3c/AB-public#105, by @frivoal.
-
Feedback on Vision document w3c/AB-public#104, by @ianbjacobs.
-
refocus scope of vision w3c/AB-public#102, by @TzviyaSiegman.
-
Laws then consensus w3c/AB-public#98, by @jwrosewell.
-
-
4 issues closed.
-
word consistency about "Web" w3c/AB-public#97.
-
Values need further specificity w3c/AB-public#5.
-
Collapse "Vision for W3C" and "Mission of W3C" together w3c/AB-public#94.
-
6 issues received 80 new comments.
-
refocus scope of vision w3c/AB-public#102 (36 comments by @avneeshsingh, @chrisn, @cwilso, @darobin, @dwsinger, @LJWatson, @michaelchampion, @mnot, @TzviyaSiegman, @wareid)
-
Introduction is negative and exceeds the remit of a neutral technical standards body w3c/AB-public#90 (17 comments by @chaals, @darobin, @frivoal, @jwrosewell, @mgendler, @michaelchampion, @mnot, @wareid)
-
Laws then consensus w3c/AB-public#98 (11 comments by @chaals, @dwsinger, @jwrosewell, @michaelchampion, @mnot)
-
Publication of "History" w3c/AB-public#105 (7 comments by @dwsinger, @fantasai, @frivoal, @michaelchampion)
-
Notice Pursuant to the National Cooperative Research and Production Act of 1993-World Wide Web Consortium, Inc. w3c/AB-public#100 (7 comments by @cwilso, @jwrosewell, @michaelchampion, @wareid)
-
-
5 pull requests opened.
-
Set up an automated glossary w3c/AB-public#107, by @frivoal.
-
Set up the Vision document for automated publishing w3c/AB-public#106, by @frivoal.
-
Proposal sketch in Markdown for discussion w3c/AB-public#103, by @cwilso.
-
Fixes #97 (Consistency in "Web"/"World Wide Web") w3c/AB-public#101, by @cwilso.
-
accessibility needs -> disabilities w3c/AB-public#99, by @shawna-slh.
-
-
6 pull requests merged.
-
Set up the Vision document for automated publishing w3c/AB-public#106.
-
Fixes #97 (Consistency in "Web"/"World Wide Web") w3c/AB-public#101.
-
Fixes #88 (enumerating unintended consequences) w3c/AB-public#92.
-
Fixes #5 (Values need further specificity) w3c/AB-public#93.
-
Collapse "Vision for W3C" and "Mission of W3C" together w3c/AB-public#95.
-
accessibility needs -> disabilities w3c/AB-public#99.
-
-
4 pull requests received 6 new comments.
-
Fixes #97 (Consistency in "Web"/"World Wide Web") w3c/AB-public#101 (2 comments by @cwilso, @frivoal)
-
w3c-cg/PWETF
-
5 issues opened.
-
3.3 Safety vs. Comfort - editorial w3c-cg/PWETF#309, by @mnot.
-
Language choices / Getting people on board with the CEPC w3c-cg/PWETF#308, by @mnot.
-
Is disruptive behaviour a CEPC issue? w3c-cg/PWETF#307, by @mnot.
-
Code of conduct violation w3c-cg/PWETF#306, by @ghost.
-
-
3 issues closed.
-
Language choices / Getting people on board with the CEPC w3c-cg/PWETF#308.
-
Code of conduct violation w3c-cg/PWETF#306.
-
Add "Gaming of the W3C Process" to Unacceptable Behavior w3c-cg/PWETF#154.
-
-
7 issues received 31 new comments.
-
Code of conduct violation w3c-cg/PWETF#306 (10 comments by @ghost, @joepie91, @jwrosewell, @mnot, @nigelmegitt, @roryyamm, @TzviyaSiegman, @wareid)
-
Is disruptive behaviour a CEPC issue? w3c-cg/PWETF#307 (7 comments by @frivoal, @LJWatson, @michaelchampion, @mnot, @TzviyaSiegman)
-
Language choices / Getting people on board with the CEPC w3c-cg/PWETF#308 (4 comments by @dbooth-boston, @mnot, @wareid)
-
make CEPC consequence section more robust w3c-cg/PWETF#193 (3 comments by @mnot, @TzviyaSiegman, @wareid)
-
-
3 pull requests opened.
-
Fix the spelling of "microaggression". w3c-cg/PWETF#305, by @jyasskin.
-
(minor) consistent terminal punctuation on list items. w3c-cg/PWETF#304, by @shawna-slh.
-
Adding Changelog and Acknowledgements w3c-cg/PWETF#303, by @wareid.
-
-
3 pull requests merged.
-
Fix the spelling of "microaggression". w3c-cg/PWETF#305.
-
(minor) consistent terminal punctuation on list items. w3c-cg/PWETF#304.
-
Adding Changelog and Acknowledgements w3c-cg/PWETF#303.
-
-
2 pull requests received 13 new comments.
-
(minor) consistent terminal punctuation on list items. w3c-cg/PWETF#304 (2 comments by @shawna-slh, @wareid)
w3c/PWETF
-
5 issues opened.
-
3.3 Safety vs. Comfort - editorial w3c/PWETF#309, by @mnot.
-
Language choices / Getting people on board with the CEPC w3c/PWETF#308, by @mnot.
-
Is disruptive behaviour a CEPC issue? w3c/PWETF#307, by @mnot.
-
Code of conduct violation w3c/PWETF#306, by @ghost.
-
-
3 issues closed.
-
Language choices / Getting people on board with the CEPC w3c/PWETF#308.
-
Code of conduct violation w3c/PWETF#306.
-
Add "Gaming of the W3C Process" to Unacceptable Behavior w3c/PWETF#154.
-
-
7 issues received 31 new comments.
-
Code of conduct violation w3c/PWETF#306 (10 comments by @ghost, @joepie91, @jwrosewell, @mnot, @nigelmegitt, @roryyamm, @TzviyaSiegman, @wareid)
-
Is disruptive behaviour a CEPC issue? w3c/PWETF#307 (7 comments by @frivoal, @LJWatson, @michaelchampion, @mnot, @TzviyaSiegman)
-
Language choices / Getting people on board with the CEPC w3c/PWETF#308 (4 comments by @dbooth-boston, @mnot, @wareid)
-
make CEPC consequence section more robust w3c/PWETF#193 (3 comments by @mnot, @TzviyaSiegman, @wareid)
-
-
3 pull requests opened.
-
Fix the spelling of "microaggression". w3c/PWETF#305, by @jyasskin.
-
(minor) consistent terminal punctuation on list items. w3c/PWETF#304, by @shawna-slh.
-
Adding Changelog and Acknowledgements w3c/PWETF#303, by @wareid.
-
-
3 pull requests merged.
-
Fix the spelling of "microaggression". w3c/PWETF#305.
-
(minor) consistent terminal punctuation on list items. w3c/PWETF#304.
-
Adding Changelog and Acknowledgements w3c/PWETF#303.
-
-
2 pull requests received 13 new comments.
-
(minor) consistent terminal punctuation on list items. w3c/PWETF#304 (2 comments by @shawna-slh, @wareid)
Vision Task Force
Past meetings
-
1 meeting of the Vision Task Force.
Past meetings
-
2 meetings.
Participants
-
2 participants joined.
-
Song XU joined.
-
Wendy Reid joined.
-
GitHub
w3c/process
-
3 issues opened.
-
Link for "W3C Horizontal Groups" doesn't describe W3C horizontal groups w3c/process#769, by @jyasskin.
-
2 issues closed.
-
Japanese translation of Process 2021 w3c/process#767.
-
7 issues received 38 new comments.
-
Incumbent bias in elections / impose term limits? w3c/process#697 (16 comments by @cwilso, @dwsinger, @frivoal, @LJWatson, @michaelchampion, @mnot, @TzviyaSiegman)
-
Japanese translation of Process 2021 w3c/process#767 (6 comments by @frivoal, @xueyuanjia, @yonaomi, @ytakamu)
-
Clarify and simplify the sections regarding publication and process 2021 w3c/process#700 (5 comments by @dwsinger, @marcoscaceres, @nigelmegitt, @TzviyaSiegman, @wareid)
-
Can WGs request the W3C team to negotiate technical agreements with liaison organizations? w3c/process#773 (4 comments by @fantasai, @frivoal, @nigelmegitt, @TallTed)
-
Use Alias rather than Redirect for /Consortium/Process w3c/process#729 (3 comments by @koalie, @plehegar)
-
Link for "W3C Horizontal Groups" doesn't describe W3C horizontal groups w3c/process#769 (1 comment by @samuelweiler)
-
-
1 pull request merged.
-
informative role of chair/contact. fixes #765 w3c/process#766.
-
-
1 pull request received 1 new comment.
w3c-cg/PWETF
-
5 issues closed.
-
Redundancy in the "patronizing" section w3c-cg/PWETF#265.
-
Safety vs Comfort section additional clarity on the first bullet. w3c-cg/PWETF#263.
-
Definition of "Microaggression" w3c-cg/PWETF#235.
-
"Improper" is elitist and arbitrary w3c-cg/PWETF#234.
-
Redundant phrase in section 1.1 w3c-cg/PWETF#294.
-
-
8 issues received 26 new comments.
-
Add "Gaming of the W3C Process" to Unacceptable Behavior w3c-cg/PWETF#154 (6 comments by @dbooth-boston, @mnot, @msporny, @TzviyaSiegman, @wareid)
-
Definition of "Microaggression" w3c-cg/PWETF#235 (5 comments by @dbooth-boston, @TzviyaSiegman, @wareid)
-
Clarify authority of people in Leadership Positions to take immediate action w3c-cg/PWETF#77 (3 comments by @mnot, @nigelmegitt, @TzviyaSiegman)
-
Visibility and retention of CEPC violation assessments w3c-cg/PWETF#34 (2 comments by @mnot, @TzviyaSiegman)
-
Clarify bullets on "patronizing language or behavior" w3c-cg/PWETF#232 (1 comment by @TzviyaSiegman)
-
-
4 pull requests opened.
-
Fixing ReSpec issues w3c-cg/PWETF#301, by @wareid.
-
Adding "well, actually" back as an example w3c-cg/PWETF#300, by @wareid.
-
Revised definition for microagression w3c-cg/PWETF#299, by @wareid.
-
delete double "at any time" w3c-cg/PWETF#298, by @TzviyaSiegman.
-
-
5 pull requests merged.
-
Fixing ReSpec issues w3c-cg/PWETF#301.
-
Adding "well, actually" back as an example w3c-cg/PWETF#300.
-
safety v comfort w3c-cg/PWETF#290.
-
Revised definition for microagression w3c-cg/PWETF#299.
-
delete double "at any time" w3c-cg/PWETF#298.
-
-
2 pull requests received 13 new comments.
-
Adding "well, actually" back as an example w3c-cg/PWETF#300 (12 comments by @cwilso, @dbooth-boston, @nigelmegitt, @TzviyaSiegman, @wareid)
-
w3c/PWETF
-
5 issues closed.
-
Redundancy in the "patronizing" section w3c/PWETF#265.
-
Definition of "Microaggression" w3c/PWETF#235.
-
"Improper" is elitist and arbitrary w3c/PWETF#234.
-
Redundant phrase in section 1.1 w3c/PWETF#294.
-
-
8 issues received 26 new comments.
-
Add "Gaming of the W3C Process" to Unacceptable Behavior w3c/PWETF#154 (6 comments by @dbooth-boston, @mnot, @msporny, @TzviyaSiegman, @wareid)
-
Definition of "Microaggression" w3c/PWETF#235 (5 comments by @dbooth-boston, @TzviyaSiegman, @wareid)
-
Clarify authority of people in Leadership Positions to take immediate action w3c/PWETF#77 (3 comments by @mnot, @nigelmegitt, @TzviyaSiegman)
-
Visibility and retention of CEPC violation assessments w3c/PWETF#34 (2 comments by @mnot, @TzviyaSiegman)
-
-
4 pull requests opened.
-
Fixing ReSpec issues w3c/PWETF#301, by @wareid.
-
Adding "well, actually" back as an example w3c/PWETF#300, by @wareid.
-
Revised definition for microagression w3c/PWETF#299, by @wareid.
-
delete double "at any time" w3c/PWETF#298, by @TzviyaSiegman.
-
-
5 pull requests merged.
-
Fixing ReSpec issues w3c/PWETF#301.
-
Adding "well, actually" back as an example w3c/PWETF#300.
-
safety v comfort w3c/PWETF#290.
-
Revised definition for microagression w3c/PWETF#299.
-
delete double "at any time" w3c/PWETF#298.
-
-
2 pull requests received 13 new comments.
-
Adding "well, actually" back as an example w3c/PWETF#300 (12 comments by @cwilso, @dbooth-boston, @nigelmegitt, @TzviyaSiegman, @wareid)
-
w3c/AB-public
-
9 issues opened.
-
word consistency about "Web" w3c/AB-public#97, by @hsano1234.
-
DRM/Copyright and our position in the Vision w3c/AB-public#96, by @wareid.
-
Collapse "Vision for W3C" and "Mission of W3C" together w3c/AB-public#94, by @cwilso.
-
For all humanity? w3c/AB-public#91, by @darobin.
-
exemplifying unintended consequences w3c/AB-public#88, by @FabienGandon.
-
Mission of the W3C as a workspace w3c/AB-public#87, by @KotisK.
-
changing the title of W3C Vision w3c/AB-public#86, by @KotisK.
-
Vision for the W3C w3c/AB-public#85, by @KotisK.
-
-
5 issues closed.
-
Increase input and positivity? w3c/AB-public#14.
-
Needs editorial work to reduce redundancy w3c/AB-public#9.
-
Vision for the W3C w3c/AB-public#85.
-
Adding content related to the future Web w3c/AB-public#67.
-
Add to principle around centralization w3c/AB-public#11.
-
-
1 issue reopened.
-
Recognizing the value provided by the wide diversity of publishers w3c/AB-public#16, by @TzviyaSiegman.
-
-
19 issues received 118 new comments.
-
For all humanity? w3c/AB-public#91 (22 comments by @chaals, @cwilso, @darobin, @dwsinger, @frivoal, @mnot, @TzviyaSiegman, @wareid)
-
Add a principle of "Origin Sovereignty"? w3c/AB-public#17 (15 comments by @chaals, @darobin, @dwsinger, @jwrosewell, @koalie, @michaelchampion, @mnot, @TzviyaSiegman)
-
emphasis on industry w3c/AB-public#75 (14 comments by @agreiner, @avneeshsingh, @dwsinger, @FabienGandon, @fantasai, @frivoal, @koalie, @mnot)
-
Introduction is negative and exceeds the remit of a neutral technical standards body w3c/AB-public#90 (13 comments by @darobin, @frivoal, @jwrosewell, @mgendler, @michaelchampion, @mnot, @TzviyaSiegman, @wareid)
-
Remove reference to the Ethical Web Principles w3c/AB-public#81 (9 comments by @chaals, @cwilso, @jwrosewell)
-
Reconsider our definition of "World Wide Web" w3c/AB-public#58 (7 comments by @cwilso, @darobin, @frivoal, @mnot, @TzviyaSiegman)
-
exemplifying unintended consequences w3c/AB-public#88 (5 comments by @cwilso, @fantasai, @frivoal, @michaelchampion, @TzviyaSiegman)
-
Vision: add malvertising to explicit mentions of known web harms w3c/AB-public#71 (4 comments by @chrisn, @dwsinger, @TzviyaSiegman)
-
Recognizing the value provided by the wide diversity of publishers w3c/AB-public#16 (2 comments by @TzviyaSiegman)
-
Resolve issues associated with antitrust before progressing further w3c/AB-public#80 (2 comments by @koalie, @TzviyaSiegman)
-
-
4 pull requests opened.
-
Collapse "Vision for W3C" and "Mission of W3C" together w3c/AB-public#95, by @cwilso.
-
Fixes #5 (Values need further specificity) w3c/AB-public#93, by @cwilso.
-
Fixes #88 (enumerating unintended consequences) w3c/AB-public#92, by @cwilso.
-
avoiding dupes, broader critical axes of diverse voices w3c/AB-public#89, by @koalie.
-
Vision Task Force
Past meetings
-
1 meeting of the Vision Task Force.
Past meetings
-
2 meetings.
GitHub
w3c/AB-public
-
8 issues opened.
-
Add use cases of "industries" w3c/AB-public#84, by @igarashi50.
-
Refine definition of sustainability w3c/AB-public#83, by @cwilso.
-
Distinguish our aspirations from what we have already operationalized w3c/AB-public#82, by @dontcallmedom.
-
Remove reference to the Ethical Web Principles w3c/AB-public#81, by @jwrosewell.
-
Resolve issues associated with antitrust before progressing further w3c/AB-public#80, by @jwrosewell.
-
adequate implementation experience w3c/AB-public#76, by @FabienGandon.
-
emphasis on industry w3c/AB-public#75, by @FabienGandon.
-
"Vision for the web" and "Vision for the W3C" might be separate documents? w3c/AB-public#74, by @dwsinger.
-
-
5 issues closed.
-
Add Sustainability as a principle or value in the Vision w3c/AB-public#62.
-
Define the purpose of Vision document w3c/AB-public#22.
-
adequate implementation experience w3c/AB-public#76.
-
W3C is a Voluntary standards forum w3c/AB-public#69.
-
-
9 issues received 42 new comments.
-
emphasis on industry w3c/AB-public#75 (13 comments by @chaals, @cwilso, @FabienGandon, @fantasai, @frivoal, @jwrosewell, @michaelchampion, @TzviyaSiegman)
-
Add to principle around centralization w3c/AB-public#11 (7 comments by @frivoal, @jwrosewell, @mnot, @TzviyaSiegman)
-
Vision: add malvertising to explicit mentions of known web harms w3c/AB-public#71 (6 comments by @chaals, @frivoal, @jwrosewell, @michaelchampion)
-
"Vision for the web" and "Vision for the W3C" might be separate documents? w3c/AB-public#74 (5 comments by @cwilso, @dwsinger, @hober, @michaelchampion)
-
Add a principle of "Origin Sovereignty"? w3c/AB-public#17 (4 comments by @chaals, @darobin, @dwsinger, @jwrosewell)
-
Add Sustainability as a principle or value in the Vision w3c/AB-public#62 (3 comments by @cwilso, @michaelchampion)
-
Vision: distinguish between vision as an org vs vision of our output w3c/AB-public#72 (1 comment by @cwilso)
-
-
3 pull requests opened.
-
Add implementation experience w3c/AB-public#79, by @cwilso.
-
Add Sustainability goal w3c/AB-public#78, by @cwilso.
-
Add adapted Status of this Document w3c/AB-public#77, by @cwilso.
-
-
4 pull requests merged.
-
Add Sustainability goal w3c/AB-public#78.
-
Add adapted Status of this Document w3c/AB-public#77.
-
Add implementation experience w3c/AB-public#79.
-
Voluntary standards (fixes #69) w3c/AB-public#70.
-
-
3 pull requests received 9 new comments.
w3c/process
-
5 issues opened.
-
Japanese translation of Process 2021 w3c/process#767, by @xueyuanjia.
-
Closing the loop on resolving Formal Objections w3c/process#755, by @plehegar.
-
Define "joint deliverables" w3c/process#754, by @frivoal.
-
-
9 issues closed.
-
Avoid using two different meanings of "sustain" w3c/process#746.
-
Editorial: dismissal w3c/process#747.
-
AC Review dissent requirement vs questionnaire options w3c/process#738.
-
Clarify where Submission Appeals go w3c/process#742.
-
editorial: textual inconsistencies in basic-rec-track.svg w3c/process#661.
-
Dissent in AC review w3c/process#750.
-
Minority Opinions w3c/process#752.
-
19 issues received 113 new comments.
-
Closing the loop on resolving Formal Objections w3c/process#755 (24 comments by @chaals, @dwsinger, @fantasai, @frivoal, @marcoscaceres, @nigelmegitt, @palemieux)
-
Council decision side effects w3c/process#751 (23 comments by @chrisn, @dwsinger, @fantasai, @frivoal, @mnot, @nigelmegitt, @othermaciej, @plehegar)
-
Define "joint deliverables" w3c/process#754 (9 comments by @anssiko, @dwsinger, @frivoal, @marcoscaceres, @nigelmegitt, @plehegar)
-
Dismissal voting w3c/process#748 (8 comments by @dwsinger, @fantasai, @frivoal, @mnot, @nigelmegitt)
-
Avoid using two different meanings of "sustain" w3c/process#746 (5 comments by @chrisn, @css-meeting-bot, @fantasai, @frivoal)
-
New W3C Council and updated TAG Composition section errantly only includes Tim Berners-Lee... w3c/process#764 (4 comments by @fantasai, @frivoal, @tantek)
-
Addressing formal objections before requesting advancement w3c/process#737 (2 comments by @frivoal, @jyasskin)
-
AC Review dissent requirement vs questionnaire options w3c/process#738 (2 comments by @fantasai, @jyasskin)
-
Normative prose for role of Chair / Team Contact cites informative reference for description w3c/process#765 (1 comment by @frivoal)
-
"Regression on the REC track" should say what kind of approval is needed w3c/process#741 (1 comment by @fantasai)
-
-
7 pull requests opened.
-
informative role of chair/contact. fixes #765 w3c/process#766, by @tantek.
-
Clarify 'formal contexts' for Formal Objections w3c/process#763, by @chrisn.
-
Disambiguate sustain w3c/process#762, by @frivoal.
-
Exclude TAG/AB from voting on their own decisions/proposals. #749 w3c/process#761, by @fantasai.
-
Must report dismissal vote counts. #748 w3c/process#760, by @fantasai.
-
Fix typo in description of Council formation w3c/process#759, by @chrisn.
-
Dismissal wording w3c/process#757, by @fantasai.
-
-
7 pull requests merged.
-
fix punc, spelling, inconsistent labels, etc. w3c/process#667.
-
Dismissal wording w3c/process#757.
-
Disambiguate sustain w3c/process#762.
-
Clarify 'formal contexts' for Formal Objections w3c/process#763.
-
Don't say that dissent goes away when it's overruled w3c/process#740.
-
Fix typo in description of Council formation w3c/process#759.
-
-
6 pull requests received 7 new comments.
-
fix punc, spelling, inconsistent labels, etc. w3c/process#667 (2 comments by @css-meeting-bot, @fantasai)
-
Exclude TAG/AB from voting on their own decisions/proposals. #749 w3c/process#761 (1 comment by @dwsinger)
-
w3c-cg/PWETF
-
11 issues opened.
-
Item on abusive behavior is in the wrong section w3c-cg/PWETF#296, by @dbooth-boston.
-
Change "Ombudsperson"/"Ombudspeople" to "Ombud"/"Ombuds" throughout w3c-cg/PWETF#295, by @dbooth-boston.
-
Redundant phrase in section 1.1 w3c-cg/PWETF#294, by @dbooth-boston.
-
Missed CEPC --> CoC conversion w3c-cg/PWETF#293, by @dbooth-boston.
-
Redundancy in the "patronizing" section w3c-cg/PWETF#265, by @dbooth-boston.
-
Definition of "patronizing" needs to be acknowledged w3c-cg/PWETF#264, by @dbooth-boston.
-
Safety vs Comfort section additional clarity on the first bullet. w3c-cg/PWETF#263, by @jspellman.
-
In Unacceptable Behavior - Sustained Disruption of Discussion w3c-cg/PWETF#261, by @jspellman.
-
Number bullet points in the Code section w3c-cg/PWETF#259, by @jspellman.
-
-
10 issues closed.
-
Missed CEPC --> CoC conversion w3c-cg/PWETF#293.
-
Number bullet points in the Code section w3c-cg/PWETF#259.
-
Include an up-front overview of the code w3c-cg/PWETF#230.
-
CEPC: Safety versus comfort w3c-cg/PWETF#228.
-
Move and clarify the "Safety versus comfort" section w3c-cg/PWETF#233.
-
In Unacceptable Behavior - Sustained Disruption of Discussion w3c-cg/PWETF#261.
-
Definition of "patronizing" needs to be acknowledged w3c-cg/PWETF#264.
-
The Goal of the CEPC sets a rather low bar w3c-cg/PWETF#250.
-
-
9 issues received 31 new comments.
-
"Improper" is elitist and arbitrary w3c-cg/PWETF#234 (12 comments by @cwilso, @dbooth-boston, @LJWatson, @wareid)
-
In Unacceptable Behavior - Sustained Disruption of Discussion w3c-cg/PWETF#261 (6 comments by @csarven, @cwilso, @dbooth-boston, @wareid)
-
Item on abusive behavior is in the wrong section w3c-cg/PWETF#296 (3 comments by @cwilso, @dbooth-boston, @TzviyaSiegman)
-
Redundancy in the "patronizing" section w3c-cg/PWETF#265 (3 comments by @dbooth-boston, @TzviyaSiegman)
-
Number bullet points in the Code section w3c-cg/PWETF#259 (2 comments by @dbooth-boston, @TzviyaSiegman)
-
Move and clarify the "Safety versus comfort" section w3c-cg/PWETF#233 (2 comments by @dbooth-boston, @wareid)
-
-
7 pull requests opened.
-
CEPC -> CoC w3c-cg/PWETF#297, by @TzviyaSiegman.
-
Editing the Abstract w3c-cg/PWETF#292, by @wareid.
-
Issue 259 - Changing to numbered lists w3c-cg/PWETF#291, by @wareid.
-
safety v comfort w3c-cg/PWETF#290, by @TzviyaSiegman.
-
safety v comfort w3c-cg/PWETF#289, by @TzviyaSiegman.
-
Fixing missed "CEPC" mentions and attribution error w3c-cg/PWETF#288, by @wareid.
-
Editorial Recommendations from issues 260, 261, 262 w3c-cg/PWETF#287, by @wareid.
-
-
6 pull requests merged.
-
CEPC -> CoC w3c-cg/PWETF#297.
-
Issue 259 - Changing to numbered lists w3c-cg/PWETF#291.
-
Editing the Abstract w3c-cg/PWETF#292.
-
Editorial Recommendations from issues 260, 261, 262 w3c-cg/PWETF#287.
-
Fixing missed "CEPC" mentions and attribution error w3c-cg/PWETF#288.
-
Goal of the CEPC w3c-cg/PWETF#258.
-
-
2 pull requests closed.
-
Issue 235 - proposed changes - Definition of "Microaggression" w3c-cg/PWETF#241.
-
safety v comfort w3c-cg/PWETF#289.
-
-
3 pull requests received 8 new comments.
-
Fixing missed "CEPC" mentions and attribution error w3c-cg/PWETF#288 (3 comments by @nigelmegitt, @wareid)
w3c/PWETF
-
11 issues opened.
-
Item on abusive behavior is in the wrong section w3c/PWETF#296, by @dbooth-boston.
-
Redundant phrase in section 1.1 w3c/PWETF#294, by @dbooth-boston.
-
Missed CEPC --> CoC conversion w3c/PWETF#293, by @dbooth-boston.
-
Redundancy in the "patronizing" section w3c/PWETF#265, by @dbooth-boston.
-
Definition of "patronizing" needs to be acknowledged w3c/PWETF#264, by @dbooth-boston.
-
Safety vs Comfort section additional clarity on the first bullet. w3c/PWETF#263, by @jspellman.
-
In Unacceptable Behavior - Sustained Disruption of Discussion w3c/PWETF#261, by @jspellman.
-
Number bullet points in the Code section w3c/PWETF#259, by @jspellman.
-
-
10 issues closed.
-
Missed CEPC --> CoC conversion w3c/PWETF#293.
-
Number bullet points in the Code section w3c/PWETF#259.
-
Include an up-front overview of the code w3c/PWETF#230.
-
CEPC: Safety versus comfort w3c/PWETF#228.
-
Move and clarify the "Safety versus comfort" section w3c/PWETF#233.
-
Definition of "patronizing" needs to be acknowledged w3c/PWETF#264.
-
The Goal of the CEPC sets a rather low bar w3c/PWETF#250.
-
-
9 issues received 31 new comments.
-
"Improper" is elitist and arbitrary w3c/PWETF#234 (12 comments by @cwilso, @dbooth-boston, @LJWatson, @wareid)
-
In Unacceptable Behavior - Sustained Disruption of Discussion w3c/PWETF#261 (6 comments by @csarven, @cwilso, @dbooth-boston, @wareid)
-
Item on abusive behavior is in the wrong section w3c/PWETF#296 (3 comments by @cwilso, @dbooth-boston, @TzviyaSiegman)
-
Redundancy in the "patronizing" section w3c/PWETF#265 (3 comments by @dbooth-boston, @TzviyaSiegman)
-
Number bullet points in the Code section w3c/PWETF#259 (2 comments by @dbooth-boston, @TzviyaSiegman)
-
Move and clarify the "Safety versus comfort" section w3c/PWETF#233 (2 comments by @dbooth-boston, @wareid)
-
-
7 pull requests opened.
-
CEPC -> CoC w3c/PWETF#297, by @TzviyaSiegman.
-
Editing the Abstract w3c/PWETF#292, by @wareid.
-
Issue 259 - Changing to numbered lists w3c/PWETF#291, by @wareid.
-
safety v comfort w3c/PWETF#290, by @TzviyaSiegman.
-
safety v comfort w3c/PWETF#289, by @TzviyaSiegman.
-
Fixing missed "CEPC" mentions and attribution error w3c/PWETF#288, by @wareid.
-
Editorial Recommendations from issues 260, 261, 262 w3c/PWETF#287, by @wareid.
-
-
6 pull requests merged.
-
CEPC -> CoC w3c/PWETF#297.
-
Issue 259 - Changing to numbered lists w3c/PWETF#291.
-
Editing the Abstract w3c/PWETF#292.
-
Editorial Recommendations from issues 260, 261, 262 w3c/PWETF#287.
-
Fixing missed "CEPC" mentions and attribution error w3c/PWETF#288.
-
Goal of the CEPC w3c/PWETF#258.
-
-
2 pull requests closed.
-
safety v comfort w3c/PWETF#289.
-
3 pull requests received 8 new comments.
-
Fixing missed "CEPC" mentions and attribution error w3c/PWETF#288 (3 comments by @nigelmegitt, @wareid)
Vision Task Force
Past meetings
-
1 meeting of the Vision Task Force.
Participants
-
1 participant joined the Vision Task Force.
-
Tzviya Siegman joined.
-
Past meetings
-
2 meetings.
GitHub
w3c/AB-public
-
6 issues opened.
-
We should start the formatting of the Vision as a (Draft) Note w3c/AB-public#73, by @dwsinger.
-
Vision: distinguish between vision as an org vs vision of our output w3c/AB-public#72, by @nigelmegitt.
-
Vision: add malvertising to explicit mentions of known web harms w3c/AB-public#71, by @tantek.
-
W3C is a Voluntary standards forum w3c/AB-public#69, by @cwilso.
-
Need instructions for how to file issues/PRs and participate in the Vision w3c/AB-public#68, by @cwilso.
-
Adding content related to the future Web w3c/AB-public#67, by @KotisK.
-
-
2 issues closed.
-
Strategic goals needs a revision w3c/AB-public#12.
-
How should we develop the "W3C Vision and Values"? w3c/AB-public#57.
-
-
10 issues received 30 new comments.
-
Vision: add malvertising to explicit mentions of known web harms w3c/AB-public#71 (8 comments by @cwilso, @dwsinger, @michaelchampion)
-
Is a Community Group the right place to develop our own Process? w3c/AB-public#295 (4 comments by @dwsinger, @frivoal, @mnot)
-
Add Sustainability as a principle or value in the Vision w3c/AB-public#62 (4 comments by @frivoal, @nigelmegitt, @tantek)
-
We should start the formatting of the Vision as a (Draft) Note w3c/AB-public#73 (3 comments by @cwilso, @fantasai, @frivoal)
-
Adding content related to the future Web w3c/AB-public#67 (3 comments by @cwilso, @KotisK, @michaelchampion)
-
-
1 pull request opened.
-
Voluntary standards (fixes #69) w3c/AB-public#70, by @cwilso.
-
-
2 pull requests closed.
-
add malvertising to current web harms w3c/AB-public#49.
-
voluntary standards forum w3c/AB-public#61.
-
-
3 pull requests received 3 new comments.
w3c/process
-
18 issues opened.
-
Minority Opinions w3c/process#752, by @mnot.
-
Council decision side effects w3c/process#751, by @mnot.
-
Dissent in AC review w3c/process#750, by @mnot.
-
Conflict of Interest in Council composition w3c/process#749, by @mnot.
-
Dismissal voting w3c/process#748, by @mnot.
-
Editorial: dismissal w3c/process#747, by @mnot.
-
Avoid using two different meanings of "sustain" w3c/process#746, by @jyasskin.
-
Remove normative keywords from non-normative sections w3c/process#745, by @jyasskin.
-
Clarify where Submission Appeals go w3c/process#742, by @jyasskin.
-
"Regression on the REC track" should say what kind of approval is needed w3c/process#741, by @jyasskin.
-
AC Review is missing a step to resolve formal objections w3c/process#739, by @jyasskin.
-
AC Review dissent requirement vs questionnaire options w3c/process#738, by @jyasskin.
-
Addressing formal objections before requesting advancement w3c/process#737, by @jyasskin.
-
Requirement to publish formal objections should include a timeline w3c/process#735, by @jyasskin.
-
Broken link in changes section w3c/process#734, by @jyasskin.
-
Use Alias rather than Redirect for /Consortium/Process w3c/process#729, by @fantasai.
-
Editorial: "W3C" as a proper noun w3c/process#728, by @koalie.
-
-
2 issues closed.
-
Broken link in changes section w3c/process#734.
-
Editorial: "W3C" as a proper noun w3c/process#728.
-
-
10 issues received 19 new comments.
-
AC Review dissent requirement vs questionnaire options w3c/process#738 (4 comments by @frivoal, @jyasskin, @nigelmegitt)
-
Addressing formal objections before requesting advancement w3c/process#737 (4 comments by @chrisn, @jyasskin, @nigelmegitt)
-
FPWD → CRS transition has onerous change documentation requirements w3c/process#727 (2 comments by @dontcallmedom, @frivoal)
-
-
6 pull requests opened.
-
Say that Chair Decision Appeals were also merged with Formal Objections. w3c/process#743, by @jyasskin.
-
Don't say that dissent goes away when it's overruled w3c/process#740, by @jyasskin.
-
Expand the TAG from 6+3 to 8+3 participants w3c/process#733, by @frivoal.
-
Update SoTD w3c/process#732, by @swickr.
-
editorial change to harmonize "website"/"Web site" w3c/process#731, by @koalie.
-
Use “W3C”, not “the W3C” w3c/process#730, by @frivoal.
-
-
3 pull requests merged.
-
Update SoTD w3c/process#732.
-
Use “W3C”, not “the W3C” w3c/process#730.
-
editorial change to harmonize "website"/"Web site" w3c/process#731.
-
-
2 pull requests received 13 new comments.
-
Don't say that dissent goes away when it's overruled w3c/process#740 (11 comments by @dwsinger, @jyasskin, @nigelmegitt, @TallTed)
-
w3c-cg/PWETF
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Goal of the CEPC w3c-cg/PWETF#258, by @wareid.
-
-
2 pull requests merged.
-
Patronizing Language (Issue 232) w3c-cg/PWETF#237.
-
safety v comfort update w3c-cg/PWETF#251.
-
-
3 pull requests closed.
-
Issue 230 - proposed changes - Include an up-front overview of the code w3c-cg/PWETF#240.
-
Issue 232 proposed changes w3c-cg/PWETF#238.
-
-
4 pull requests received 15 new comments.
-
Patronizing Language (Issue 232) w3c-cg/PWETF#237 (12 comments by @a11ydoer, @cwilso, @dbooth-boston, @nigelmegitt, @swickr, @wareid)
-
Issue 230 - proposed changes - Include an up-front overview of the code w3c-cg/PWETF#240 (1 comment by @tobie)
-
w3c/PWETF
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Goal of the CEPC w3c/PWETF#258, by @wareid.
-
-
2 pull requests merged.
-
Patronizing Language (Issue 232) w3c/PWETF#237.
-
safety v comfort update w3c/PWETF#251.
-
-
3 pull requests closed.
-
Issue 232 proposed changes w3c/PWETF#238.
-
4 pull requests received 15 new comments.
-
Patronizing Language (Issue 232) w3c/PWETF#237 (12 comments by @a11ydoer, @cwilso, @dbooth-boston, @nigelmegitt, @swickr, @wareid)
-
Issue 230 - proposed changes - Include an up-front overview of the code w3c/PWETF#240 (1 comment by @tobie)
-
Vision Task Force
Past meetings
-
1 meeting of the Vision Task Force.
Past meetings
GitHub
w3c/process
-
6 issues opened.
-
FPWD → CRS transition has onerous change documentation requirements w3c/process#727, by @dontcallmedom.
-
Candidate Recommendation Draft vs "return to Working Draft" w3c/process#726, by @dontcallmedom.
-
Registry report requirements w3c/process#725, by @chrisn.
-
Ratification of TAG appointments w3c/process#715, by @mnot.
-
Rename Acknowledgement (for Member submission requests) w3c/process#714, by @frivoal.
-
-
4 issues closed.
-
"The W3C Council" should often be "A W3C Council" w3c/process#710.
-
Ratification of TAG appointments w3c/process#715.
-
export registry-related terms for ease of reference w3c/process#713.
-
22 issues received 77 new comments.
-
Rename Acknowledgement (for Member submission requests) w3c/process#714 (10 comments by @chrisn, @dwsinger, @fantasai, @frivoal, @koalie, @nigelmegitt)
-
Ratification of TAG appointments w3c/process#715 (8 comments by @css-meeting-bot, @cwilso, @dwsinger, @fantasai, @mnot, @swickr)
-
Appeal process for proposals w3c/process#478 (6 comments by @chaals, @fantasai, @frivoal, @jwrosewell)
-
Should a team-confidential formal objection lead to a team-confidential council report? w3c/process#717 (5 comments by @css-meeting-bot, @dwsinger, @frivoal, @swickr)
-
TAG appointment should be via IETF style nomcom w3c/process#230 (4 comments by @frivoal, @mnot, @nrooney)
-
Stronger emphasis on reaching Recommendation w3c/process#443 (3 comments by @chrisn, @frivoal, @plehegar)
-
The team should not be expected to recommend a disposition of an FO w3c/process#629 (3 comments by @frivoal, @palemieux)
-
Order of precedence of Membership Agreement, Process document and normative references w3c/process#574 (2 comments by @css-meeting-bot, @fantasai)
-
Setup document management for director-free matters w3c/process#366 (2 comments by @frivoal, @LJWatson)
-
Grace period for contributing to specifications? w3c/process#672 (2 comments by @frivoal, @jyasskin)
-
Sustaining an FO should always require super-majority support w3c/process#631 (2 comments by @frivoal, @palemieux)
-
FO Council should not be allowed to delegate its responsibility w3c/process#630 (2 comments by @frivoal, @palemieux)
-
export registry-related terms for ease of reference w3c/process#713 (2 comments by @frivoal, @nigelmegitt)
-
-
4 pull requests opened.
-
Confidentiality Levels and Redactions w3c/process#722, by @joshco.
-
Fix up inconsistencies in the confidentiality of FOs and Council Reports w3c/process#720, by @frivoal.
-
Speak of *a* Council, not *the* Council w3c/process#719, by @frivoal.
-
Change who ratifies the TAG appointees w3c/process#718, by @frivoal.
-
-
3 pull requests merged.
-
Speak of *a* Council, not *the* Council w3c/process#719.
-
Change who ratifies the TAG appointees w3c/process#718.
-
4 pull requests received 8 new comments.
-
Fix up inconsistencies in the confidentiality of FOs and Council Reports w3c/process#720 (4 comments by @dwsinger, @frivoal, @nigelmegitt)
-
Rename Acknowledgement to Acceptance (for Member submission requests) w3c/process#640 (1 comment by @frivoal)
-
Clarify integration (and potential conflicts) between the Process and its normative references w3c/process#572 (1 comment by @nigelmegitt)
-
w3c-cg/PWETF
-
3 issues opened.
-
Just digging the vibe w3c-cg/PWETF#256, by @caltrops6490.
-
CEPCdisciplinary-process.md needs a SoTD w3c-cg/PWETF#252, by @swickr.
-
The Goal of the CEPC sets a rather low bar w3c-cg/PWETF#250, by @dwsinger.
-
-
3 issues closed.
-
Just digging the vibe w3c-cg/PWETF#256.
-
Add a CONTRIBUTING.md file to explain how to contribute w3c-cg/PWETF#242.
-
CEPCdisciplinary-process.md needs a SoTD w3c-cg/PWETF#252.
-
-
4 issues received 5 new comments.
-
The Goal of the CEPC sets a rather low bar w3c-cg/PWETF#250 (2 comments by @dwsinger, @TzviyaSiegman)
-
-
2 pull requests opened.
-
safety v comfort update w3c-cg/PWETF#251, by @TzviyaSiegman.
-
Issue 247 - Draft guidelines for forum moderation w3c-cg/PWETF#248, by @dbooth-boston.
-
-
3 pull requests merged.
-
Editorial Changes w3c-cg/PWETF#236.
-
Adding Update cadence text w3c-cg/PWETF#207.
-
Demonstrating proposed change to Code of Conduct w3c-cg/PWETF#245.
-
-
2 pull requests closed.
-
change the label w3c-cg/PWETF#165.
-
Verbal -> Informal w3c-cg/PWETF#183.
-
-
5 pull requests received 10 new comments.
-
Issue 247 - Draft guidelines for forum moderation w3c-cg/PWETF#248 (6 comments by @chrisn, @cwilso, @dbooth-boston)
-
Issue 230 - proposed changes - Include an up-front overview of the code w3c-cg/PWETF#240 (1 comment by @TzviyaSiegman)
-
w3c/PWETF
-
3 issues opened.
-
Just digging the vibe w3c/PWETF#256, by @caltrops6490.
-
CEPCdisciplinary-process.md needs a SoTD w3c/PWETF#252, by @swickr.
-
The Goal of the CEPC sets a rather low bar w3c/PWETF#250, by @dwsinger.
-
-
3 issues closed.
-
Just digging the vibe w3c/PWETF#256.
-
Add a CONTRIBUTING.md file to explain how to contribute w3c/PWETF#242.
-
CEPCdisciplinary-process.md needs a SoTD w3c/PWETF#252.
-
-
4 issues received 5 new comments.
-
2 pull requests opened.
-
safety v comfort update w3c/PWETF#251, by @TzviyaSiegman.
-
Issue 247 - Draft guidelines for forum moderation w3c/PWETF#248, by @dbooth-boston.
-
-
3 pull requests merged.
-
Editorial Changes w3c/PWETF#236.
-
Adding Update cadence text w3c/PWETF#207.
-
Demonstrating proposed change to Code of Conduct w3c/PWETF#245.
-
-
2 pull requests closed.
-
change the label w3c/PWETF#165.
-
Verbal -> Informal w3c/PWETF#183.
-
-
5 pull requests received 10 new comments.
-
Issue 247 - Draft guidelines for forum moderation w3c/PWETF#248 (6 comments by @chrisn, @cwilso, @dbooth-boston)
-
Issue 230 - proposed changes - Include an up-front overview of the code w3c/PWETF#240 (1 comment by @TzviyaSiegman)
-
w3c/AB-public
-
5 issues opened.
-
Thank contributors by name w3c/AB-public#64, by @chaals.
-
Proposal to re-organize the Mission/Principles/Values bullets w3c/AB-public#63, by @michaelchampion.
-
Add Sustainability as a principle or value in the Vision w3c/AB-public#62, by @michaelchampion.
-
Needs a Status [of this Document] section w3c/AB-public#60, by @swickr.
-
The Vision draft needs a Status section w3c/AB-public#59, by @chaals.
-
-
10 issues closed.
-
The Vision draft needs a Status section w3c/AB-public#59.
-
Add 'industries into 3rd bullet of principles? w3c/AB-public#7.
-
Extract useful points from AB discussion w3c/AB-public#6.
-
Split W3C and Web principles w3c/AB-public#4.
-
Purpose should encompass public at large w3c/AB-public#3.
-
Proposal to re-organize the Mission/Principles/Values bullets w3c/AB-public#63.
-
This very convoluted sentence... w3c/AB-public#44.
-
Needs a Status [of this Document] section w3c/AB-public#60.
-
-
12 issues received 34 new comments.
-
How should we develop the "W3C Vision and Values"? w3c/AB-public#57 (7 comments by @avneeshsingh, @dwsinger, @fantasai, @frivoal, @LJWatson)
-
Clarify intended use of the Vision document w3c/AB-public#53 (5 comments by @cwilso, @darobin, @dennis-dingwei, @dwsinger, @michaelchampion)
-
Keep the 2 strategic goals about meeting members business needs and ensuring industry adoption? w3c/AB-public#8 (4 comments by @chaals, @cwilso)
-
Add Sustainability as a principle or value in the Vision w3c/AB-public#62 (4 comments by @cwilso, @michaelchampion)
-
Proposal to re-organize the Mission/Principles/Values bullets w3c/AB-public#63 (4 comments by @cwilso, @michaelchampion)
-
Reconsider our definition of "World Wide Web" w3c/AB-public#58 (3 comments by @frivoal, @nigelmegitt, @swickr)
-
Improve Vision language to avoid colloquial or complex expressions w3c/AB-public#23 (1 comment by @cwilso)
-
Be more explicit about how to improve web's "integrity" w3c/AB-public#13 (1 comment by @michaelchampion)
-
-
2 pull requests opened.
-
Add status section w3c/AB-public#65, by @cwilso.
-
voluntary standards forum w3c/AB-public#61, by @tantek.
-
-
4 pull requests merged.
-
Add status section w3c/AB-public#65.
-
Rewritten intro to address readability w3c/AB-public#55.
-
Remove "and collective empowerment" w3c/AB-public#56.
-
Fixes #44 w3c/AB-public#54.
-
-
4 pull requests received 8 new comments.
-
Rewritten intro to address readability w3c/AB-public#55 (4 comments by @avneeshsingh, @cwilso, @dwsinger, @fantasai)
-
Past meetings
-
1 meeting.
GitHub
w3c/AB-public
-
5 issues opened.
-
Reconsider our definition of "World Wide Web" w3c/AB-public#58, by @nigelmegitt.
-
How should we develop the "W3C Vision and Values"? w3c/AB-public#57, by @chaals.
-
Clarify intended use of the Vision document w3c/AB-public#53, by @michaelchampion.
-
Normatively reference TAG Ethical Web Principles? w3c/AB-public#52, by @michaelchampion.
-
"Ensure the Web does not favor centralization" is not strong enough w3c/AB-public#50, by @cwilso.
-
-
5 issues closed.
-
Trim the Introductory section of the Vision w3c/AB-public#26.
-
Normatively reference TAG Ethical Web Principles? w3c/AB-public#52.
-
Community consensus w3c/AB-public#45.
-
The Vision no longer has a helpful title w3c/AB-public#35.
-
"Ensure the Web does not favor centralization" is not strong enough w3c/AB-public#50.
-
-
12 issues received 83 new comments.
-
Clarify intended use of the Vision document w3c/AB-public#53 (53 comments by @chaals, @cwilso, @darobin, @dwsinger, @frivoal, @michaelchampion, @mnot, @TzviyaSiegman)
-
what is "collective empowerment" and what does it have to do with interop? w3c/AB-public#37 (5 comments by @cwilso, @dwsinger, @TzviyaSiegman)
-
How should we develop the "W3C Vision and Values"? w3c/AB-public#57 (4 comments by @chaals, @chrisn, @fantasai, @frivoal)
-
Improve Vision language to avoid colloquial or complex expressions w3c/AB-public#23 (3 comments by @chaals, @cwilso)
-
Reconsider our definition of "World Wide Web" w3c/AB-public#58 (2 comments by @frivoal, @nigelmegitt)
-
-
8 pull requests opened.
-
Remove "and collective empowerment" w3c/AB-public#56, by @cwilso.
-
Rewritten intro to address readability w3c/AB-public#55, by @cwilso.
-
Aim to reduce centralization w3c/AB-public#51, by @cwilso.
-
add malvertising to current web harms w3c/AB-public#49, by @tantek.
-
Simplify time reference w3c/AB-public#48, by @chaals.
-
A Helpful Title w3c/AB-public#47, by @cwilso.
-
Consensus bullet point added w3c/AB-public#46, by @cwilso.
-
-
3 pull requests merged.
-
Consensus bullet point added w3c/AB-public#46.
-
A Helpful Title w3c/AB-public#47.
-
Aim to reduce centralization w3c/AB-public#51.
-
-
1 pull request closed.
-
Simplify time reference w3c/AB-public#48.
-
-
5 pull requests received 32 new comments.
-
Rewritten intro to address readability w3c/AB-public#55 (17 comments by @chaals, @cwilso, @dwsinger, @TzviyaSiegman)
-
w3c/process
-
3 issues opened.
-
export registry-related terms for ease of reference w3c/process#713, by @nigelmegitt.
-
Are Statements fit for purpose? w3c/process#712, by @mnot.
-
"The W3C Council" should often be "A W3C Council" w3c/process#710, by @TallTed.
-
-
8 issues closed.
-
Clarify AC and BoD priority when signing MoUs and similar contracts w3c/process#670.
-
Should W3C continue to stagger AB/TAG elections ? w3c/process#688.
-
Ensuring charters fit the mission and values of W3C w3c/process#620.
-
[Editorial] Adjust grounding of RF distribution of specifications w3c/process#681.
-
11 issues received 26 new comments.
-
Are Statements fit for purpose? w3c/process#712 (13 comments by @chaals, @dwsinger, @frivoal, @michaelchampion, @mnot, @nigelmegitt, @TzviyaSiegman)
-
Mandate default custodianship for Registries if the specified custodian is no longer available w3c/process#699 (1 comment by @frivoal)
-
[Editorial] Where Formal Objection is defined, identify milder ways to express disagreement w3c/process#680 (1 comment by @frivoal)
-
[editorial] Council composition statement spends too much time on exceptions w3c/process#679 (1 comment by @css-meeting-bot)
-
Clarify AC and BoD priority when signing MoUs and similar contracts w3c/process#670 (1 comment by @css-meeting-bot)
-
Should there be good standing / supermajority criteria in authoritative ballots? w3c/process#76 (1 comment by @michaelchampion)
-
Possibly dismissing a Formal Objection before it goes to full Council? w3c/process#678 (1 comment by @frivoal)
-
-
2 pull requests opened.
-
Editorial cleanup regarding normative dependencies of the Process w3c/process#711, by @frivoal.
-
Enable changes of chair in a Council w3c/process#709, by @frivoal.
-
-
9 pull requests merged.
-
Clarify interactions between AC / Team / Board about MoUs w3c/process#704.
-
Editorial cleanup regarding normative dependencies of the Process w3c/process#711.
-
Simplify phrasing about council composition w3c/process#706.
-
Correct reference to W3C Document / Software licensing w3c/process#705.
-
Introduce path to shortcut the Council w3c/process#703.
-
Enable changes of chair in a Council w3c/process#709.
-
Include Council Team Contact in the confidence of the Council w3c/process#702.
-
Clarify role of Council Team Contact (and define the term) w3c/process#701.
-
-
9 pull requests received 69 new comments.
-
Simplify phrasing about council composition w3c/process#706 (20 comments by @chrisn, @css-meeting-bot, @cwilso, @dwsinger, @fantasai, @frivoal, @nigelmegitt, @TallTed)
-
Clarify interactions between AC / Team / Board about MoUs w3c/process#704 (18 comments by @css-meeting-bot, @cwilso, @dwsinger, @frivoal, @LJWatson, @nigelmegitt, @TallTed)
-
Rename Acknowledgement to Acceptance (for Member submission requests) w3c/process#640 (10 comments by @css-meeting-bot, @fantasai, @frivoal, @koalie, @nigelmegitt, @TallTed)
-
Editorial cleanup regarding normative dependencies of the Process w3c/process#711 (6 comments by @chrisn, @css-meeting-bot, @dwsinger, @TallTed)
-
Include Council Team Contact in the confidence of the Council w3c/process#702 (5 comments by @frivoal, @nigelmegitt, @TallTed)
-
Clarify integration (and potential conflicts) between the Process and its normative references w3c/process#572 (2 comments by @frivoal, @nigelmegitt)
-
w3c-cg/PWETF
-
6 issues opened.
-
Moderation of W3C lists w3c-cg/PWETF#247, by @dbooth-boston.
-
Add a CONTRIBUTING.md file to explain how to contribute w3c-cg/PWETF#242, by @nigelmegitt.
-
Definition of "Microaggression" w3c-cg/PWETF#235, by @dbooth-boston.
-
"Improper" is elitist and arbitrary w3c-cg/PWETF#234, by @dbooth-boston.
-
Move and clarify the "Safety versus comfort" section w3c-cg/PWETF#233, by @dbooth-boston.
-
Clarify bullets on "patronizing language or behavior" w3c-cg/PWETF#232, by @dbooth-boston.
-
-
4 issues closed.
-
CEPC lacks a code of ethics w3c-cg/PWETF#223.
-
Add "or microharms" or otherwise reword the Microaggressions bullet w3c-cg/PWETF#231.
-
CEPC: How to politely correct someone? w3c-cg/PWETF#226.
-
CEPC: Assume that the audience is "intelligent but uninformed" w3c-cg/PWETF#225.
-
-
9 issues received 34 new comments.
-
Definition of "Microaggression" w3c-cg/PWETF#235 (9 comments by @cwilso, @dbooth-boston, @nigelmegitt, @torgo, @TzviyaSiegman)
-
Add "or microharms" or otherwise reword the Microaggressions bullet w3c-cg/PWETF#231 (8 comments by @cwilso, @dbooth-boston, @hober, @LJWatson, @nigelmegitt, @TzviyaSiegman)
-
sensory rooms at TPAC w3c-cg/PWETF#213 (6 comments by @cwilso, @jenstrickland, @LJWatson, @plehegar, @TzviyaSiegman, @wareid)
-
CEPC: Assume that the audience is "intelligent but uninformed" w3c-cg/PWETF#225 (2 comments by @dbooth-boston)
-
Move and clarify the "Safety versus comfort" section w3c-cg/PWETF#233 (2 comments by @dbooth-boston, @nigelmegitt)
-
Add a CONTRIBUTING.md file to explain how to contribute w3c-cg/PWETF#242 (1 comment by @dbooth-boston)
-
-
10 pull requests opened.
-
CEPC preamble initial w3c-cg/PWETF#246, by @TzviyaSiegman.
-
Demonstrating proposed change to Code of Conduct w3c-cg/PWETF#245, by @wareid.
-
Adding DR White Supremacy Culture w3c-cg/PWETF#244, by @TzviyaSiegman.
-
Adding a contributing guide and editing readme w3c-cg/PWETF#243, by @wareid.
-
Issue 235 - proposed changes - Definition of "Microaggression" w3c-cg/PWETF#241, by @dbooth-boston.
-
Issue 230 - proposed changes - Include an up-front overview of the code w3c-cg/PWETF#240, by @dbooth-boston.
-
Issue 232 proposed changes w3c-cg/PWETF#238, by @dbooth-boston.
-
Patronizing Language (Issue 232) w3c-cg/PWETF#237, by @wareid.
-
Editorial Changes w3c-cg/PWETF#236, by @wareid.
-
-
3 pull requests merged.
-
Adding a contributing guide and editing readme w3c-cg/PWETF#243.
-
ins "and" w3c-cg/PWETF#227.
-
Adding DR White Supremacy Culture w3c-cg/PWETF#244.
-
-
6 pull requests received 43 new comments.
-
Patronizing Language (Issue 232) w3c-cg/PWETF#237 (18 comments by @cwilso, @dbooth-boston, @nigelmegitt, @TzviyaSiegman, @wareid)
-
Adding a contributing guide and editing readme w3c-cg/PWETF#243 (11 comments by @cwilso, @dbooth-boston, @nigelmegitt, @npdoty, @TzviyaSiegman)
-
Issue 233 - proposed changes - Move and clarify the "Safety versus comfort" section w3c-cg/PWETF#239 (3 comments by @dbooth-boston, @wareid)
-
Issue 230 - proposed changes - Include an up-front overview of the code w3c-cg/PWETF#240 (2 comments by @dbooth-boston, @wareid)
-
Issue 235 - proposed changes - Definition of "Microaggression" w3c-cg/PWETF#241 (2 comments by @dbooth-boston, @wareid)
-
w3c/PWETF
-
6 issues opened.
-
Moderation of W3C lists w3c/PWETF#247, by @dbooth-boston.
-
Add a CONTRIBUTING.md file to explain how to contribute w3c/PWETF#242, by @nigelmegitt.
-
Definition of "Microaggression" w3c/PWETF#235, by @dbooth-boston.
-
"Improper" is elitist and arbitrary w3c/PWETF#234, by @dbooth-boston.
-
Move and clarify the "Safety versus comfort" section w3c/PWETF#233, by @dbooth-boston.
-
Clarify bullets on "patronizing language or behavior" w3c/PWETF#232, by @dbooth-boston.
-
-
4 issues closed.
-
CEPC lacks a code of ethics w3c/PWETF#223.
-
CEPC: How to politely correct someone? w3c/PWETF#226.
-
-
9 issues received 34 new comments.
-
Definition of "Microaggression" w3c/PWETF#235 (9 comments by @cwilso, @dbooth-boston, @nigelmegitt, @torgo, @TzviyaSiegman)
-
Add "or microharms" or otherwise reword the Microaggressions bullet w3c/PWETF#231 (8 comments by @cwilso, @dbooth-boston, @hober, @LJWatson, @nigelmegitt, @TzviyaSiegman)
-
sensory rooms at TPAC w3c/PWETF#213 (6 comments by @cwilso, @jenstrickland, @LJWatson, @plehegar, @TzviyaSiegman, @wareid)
-
CEPC: Assume that the audience is "intelligent but uninformed" w3c/PWETF#225 (2 comments by @dbooth-boston)
-
Move and clarify the "Safety versus comfort" section w3c/PWETF#233 (2 comments by @dbooth-boston, @nigelmegitt)
-
-
10 pull requests opened.
-
CEPC preamble initial w3c/PWETF#246, by @TzviyaSiegman.
-
Demonstrating proposed change to Code of Conduct w3c/PWETF#245, by @wareid.
-
Adding DR White Supremacy Culture w3c/PWETF#244, by @TzviyaSiegman.
-
Adding a contributing guide and editing readme w3c/PWETF#243, by @wareid.
-
Issue 235 - proposed changes - Definition of "Microaggression" w3c/PWETF#241, by @dbooth-boston.
-
Issue 232 proposed changes w3c/PWETF#238, by @dbooth-boston.
-
Patronizing Language (Issue 232) w3c/PWETF#237, by @wareid.
-
Editorial Changes w3c/PWETF#236, by @wareid.
-
-
3 pull requests merged.
-
Adding a contributing guide and editing readme w3c/PWETF#243.
-
ins "and" w3c/PWETF#227.
-
Adding DR White Supremacy Culture w3c/PWETF#244.
-
-
6 pull requests received 43 new comments.
-
Patronizing Language (Issue 232) w3c/PWETF#237 (18 comments by @cwilso, @dbooth-boston, @nigelmegitt, @TzviyaSiegman, @wareid)
-
Adding a contributing guide and editing readme w3c/PWETF#243 (11 comments by @cwilso, @dbooth-boston, @nigelmegitt, @npdoty, @TzviyaSiegman)
-
Issue 233 - proposed changes - Move and clarify the "Safety versus comfort" section w3c/PWETF#239 (3 comments by @dbooth-boston, @wareid)
-
Issue 230 - proposed changes - Include an up-front overview of the code w3c/PWETF#240 (2 comments by @dbooth-boston, @wareid)
-
Issue 235 - proposed changes - Definition of "Microaggression" w3c/PWETF#241 (2 comments by @dbooth-boston, @wareid)
-
Participants
-
4 participants joined.
-
Qing An joined.
-
Elika Etemad joined.
-
Chaals Nevile joined.
-
Tantek Çelik joined.
-
-
5 participants left.
-
Hongru (Judy) Zhu left.
-
Léonie Watson left.
-
Eric Siow left.
-
David Singer left.
-
Wendy Seltzer left.
-
GitHub
w3c/AB-public
-
7 issues opened.
-
Community consensus w3c/AB-public#45, by @mnot.
-
This very convoluted sentence... w3c/AB-public#44, by @fantasai.
-
Adopt semantic line breaks in source code w3c/AB-public#42, by @fantasai.
-
Oxford commas: yes or no? w3c/AB-public#39, by @cwilso.
-
what is "collective empowerment" and what does it have to do with interop? w3c/AB-public#37, by @dwsinger.
-
The Vision no longer has a helpful title w3c/AB-public#35, by @dwsinger.
-
-
6 issues closed.
-
Adopt semantic line breaks in source code w3c/AB-public#42.
-
Oxford commas: yes or no? w3c/AB-public#39.
-
Don't refer to people as "other things" w3c/AB-public#32.
-
Create a clearer structure for the Vision document w3c/AB-public#27.
-
-
11 issues received 58 new comments.
-
The Vision no longer has a helpful title w3c/AB-public#35 (16 comments by @avneeshsingh, @cwilso, @dwsinger)
-
Vision document principles and values mixes values for the web with values for the consortium w3c/AB-public#36 (14 comments by @cwilso, @dwsinger, @TzviyaSiegman)
-
what is "collective empowerment" and what does it have to do with interop? w3c/AB-public#37 (10 comments by @avneeshsingh, @cwilso, @dwsinger)
-
Oxford commas: yes or no? w3c/AB-public#39 (5 comments by @avneeshsingh, @cwilso, @frivoal, @michaelchampion)
-
Put support of human rights into our Vision? w3c/AB-public#34 (5 comments by @avneeshsingh, @cwilso, @dwsinger, @TzviyaSiegman)
-
W3C's vision should not only be "Vision on Web", but also "Vision for W3C" w3c/AB-public#25 (2 comments by @cwilso, @dennis-dingwei)
-
Improve Vision language to avoid colloquial or complex expressions w3c/AB-public#23 (1 comment by @TzviyaSiegman)
-
-
4 pull requests opened.
-
Semantic linefeeds added to document w3c/AB-public#43, by @cwilso.
-
Separate external- and internal-focused principles and values w3c/AB-public#41, by @cwilso.
-
Enforce consistent Oxford comma style w3c/AB-public#40, by @cwilso.
-
Fix #32: Don't refer to people as "other things" w3c/AB-public#38, by @cwilso.
-
-
5 pull requests merged.
-
Semantic linefeeds added to document w3c/AB-public#43.
-
Separate external- and internal-focused principles and values w3c/AB-public#41.
-
Enforce consistent Oxford comma style w3c/AB-public#40.
-
Fix #32: Don't refer to people as "other things" w3c/AB-public#38.
-
Finer-grained refactoring of Vision document restructuring w3c/AB-public#30.
-
-
1 pull request closed.
-
Break up a complicated bullet w3c/AB-public#31.
-
-
4 pull requests received 16 new comments.
-
Separate external- and internal-focused principles and values w3c/AB-public#41 (2 comments by @dwsinger, @frivoal)
w3c-cg/PWETF
-
4 issues opened.
-
Add "or microharms" or otherwise reword the Microaggressions bullet w3c-cg/PWETF#231, by @dbooth-boston.
-
Include an up-front overview of the code w3c-cg/PWETF#230, by @dbooth-boston.
-
W3C Ombuds list is out of date w3c-cg/PWETF#229, by @npdoty.
-
CEPC: Safety versus comfort w3c-cg/PWETF#228, by @dbooth-boston.
-
-
3 issues closed.
-
W3C Ombuds list is out of date w3c-cg/PWETF#229.
-
CEPC: Missing word in sentence w3c-cg/PWETF#224.
-
Child care w3c-cg/PWETF#217.
-
-
1 issue reopened.
-
CEPC: Safety versus comfort w3c-cg/PWETF#228, by @TzviyaSiegman.
-
-
6 issues received 25 new comments.
-
CEPC: How to politely correct someone? w3c-cg/PWETF#226 (9 comments by @cwilso, @dbooth-boston, @nigelmegitt, @rigow, @TzviyaSiegman, @wareid)
-
CEPC: Assume that the audience is "intelligent but uninformed" w3c-cg/PWETF#225 (2 comments by @cwilso, @dbooth-boston)
-
-
1 pull request opened.
-
ins "and" w3c-cg/PWETF#227, by @TzviyaSiegman.
-
w3c/PWETF
-
4 issues opened.
-
Include an up-front overview of the code w3c/PWETF#230, by @dbooth-boston.
-
W3C Ombuds list is out of date w3c/PWETF#229, by @npdoty.
-
CEPC: Safety versus comfort w3c/PWETF#228, by @dbooth-boston.
-
3 issues closed.
-
W3C Ombuds list is out of date w3c/PWETF#229.
-
CEPC: Missing word in sentence w3c/PWETF#224.
-
Child care w3c/PWETF#217.
-
-
1 issue reopened.
-
CEPC: Safety versus comfort w3c/PWETF#228, by @TzviyaSiegman.
-
-
6 issues received 25 new comments.
-
CEPC: How to politely correct someone? w3c/PWETF#226 (9 comments by @cwilso, @dbooth-boston, @nigelmegitt, @rigow, @TzviyaSiegman, @wareid)
-
CEPC: Assume that the audience is "intelligent but uninformed" w3c/PWETF#225 (2 comments by @cwilso, @dbooth-boston)
-
-
1 pull request opened.
-
ins "and" w3c/PWETF#227, by @TzviyaSiegman.
-
w3c/process
-
5 issues opened.
-
Clarify and simplify the sections regarding publication and process 2021 w3c/process#700, by @wareid.
-
Votes transparency w3c/process#698, by @marcoscaceres.
-
Incumbent bias in elections / impose term limits? w3c/process#697, by @marcoscaceres.
-
TAG charter needs revision for Director-free alignment w3c/process#695, by @ianbjacobs.
-
-
5 issues closed.
-
What is the CR Review Period? w3c/process#637.
-
Closing Groups w3c/process#653.
-
Reintroduce the conditions for closure of a group w3c/process#685.
-
Should appeal request be shared with the Membership? w3c/process#603.
-
TAG charter needs revision for Director-free alignment w3c/process#695.
-
-
20 issues received 74 new comments.
-
Incomplete Term Assignment Choices w3c/process#694 (16 comments by @chaals, @cwilso, @dwsinger, @frivoal, @TzviyaSiegman)
-
Incumbent bias in elections / impose term limits? w3c/process#697 (11 comments by @chaals, @cwilso, @dwsinger, @frivoal, @marcoscaceres, @michaelchampion)
-
TAG charter needs revision for Director-free alignment w3c/process#695 (10 comments by @chaals, @dwsinger, @fantasai, @ianbjacobs, @TzviyaSiegman)
-
Ensuring charters fit the mission and values of W3C w3c/process#620 (8 comments by @chaals, @cwilso, @dwsinger, @michaelchampion, @mnot)
-
Possibly dismissing a Formal Objection before it goes to full Council? w3c/process#678 (7 comments by @dwsinger, @fantasai, @frivoal, @michaelchampion, @mnot)
-
Mandate default custodianship for Registries if the specified custodian is no longer available w3c/process#699 (3 comments by @dwsinger, @frivoal, @TallTed)
-
[patent policy] Exclusion opportunity when work leaves a Working Group w3c/process#518 (2 comments by @dwsinger, @plehegar)
-
[Editorial] Where Formal Objection is defined, identify milder ways to express disagreement w3c/process#680 (1 comment by @frivoal)
-
Community Groups and Business Groups should be incorporated into the Process w3c/process#409 (1 comment by @plehegar)
-
Have the normal, default, decision policy for charters in the process w3c/process#425 (1 comment by @plehegar)
-
Should appeal request be shared with the Membership? w3c/process#603 (1 comment by @css-meeting-bot)
-
-
7 pull requests opened.
-
Simplify phrasing about council composition w3c/process#706, by @frivoal.
-
Correct reference to W3C Document / Software licensing w3c/process#705, by @frivoal.
-
Clarify interactions between AC / Team / Board about MoUs w3c/process#704, by @frivoal.
-
Introduce path to shortcut the Council w3c/process#703, by @frivoal.
-
Include Council Team Contact in the confidence of the Council w3c/process#702, by @frivoal.
-
Clarify role of Council Team Contact (and define the term) w3c/process#701, by @frivoal.
-
Update conditions for proposing closure of a group w3c/process#696, by @frivoal.
-
-
3 pull requests merged.
-
Clarify what the CR review period is w3c/process#691.
-
Update conditions for proposing closure of a group w3c/process#696.
-
-
3 pull requests closed.
-
Simplify the text on liaisons w3c/process#433.
-
Make it clear than any decision can be objected to w3c/process#299.
-
Broaden who may propose group closure w3c/process#660.
-
-
6 pull requests received 20 new comments.
-
Clarify role of Council Team Contact (and define the term) w3c/process#701 (5 comments by @frivoal, @TallTed)
-
Clarify interactions between AC / Team / Board about MoUs w3c/process#704 (2 comments by @frivoal, @TallTed)
-
Update conditions for proposing closure of a group w3c/process#696 (2 comments by @css-meeting-bot, @TallTed)