13:34:50 RRSAgent has joined #pwe 13:34:54 logging to https://www.w3.org/2023/05/23-pwe-irc 13:35:26 Zakim has joined #pwe 13:35:36 Meeting: PWE 13:35:43 Date: 2023-05-23 13:35:49 Chair: Tzviya, Wendy 13:57:24 dbooth has joined #pwe 13:57:34 rrsagent, make logs public 13:57:55 zakim, start meeting 13:57:55 RRSAgent, make logs Public 13:57:57 Meeting: Positive Work Environment CG 13:58:01 present+ 14:00:31 wendyreid has joined #pwe 14:00:47 present+ 14:02:52 present+ 14:02:57 regrets+ Jemma 14:03:07 present+ 14:03:12 sheila has joined #pwe 14:03:24 Scribe: David Booth 14:03:30 Topic: About the group 14:04:15 tzviya: We're not a regular WG. Need to put safety of under-rep groups over comfort of others. Need to ask if you can live with what's in this doc. 14:04:24 appreciate this sentiment, thanks 14:04:52 present+ 14:04:58 Topic: Ombud proposal 14:05:01 agenda: https://lists.w3.org/Archives/Public/public-pwe/2023May/0004.html 14:05:26 tz: I sent the budget to the finance committee. 14:06:03 ... We set up interview doc. heila and Judy Brewer put together the interview process -- selection of W3C people and Team. Need to decide who. 14:06:15 ... Suggest Sheila work on that. 14:06:30 ... Ralph, team suggestions? Perhaps someone from the board? 14:06:59 ralph: We'lll have to talk. 14:07:35 q? 14:07:36 tz: Need to put out the call for interviews -- 4 ombuds, one from each region. Want both qualifications and diversity. 14:07:40 happy to help 14:08:28 tz: Board peronnel committee is busy working on CEO selection. 14:08:50 Topic: CoC schedule and planning 14:09:16 wendy: We added a section to the doc that outlines our yearly revision process. 14:09:25 ... From March onward we enter a reviion cycle. 14:09:55 ... Goal is by the end of June to have everything in a good state to send for review by AB and AC. 14:10:17 ... Goal this year is to get that in by July so that a new version w be ready by TPAC. 14:10:37 i|Topic:|-> https://www.w3.org/2023/04/25-pwe-minutes.html previous 25 April 14:10:57 ... We're on track. This is the first time we're doing a proper revision. Want to close PRs we have, wrap up issues and get it off for review. 14:11:09 q+ for quick clarifying question 14:11:27 ... Mid-june w trigger review within the group too. 14:12:15 tz: Last time we did this it was a total rewrite, and a heavy lift for the AB to review. 14:12:24 ... This time I think they're watching more. 14:12:51 ... We'll ee what the AC says. Didn't get much comment from them last time. 14:13:13 ... Depending on Process 2023 we may or may not need Director approval. 14:13:24 ack Ralph 14:14:08 ralph: You expect to send this to AB for review and comments? And then send to AC? What's the next level of detail about the sched? 14:14:27 ... How many weeks after this group's approval? 14:14:45 ... Previsouly there was confusion and debate about what was needed. 14:15:05 tz: i'll check. We can ask the AB to start reviewing it now. 14:15:12 ack sheila 14:15:12 sheila, you wanted to discuss quick clarifying question 14:15:38 q+ 14:15:46 sheila: Florian asked me: Thy're updating the Prcess doc. Would it be appropriate to change it to CoC preemptively? 14:16:00 ... I think i'ts harmless to do. 14:16:05 +1 to preemptively changing 14:16:09 ack cw 14:16:12 wendy: Fine to me. 14:16:54 chris: No requirements on how long for AB to review. Not positive we want to do a forward naming, becaues it would be weird to change to point to a doc that doesn't exist yet. 14:17:01 sheila: The link would still work. 14:17:20 -> https://www.w3.org/Consortium/Process/Drafts/#GAProcess 11. Process Evolution 14:17:41 ralph: I concur w CHris, there's no particular duration of review required, but eh AB formally owns this doc, so it's uup to them to decide hoow long they want to review it. 14:18:09 ... .on naming, I strongly discourage asking the AB to change thename before it's formally changed. 14:18:26 ... Important for our constitution to be self-consistent. 14:19:01 ack Ralph 14:19:01 Ralph, you wanted to comment on naming 14:19:03 makes sense, thanks 14:19:05 ... i also suggest to Florian that an editorial note could be added indicating that the name may change. 14:19:08 q? 14:20:29 tz: AC gets 28 days to review 14:21:09 wendy: If we can go tto AB mid july and AC beginning of Aug. Or more like beginning of July for AB. 14:21:17 s/no particular duration of review required, but eh AB/no particular duration of AB review required, but the AB 14:22:09 s/asking the AB to change thename before it's formally changed/asking the AB to change the reference in Process before CoC is formally published 14:22:22 https://github.com/w3c/PWETF/pulls?q=is%3Apr+is%3Aopen+label%3A%22CEPC+2023%22 14:22:51 Topic: Editing the Abstract PR 292 14:23:16 I have made the request to generate https://www.w3.org/2023/05/23-pwe-minutes.html Ralph 14:23:34 https://github.com/w3c/PWETF/pull/292 14:23:57 tzviya: Not much comment, except one from DBooth. 14:24:03 q+ 14:24:10 ack dbooth 14:24:13 scribe+ 14:24:17 ack dbooth 14:24:40 dbooth: I've heard a lot of sensitivity in the past around people interpreting the list of behaviours as exhaustive and therefore if something they did wasn't there, it was fine 14:24:52 q+ 14:24:55 ack sheila 14:24:57 ... my goal was making it clear that the list was not exhaustive, but an example of behaviours 14:25:34 sheila: Suggest "exmples of" instead of "some", though personally don't feel it's necessary. 14:25:51 +1 to sheila's suggestion 14:26:04 ack ra 14:26:14 tzviya: we're trying to be comprehensive, but ... 14:26:54 +1 14:26:59 ralph: Brevity in abstracts is good. Second sentence say it does not cover every case. I don't thinkn "some" is necessary. 14:27:06 "This list of unacceptable behaviors does not cover every case. " 14:27:17 ^^ 3.2 Unacceptable Behavior 14:27:22 AGREED: Merge without adding "some" 14:27:49 https://github.com/w3c/PWETF/pull/291 14:28:05 Topic: Number bullet points in the Code section #259 14:28:30 -> https://pr-preview.s3.amazonaws.com/w3c/PWETF/291/da79c51...39c72c5.html Pull 291 preview 14:28:55 wendy: Numbering would aid in referencing. 14:28:59 +1 to this change 14:29:20 +1 14:29:26 tzviya: Some might be concerned that the numbers would indicate ranking. 14:29:32 0 14:29:42 ... We could say that these are not ranked. 14:29:52 0 14:30:10 wendy: I like it better 14:30:13 +1 as this makes it easier to refer to 14:30:51 AGREED: Add numbers -- merge the PR 14:31:27 https://github.com/w3c/PWETF/pull/290 14:31:33 Topic: safety v comfort #290 14:32:00 wendy: Need feedback. This section is hard to edit. 14:32:28 tzviya: Chris suggested "Criticim of..." I like that. 14:32:42 q? 14:32:44 q+ 14:32:50 ack dbooth 14:32:58 dbooth: I like the direction of cwilso's comment 14:33:14 ... I did previously suggest something along those lines, I imagine others will read those comments 14:33:36 1+ 14:33:38 q+ 14:33:46 ack cw 14:34:38 chris: When I read David's comment, unclear how "not tolerating" I liked. That's why I put it at the end of the prev one. More related to criticim than ranking -- less prioritized on purpose for that reason. 14:35:08 ack ra 14:36:01 ralph: We've strugged w this secion. Chris's addition helps. Tweak I suggest if it remains the last bullet, is to add the word "also". Or "likewise" is okay. 14:36:12 q+ 14:36:19 ack dbooth 14:36:22 ack dbooth 14:36:26 "We also will not tolerate ..." 14:36:50 dbooth: That part doesn't work for me. Not tolerating reverse-isms doesn't make sense in what we are trying to convey here 14:37:26 +1 to "tolerating claims of reverse-isms" 14:37:27 q+ 14:37:28 ... we won't tolerate claims of reverse-isms 14:37:34 ack cwilso 14:37:52 tzviya: Could say "we will not tolerate claims of reversisms because they do not exist" 14:38:06 chris: It's both> We won't tolerate claims not reversisms. 14:38:09 q+ 14:38:12 ack Ralph 14:38:13 ... Neither are ok. 14:38:43 ack sheila 14:38:45 ralph: The intro says 'we will prioritize ..." so the last bullet needs to be consistent, so I think David's onto something. 14:39:02 regrets+ Jen 14:39:55 sheila: I agree. Makingn fun of someone's skin is not okay, but this is about about claims of reverse-isms, so that wouldn't be relevant in this section. 14:40:03 +1 to sheila's comment 14:40:07 "Criticisms of racist, sexist, cissexist , or otherwise oppressive behavior or assumptions. We will also not tolerate claims of "Reverse" -isms, including "reverse racism," "reverse sexism ," and "cisphobia"." 14:40:22 +1 14:40:27 q+ 14:40:31 q+ 14:40:32 ack dbooth 14:40:32 ack dbooth 14:40:48 dbooth: I'd like to propose the wording I proposed in the comment 14:42:07 dbooth; i thiink it would be good to say in the code that it's okay to critizize sexist etc behavior 14:42:47 q+ 14:42:59 ack sheila 14:43:12 tzviya: There are too many other things that are permissible. 14:43:26 sheila: I do agree with the language, but do have an issue with putting them together without some sort of connection 14:43:44 ... to me that reads like we're saying they behaviours are comparable 14:43:52 sheila: Confusing to put these sentences together. Sounds like we are drawing a comparisong that doesn't exist. 14:44:51 q+ 14:45:08 tzviya: I like "likewise" 14:45:16 ack dbooth 14:45:16 wendy: "similrly"? 14:45:20 ack db 14:45:47 dbooth: Partly because I'm trying to scribe, I feel that this may need some more thought. I don't think it's productive to try and do it in real time 14:46:00 ... I would suggest we accept this PR, then we tweak it afterwards 14:46:06 ... I want us to move forward 14:46:39 "similarly" and "claims of" are the only two changes 14:46:41 wendy: Suggest we change "similarly" in the PR but not merge yet. 14:47:04 +1 14:47:33 https://github.com/w3c/PWETF/pull/241 14:48:06 dbooth: I feel like we addressed it already, and I'm fine with closing this. 14:48:22 ... I should note, I went through the meeting notes, found discussion but not decision 14:48:26 dbooth: I think we addressed this already and can close. 14:49:08 AGREED: Close 14:49:08 https://github.com/w3c/PWETF/issues?q=is%3Aissue+is%3Aopen+label%3A%22CEPC+2023%22 14:49:08 https://github.com/w3c/PWETF/issues/265 14:49:31 Topic; Redundancy in the "patronizing" section #265 14:50:16 wendy: We could merge the first two bullets, or reword them. 14:50:33 q+ 14:50:36 +1 to overlap being appropriate 14:50:52 ack db 14:51:11 dbooth: They're not entirely redundant, but there is some redundancy 14:51:19 ... I did have a proposed rewording 14:51:34 q+ 14:51:53 wendy: I like these rewordings. 14:52:07 ack sheila 14:52:35 q+ 14:52:57 sheila: The suggested language here adds unnecessary caveats -- -overyly specific, eg "unusually uninformed". IDK why it would be specifically "demographic" groups. 14:53:34 ... There can be overlap between items. Okay to have some redundancy. 14:54:00 q+ go suggest s/demographic// 14:54:27 sheila: Don't see it as a necesary change. Would rather have more reinvforcement than less. 14:54:27 ack me 14:55:12 tzviya: A few important points get tking out by this suggestion, eg "intentionally or untintenionally". This i one of the most frequently violated sections. 14:55:12 ack dbooth 14:55:40 dbooth: Totally fine with removing the word demographic, and adding intentionally/unintentionally 14:55:43 q+ 14:56:12 ack sheila 14:56:18 tzviya: Rewording is assuming, not just implying. 14:56:58 sheila; What problem are you trying to resolve w this proposed change? 14:57:14 s/Rewording is assuming/Rewording removes assuming 14:57:16 dbooth: I don't think there's harm, its just to improve the readability 14:57:27 ... they are both about making assumptions about the skills of others 14:57:35 ... I don't think we need two bullets on that topic 14:57:42 ... one bullet is sufficient 14:57:54 ... there's other aspects in the bullets, which should be kept 14:58:23 tzviya: There's nuance between these. 14:59:34 I feel strongly that we should maintain the existing language, as these are nuanced and important points that warrant individual mention 15:00:24 tzviya: Continue this discussion next time. 15:00:44 I'm not wedded to my proposed verbiage. Just try to improve the wording. 15:00:53 ADJOURNED 15:00:57 zakim, end meeting 15:00:57 As of this point the attendees have been dbooth, wendyreid, tzviya, Ralph, cwilso 15:00:58 rrsagent, draft minutes 15:01:00 I have made the request to generate https://www.w3.org/2023/05/23-pwe-minutes.html dbooth 15:01:06 RRSAgent, please draft minutes v2 15:01:07 I have made the request to generate https://www.w3.org/2023/05/23-pwe-minutes.html Zakim 15:01:12 I am happy to have been of service, wendyreid; please remember to excuse RRSAgent. Goodbye 15:01:12 Zakim has left #pwe 15:16:35 s/tz:/tzviya:/g 15:16:55 rrsagent, draft minutes 15:16:56 I have made the request to generate https://www.w3.org/2023/05/23-pwe-minutes.html dbooth 15:20:58 P.S. Thanks @tzviya for the tab-completion tip! FYI, I also corrected the other abbreviations of your name using s/tz:/tzviya:/g 15:21:24 rrsagent, draft minutes 15:21:26 I have made the request to generate https://www.w3.org/2023/05/23-pwe-minutes.html dbooth 15:25:08 i/I feel like we addressed it already/Topic: Issue 235 - proposed changes - Definition of "Microaggression" #241 15:25:32 rrsagent, draft minutes 15:25:34 I have made the request to generate https://www.w3.org/2023/05/23-pwe-minutes.html dbooth 15:26:59 s/Topic;/Topic:/ 15:27:02 rrsagent, draft minutes 15:27:03 I have made the request to generate https://www.w3.org/2023/05/23-pwe-minutes.html dbooth 15:27:49 s/tking/taken/ 15:29:12 rrsagent, draft minutes 15:29:13 I have made the request to generate https://www.w3.org/2023/05/23-pwe-minutes.html dbooth 16:36:35 dbooth has joined #pwe 16:49:50 i/AGREED: Close/[Ralph steps away to take a phone call] 16:50:50 s/before CoC is formally published./before CoC is formally published under the new name./ 16:51:12 s/i also suggest to Florian/I had also suggested to Florian 16:52:05 rrsagent, please draft minutes 16:52:07 I have made the request to generate https://www.w3.org/2023/05/23-pwe-minutes.html Ralph 16:52:57 present+ Sheila 16:53:28 rrsagent, please draft minutes 16:53:29 I have made the request to generate https://www.w3.org/2023/05/23-pwe-minutes.html Ralph 17:01:40 dbooth has joined #pwe