13:56:32 RRSAgent has joined #w3process 13:56:32 logging to https://www.w3.org/2021/10/06-w3process-irc 13:56:34 RRSAgent, make logs Public 13:56:36 Meeting: Revising W3C Process Community Group 13:56:49 present+ dsinger 13:58:56 present+ 14:01:13 plh has joined #w3process 14:05:32 jrosewell has joined #w3process 14:05:38 present+ 14:05:48 present+ 14:06:38 present+ 14:06:38 scribe+ 14:06:51 Chair David 14:06:56 Chair: David 14:07:50 jeff has joined #w3process 14:08:14 plh: Update on the FO. W3M decided to approve the process last week. Understood from the objectors that the objections will be dealt with in teh next version. But we won't hold. 14:08:30 plh; we will add the two clarifications on the documents that are subject to AC review 14:08:57 plh: Formal release will be after TPAC on Nov 2nd 14:09:11 Florian: what document would you like me to make? 14:09:35 plh: Please make a final document, with the Nov date and the status of the current official process 14:09:40 TallTed has joined #w3process 14:09:44 q? 14:09:49 Thank you. 14:10:02 present+ 14:10:06 scribe+ 14:10:38 Topic: Pull Requests 14:10:52 looking at 557 https://github.com/w3c/w3process/pull/557 14:11:28 #557 allows the CEO/team to handle Member submissions 14:11:54 florian: separate questions on what to do to appeal, we'll deal with that later 14:11:59 present+ 14:12:02 q? 14:12:18 Resolved: Merge #557 14:12:30 https://github.com/w3c/w3process/pull/558 14:12:31 Next #558 Disciplnary auth https://github.com/w3c/w3process/pull/558 14:12:50 florian: moving disciplinary authority from the Director to the CEO 14:12:55 q? 14:13:04 Resolved: Merge #558 14:13:26 https://github.com/w3c/w3process/pull/559 14:13:30 Next #559 a grab-bag https://github.com/w3c/w3process/pull/559 14:14:12 Florian: moving participation from the Director to the CEO 14:14:27 q+ 14:14:55 David: Member, Group chairs, Participants 14:15:06 ... we never used that participants in the past 14:15:15 David: Invited Experts 14:15:46 ... including disagreement between Chairs and Team Contacts 14:16:01 ack cw 14:16:03 ack cw 14:16:19 Chris: bit concerned about appointing and reappointing Chairs 14:16:24 ... it's a hot topic lately 14:16:38 ... Chair appointment have been contentious 14:16:53 ... moving that to the team may create frustrations 14:17:03 Florian: initial decision and recourse 14:17:11 q? 14:17:13 ... team is the right one to make the initial decision 14:17:15 q+ 14:17:17 s/initial/two parts to this: initial/ 14:17:52 ... but if you disagree, we have an open issue about this. lack of clarity if you can formally object or not 14:17:56 q+ 14:18:22 ... you can reach out to the team before making a formal objection 14:18:27 Indeed we have https://github.com/w3c/w3process/issues/281 objecting to chair appointments #281 14:18:46 chris: concerns that it doesn't put pressure on the team to negotiate that ahead of time 14:18:49 q? 14:18:49 q+ 14:19:00 q+ 14:19:02 ... I don't have a clear answer, just concerned 14:19:22 david: we have an open issue indeed 14:19:41 https://github.com/w3c/w3process/issues/281 14:19:47 scribe+ 14:19:48 ... it's also about documenting current practices 14:20:07 dsinger: ... 14:20:19 plh: Believe we should have a process that's easy in the straightforward cases 14:20:24 plh: and have recourse if things go wrong 14:20:31 plh: I like Florian's proposal 14:20:48 plh: Right now if chair wants to step down, we refuse until they give us an alternative person, e.g 14:20:59 plh: We do rely more and more on the participants of the WG to decide the group 14:21:03 plh: so it's done very cooperatively 14:21:24 plh: I'm surprised to hear we don't have a way to formally object 14:21:34 plh: for initial groups, we don't always have names at the start 14:21:42 plh: but we try to put names of chairs in the charter 14:21:49 q? 14:21:49 plh: I don't remember AC review opposing chairs 14:21:51 ack ds 14:21:54 ack plh 14:21:55 plh: but there have indeed been tricky cases in the past 14:22:19 jeff: On this particular PR I agree with Florian and plh 14:22:23 jeff: on this particular pull request, I concur 14:22:31 jeff: But cwilso is raising a larger issue I'm concerned about 14:22:31 ... chris is raising a larger issue however 14:22:41 jeff: There are a lot of things the Team's been doing under the Director's delegation for a long time 14:22:49 jeff: I'm not sure we've systematically thought through how we want all those to land 14:22:55 jeff: I'm not sure going through issue by issue isthe right approach 14:23:16 jeff: Example that sits in my mind is typically if a WG wants to take a document to PR, that's a Director decision 14:23:22 jeff: Ralph makes that on behalf of the Director 14:23:37 jeff: He checks a bunch of things about the document to make sure it's done properly 14:23:48 jeff: That transition is done on behalf of the Director by the Team 14:23:57 jeff: If not Director, who makes that decision? 14:24:04 jeff: Doubt Council will do it 14:24:11 q+ dsinger 14:24:14 jeff: If no check, then have to just trust the WG 14:24:24 jeff: Need to think through the whole flow ... 14:24:35 jeff: I know today was supposed to do the "easy" ones, but we need a systematic approach 14:24:46 florian: The one Jeff raised is on my radar 14:24:49 ack flo 14:24:52 q- 14:24:53 ack je 14:24:54 florian: I have a different answer than here 14:25:09 florian: I do think we should go piece by piece, because if we wait until we agree on everything to do anything, we are not going to make progress 14:25:22 florian: Right now, aligning the Process with what we do today 14:25:31 florian: and where we are uneasy about it, raise issues and work on them 14:25:43 q? 14:25:45 florian: For the other issue, I am preparing a PR for that also 14:26:04 florian: But cwilso, would you be comfortable landing this now and addressing conflicts later? 14:26:09 cwilso: Not going to block 14:26:19 cwilso: Just want to bring up that this needs to be addressed 14:26:22 cwilso: It's increasingly a problem 14:26:33 cwilso: Lots of concerns wrt bias in chairing 14:26:53 cwilso: In the past, in retrospect, are we going to formally object to the appointment of a chair? 14:26:59 cwilso: that's an elephant gun solution 14:27:28 q+ 14:27:29 q+ 14:27:30 cwilso: but also Team swapping chairs, with first notice being opportunity to object, is not great 14:27:37 cwilso: Should make it possible to fix before getting to FO 14:27:59 q? 14:28:03 ack weil 14:28:03 cwilso: So no objection to merging, but do want to fix the larger problem 14:28:25 weiler: I'm very sympathetic to the issue 14:28:33 weiler: of "wait, first we heard about this, it's a done deal" 14:28:40 weiler: I'm trying to work out though from a management standpoint 14:28:45 weiler: if a chair appointment gets objected to 14:29:01 weiler: if plh is in situation of "need to appoint a chair, because down to zero chairs" 14:29:07 weiler: a slow-track process is going to be very painful 14:29:19 weiler: can we meet your concern without stop-energy black hole 14:29:21 q? 14:29:43 florian: Briefly, my proposal is not to introduce the ability to FO, but understand that the Process currently allow this 14:29:45 ack plh 14:30:20 plh: Reminds me, how do we make changes to charters after AC review and before approval 14:30:33 plh: We make changes, but there was complaints that no review of those changes 14:30:43 plh: We didn't start by changing Process, but updating guidebook for the Team 14:30:56 plh: requiring Team to circulate proposal to those who responded 14:31:08 plh: We're not saying Team cannot make initial decision, but document how it's done 14:31:25 plh: How to balance that with not having a chair for a long time... 14:31:31 plh: But the guidebook can be more precise 14:31:35 IMO in a consensus driven organization then appointing chairs that are capable of gaining consensus seems pretty fundamental and therefore the working group's purpose would be in question if chairs can't be agreed. 14:31:38 ack ds 14:31:49 dsinger: My conclusion is we should pull this PR to document reality 14:31:57 dsinger: comment in 281 or file a new issue if needed 14:32:01 q+ 14:32:10 dsinger: I think an FO is in-your-face and rather too public about questions about a perosn 14:32:20 dsinger: I think we might need a way for e.g. AB to mediate in camera 14:32:37 dsinger: In most cases, Team only has a candidate 14:32:46 dsinger: if more candidates, maybe should hold votes 14:33:06 dsinger: I'm unsure about Team handling cases where there are conflicting visions for chairing the WG 14:33:24 cwilso: I think 281 is about objecting to appointments 14:33:33 cwilso: Should I open a new WG about figuring out better process? 14:34:08 cwilso: Maybe we should change the title of the issue? 14:34:14 dsinger: Yes, let's do that, keeps all the discussion in one place 14:34:30 q? 14:34:34 ack cw 14:34:36 ack cwi 14:35:01 "With the input of the AB, the Team appoints the Chair" 14:35:01 q+ 14:35:08 fantasai: Maybe we should say the same for this appointment? 14:35:09 ack fant 14:35:13 ack wei 14:35:25 fantasai: "With the input of the WG members" 14:35:38 weiler: Want to urge caution about soliciting input 14:35:42 weiler: in a public way 14:35:55 weiler: I've done this for WG and it's a good change 14:36:01 weiler: but requiring it could have some bad impacts 14:36:08 weiler: and ability to select the best people 14:36:31 dsinger: I will note that in ???, an indicative vote is held 14:36:35 dsinger: and ???? 14:36:50 dsinger: And in general there's widespread approval and the executive board signs off 14:36:51 s/???/INCITS/ 14:37:31 RESOLVED: Land PR #559, continue discussing chair appointments in 281 14:37:35 Incidentally, I put a comment in 281 with a suggested title change - I don't have privileges to change the title myself. 14:37:48 florian: Last topic is MOUs 14:38:10 florian: Currently the person in charge of negotiating and signing is the Director 14:38:13 https://github.com/w3c/w3process/pull/556 14:38:14 florian: This PR changes it to the CEO 14:38:24 florian: Implicitly under the supervision of the Board of Directors once we have one 14:38:26 q+ 14:38:34 ack jef 14:38:56 https://github.com/w3c/w3process/pull/556 14:39:05 jeff: This PR is fine but 14:39:16 jeff: We have in our history one MOU which assigns directly specific responsibilities to the Director 14:39:20 jeff: which is the WHATWG-W3C MOU 14:39:34 jeff: I doubt that this PR is trying to assign those responsibilities in that MOU to the CEO 14:39:37 jeff: and would be a mistake to do so 14:39:43 jeff: but if we're moving forward with this PR 14:39:46 q+ 14:39:52 jeff: need to document somewhere that we have this other open issue 14:39:55 q+ 14:40:08 jeff: Maybe say in the PR, that this is strictly about approving new MOUs, and not assigning Director role in any existing MOU 14:40:22 dsinger: Can you file an issue that we have an existing MOU that mentions the Director? 14:40:24 --> https://www.w3.org/2019/04/WHATWG-W3C-MOU.html WHATWG/W3C MoU 14:40:29 dsinger: I think it's more of an AB issue than Process CG 14:40:33 jeff: Unsure how tracking 14:40:57 jeff: But Florian and I identified all the Director's responsibilities so we can address them, and this was included 14:41:09 jeff: Just as long as we're talking about MOUs, just wanted to raise it 14:41:30 dsinger: I put a comment in the PR that tis is only about negotiation, not about contents of MOU 14:41:48 q? 14:41:48 dsinger: but good point, we should follow up on that MOU 14:41:57 ack plh 14:42:02 plh: it does mean that we're going to have to review all our official documents 14:42:09 plh: and map from W3C Director to new process 14:42:12 WHATWG, W3C MoU that was mentioned above --> https://www.w3.org/2019/04/WHATWG-W3C-MOU.html 14:42:25 plh: You're right in the case of the WHATWG case we will need to replace Director with the Council 14:42:38 plh: but each situation is different, so we will have to evaluate one by one 14:42:58 q? 14:43:18 jeff: I'll open in AB-memberonly? 14:43:28 cwilso: Yes, we need to track all of these and figure out how to edit those agreements 14:43:30 ack flo 14:43:52 florian: Just want to agree that this PR does not assign role of Director in MOU. It will be the CEO's responsibility to negotiate the update. 14:44:11 florian: and CEO should probably do that with advice of AB and the party we're negotiating with 14:44:26 q? 14:44:27 RESOLVED: Merge PR #556 14:45:06 dsinger: Please comment on issues and help us make progress 14:45:12 florian: Once we land these, btw, some of the issues will be closed 14:45:28 florian: I have another batch of PRs in preparation, but they are more tangled and more complicated than these 14:45:47 wseltzer has joined #w3process 14:45:47 dsinger: Yes, and we'll have to evaluate the overall balance as well 14:46:21 dsinger: [discussion of issue management] 14:46:22 present+ 14:46:34 rrsagent, pointer? 14:46:34 See https://www.w3.org/2021/10/06-w3process-irc#T14-46-34 14:46:36 dsinger: I wonder if we can close without action "Clearer wording for transition to obsolete status" 14:46:50 dsinger: It's been open since 2020, and we've asked repeatedly for text and haven't got it 14:46:56 dsinger: any objection to simply closing this issue? 14:47:07 florian: We said we'd soon close it in July 2019 ... 14:47:13 dsinger: It's editorial 14:47:17 q? 14:47:25 florian: and if someone comes up with something they can always open a PR 14:47:32 RESOVLED: Close that issue (whatever it was) 14:47:42 s/RESOVLED/RESOLVED/ 14:47:43 q+ 14:47:49 dsinger: Next issue is horizontal review 14:47:56 dsinger: we have this documented now in /Guide 14:48:02 q? 14:48:04 dsinger: shall we close? 14:48:06 ack jef 14:48:21 jeff: I agree that we've effectively made it mandatory 14:48:33 jeff: wide review is mandatory, and HR is part of that 14:48:36 jeff: that works today in P2021 14:48:48 jeff: but mindful of what I said earlier: who is doing the checking in Director-free? 14:49:07 jeff: Today, Ralph acting as Director, interrogates the Team or Chair or whoever to make sure this was done 14:49:35 jeff: Who's doing this stuff? Unless someone's checking, mandate doesn't mean anything 14:49:44 1+ 14:49:46 q+ 14:49:51 s/1+// 14:49:56 I think that the team is the right place to be checking that mandates are obeyed 14:49:57 jeff: Closing this is fine, but I'm concerned closing all the reminders of things that we need to address 14:49:59 q? 14:50:14 dsinger: [comment above] 14:50:28 q+ 14:50:30 ack fant 14:50:51 dsinger: If there something we didn't address, please open a new issue. 14:50:54 ack wei 14:50:58 weiler: If we're talking about #394? 14:50:59 ack flo 14:51:00 dsinger: yes 14:51:02 weiler: fine with closing 14:51:07 florian: also fine with closing 14:51:21 florian: also agree that Team being in the business of checking is right 14:51:31 florian: especially since these are initiated not by the Team, for them to check is fine 14:51:40 florian: This is a part that I'm not that worried about the Director stepping away 14:51:47 florian: ... 14:51:53 q+ 14:52:11 ack jrose 14:52:28 RESOLVED: Close #394 14:53:00 Topic: Scheduling 14:53:18 dsinger: I'll be away on Oct 27th, prefer not to chair 14:53:22 jeff: It's also during TPAC 14:53:28 q? 14:53:33 dsinger: So for both those reasons, I think we should cancel 14:53:39 RESOLVED: Cancel Oct 27th meeting 14:54:04 dsinger: Meeting after that would be the 10th of November 14:54:19 dsinger: Any other business? 14:54:20 q? 14:54:20 q+ 14:54:23 Should we cancel 14:54:53 jrosewell: next meeting after that is the 24th of November, should we cancel that because right before Thanksgiving? 14:54:54 q? 14:54:56 dsinger: yes 14:54:59 Meeting closed. 14:55:00 ack jrose 15:14:19 rrsagent, draft minutes 15:14:19 I have made the request to generate https://www.w3.org/2021/10/06-w3process-minutes.html wseltzer 15:55:15 tantek has joined #w3process 18:09:02 Zakim has left #w3process 18:48:50 MacTed has joined #w3process 18:55:01 tantek has joined #w3process 22:07:19 plh_ has joined #w3process 22:31:04 tantek has joined #w3process 23:59:09 jeff has joined #w3process