13:51:37 RRSAgent has joined #pwe 13:51:41 logging to https://www.w3.org/2023/04/25-pwe-irc 13:51:45 zakim, start the meeting 13:51:45 RRSAgent, make logs Public 13:51:47 Meeting: Positive Work Environment CG 13:57:58 dbooth has joined #pwe 13:58:33 present+ 13:58:42 rrsagent, draft minutes 13:58:43 I have made the request to generate https://www.w3.org/2023/04/25-pwe-minutes.html dbooth 14:00:05 present+ 14:00:11 wendyreid has joined #pwe 14:00:26 present+ 14:00:41 Jem has joined #pwe 14:00:41 Chair: Tzviya, Wendy 14:00:42 nigel has joined #pwe 14:00:59 Date: 2023-04-25 14:01:55 present+ 14:03:12 https://github.com/w3c/PWETF/pull/237 14:03:41 sheila has joined #pwe 14:04:11 scribe+ 14:04:39 Wendy: I added a definition of patronizing, since it can have more than 1 meaning in English. I took the Oxford definition. 14:04:51 ...I also clarified examples and fixed a typo 14:05:08 present+ 14:05:16 scribe+ 14:05:52 Tzviya: I think we've already discussed all of this except conveys vs portrays 14:06:04 a+ 14:06:07 i|Date:|agenda: https://lists.w3.org/Archives/Public/public-pwe/2023Apr/0003.html 14:06:11 sq+ 14:06:19 ...we do want to get this nailed down prior to the AC meeting, ideally 14:06:21 q+ sheila 14:06:26 ack sheila 14:07:14 q+ to disagree 14:07:16 sheila: on conveys vs betrays: I think conveys shows impact rather than intent. I would +1 keeping conveys vs betrays 14:07:18 +1 14:07:23 +1 to sheila 14:07:25 ack dbooth 14:07:25 dbooth, you wanted to disagree 14:07:57 q+ to respond 14:07:57 q+ 14:08:01 ack tz 14:08:01 tzviya, you wanted to respond 14:08:05 david: I think there's an important element in the definition of patronizing: an element of intent, insult, deceit - this gets lost if this is changed to conveys 14:08:32 tzviya: we've been trying to get across in the document that intent frequently doesn't matter; impact does. 14:08:35 q+ 14:08:38 ack sheila 14:09:35 sheila: the definition is one thing; we're trying to capture something else. There's a reason this is called patronizing language rather than patronizing feelings. 14:09:35 ack cw 14:09:44 +1 to Sheila 14:10:18 q+ 14:10:24 cwilso: I agree with sheila. This document is about what other people are feeling. We don't want to leave room for someoen to say, "But, I didn't mean it." It is my responsibility. 14:10:26 +1 to sheilka 14:10:27 q+ 14:10:28 ack wendyreid 14:10:29 +1 to sheila 14:10:39 chris: +1; it's about impact not intent 14:10:45 wendy: context really matters. 14:13:02 wendyreid++ 14:13:04 q+ 14:13:08 ack dbooth 14:13:08 +1 14:13:34 wendyreid: above all this document is to provide guidance not offer guidance for punishment 14:14:04 q+ 14:14:09 david: I understand impact vs intent. But the concept of being patronizing is that if the recipient feels the other person was being sincere, it's not patronizing. 14:14:11 ack she 14:14:17 dbooth: "I understand the idea of impact vs intent, but the concept of being patronizing is that the recipient feels that the patronizer was being insulting, as opposed to being genuinely kind and helpful. That is an important distinction. If someone is being genuinely kind or helpful." 14:14:39 sheila: but "betrays" refers to the intent of the person who said it, not the person who heard it. 14:14:57 q+ to straw poll 14:15:42 ...sometimes the context of how someone is trying to be helpful can still be patronizing 14:16:11 +1 14:16:19 If recipient feels that the speaker is being genuinely kind or helpful, then the recipient does not feel patronized. 14:16:51 q+ 14:17:17 tzviya: 14:17:43 ack tz 14:17:43 tzviya, you wanted to straw poll 14:17:50 ack cwilso 14:17:57 q+ to straw poll 14:18:16 scribe+ 14:18:30 cwilso: it also matters how others perceive what was said 14:18:34 cwilso: It's not just about whether the recipient feels patronized either, relationship matters, but also others can discern whether something is patronizing 14:18:39 ack Ralph 14:18:39 Ralph, you wanted to comment on examples 14:18:42 ... we're rabbit-holing 14:18:44 scribe+ 14:18:47 +1 to a straw poll, once people have had a chance to share 14:19:03 Ralph: I found Tzviya's examples informative, I've never had it happen to me, but seen it happen to others 14:19:24 ... it helps others in the room to see that that behaviour is inappropriate 14:19:33 scribe- 14:19:43 q+ To say I won't object to using "convey". I idont' think it's very important. 14:19:55 https://pr-preview.s3.amazonaws.com/w3c/PWETF/237/9cade31...8c0d884.html 14:20:25 ack me 14:20:25 tzviya, you wanted to straw poll 14:20:33 tzviya: POLL: ^^ 14:20:34 +1 14:21:02 ack next 14:21:03 dbooth, you wanted to say I won't object to using "convey". I idont' think it's very important. 14:21:18 +1 14:21:56 dbooth: I'm concerned that I find most of these examples to be examples of something else, like prejudice or rudeness. 14:22:05 q+ wendyreid 14:22:07 patronizing language often stems from implicit bias or prejudice 14:22:12 ^^ 14:22:16 +1 sheila 14:22:33 q+ 14:22:44 ack wendy 14:23:55 wendy: most patronizing language does come from implicit bias. It can come from people who have positive intent, or are just being nice. 14:24:13 +q to add comment on "readily found in any dictionary" and "doc from growing larger" 14:24:30 ...we already say "don't be racist" and "don't be sexist". This is a pattern that isn't explicit. 14:24:31 dbooth: Suggest simplifying the patronizing section to: "Patronizing language or behavior, such as using language that insultingly implies the audience is uninformed on a topic, e.g., making statements like "I can't believe you don't know about [topic]"." 14:25:09 q+ to ask dbooth a question 14:25:15 +1 to Wendy re: the idea that that this section is an umbrella for a lot of other objectionable problem that manifest as patronizing language 14:25:32 +1 to wendyreid 14:25:35 ... the reality is that this isn't here to punish people, it's to help guide people. 14:25:38 +1 wendy 14:26:48 ack sheila 14:27:59 ack Jem 14:27:59 Jem, you wanted to add comment on "readily found in any dictionary" and "doc from growing larger" 14:28:06 s/it helps others in the room/calling it out helps others in the room 14:28:17 sheila: on "I don't think you understood", there are a lot of other ways to ensure comprehension that are not questioning ability to comprehend. 14:28:29 I have made the request to generate https://www.w3.org/2023/04/25-pwe-minutes.html Ralph 14:29:00 jem: we should not rely on dictionary definition alone; one may give up instead of looking up in the dictionary. 14:29:18 ack me 14:29:18 tzviya, you wanted to ask dbooth a question 14:29:24 ...it is also very useful to be able to point to the exact type of behavior detailed in the document. 14:30:19 Should we adopt PR #237 14:30:20 +1 14:30:21 +1 to merge #237 14:30:23 -1 14:30:25 +1 14:30:26 +1 14:30:28 +1 14:30:28 +1 14:31:17 I think we spent an entire meeting discussing that exact issue 14:31:23 we did 14:32:20 I don't think there's going to be consensus 14:32:29 May we clarify "the assumption" "with prejudices", not just assumption? 14:32:39 i|Date:|-> https://www.w3.org/2023/04/11-pwe-minutes.html previous 11 April 14:32:55 q+ to ask the chairs to make a decision at this point. 14:33:07 -> https://www.w3.org/2023/04/11-pwe-minutes.html#t03 11 April discussion of #237 and #238 14:33:56 JenStrickland has joined #pwe 14:34:38 q+ 14:34:43 q+ to ask a process question about how we proceed if there's a single dissenting voice? 14:34:44 q- 14:35:17 qq+ 14:35:17 I suggested the "qualtification" 14:35:18 present+ 14:36:19 ack cw 14:36:19 cwilso, you wanted to react to tzviya 14:36:28 scribe+ 14:36:43 ack JenStrickland 14:36:44 cwilso: this should cause people to think 14:36:55 ... @@more 14:37:50 q+ to make a decision 14:37:56 dbooth: I could live with keeping the example, but not with their current wording. I think the wording problems that I see could be relatively easily corrected, and I'd be happy to make suggestions to do so. 14:39:44 ack sheila 14:39:44 sheila, you wanted to ask a process question about how we proceed if there's a single dissenting voice? 14:39:50 Thanks Jenn, for your comments! 14:39:52 Jen: perhaps we should table this for a while 14:40:10 sheila: process-wise, I don't know what happens in this kind of case 14:40:20 q+ to answer process question 14:40:34 ack cw 14:40:34 cwilso, you wanted to answer process question 14:41:07 sheila++ 14:41:39 present+ 14:41:41 q+ To say i think there's a simple path forward: I'll propose simple changes that would adequately address my concerns, while (I hope) retaining the important content that others believe are important. 14:41:50 ack me 14:41:50 tzviya, you wanted to make a decision 14:42:15 You did not see my next proposal yet. 14:42:28 tzviya: we are going to move on with this merge. 14:42:47 ...next issue 240: https://github.com/w3c/PWETF/pull/240 14:43:14 q+ 14:43:35 I think David can open new issue although we close the issue 237. 14:43:52 ack db 14:43:52 dbooth, you wanted to say i think there's a simple path forward: I'll propose simple changes that would adequately address my concerns, while (I hope) retaining the important 14:43:55 ... content that others believe are important. 14:44:11 ... this issue is summarizing the code. there is some question about whether this is helpful or not. 14:44:21 ack we 14:44:22 +1 Jemma, like the idea of merging and then David can open a new issue 14:44:39 q+ jemma 14:45:07 wendy: I see both sides of this, but I agree with Tzviya that we really do want people to read the whole thing. 14:45:33 ... I think maybe we need some opening text that captures the intent of the Code 14:45:37 q+ to improve the abstract 14:46:13 ...I don't want a really short version of what we've done, though 14:46:13 ack Jem 14:46:14 +1 14:46:51 jem and Sheila, process-wise, I don't think it would be appropriate for me to open a new issue on a closed issue. I think the process is for me to file a formal objection. 14:47:01 q+ re:summary 14:47:06 ack re: 14:47:16 q+ to make comment re:summary 14:47:41 ack me 14:47:41 tzviya, you wanted to improve the abstract 14:47:58 ack Ralph 14:47:58 tzviya: we have an abstract, we could consider improving the abstract. 14:48:04 ...rather than adding a summary 14:48:18 Putting it in the abstract seems like an adequate solution to me also. 14:48:40 ralph: I was going to make a similar comment: we shouldn't make an abbreviated version of the code. 14:48:42 david, right, that makes sense - I was just suggesting as a potential alternative if you wanted to submit a NEW set of edits that weren't the same as the previous. but you're probably right that a formal objection would be best 14:49:05 ...258 is about abstract 14:49:07 ack cw 14:49:07 cwilso, you wanted to make comment re:summary 14:49:39 Ralph: see #258; it accomplishes helping people know why they should read this 14:49:41 scribe: 14:50:21 cwilso: the "TL;DR;" practice self-destructed when people realized that 50% of those would not read the full version 14:50:36 ... if we say "here's the short version of the rules" then we're re-writing the rules 14:50:36 q? 14:50:50 People routinely read only the abstract of a paper and skip the body. 14:50:59 q+ 14:50:59 tzviya: should we replace this with 258 14:51:05 ack dbooth 14:51:21 david: is the idea to put this in the abstract? 14:51:55 tzviya: no: the abstract is something different, it is not intended to be a summary, but a declaration of value. 14:52:04 Proposal: Close #240, focus on #258 (revising abstract) 14:52:05 david: sounds fine, let's take that approach. 14:52:05 +1 14:52:05 +1 to close #240 without merging 14:52:07 +1 14:52:07 +1 14:52:10 +1 14:52:12 +1 14:52:14 +1 14:52:19 0 14:52:32 Resolved: Close #240, focus on #258 (revising abstract) 14:53:11 https://github.com/w3c/PWETF/pull/241 14:54:32 tzviya: proposed changes to microaggressions 14:55:37 ack Ralph 14:55:39 ...microagression can be a one-time thing, not just a repeated pattern, so I would disagree with that change 14:55:47 q+ 14:55:54 q+ to say a pattern is what matters. 14:56:26 ack sheila 14:56:41 ralph: I'm less uncomfortable with this. 14:57:24 q+ Jem 14:57:25 sheila: I agree with Tzviya that it doesn't need to be a pattern to count. Committing a single microagression warrants a discussion, and we should enable the document to capture that 14:57:34 +q 14:57:49 ack db 14:57:49 dbooth, you wanted to say a pattern is what matters. 14:57:49 +1 to Sheila's statement. 14:57:53 david: q+ to suggest text 14:58:10 q+ 14:58:12 david: pattern is really fundamental to the concept of microagressions. 14:58:37 ack jem 14:58:40 Definition: noun: micro-aggression a statement, action, or incident regarded as an instance of indirect, subtle, or unintentional discrimination against members of a marginalized group such as a racial or ethnic minority. "students posed with dry-erase boards documenting their experiences with microaggressions on campus" indirect, subtle, or unintentional discrimination against members of a marginalized group. "they are not subject to [CUT] 14:58:44 q+ 14:58:53 ...it's about cumulative effect. 14:59:37 q+ 14:59:46 ack sheila 15:01:14 +1 15:01:22 +1 15:01:48 I hear that "pattern" can be in different layers. thanks, Sheila 15:01:50 https://www.dismantlingracism.org/uploads/4/3/5/7/43579015/okun_-_white_sup_culture.pdf 15:01:52 I agree that a pattern does not need to be restricted to one person. It certaainly can be a pattern across multiple individuals and time. 15:01:59 sheila: I've been to a lot of trainings that describe microaggressions, it's not been described as patterns. 15:02:13 I wanted to point to Microaggression is a term used for commonplace daily verbal, behavioral or environmental slights, whether intentional or unintentional, that communicate hostile, derogatory, or negative attitudes toward stigmatized or culturally marginalized groups.[1] 15:02:18 (Wikipedia defn) 15:02:37 thank you! 15:02:38 i.e., the definition we are referencing is about individual slights, not patterns. 15:02:47 rrsagent, make minutes 15:02:48 I have made the request to generate https://www.w3.org/2023/04/25-pwe-minutes.html tzviya 15:03:11 zakim, bye 15:03:11 leaving. As of this point the attendees have been dbooth, tzviya, wendyreid, Jem, Ralph, JenStrickland 15:03:11 Zakim has left #pwe 15:09:07 present+ 20:23:53 RRSAgent has joined #pwe 20:23:53 logging to https://www.w3.org/2023/04/25-pwe-irc 20:23:57 rrsagent, make logs public 20:24:07 The meeting adjourned 5 hours ago. But in reviewing the minutes, I see that they do not adequately capture what happened when PR 237 was close. I am appending further explanation here. 20:24:12 Others should please correct me if you think I get anything wrong. What happened: 20:24:18 1. A straw poll was taken on the proposal to merge PR 237. Six members voted to merge, and one (DBooth) voted against merging. 20:24:24 2. Someone asked what to do if consensus is not reached. Chris said that there is a provision in the W3C process for the chair to make a decision without consensus. 20:24:30 3. DBooth offered to try to resolve the lack of consensus by proposing "simple changes that would adequately address my concerns, while (I hope) retaining the important content that others believe are important". 20:24:37 4. The chair made a decision to merge PR 237 in spite of the lack of consensus, without a taking a binding group vote, and without considering DBooth's offer to further try to reach consensus. 20:24:43 5. Two others suggested in IRC that DBooth should submit new issues against the newly merged text. 20:24:52 6. DBooth pointed out in IRC that "process-wise, I don't think it would be appropriate for me to open a new issue on a closed issue. I think the process is for me to file a formal objection". 20:24:59 rrsagent, draft minutes 20:25:00 I have made the request to generate https://www.w3.org/2023/04/25-pwe-minutes.html dbooth 20:25:37 s/was close/was closed/ 20:25:39 rrsagent, draft minutes 20:25:40 I have made the request to generate https://www.w3.org/2023/04/25-pwe-minutes.html dbooth 20:30:04 amy has joined #pwe