13:57:17 RRSAgent has joined #pwe 13:57:21 logging to https://www.w3.org/2024/03/19-pwe-irc 13:57:21 RRSAgent, make logs Public 13:57:22 Meeting: Positive Work Environment CG 13:57:48 date: 2024-03-19 13:57:55 chair: wendyreid, tzviya 14:07:31 sheila has joined #pwe 14:07:39 present+ 14:08:31 present+ 14:09:19 present+ 14:09:34 JenStrickland has joined #pwe 14:09:40 present+ 14:09:45 regrets+ David 14:09:48 present+ 14:09:56 https://www.w3.org/policies/code-of-conduct/ 14:10:11 scribe+ 14:10:17 tzviya: We published! 14:10:29 ... as soon as we published, we got some comments and we're hoping to sneak it in 14:10:38 ... there's an acknowledgements section and we forgot to update it 14:10:54 ... there's a lot of people who contributed to this update, since we've been working on it for 4 years 14:11:05 ... there's people who contributed who's names don't appear 14:11:57 ... we're unsure how to approach editing the contributors 14:11:57 q+ 14:12:02 ... thought we'd ask for advice 14:12:10 ... we want to update 14:12:29 ... typically a group adds all members, but we have a lot of members who do not attend 14:12:44 q+ 14:12:47 ... we forgot a few important people 14:12:50 ack sheila 14:15:13 [discussing contributor eligibility] 14:15:17 ack csarven 14:16:17 q+ 14:16:29 csarven: The complaints being mentioned, was it within PWE or elsewhere, was it reported or processed in any way? The optics might matter for attribution 14:17:07 ... or if it's "I've observed this person violating the code..." but the process to handle it has not been followed yet 14:17:31 sheila: Makes sense to me 14:17:32 ack me 14:17:48 tzviya: What makes this challenging, the reporting mechanisms are inadequate 14:17:56 ... we got comments on the ombuds situation 14:18:09 q+ 14:18:10 ... it's true, we've been working on it, Sheila has been working on it 14:18:15 ... it's out of our hands 14:18:33 ... if confidentiality were in place, and this was reported, we'd not know if it was handled 14:18:52 q- 14:19:10 q+ 14:19:20 ... I don't want to know details, but I'm uncomfortable with removing someone based on what others' allude to 14:19:22 ack sheila 14:19:26 ... confidentiality issues 14:19:32 sheila: I understand someone raising it 14:19:48 ... it's hard to see people credited who haven't followed the spirit of the document 14:20:13 ... I wonder if there's a world where they haven't been removed from the organization, as long as they are still a member, they are credited 14:20:31 ... we don't have the context or the authority to determine whose violations are bad enough to warrant removal 14:20:50 ... that's maybe as far as we can go with it 14:20:59 ... don't feel comfortable ranking violations against each other 14:21:25 JenStrickland: We're in a weird place, the ombuds program is not working, there's not always proper resolution for issues even now 14:22:31 ... we have to be neutral 14:22:33 q+ 14:22:39 ack wendyreid 14:24:29 q+ 14:24:48 +1 14:24:51 tzviya: Might be worth doing as a paragraph of contributors 14:25:04 [Ralph joins] 14:25:31 csarven: Separate topic maybe, in the SOLID CG, we have a code of conduct, we also acknowledge the W3C code 14:25:33 wendyreid: It is tricky but this document is still unique. We wouldn't have this discussion if it was a technical document. And we do have the culture of ack'ing and giving credit where it is due. It could be arbitrary / and weaponised. I can also see the other side seeing someone's name... 14:26:16 ack csarven 14:26:17 ... our code of conduct extends the W3C one, we have enforcement to a certain extent, improve the work space where possible 14:26:48 ... I'm curious to know, if this is a rare thing in W3C to have their own CoC committee or enforcement processes 14:27:02 Solid CoC: https://github.com/solid/process/blob/main/code-of-conduct.md 14:29:26 [giving Ralph an overview of discussion so far] 14:30:03 q? 14:31:03 Ralph: My intuition is that removing someone from a published list may raise flags, but updating it with people who need to be included is reasonable 14:31:20 q+ 14:31:29 sheila: 14:31:31 ack sheila 14:34:29 s/sheila:// 14:34:40 tzviya: Sheila, any update on ombuds? 14:34:48 sheila: I met with Seth, it's on his priority list 14:35:04 ... he is going to do more thinking on internal vs external but is leaning towards external 14:35:12 ... I'm going to send him some resources 14:35:23 ... challenge is finding ombuds who aren't academic-focused 14:35:35 ... resources for sourcing outside those institutions 14:36:05 JenStrickland: Would there be something that's more conflict-mediation oriented? Non-violent communication practitioners 14:36:44 sheila: I'm looking at that, and we're looking at mediators/investigators, and I'm talking with the ombuds association to try and find options, I've only done this in the US 14:36:47 ... we need international 14:36:53 tzviya: Thanks 14:37:09 s/ombuds association/international ombuds association 14:40:18 tzviya: Now that the code is published and ombuds is moving, what now? 14:40:36 Ralph: I would love to see effort put into what kinds of activities we can do to increase positivity 14:40:46 q+ 14:40:57 ack sheila 14:40:57 ... what can we do during remote meetings, in person meetings, etc 14:41:02 ... help us feel more connected 14:41:34 sheila: Dispute resolution guidelines, I did one of the AC onboarding videos, and I wanted to talk about dispute resolution 14:41:44 ... I know we're working on ombuds and mediators 14:41:49 ... a priority for me too 14:42:02 q+ 14:42:49 tzviya: We put it on ice a bit since we didn't know how to proceed 14:43:07 ack csarven 14:43:08 wendyreid: We need to have it reviewed, but we did want to publish parts of it that we felt good about 14:43:57 csarven: If any group were to provide training, it would be this group, to come in and understand the code and facilitate the meetings 14:44:07 ... more training for community groups 14:44:18 ... a lot of the encounters I have, I think people are unaware of the code 14:44:28 ... or at least unaware of its contents 14:44:44 ... training for chairs to be more understanding of dynamics 14:44:58 ... more to it than common sense, why the code exists and what are our expectations 14:45:25 ... even in SOLID's case, we run into cases where we're not sure how to handle something 14:45:39 ... we're hoping that there can be more input to make CGs a better work space 14:45:45 q+ to mention translations 14:45:56 ... this group can help educate and train the wider community on the code and its contents 14:46:33 love the idea of a resource and training hub around the CoC etc 14:46:51 s/CoC/Code 14:47:01 JenStrickland: Sarven brings up an interesting point, there is the training, but maybe members of PWE can go to groups to help educate them 14:47:56 q+ 14:48:08 ack Ralph 14:48:08 Ralph, you wanted to mention terminology 14:50:33 C.O.C. is such a common acronym. It's not like it's used as the curse word, spoken as a rooster, for example. The irony that Sheila works for Bocoup with their rooster makes me lol. 14:52:51 tzviya: We've done talks, we've done sessions on running better meetings 14:53:06 ack me 14:53:06 tzviya, you wanted to mention translations 14:53:08 ... in terms of speaking about the code, it's not done yet, an overview for chairs to do 14:53:18 ... giving chairs a script to run through 14:53:26 q+ 14:53:44 tzviya: I haven't looked at this in a while, but to give chairs materials to work with 14:53:46 ack shei 14:54:15 sheila: I really love the suggestion, I wonder if we could do an activity to identify the biggest pain points, look at the resources, and then see if we're covering them 14:54:28 ... look at our resource library and filling the gaps 14:54:39 ... here is an organized set of resources 14:54:52 ... here's a way for us to be proactive 14:54:58 ack wendyreid 14:57:25 q+ 14:57:31 q+ 14:57:35 wendyreid: Let's build up those resources! We should bring back the chairs meeting, and more training and resource opportunities 14:58:27 csarven: I think as a side effect, by attracting more individuals to the conduct, we can improve behaviour and work 14:58:43 ack sheila 14:59:02 sheila: Wanted to add, we also could revisit the conversation of the tenor of the listserv 14:59:26 ... resource lists, next steps on dispute resolution, something around listservs and moderation 14:59:35 ack JenStrickland 15:00:14 JenStrickland: The trainings that Wendy held had lower attendance, maybe it's worth having PWE do sessions with groups presenting the training, as a conversation too 15:00:42 ... get feedback and information on challenges groups have about implementing positive work environments and inclusion in their groups 15:00:56 +1 to the idea of a tour, once we have our resources gathered! 15:01:40 ... what we're doing in PWE is what W3C wants, more collaboration, more inclusion, more technical development that benefits society 15:02:08 ... a good example is the sustainability group, they work hard to work together 15:02:26 ... an opportunity for us to help 15:02:29 tzviya: Thanks Jen 15:02:52 ... I think we need to gather resources, then it would be interesting to see if we can pull something like that off, if groups are willing to spare their time 15:03:21 JenStrickland: Maybe a requirement for groups, to address issues that have been reported, or to prevent them 15:04:04 tzviya: I hear what you're saying, I'm not sure we can change groups but stepping in, but it needs some thought on how to proceed 15:05:28 ... we need to sell it by convincing them that this will improve their product, their work 15:05:36 present+ 15:05:50 [CWilso joins] 15:06:15 ... here's how diversity can improve your specification 15:06:37 ... first step, lets get our ducks in a row 15:06:45 ... get the documents organized 15:06:58 zakim, end meeting 15:06:58 As of this point the attendees have been sheila, tzviya, wendyreid, JenStrickland, csarven, cwilso 15:07:00 RRSAgent, please draft minutes v2 15:07:02 I have made the request to generate https://www.w3.org/2024/03/19-pwe-minutes.html Zakim 15:07:10 I am happy to have been of service, wendyreid; please remember to excuse RRSAgent. Goodbye 15:07:10 Zakim has left #pwe 15:07:18 rrsagent, make logs public 15:07:29 rrsagent, bye 15:07:29 I see no action items