Advisory Board - Activity in 2019
No matches.
GitHub
w3c/process
-
7 issues opened.
-
Revising a Recommendation: Substantive Changes or New Features. w3c/process#358, by @jeffjaffe.
-
Streamlining the Process Document w3c/process#356, by @wseltzer.
-
"Evolution of the Governing Documents" incorrect w3c/process#355, by @wseltzer.
-
What aspects of Registries should/may/should-not be published together? w3c/process#354, by @dwsinger.
-
Where are registries published? w3c/process#353, by @dwsinger.
-
Steps to advancing to Recommendation w3c/process#352, by @jeffjaffe.
-
Who publishes Technical Reports? w3c/process#351, by @jeffjaffe.
-
-
1 issue closed.
-
Merge 6.7.4 and 6.7.5 w3c/process#341.
-
-
1 issue reopened.
-
Re-envisioning the CRUD/Snapshot split w3c/process#346, by @michaelchampion.
-
-
10 issues received 70 new comments.
-
Steps to advancing to Recommendation w3c/process#352 (19 comments by @chaals, @dwsinger, @fantasai, @frivoal, @jeffjaffe, @michaelchampion, @nigelmegitt, @plehegar, @wseltzer)
-
Re-envisioning the CRUD/Snapshot split w3c/process#346 (14 comments by @caribouW3, @chaals, @css-meeting-bot, @dwsinger, @fantasai, @frivoal, @jeffjaffe, @michaelchampion, @plehegar, @wseltzer)
-
"Evolution of the Governing Documents" incorrect w3c/process#355 (13 comments by @chaals, @dwsinger, @fantasai, @frivoal, @TzviyaSiegman, @wseltzer)
-
Streamlining the Process Document w3c/process#356 (9 comments by @chaals, @dwsinger, @frivoal, @jeffjaffe, @nigelmegitt)
-
Revising a Recommendation: Substantive Changes or New Features. w3c/process#358 (3 comments by @fantasai, @frivoal, @jeffjaffe)
-
We need a process for handling registries, APIs and other 'enumerations' w3c/process#168 (1 comment by @jeffjaffe)
-
Should whether new features are allowed into RECs be distinguished? w3c/process#345 (1 comment by @dwsinger)
-
What aspects of Registries should/may/should-not be published together? w3c/process#354 (1 comment by @dwsinger)
-
-
2 pull requests opened.
-
Avoid using the word contributor to limit conflicts with the Patent Policy w3c/process#359, by @frivoal.
-
spelling fix: judgment w3c/process#357, by @wseltzer.
-
-
2 pull requests received 14 new comments.
-
Avoid using the word contributor to limit conflicts with the Patent Policy w3c/process#359 (9 comments by @chaals, @fantasai, @frivoal)
-
spelling fix: judgment w3c/process#357 (5 comments by @dwsinger, @fantasai, @nigelmegitt, @wseltzer)
-
w3c-cg/PWETF
-
2 issues opened.
-
swapped definitions w3c-cg/PWETF#78, by @TzviyaSiegman.
-
Clarify authority of people in Leadership Positions to take immediate action w3c-cg/PWETF#77, by @chaals.
-
-
8 issues closed.
-
Consider editorial restructuring of the Expected Behavior section w3c-cg/PWETF#43.
-
Consider proposed revisions to CEPC w3c-cg/PWETF#7.
-
Can this be be a living document? w3c-cg/PWETF#15.
-
Use of 'Never' statements in CEPC w3c-cg/PWETF#32.
-
Privacy and confidentiality w3c-cg/PWETF#42.
-
Use Mediator instead of Ombud w3c-cg/PWETF#53.
-
Glossary w3c-cg/PWETF#62.
-
There is no need for "Glossary" in the "Code of Conduct" w3c-cg/PWETF#40.
-
-
1 issue reopened.
-
Visibility and retention of CEPC violation assessments w3c-cg/PWETF#34, by @nigelmegitt.
-
-
13 issues received 23 new comments.
-
Visibility and retention of CEPC violation assessments w3c-cg/PWETF#34 (4 comments by @nigelmegitt, @TzviyaSiegman)
-
Clarify authority of people in Leadership Positions to take immediate action w3c-cg/PWETF#77 (2 comments by @chaals, @nigelmegitt)
-
Guidance for when it is appropriate to edit or delete a GitHub comment w3c-cg/PWETF#23 (2 comments by @nigelmegitt, @vlevantovsky)
-
Consider editorial restructuring of the Expected Behavior section w3c-cg/PWETF#43 (2 comments by @TzviyaSiegman, @vlevantovsky)
-
There is no need for "Glossary" in the "Code of Conduct" w3c-cg/PWETF#40 (1 comment by @vlevantovsky)
-
-
3 pull requests opened.
-
editorial nits w3c-cg/PWETF#76, by @TzviyaSiegman.
-
Decsribe role of chairs more w3c-cg/PWETF#75, by @chaals.
-
Remove "enforcers" w3c-cg/PWETF#74, by @chaals.
-
-
6 pull requests merged.
-
Decsribe role of chairs more w3c-cg/PWETF#75.
-
editorial nits w3c-cg/PWETF#76.
-
Start editing glossary w3c-cg/PWETF#66.
-
Remove "enforcers" w3c-cg/PWETF#74.
-
Include both visible and invisible mental illness. w3c-cg/PWETF#72.
-
add link to wikipedia local law enforcement w3c-cg/PWETF#73.
-
-
4 pull requests received 37 new comments.
-
Decsribe role of chairs more w3c-cg/PWETF#75 (22 comments by @AdaRoseCannon, @chaals, @nigelmegitt, @TzviyaSiegman, @vlevantovsky)
-
Start editing glossary w3c-cg/PWETF#66 (12 comments by @AdaRoseCannon, @BarbaraHochgesang, @brewerj, @nigelmegitt, @TzviyaSiegman, @wareid)
-
w3c/PWETF
-
2 issues opened.
-
swapped definitions w3c/PWETF#78, by @TzviyaSiegman.
-
-
8 issues closed.
-
Consider proposed revisions to CEPC w3c/PWETF#7.
-
Can this be be a living document? w3c/PWETF#15.
-
Use of 'Never' statements in CEPC w3c/PWETF#32.
-
Privacy and confidentiality w3c/PWETF#42.
-
Use Mediator instead of Ombud w3c/PWETF#53.
-
Glossary w3c/PWETF#62.
-
There is no need for "Glossary" in the "Code of Conduct" w3c/PWETF#40.
-
1 issue reopened.
-
Visibility and retention of CEPC violation assessments w3c/PWETF#34, by @nigelmegitt.
-
-
13 issues received 23 new comments.
-
Visibility and retention of CEPC violation assessments w3c/PWETF#34 (4 comments by @nigelmegitt, @TzviyaSiegman)
-
Clarify authority of people in Leadership Positions to take immediate action w3c/PWETF#77 (2 comments by @chaals, @nigelmegitt)
-
Guidance for when it is appropriate to edit or delete a GitHub comment w3c/PWETF#23 (2 comments by @nigelmegitt, @vlevantovsky)
-
Consider editorial restructuring of the Expected Behavior section w3c/PWETF#43 (2 comments by @TzviyaSiegman, @vlevantovsky)
-
-
3 pull requests opened.
-
editorial nits w3c/PWETF#76, by @TzviyaSiegman.
-
Decsribe role of chairs more w3c/PWETF#75, by @chaals.
-
Remove "enforcers" w3c/PWETF#74, by @chaals.
-
-
6 pull requests merged.
-
Decsribe role of chairs more w3c/PWETF#75.
-
editorial nits w3c/PWETF#76.
-
Start editing glossary w3c/PWETF#66.
-
Remove "enforcers" w3c/PWETF#74.
-
Include both visible and invisible mental illness. w3c/PWETF#72.
-
add link to wikipedia local law enforcement w3c/PWETF#73.
-
-
4 pull requests received 37 new comments.
-
Decsribe role of chairs more w3c/PWETF#75 (22 comments by @AdaRoseCannon, @chaals, @nigelmegitt, @TzviyaSiegman, @vlevantovsky)
-
Start editing glossary w3c/PWETF#66 (12 comments by @AdaRoseCannon, @BarbaraHochgesang, @brewerj, @nigelmegitt, @TzviyaSiegman, @wareid)
-
GitHub
w3c-cg/PWETF
-
1 issue closed.
-
Be careful when mentioning sexual violence and stalking. w3c-cg/PWETF#69.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
add link to wikipedia local law enforcement w3c-cg/PWETF#73, by @TzviyaSiegman.
-
Include both visible and invisible mental illness. w3c-cg/PWETF#72, by @AdaRoseCannon.
-
-
1 pull request merged.
-
Be sensitive in language used w3c-cg/PWETF#71.
-
-
3 pull requests received 3 new comments.
w3c/PWETF
-
1 issue closed.
-
Be careful when mentioning sexual violence and stalking. w3c/PWETF#69.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
add link to wikipedia local law enforcement w3c/PWETF#73, by @TzviyaSiegman.
-
Include both visible and invisible mental illness. w3c/PWETF#72, by @AdaRoseCannon.
-
-
1 pull request merged.
-
Be sensitive in language used w3c/PWETF#71.
-
-
3 pull requests received 3 new comments.
w3c/process
-
10 issues opened.
-
Streamlining horizontal reviews w3c/process#347, by @lknik.
-
Re-envisioning the CRUD/Snapshot split w3c/process#346, by @wseltzer.
-
Should whether new features are allowed into RECs be distinguished? w3c/process#345, by @fantasai.
-
Should W3C adopt the EverTeal modifications to the REC track? w3c/process#344, by @fantasai.
-
Should W3C adopt the separate Evergreen Track? w3c/process#343, by @fantasai.
-
Decoupling Notes and REC track w3c/process#342, by @frivoal.
-
Merge 6.7.4 and 6.7.5 w3c/process#341, by @frivoal.
-
Refactor section about Errata w3c/process#340, by @frivoal.
-
Why can AC comments on CR be ignored? w3c/process#339, by @fantasai.
-
Decisions w3c/process#338, by @jeffjaffe.
-
-
14 issues received 38 new comments.
-
Should W3C adopt the separate Evergreen Track? w3c/process#343 (7 comments by @astearns, @dwsinger, @jeffjaffe, @michaelchampion, @nigelmegitt, @TzviyaSiegman, @wseltzer)
-
Should whether new features are allowed into RECs be distinguished? w3c/process#345 (7 comments by @dwsinger, @jeffjaffe, @michaelchampion, @nigelmegitt)
-
Re-envisioning the CRUD/Snapshot split w3c/process#346 (6 comments by @AutomatedTester, @brewerj, @fantasai, @jakearchibald, @wseltzer)
-
Chair appointment community involvement, transparency, enabling objections and handling them w3c/process#281 (3 comments by @cwilso, @plehegar)
-
Please reconsider director-free formal objection handling w3c/process#331 (3 comments by @jeffjaffe, @michaelchampion, @mnot)
-
Define charter review process to require addressing comments as in CR transitions w3c/process#182 (2 comments by @samuelweiler, @wseltzer)
-
Should W3C adopt the EverTeal modifications to the REC track? w3c/process#344 (1 comment by @wseltzer)
-
-
1 pull request opened.
-
Section 6 clean up w3c/process#348, by @frivoal.
-
GitHub
w3c-cg/PWETF
-
1 issue opened.
-
In case it is of use as a referent or example for the CEPC work... w3c-cg/PWETF#70, by @koalie.
-
-
1 issue reopened.
-
Be careful when mentioning sexual violence and stalking. w3c-cg/PWETF#69, by @AdaRoseCannon.
-
-
5 issues received 10 new comments.
-
Visibility and retention of CEPC violation assessments w3c-cg/PWETF#34 (2 comments by @brewerj, @jeffjaffe)
-
Be careful when mentioning sexual violence and stalking. w3c-cg/PWETF#69 (2 comments by @AdaRoseCannon, @vlevantovsky)
-
should every F2F agenda include CEPC in short? w3c-cg/PWETF#55 (2 comments by @koalie, @nigelmegitt)
-
1 pull request opened.
-
Be sensitive in language used w3c-cg/PWETF#71, by @AdaRoseCannon.
-
-
1 pull request received 1 new comment.
w3c/PWETF
-
1 issue opened.
-
In case it is of use as a referent or example for the CEPC work... w3c/PWETF#70, by @koalie.
-
-
1 issue reopened.
-
Be careful when mentioning sexual violence and stalking. w3c/PWETF#69, by @AdaRoseCannon.
-
-
5 issues received 10 new comments.
-
Visibility and retention of CEPC violation assessments w3c/PWETF#34 (2 comments by @brewerj, @jeffjaffe)
-
Be careful when mentioning sexual violence and stalking. w3c/PWETF#69 (2 comments by @AdaRoseCannon, @vlevantovsky)
-
1 pull request opened.
-
Be sensitive in language used w3c/PWETF#71, by @AdaRoseCannon.
-
-
1 pull request received 1 new comment.
w3c/process
-
3 issues opened.
-
Link to document on formal objection processing w3c/process#337, by @samuelweiler.
-
Retitle STATUS Sections to Avoid Double Definitions w3c/process#336, by @fantasai.
-
Recording of meetings w3c/process#334, by @hober.
-
-
1 issue closed.
-
add references to "Open Stand" principles w3c/process#325.
-
-
9 issues received 52 new comments.
-
Recording of meetings w3c/process#334 (38 comments by @chaals, @chrisn, @cwilso, @dwsinger, @fantasai, @frivoal, @hober, @LJWatson, @nigelmegitt, @yoavweiss)
-
Chair appointment community involvement, transparency, enabling objections and handling them w3c/process#281 (3 comments by @mnot, @samuelweiler)
-
What does the document status "discontinued" mean? w3c/process#262 (3 comments by @css-meeting-bot, @dwsinger)
-
add references to "Open Stand" principles w3c/process#325 (2 comments by @css-meeting-bot, @dwsinger)
-
Retitle STATUS Sections to Avoid Double Definitions w3c/process#336 (2 comments by @dwsinger, @fantasai)
-
provide clearer/common wording for transitions to Obsolete/Superseded status w3c/process#141 (1 comment by @css-meeting-bot)
-
TAG and AB should be able to formally review charters w3c/process#328 (1 comment by @michaelchampion)
-
-
1 pull request opened.
-
Registries w3c/process#335, by @frivoal.
-
-
1 pull request merged.
-
2 pull requests received 11 new comments.
-
Make it clear than any decision can be objected to w3c/process#299 (8 comments by @css-meeting-bot, @dwsinger, @frivoal, @jeffjaffe, @mnot)
-
GitHub
w3c/process
-
8 issues opened.
-
Undefined: rationale for "short term(s)" for AB/TAG elections w3c/process#333, by @koalie.
-
Typo in 2.5.3 w3c/process#332, by @koalie.
-
Please reconsider director-free formal objection handling w3c/process#331, by @michaelchampion.
-
Survivability of registries w3c/process#330, by @mnot.
-
TAG and AB should be able to formally review charters w3c/process#328, by @fantasai.
-
W3C Council should be limited to one vote per member organization w3c/process#327, by @dwsinger.
-
Community and Business Groups w3c/process#326, by @mnot.
-
add references to "Open Stand" principles w3c/process#325, by @masinter.
-
-
5 issues closed.
-
Typo in 2.5.3 w3c/process#332.
-
Add note to Process about flexibility of consensus w3c/process#296.
-
Filling appointed TAG seats that have been vacated w3c/process#311.
-
-
19 issues received 54 new comments.
-
What can the Objection Decision Committee actually decide? w3c/process#279 (7 comments by @dwsinger, @fantasai, @frivoal)
-
Enumerate the requirements for wide review w3c/process#130 (6 comments by @brewerj, @LJWatson, @r12a)
-
How does W3C Council handle membership turnover? w3c/process#290 (5 comments by @dwsinger, @frivoal, @michaelchampion)
-
Filling appointed TAG seats that have been vacated w3c/process#311 (5 comments by @dwsinger, @fantasai, @frivoal, @mnot)
-
add references to "Open Stand" principles w3c/process#325 (5 comments by @dwsinger, @masinter, @michaelchampion)
-
Undefined: rationale for "short term(s)" for AB/TAG elections w3c/process#333 (2 comments by @dwsinger, @frivoal)
-
We need a process for handling registries, APIs and other 'enumerations' w3c/process#168 (2 comments by @dwsinger)
-
W3C Council should be limited to one vote per member organization w3c/process#327 (1 comment by @fantasai)
-
Consensus in the TAG Appointment Committee - Formal Objections w3c/process#314 (1 comment by @dwsinger)
-
-
3 pull requests merged.
-
Clarify superseding w3c/process#213.
-
Dont require documenting editorial changes since the previous CR w3c/process#308.
-
Add Note about the flexibility of Consensus w3c/process#323.
-
-
3 pull requests received 3 new comments.
-
Dont require documenting editorial changes since the previous CR w3c/process#308 (1 comment by @css-meeting-bot)
w3c-cg/PWETF
-
1 issue opened.
-
Be careful when mentioning sexual violence and stalking. w3c-cg/PWETF#69, by @AdaRoseCannon.
-
-
2 pull requests opened.
-
minor: remove duplicate sentence fragment w3c-cg/PWETF#68, by @tantek.
-
Add Ada to the list of Editors w3c-cg/PWETF#67, by @AdaRoseCannon.
-
-
2 pull requests merged.
-
minor: remove duplicate sentence fragment w3c-cg/PWETF#68.
-
Add Ada to the list of Editors w3c-cg/PWETF#67.
-
-
2 pull requests received 2 new comments.
w3c/PWETF
-
1 issue opened.
-
Be careful when mentioning sexual violence and stalking. w3c/PWETF#69, by @AdaRoseCannon.
-
-
2 pull requests opened.
-
minor: remove duplicate sentence fragment w3c/PWETF#68, by @tantek.
-
Add Ada to the list of Editors w3c/PWETF#67, by @AdaRoseCannon.
-
-
2 pull requests merged.
-
minor: remove duplicate sentence fragment w3c/PWETF#68.
-
Add Ada to the list of Editors w3c/PWETF#67.
-
-
2 pull requests received 2 new comments.
GitHub
w3c/process
-
13 issues opened.
-
Do we need a lighter-weight process for superseding when it's "obvious"? w3c/process#324, by @dwsinger.
-
What are the rules for where/how W3C publications are developed? w3c/process#322, by @dwsinger.
-
Evolution of documents that are linked to the process w3c/process#319, by @jeffjaffe.
-
The Team should have a role in the Process evolution w3c/process#318, by @jeffjaffe.
-
Meta: Link to branch HTML and diffs w3c/process#317, by @mnot.
-
The Elephant in the Director-free Room w3c/process#316, by @mnot.
-
TAG Appointment Committee composition w3c/process#315, by @mnot.
-
Consensus in the TAG Appointment Committee - Formal Objections w3c/process#314, by @mnot.
-
Team-Appointed TAG Chair(s) w3c/process#313, by @mnot.
-
Suspension / Removal for cause w3c/process#312, by @mnot.
-
Filling appointed TAG seats that have been vacated w3c/process#311, by @mnot.
-
TAG chair selection timing w3c/process#310, by @mnot.
-
CR change documentation requirement should be for substantive changes only w3c/process#307, by @fantasai.
-
-
8 issues closed.
-
Further automating transition requests w3c/process#260.
-
Suggesting a change to horizontal reviews in the Process w3c/process#264.
-
Are W3C hosts members of W3C? w3c/process#10.
-
Evolution of documents that are linked to the process w3c/process#319.
-
The Team should have a role in the Process evolution w3c/process#318.
-
Definition of "extraordinary" in 7.2 w3c/process#89.
-
Meta: Link to branch HTML and diffs w3c/process#317.
-
-
1 issue reopened.
-
Definition of "extraordinary" in 7.2 w3c/process#89, by @chaals.
-
-
28 issues received 86 new comments.
-
We need a process for handling registries, APIs and other 'enumerations' w3c/process#168 (12 comments by @ChristopherA, @dwsinger, @fantasai, @frivoal)
-
Suspension / Removal for cause w3c/process#312 (10 comments by @dwsinger, @frivoal, @jeffjaffe, @michaelchampion, @mnot)
-
The Elephant in the Director-free Room w3c/process#316 (8 comments by @chaals, @dbaron, @dwsinger, @jeffjaffe, @michaelchampion, @mnot)
-
Enumerate the requirements for wide review w3c/process#130 (6 comments by @dwsinger, @LJWatson, @pes10k)
-
Add note to Process about flexibility of consensus w3c/process#296 (6 comments by @dwsinger, @frivoal)
-
What can the Objection Decision Committee actually decide? w3c/process#279 (6 comments by @chaals, @dwsinger, @frivoal, @michaelchampion)
-
What are the rules for where/how W3C publications are developed? w3c/process#322 (5 comments by @dwsinger, @frivoal, @LJWatson)
-
[director-free] Should the Council be all TAG+AB, or smaller and separately elected? w3c/process#293 (3 comments by @dwsinger, @frivoal, @mnot)
-
Do we need a lighter-weight process for superseding when it's "obvious"? w3c/process#324 (2 comments by @dwsinger, @frivoal)
-
CR change documentation requirement should be for substantive changes only w3c/process#307 (2 comments by @frivoal, @LJWatson)
-
Consensus in the TAG Appointment Committee - Formal Objections w3c/process#314 (2 comments by @chaals, @mnot)
-
Does the decision to allow the Evergreen state need to be made in the Charter? w3c/process#271 (1 comment by @css-meeting-bot)
-
[evergreen] Need to be able to Rescind not-yet-REC REC-track documents w3c/process#303 (1 comment by @css-meeting-bot)
-
provide clearer/common wording for transitions to Obsolete/Superseded status w3c/process#141 (1 comment by @cwilso)
-
Chair appointment community involvement, transparency, enabling objections and handling them w3c/process#281 (1 comment by @dwsinger)
-
The process does not include any disposition for updating the Patent Policy w3c/process#305 (1 comment by @frivoal)
-
-
4 pull requests opened.
-
Add Note about the flexibility of Consensus w3c/process#323, by @frivoal.
-
Reframe adoption of pre-existing drafts per the new Patent Policy w3c/process#320, by @frivoal.
-
Define how Governing Documents other than the Process are revised w3c/process#309, by @frivoal.
-
Dont require documenting editorial changes since the previous CR w3c/process#308, by @frivoal.
-
-
4 pull requests merged.
-
Define how Governing Documents other than the Process are revised w3c/process#309.
-
Reframe adoption of pre-existing drafts per the new Patent Policy w3c/process#320.
-
Evergreen w3c/process#304.
-
Tie everblue to updated patent policy w3c/process#306.
-
-
4 pull requests received 18 new comments.
-
Define how Governing Documents other than the Process are revised w3c/process#309 (4 comments by @css-meeting-bot, @frivoal, @jeffjaffe)
-
Fix "signficicant change" to "substantive changes" for EG publication w3c/process#298 (1 comment by @frivoal)
w3c-cg/PWETF
-
2 issues opened.
-
Publication plan for Updated CEPC w3c-cg/PWETF#65, by @lianqi.
-
PWE CG Priorities w3c-cg/PWETF#64, by @judy-zhuhr.
-
-
1 issue closed.
-
Improve details of reporting sections. w3c-cg/PWETF#56.
-
-
4 issues received 13 new comments.
-
Glossary w3c-cg/PWETF#62 (10 comments by @AdaRoseCannon, @lianqi, @RachelComerford, @swickr, @vlevantovsky)
-
-
1 pull request opened.
-
Start editing glossary w3c-cg/PWETF#66, by @AdaRoseCannon.
-
-
2 pull requests merged.
-
added rapid response info to Reporting w3c-cg/PWETF#51.
-
Add detail to reporting section w3c-cg/PWETF#63.
-
w3c/PWETF
-
2 issues opened.
-
Publication plan for Updated CEPC w3c/PWETF#65, by @lianqi.
-
PWE CG Priorities w3c/PWETF#64, by @judy-zhuhr.
-
-
1 issue closed.
-
Improve details of reporting sections. w3c/PWETF#56.
-
-
4 issues received 13 new comments.
-
Glossary w3c/PWETF#62 (10 comments by @AdaRoseCannon, @lianqi, @RachelComerford, @swickr, @vlevantovsky)
-
-
1 pull request opened.
-
Start editing glossary w3c/PWETF#66, by @AdaRoseCannon.
-
-
2 pull requests merged.
-
added rapid response info to Reporting w3c/PWETF#51.
-
Add detail to reporting section w3c/PWETF#63.
-
GitHub
w3c-cg/PWETF
-
6 issues opened.
-
Glossary w3c-cg/PWETF#62, by @vlevantovsky.
-
Idea follow-up: Chairs Training w3c-cg/PWETF#60, by @jorydotcom.
-
Informational: Initial Training Resources Work w3c-cg/PWETF#59, by @jorydotcom.
-
HTML Linting w3c-cg/PWETF#58, by @AdaRoseCannon.
-
Improve details of reporting sections. w3c-cg/PWETF#56, by @AdaRoseCannon.
-
should every F2F agenda include CEPC in short? w3c-cg/PWETF#55, by @TzviyaSiegman.
-
-
3 issues closed.
-
HTML Linting w3c-cg/PWETF#58.
-
add section to "unacceptable" about reverse -isms w3c-cg/PWETF#44.
-
Immersive Web Working Group CoC w3c-cg/PWETF#17.
-
-
9 issues received 36 new comments.
-
Improve details of reporting sections. w3c-cg/PWETF#56 (10 comments by @AdaRoseCannon, @brewerj, @jeffjaffe, @nigelmegitt, @TzviyaSiegman)
-
Idea follow-up: Chairs Training w3c-cg/PWETF#60 (9 comments by @jorydotcom, @kimdhamilton, @nigelmegitt, @RachelComerford, @TzviyaSiegman)
-
Visibility and retention of CEPC violation assessments w3c-cg/PWETF#34 (5 comments by @AdaRoseCannon, @nigelmegitt)
-
should every F2F agenda include CEPC in short? w3c-cg/PWETF#55 (4 comments by @AdaRoseCannon, @jorydotcom, @RachelComerford, @TzviyaSiegman)
-
Informational: Initial Training Resources Work w3c-cg/PWETF#59 (3 comments by @jorydotcom, @TzviyaSiegman)
-
-
3 pull requests opened.
-
Add detail to reporting section w3c-cg/PWETF#63, by @AdaRoseCannon.
-
Whitespace and Linting w3c-cg/PWETF#61, by @AdaRoseCannon.
-
"unacceptable" about reverse -isms w3c-cg/PWETF#57, by @AdaRoseCannon.
-
-
6 pull requests merged.
-
Whitespace and Linting w3c-cg/PWETF#61.
-
"unacceptable" about reverse -isms w3c-cg/PWETF#57.
-
Adjustment to Patronizing language section w3c-cg/PWETF#46.
-
dealing with my review comments w3c-cg/PWETF#33.
-
note about glossary w3c-cg/PWETF#54.
-
added be inclusive/removed "nevers" w3c-cg/PWETF#49.
-
-
6 pull requests received 59 new comments.
-
"unacceptable" about reverse -isms w3c-cg/PWETF#57 (41 comments by @AdaRoseCannon, @nigelmegitt, @swickr, @TzviyaSiegman, @vlevantovsky)
-
added be inclusive/removed "nevers" w3c-cg/PWETF#49 (10 comments by @AdaRoseCannon, @nigelmegitt, @TzviyaSiegman, @vlevantovsky)
-
w3c/PWETF
-
6 issues opened.
-
Glossary w3c/PWETF#62, by @vlevantovsky.
-
Idea follow-up: Chairs Training w3c/PWETF#60, by @jorydotcom.
-
Informational: Initial Training Resources Work w3c/PWETF#59, by @jorydotcom.
-
HTML Linting w3c/PWETF#58, by @AdaRoseCannon.
-
Improve details of reporting sections. w3c/PWETF#56, by @AdaRoseCannon.
-
should every F2F agenda include CEPC in short? w3c/PWETF#55, by @TzviyaSiegman.
-
-
3 issues closed.
-
HTML Linting w3c/PWETF#58.
-
add section to "unacceptable" about reverse -isms w3c/PWETF#44.
-
Immersive Web Working Group CoC w3c/PWETF#17.
-
-
9 issues received 36 new comments.
-
Improve details of reporting sections. w3c/PWETF#56 (10 comments by @AdaRoseCannon, @brewerj, @jeffjaffe, @nigelmegitt, @TzviyaSiegman)
-
Idea follow-up: Chairs Training w3c/PWETF#60 (9 comments by @jorydotcom, @kimdhamilton, @nigelmegitt, @RachelComerford, @TzviyaSiegman)
-
Visibility and retention of CEPC violation assessments w3c/PWETF#34 (5 comments by @AdaRoseCannon, @nigelmegitt)
-
should every F2F agenda include CEPC in short? w3c/PWETF#55 (4 comments by @AdaRoseCannon, @jorydotcom, @RachelComerford, @TzviyaSiegman)
-
Informational: Initial Training Resources Work w3c/PWETF#59 (3 comments by @jorydotcom, @TzviyaSiegman)
-
-
3 pull requests opened.
-
Add detail to reporting section w3c/PWETF#63, by @AdaRoseCannon.
-
Whitespace and Linting w3c/PWETF#61, by @AdaRoseCannon.
-
"unacceptable" about reverse -isms w3c/PWETF#57, by @AdaRoseCannon.
-
-
6 pull requests merged.
-
Whitespace and Linting w3c/PWETF#61.
-
"unacceptable" about reverse -isms w3c/PWETF#57.
-
Adjustment to Patronizing language section w3c/PWETF#46.
-
dealing with my review comments w3c/PWETF#33.
-
note about glossary w3c/PWETF#54.
-
added be inclusive/removed "nevers" w3c/PWETF#49.
-
-
6 pull requests received 59 new comments.
-
"unacceptable" about reverse -isms w3c/PWETF#57 (41 comments by @AdaRoseCannon, @nigelmegitt, @swickr, @TzviyaSiegman, @vlevantovsky)
-
added be inclusive/removed "nevers" w3c/PWETF#49 (10 comments by @AdaRoseCannon, @nigelmegitt, @TzviyaSiegman, @vlevantovsky)
-
w3c/process
-
6 issues opened.
-
The process does not include any disposition for updating the Patent Policy w3c/process#305, by @frivoal.
-
[evergreen] Need to be able to Rescind not-yet-REC REC-track documents w3c/process#303, by @fantasai.
-
[evergreen] two types of wide review? w3c/process#302, by @frivoal.
-
[evergreen] Depending on not existant tooling is problematic w3c/process#301, by @frivoal.
-
[evergreen] Role of PD w3c/process#300, by @frivoal.
-
[Evergreen] Retiring an evergreen REC by rescinding vs via republishing as Note w3c/process#297, by @frivoal.
-
-
5 issues closed.
-
Define "Working Group Decision" w3c/process#249.
-
update graphics w3c/process#91.
-
[evergreen] Role of PD w3c/process#300.
-
Review the role of the Director in the process document w3c/process#173.
-
minor changes vs editorial changes w3c/process#243.
-
-
17 issues received 84 new comments.
-
Enumerate the requirements for wide review w3c/process#130 (17 comments by @aphillips, @astearns, @chaals, @cwilso, @dwsinger, @LJWatson, @nigelmegitt, @pes10k, @r12a)
-
We need a process for handling registries, APIs and other 'enumerations' w3c/process#168 (10 comments by @chaals, @ChristopherA, @dret, @dwsinger, @fantasai)
-
First meeting of a WG allowed too soon w3c/process#251 (6 comments by @dwsinger, @frivoal, @jeffjaffe, @therealglazou)
-
What does the document status "discontinued" mean? w3c/process#262 (5 comments by @dwsinger, @frivoal, @rduerr)
-
What is the difference between a PD and a WD? w3c/process#272 (4 comments by @dwsinger, @frivoal, @michaelchampion)
-
Does the process assume all WDs are on the Rec. Track? w3c/process#236 (4 comments by @dwsinger, @frivoal)
-
Chair appointment community involvement, transparency, enabling objections and handling them w3c/process#281 (3 comments by @dwsinger, @frivoal)
-
[Evergreen] Retiring an evergreen REC by rescinding vs via republishing as Note w3c/process#297 (3 comments by @dwsinger, @frivoal, @swickr)
-
The process does not include any disposition for updating the Patent Policy w3c/process#305 (2 comments by @chaals, @michaelchampion)
-
[evergreen] Need to be able to Rescind not-yet-REC REC-track documents w3c/process#303 (2 comments by @chaals, @dwsinger)
-
Review the role of the Director in the process document w3c/process#173 (2 comments by @dwsinger, @frivoal)
-
provide clearer/common wording for transitions to Obsolete/Superseded status w3c/process#141 (1 comment by @dwsinger)
-
4 pull requests opened.
-
Tie everblue to updated patent policy w3c/process#306, by @frivoal.
-
Make it clear than any decision can be objected to w3c/process#299, by @frivoal.
-
Fix "signficicant change" to "substantive changes" for EG publication w3c/process#298, by @frivoal.
-
-
2 pull requests merged.
-
Define and differentiate between Group Decisions and Chair Decisions w3c/process#270.
-
"Minor changes" w3c/process#269.
-
-
7 pull requests received 32 new comments.
-
Clarify superseding w3c/process#213 (12 comments by @dwsinger, @fantasai, @frivoal, @jeffjaffe, @nigelmegitt)
-
Remove reference to stale document w3c/process#274 (7 comments by @dwsinger, @frivoal, @jeffjaffe, @nigelmegitt)
-
Define and differentiate between Group Decisions and Chair Decisions w3c/process#270 (5 comments by @dwsinger, @frivoal)
-
Make it clear than any decision can be objected to w3c/process#299 (4 comments by @dwsinger, @frivoal)
-
Fix "signficicant change" to "substantive changes" for EG publication w3c/process#298 (1 comment by @frivoal)
-
GitHub
w3c/process
-
5 issues opened.
-
Add note to Process about flexibility of consensus w3c/process#296, by @frivoal.
-
Multiple concerns about the creation and makeup of the Council w3c/process#292, by @michaelchampion.
-
"W3C Council" may have to hear information in confidence w3c/process#291, by @chaals.
-
How does W3C Council handle membership turnover? w3c/process#290, by @fantasai.
-
-
2 issues closed.
-
Multiple concerns about the creation and makeup of the Council w3c/process#292.
-
18 issues received 115 new comments.
-
We need a process for handling registries, APIs and other 'enumerations' w3c/process#168 (31 comments by @dbaron, @dret, @dwsinger, @fantasai, @frivoal, @michaelchampion, @nigelmegitt, @swickr)
-
How does W3C Council handle membership turnover? w3c/process#290 (20 comments by @chaals, @cwilso, @dwsinger, @fantasai, @frivoal, @LJWatson, @michaelchampion, @TzviyaSiegman)
-
Enumerate the requirements for wide review w3c/process#130 (18 comments by @aphillips, @brewerj, @chaals, @dwsinger, @frivoal, @LJWatson, @michael-n-cooper, @r12a, @swickr)
-
Allow AB to choose its own chair w3c/process#223 (10 comments by @chaals, @fantasai, @frivoal, @jeffjaffe, @LJWatson, @nigelmegitt)
-
Chair appointment community involvement, transparency, enabling objections and handling them w3c/process#281 (5 comments by @dwsinger, @frivoal, @michaelchampion)
-
Add note to Process about flexibility of consensus w3c/process#296 (5 comments by @dwsinger, @michaelchampion, @wseltzer)
-
Recusal from FO handling w3c/process#278 (4 comments by @nigelmegitt, @swickr, @TzviyaSiegman, @wseltzer)
-
discipline and CEO recusal w3c/process#275 (4 comments by @avneeshsingh, @dwsinger, @michaelchampion)
-
What to do when there's no consensus in the Council w3c/process#280 (3 comments by @avneeshsingh, @fantasai, @michaelchampion)
-
new "currently vacant" rule seems to preclude resignation in advance that is coincident with an AB/TAG election w3c/process#238 (2 comments by @dwsinger, @frivoal)
-
Multiple concerns about the creation and makeup of the Council w3c/process#292 (2 comments by @dwsinger, @michaelchampion)
-
[director-free] Should the Council be all TAG+AB, or smaller and separately elected? w3c/process#293 (1 comment by @TzviyaSiegman)
-
Does the decision to allow the Evergreen state need to be made in the Charter? w3c/process#271 (1 comment by @fantasai)
-
-
2 pull requests opened.
-
fixing typo w3c/process#295, by @dret.
-
Add subsection headings to the section about REC revisions w3c/process#294, by @frivoal.
-
-
3 pull requests merged.
-
Clarify rule on "currently vacant" seats w3c/process#286.
-
fixing typo w3c/process#295.
-
Add subsection headings to the section about REC revisions w3c/process#294.
-
-
4 pull requests received 12 new comments.
w3c-cg/PWETF
-
1 issue opened.
-
Use Mediator instead of Ombud w3c-cg/PWETF#53, by @nigelmegitt.
-
-
3 issues received 10 new comments.
-
Make TPAC more welcoming w3c-cg/PWETF#48 (5 comments by @AdaRoseCannon, @koalie, @LJWatson, @TzviyaSiegman)
-
Visibility and retention of CEPC violation assessments w3c-cg/PWETF#34 (3 comments by @nigelmegitt, @TzviyaSiegman)
-
-
2 pull requests opened.
-
note about glossary w3c-cg/PWETF#54, by @TzviyaSiegman.
-
changes to "made a mistake" section w3c-cg/PWETF#52, by @TzviyaSiegman.
-
-
1 pull request merged.
-
changes to "made a mistake" section w3c-cg/PWETF#52.
-
-
5 pull requests received 23 new comments.
-
added be inclusive/removed "nevers" w3c-cg/PWETF#49 (13 comments by @nigelmegitt, @TzviyaSiegman, @vlevantovsky)
-
Adjustment to Patronizing language section w3c-cg/PWETF#46 (3 comments by @AdaRoseCannon, @TzviyaSiegman)
-
w3c/PWETF
-
1 issue opened.
-
Use Mediator instead of Ombud w3c/PWETF#53, by @nigelmegitt.
-
-
3 issues received 10 new comments.
-
Make TPAC more welcoming w3c/PWETF#48 (5 comments by @AdaRoseCannon, @koalie, @LJWatson, @TzviyaSiegman)
-
Visibility and retention of CEPC violation assessments w3c/PWETF#34 (3 comments by @nigelmegitt, @TzviyaSiegman)
-
-
2 pull requests opened.
-
note about glossary w3c/PWETF#54, by @TzviyaSiegman.
-
changes to "made a mistake" section w3c/PWETF#52, by @TzviyaSiegman.
-
-
1 pull request merged.
-
changes to "made a mistake" section w3c/PWETF#52.
-
-
5 pull requests received 23 new comments.
-
added be inclusive/removed "nevers" w3c/PWETF#49 (13 comments by @nigelmegitt, @TzviyaSiegman, @vlevantovsky)
-
Adjustment to Patronizing language section w3c/PWETF#46 (3 comments by @AdaRoseCannon, @TzviyaSiegman)
-
GitHub
w3c/process
-
12 issues opened.
-
CEO is part of the AB, and ex-officio participant in Objection Decision Committee w3c/process#284, by @chaals.
-
What to do when there's no consensus in the Council w3c/process#280, by @frivoal.
-
What can the Objection Decision Committee actually decide? w3c/process#279, by @frivoal.
-
Recusal from FO handling w3c/process#278, by @frivoal.
-
CEO recusal while handling FOs w3c/process#277, by @frivoal.
-
Generalize FO-handling w3c/process#276, by @frivoal.
-
discipline and CEO recusal w3c/process#275, by @frivoal.
-
What is the difference between a PD and a WD? w3c/process#272, by @michaelchampion.
-
Can records of appeals ever be made public? w3c/process#268, by @nigelmegitt.
-
-
7 issues closed.
-
Resignation of AB and TAG members is illdefined w3c/process#242.
-
Section 1 Introduction, general overview w3c/process#232.
-
Patent policy and TAG participation w3c/process#241.
-
WDs are incorrectly characterized in 6.2.1 w3c/process#235.
-
Can records of appeals ever be made public? w3c/process#268.
-
Undefined term: member-visible w3c/process#244.
-
-
26 issues received 180 new comments.
-
We need a process for handling registries, APIs and other 'enumerations' w3c/process#168 (42 comments by @chaals, @dret, @dwsinger, @edent, @fantasai, @frivoal, @kcoyle, @LJWatson, @michaelchampion, @nigelmegitt, @nrooney, @TzviyaSiegman)
-
Can the Evergreen state be permanent or should ERs eventually become Recs? w3c/process#273 (14 comments by @cwilso, @dwsinger, @frivoal, @jeffjaffe, @michaelchampion, @nigelmegitt, @TzviyaSiegman)
-
What can the Objection Decision Committee actually decide? w3c/process#279 (14 comments by @chaals, @dwsinger, @frivoal, @michaelchampion, @nigelmegitt)
-
minor changes vs editorial changes w3c/process#243 (13 comments by @css-meeting-bot, @dwsinger, @fantasai, @frivoal, @nigelmegitt, @wseltzer)
-
Does the decision to allow the Evergreen state need to be made in the Charter? w3c/process#271 (10 comments by @dwsinger, @jeffjaffe, @michaelchampion)
-
Process supporting "Living Standards"? w3c/process#79 (10 comments by @dret, @dwsinger, @fantasai, @jeffjaffe, @michaelchampion, @nigelmegitt, @plehegar)
-
new "currently vacant" rule seems to preclude resignation in advance that is coincident with an AB/TAG election w3c/process#238 (7 comments by @chaals, @dwsinger, @fantasai, @frivoal)
-
Patent policy and TAG participation w3c/process#241 (7 comments by @css-meeting-bot, @dwsinger, @frivoal, @wseltzer)
-
What is the difference between a PD and a WD? w3c/process#272 (6 comments by @dwsinger, @fantasai, @frivoal, @michaelchampion)
-
CEO is part of the AB, and ex-officio participant in Objection Decision Committee w3c/process#284 (5 comments by @chaals, @dwsinger, @frivoal)
-
Resignation of AB and TAG members is illdefined w3c/process#242 (5 comments by @chaals, @dwsinger, @frivoal)
-
Does the process assume all WDs are on the Rec. Track? w3c/process#236 (5 comments by @chaals, @frivoal, @michaelchampion, @nigelmegitt)
-
discipline and CEO recusal w3c/process#275 (5 comments by @chaals, @frivoal, @michaelchampion, @nigelmegitt)
-
What to do when there's no consensus in the Council w3c/process#280 (4 comments by @chaals, @dwsinger, @nigelmegitt)
-
WDs are incorrectly characterized in 6.2.1 w3c/process#235 (4 comments by @css-meeting-bot, @dwsinger, @nigelmegitt)
-
Can records of appeals ever be made public? w3c/process#268 (3 comments by @dwsinger, @frivoal, @nigelmegitt)
-
Sections 3.4 and 6.2.6 have different statements about Voting rules in a Charter w3c/process#24 (3 comments by @css-meeting-bot, @dwsinger)
-
Chair appointment community involvement, transparency, enabling objections and handling them w3c/process#281 (2 comments by @dwsinger, @TzviyaSiegman)
-
EVERGREEN: Evergreen should be a maturity state, not a separate track w3c/process#267 (2 comments by @jeffjaffe, @michaelchampion)
-
-
6 pull requests opened.
-
Clarify rule on "currently vacant" seats w3c/process#286, by @frivoal.
-
TAG and AB resignations don't involve the AC-Rep w3c/process#283, by @frivoal.
-
Remove broken reference to non existent part of the patent policy w3c/process#282, by @frivoal.
-
Remove reference to stale document w3c/process#274, by @frivoal.
-
Define and differentiate between Group Decisions and Chair Decisions w3c/process#270, by @frivoal.
-
"Minor changes" w3c/process#269, by @frivoal.
-
-
2 pull requests merged.
-
TAG and AB resignations don't involve the AC-Rep w3c/process#283.
-
Remove broken reference to non existent part of the patent policy w3c/process#282.
-
-
1 pull request closed.
-
Let the AB choose its chair(s) and make the CEO an ex officio member w3c/process#225.
-
-
2 pull requests received 4 new comments.
-
Define and differentiate between Group Decisions and Chair Decisions w3c/process#270 (3 comments by @nigelmegitt, @nrooney)
-
w3c-cg/PWETF
-
1 issue opened.
-
Contacts at F2F meetings w3c-cg/PWETF#50, by @wseltzer.
-
-
3 issues received 16 new comments.
-
Make TPAC more welcoming w3c-cg/PWETF#48 (11 comments by @chaals, @hober, @jnurthen, @LJWatson, @nigelmegitt, @torgo, @TzviyaSiegman, @wareid)
-
-
2 pull requests opened.
-
added rapid response info to Reporting w3c-cg/PWETF#51, by @TzviyaSiegman.
-
added be inclusive/removed "nevers" w3c-cg/PWETF#49, by @TzviyaSiegman.
-
w3c/PWETF
-
1 issue opened.
-
Contacts at F2F meetings w3c/PWETF#50, by @wseltzer.
-
-
3 issues received 16 new comments.
-
Make TPAC more welcoming w3c/PWETF#48 (11 comments by @chaals, @hober, @jnurthen, @LJWatson, @nigelmegitt, @torgo, @TzviyaSiegman, @wareid)
-
-
2 pull requests opened.
-
added rapid response info to Reporting w3c/PWETF#51, by @TzviyaSiegman.
-
added be inclusive/removed "nevers" w3c/PWETF#49, by @TzviyaSiegman.
-
GitHub
w3c/process
-
3 issues opened.
-
EVERGREEN: Evergreen should be a maturity state, not a separate track w3c/process#267, by @michaelchampion.
-
Suggesting a change to horizontal reviews in the Process w3c/process#264, by @xfq.
-
FYI - for your research on Evergreen Standards proposal w3c/process#263, by @jorydotcom.
-
-
10 issues received 27 new comments.
-
Enumerate the requirements for wide review w3c/process#130 (8 comments by @chaals, @frivoal, @LJWatson, @michaelchampion, @nrooney, @r12a)
-
Process supporting "Living Standards"? w3c/process#79 (7 comments by @css-meeting-bot, @dret, @evanp, @jeffjaffe, @wseltzer)
-
Suggesting a change to horizontal reviews in the Process w3c/process#264 (3 comments by @aphillips, @dwsinger, @LJWatson)
-
EVERGREEN: Evergreen should be a maturity state, not a separate track w3c/process#267 (2 comments by @dwsinger, @michaelchampion)
-
We need a process for handling registries, APIs and other 'enumerations' w3c/process#168 (1 comment by @dret)
-
Sections 3.4 and 6.2.6 have different statements about Voting rules in a Charter w3c/process#24 (1 comment by @dwsinger)
-
Substantive changes undefined for Charter, Process reviews, and things other than specifications w3c/process#28 (1 comment by @dwsinger)
-
new "currently vacant" rule seems to preclude resignation in advance that is coincident with an AB/TAG election w3c/process#238 (1 comment by @dwsinger)
-
-
1 pull request opened.
-
tpyo w3c/process#266, by @tabatkins.
-
-
1 pull request merged.
-
tpyo w3c/process#266.
-
w3c-cg/PWETF
-
8 issues opened.
-
Make TPAC more welcoming w3c-cg/PWETF#48, by @TzviyaSiegman.
-
Positive mitigation for unreported incidents w3c-cg/PWETF#47, by @evanp.
-
Remove or reword "well actually" example w3c-cg/PWETF#45, by @nigelmegitt.
-
add section to "unacceptable" about reverse -isms w3c-cg/PWETF#44, by @TzviyaSiegman.
-
Consider editorial restructuring of the Expected Behavior section w3c-cg/PWETF#43, by @vlevantovsky.
-
Privacy and confidentiality w3c-cg/PWETF#42, by @TzviyaSiegman.
-
Role of Chairs w3c-cg/PWETF#41, by @jeffjaffe.
-
There is no need for "Glossary" in the "Code of Conduct" w3c-cg/PWETF#40, by @vlevantovsky.
-
-
1 issue closed.
-
Remove or reword "well actually" example w3c-cg/PWETF#45.
-
-
3 issues received 25 new comments.
-
Remove or reword "well actually" example w3c-cg/PWETF#45 (15 comments by @AdaRoseCannon, @nigelmegitt, @RedRoxProjects, @torgo, @TzviyaSiegman, @vlevantovsky)
-
add section to "unacceptable" about reverse -isms w3c-cg/PWETF#44 (7 comments by @boazsender, @dauwhe, @torgo, @TzviyaSiegman, @vlevantovsky)
-
-
4 pull requests opened.
-
Adjustment to Patronizing language section w3c-cg/PWETF#46, by @TzviyaSiegman.
-
Tzviya siegman slides w3c-cg/PWETF#39, by @TzviyaSiegman.
-
Shutoff Jekyll w3c-cg/PWETF#38, by @BigBlueHat.
-
unacceptable behavior w3c-cg/PWETF#37, by @TzviyaSiegman.
-
-
6 pull requests merged.
-
unacceptable behavior w3c-cg/PWETF#37.
-
Added similarities and differences to Code w3c-cg/PWETF#36.
-
edited code intro and Respect statement w3c-cg/PWETF#35.
-
Added Reporting and What to do w3c-cg/PWETF#28.
-
edit typos, minor changes to intro w3c-cg/PWETF#27.
-
Tzviya siegman slides w3c-cg/PWETF#39.
-
-
1 pull request closed.
-
Shutoff Jekyll w3c-cg/PWETF#38.
-
-
8 pull requests received 54 new comments.
-
unacceptable behavior w3c-cg/PWETF#37 (38 comments by @AdaRoseCannon, @nigelmegitt, @TzviyaSiegman, @vlevantovsky, @wareid)
-
Adjustment to Patronizing language section w3c-cg/PWETF#46 (5 comments by @nigelmegitt, @TzviyaSiegman, @vlevantovsky, @wareid)
-
edited code intro and Respect statement w3c-cg/PWETF#35 (4 comments by @nigelmegitt, @TzviyaSiegman)
-
w3c/PWETF
-
8 issues opened.
-
Make TPAC more welcoming w3c/PWETF#48, by @TzviyaSiegman.
-
Positive mitigation for unreported incidents w3c/PWETF#47, by @evanp.
-
Remove or reword "well actually" example w3c/PWETF#45, by @nigelmegitt.
-
add section to "unacceptable" about reverse -isms w3c/PWETF#44, by @TzviyaSiegman.
-
Privacy and confidentiality w3c/PWETF#42, by @TzviyaSiegman.
-
Role of Chairs w3c/PWETF#41, by @jeffjaffe.
-
There is no need for "Glossary" in the "Code of Conduct" w3c/PWETF#40, by @vlevantovsky.
-
-
1 issue closed.
-
Remove or reword "well actually" example w3c/PWETF#45.
-
-
3 issues received 25 new comments.
-
Remove or reword "well actually" example w3c/PWETF#45 (15 comments by @AdaRoseCannon, @nigelmegitt, @RedRoxProjects, @torgo, @TzviyaSiegman, @vlevantovsky)
-
add section to "unacceptable" about reverse -isms w3c/PWETF#44 (7 comments by @boazsender, @dauwhe, @torgo, @TzviyaSiegman, @vlevantovsky)
-
-
4 pull requests opened.
-
Adjustment to Patronizing language section w3c/PWETF#46, by @TzviyaSiegman.
-
Tzviya siegman slides w3c/PWETF#39, by @TzviyaSiegman.
-
Shutoff Jekyll w3c/PWETF#38, by @BigBlueHat.
-
unacceptable behavior w3c/PWETF#37, by @TzviyaSiegman.
-
-
6 pull requests merged.
-
unacceptable behavior w3c/PWETF#37.
-
Added similarities and differences to Code w3c/PWETF#36.
-
edited code intro and Respect statement w3c/PWETF#35.
-
Added Reporting and What to do w3c/PWETF#28.
-
edit typos, minor changes to intro w3c/PWETF#27.
-
Tzviya siegman slides w3c/PWETF#39.
-
-
1 pull request closed.
-
Shutoff Jekyll w3c/PWETF#38.
-
-
8 pull requests received 54 new comments.
-
unacceptable behavior w3c/PWETF#37 (38 comments by @AdaRoseCannon, @nigelmegitt, @TzviyaSiegman, @vlevantovsky, @wareid)
-
Adjustment to Patronizing language section w3c/PWETF#46 (5 comments by @nigelmegitt, @TzviyaSiegman, @vlevantovsky, @wareid)
-
GitHub
w3c-cg/PWETF
-
2 issues opened.
-
Visibility and retention of CEPC violation assessments w3c-cg/PWETF#34, by @nigelmegitt.
-
Use of 'Never' statements in CEPC w3c-cg/PWETF#32, by @RachelComerford.
-
-
1 issue closed.
-
Incorporate Procedures into CEPC? w3c-cg/PWETF#29.
-
-
6 issues received 12 new comments.
-
5 pull requests opened.
-
Added similarities and differences to Code w3c-cg/PWETF#36, by @TzviyaSiegman.
-
edited code intro and Respect statement w3c-cg/PWETF#35, by @TzviyaSiegman.
-
dealing with my review comments w3c-cg/PWETF#33, by @chaals.
-
Cite the operative CEPC w3c-cg/PWETF#31, by @swickr.
-
initial commit PWE homepage w3c-cg/PWETF#30, by @TzviyaSiegman.
-
-
2 pull requests merged.
-
initial commit PWE homepage w3c-cg/PWETF#30.
-
Cite the operative CEPC w3c-cg/PWETF#31.
-
-
4 pull requests received 25 new comments.
-
Added Reporting and What to do w3c-cg/PWETF#28 (15 comments by @AdaRoseCannon, @nigelmegitt, @RachelComerford, @TzviyaSiegman, @vlevantovsky)
-
w3c/PWETF
-
2 issues opened.
-
Visibility and retention of CEPC violation assessments w3c/PWETF#34, by @nigelmegitt.
-
Use of 'Never' statements in CEPC w3c/PWETF#32, by @RachelComerford.
-
-
1 issue closed.
-
Incorporate Procedures into CEPC? w3c/PWETF#29.
-
-
6 issues received 12 new comments.
-
5 pull requests opened.
-
Added similarities and differences to Code w3c/PWETF#36, by @TzviyaSiegman.
-
edited code intro and Respect statement w3c/PWETF#35, by @TzviyaSiegman.
-
dealing with my review comments w3c/PWETF#33, by @chaals.
-
Cite the operative CEPC w3c/PWETF#31, by @swickr.
-
initial commit PWE homepage w3c/PWETF#30, by @TzviyaSiegman.
-
-
2 pull requests merged.
-
initial commit PWE homepage w3c/PWETF#30.
-
Cite the operative CEPC w3c/PWETF#31.
-
-
4 pull requests received 25 new comments.
-
Added Reporting and What to do w3c/PWETF#28 (15 comments by @AdaRoseCannon, @nigelmegitt, @RachelComerford, @TzviyaSiegman, @vlevantovsky)
-
w3c/process
-
3 issues opened.
-
What does the document status "discontinued" mean? w3c/process#262, by @rduerr.
-
Further automating transition requests w3c/process#260, by @frivoal.
-
Editorial change to "after ac review" section w3c/process#259, by @koalie.
-
-
5 issues closed.
-
Does the “Team Submission“ mechanism still serve a purpose? w3c/process#246.
-
Change informal uses uses of the word "dissent" w3c/process#239.
-
Incorrect use of the specialized term "publish" w3c/process#245.
-
Editorial change to "after ac review" section w3c/process#259.
-
Unneeded sentence fragment w3c/process#250.
-
-
15 issues received 81 new comments.
-
Process supporting "Living Standards"? w3c/process#79 (30 comments by @cwilso, @dwsinger, @frivoal, @jeffjaffe, @michaelchampion, @nigelmegitt, @plehegar, @swickr, @wseltzer)
-
minor changes vs editorial changes w3c/process#243 (10 comments by @chaals, @dwsinger, @frivoal, @nigelmegitt)
-
Does the “Team Submission“ mechanism still serve a purpose? w3c/process#246 (7 comments by @caribouW3, @dwsinger, @frivoal, @jeffjaffe, @nigelmegitt, @plehegar)
-
First meeting of a WG allowed too soon w3c/process#251 (7 comments by @chaals, @dwsinger, @frivoal, @plehegar, @therealglazou)
-
What does the document status "discontinued" mean? w3c/process#262 (5 comments by @chaals, @frivoal, @rduerr, @swickr)
-
Further automating transition requests w3c/process#260 (5 comments by @frivoal, @nigelmegitt, @plehegar)
-
We need a process for handling registries, APIs and other 'enumerations' w3c/process#168 (3 comments by @dret, @dwsinger)
-
Enumerate the requirements for wide review w3c/process#130 (3 comments by @dwsinger, @frivoal, @LJWatson)
-
-
1 pull request opened.
-
Remove Team Submissions w3c/process#261, by @frivoal.
-
-
3 pull requests merged.
-
Retire the “Team Submission” Mechanism w3c/process#255.
-
Rephrase incorrect uses of the specialized term “publish” w3c/process#257.
-
-
1 pull request closed.
-
Remove Team Submissions w3c/process#261.
-
-
3 pull requests received 12 new comments.
-
[director-free] Gratuitous mentions of the Director w3c/process#254 (6 comments by @cwilso, @dwsinger, @frivoal, @jeffjaffe)
-
Retire the “Team Submission” Mechanism w3c/process#255 (5 comments by @dwsinger, @frivoal, @michaelchampion)
-
GitHub
w3c/process
-
12 issues opened.
-
Affiliations (and links) of editors w3c/process#253, by @koalie.
-
First meeting of a WG allowed too soon w3c/process#251, by @frivoal.
-
Unneeded sentence fragment w3c/process#250, by @frivoal.
-
Define "Working Group Decision" w3c/process#249, by @chaals.
-
Does the “Team Submission“ mechanism still serve a purpose? w3c/process#246, by @frivoal.
-
Incorrect use of the specialized term "publish" w3c/process#245, by @frivoal.
-
Undefined term: member-visible w3c/process#244, by @frivoal.
-
minor changes vs editorial changes w3c/process#243, by @frivoal.
-
Resignation of AB and TAG members is illdefined w3c/process#242, by @frivoal.
-
Patent policy and TAG participation w3c/process#241, by @frivoal.
-
Change informal uses uses of the word "dissent" w3c/process#239, by @frivoal.
-
-
2 issues closed.
-
Affiliations (and links) of editors w3c/process#253.
-
Acronyms & Terms Section w3c/process#198.
-
-
16 issues received 70 new comments.
-
minor changes vs editorial changes w3c/process#243 (13 comments by @chaals, @dwsinger, @frivoal, @michaelchampion, @wseltzer)
-
WDs are incorrectly characterized in 6.2.1 w3c/process#235 (10 comments by @chaals, @dwsinger, @frivoal, @nigelmegitt)
-
Allow AB to choose its own chair w3c/process#223 (9 comments by @chaals, @cwilso, @fantasai, @michaelchampion)
-
Does the “Team Submission“ mechanism still serve a purpose? w3c/process#246 (7 comments by @chaals, @dwsinger, @frivoal, @michaelchampion, @nigelmegitt)
-
Patent policy and TAG participation w3c/process#241 (6 comments by @chaals, @dwsinger, @frivoal, @michaelchampion)
-
Change informal uses uses of the word "dissent" w3c/process#239 (6 comments by @chaals, @frivoal, @nigelmegitt)
-
Affiliations (and links) of editors w3c/process#253 (5 comments by @chaals, @frivoal, @ianbjacobs, @nrooney)
-
new "currently vacant" rule seems to preclude resignation in advance that is coincident with an AB/TAG election w3c/process#238 (3 comments by @dbaron, @dwsinger, @frivoal)
-
-
8 pull requests opened.
-
Rephrase incorrect uses of the specialized term “publish” w3c/process#257, by @frivoal.
-
Avoid uses of the word “dissent” that clash with its formal definition w3c/process#256, by @frivoal.
-
Retire the “Team Submission” Mechanism w3c/process#255, by @frivoal.
-
[director-free] Gratuitous mentions of the Director w3c/process#254, by @frivoal.
-
Fix incorrect punctuation w3c/process#252, by @frivoal.
-
Drop redundant word w3c/process#248, by @frivoal.
-
Remove extraneous phrasing w3c/process#247, by @frivoal.
-
[editorial] Grammar fix: add missing auxiliary w3c/process#240, by @frivoal.
-
-
5 pull requests merged.
-
Remove extraneous phrasing w3c/process#247.
-
[editorial] Grammar fix: add missing auxiliary w3c/process#240.
-
Fix incorrect punctuation w3c/process#252.
-
Drop redundant word w3c/process#248.
-
Spelling fixes and one typo fix. w3c/process#237.
-
-
2 pull requests closed.
-
Require a return for additional work for substantive changes w3c/process#218.
-
Defines substantive and editorial changes for charters w3c/process#217.
-
-
9 pull requests received 17 new comments.
-
Let the AB choose its chair(s) and make the CEO an ex officio member w3c/process#225 (1 comment by @frivoal)
-
Require a return for additional work for substantive changes w3c/process#218 (1 comment by @frivoal)
w3c-cg/PWETF
-
1 issue opened.
-
Incorporate Procedures into CEPC? w3c-cg/PWETF#29, by @TzviyaSiegman.
-
-
1 issue closed.
-
Replicate the text of the current CEPC w3c-cg/PWETF#14.
-
-
4 issues received 7 new comments.
-
2 pull requests opened.
-
Added Reporting and What to do w3c-cg/PWETF#28, by @TzviyaSiegman.
-
edit typos, minor changes to intro w3c-cg/PWETF#27, by @TzviyaSiegman.
-
-
2 pull requests received 6 new comments.
-
Added Reporting and What to do w3c-cg/PWETF#28 (3 comments by @chaals, @TzviyaSiegman, @vlevantovsky)
w3c/PWETF
-
1 issue opened.
-
Incorporate Procedures into CEPC? w3c/PWETF#29, by @TzviyaSiegman.
-
-
1 issue closed.
-
Replicate the text of the current CEPC w3c/PWETF#14.
-
-
4 issues received 7 new comments.
-
2 pull requests opened.
-
Added Reporting and What to do w3c/PWETF#28, by @TzviyaSiegman.
-
edit typos, minor changes to intro w3c/PWETF#27, by @TzviyaSiegman.
-
-
2 pull requests received 6 new comments.
GitHub
w3c/process
-
1 issue opened.
-
Does the process assume all WDs are on the Rec. Track? w3c/process#236, by @nigelmegitt.
-
-
2 issues received 10 new comments.
-
WDs are incorrectly characterized in 6.2.1 w3c/process#235 (9 comments by @chaals, @dwsinger, @nigelmegitt)
-
-
1 pull request opened.
-
Spelling fixes and one typo fix. w3c/process#237, by @dbaron.
-
w3c-cg/PWETF
-
2 issues opened.
-
increase globalization w3c-cg/PWETF#26, by @TzviyaSiegman.
-
Guidance for when it is appropriate to edit or delete a GitHub comment w3c-cg/PWETF#23, by @nigelmegitt.
-
-
1 issue closed.
-
[CEPC] Add text discouraging the use of violent imagery w3c-cg/PWETF#21.
-
-
4 issues received 10 new comments.
-
Guidance for when it is appropriate to edit or delete a GitHub comment w3c-cg/PWETF#23 (6 comments by @dauwhe, @nigelmegitt, @vlevantovsky)
-
[CEPC] Add text discouraging the use of violent imagery w3c-cg/PWETF#21 (1 comment by @TzviyaSiegman)
-
-
2 pull requests opened.
-
DO NOT MERGE! Make a change to test PR preview w3c-cg/PWETF#25, by @nigelmegitt.
-
Enables PR Preview. w3c-cg/PWETF#24, by @nigelmegitt.
-
-
2 pull requests merged.
-
resolve ReSpec dfn, link and heading issues w3c-cg/PWETF#22.
-
Enables PR Preview. w3c-cg/PWETF#24.
-
-
1 pull request closed.
-
DO NOT MERGE! Make a change to test PR preview w3c-cg/PWETF#25.
-
-
1 pull request received 1 new comment.
w3c/PWETF
-
2 issues opened.
-
increase globalization w3c/PWETF#26, by @TzviyaSiegman.
-
-
1 issue closed.
-
[CEPC] Add text discouraging the use of violent imagery w3c/PWETF#21.
-
-
4 issues received 10 new comments.
-
Guidance for when it is appropriate to edit or delete a GitHub comment w3c/PWETF#23 (6 comments by @dauwhe, @nigelmegitt, @vlevantovsky)
-
-
2 pull requests opened.
-
DO NOT MERGE! Make a change to test PR preview w3c/PWETF#25, by @nigelmegitt.
-
Enables PR Preview. w3c/PWETF#24, by @nigelmegitt.
-
-
2 pull requests merged.
-
resolve ReSpec dfn, link and heading issues w3c/PWETF#22.
-
Enables PR Preview. w3c/PWETF#24.
-
-
1 pull request closed.
-
DO NOT MERGE! Make a change to test PR preview w3c/PWETF#25.
-
-
1 pull request received 1 new comment.