13:59:35 RRSAgent has joined #w3process 13:59:35 logging to https://www.w3.org/2020/08/26-w3process-irc 13:59:36 RRSAgent, make logs Public 13:59:37 Meeting: Revising W3C Process Community Group 13:59:37 zakim, start meeting 13:59:37 RRSAgent, make logs Public 13:59:39 Meeting: Revising W3C Process Community Group 13:59:44 present+ 14:00:00 present+ 14:00:11 present+ florian 14:00:26 present+ 14:00:57 present+ 14:01:32 koalie has joined #w3process 14:02:12 scribenick: wseltzer 14:02:18 dsinger_: state of P2020 14:02:27 ... anything we need to know, do? 14:02:33 present+ 14:02:38 jeff: we're moving forward 14:02:43 plh has joined #w3process 14:02:52 florian: we have a published ref to reference 14:02:56 jrosewell has joined #w3process 14:03:05 present+ 14:03:14 present+ 14:03:49 present+ Coralie 14:04:10 plh: are you continuig to make edits? 14:04:20 ... since I took a snapshot 14:04:20 https://github.com/w3c/w3process/commit/1a983931903e79981a4bffc0f7738f80cbdc1d35#diff-ec9cfa5f3f35ec1f84feb2e59686c34d 14:05:13 dsinger_: agenda-bash? 14:05:24 [crickets] 14:05:43 Topic: 4) Issues and PRs tagged agenda+. 14:05:53 dsinger_: 4.1) Discipline; we were working on the text at the last meeting 14:06:00 https://github.com/w3c/w3process/pull/432 14:07:12 florian: there was sugestion that insertion could be confusing in context 14:07:22 ... that was from fantasai, and we haven't heard from her 14:07:41 ... a new, publicly available document regarding discipline 14:07:48 ... from Coralie 14:08:02 https://www.w3.org/Guide/process/banning.html 14:08:13 koalie: W3M has developed guidance on procedures for removing individuals from groups in rare instances 14:08:21 ... ^ guidebook resource 14:08:48 ... we'll announce it to members and chairs 14:08:54 q? 14:09:23 florian: sounds ok to me 14:09:35 q+ 14:09:46 ... if Process delegates to Director, and this is how director will act 14:09:54 plh: goal to document 14:10:24 dsinger_: should we link to these guidelines, and Process text 14:10:30 ack ds 14:10:31 ... re guidelines... 14:10:33 florian: I support 14:10:38 dsinger_: mostly supportive 14:11:24 ... but is it CEPC-specific 14:11:40 plh: it doesn't say CEPC 14:11:50 florian: might be a question for AB review 14:11:55 s/say/restrict to/ 14:12:00 dsinger_: consensus here that this doc is good enough to link to? 14:12:04 ... any objections? 14:12:19 ... hearing silence, link it. 14:12:21 ... thanks koalie 14:12:30 plh: I'll link from /guide as well 14:12:44 koalie++ 14:13:04 dsinger_: is the glitch solved? 14:13:19 florian: works for me, but I wasn't the one who raised the issue 14:13:50 q? 14:13:52 dsinger_: fine to leave for next week 14:13:58 s/week/meeting/ 14:14:05 dsinger_: will we address 312 at the same time? 14:14:11 q+ 14:14:42 jeff: 312 introduces additional topics for Director-free 14:14:49 https://github.com/w3c/w3process/issues/312 14:14:50 q- 14:14:54 fantasai has joined #w3process 14:14:58 ... so leave it for the AB project 14:15:09 q+ 14:15:18 florian: note in 312 that it's partially addressed by this PR 14:15:30 q- 14:16:03 present+ 14:17:24 dsinger_: propose we continue offline 14:17:52 dsinger_: 428 14:17:56 [coralie departs] 14:17:58 ... plh, you wanted to keep it open 14:18:12 florian: I updated 14:18:20 koalie has left #w3process 14:18:23 ... note re no way to update Rec normatively 14:18:50 ... ambiguity wrt whether team can/can't make proposed corrections 14:18:58 ... as it's class 2, clarify they can 14:19:27 plh: need to review 14:19:40 dsinger_: First meetings, 434 14:19:58 florian: we had a discussion and resolution in the AB 14:20:14 ... we have a requirement for 8 weeks between announcement and meeting 14:20:19 ... for physical meeting 14:20:56 q+ 14:21:23 ... but under current process, you could have a proposed charter, and meet sooner than 8weeks after approval 14:21:57 q? 14:22:42 q- 14:22:47 q+ 14:23:18 q+ 14:23:26 ack plh 14:23:52 wseltzer: this seemed to me overly constraining, especially when groups are just resolving minor wording issues in charters 14:24:07 ... and they plan toward a pre-existing meeting, such as TPAC 14:24:14 ... I haven't seen AB resolution 14:24:30 plh: so are you saying groups under discussion now can't plan for TPAC 14:24:40 florian: this year, not a problem with virtual 14:24:45 q+ 14:25:01 ... but saying you can't make plans before the group exists 14:25:23 q? 14:25:29 ack weil 14:25:40 q+ to talk about getting approvals to join 14:25:49 weiler: when I think about how specs are being incubated, can imagine a CG sayig 14:26:01 ... "we want to have a meeting" whether as a CG or WG 14:26:24 ... does this mean they can't meet if thinking about chartering? 14:26:31 florian: you can't meet as formal WG meeting 14:26:54 dsinger_: you can have a CG meeting, not one making WG decisions 14:27:31 q+ to mention that decisions are async nowadays 14:27:48 q? 14:27:50 dsinger_: e.g. decision to take up a new WD 14:27:51 ack jef 14:28:04 aren't these examples of issues for the chair(s) of the group to be empowered to decide upon? If the chair makes a decision that the members of the group disagree with can't they address that via another route? 14:28:12 jeff: sounds as though this conversation supports informal meeting at TPAC 14:28:26 weiler: what is a WD decision? What sort of decisions could/should an incubator group not make? 14:28:33 ... but the text says "informal meetings should not be planned to get around this restriction" 14:28:52 ... maybe remove that text from PR? 14:29:21 q? 14:29:23 florian: the AB had said no exception for TPAC, because some peoople don't travel to all TPACs 14:29:44 jeff: I thought I was hearing agreement here that groups could meet informally 14:29:57 florian: no, I'm not agreeing that 14:30:24 q+ 14:30:50 ... disagree with setting social pressures that start the group informally and then make others come in later to object 14:31:13 q?> 14:31:17 ack ds 14:31:17 dsinger_, you wanted to talk about getting approvals to join 14:31:19 plh: but it's too easy to evade that restriction, just pick another name 14:31:54 ack plh 14:31:54 plh, you wanted to mention that decisions are async nowadays 14:32:00 dsinger_: speaking from personal experience, I can't get formal approval to join a group before its charter is finalized; can't start internal approval process 14:32:04 ... and that takes time 14:32:25 plh: that's why we earlier set the time from the time the charter was sent for review 14:33:09 ... also, all of our decisions are now taken asynchronously, confirmed offline 14:33:29 q? 14:33:35 florian: but social pressures not to go against consensus, or not object and make us change travel plans 14:33:36 q? 14:33:36 q+ to discuss "really hard to go against the pre-agreed consensus" 14:33:37 ack fanta 14:34:09 fantasai: not sure how much practical distinction between formal and infrmal meetings 14:34:22 ... also exception if all participants agree, right? 14:34:32 ... that should still be allowed 14:34:33 q+ 14:34:34 q? 14:34:39 ack wei 14:34:40 q+ re ordering of exception, rule 14:35:12 weiler: fantasai seems to capture my sense of pre-existing group wanting to meet 14:35:32 that have not yet been chartered," 14:35:37 ... florian, are you describing a case where people would want to participate in WG but have been avoiding prior incubation? 14:37:57 q? 14:39:08 ack jeff 14:39:08 jeff, you wanted to discuss "really hard to go against the pre-agreed consensus" 14:39:43 q- 14:40:48 jeff: I think the description of social pressure is not fully aligned 14:41:02 ... there are also long-term incubations 14:41:28 ... and remote participation is now usually possible for those who can't arrange travel 14:41:32 q? 14:41:48 ... we shouldn't block those who are available from meeting 14:42:02 +1 to David's suggestion 14:42:10 dsinger_: maybe we should say that short-scheduled meetings should be open, not restricted to those in the WG 14:42:14 plh: +1 to that 14:42:25 dsinger_: think we need to consider how to bring to AB 14:42:44 q? 14:42:52 [I added my comments in https://github.com/frivoal/w3process/commit/68ace68304045c3e59ec624b1e8f97f1635e42f1 ] 14:42:58 dsinger_: discontinued 14:43:25 ... suggest addition to the Status indicating why discontinued 14:43:50 q+ 14:43:52 florian: alternative, not create a new term, and just describe in status 14:43:59 ack plh 14:44:10 plh: today, we can mark doc retired 14:44:33 ... obsolete, superceded, rescinded, so they disappear from default /TR view 14:44:38 ... and also docs that become WG notes 14:45:01 ... from publishing perspective, we should ask those publishing the docs to describe their publications 14:45:36 florian: this issue triggered by someone confused about what the status section means 14:46:07 dsinger_: look at the issue. 14:46:28 florian: if we add the sentence, then use "discontinued" consistently 14:47:01 dsinger_: fine to uise the definition, without the word, too 14:47:30 dsinger_: substantive changes to charter 14:47:36 Topic: Substantive changes to charter 14:47:45 ... ready to go? 14:47:47 github: https://github.com/w3c/w3process/issues/28 14:48:18 florian: still have some concern 14:48:50 q+ 14:48:55 q+ 14:49:01 q- 14:49:12 ... when a charter is substantively changed director must seek re-review 14:49:31 rrsagent, generate minutes v2 14:49:31 I have made the request to generate https://www.w3.org/2020/08/26-w3process-minutes.html plh 14:49:58 jeff: I said essentially, it's a judgment call 14:50:13 ... if we don't want to leave it there, requires an enumeratioin of all cases, which is quite difficult 14:50:31 ... dsinger_'s approach enumerated examples, but not claiming to be a comprehensive list 14:50:38 q? 14:50:39 +! 14:50:41 ack jef 14:50:41 +1 14:51:15 florian: if the Director can make changes without telling anyone, we need to know what those cases are 14:51:30 ... maybe in all cases, Dir must announce 14:51:49 q+ 14:51:50 ... and then it's okay to have more leeway 14:52:23 ... Dir must document rationale 14:52:59 q? 14:53:02 https://www.w3.org/Guide/process/charter.html#managing-changes 14:53:04 ack jrose 14:53:13 ^ Guide on managing changes to charters 14:53:40 jrosewell: should we focus on processes for Director-free future instead? 14:53:47 jrosewell++ for optimism 14:54:00 dsinger_: we're trying not to introduce new Diretor instances 14:54:13 q? 14:54:16 jrosewell: we could park things as not making it worse 14:54:23 florian: this is still open in Director-free 14:54:30 ... Formal Objections go to the Council 14:54:46 ... we haven't yet resolved whether they can only say yes/no, or make changes 14:54:48 ... we could pund 14:55:00 s/pund/punt/ 14:55:13 Topic: P2021 milestone 14:55:25 dsinger_: please look at the milestone ^ 14:55:46 ... Registries, I'm working to simplify what Florian and Fantasai wrote 14:55:50 ... hope to have for next meeting 14:56:05 q? 14:56:06 ... please share input. 14:56:48 florian: can we look at 438, editorial PR? 14:57:32 https://github.com/w3c/w3process/pull/438 14:57:47 introduces new terms for future reference from Dir-free 14:59:21 fantasai: +1 to the PR, with Chaals's revision 14:59:29 +1 14:59:51 q? 15:00:05 jeff: think we need substantially shorter note 15:00:53 fantasai: take PRs on the note. it derived from substantial discussion 15:01:02 jeff: can't approve without reviewing 15:02:00 chaals's suggestion for shortening was not the not, it was just removing some words earlier in the PR. 15:02:06 s/not the not/not the note/ 15:02:23 dsinger_: net meeting 9 Sept 15:05:21 next meeting sept 16th! 16:47:38 tantek has joined #w3process 17:07:03 jeff has joined #w3process 17:10:00 Zakim has left #w3process