13:57:28 <RRSAgent> RRSAgent has joined #pwe
13:57:28 <RRSAgent> logging to https://www.w3.org/2022/07/19-pwe-irc
13:57:30 <Zakim> RRSAgent, make logs Public
13:57:31 <Zakim> Meeting: Positive Work Environment CG
13:57:45 <wendyreid> date: 2022-07-19
13:57:59 <wendyreid> chair: wendyreid, liz
14:01:09 <wseltzer> present+
14:02:28 <wendyreid> present+
14:05:47 <wseltzer> scribe+
14:06:05 <Lutgendorff> Lutgendorff has joined #pwe
14:06:07 <wseltzer> Topic: Disciplinary Process
14:06:37 <wseltzer> Liz: there's a draft
14:07:00 <wseltzer> ... this came up because WendyS suggested we package the disciplinary process with the Ombuds program
14:07:15 <wseltzer> ... to be able to cost and describe how dispute resolution should work
14:07:22 <wseltzer> q+
14:07:29 <wendyreid> scribe+
14:07:40 <wendyreid> ack wseltzer
14:07:43 <wseltzer> Judy: I thought we might be looking at whether some could be sourced from existing HR
14:09:09 <Lutgendorff> q+
14:09:16 <wendyreid> ack Lutgendorff
14:09:23 <Judy> Judy has joined #pwe
14:10:03 <wseltzer> wseltzer: when I brought the Ombuds program and budget proposal to management team, they wanted to see the overall program to see how it addresses CEPC enforcement
14:10:39 <wseltzer> Lutgendorff: also valuable to help W3C team see what is expected of them
14:10:53 <wseltzer> ... I'll email it to the list
14:11:10 <Judy> Judy has changed the topic to: 19 July PWE CG meeting in progress... https://www.w3.org/groups/cg/pwe/calendar
14:11:15 <wseltzer> several: sounds good
14:11:19 <hober> present+
14:11:23 <wseltzer> Topic: Cadence for updating CEPC
14:11:42 <wseltzer> wendyreid: there have been several editorial changes made to CEPC
14:11:51 <wseltzer> ... want to discuss cadence or triggers for CEPC update
14:12:06 <wseltzer> ... recognizing that publishing requires AC approval
14:12:08 <wseltzer> ... thoughts?
14:12:24 <cwilso> present+
14:12:27 <Judy> q+
14:12:30 <wseltzer> hober: as you identified, we don't want to go to the AC too frequently with small changes
14:12:30 <Judy> present+
14:12:56 <wseltzer> ... I'd set some threshold of normative changes: one significant or several smaller normative changes
14:12:57 <cwilso> q+ to suggest two approaches
14:13:00 <Lutgendorff> Q+
14:13:22 <Judy> q- later
14:13:31 <Judy> present+
14:13:58 <wseltzer> ... it would be nice if we could go forward with a discrete vote, just on the change
14:14:04 <wendyreid> ack cwilso
14:14:04 <Zakim> cwilso, you wanted to suggest two approaches
14:14:40 <wseltzer> cwilso: 2 ways to look at: threshold of changes, or as process does, by default, we'll update once a year
14:15:19 <wendyreid> q+
14:15:19 <wseltzer> ... hard part is knowing when to update. Probably once a year
14:15:25 <wendyreid> ack Lutgendorff
14:15:57 <wseltzer> Lutgendorff: time-based is easiest, and we can pick a schedule
14:16:18 <wseltzer> ... also helps maintain timeliness if we telegraph a regular cadence
14:16:33 <wseltzer> ... "get your changes in before this date", set expectations
14:16:59 <wseltzer> ... helps to cut through differences on what constitutes a substantive change
14:17:11 <wendyreid> ack Judy
14:17:21 <wseltzer> Judy: +1 to having a cadence
14:17:49 <wseltzer> ... we might want to phrase as, we'll evaluate on X date whethere we'll propose a rev that year
14:18:00 <wseltzer> ... conservatism on the commitment we make each year
14:18:11 <wseltzer> ... also suggest asking the Ombuds for input
14:18:24 <wseltzer> ... if they see issues that could be clearer
14:18:43 <wseltzer> ack wendyreid
14:18:44 <wendyreid> ack wendyreid
14:18:57 <wseltzer> wendyreid: I like the idea of having a time of year to review
14:19:09 <wseltzer> ... reach out to the ombuds, AC
14:20:26 <Lutgendorff> q+
14:20:35 <wendyreid> ack Lutgendorff
14:20:40 <wendyreid> q+
14:21:14 <wseltzer> Lutgendorff: normalizing as a bureaucratic process can help deescalate
14:22:13 <wseltzer> ... making it open, transparent, and more manageable
14:22:27 <wendyreid> ack wendyreid
14:22:28 <wseltzer> wendyreid: +1
14:22:48 <wseltzer> ... It should be open and systematic
14:23:44 <wseltzer> ... To summarize: we agree there should be a yearly cadence, in a time of year that's lower key
14:24:00 <wseltzer> ... with a 3-4 month window for intake, processing, and proposing revision to AC
14:24:35 <wseltzer> hober: if we avoid fall and spring AC meetings; maybe look at summer?
14:24:40 <cwilso> +1
14:25:23 <wseltzer> wendyreid: aim for July, be able to socialize the start at spring AC meeting, and the result at TPAC
14:26:02 <wseltzer> Lutgendorff: does anyone volunteer to write up the cadence
14:26:06 <wseltzer> wendyreid: I can
14:26:31 <wendyreid> https://github.com/w3c/idcg/issues
14:26:43 <wseltzer> Topic: IDCG repo
14:27:18 <wseltzer> wendyreid: there are lots of old issues there
14:28:01 <wseltzer> ... the one that stands out to me is equity review process
14:28:19 <wseltzer> ... would like to bring that for more discussion
14:28:30 <wendyreid> https://github.com/w3c/idcg/issues/14
14:28:44 <wseltzer> Judy: I didn't recall it had gotten that far
14:28:55 <wseltzer> ... lots of investigation still to do
14:32:07 <wseltzer> wendyreid: another issue, mentoring/buddy system
14:32:23 <Lutgendorff> q+
14:33:30 <wendyreid> ack Lutgendorff
14:34:01 <wseltzer> Lutgendorff: confirm it's a lot of work
14:34:34 <wseltzer> ... can we start with providing information about mentoring resources?
14:35:11 <Judy> s/lots of investigation still to do/tried investigating model ERBs when this initially came up, very hard to find examples, would need fresh investigation to see if more examples now./
14:35:43 <Judy> +1 to trying to provide DIY guidance on mentoring
14:36:23 <wseltzer> wendyreid: could we give suggestion to chairs on how to welcome new participants?
14:37:24 <wseltzer> q+
14:37:29 <wendyreid> ack wseltzer
14:38:04 <wendyreid> wseltzer: As we're all thinking towards TPAC, should we think about welcoming event or opportunity there? To the community
14:39:36 <wseltzer> wendyreid: I recall an informal pre-meeting at Lyon TPAC
14:41:03 <Judy> q+
14:41:07 <wendyreid> wseltzer: IETF has used a "dot" system in the past for people to indicate they are new
14:41:11 <wendyreid> ack Judy
14:41:49 <wseltzer> Judy: people may also be signaling their interaction preferences re COVID
14:41:59 <wseltzer> ... coordinate with events team
14:42:11 <wseltzer> hober: my daughter often wants to signal "don't see me or hear me"
14:42:26 <wseltzer> ... visibility: none
14:45:06 <Judy> q+
14:46:14 <wendyreid> ack Judy
14:46:49 <wseltzer> wendyreid: consider some pre-opening gathering, talk to events team
14:47:26 <wseltzer> wendyreid: any other issues in IDCG repo that stand out?
14:47:55 <wseltzer> Lutgendorff: or anything we can close?
14:51:20 <wseltzer> [suggested out of scope: 33, 29]
14:51:47 <wseltzer> [adjourned]
14:52:04 <wseltzer> rrsagent, draft minutes
14:52:06 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/19-pwe-minutes.html wseltzer