13:51:17 RRSAgent has joined #pwe 13:51:17 logging to https://www.w3.org/2019/07/11-pwe-irc 13:51:24 Zakim has joined #pwe 13:51:35 Meeting: PWE July Meeting 13:51:42 Date: 2019-07-11 13:51:48 Chair: An Qi Li 13:55:24 Ralph has joined #pwe 13:55:58 present+ 13:57:26 agenda: https://lists.w3.org/Archives/Public/public-pwe/2019Jul/0019.html 13:59:05 present+ 14:00:35 nigel has joined #pwe 14:01:53 angel has joined #pwe 14:02:00 present+ Angel 14:02:21 present+ 14:03:03 Present+ Nigel 14:03:30 present+ Judy 14:03:38 zakim, agenda? 14:03:38 I see nothing on the agenda 14:04:38 agenda +Review and merge open Pull Requests 14:04:54 agenda +3. Issue 56[4] - Improve details of reporting sections 14:05:14 agenda + Pull request discussion tracking 14:05:19 Judy has joined #pwe 14:05:24 agenda +5. ombuds training resources 14:05:37 agenda + Group priority and Publication Plan 14:05:53 agenda + AoB 14:06:31 Not knowing who is chairing or who scribed recently, I propose Angel 14:06:34 Not knowing who is chairing or who scribed recently, I propose wendyreid 14:06:35 zakim, take up agenda 1 14:06:37 agendum 1. "Review and merge open Pull Requests" taken up [from angel] 14:07:06 scribenick: Ralph 14:07:35 jorydotcom has joined #pwe 14:07:42 hello 14:08:23 -> https://github.com/w3c/PWETF/issues/56 #56 Improve details of reporting sections 14:08:38 Ada: thanks for the feedback 14:08:50 https://github.com/w3c/PWETF/issues/56 14:09:21 ... this was inspired by the BBC CoC which had very clear reporting guidelines 14:09:41 ... rapid response / emergency services info was missing; see separate PR 14:09:59 ... next PoC could be speaking to the chair 14:10:06 q+ 14:10:14 ... the chair should be familiar with those involved 14:10:43 ... but should the person not be comfortable raising an issue to the chair -- or if the chair is the issue -- they should be able to go straight to the Ombuds 14:11:13 ... and the chairs themselves should be able to go to the Ombuds if they don't feel they can resolve the issue 14:11:27 q+ 14:11:32 q+ 14:11:54 ack Judy 14:12:34 Judy: I'm glad to see we're not assuming everyone would be comfortable going first to the chair 14:12:51 ... I encourage that we provide other channels 14:13:04 ... where is the link to the BBC policy? 14:13:19 https://www.bbc.com/aboutthebbc/reports/policies/codeofconduct 14:13:23 bbc coc:https://www.bbc.com/aboutthebbc/reports/policies/codeofconduct 14:13:48 q? 14:13:59 ack nigel 14:14:19 -> https://github.com/w3c/PWETF/blob/master/ReferencesAndResources.md References and Resources 14:14:53 Nigel: regarding chairs being in the escalation path; some groups have multiple chairs 14:15:14 ... it should be possible that one chair can seek assistance from another chair 14:15:49 ... should a chair be able to do that, or approach another Team member, before going to the Ombuds? 14:16:21 Ada: giving people options and letting them go wherever they're most comfortable 14:16:30 Nigel: yes; open wording rather than closed wording 14:16:31 ack tzviya 14:16:57 Tzviya: +1 to Ada; we have to remember this is not a formal process and that people will go where they're more comfortable anyway 14:17:08 ... I'd prefer to advise people to go to a chair or Ombuds 14:17:09 + 1 to encourage people to go to umbuds and chairs 14:17:22 ... our goal should be to circulate this for review very soon 14:17:35 s/umbuds/ombuds 14:17:36 ... we'd discussed whether reporting should be more robust in this document or in a separate place 14:17:46 q+ 14:17:50 ... I'm fine adding a bit more to this document 14:17:53 ack angel 14:17:59 ... so we can circulate for review quickly 14:18:16 +q 14:18:25 Angel: will all chairs be comfortable handling issues such as these? 14:18:39 ack jorydotcom 14:19:00 Ada: we could say that if a chair is not comfortable handling CEPC issues the chair should help the individual raise it in other ways 14:19:13 Jory: that leads to the training issue 14:19:37 ... I've been talking with others about finding resources and developing a training program 14:20:02 ... we'd need to provide training before asking chairs to step into this role 14:20:12 ... we could even open it to everybody 14:20:16 q+ 14:20:19 ack Judy 14:20:21 +1 to the idea of training for Chairs, as a Chair! 14:20:28 Angel: could raise this during TPAC Chairs' Breakfast 14:20:56 Judy: important to have training for chairs, also important to not put them in this role before there is training 14:21:04 +1 to chairs' training, as a chair 14:21:17 +1 to chair's training, also as a chair 14:21:37 q+ 14:21:52 ack tz 14:22:11 Tzviya: every chair with whom I've spoken thinks this [training] is a good idea 14:22:24 ... people approach chairs now 14:22:37 ... we know that not everyone will handle such issues well 14:22:48 [jb: what tzviya is saying works for me] 14:22:52 ... people can judge for themselves what they think is the best option 14:22:58 ... so we can list several options 14:23:47 Judy: if we raise this with the chairs at TPAC, let's have a proposal; not just raise the question 14:23:58 Jory: agree; a concrete proposal for what we might provide 14:24:11 ... e.g. a 30-minute training session on responding to incident reports 14:24:18 ... and point to the type of materials we might use 14:25:09 Judy: "welcome everyone to be resources for each other, plan to have resources, plan to have a training session, any discussion" 14:25:15 Jory: sounds do-able 14:28:18 Ada: I'll make a pull request for #56 14:28:54 topic: Pull Request 57 - Clarify what we reserve the right to not act on 14:29:16 -> https://github.com/w3c/PWETF/pull/57 #57 "unacceptable" about reverse -isms 14:29:37 Ada: there was an old discussion on #44 where people felt OK to draft a pr 14:29:46 ... there have been some changes proposed to my initial text 14:30:31 ... social justice debates 14:30:35 ... tone 14:30:59 ... this is a list of stuff that Ombuds may choose not to act on 14:31:32 ... I'm working on improving the text based on the feedback 14:31:43 q+ 14:31:52 ... generally there seems to be agreement 14:32:14 ... the current conversation is on the opening text; do we have to guarantee that we will give a response? 14:32:55 ... the pr largely seems to be uncontroversial; it's getting the details right 14:33:18 ack nigel 14:34:19 Nigel: what's the motivation for 'will' vs. 'should'? 14:35:03 Ada: initially it read "will prioritize the safety" but the section was moved into a "... but ..." case and I didn't want to reduce the intensity of the initial statement 14:35:32 ... I didn't want to reduce the importance of that second bit with it being after a 'but' in the initial phrase 14:35:42 Nigel: perhaps 'but' should be 'and'? 14:35:51 Ada: there needs to be some contrast 14:36:07 ... we do need to take everything seriously but some issues shouldn't be brought forward for these reasons 14:36:20 ... but maybe 'and' does work 14:36:23 Nigel: or a new sentence 14:37:20 Ada: perhaps [the initial sentence] should be moved elsewhere 14:37:25 Nigel, Jory: +1 14:37:33 Ada: I'll make that change; it makes more sense 14:38:27 topic: pull request #51 14:38:46 -> https://github.com/w3c/PWETF/pull/51 #51 added rapid response info to Reporting 14:39:06 Ada: this is about contacting law enforcement first 14:39:15 ... we're waiting for an email address to populate the field 14:39:16 q+ 14:39:28 ... then it should be OK to merge 14:39:32 ack judy 14:39:39 Judy: a practical issue: 14:39:59 ... in most codes it's practical to say "contact local law enforcement" 14:40:22 ... we work in a very diverse organization where people come from multiple contries and may not be familiar with the jurisdiction they're visiting 14:40:45 ... it may be bewildering to have to find local law enforcement, and possibly not even safe 14:41:04 ... I suggest that we make this real and think about what might actually work 14:41:18 ... for instance, "if you need help in doing so, here's how ..." 14:41:23 q+ 14:41:46 ... these are hypotheticals but may be likely in our distributed international environment 14:41:59 ... "contact local law enforcement but also contact the Ombuds" 14:42:17 ... [W3M] has had some discussion about rapid response procedures 14:42:34 ack ralph 14:42:37 scribe: nigel 14:42:42 Ralph: 3 things. 14:42:48 s/practical to say/common to say, in urgent situations,/ 14:42:58 .. I concur with Judy's comment that someone might not know how to contact local law enforcement 14:43:21 .. There's a W3M conversation about rapid response protocol. 14:43:43 .. The current PWE procedures document notes [looks up the link] 14:43:47 https://www.w3.org/Consortium/pwe/#ombuds 14:44:09 .. lists the Ombuds and has a note that the Ombuds may be contacted individually or in subset (or all of them) 14:44:18 .. I realised we don't have a convenient way to contact all of them, so 14:44:23 .. I created an alias 14:44:27 mailto:ombuds@w3.org 14:44:41 .. I suggest that might be a reasonable place to start. 14:44:47 [JB: tries to clarify that I *wasn't* proposing adding detail about "How" -- I was suggesting adding something to make it less of an either-or, but rather a "both-and" -- e.g. contact local law enforcement, and feel free to also contact ombuds to ask for help or support with dealing with local law enforcement] 14:44:49 q+ 14:44:51 .. I proposed internally that we create an alias specifically for rapid response 14:44:56 .. That's undergoing discussion 14:45:23 Ada: I'll add that to the PR 14:45:30 Judy: That doesn't address my concerns fully 14:45:34 Ralph: I didn't intend it to. 14:45:35 q? 14:45:37 ack angel 14:45:46 q+ to re-focus the discussion of my suggestion 14:45:57 Angel: Practical suggestion: could we have the ombudsperson prepare the local law enforcement contact info 14:46:16 .. and people may not have an idea how to call the police like Tokyo, China, Lisbon. 14:46:35 .. When we have the location fixed before the event the ombudsperson could check out the local law enforcement 14:46:44 .. contact information and prepare that for quick access. 14:46:59 s/ location/contact info and way to contact 14:47:00 Judy: Difficult suggestion to do. In a given country of the many we hold meetings in, even from region to region 14:47:16 .. or city to city the contact policies may be different and that would be an exhaustive exercise to compile it. 14:47:23 .. It could get left off the planning list. 14:47:32 q+ 14:47:35 .. The frequency of urgent situations is hopefully low, but not non-existent. 14:47:49 .. What I was thinking of was different, which was to indicate not that a message would go to 14:47:49 -> https://en.wikipedia.org/wiki/List_of_emergency_telephone_numbers [Wikipedia] List of emergency telephone numbers 14:47:59 Judy, you wanted to re-focus the discussion of my suggestion 14:48:05 .. all the ombudspeople, but rather that we not present to somebody an either/or if it is an urgent issue. 14:48:16 .. Just say "call your local folks and feel free to let an ombudsperson know" 14:48:32 .. Along the same lines as physical injury away from base, have to go to emergency room. 14:48:51 .. We encourage people not to go alone but for someone else to go with them esp if the country isn't familiar to them. 14:49:05 q+ to ask about building security when available 14:49:27 .. I'm thinking of something lightweight - if urgent, contact local law enforcement and also you can let someone else know 14:49:34 Ralph, you wanted to discuss a practical suggestion about local instruction 14:49:42 Ralph: I think we're deep into details which are probably better handled outside this call 14:50:00 .. I thought we'd had a conversation, I don't recall where, but would solicit advice here, of making emergency, both 14:50:16 +1 to that 14:50:16 .. for law enforcement and health, a required part of every f2f meeting logistics planning and documentation 14:50:24 q+ 14:50:34 .. It's more general than the PWE issues we're discussing 14:50:39 ack ada 14:50:40 rrsagent, pointer? 14:50:40 See https://www.w3.org/2019/07/11-pwe-irc#T14-50-40 14:50:57 Ada: From recent meetings, when the venue has been hosted at a big organisation, 14:51:06 zakim, close the queue 14:51:06 ok, angel, the speaker queue is closed 14:51:11 I have made the request to generate https://www.w3.org/2019/07/11-pwe-minutes.html Ralph 14:51:11 .. we've been requested by the hosts not to call emegrency services but inform someone in the building 14:51:18 .. Wondering if important to see that represented. 14:51:32 Ralph: Exactly, that's not PWE, it's instructions for organising a meeting 14:51:50 .. Those kinds of venue specific constructions can't be done by ombuds in general. 14:52:05 .. The local organiser knows building-specific instructions. Exactly right Ada. 14:52:14 .. Date specific too 14:52:15 q? 14:52:26 ack nigel 14:52:26 nigel, you wanted to ask about building security when available 14:52:52 Nigel ... some buildings have security present 14:53:11 .. is it reasonable to suggest that they be part of a protocol 14:53:31 .. if people aren't comfy with local law enforcement 14:54:12 .. what happens if you go to a meeting hosted by a big company with it's own building security 14:54:17 q? 14:54:48 s/Nigel ... some/Nigel: Some 14:54:55 i/Nigel/scribe: jorydotcom 14:55:21 Judy .. when things have gone wrong, that's been one of the problems 14:55:48 .. let's say someone has a med emergency. you want to call local law enf anyway and you can notify security 14:56:05 .. but building sec. can still be a 5-10 min response cycle anyway 14:56:16 even in med emergency 14:56:32 -> http://emergency.mit.edu/ MIT's emergency instructions (for example) 14:56:32 .. so don't risk losing critical time by only contacting one 14:56:56 .. I like angel's idea about making sure local numbers are available 14:57:31 .. i'm suggesting that we add something that says if you do need to contact local law enforcement, please let an omsbudsperson know and whether you want someone to go with you 14:57:49 angel... I thnk thiis should be part of meeting of preparation 14:58:36 .. we have one more meeting between now and TPAC 14:58:51 .. should we have another meeting? 14:58:59 (+1) 14:59:17 .. group is +1 to scheduling bi-weekly 14:59:31 .. next call would be the 26th? 14:59:36 .. we still have items for today that are not finished 14:59:39 +1 15:00:23 .. group is ok moving add'l items from this week to next time 15:00:27 [JB: does anyone disagree with the suggestion I've been making? I can add an issue on this if needed; I have not heard an objection, but neither have I heard anyone respond directly on my suggestion, only other alternative ideas, some of which may also be useful.] 15:00:53 [I would appreciate an issue with specific wording, Judy] 15:01:05 .. we need to have something by end of August 15:01:26 ada .. would it be ok to get something after #57 is merged 15:01:34 angel .. yes 15:01:53 judy .. also looking for feedback on my suggestion, will add an issue 15:02:08 Ralph .. specific wording would be helpful 15:02:27 .. meeting concludes 15:05:40 question to probably @Ralph - is there a good resource for learning the irc bot commands etc? 15:05:45 I'm not so great at IRC 15:08:58 Jory, mostly people learn by watching :) but the "Running a Meeting" section of the Chair's Guidebook -- https://www.w3.org/Guide/#run -- has several resources that help to get started 15:09:14 jorydotcom: We have this resource we use in publishing :) https://github.com/w3c/publ-bg/wiki/Using-IRC-for-Meetings 15:09:23 A little more simplified 15:09:25 s/dotcom:/dotcom, 15:09:39 TY TY!!! 15:09:42 I have made the request to generate https://www.w3.org/2019/07/11-pwe-minutes.html Ralph 15:10:30 and, as Wendy just noted, each group customizes the "general practices" according to that group's preferences 15:11:16 scribe: Ralph, Nigel, Jory 15:11:31 present+ AdaRose 15:11:49 present+ Jory 15:11:53 zakim, bye 15:11:53 leaving. As of this point the attendees have been Ralph, tzviya, Angel, wendyreid, Nigel, Judy, AdaRose, Jory 15:11:53 Zakim has left #pwe 15:12:13 s/+q//g 15:13:06 s/(+1)/ +1 15:13:15 I have made the request to generate https://www.w3.org/2019/07/11-pwe-minutes.html Ralph 15:13:51 s/Judy .. when/Judy: .. when 15:14:22 s/angel... I thnk/Angel: I think 15:14:36 I have made the request to generate https://www.w3.org/2019/07/11-pwe-minutes.html Ralph 15:16:19 rrsagent, ybe 15:16:19 I'm logging. I don't understand 'ybe', Ralph. Try /msg RRSAgent help 15:16:22 rrsagent, bye 15:16:22 I see no action items