13:47:43 RRSAgent has joined #pwe 13:47:43 logging to https://www.w3.org/2021/07/06-pwe-irc 13:47:49 Zakim has joined #pwe 13:48:29 Agenda 13:48:29 Agenda+ Revised ombuds job description + selection criteria and interview techniques 13:48:29 Agenda+ Early draft of Disciplinary Procedures 13:48:29 Agenda+ Grants for the Web 13:48:30 Agenda+ Survey updates 13:48:30 Agenda+ AOB 13:56:38 jeff has joined #pwe 14:00:03 present+ 14:01:54 Ralph has joined #pwe 14:02:03 present+ 14:02:12 scribe+ 14:02:16 present+ 14:02:21 regrets+ WendySeltzer 14:02:24 presnet+ Sheila, Tobie, Mallory 14:02:29 s/presnet+ Sheila, Tobie, Mallory// 14:02:32 sheila has joined #pwe 14:02:38 present+ Sheila, Tobie, Mallory 14:04:03 sheila: Working on the job description for the ombuds role 14:04:04 https://github.com/w3c/PWETF/pull/180 14:04:16 ... I just incorporated the edits into the actual job description 14:04:32 ... main changes were about the relationship between the ombuds role and formal procedures 14:04:44 ... also a few questions around how folks are prepared for this role 14:04:49 present+ Jeff, Judy 14:04:49 ... training would be part of this role 14:04:57 ... and we need to still figure out the nature of the training 14:05:09 ... hopefully these edits are relatively straightforward and clarify 14:05:11 Judy has joined #pwe 14:05:23 ... just to reiterate, this is meant to complement a formal grievance process 14:05:28 ... it is not intended to replace it 14:05:29 present+ 14:05:50 ... the idea is that the ombud is a neutral third party, someone to talk to, or to assist with the grievance process 14:06:06 ... the research indicates that people are more likely to report when there are options 14:06:21 ... the ombuds are meant to help the process run quickly and smoothly 14:06:26 https://github.com/w3c/PWETF/pull/180 14:06:30 ack Ralph 14:06:50 Ralph: Thanks, maybe you could expand briefly on the implication of dropping the word peer 14:07:07 sheila: There were a couple of comments where people found that confusing, uncertainty about the role 14:07:15 ... the person may not actually be a peer 14:07:36 ... the people who are engaging as ombuds should not be leadership in the W3C, and I made that language more clear 14:07:38 Ralph: Thanks 14:07:51 tzviya: I'm guessing people have not had a chance to review this 14:07:55 present+ 14:07:56 ... so we'll vote on this later 14:07:59 ... thank you for the edits 14:08:13 present+ Annette, Hober 14:08:25 sheila: One of the things we talked about was how to select ombuds 14:08:26 present+ Barbara 14:08:32 ... what the process would be for vetting them 14:08:47 ... one of the things we thought was the idea of treating as a proper interview process 14:08:53 ... treat it like an actual position 14:08:57 regrets+ Jemma 14:09:04 ... it might be good to have a representative from all of the regions 14:09:09 ... open to other ideas 14:09:18 ... people could nominate others or self-nominate 14:09:26 ... and then there'd be a committee to select 14:09:35 ... there would be requirements in the job description 14:09:40 ... and an interview guide 14:09:56 ... outstanding question is how many people do we want on the committee, and how do we choose the ombuds 14:10:01 ... we want it to be intentional 14:10:07 ... it's an important and sensitive role 14:10:21 ... any thoughts and questions? 14:10:29 ... I'll put together an interview guide 14:10:43 q? 14:10:46 tzviya: Any comments? 14:10:54 ... I guess everyone needs some time to digest 14:10:59 ... thanks so much Sheila 14:11:05 Barb_H has joined #PWE 14:11:05 zakim, next item 14:11:06 agendum 1 -- Revised ombuds job description + selection criteria and interview techniques -- taken up [from tzviya] 14:11:15 https://github.com/w3c/PWETF/blob/main/CEPCdisciplinary-process.md 14:11:17 zakim, next item 14:11:17 agendum 1 was just opened, wendyreid 14:12:01 tzviya: This is based on a disciplinary process from Tetralogical, based on UK standards, some of this doesn't apply to us, like salary 14:12:18 ... there's a list of open questions based on the questions from Wendy S 14:12:24 ... I would appreciate feedback here 14:12:30 ... the current process is really vague 14:12:43 ... doesn't define what merits discipline and is very tied to the director 14:12:57 q+ to point to Contributor Covenant for this: https://www.contributor-covenant.org/version/2/0/code_of_conduct/ 14:12:58 ... has a strikes system, but I'd love some suggestions 14:13:04 ack tobie 14:13:04 tobie, you wanted to point to Contributor Covenant for this: https://www.contributor-covenant.org/version/2/0/code_of_conduct/ 14:13:15 tobie: I just wanted to say this looks like a good start 14:13:27 ... reminds me of the contributor covenant 14:13:37 ... this is used a lot in open source so is releveant 14:13:40 tzviya: Thanks 14:13:58 ... does anyone have any feedback on who should be enforcing this 14:14:08 ... we had this discussion with CEPC 14:14:18 ... I hesitate putting it in the hands of the director 14:14:27 Comment - Level of aggrievance? 14:14:30 ... since we're moving to director-free, we're moving to a board of directors 14:14:38 ... is this something we ask chairs to do? 14:14:44 q+ 14:14:46 ... but chairs sometimes are violators as well 14:15:23 Barb_H: With the grievance, I like the overall strategy, but sometimes the offense is small/medium/large, I worry about using a heavy process for all of them 14:15:31 ... I wonder if there is a way to score a grievance 14:15:34 ... minor vs major 14:15:40 ... I don't have an easy answer 14:15:50 ack hober 14:15:58 hober: On the question of who enforces 14:16:20 annette_g has joined #pwe 14:16:23 ... like you mentioned, chairs are also potential violators, but are also responsible for running meetings, where violations can occur 14:16:30 present+ 14:16:31 ... I think there's a real value in swift action 14:16:46 ... making it clear immediately that something is inappropriate 14:17:22 ... if someone violates CEPC during a meeting 14:17:27 q+ to talk about how Node.js does this (in terms of prevention / upfront work) and OpenJSF (in terms of escalation strategy) 14:17:37 ... and I as a chair corrects it to keep the meeting running, it's not exactly confidential 14:17:46 ... it's best if you can to pull them aside 14:17:53 ... but an hourlong phone call 14:18:12 ... the important thing there is to correct in a way that says "this is wrong" to everyone 14:18:21 ... chairs should be part of the solution 14:18:23 +1 14:18:26 ack tobie 14:18:26 tobie, you wanted to talk about how Node.js does this (in terms of prevention / upfront work) and OpenJSF (in terms of escalation strategy) 14:18:31 q+ 14:18:43 tobie: I just wanted to mention about light vs more grave ones 14:18:50 ... node.js has process on this 14:19:06 ... removing offensive comments/approaching people before a grievance process 14:19:21 ... to understand people who are being problematic 14:19:33 ... work that happens before you enter an enforcement situation 14:19:48 ... educating people instead of defaulting to punishment 14:20:03 ... openjsf has an escalation process 14:20:11 ... every project can handle CoC violations on their own 14:20:17 ... using whatever resources they have 14:20:29 ... but there's an escalation strategy to a structure that's owned by the foundation 14:20:46 ack Judy 14:20:47 ... in case you're not happy with the project-level management or the leader in that project is the one being problematic 14:20:54 Judy: To comment on the severity issue 14:20:59 ... I agree it's important 14:21:10 ... it's very common that most issues fall into a grey zone 14:21:21 ... it depends on the people in the meeting 14:21:28 ... I'm interested in the early-stage education approach 14:21:37 ... I just re-reviewed the CEPC 14:21:51 ... I was trying to recall if we tried to tackle severity, and I think we dodged it 14:21:57 ... I think there's work to do in gauging that 14:22:08 OpenJSF code of conduct and escalation approach: http://code-of-conduct.openjsf.org/ 14:22:09 q+ 14:22:13 ... it's a thornier one 14:22:13 ack hober 14:22:21 hober: Something that just occurred to me 14:22:29 ... if we do make a distinction between minor and major 14:22:38 ... I think it should be explicitly called out 14:22:47 ... instead of left to enforcement 14:23:10 ... we often see rules clearly written, but not enforced for the dominant group, and weaponized against those on the margins 14:23:14 https://www.w3.org/Consortium/cepc/#safety-versus-comfort 14:23:25 +1 to hober's point. 14:23:29 ... people who have been around for awhile may get more lenient treatment 14:23:50 +1 14:23:55 ... newcomers may be squashed for being unfamiliar to our process or groups 14:24:01 ... less room for interpretation 14:24:01 q+ 14:24:19 ack sheila 14:24:20 tzviya: I think that's an excellent point, and I think maybe should go into the safety vs comfort section 14:24:34 sheila: One way to address that point, being explicit about priorities 14:24:40 ... in the safety vs comfort section 14:24:49 ... whose safety is prioritized, why, and when 14:25:01 ... this isn't meant to be a blanket and vague policy 14:25:22 ... that inevitably will be inequitebly applied 14:25:41 tzviya: There's enforcement powers and a grievance process 14:25:48 ... can't be weaponized 14:25:57 ... there's a difference between annoying and violating CEPC 14:26:45 ... some of the other questions are what are the relationships to the membership agreement, can this be doctored, what about rapid response 14:27:04 ... rapid response might be something we're best equipped to respond to 14:27:15 ... I think that needs to be documented 14:27:36 ... we have contact emergency services, but what about the fallout 14:27:43 q+ to share: https://github.com/mozilla/inclusion 14:27:52 ack to 14:27:52 tobie, you wanted to share: https://github.com/mozilla/inclusion 14:28:07 tobie: I just wanted to share the mozilla resource which is their work on this 14:28:12 zakim, next item 14:28:12 agendum 2 -- Early draft of Disciplinary Procedures -- taken up [from tzviya] 14:28:18 zakim, next item 14:28:18 agendum 2 was just opened, wendyreid 14:28:28 zakim, close this item 14:28:28 agendum 2 closed 14:28:29 I see 3 items remaining on the agenda; the next one is 14:28:29 3. Grants for the Web [from tzviya] 14:28:31 zakim, next item 14:28:31 agendum 3 -- Grants for the Web -- taken up [from tzviya] 14:29:01 I have made the request to generate https://www.w3.org/2021/07/06-pwe-minutes.html Ralph 14:29:33 jeff: There's an organization called Grants for the Web, a non-profit that gives grants for proposers who would like to experiment on new approaches for web monetization 14:29:37 ... with privacy in mind 14:29:44 ... closely affiliated with Coik 14:29:45 -> https://www.grantfortheweb.org/ Grant for the Web 14:29:52 s/Coik/Coil/ 14:30:07 ... about a year ago they approached W3C 14:30:16 ... when folks are working on better web monetization 14:30:20 [Founding Collaborators: Coil, Mozilla, Creative Commons] 14:30:37 ... they would really like their grantees to do it in a way that allows the protocols to become open standards 14:30:46 ... as unpropriatary as possible 14:31:09 ... and adhere to our principles of security, accessibility etc 14:31:29 ... because of vendor neutrality, we can't advocate a position on monetizing the web 14:31:50 ... we constructed the proposal that allows us to give advice, we would be available to consult 14:32:25 ... through the lifecycle of the ecosystem, from proposal applications, judging, and that the work is developed with accessibility, i18n in mind 14:32:33 ... we published our intention to participate 14:32:40 ... it's going along pretty well 14:32:47 ... one of the aspects of the proposal 14:33:14 ... the web monetization approach is focused on diverse content creators who may not be able to monetize their content under the current model 14:33:23 ... focus on diversity, especially geographic diversity 14:33:30 ... which aligns with our goals 14:33:40 ... one of the components of the agreement 14:33:56 ... if we notice that some of their grantees are working on things that impact standardization 14:34:21 ... if these grantees are small orgs from underrepresented regions, Grant for the Web would pay for their membership 14:34:31 ... that's been going pretty well 14:34:33 s/agendum 2 -- Early draft of Disciplinary Procedures -- taken up [from tzviya]// 14:35:18 ... Grant for the Web set aside 25k for memberships 14:35:31 ... membership from lower-income regions is under 1k 14:35:43 q? 14:35:45 ... important thing is having more diverse members joining W3C 14:35:50 i/agendum 1 -- Revised ombuds job description + selection criteria and interview techniques -- taken up [from tzviya]/agendum 2 -- Early draft of Disciplinary Procedures -- taken up [from tzviya]/ 14:36:06 tzviya: That leaves us time for survey updates 14:36:08 zakim, next item 14:36:08 agendum 4 -- Survey updates -- taken up [from tzviya] 14:36:15 s/agendum 1 -- Revised ombuds job description + selection criteria and interview techniques -- taken up [from tzviya]// 14:36:21 tobie: So the initial idea was to have a survey to better understand the composition of our membership 14:36:36 ... across leadership, chairs, staff, editors 14:36:41 i/sheila: Working on the job description/agendum 1 -- Revised ombuds job description + selection criteria and interview techniques -- taken up [from tzviya]/ 14:36:45 ... OpenJS foundation is looking at the same 14:36:51 ... advised to look at 2 options 14:36:51 I have made the request to generate https://www.w3.org/2021/07/06-pwe-minutes.html Ralph 14:37:22 ... essentially because W3C has a direct relationship with everyone involved in standards, OpenJS doesn't, there's GDPR challenges 14:37:34 meeting: PWE/IDCG weekly meeting 14:37:43 ... the answer seems to be that on the OpenJS side, we can't do it and abide by GDPR 14:37:50 agenda: https://lists.w3.org/Archives/Public/public-pwe/2021Jul/0000.html 14:37:55 ... so sharing the upfront cost of sharing questions and things fall through 14:38:10 ... we'd have to do a completely different system on their side to get the same data 14:38:20 i/sheila: Working on the job description/agendum 1 -- Revised ombuds job description + selection criteria and interview techniques -- taken up [from tzviya]/ 14:38:21 ... the overall cost of one of the solutions would not be split in two 14:38:27 ... one solution is 25k/year 14:38:31 ... it's a lot 14:38:57 ... the fact that if we pursued something like that, we'd not have to pursue GDPR issues 14:39:05 ... the cheaper option, 3-4l 14:39:14 s/3-4l/3-4k/ 14:39:23 ... I want to go back to that option and explore it more 14:39:36 i/… thanks so much Sheila/agendum 2 -- Early draft of Disciplinary Procedures -- taken up [from tzviya]/ 14:39:44 tzviya: Can you clarify? 14:39:44 I have made the request to generate https://www.w3.org/2021/07/06-pwe-minutes.html Ralph 14:39:55 tobie: W3C has a direct relationship with all members and staff 14:40:05 ... it's ok for us to send a pointer to our mailing list 14:40:11 ... OpenJS doesn't have this at all 14:40:21 ... the project maintainers have this kind of relationship 14:40:31 ... and OpenJS has relationships with the projects 14:40:45 ... people don't have email relationships over email, mainly github 14:41:04 ... I couldn't get a clear idea of if extracting emails from Github would be GDPR compliant 14:41:09 i/sheila: Working on the job description/Topic: Revised ombuds job description + selection criteria and interview techniques 14:41:23 ... wanting to do things ethically made this tricky 14:41:39 i/… thanks so much Sheila/Topic: Early draft of Disciplinary Procedures/ 14:41:53 I have made the request to generate https://www.w3.org/2021/07/06-pwe-minutes.html Ralph 14:41:56 tzviya: If the main method of communication is GitHub, could posting the survey there be a method? 14:42:07 tobie: Maybe, but hard to know, might be biased 14:42:13 ... maintainers not all on board 14:42:22 ... might be biased depending on the project 14:42:40 tzviya: Sounds like the next steps would be to look into the cheaper option 14:42:51 tobie: The original set of questions are from the OpenJS 14:42:59 ... from the StackOverflow survey 14:43:00 i|https://github.com/w3c/PWETF/blob/main/CEPCdisciplinary-process.md|Topic: Early draft of Disciplinary Procedures/ 14:43:02 I have made the request to generate https://www.w3.org/2021/07/06-pwe-minutes.html Ralph 14:43:14 ... and now I have to inquire on the IP status and if we can use them 14:43:21 ... in short, more complicated 14:43:29 Question - Did we want to ask a question to Stackoverflow or Slashdata? Slashdata is survey now. 14:43:37 tzviya: Could we get an update in 2 weeks? 14:43:40 tobie: Yes 14:44:08 Barb_H: Slashdata is now just executing their survey to be available in the fall 14:44:17 ... is there any way we can influence the type of questions that get asked 14:44:24 ... that meet our needs around standards 14:44:59 ... is there any way we can ask a question to be answered in that survey 14:45:04 tobie: I haven't thought about it 14:45:12 ... the idea was more to use the same questions they're using 14:45:23 ... because they were good and had been worked on and thoughtful 14:45:41 ... and also they implicitly had a way to compare our community to the broader community 14:45:58 ... point out things that are better/worse than the general community 14:46:09 Barb_H: The way we look at it, primary vs secondary 14:46:43 ... primary, alignment with the SO questions, but I think there are secondary surveys out there where we might find some insights 14:47:08 ... the other day, the game group found a survey for game developers, asking what APIs they use 14:47:23 ... we want to know what different communities are doing 14:47:46 ... could we view or influence the secondary level of surveys 14:48:09 tzviya: The only thing that might be similar is the WebAIM user data survey 14:48:20 q+ to mention MDN survey 14:48:51 Barb_H: The gaming one was interesting, asking for APIs, what environments 14:48:51 ack tobie 14:48:51 tobie, you wanted to mention MDN survey 14:48:56 tobie: There's the MDN survey too 14:49:08 ... there's options there as well 14:49:22 ... the scope is similar 14:49:24 https://hacks.mozilla.org/2019/07/mdn-web-developer-designer-survey/ 14:49:38 tzviya: I think the MDN survey has only come out once? 14:50:29 ... we can look at different surveys and see whats out there, and Tobie's proposla 14:50:37 tobie: Will look and report back 14:50:44 Comment - Game Survey - Interesting reading - https://gamedevjs.com/survey/2021/ 14:50:46 tzviya: AOB? 14:51:02 ... thanks everyone! 14:51:18 zakim, end meeting 14:51:18 As of this point the attendees have been tzviya, Ralph, wendyreid, Sheila, Tobie, Mallory, Jeff, Judy, hober, Annette, Barbara, annette_g 14:51:20 RRSAgent, please draft minutes v2 14:51:20 I have made the request to generate https://www.w3.org/2021/07/06-pwe-minutes.html Zakim 14:51:23 I am happy to have been of service, Ralph; please remember to excuse RRSAgent. Goodbye 14:51:28 Zakim has left #pwe 14:52:40 Found the moderation resources: https://github.com/nodejs/admin/blob/main/Moderation-Policy.md 14:53:05 tzviya: ^ what's the best way to share those with the group? 14:54:38 rrsagent, bye 14:54:38 I see no action items