14:39:56 RRSAgent has joined #pwe 14:40:00 logging to https://www.w3.org/2025/01/07-pwe-irc 14:40:06 Meeting: PWE 14:40:14 Chairs: Tzviya, Wendy 14:40:24 Date: 2025-01-07 15:00:09 wendyreid has joined #pwe 15:01:00 JenStrickland has joined #pwe 15:01:12 present+ 15:01:39 present+ 15:02:10 dbooth has joined #pwe 15:02:16 rrsagent, pointer? 15:02:16 See https://www.w3.org/2025/01/07-pwe-irc#T15-02-16 15:02:32 rrsagent, make logs public 15:02:34 present+ 15:02:41 zakim, start the meeting 15:02:41 RRSAgent, make logs Public 15:02:43 Meeting: Positive Work Environment CG 15:02:43 present+ 15:04:49 scribe+ 15:05:28 present: CWilso, Tzviya, WendyReid, JenStrickland,DBooth,SheilaMoussavi,Ralph 15:05:31 sheila has joined #pwe 15:05:57 topic: Ombuds Program 15:06:24 Sheila: I have a meeting with Catrina, Seth's Chief of Staff, right after this 15:07:09 Tzviya: we'll take the documents that have been sitting in GitHub for a long time and write an escalation path when Ombuds are not available 15:07:16 https://www.w3.org/about/positive-work-environment/ 15:07:22 ... we have things in several places now' 15:07:40 ... PLH recommended the PWE landing page ^^ 15:08:08 ... that page has a link to a procedures document 15:08:21 ... we'll eliminate this page and move the procedures information to /Guide 15:08:45 ... we'll be able to update /Guide via GitHub 15:08:46 q+ to ask about "the guide" 15:09:16 ... if this group has consensus about what should go into /Guide, PLH feels it unlikely that the Team will revise our consensus 15:09:39 ... my inclination is to have education and training in our repo 15:09:52 ... feedback about the CoC doesn't belong here; it is already in GitHub 15:10:03 q? 15:10:04 ack dbooth 15:10:04 dbooth, you wanted to ask about "the guide" 15:10:15 Is this what you mean by "the guide" https://www.w3.org/Guide/ ? 15:10:21 David: do you mean ^^ 15:10:24 Tzviya: yes 15:10:39 ... PLH is working on consolidating things there 15:11:00 David: that document is mostly an organization of links right now 15:11:01 https://www.w3.org/Guide/ 15:11:12 ... it seems reasonably well organized as a collection of links 15:11:18 https://www.w3.org/Guide/ 15:11:20 ... are you expecting to add content as well? 15:11:23 Tzviya: it has both 15:11:28 JenStrickland has joined #pwe 15:12:10 amy has joined #pwe 15:12:11 I'm logging. I don't understand 'please draft meetings', Ralph. Try /msg RRSAgent help 15:12:17 I have made the request to generate https://www.w3.org/2025/01/07-pwe-minutes.html Ralph 15:12:26 ... we could highlight CoC more 15:12:39 https://www.w3.org/Guide/process/suspension.html 15:13:02 ... we would have Procedures as a sublink 15:13:14 present+ 15:13:26 ... it would live in the GitHub repo for /Guide and therefore be easier for us to update 15:13:48 q? 15:14:09 ... we'll rewrite and relocate the procedures page 15:14:17 q+ for more clarification 15:14:21 ... then rewrite it again when we have Ombuds 15:14:40 agenda: https://lists.w3.org/Archives/Public/public-pwe/2025Jan/0000.html 15:14:55 ... there will be other materials we can add; e.g. Incident Resolution 15:14:56 ack dbooth 15:14:56 dbooth, you wanted to discuss more clarification 15:15:10 David: are we talking about merging incident resolution into the 'suspension' page? 15:15:16 Tzviya: no, it will be its own page 15:15:22 David: so there will be overlap 15:15:36 Tzviya: we'll work out those details, for now work on the escalation path 15:15:43 q+ 15:15:55 ack wendyreid 15:16:08 Wendy: there's desire to revise /Guide in general 15:16:26 ... it is organized but still hard to find something you're looking for 15:16:42 q+ 15:17:14 ack JenStrickland 15:17:16 i|Date: 2025|-> https://www.w3.org/2024/12/10-pwe-minutes.html previous 10-Dec| 15:17:25 ... we'll work with Team on that 15:17:36 Jen: do we have a list of what kinds of things can go into /Guide? 15:17:39 q+ to recommend limiting expansion of guide right now 15:18:18 Tzviya: as of now we're working on escalation aka Incident Resolution 15:18:39 ... Sheila and Catrina will let us know in the future what to document regarding Ombuds 15:19:00 ack amy 15:19:00 amy, you wanted to recommend limiting expansion of guide right now 15:19:06 right now it is Guide -> Running a Group ->-> (subsection) People management -> 15:19:08 ... for the short term it's the incident resolution document and possibly editing the suspension document based on what we conclude for incident resolution 15:19:51 Amy: let's address what comes under Code of Conduct and the procedures; let's focus there 15:20:11 ... Procedures is linked from /Guide 15:20:27 Tzviya: yes, but PLH wants to pull these strings into /Guide 15:21:18 Amy: please include the Team 15:21:21 Tzviya: sure 15:21:39 https://github.com/w3c/PWETF/blob/main/conflict_resolution.html 15:21:55 Tzviya: we have ^^ 15:22:09 https://www.w3.org/about/positive-work-environment/#Procedures 15:22:23 https://github.com/w3c/PWETF/pull/364 15:22:23 s/the Team/the Team, in particular Comm Team/ 15:22:37 ... we have a lot of material to work from 15:23:04 ... these documents currently all assume the existence of ombuds; our task now is to create versions that do not rely on ombuds 15:23:16 ... in particular, look at escalation 15:23:35 ... how can we make a functional path of escalation? 15:23:52 I have made the request to generate https://www.w3.org/2025/01/07-pwe-minutes.html Ralph 15:24:03 q+ 15:24:06 ... example: a participant in a WG has an issue with the chair; to whom do they go? 15:24:18 ack sheila 15:24:28 ... what can we document that is not "go straight to the CEO"? 15:24:42 Sheila: it should be someone on the Team before the CEO 15:24:48 q+ to ask about existing ombuds 15:25:14 + to mention good and bad ideas for escalation including: option to reach out to more than one person, possibly a list (are there ways this can be a not bad idea?); i wonder about chair/team contact/area lead 15:25:21 ... someone who works closely with the CEO but is not in a position to ban someone from the Consortium but who could escalate if needed 15:25:22 ack me 15:25:22 tzviya, you wanted to ask about existing ombuds 15:25:32 Tzviya: we have some Ombuds listed 15:25:41 q+ amy 15:25:42 ... do they have training 15:25:54 ralph: We have not had any formal training for current ombuds. 15:25:55 s/ing/ing?/ 15:25:55 ack amy 15:26:39 Amy: I've heard that if an issue only goes to one person they can get stuck 15:26:54 ... and little accountability 15:27:08 ... including Catrina is a good idea if it's a message to Seth 15:27:47 ... but including an archived list could be bad; we don't want personal details there 15:28:28 [the ombuds@w3.org alias is a set of people, and not archived] 15:28:51 ... could things go to the Team Contact [of the WG] and to an area lead? 15:29:07 ... to keep it from being funneled to just one person without followup 15:29:14 q+ 15:29:19 ack sheila 15:29:24 Including the area lead sounds like a good idea to me. 15:29:42 Sheila: I'm wary of using the ombuds@ email before there is training set up 15:29:44 +1 15:29:50 ... I'd rather start fresh 15:29:56 I also wonder about some kind of training. even something like non-violent communication that team or others could take 15:30:01 +1 to "and/or" 15:30:05 ... I think and/or rather than just and is good 15:30:09 +1 to and/or 15:30:28 ... having a few options of people to go to; good practice to document multiple possibilities 15:30:48 q+ 15:31:14 ... a rational next step could be if the chair doesn't engage, the chairs of the PWE CG could be a backup 15:31:19 +1 to Chairs and I might add in some TF - as Sheila just mentioned, those who have some training 15:31:38 ... and there's also access to the CEO if further escalation is needed 15:31:41 ack JenStrickland 15:32:00 q+ to echo PWE idea from Shiela with option for Chairs+TF training? 15:32:31 Jen: any of us in PWE could receive training too 15:32:40 q+ to mention liability (sorry) 15:33:42 ... in the work we've been doing we have ability to be neutral, see the big picture, genuinely want to help 15:33:55 ... make sure we all get training when the training is ready 15:34:05 ... I'd love to see more international people involved in PWE 15:34:38 ... I can make some recommendations 15:35:13 q+ to say I think we have an obligation to have the current ombuds somewhere in any interim escalation path, because that's the guidance we've been giving and will be giving when the ombud program is in place. 15:35:15 ack amy 15:35:15 amy, you wanted to echo PWE idea from Shiela with option for Chairs+TF training? 15:36:19 +1 to amy's suggestion for training 15:36:20 Amy: if we see a change to the procedures as an interim step and we create guidelines it would be good to make training available for interested people to 15:36:38 ... maybe it's open to chairs 15:36:44 s/people to/people/ 15:36:58 ack me 15:36:58 tzviya, you wanted to mention liability (sorry) 15:37:00 ... anyone identified in procedures should have training 15:37:08 Tzviya: +1; that's an important point 15:37:22 ... I also wanted to point out liability considerations 15:37:57 ... these are questions that need to be discussed with Christine 15:38:00 +1 to including Christine for questions of training etc 15:38:21 ... the PWE CG has 40+ "members"; not everyone in the CG can be trained 15:38:47 ack dbooth 15:38:47 dbooth, you wanted to say I think we have an obligation to have the current ombuds somewhere in any interim escalation path, because that's the guidance we've been giving and will 15:38:50 ... be giving when the ombud program is in place. 15:38:53 ... we need to be careful about who is named in our interim process 15:39:30 David: given that the guidance thus far has included mention of ombuds, I think it is important that the interim process include mention of current ombuds 15:39:35 ack Ralph 15:39:38 Tzviya: I don't think so 15:40:50 Ralph: we need to revisit the list 15:41:05 i would recommend we not label anyone as a kind of interim ombudsman. we had at MIT different levels of duty for reporting. there was a term "Responsible Employee obligation" for which one had to be trained 15:41:30 Tzviya: we can have multiple options on where to escalate 15:41:38 eg: https://idhr.mit.edu/education/pshtraining 15:41:49 ... I'm soliciting ideas; we'll do some drafting on how to move forward 15:41:54 q+ 15:41:59 ack sheila 15:42:08 ... we had concepts such as mediation and I don't think we're ready fo rthat 15:42:15 s/fo rt/for t/ 15:42:30 Sheila: I think the next step is to learn Catrina's expectations 15:42:45 ... beyond that, who makes the most sense among the options 15:43:17 ... once we have the ombuds program we can add other escalation possibilities 15:43:21 ... simpler is better at this stage 15:43:33 q+ to wonder if we should invite Christine to our next meeting to ask some of these questions 15:43:37 Can it be you, Sheila? :) 15:43:39 +1 for simple 15:44:31 who is for accessibility? 15:44:38 Amy: we have Team Contacts for each Group 15:44:42 https://www.w3.org/staff/ 15:44:48 ... if you look at the staff list you see more nuance 15:45:49 q- 15:45:52 ack Ralph 15:46:54 ralph: There are different sets of responsibilities. If an issue involves a team member, different criteria may determine who to contact. Don't expect tech people to be involved with this kind of issues. 15:47:12 I need to drop. Thanks all! 15:47:34 s/expect tech people/necessarily expect those people identified with specific technical areas 15:47:43 +1 to this idea 15:48:03 Tzviya: it's possible that Christine and Catrina might be resources 15:48:20 ... we need an interim process, may be short-term 15:48:24 (Christine and/or Catrina I mean) 15:48:31 ... we can write the shell of a document without names 15:48:57 ... it's going to be more work to write this document as we don't yet have a clear path 15:49:02 +1 to help 15:49:03 Sheila: I'm happy to help 15:49:09 Tzviya: thank you very much 15:49:44 Amy: are there other reactions to reporting to a list or an alias? 15:49:57 ack Ralph 15:50:14 q+ 15:51:29 q+ 15:51:51 ack sheila 15:52:04 Ralph: both cases are important: an alias that goes to a set of responsible people as well as an enumeration of who is on that list so that an individual can be contacted 15:52:20 Sheila: I feel strongly there should be an alias that allows everything to be tracked 15:52:40 ... in the interim, in the absence of a clear process, it could be more dangerous to have that 15:52:50 +1 to Shiela's nuance for short term no, long term absolutely 15:52:51 ... so no in the short term but longer-term absolutely 15:52:59 ... in the interim, one-to-one communcation 15:53:11 s/Shiela/Sheila 15:53:14 ... in the long term there needs to be a secure place where everything goes 15:53:15 ack me 15:53:17 Tzviya: +1 15:53:27 ... we have to figure out the archiving 15:54:04 I appreciate Tzviya's long term thinking for tracking 15:54:41 ... we need training 15:54:55 ... the majority of our issues are about deescalation 15:56:17 ack Ralph 15:58:04 Tzviya: thanks; we're adjourned 15:58:09 zakim, end meeting 15:58:09 As of this point the attendees have been CWilso, Tzviya, WendyReid, JenStrickland, DBooth, SheilaMoussavi, Ralph, amy 15:58:11 RRSAgent, please draft minutes v2 15:58:12 I have made the request to generate https://www.w3.org/2025/01/07-pwe-minutes.html Zakim 15:58:18 I am happy to have been of service, Ralph; please remember to excuse RRSAgent. Goodbye 15:58:19 Zakim has left #pwe 17:34:19 dbooth has joined #pwe