Advisory Board - Activity in 2024
No matches.
GitHub
w3c-cg/PWETF
-
1 issue opened.
-
Clarify W3C group participants w3c-cg/PWETF#396, by @csarven.
-
-
3 pull requests opened.
-
Create jekyll-docker.yml w3c-cg/PWETF#395, by @Melissa1181.
-
Create devcontainer.json w3c-cg/PWETF#392, by @Melissa1181.
-
Create jekyll-docker.yml w3c-cg/PWETF#391, by @Karinza38.
-
-
2 pull requests closed.
-
Create devcontainer.json w3c-cg/PWETF#392.
-
Create jekyll-docker.yml w3c-cg/PWETF#391.
-
-
1 pull request reopened.
-
Create jekyll-docker.yml w3c-cg/PWETF#390, by @Melissa1181.
-
-
2 pull requests received 3 new comments.
w3c/PWETF
-
1 issue opened.
-
Clarify W3C group participants w3c/PWETF#396, by @csarven.
-
-
3 pull requests opened.
-
Create jekyll-docker.yml w3c/PWETF#395, by @Melissa1181.
-
Create devcontainer.json w3c/PWETF#392, by @Melissa1181.
-
Create jekyll-docker.yml w3c/PWETF#391, by @Karinza38.
-
-
2 pull requests closed.
-
Create devcontainer.json w3c/PWETF#392.
-
Create jekyll-docker.yml w3c/PWETF#391.
-
-
1 pull request reopened.
-
Create jekyll-docker.yml w3c/PWETF#390, by @Melissa1181.
-
-
2 pull requests received 3 new comments.
w3c/process
-
6 issues opened.
-
Remnant of Proposed Recommendation w3c/process#965, by @vivienlacourba.
-
Exclusion Documents can be Recommendations, not just Drafts w3c/process#963, by @svgeesus.
-
URIs to W3C Process and Patent Policy docs w3c/process#962, by @vivienlacourba.
-
The Team should be able to initiate AC Review of charter draft w3c/process#959, by @plehegar.
-
Automatic Extension of Nomination Period due to Insufficient Candidates w3c/process#949, by @fantasai.
-
Change participation requirements for editors w3c/process#948, by @cwadamsoforacle.
-
-
11 issues closed.
-
Candidate Recommendation Draft vs "return to Working Draft" w3c/process#726.
-
Are TAG Appointments mandatory for the Team to fill? w3c/process#811.
-
Clarify deadline for nominations w3c/process#464.
-
Visibility of FO handling w3c/process#870.
-
Remnant of Proposed Recommendation w3c/process#965.
-
Align with Bylaws changes w3c/process#849.
-
Do we need a procedural track for "disclosure" documents? w3c/process#460.
-
24 issues received 63 new comments.
-
Change participation requirements for editors w3c/process#948 (20 comments by @alastc, @chaals, @csarven, @fantasai, @frivoal, @iadawn, @michael-n-cooper, @nigelmegitt, @plehegar, @rigow, @swickr, @TallTed, @xfq)
-
Open up Registries to IG, TAG, AB w3c/process#902 (8 comments by @fantasai, @frivoal, @jyasskin, @nigelmegitt)
-
Feedback on Charter refinement draft text w3c/process#934 (4 comments by @css-meeting-bot, @fantasai, @ianbjacobs)
-
URIs to W3C Process and Patent Policy docs w3c/process#962 (2 comments by @frivoal, @vivienlacourba)
-
Are TAG Appointments mandatory for the Team to fill? w3c/process#811 (2 comments by @fantasai, @plehegar)
-
Closing a group prior to the date specified in the charter should be a "Team Decision", not a "W3C Decision" w3c/process#797 (2 comments by @fantasai, @plehegar)
-
Candidate Recommendation Draft vs "return to Working Draft" w3c/process#726 (2 comments by @frivoal, @plehegar)
-
Chair appointment community involvement, transparency, enabling objections and handling them w3c/process#281 (2 comments by @frivoal, @plehegar)
-
Member submissions: can anyone else object, and if so, can they object to acceptance? w3c/process#639 (2 comments by @fantasai, @frivoal)
-
Confusing inconsistencies between stages of the REC track for documents and for amendments w3c/process#938 (1 comment by @frivoal)
-
The Team should be able to initiate AC Review of charter draft w3c/process#959 (1 comment by @frivoal)
-
Proposed addition to "9. Liaisons" to address delays in PAS Submissions to ISO w3c/process#946 (1 comment by @fantasai)
-
Strip section 6.2.2.1 “wide review” of the mailing list currently mentioned w3c/process#815 (1 comment by @frivoal)
-
The sentence about affiliation change causing a seat to be vacated is in the wrong place w3c/process#770 (1 comment by @fantasai)
-
-
8 pull requests opened.
-
Decrease emphasis on FO to charter rejection w3c/process#964, by @frivoal.
-
Fix links (2nd batch) w3c/process#961, by @vivienlacourba.
-
Fix links w3c/process#960, by @vivienlacourba.
-
Be more specific about when the council composition is locked down w3c/process#955, by @frivoal.
-
Introduce Good Standing w3c/process#954, by @frivoal.
-
Require documentation of how FOs get resolved w3c/process#953, by @frivoal.
-
Defer to /Guide for specific mailing lists to send review requests to w3c/process#952, by @frivoal.
-
Allow for some amount of leeway at the close of nomination periods w3c/process#950, by @frivoal.
-
-
6 pull requests merged.
-
Allow for some amount of leeway at the close of nomination periods w3c/process#950.
-
Require documentation of how FOs get resolved w3c/process#953.
-
Introduce Good Standing w3c/process#954.
-
Fix links (2nd batch) w3c/process#961.
-
Fix links w3c/process#960.
-
-
7 pull requests received 11 new comments.
-
Be more specific about when the council composition is locked down w3c/process#955 (3 comments by @frivoal, @plehegar, @TallTed)
-
Limit the involvement of Tim Berners-Lee to the TAG proper w3c/process#792 (2 comments by @frivoal, @torgo)
-
Defer to /Guide for specific mailing lists to send review requests to w3c/process#952 (1 comment by @plehegar)
-
Allow for some amount of leeway at the close of nomination periods w3c/process#950 (1 comment by @plehegar)
-
Generalizing AC Appeals and using this procedure for recall. w3c/process#888 (1 comment by @frivoal)
-
w3c/AB-public
-
3 issues opened.
-
Technical leadership needs a mention w3c/AB-public#221, by @hadleybeeman.
-
W3C Process & W3C Mission w3c/AB-public#220, by @fantasai.
-
Does incubation rise to the level of Vision? w3c/AB-public#219, by @martinthomson.
-
-
5 issues received 14 new comments.
-
Include the whole priority of constituencies w3c/AB-public#216 (6 comments by @chaals, @cwilso, @jyasskin, @martinthomson)
-
Vision should make a positive statement of how the Web should evolve w3c/AB-public#215 (4 comments by @chrishtr, @martinthomson)
-
Technical leadership needs a mention w3c/AB-public#221 (2 comments by @martinthomson, @michaelchampion)
-
Past meetings
-
1 meeting.
GitHub
w3c/process
-
3 issues opened.
-
Mathematical Error in Composition of the AB section w3c/process#942, by @wareid.
-
10 issues closed.
-
Typical group duration is not six months to two years w3c/process#918.
-
Inaccurate text about Membership Agreements w3c/process#879.
-
Charter creation w3c/process#650.
-
Simplify member submissions w3c/process#421.
-
Who convenes Workshops? w3c/process#649.
-
Registry report requirements w3c/process#725.
-
Should member submissions be removed from the Process? w3c/process#648.
-
Charter Approval w3c/process#651.
-
-
14 issues received 22 new comments.
-
Good standing w3c/process#935 (5 comments by @chrisn, @css-meeting-bot, @fantasai, @frivoal, @mgendler)
-
Confusing inconsistencies between stages of the REC track for documents and for amendments w3c/process#938 (3 comments by @fantasai, @frivoal)
-
Mathematical Error in Composition of the AB section w3c/process#942 (2 comments by @frivoal, @wareid)
-
How do I suggest a specification without making a whole draft about it? This specification will save lives. w3c/process#947 (1 comment by @frivoal)
-
Typical group duration is not six months to two years w3c/process#918 (1 comment by @css-meeting-bot)
-
Define charter review process to require addressing comments as in CR transitions w3c/process#182 (1 comment by @fantasai)
-
-
2 pull requests merged.
-
Simplify the section Member Submissions w3c/process#936.
-
fix id attr typo lifecyle->lifecycle w3c/process#939.
-
-
1 pull request closed.
-
Reference w3c-ac-forum policy which defines list access policy w3c/process#912.
-
-
2 pull requests received 8 new comments.
-
Reference w3c-ac-forum policy which defines list access policy w3c/process#912 (1 comment by @css-meeting-bot)
w3c/AB-public
-
4 issues opened.
-
Transparency is not mentioned w3c/AB-public#218, by @fantasai.
-
Do or do not; there is no "believe in" or "committed to" w3c/AB-public#217, by @jyasskin.
-
Include the whole priority of constituencies w3c/AB-public#216, by @jyasskin.
-
Vision should make a positive statement of how the Web should evolve w3c/AB-public#215, by @jyasskin.
-
-
8 issues received 10 new comments.
-
Is the term "users" the right way to refer to people that contribute to the Web's existence? w3c/AB-public#211 (3 comments by @capjamesg, @jenstrickland, @TzviyaSiegman)
-
Vision should make a positive statement of how the Web should evolve w3c/AB-public#215 (1 comment by @martinthomson)
-
Consider making thresholds relative to active participation w3c/AB-public#296 (1 comment by @plehegar)
-
w3c-cg/PWETF
-
1 issue opened.
-
Travel funding for TAG IEs towards enabling bigger participant pool w3c-cg/PWETF#389, by @rhiaro.
-
-
1 pull request opened.
-
Create jekyll-docker.yml w3c-cg/PWETF#390, by @Melissa1181.
-
w3c/PWETF
-
1 issue opened.
-
Travel funding for TAG IEs towards enabling bigger participant pool w3c/PWETF#389, by @rhiaro.
-
-
1 pull request opened.
-
Create jekyll-docker.yml w3c/PWETF#390, by @Melissa1181.
-
w3c/standards-track
-
1 issue closed.
-
needs a README with short summary and link to actual readable document w3c/standards-track#28.
-
-
1 pull request merged.
-
add link per issue #28 w3c/standards-track#32.
-
TR publications
-
1 document published.
-
Vision for W3C published as a Note. History of Vision for W3C
-
Past meetings
-
1 meeting.
GitHub
w3c/AB-public
-
5 issues opened.
-
Consideration for Section 2 of the Vision w3c/AB-public#213, by @jenstrickland.
-
Vision document does not say how vision is achieved w3c/AB-public#212, by @msporny.
-
W3C Vision: wide and horizontal reviews tracking w3c/AB-public#195, by @tantek.
-
Does this document articulate the W3C's mission? w3c/AB-public#188, by @chaals.
-
-
2 issues closed.
-
Does this document articulate the W3C's mission? w3c/AB-public#188.
-
Fix duplication of "equitable informed interconnected" w3c/AB-public#180.
-
-
9 issues received 54 new comments.
-
Who are the standards voluntary for? w3c/AB-public#177 (31 comments by @chaals, @chrisn, @csarven, @darobin, @fantasai, @frivoal, @mgendler, @michaelchampion, @mnot)
-
Vision document does not say how vision is achieved w3c/AB-public#212 (4 comments by @chrisn, @cwilso, @michaelchampion, @msporny)
-
Consider making thresholds relative to active participation w3c/AB-public#296 (1 comment by @frivoal)
-
-
22 pull requests opened.
-
revert to ED, new prev version, new changes subsection since 2nd Note w3c/AB-public#209, by @tantek.
-
handcode diff link NOTE to prev NOTE w3c/AB-public#208, by @tantek.
-
Prepare for TR: true for NOTE publication w3c/AB-public#207, by @tantek.
-
update one old ethical-web-principles link w3c/AB-public#206, by @tantek.
-
www.w3.org instead of w3.org w3c/AB-public#205, by @tantek.
-
add p role="navigation" per pubrules warning w3c/AB-public#204, by @tantek.
-
Status NOTE, drop p id="w3c-status" w3c/AB-public#203, by @tantek.
-
move w3c-state to end of doc w3c/AB-public#202, by @tantek.
-
add p id="w3c-state" as demanded by w3.org/pubrules w3c/AB-public#201, by @tantek.
-
update Previous Version link prev public Note w3c/AB-public#200, by @tantek.
-
Changes section: adjust diffs link text w3c/AB-public#199, by @tantek.
-
Changes section: explicit headings w3c/AB-public#198, by @tantek.
-
Changes section: Status section, add links to changes w3c/AB-public#197, by @tantek.
-
[Vision] Define voluntary standards as an operational principle w3c/AB-public#196, by @fantasai.
-
draft of Voluntary to Implement explicit principle w3c/AB-public#194, by @tantek.
-
Restructure Abstract/Introduction/Purpose w3c/AB-public#193, by @cwilso.
-
Reflect the reality that some W3C standards are voluntary and some not w3c/AB-public#192, by @darobin.
-
abbr around first use of "W3C" next to expansion w3c/AB-public#191, by @tantek.
-
Add ages and economic backgrounds w3c/AB-public#190, by @francescorn.
-
"(WWW)" in parallel structure to existing "(W3C)" in doc w3c/AB-public#189, by @francescorn.
-
update AB priority projects wiki link from 2021 to 2025 w3c/AB-public#187, by @tantek.
-
editorial: copy a SOTD consensus line from EWP w3c/AB-public#186, by @tantek.
-
-
18 pull requests merged.
-
revert to ED, new prev version, new changes subsection since 2nd Note w3c/AB-public#209.
-
handcode diff link NOTE to prev NOTE w3c/AB-public#208.
-
Prepare for TR: true for NOTE publication w3c/AB-public#207.
-
update one old ethical-web-principles link w3c/AB-public#206.
-
www.w3.org instead of w3.org w3c/AB-public#205.
-
add p role="navigation" per pubrules warning w3c/AB-public#204.
-
Status NOTE, drop p id="w3c-status" w3c/AB-public#203.
-
move w3c-state to end of doc w3c/AB-public#202.
-
add p id="w3c-state" as demanded by w3.org/pubrules w3c/AB-public#201.
-
update Previous Version link prev public Note w3c/AB-public#200.
-
Changes section: adjust diffs link text w3c/AB-public#199.
-
Changes section: explicit headings w3c/AB-public#198.
-
Changes section: Status section, add links to changes w3c/AB-public#197.
-
Give a sensical reading for "Be timeless enough" #167 w3c/AB-public#181.
-
update AB priority projects wiki link from 2021 to 2025 w3c/AB-public#187.
-
abbr around first use of "W3C" next to expansion w3c/AB-public#191.
-
editorial: copy a SOTD consensus line from EWP w3c/AB-public#186.
-
editorial: de-dupe a clause, shorten to principles-based, puncts w3c/AB-public#184.
-
-
4 pull requests closed.
-
Reflect the reality that some W3C standards are voluntary and some not w3c/AB-public#192.
-
Rename Introduction to Background w3c/AB-public#183.
-
draft of Voluntary to Implement explicit principle w3c/AB-public#194.
-
[Vision] Define voluntary standards as an operational principle w3c/AB-public#196.
-
-
11 pull requests received 57 new comments.
-
Clarify inclusion w3c/AB-public#185 (12 comments by @chaals, @cwilso, @fantasai, @francescorn, @mgendler, @tantek, @wareid)
-
Reflect the reality that some W3C standards are voluntary and some not w3c/AB-public#192 (12 comments by @chaals, @chrisn, @darobin, @frivoal, @mgendler, @michaelchampion, @tantek)
-
Give a sensical reading for "Be timeless enough" #167 w3c/AB-public#181 (8 comments by @cwilso, @fantasai, @frivoal, @tantek)
-
"(WWW)" in parallel structure to existing "(W3C)" in doc w3c/AB-public#189 (7 comments by @cwilso, @fantasai, @frivoal, @tantek)
-
Add ages and economic backgrounds w3c/AB-public#190 (4 comments by @chrisn, @frivoal, @tantek, @wareid)
-
[Vision] Define voluntary standards as an operational principle w3c/AB-public#196 (3 comments by @fantasai, @frivoal, @tantek)
-
draft of Voluntary to Implement explicit principle w3c/AB-public#194 (2 comments by @chaals, @tantek)
-
w3c/process
-
7 issues opened.
-
Good standing w3c/process#935, by @frivoal.
-
Feedback on Charter refinement draft text w3c/process#934, by @caribouW3.
-
Ambiguity in many voting rules w3c/process#933, by @martinthomson.
-
Update references to "CEPC" and "Code of Ethics and Professional Conduct" w3c/process#922, by @koalie.
-
Forbid holding multiple leadership positions w3c/process#921, by @martinthomson.
-
7 issues closed.
-
Charter review process w3c/process#580.
-
Clarify changes allowed during CR->REC transition w3c/process#919.
-
Multiple possible outcomes of a successful AC Appeal w3c/process#844.
-
Invited Experts without Member-only access w3c/process#900.
-
Closing the loop on resolving Formal Objections w3c/process#755.
-
Anonymous input for offline debate w3c/process#469.
-
-
20 issues received 59 new comments.
-
Forbid holding multiple leadership positions w3c/process#921 (27 comments by @chaals, @chrisn, @cwilso, @dwsinger, @fantasai, @frivoal, @igarashi50, @jyasskin, @martinthomson, @michaelchampion, @nigelmegitt, @rigow, @torgo, @wareid)
-
Confusing inconsistencies between stages of the REC track for documents and for amendments w3c/process#938 (4 comments by @fantasai, @frivoal)
-
Ambiguity about the formation time of a Council, and through that, about its composition w3c/process#926 (3 comments by @fantasai, @TallTed, @ylafon)
-
Multiple possible outcomes of a successful AC Appeal w3c/process#844 (2 comments by @css-meeting-bot, @fantasai)
-
Clarify changes allowed during CR->REC transition w3c/process#919 (2 comments by @css-meeting-bot, @fantasai)
-
Update references to "CEPC" and "Code of Ethics and Professional Conduct" w3c/process#922 (2 comments by @frivoal, @koalie)
-
Link for "W3C Horizontal Groups" doesn't describe W3C horizontal groups w3c/process#769 (1 comment by @frivoal)
-
Simplify Process 2021 (candidate|proposed) (change|addition|correction) terminology w3c/process#590 (1 comment by @frivoal)
-
-
8 pull requests opened.
-
fix id attr typo lifecyle->lifecycle w3c/process#939, by @tantek.
-
Simplify the section Member Submissions w3c/process#936, by @frivoal.
-
update BYLAWS reference to 2024 adopted revision w3c/process#930, by @tantek.
-
Forbid the Team from AB/TAG service w3c/process#929, by @martinthomson.
-
Require resignation from AB/TAG/BoD as a condition of service w3c/process#928, by @martinthomson.
-
Close review loopholes from dropping Proposed Recommendation w3c/process#927, by @frivoal.
-
Streamline Council formation and provide safeguards w3c/process#925, by @frivoal.
-
-
3 pull requests merged.
-
update BYLAWS reference to 2024 adopted revision w3c/process#930.
-
Streamline Council formation and provide safeguards w3c/process#925.
-
Close review loopholes from dropping Proposed Recommendation w3c/process#927.
-
-
2 pull requests closed.
-
Intro: State some high-level goals related to WGs and their specs w3c/process#894.
-
Allow Tim Berners-Lee to abstain in Unanimous Short Circuit votes w3c/process#793.
-
-
11 pull requests received 36 new comments.
-
Streamline Council formation and provide safeguards w3c/process#925 (6 comments by @css-meeting-bot, @frivoal, @TallTed)
-
Forbid the Team from AB/TAG service w3c/process#929 (5 comments by @cwilso, @dwsinger, @fantasai, @martinthomson)
-
Reference w3c-ac-forum policy which defines list access policy w3c/process#912 (5 comments by @css-meeting-bot, @fantasai, @frivoal, @koalie)
-
Intro: State some high-level goals related to WGs and their specs w3c/process#894 (5 comments by @chaals, @fantasai, @frivoal, @sideshowbarker, @TzviyaSiegman)
-
Require resignation from AB/TAG/BoD as a condition of service w3c/process#928 (4 comments by @cwilso, @martinthomson, @TallTed)
-
Adjust the status of Tim Berners-Lee in the TAG w3c/process#791 (4 comments by @frivoal, @martinthomson)
-
Close review loopholes from dropping Proposed Recommendation w3c/process#927 (3 comments by @fantasai, @frivoal, @TallTed)
-
Synchronize Advisory Committee representative and Consortium Member Representative w3c/process#937 (1 comment by @TallTed)
-
Add back language about substantive changes invalidating previous review w3c/process#887 (1 comment by @frivoal)
-
Allow Tim Berners-Lee to abstain in Unanimous Short Circuit votes w3c/process#793 (1 comment by @frivoal)
-
w3c-cg/PWETF
-
1 issue closed.
-
PWE page still refers to Director w3c-cg/PWETF#384.
-
-
1 issue received 3 new comments.
-
1 pull request opened.
-
Create SECURITY.md w3c-cg/PWETF#385, by @Anusorn1997.
-
-
1 pull request closed.
-
Create SECURITY.md w3c-cg/PWETF#385.
-
w3c/PWETF
-
1 issue closed.
-
PWE page still refers to Director w3c/PWETF#384.
-
-
1 issue received 3 new comments.
-
1 pull request opened.
-
Create SECURITY.md w3c/PWETF#385, by @Anusorn1997.
-
-
1 pull request closed.
-
Create SECURITY.md w3c/PWETF#385.
-
Vision Task Force
Participants
-
1 chair stepped down in the Vision Task Force.
-
Chris Wilson stepped down as a chair.
-
-
2 participants joined the Vision Task Force.
-
Max Gendler joined.
-
Tantek Çelik joined.
-
Past meetings
-
2 meetings.
GitHub
w3c/AB-public
-
4 issues opened.
-
Fix duplication of "equitable informed interconnected" w3c/AB-public#180, by @cwilso.
-
Who are the standards voluntary for? w3c/AB-public#177, by @darobin.
-
W3C Vision needs adversarial reading analyses w3c/AB-public#176, by @tantek.
-
W3C Participant Mailing List w3c/AB-public#172, by @wareid.
-
-
5 issues closed.
-
Thorough Review should mention technical soundness w3c/AB-public#170.
-
"supports truth over falsehood" may read like censorship w3c/AB-public#113.
-
Thank contributors by name w3c/AB-public#64.
-
Make it more clear that as a Statement the vision will continue to evolve w3c/AB-public#168.
-
smoke-testing the values... w3c/AB-public#126.
-
-
10 issues received 31 new comments.
-
W3C Participant Mailing List w3c/AB-public#172 (11 comments by @chaals, @chrisn, @cwilso, @frivoal, @igarashi50, @martinthomson, @tobie, @wareid)
-
interoperability across our work - architectural "integrity" w3c/AB-public#141 (2 comments by @chaals, @fantasai)
-
-
10 pull requests opened.
-
Clarify inclusion w3c/AB-public#185, by @fantasai.
-
editorial: de-dupe a clause, shorten to principles-based, puncts w3c/AB-public#184, by @tantek.
-
Rename Introduction to Background w3c/AB-public#183, by @fantasai.
-
Remove duplicate reference to "empower an equitable, informed, and in… w3c/AB-public#182, by @cwilso.
-
Give a sensical reading for "Be timeless enough" #167 w3c/AB-public#181, by @fantasai.
-
Restore “in other words” w3c/AB-public#179, by @fantasai.
-
Shuffle sentences to form a paragraph. w3c/AB-public#178, by @fantasai.
-
Add VisionTF to acks #64 w3c/AB-public#175, by @fantasai.
-
Shuffle SOTD sentences to avoid confusion. #168 w3c/AB-public#174, by @fantasai.
-
Add technical soundness and architectural integrity to Thorough Review w3c/AB-public#173, by @fantasai.
-
-
5 pull requests merged.
-
Shuffle sentences to form a paragraph. w3c/AB-public#178.
-
Restore “in other words” w3c/AB-public#179.
-
Add technical soundness and architectural integrity to Thorough Review w3c/AB-public#173.
-
Shuffle SOTD sentences to avoid confusion. #168 w3c/AB-public#174.
-
Add VisionTF to acks #64 w3c/AB-public#175.
-
-
1 pull request closed.
-
Remove duplicate reference to "empower an equitable, informed, and in… w3c/AB-public#182.
-
-
7 pull requests received 31 new comments.
-
Give a sensical reading for "Be timeless enough" #167 w3c/AB-public#181 (11 comments by @fantasai, @frivoal, @tantek)
-
Add technical soundness and architectural integrity to Thorough Review w3c/AB-public#173 (9 comments by @cwilso, @fantasai, @tantek)
-
editorial: de-dupe a clause, shorten to principles-based, puncts w3c/AB-public#184 (2 comments by @cwilso, @fantasai)
-
Remove duplicate reference to "empower an equitable, informed, and in… w3c/AB-public#182 (2 comments by @fantasai, @tantek)
-
w3c-cg/PWETF
-
1 issue opened.
-
PWE page still refers to Director w3c-cg/PWETF#384, by @gsnedders.
-
-
1 issue received 2 new comments.
-
"After the meeting" should recommend consideration of reaching out to Chair(s) and/or Team Contact(s) before Ombuds w3c-cg/PWETF#302 (2 comments by @Ebn7sh)
-
w3c/PWETF
-
1 issue opened.
-
PWE page still refers to Director w3c/PWETF#384, by @gsnedders.
-
-
1 issue received 2 new comments.
-
"After the meeting" should recommend consideration of reaching out to Chair(s) and/or Team Contact(s) before Ombuds w3c/PWETF#302 (2 comments by @Ebn7sh)
-
w3c/process
-
3 issues opened.
-
Clarify changes allowed during CR->REC transition w3c/process#919, by @fantasai.
-
Typical group duration is not six months to two years w3c/process#918, by @svgeesus.
-
Be consistent with terms "non-normative" and "informative" w3c/process#914, by @nigelmegitt.
-
-
4 issues closed.
-
Recommendation track diagram does not show Rec maintenance w3c/process#596.
-
Dealing with procedural disagreements within the Council w3c/process#843.
-
Determining AC Consensus of Post-Review Changes w3c/process#825.
-
REC track diagram does not reflect normative text w3c/process#638.
-
-
9 issues received 22 new comments.
-
"Candidate Recommendation" is no longer an accurate term w3c/process#402 (8 comments by @nigelmegitt, @rossberg, @sideshowbarker)
-
Open up Registries to IG, TAG, AB w3c/process#902 (4 comments by @dwsinger, @frivoal, @jyasskin, @nigelmegitt)
-
Recommendation track diagram does not show Rec maintenance w3c/process#596 (2 comments by @css-meeting-bot, @svgeesus)
-
Dealing with procedural disagreements within the Council w3c/process#843 (2 comments by @css-meeting-bot, @frivoal)
-
Be consistent with terms "non-normative" and "informative" w3c/process#914 (2 comments by @frivoal, @TallTed)
-
Should member submissions be removed from the Process? w3c/process#648 (1 comment by @css-meeting-bot)
-
-
3 pull requests merged.
-
Tighten the how sustantive changes are handled post AC-Review w3c/process#910.
-
Explicitly mark figures as non-normative w3c/process#911.
-
Add REC maintenance to diagram w3c/process#908.
-
-
1 pull request closed.
-
Deal with procedural disagreements within the Council w3c/process#909.
-
-
3 pull requests received 7 new comments.
-
Reference w3c-ac-forum policy which defines list access policy w3c/process#912 (5 comments by @chrisn, @frivoal)
-
Tighten the how sustantive changes are handled post AC-Review w3c/process#910 (1 comment by @TallTed)
-
Past meetings
-
1 meeting.
Participants
-
1 participant joined.
-
Emma Fraser joined.
-
-
2 participants left.
-
Qing An left.
-
Tzviya Siegman left.
-
GitHub
w3c/process
-
3 issues closed.
-
Diagram should clarify that it's possible to go from REC back to CR w3c/process#775.
-
a role should be a role, not a task w3c/process#615.
-
-
6 issues received 12 new comments.
-
Diagram should clarify that it's possible to go from REC back to CR w3c/process#775 (1 comment by @frivoal)
-
Proposed Recommendations aren't useful in the same way other maturity stages are w3c/process#861 (1 comment by @css-meeting-bot)
-
6 pull requests opened.
-
Reference w3c-ac-forum policy which defines list access policy w3c/process#912, by @tobie.
-
Explicitly mark figures as non-normative w3c/process#911, by @frivoal.
-
Tighten the how sustantive changes are handled post AC-Review w3c/process#910, by @frivoal.
-
Deal with procedural disagreements within the Council w3c/process#909, by @frivoal.
-
Add REC maintenance to diagram w3c/process#908, by @frivoal.
-
short-circuit drop Team-related votes w3c/process#906, by @tantek.
-
-
2 pull requests merged.
-
Introduce an appendix cataloging old terminology w3c/process#898.
-
Retire Proposed Recommendation w3c/process#868.
-
-
1 pull request closed.
-
Meetings of new groups are 8 weeks from charter approval w3c/process#434.
-
-
8 pull requests received 60 new comments.
-
Allow Tim Berners-Lee to abstain in Unanimous Short Circuit votes w3c/process#793 (18 comments by @dwsinger, @frivoal, @TallTed, @tantek)
-
Introduce an appendix cataloging old terminology w3c/process#898 (8 comments by @css-meeting-bot, @fantasai, @frivoal)
-
Adjust the status of Tim Berners-Lee in the TAG w3c/process#791 (8 comments by @frivoal, @TallTed, @tantek)
-
Tighten the how sustantive changes are handled post AC-Review w3c/process#910 (3 comments by @TallTed)
-
Intro: State some high-level goals related to WGs and their specs w3c/process#894 (3 comments by @TallTed)
w3c-cg/PWETF
-
1 pull request received 1 new comment.
w3c/PWETF
-
1 pull request received 1 new comment.
Advisory Board Elected Members
Participants
-
2 participants left the Advisory Board Elected Members.
-
Qing An left.
-
Tzviya Siegman left.
-
Vision Task Force
Participants
-
1 participant left the Vision Task Force.
-
Tzviya Siegman left.
-
Participants
-
1 chair appointed.
-
Chris Wilson became a chair.
-
-
1 chair stepped down.
-
Tzviya Siegman stepped down as a chair.
-
GitHub
w3c/process
-
5 issues opened.
-
Glossaries: a different pattern needed? w3c/process#904, by @cwilso.
-
Suboptimal wording about "License Grants from Non-Participants" w3c/process#903, by @frivoal.
-
Open up Registries to IG, TAG, AB w3c/process#902, by @frivoal.
-
Invited Experts without Member-only access w3c/process#900, by @jyasskin.
-
Phrasing disagreement w3c/process#899, by @frivoal.
-
-
5 issues closed.
-
Adjust AC appeal vote threshold based on participation w3c/process#886.
-
Who can initiate and prepare a Charter? w3c/process#560.
-
Phrasing disagreement w3c/process#899.
-
Making the Council's short circuit a little more flexible w3c/process#852.
-
Remove section of the Process on Workshop and Symposia w3c/process#419.
-
-
9 issues received 23 new comments.
-
Grace period for contributing to specifications? w3c/process#672 (3 comments by @dwsinger, @jyasskin, @OrKoN)
-
Enhancing the W3C REC Update Process for Greater Efficiency and Engagement w3c/process#866 (2 comments by @frivoal, @sideshowbarker)
-
Suboptimal wording about "License Grants from Non-Participants" w3c/process#903 (1 comment by @chaals)
-
2 pull requests opened.
-
Set up progressive vote threshold depending on participation w3c/process#901, by @frivoal.
-
Introduce an appendix cataloging old terminology w3c/process#898, by @frivoal.
-
-
4 pull requests merged.
-
Set up progressive vote threshold depending on participation w3c/process#901.
-
Introduce a formal Charter Refinement phase w3c/process#851.
-
Relax the criteria for short-circuit w3c/process#885.
-
Shift most discussion of Workshops to /Guide w3c/process#876.
-
-
7 pull requests received 81 new comments.
-
Retire Proposed Recommendation w3c/process#868 (34 comments by @fantasai, @frivoal, @nigelmegitt, @plehegar, @TallTed)
-
Generalizing AC Appeals and using this procedure for recall. w3c/process#888 (15 comments by @chaals, @dwsinger, @frivoal, @TallTed)
-
Introduce an appendix cataloging old terminology w3c/process#898 (15 comments by @frivoal, @TallTed)
-
Introduce a formal Charter Refinement phase w3c/process#851 (13 comments by @chrisn, @dontcallmedom, @fantasai, @frivoal, @swickr, @TallTed)
-
Set up progressive vote threshold depending on participation w3c/process#901 (2 comments by @chrisn, @TallTed)
-
w3c-cg/PWETF
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Fixing acknowledgements w3c-cg/PWETF#382, by @wareid.
-
-
1 pull request merged.
-
Fixing acknowledgements w3c-cg/PWETF#382.
-
w3c/PWETF
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Fixing acknowledgements w3c/PWETF#382, by @wareid.
-
-
1 pull request merged.
-
Fixing acknowledgements w3c/PWETF#382.
-
Advisory Board Elected Members
Participants
-
2 participants joined the Advisory Board Elected Members.
-
Elena Lape joined.
-
Max Gendler joined.
-
Past meetings
-
1 meeting.
GitHub
w3c/process
-
2 issues opened.
-
Adjust AC appeal vote threshold based on participation w3c/process#886, by @frivoal.
-
Recall procedures for TAG and AB w3c/process#882, by @mnot.
-
-
2 issues closed.
-
Use Alias rather than Redirect for /Consortium/Process w3c/process#729.
-
repo name nit: it'd be nice if this were simply w3c/process w3c/process#871.
-
-
1 issue reopened.
-
"Candidate Recommendation" is no longer an accurate term w3c/process#402, by @fantasai.
-
-
6 issues received 44 new comments.
-
"Candidate Recommendation" is no longer an accurate term w3c/process#402 (18 comments by @caribouW3, @dwsinger, @frivoal, @hober, @liamquin, @nigelmegitt, @sideshowbarker, @TallTed)
-
Use Alias rather than Redirect for /Consortium/Process w3c/process#729 (9 comments by @deniak, @frivoal, @koalie, @plehegar, @vivienlacourba)
-
repo name nit: it'd be nice if this were simply w3c/process w3c/process#871 (5 comments by @frivoal, @plehegar, @vivienlacourba)
-
Enhancing the W3C REC Update Process for Greater Efficiency and Engagement w3c/process#866 (1 comment by @dontcallmedom)
-
-
8 pull requests opened.
-
Intro: State some high-level goals related to WGs and their specs w3c/process#894, by @sideshowbarker.
-
Candidate Recommendation → Working Group Publication w3c/process#890, by @sideshowbarker.
-
Generalizing AC Appeals and using this procedure for recall. w3c/process#888, by @frivoal.
-
Add back language about substantive changes invalidating previous review w3c/process#887, by @sideshowbarker.
-
Relax the criteria for short-circuit w3c/process#885, by @frivoal.
-
Rationalize/streamline/modernize some core terminology w3c/process#883, by @sideshowbarker.
-
1 pull request merged.
-
Remove note about AC consensus assessment w3c/process#875.
-
-
2 pull requests closed.
-
Candidate Recommendation → Working Group Publication w3c/process#890.
-
2 pull requests reopened.
-
13 pull requests received 67 new comments.
-
Generalizing AC Appeals and using this procedure for recall. w3c/process#888 (23 comments by @frivoal, @TallTed)
-
Candidate Recommendation → Working Group Publication w3c/process#890 (6 comments by @cwilso, @sideshowbarker, @TallTed)
-
Add back language about substantive changes invalidating previous review w3c/process#887 (3 comments by @dwsinger, @frivoal, @sideshowbarker)
-
Note that “Candidate” means “eligible” for further-advancement consideration w3c/process#895 (2 comments by @nigelmegitt, @TallTed)
-
Rationalize/streamline/modernize some core terminology w3c/process#883 (2 comments by @frivoal, @sideshowbarker)
-
Add note reminding that the first stage of REC track is WD w3c/process#877 (2 comments by @frivoal, @TallTed)
-
Note that “Candidate” means “eligible” for further-advancement consideration w3c/process#893 (1 comment by @sideshowbarker)
-
w3c-cg/PWETF
-
1 issue opened.
-
add demonizing to unacceptable behaviors w3c-cg/PWETF#381, by @TzviyaSiegman.
-
-
2 issues received 2 new comments.
w3c/PWETF
-
1 issue opened.
-
add demonizing to unacceptable behaviors w3c/PWETF#381, by @TzviyaSiegman.
-
-
2 issues received 2 new comments.
w3c/standards-track
-
1 pull request opened.
-
Process pp links w3c/standards-track#33, by @plehegar.
-
-
1 pull request merged.
-
Process pp links w3c/standards-track#33.
-
Past meetings
-
1 meeting.
Participants
-
2 participants joined.
-
Elena Lape joined.
-
Max Gendler joined.
-
GitHub
w3c/process
-
6 issues opened.
-
Inaccurate text about Membership Agreements w3c/process#879, by @hober.
-
repo name nit: it'd be nice if this were simply w3c/process w3c/process#871, by @hober.
-
Visibility of FO handling w3c/process#870, by @frivoal.
-
FPWD and joint deliverables—the process may be missing an exclusion opportunity w3c/process#869, by @hober.
-
Enhancing the W3C REC Update Process for Greater Efficiency and Engagement w3c/process#866, by @marcoscaceres.
-
Switching tracks **and back** w3c/process#864, by @frivoal.
-
-
6 issues closed.
-
CRD may be followed by a Proposed Recommendation w3c/process#450.
-
Switching tracks **and back** w3c/process#864.
-
Chair should be required in charter w3c/process#823.
-
Process should say how W3T can update NOTES w3c/process#120.
-
Representing the W3C w3c/process#582.
-
-
16 issues received 42 new comments.
-
Making the Council's short circuit a little more flexible w3c/process#852 (7 comments by @css-meeting-bot, @dwsinger, @frivoal, @hober, @tantek)
-
Switching tracks **and back** w3c/process#864 (5 comments by @caribouW3, @css-meeting-bot, @dwsinger, @frivoal)
-
FPWD and joint deliverables—the process may be missing an exclusion opportunity w3c/process#869 (5 comments by @dwsinger, @fantasai, @frivoal, @plehegar)
-
Proposed Recommendations aren't useful in the same way other maturity stages are w3c/process#861 (5 comments by @chaals, @css-meeting-bot, @frivoal)
-
repo name nit: it'd be nice if this were simply w3c/process w3c/process#871 (4 comments by @frivoal, @plehegar)
-
Should member submissions be removed from the Process? w3c/process#648 (2 comments by @dwsinger, @frivoal)
-
Use Alias rather than Redirect for /Consortium/Process w3c/process#729 (2 comments by @frivoal, @plehegar)
-
Council Composition requirements include Tim Berners-Lee, TAG life member w3c/process#784 (1 comment by @hober)
-
Enhancing the W3C REC Update Process for Greater Efficiency and Engagement w3c/process#866 (1 comment by @marcoscaceres)
-
-
9 pull requests opened.
-
Consolidate similar parts of REC revision w3c/process#878, by @frivoal.
-
Add note reminding that the first stage of REC track is WD w3c/process#877, by @frivoal.
-
Shift most discussion of Workshops to /Guide w3c/process#876, by @frivoal.
-
Remove note about AC consensus assessment w3c/process#875, by @frivoal.
-
Require listing chair(s) in charters w3c/process#874, by @frivoal.
-
[Editorial] Rephrase what CRDs are for w3c/process#873, by @frivoal.
-
Retire Proposed Recommendation w3c/process#868, by @frivoal.
-
Consolidate similar parts of REC revision w3c/process#865, by @frivoal.
-
[Editorial] Give context for candidate amendments when revising a REC w3c/process#862, by @frivoal.
-
-
6 pull requests merged.
-
[Editorial] Rephrase what CRDs are for w3c/process#873.
-
Consolidate similar parts of REC revision w3c/process#878.
-
Add note reminding that the first stage of REC track is WD w3c/process#877.
-
Require listing chair(s) in charters w3c/process#874.
-
Consolidate maintenance by the Team of technical reports w3c/process#860.
-
-
1 pull request closed.
-
Consolidate similar parts of REC revision w3c/process#865.
-
-
11 pull requests received 45 new comments.
-
Introduce a formal Charter Refinement phase w3c/process#851 (18 comments by @chrisn, @css-meeting-bot, @frivoal, @hober, @TallTed)
-
Shift most discussion of Workshops to /Guide w3c/process#876 (7 comments by @css-meeting-bot, @fantasai, @frivoal)
-
[Editorial] Give context for candidate amendments when revising a REC w3c/process#862 (4 comments by @css-meeting-bot, @TallTed)
-
Limit the involvement of Tim Berners-Lee to the TAG proper w3c/process#792 (2 comments by @frivoal, @hober)
-
Allow Tim Berners-Lee to abstain in Unanimous Short Circuit votes w3c/process#793 (1 comment by @frivoal)
-
Consolidate maintenance by the Team of technical reports w3c/process#860 (1 comment by @css-meeting-bot)
-
w3c-cg/PWETF
-
1 issue received 1 new comment.
w3c/PWETF
-
1 issue received 1 new comment.
TR publications
-
1 document published.
-
Vision for W3C published as a Note. History of Vision for W3C
-
Past meetings
GitHub
w3c-cg/PWETF
-
1 issue opened.
-
W3C Awards: Recognizing the Community w3c-cg/PWETF#378, by @wareid.
-
-
1 pull request received 5 new comments.
w3c/PWETF
-
1 issue opened.
-
W3C Awards: Recognizing the Community w3c/PWETF#378, by @wareid.
-
-
1 pull request received 5 new comments.
w3c/process
-
8 issues opened.
-
Proposed Recommendations aren't useful in the same way other maturity stages are w3c/process#861, by @frivoal.
-
Retire the "Streamlined Publication Approval" system w3c/process#856, by @frivoal.
-
Creating a more visible banner for old process documents w3c/process#855, by @egekorkan.
-
Member Associations to Liaison Relationships w3c/process#853, by @mnot.
-
Making the Council's short circuit a little more flexible w3c/process#852, by @frivoal.
-
Align with Bylaws changes w3c/process#849, by @fantasai.
-
Multiple possible outcomes of a successful AC Appeal w3c/process#844, by @frivoal.
-
Dealing with procedural disagreements within the Council w3c/process#843, by @frivoal.
-
-
7 issues closed.
-
TAG appointment ambiguity about ratification by both AB and TAG w3c/process#836.
-
Retire the "Streamlined Publication Approval" system w3c/process#856.
-
Identify and (explain or change) W3C jargon words w3c/process#456.
-
Whistle blower w3c/process#481.
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779.
-
Addressing formal objections before requesting advancement w3c/process#737.
-
1 issue reopened.
-
Addressing formal objections before requesting advancement w3c/process#737, by @frivoal.
-
-
20 issues received 44 new comments.
-
Process should say how W3T can update NOTES w3c/process#120 (3 comments by @css-meeting-bot, @frivoal)
-
Ambiguity about (super) majority thresholds: of those voting, or of those eligible to vote? w3c/process#838 (3 comments by @css-meeting-bot, @frivoal)
-
Retire the "Streamlined Publication Approval" system w3c/process#856 (3 comments by @css-meeting-bot, @fantasai, @nigelmegitt)
-
Identify and (explain or change) W3C jargon words w3c/process#456 (3 comments by @css-meeting-bot, @fantasai, @frivoal)
-
Addressing formal objections before requesting advancement w3c/process#737 (3 comments by @frivoal, @jyasskin)
-
Have the normal, default, decision policy for charters in the process w3c/process#425 (3 comments by @frivoal, @svgeesus)
-
Should member submissions be removed from the Process? w3c/process#648 (3 comments by @frivoal, @nigelmegitt)
-
TAG appointment ambiguity about ratification by both AB and TAG w3c/process#836 (2 comments by @css-meeting-bot, @frivoal)
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779 (2 comments by @css-meeting-bot, @frivoal)
-
Creating a more visible banner for old process documents w3c/process#855 (2 comments by @frivoal, @plehegar)
-
Making the Council's short circuit a little more flexible w3c/process#852 (2 comments by @chaals, @frivoal)
-
Multiple possible outcomes of a successful AC Appeal w3c/process#844 (2 comments by @fantasai, @TallTed)
-
7 pull requests opened.
-
Consolidate maintenance by the Team of technical reports w3c/process#860, by @frivoal.
-
Link "Advisory Committee Review" in the Statement section. w3c/process#858, by @jyasskin.
-
Retire the Streamlined Publication Approval system w3c/process#857, by @frivoal.
-
Introduce a formal Charter Refinement phase w3c/process#851, by @frivoal.
-
Editorial rewrite of section on charter approval w3c/process#850, by @frivoal.
-
Clarifies Council votes w3c/process#842, by @frivoal.
-
Eliminate potential ambiguity in dismissal w3c/process#841, by @frivoal.
-
-
7 pull requests merged.
-
Disambiguate what "each" means in TAG appointment ratification w3c/process#837.
-
Eliminate potential ambiguity in dismissal w3c/process#841.
-
Clarifies Council votes w3c/process#842.
-
Retire the Streamlined Publication Approval system w3c/process#857.
-
Editorial rewrite of section on charter approval w3c/process#850.
-
Link "Advisory Committee Review" in the Statement section. w3c/process#858.
-
-
1 pull request closed.
-
Confidentiality Levels and Redactions w3c/process#722.
-
-
4 pull requests received 26 new comments.
-
Introduce a formal Charter Refinement phase w3c/process#851 (13 comments by @caribouW3, @fantasai, @frivoal, @TallTed)
-
Editorial rewrite of section on charter approval w3c/process#850 (10 comments by @css-meeting-bot, @fantasai, @frivoal, @TallTed)
-
Consolidate maintenance by the Team of technical reports w3c/process#860 (2 comments by @frivoal, @TallTed)
-
w3c/AB-public
-
4 issues opened.
-
Thorough Review should mention technical soundness w3c/AB-public#170, by @cynthia.
-
Adjusting how we use "diversity" in the vision w3c/AB-public#169, by @torgo.
-
Make it more clear that as a Statement the vision will continue to evolve w3c/AB-public#168, by @astearns.
-
Review of editorial edits w3c/AB-public#167, by @fantasai.
-
-
7 issues closed.
-
Explicitly en-vision a perfect indefinite future? w3c/AB-public#147.
-
How to publish, goals w3c/AB-public#135.
-
For all humanity? w3c/AB-public#91.
-
changing the title of W3C Vision w3c/AB-public#86.
-
Resolve issues associated with antitrust before progressing further w3c/AB-public#80.
-
Include a purpose statement in the vision? w3c/AB-public#153.
-
-
9 issues received 35 new comments.
-
Resolve issues associated with antitrust before progressing further w3c/AB-public#80 (15 comments by @cwilso, @frivoal, @jwrosewell, @wareid)
-
Include a purpose statement in the vision? w3c/AB-public#153 (9 comments by @avneeshsingh, @cwilso, @dwsinger, @fantasai, @LJWatson, @mnot)
-
Adjusting how we use "diversity" in the vision w3c/AB-public#169 (3 comments by @chaals, @cwilso, @fantasai)
-
Explicitly en-vision a perfect indefinite future? w3c/AB-public#147 (2 comments by @cwilso, @fantasai)
-
Clarify how web technology alone or with government aid can protect people from harm w3c/AB-public#15 (1 comment by @cwilso)
-
-
1 pull request opened.
-
Split diverse perspectives and inclusion points w3c/AB-public#171, by @cwilso.
-
-
1 pull request received 2 new comments.
-
Split diverse perspectives and inclusion points w3c/AB-public#171 (2 comments by @cwilso, @fantasai)
-
Past meetings
-
1 meeting.
GitHub
w3c/process
-
4 issues opened.
-
TAG appointment ambiguity about ratification by both AB and TAG w3c/process#836, by @frivoal.
-
Description of the role of the AB w3c/process#833, by @dwsinger.
-
Determining AC Consensus of Post-Review Changes w3c/process#825, by @fantasai.
-
3 issues closed.
-
Are the rules for updating Registry Definitions appropriate? w3c/process#800.
-
Run link checker on Process Drafts w3c/process#824.
-
-
11 issues received 83 new comments.
-
Chair should be required in charter w3c/process#823 (29 comments by @chaals, @chrisn, @csarven, @css-meeting-bot, @cwilso, @dwsinger, @frivoal, @nigelmegitt, @plehegar, @samuelweiler)
-
TAG appointment ambiguity about ratification by both AB and TAG w3c/process#836 (12 comments by @css-meeting-bot, @cwilso, @frivoal, @martinthomson, @TallTed, @torgo)
-
Determining AC Consensus of Post-Review Changes w3c/process#825 (8 comments by @css-meeting-bot, @dwsinger, @frivoal, @plehegar, @TallTed)
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779 (6 comments by @dwsinger, @fantasai, @frivoal, @shawna-slh, @TallTed)
-
Ambiguity about (super) majority thresholds: of those voting, or of those eligible to vote? w3c/process#838 (5 comments by @css-meeting-bot, @fantasai, @TallTed)
-
Are the rules for updating Registry Definitions appropriate? w3c/process#800 (4 comments by @css-meeting-bot, @fantasai, @frivoal, @nigelmegitt)
-
Use Alias rather than Redirect for /Consortium/Process w3c/process#729 (3 comments by @fantasai, @frivoal, @plehegar)
-
Chair appointment community involvement, transparency, enabling objections and handling them w3c/process#281 (3 comments by @chaals, @csarven, @michaelchampion)
-
Ground the different types of groups / maturity stages in Problem Statements w3c/process#813 (1 comment by @michaelchampion)
-
-
6 pull requests opened.
-
Disambiguate what "each" means in TAG appointment ratification w3c/process#837, by @frivoal.
-
Clarify confidentiality requirements w3c/process#835, by @frivoal.
-
Create SECURITY.md w3c/process#834, by @Angelaaa0609.
-
Clarify definition of the REC-track w3c/process#831, by @frivoal.
-
Update compile.yml w3c/process#830, by @DawallAZllon91.
-
NUEVA IMPLEMENTACIÓN w3c/process#829, by @DawallAZllon91.
-
-
3 pull requests merged.
-
Clarify confidentiality requirements w3c/process#835.
-
Clarify definition of the REC-track w3c/process#831.
-
Clarify what a registry is made of w3c/process#818.
-
-
3 pull requests closed.
-
Create SECURITY.md w3c/process#834.
-
Update compile.yml w3c/process#830.
-
NUEVA IMPLEMENTACIÓN w3c/process#829.
-
-
7 pull requests received 26 new comments.
-
Clarify definition of the REC-track w3c/process#831 (10 comments by @chaals, @css-meeting-bot, @dwsinger, @fantasai, @frivoal, @sideshowbarker)
-
Disambiguate what "each" means in TAG appointment ratification w3c/process#837 (6 comments by @cwilso, @fantasai, @martinthomson, @TallTed)
-
Confidentiality Levels and Redactions w3c/process#722 (4 comments by @css-meeting-bot, @frivoal, @joshco, @nigelmegitt)
-
Improve consistency of document status names that use the word "Draft" w3c/process#819 (1 comment by @TallTed)
-
w3c/AB-public
-
4 issues opened.
-
Articulate how we will learn from the harms of the web w3c/AB-public#166, by @wareid.
-
Use of "W3C" needs to conform with branding guidelines w3c/AB-public#164, by @cwilso.
-
Integrate with W3C mission statement w3c/AB-public#163, by @cwilso.
-
Careful use of the word "mission" w3c/AB-public#161, by @cwilso.
-
-
3 issues closed.
-
Use of "W3C" needs to conform with branding guidelines w3c/AB-public#164.
-
Careful use of the word "mission" w3c/AB-public#161.
-
Vision: add malvertising to explicit mentions of known web harms w3c/AB-public#71.
-
-
5 issues received 11 new comments.
-
Include a purpose statement in the vision? w3c/AB-public#153 (4 comments by @avneeshsingh, @cwilso, @dwsinger)
-
Resolve issues associated with antitrust before progressing further w3c/AB-public#80 (4 comments by @cwilso, @jwrosewell, @koalie)
-
Articulate how we will learn from the harms of the web w3c/AB-public#166 (1 comment by @michaelchampion)
-
Vision: add malvertising to explicit mentions of known web harms w3c/AB-public#71 (1 comment by @tantek)
-
-
6 pull requests opened.
-
"The W3C" -> "W3C" as appropriate w3c/AB-public#165, by @cwilso.
-
Mission editorial refactor w3c/AB-public#162, by @cwilso.
-
editorial: consistent abstract & purpose use of "articulates" w3c/AB-public#160, by @tantek.
-
editorial: list item sentences don't need periods w3c/AB-public#157, by @tantek.
-
editorial: simplify, copy edit Abstract & Purpose w3c/AB-public#156, by @tantek.
-
editorial: rm awkward dupe wording, +ed w3c/AB-public#155, by @tantek.
-
-
6 pull requests merged.
-
"The W3C" -> "W3C" as appropriate w3c/AB-public#165.
-
Mission editorial refactor w3c/AB-public#162.
-
editorial: consistent abstract & purpose use of "articulates" w3c/AB-public#160.
-
editorial: list item sentences don't need periods w3c/AB-public#157.
-
editorial: simplify, copy edit Abstract & Purpose w3c/AB-public#156.
-
editorial: rm awkward dupe wording, +ed w3c/AB-public#155.
-
-
1 pull request closed.
-
Possible update from feedback w3c/AB-public#154.
-
-
2 pull requests received 4 new comments.
w3c-cg/PWETF
-
2 issues opened.
-
Impact of CoC changes on past behaviour handling w3c-cg/PWETF#373, by @csarven.
-
If swearing is covered, it's not clear where w3c-cg/PWETF#372, by @fstrr.
-
-
1 issue received 5 new comments.
-
If swearing is covered, it's not clear where w3c-cg/PWETF#372 (5 comments by @csarven, @cwilso, @fstrr, @TzviyaSiegman, @wareid)
-
-
1 pull request merged.
-
Addressing feedback from the AC Vote w3c-cg/PWETF#371.
-
-
1 pull request received 5 new comments.
w3c/PWETF
-
2 issues opened.
-
Impact of CoC changes on past behaviour handling w3c/PWETF#373, by @csarven.
-
If swearing is covered, it's not clear where w3c/PWETF#372, by @fstrr.
-
-
1 issue received 5 new comments.
-
If swearing is covered, it's not clear where w3c/PWETF#372 (5 comments by @csarven, @cwilso, @fstrr, @TzviyaSiegman, @wareid)
-
-
1 pull request merged.
-
Addressing feedback from the AC Vote w3c/PWETF#371.
-
-
1 pull request received 5 new comments.
GitHub
w3c/process
-
2 issues opened.
-
Run link checker on Process Drafts w3c/process#824, by @plehegar.
-
Chair should be required in charter w3c/process#823, by @cwilso.
-
-
3 issues received 12 new comments.
-
Chair should be required in charter w3c/process#823 (7 comments by @cwilso, @frivoal, @nigelmegitt, @plehegar, @samuelweiler)
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779 (4 comments by @frivoal, @nigelmegitt)
-
Use Alias rather than Redirect for /Consortium/Process w3c/process#729 (1 comment by @vivienlacourba)
-
-
1 pull request received 1 new comment.
-
Allow Tim Berners-Lee to abstain in Unanimous Short Circuit votes w3c/process#793 (1 comment by @frivoal)
-
w3c-cg/PWETF
-
1 issue opened.
-
Please do not use the "CoC" acronym to refer to this document w3c-cg/PWETF#368, by @vivienlacourba.
-
-
1 issue closed.
-
Please do not use the "CoC" acronym to refer to this document w3c-cg/PWETF#368.
-
-
1 issue received 10 new comments.
-
Please do not use the "CoC" acronym to refer to this document w3c-cg/PWETF#368 (10 comments by @chrisn, @cwilso, @dbooth-boston, @koalie, @TzviyaSiegman, @vivienlacourba)
-
-
3 pull requests opened.
-
Addressing feedback from the AC Vote w3c-cg/PWETF#371, by @wareid.
-
Remove use of "CoC" acronym w3c-cg/PWETF#369, by @wareid.
-
The code of conduct is expected to be hosted under /policies/ w3c-cg/PWETF#367, by @deniak.
-
-
3 pull requests merged.
-
Remove use of "CoC" acronym w3c-cg/PWETF#369.
-
Give ids to all entries in the behavior lists w3c-cg/PWETF#366.
-
The code of conduct is expected to be hosted under /policies/ w3c-cg/PWETF#367.
-
-
4 pull requests received 18 new comments.
-
Addressing feedback from the AC Vote w3c-cg/PWETF#371 (6 comments by @hober, @mnot, @nigelmegitt, @TzviyaSiegman, @wareid)
-
The code of conduct is expected to be hosted under /policies/ w3c-cg/PWETF#367 (4 comments by @deniak, @TzviyaSiegman, @vivienlacourba)
-
Give ids to all entries in the behavior lists w3c-cg/PWETF#366 (3 comments by @frivoal, @nigelmegitt, @wareid)
-
w3c/PWETF
-
1 issue opened.
-
Please do not use the "CoC" acronym to refer to this document w3c/PWETF#368, by @vivienlacourba.
-
-
1 issue closed.
-
1 issue received 10 new comments.
-
Please do not use the "CoC" acronym to refer to this document w3c/PWETF#368 (10 comments by @chrisn, @cwilso, @dbooth-boston, @koalie, @TzviyaSiegman, @vivienlacourba)
-
-
3 pull requests opened.
-
Addressing feedback from the AC Vote w3c/PWETF#371, by @wareid.
-
Remove use of "CoC" acronym w3c/PWETF#369, by @wareid.
-
The code of conduct is expected to be hosted under /policies/ w3c/PWETF#367, by @deniak.
-
-
3 pull requests merged.
-
Remove use of "CoC" acronym w3c/PWETF#369.
-
Give ids to all entries in the behavior lists w3c/PWETF#366.
-
-
4 pull requests received 18 new comments.
-
Addressing feedback from the AC Vote w3c/PWETF#371 (6 comments by @hober, @mnot, @nigelmegitt, @TzviyaSiegman, @wareid)
-
The code of conduct is expected to be hosted under /policies/ w3c/PWETF#367 (4 comments by @deniak, @TzviyaSiegman, @vivienlacourba)
-
Give ids to all entries in the behavior lists w3c/PWETF#366 (3 comments by @frivoal, @nigelmegitt, @wareid)
-
w3c/AB-public
-
1 issue opened.
-
Include a purpose statement in the vision? w3c/AB-public#153, by @LJWatson.
-
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Possible update from feedback w3c/AB-public#154, by @cwilso.
-
-
1 pull request received 2 new comments.
Vision Task Force
Participants
-
1 chair stepped down in the Vision Task Force.
-
Tzviya Siegman stepped down as a chair.
-
-
1 participant joined the Vision Task Force.
-
Chris Wilson joined.
-
Past meetings
-
1 meeting.
GitHub
w3c/AB-public
-
2 issues opened.
-
Explicitly en-vision a perfect indefinite future? w3c/AB-public#147, by @dwsinger.
-
Figure out how to reduce risk of unlicensed text in specs w3c/AB-public#146, by @jyasskin.
-
-
11 issues closed.
-
Multiple implementations point w3c/AB-public#120.
-
"Recognize and embody principles" w3c/AB-public#119.
-
Demonstrating core principles w3c/AB-public#118.
-
Horizontal review w3c/AB-public#117.
-
Where to define *what* we do w3c/AB-public#137.
-
shared values and consensus w3c/AB-public#129.
-
Improve Vision language to avoid colloquial or complex expressions w3c/AB-public#23.
-
exemplifying unintended consequences w3c/AB-public#88.
-
Add use cases of "industries" w3c/AB-public#84.
-
Vision should have a Glossary w3c/AB-public#1.
-
1 issue reopened.
-
Multiple implementations point w3c/AB-public#120, by @cwilso.
-
-
21 issues received 32 new comments.
-
Resolve issues associated with antitrust before progressing further w3c/AB-public#80 (5 comments by @chaals, @cwilso, @jwrosewell)
-
The Vision for the Web doesn't include growing its scope w3c/AB-public#143 (4 comments by @cwilso, @dontcallmedom, @dwsinger)
-
Improve Vision language to avoid colloquial or complex expressions w3c/AB-public#23 (2 comments by @cwilso, @dennis-dingwei)
-
Figure out how to reduce risk of unlicensed text in specs w3c/AB-public#146 (2 comments by @dbaron, @frivoal)
-
Need instructions for how to file issues/PRs and participate in the Vision w3c/AB-public#68 (1 comment by @cwilso)
-
Vision: add malvertising to explicit mentions of known web harms w3c/AB-public#71 (1 comment by @cwilso)
-
interoperability across our work - architectural "integrity" w3c/AB-public#141 (1 comment by @cwilso)
-
Clarify how web technology alone or with government aid can protect people from harm w3c/AB-public#15 (1 comment by @cwilso)
-
-
5 pull requests opened.
-
Interop restructure w3c/AB-public#152, by @cwilso.
-
Consistent -> Thorough w3c/AB-public#151, by @cwilso.
-
Consensus => represent Shared values w3c/AB-public#150, by @cwilso.
-
Clarify "what we do" - fixes #137 w3c/AB-public#149, by @cwilso.
-
Rewrite attempt to resolve #118, #119, #120: Alternate to #138 w3c/AB-public#148, by @cwilso.
-
-
5 pull requests merged.
-
Interop restructure w3c/AB-public#152.
-
Rewrite attempt to resolve #118, #119, #120: Alternate to #138 w3c/AB-public#148.
-
Consistent -> Thorough w3c/AB-public#151.
-
Clarify "what we do" - fixes #137 w3c/AB-public#149.
-
Consensus => represent Shared values w3c/AB-public#150.
-
-
2 pull requests closed.
-
Clarify purpose and practice of ensuring interoperability. #120 w3c/AB-public#136.
-
Capture what we do, not just how we do it, in the Vision for W3C #119 #118 w3c/AB-public#138.
-
-
4 pull requests received 7 new comments.
-
Clarify purpose and practice of ensuring interoperability. #120 w3c/AB-public#136 (3 comments by @cwilso)
-
Capture what we do, not just how we do it, in the Vision for W3C #119 #118 w3c/AB-public#138 (2 comments by @cwilso)
-
w3c-cg/PWETF
-
1 issue opened.
-
Align and move the "I can't believe you don't know about [topic]" example w3c-cg/PWETF#365, by @dbooth-boston.
-
-
1 issue received 3 new comments.
-
Align and move the "I can't believe you don't know about [topic]" example w3c-cg/PWETF#365 (3 comments by @dbooth-boston, @Usermsn, @wareid)
-
-
2 pull requests opened.
-
Give ids to all entries in the behavior lists w3c-cg/PWETF#366, by @frivoal.
-
total revision PWE Procedures page w3c-cg/PWETF#364, by @TzviyaSiegman.
-
-
2 pull requests received 54 new comments.
-
Give ids to all entries in the behavior lists w3c-cg/PWETF#366 (47 comments by @dbooth-boston, @frivoal, @wareid)
-
w3c/PWETF
-
1 issue opened.
-
1 issue received 3 new comments.
-
Align and move the "I can't believe you don't know about [topic]" example w3c/PWETF#365 (3 comments by @dbooth-boston, @Usermsn, @wareid)
-
-
2 pull requests opened.
-
Give ids to all entries in the behavior lists w3c/PWETF#366, by @frivoal.
-
total revision PWE Procedures page w3c/PWETF#364, by @TzviyaSiegman.
-
-
2 pull requests received 54 new comments.
-
Give ids to all entries in the behavior lists w3c/PWETF#366 (47 comments by @dbooth-boston, @frivoal, @wareid)
-
w3c/process
-
2 issues opened.
-
Affiliation constraints on TAG membership w3c/process#817, by @martinthomson.
-
Strip section 6.2.2.1 “wide review” of the mailing list currently mentioned w3c/process#815, by @koalie.
-
-
1 issue closed.
-
Requirement to publish formal objections should include a timeline w3c/process#735.
-
-
8 issues received 68 new comments.
-
TAG Appointment Process Shortcomings w3c/process#809 (24 comments by @chrisn, @cwilso, @dwsinger, @frivoal, @LeaVerou, @martinthomson, @mnot)
-
Are the rules for updating Registry Definitions appropriate? w3c/process#800 (10 comments by @darobin, @dwsinger, @frivoal, @nigelmegitt)
-
word order "W3C Group Draft Note" -> "Draft W3C Group Note" w3c/process#779 (7 comments by @chrisn, @frivoal, @nigelmegitt, @TallTed)
-
Strip section 6.2.2.1 “wide review” of the mailing list currently mentioned w3c/process#815 (1 comment by @frivoal)
-
-
3 pull requests opened.
-
Improve consistency of document status names that use the word "Draft" w3c/process#819, by @frivoal.
-
Clarify what a registry is made of w3c/process#818, by @frivoal.
-
Create google.yml w3c/process#814, by @ScorpiusDraconis83.
-
-
2 pull requests merged.
-
Reduce confusion wrt registry sections #800 w3c/process#807.
-
Clarify FO publication timing #735 w3c/process#808.
-
-
1 pull request closed.
-
Create google.yml w3c/process#814.
-
-
3 pull requests received 7 new comments.
AB Liaisons to the Board of Directors
Participants
-
2 participants joined the AB Liaisons to the Board of Directors.
-
Elika Etemad joined.
-
Tantek Çelik joined.
-