14:58:48 RRSAgent has joined #w3process 14:58:52 logging to https://www.w3.org/2025/02/26-w3process-irc 14:58:53 Zakim has joined #w3process 15:02:58 meeting: W3C Process CG Call 15:03:01 present+ 15:04:04 I have made the request to generate https://www.w3.org/2025/02/26-w3process-minutes.html TallTed 15:04:14 Ian has joined #w3process 15:04:57 scribe+ 15:05:21 plh: Ian put together an alternative proposal. Florian, Elika, Ian, and I had a chat about it. 15:05:39 ... Florian opened several pull requests against the Process to bring the CG draft closer to Ian's proposal. 15:06:44 ... some questions about what we want to do by when 15:06:52 ... AC meeting coming up in April, AB meeting right after 15:07:06 https://docs.google.com/document/d/1LlIuhhYknEirNVBmTR5BCZGIH3qetwO3qIQfd62UXHg/edit?tab=t.0#heading=h.qfkvt686yope -> Ian proposal 15:07:19 Topic: Update W3C mission 15:08:06 github: https://github.com/w3c/AB-public/issues/220 15:08:18 present+ 15:08:19 plh: that's at the top of the document. 15:08:43 github: https://github.com/w3c/process/issues/989 15:08:52 present+ 15:12:12 Resolved: Merge #990 and editors are welcome to future changes based on the W3C website mission statement 15:13:27 Topic: Ian's proposal on charter refinement 15:13:52 Ian: developed after concerns raised by the Team 15:14:18 ... tried to understand the goals of the CG had been and try to achieve them with a different approach 15:14:39 ... addressing ambiguity on whether the Team can or cannot start charter refinement. 15:14:56 ... my approach is more square 15:15:05 ... so it's more straightforward 15:15:28 ... it resolves some of the concerns from the Team 15:16:06 ... the real question was how to object to the team when it decided not to do things 15:16:20 ... proposal is more lightweight to handle those cases 15:16:38 ... 5 Members is an easier threshold 15:16:52 ... in the case of AC review, the bar is higher 15:17:13 ... other aspects of the intention: drive consensus 15:17:18 ... drive Member engagement 15:17:37 ... solicit viewpoints 15:18:04 ... it's now stated clearly that the Team must seek consensus and must formally address comments 15:18:26 ... it's a stronger requirement but I'm happy to make this as a middle ground 15:18:46 ... in any case, we need to put more things in the Guidebook 15:18:56 ... so the proposal comes along with a Guidebook update 15:19:07 ... that will create efficient and stability 15:19:52 q+ 15:20:18 plh: There's a difference in emphasis between the two proposals. 15:20:34 ... in CG proposal, emphasis is on the community effort on the chartering process 15:20:42 ... in Ian's proposal, emphasis is on the Team 15:20:52 ... There was a lot of pushback from Team about losing that emphasis. 15:21:03 plh: The other major question was about how decisions get made 15:21:14 ... for group decisions, need to know the group, and the current definition is quite vague 15:21:18 ... so this was seen as a problem. 15:21:29 ack florian 15:21:30 plh: These are the two main differences between the proposals. 15:22:42 florian: One more editorial difference: the CG draft is chronologically ordered, whereas Ian's draft describes the core of the phase first and then how you start it. 15:23:04 florian: Wrt how much time do we have to resolve this, I would like to add another time constraint which is more important. 15:23:14 ... I would like the AC Review of this to start before the next AB election. 15:23:33 ... Because it would be problematic if we need to re-start this discussion with a new AB. 15:23:41 (Start of next election is 1 May) 15:23:46 ... So want to finish this round of Process changes before the end of the term. 15:24:04 ... In other words, before end of June. 15:24:26 ... In terms of how we get there, I think this group will not be able to decide between two approaches, and kick some decisions up to AB. 15:24:36 [6 seats terms are ending on 30 June 2025) 15:24:49 ... We could share it as-is right now, but there's a lot of differences that are incidental. 15:25:04 ... Other thing we could do is look at all the things we can bring in line with Ian's proposal. 15:25:15 ... Meanwhile apply a Process editor's eye to Ian's proposal and see what to adjust there. 15:25:34 ... In other words bring the two together, and then comparing them will be easier. 15:26:02 ... I put together 3 small proposals to start aligning CG draft with some aspects of Ian's proposal. 15:26:23 q+ 15:26:38 ack scribeAssistant 15:27:03 scribe: taking this as-is to the AB isn't going to be useful for the AB 15:27:12 ... we need to outline the concrete differences 15:27:24 ... and bring concrete questions to the AB 15:27:58 q+ 15:27:59 ... we could work on the alignment within the CG 15:28:12 ack cwilso 15:28:21 s/scribe/anon 15:28:45 cwilso: Completely agree. We should align as much as possible, and whatever we take to AB, we need to distill down into "what's the big picture question here" 15:29:09 ... Even I'm having trouble here, and I'm relatively conversant with the Process. 15:29:34 s/Process/Process compared to most of the AB. 15:30:00 ack florian 15:30:09 TallTed: I echo cwilso and fantasai. When asking anyone to decide between X & Y, it's better to reduce unnecessary differences so it's clear what we're deciding between. 15:30:21 florian: In addition to substantive questions, there's matter of framing. 15:30:43 ... I think we can work at reducing the difference, but not to zero. Some differences are intentional. But maybe easier to talk about once we have reduced it. 15:31:00 plh: Sounds like we're all on board with reducing the differences. 15:31:06 ... Is it worth our time to go through the PRs from Florian? 15:31:17 florian: Maybe? There are 2 different kinds of PRs. One is purely editorial. 15:31:45 ... #993 is re-using phrasing from Ian's draft that could be easily re-used. 15:32:03 ... The other two are not editorial, they are relating to a different, more efficient way of Members being unhappy with Team's decisions. 15:32:15 ... When Team says "no" to starting Charter Refinement, or starting AC Review. 15:32:44 ack scribeAssistant 15:32:47 q+ 15:33:01 ack ian 15:33:23 anon: I think we should merge the editorial one, and discuss the two substantive ones and send with recommendation to the AB. 15:34:28 Subtopic: Editorial Improvements to Charter Refinement 15:34:56 github: https://github.com/w3c/process/pull/993 15:35:44 Ian: Had a chance to review, no objection in principle, haven't re-reviewed the whole thing. 15:36:15 TallTed: Reviewed yesterday, no objections. 15:36:22 RESOLVED: Merging #993. 15:36:38 Subtopic: Appeal vote as escalation for rejecting charter refinement 15:36:43 github: https://github.com/w3c/process/pull/991 15:37:00 florian: Case of AC Rep has asked for Charter Refinement, and Team said "no". 15:37:11 ... And there's a formal objection. 15:37:19 ... This kicks off Council process, which is expensive. 15:37:38 ... Ian's proposal is that if 5 people formally object, then we kick off Charter Refinement 15:37:49 ... We didn't want only 1 person to be able to derail the Team. 15:38:01 ... But if enough people do insist, we start Charter Refinement, and don't need a Council. 15:38:10 ... In Ian's text, it was 3 weeks for reaching 5 members or more. 15:38:22 ... I left as an open question. Doesn't seem urgent whether 3 or 7 or 12 weeks. 15:38:26 ... But would be a problem if 7 years later. 15:38:39 ... So as long as countable in weeks, not a rush. But wouldn't want it to be years. 15:38:43 ... But that's the idea of this PR. 15:39:07 plh: [proposes an example to think about] 15:40:27 Ian: Mistake in the explanation: need 5 FOs, but then that kicks off an AC Appeal. 15:40:36 florian: Right! That's correct. 15:40:40 florian: Sorry for the confusion. 15:41:15 Ian: Question is who do we appeal to when there's opposition to the Team Decision. 15:41:35 ... In some cases we go to Council, but in this case it's faster to go directly to Membership. 15:42:39 plh: Then we need 5% ... 15:42:48 anon: No, we just skip straight to the AC vote. 15:43:04 florian: There's a term that wasn't DFNed, so we DFNed it and skip right to the vote. 15:43:09 Ian: I much prefer this to my proposal. 15:43:38 plh: Are we happy with this PR? If yes, do we need to circulate with AB? 15:44:44 +1 ask for forgiveness, not permission 15:44:45 plh: Proposal is to Merge 991, and then fantasai and cwilso can bring to AB for their consideration. Objections? 15:44:50 RESOLVED: Merge #991 15:45:16 Subtopic: Enable resuming charter refinement after decision to abandon 15:45:21 github: https://github.com/w3c/process/pull/992 15:45:41 Ian: If Team decides after Charter Refinement not to start AC review, they need to announce, and if 5 members object we start AC Review. 15:46:15 florian: I suspect that when we are in the case of Team giving up, it might not be "group has reached consensus about the AC Review and Team hates it", but rather "group is a mess, and Team believes there's no chance of getting to a charter to present to AC" 15:46:27 ... In this case group might say "we think we can solve it with enough time" 15:46:42 ... In this case you would want to resume Charter Refinement, not kick off AC Review. 15:47:06 ... If in Charter Refinement phase, Team concludes it can't get any better, then can send to AC Review as-is. 15:47:33 Ian: [missed] 15:47:47 [Something about a 3-way decision] 15:48:00 florian: Either give up or go to AC Review, but another option is Charter Refinement continues. 15:48:15 florian: Proposal is if 5 ppl say "no you can't give up", then we resume Charter Refinement. 15:48:26 ... at the option of Facilitator/Team we decide whether to keep working or push to AC Review. 15:48:45 ... and if the Team thinks Charter Refinement is really a waste of time, they have option to kick it to the Council. 15:48:50 q? 15:49:07 plh: Should we merge or take more time to review? 15:49:37 florian: Weakness of proposal of, if Team is being obstructive, then Team can decide to continue and not work on it. 15:49:51 Ian: In my case, Team announces a duration of Refinement. They'd have to announce a new duration. 15:50:47 anon: Can object to the choice of Facilitator 15:50:55 Ian: That's a staff decision, who is Facilitating. 15:51:03 florian: That's a pre-existing aspect. 15:51:39 plh: With that in mind, do we want to merge now? 15:51:45 (Ok by me) 15:52:00 florian: Hard to manage lots of open PRs, so if we're comfortable with things then we should merge. 15:52:07 plh: Ian is ok to merge. Any objections? 15:52:16 RESOLVED: Merge #992 15:52:34 plh: Florian and Ian, can you keep working on PRs so we can keep aligning the two proposals further? 15:52:42 florian: Some time challenge, but I will work on it. 15:53:04 Ian: Thanks for the discussion and PRs, will follow up. 15:53:14 [Ian departs] 15:53:35 Topic: Timelines 15:53:47 florian: My goal is to start AC Review by end of term. 15:53:55 plh: We'll need to have wide review before that. 15:54:04 plh: I would think that... 1 month is good? 15:54:23 s/plh:/.../ 15:54:38 ... Some risk of if we get yet another proposal... 15:54:56 florian: I think it would be ideal if we can decide to start review at April AB meeting 15:55:02 ... but that might be tight. 15:55:09 plh: We need to start review by mid-May 15:55:18 plh: So we need a decision from AB before May 9h 15:55:22 s/9h/9th/ 15:55:34 florian: Can you work with AB to make sure we have slot to discuss? 15:55:36 cwilso: Sure 15:56:14 florian: Also, I'll be in the area long enough that I could join an AB session on Process 15:56:18 plh: I'll be available as well. 15:57:08 plh: Let's make sure we have the questions to the AB ready for the AB to discuss in April so we can start the reviews on time. 15:57:40 plh: I'm somewhat at-risk wrt next meeting, but decent chance I can make it. 15:58:01 Meeting closed. 15:58:05 I have made the request to generate https://www.w3.org/2025/02/26-w3process-minutes.html scribeAssistant 18:07:09 tantek has joined #w3process 18:14:00 michaelchampion has joined #w3process 18:19:17 Zakim has left #w3process 19:05:32 Brocker has joined #w3process