14:57:32 RRSAgent has joined #w3process 14:57:32 logging to https://www.w3.org/2021/11/10-w3process-irc 14:57:34 RRSAgent, make logs Public 14:57:36 Meeting: Revising W3C Process Community Group 14:58:46 dsinger has joined #w3process 14:58:52 TallTed has joined #w3process 14:59:21 zakim, start meeting 14:59:21 RRSAgent, make logs Public 14:59:22 Meeting: Revising W3C Process Community Group 14:59:34 present+ dsinger 15:00:53 present+ 15:01:16 plh has joined #w3process 15:01:21 present+ 15:01:29 rrsagent, generate minutes v2 15:01:29 I have made the request to generate https://www.w3.org/2021/11/10-w3process-minutes.html plh 15:02:57 present+ 15:03:04 present+ 15:03:33 present+ 15:04:12 jrosewell has joined #w3process 15:04:16 present+ 15:04:39 scribe+ 15:04:43 TallTed has changed the topic to: Nov 10th event at https://www.w3.org/events/meetings/89dd2215-93d3-4af8-971c-931529bc227d/20211110T070000#general -- Agenda https://lists.w3.org/Archives/Public/public-w3process/2021Nov/0002.html 15:05:00 David: Topic agenda bashing 15:05:24 David: I see no requests 15:05:37 Topic: Triage meeting with James 15:05:45 Thank you 15:05:47 David: Florian, James, and I had a very productive meeting 15:05:58 ... moving a bunch of issues around 15:06:02 ... PLH can you help? 15:06:10 PLH: I did not see the email, but I can help 15:06:19 David: I will refine the email. 15:06:51 Topic: Process 2022 15:07:03 David: Need to make progress on substance 15:07:12 Subtopic: Director-free pulls 15:07:22 Florian: I don't know if they are easy or hard 15:07:28 ... textually rather small 15:07:43 (Pull requests #585 and #586) 15:07:50 ... acknowledging that the Team is doing what the Director is assigned to do 15:08:02 ... maybe it should be different, but this is how it is happening. 15:08:13 ... for #586, it is fine that the team does it. 15:08:17 https://github.com/w3c/w3process/pull/586 15:08:24 ... transition requests along TR 15:08:34 ... criteria are vague, but the team cannot go wrong alone. 15:08:40 ... members need to request something 15:08:45 ... team cannot go rogue 15:08:59 q+ 15:09:04 ... if team is inappropriate, the team issues a decision which can be formally objected to 15:09:07 difference between judge and following rules 15:09:14 ... criteria are vague 15:09:24 ... but there is recourse 15:09:38 ... to make criteria less vague is a good topic, but it can be a separate topic. 15:09:43 q+ to ask about the first set 15:09:47 ack jr 15:10:00 James: Not sure what these areas are 15:10:06 ... for administrative matter it is OK 15:10:16 Florian: In this case, some judgment is required 15:10:37 ... the Director (or Team) must decide if sufficient implementation experience exists 15:10:49 ... the team could misjudge because no agreement on what the terms mean 15:10:56 ... but the team cannot move forward 15:11:09 ... if the team makes a mistake, that decision can be appealed. 15:11:27 ... until we improve the criteria the team can do it 15:11:39 James: Take DIDs for example 15:11:44 ... a great deal of discussion 15:11:52 ... wide set of opinions 15:11:59 ... don't know if it is relevant 15:12:10 q+ to ask about "Team" mechanics 15:12:16 ... only the highest level of judgment can be made about its suitability 15:12:38 Florian: In this case, the team made the judgment and then we go into debate and escalations 15:12:52 ... all we are changing is to say it is the Team; not the Director 15:13:00 James: Is the team comfortable with this? 15:13:06 q+ to address James' question 15:13:27 ... would like to hear from Wendy or Jeff 15:13:44 David: We should focus on normative changes 15:13:50 ack jeff 15:13:50 jeff, you wanted to address James' question 15:13:59 scribe+ 15:14:18 jeff: the way it works today, the authority sits with the Director, who has delegated to the Team 15:14:29 ...the Director is still available to consult, which does happen 15:15:10 ...I've never heard the Team being uncomfortable with this task; even if were to formally move to the Team, I suspect they could still consult the Director 15:15:16 ...if that would help streamline the process. 15:15:18 ack cwil 15:15:18 cwilso, you wanted to ask about "Team" mechanics 15:15:32 Chris: My only concern is that it is not clear what Team approval means. 15:15:39 ... the team is a large team. 15:15:44 q+ to respond to chris 15:15:58 ... is this a guantlet that needs to be run. 15:16:06 q+ to comment on Chris' question 15:16:13 ack flo 15:16:13 florian, you wanted to respond to chris 15:16:23 Florian: We have tackled that question in the process 15:16:29 ... we define a Team Decision 15:16:35 s/guantlet/gauntlet 15:16:46 ... they derive from Director and CEO authority even when carried out by other members of the Team 15:16:59 ... does not need to be done by a single person or 15 people 15:17:03 ... up to the CEO 15:17:11 ... roughly CEO decision = Team decision 15:17:17 ... but matter of emphasis 15:17:29 ... discipline is called out as CEO since it needs to be CEO 15:17:38 q? 15:17:41 ... matters that are for the team at large are highlighted as team decisions 15:17:43 ack dsi 15:17:43 dsinger, you wanted to ask about the first set 15:17:59 David: Looking at who "considers" 15:18:11 q+ to say CEO != Team 15:18:21 ... but to "advance" you MUST obtain team approval 15:18:42 ... similar other cases for exceptions 15:19:01 q+ to comment on P2022 v future processes 15:19:15 Florian: These are decisions which could be objected to 15:19:33 David: I get slightly uncomfortable about Team approval 15:20:00 Florian: Would you be more comfortable if we made it explicit that you can formally object to it 15:20:08 David: 99% of the time it is routine 15:20:15 ... and the team is right 15:20:24 ... I am anxious about the controversial cases 15:20:31 ... make it clear that there is recourse 15:20:38 Florian: A clarification would be nice 15:20:48 ... but the process says Decisions can be objected to 15:21:03 q? 15:21:03 ... if we start singling them out, what are we saying about other decisions? 15:21:04 q+ 15:21:06 q+ 15:21:08 ack jeff 15:21:08 jeff, you wanted to comment on Chris' question and to comment on P2022 v future processes 15:21:09 David: Just an anxiety 15:21:21 scribe+ 15:21:38 jeff: two comments: ? was asked, how are transitions handled today 15:22:01 ...as a practical matter, handling the transitions is almost entirely in the hands of Ralph 15:22:05 this bit of anxiety is a natural hazard of trimming redundant phrases wherever possible (e.g., not stating on *every* decision that it may be appealed, but saying once that all decisions may be appealed) 15:22:29 ...he consults with other Team members, most often PLH... in complex cases, he relies on others in the management team. 15:22:35 ...he may consult with Tim as well. 15:23:28 ...I also wanted to address David's well-anchored anxiety about the decision power resting in the Team. 15:23:52 ...but I think we're trying to take the least controversial things and make them reflect reality. 15:24:28 ...I would encourage we keep open an existing issue in any case. 15:24:39 q? 15:24:40 ...we should continue to have this on our radar screen. 15:24:42 David: OK 15:24:43 ack cwilso 15:24:43 cwilso, you wanted to say CEO != Team 15:25:03 Chris: Much of my concern is having been through many processes for feature approval 15:25:08 ... day job in Chrome 15:25:19 ... obtaining approval cannot be objected to if you don't get it 15:25:31 q+ 15:25:33 ... as a WG Chair, how do I obtain team approval? 15:25:43 ... team contact? PLH? Ralph? Wendy? 15:25:48 ... can any of them object? 15:25:53 How do I do this from a WG. 15:26:27 ... seems more nebulous with this change 15:26:38 ack plh 15:26:43 David: What state am I in if I have not gotten approval yet? 15:26:48 https://github.com/w3c/transitions/issues/new/choose 15:26:54 q+ to comment that the nebulous state already exists 15:27:05 PLH: Approvals are recorded in a GH repository 15:27:12 what state am I in if neither approval nor disapproval have been received? what do I do? 15:27:25 q+ re timeout 15:27:33 ... that should handle approvals for our three tracks 15:27:34 q- 15:27:51 ... to complicate a bit, I will change the workmode of repository 15:28:06 ... before for "Director" approval; now for "Team" approval 15:28:22 ... sometimes the groups don't make a request 15:28:30 q? 15:28:30 ... but the team checks compliance and we are done 15:28:45 ... yesterday I need to pushback because some changes were substantive 15:28:55 ... went beyond normal pubrules 15:29:02 ... but didn't need team approval 15:29:05 ... something in between 15:29:15 ... if there are disagreements, need to be escalated to the council 15:29:24 q? 15:29:31 ack jrose 15:29:40 David: I would like to move on soon to shape the questions 15:30:00 James: Issues are about accountability, responsibility, need to be informed 15:30:05 ... today delegated authority 15:30:10 ... administrative rules 15:30:14 ... judgment 15:30:22 ... we will see similar points in other areas of the document 15:30:37 ... are we better served by replacing sentences or looking at it holistically 15:30:44 ... may yield better result 15:30:48 ... that's my preference 15:30:56 ack je\ 15:31:01 ack je 15:31:01 jeff, you wanted to comment that the nebulous state already exists 15:31:02 ack jef 15:31:03 scribe+ 15:31:32 jeff: I understand concerns re: wanting approval and it doesn't come, so outcome is nebulous. fair concerns. 15:31:52 ... To the extent they're fair, they're also in P2021 - they're not new in what we're looking at today. 15:32:24 ... We should discuss improvements there, but not fixing existing problem shouldn't block this. 15:32:24 David: Florian, please wrap this up 15:32:28 scribe- 15:32:33 Florian: Either we have consensus and merge it now 15:32:43 ... or assign me to go back to tweak and make clearer 15:32:53 ... possibly introducing time outs 15:33:08 ... I lean towards - these are good questions, but separate questions 15:33:23 David: Let's move to #585 15:33:27 ... team decision 15:33:30 ... premature closing 15:33:42 Florian: This one is similar in shape but possibly more concerning 15:33:51 ... deals with group creation and closure 15:34:04 ... for creation, does not tell us how we get to a proposed charter 15:34:17 ... it starts with the proposed charter and the Director is then looking at it 15:34:26 ... for that part, it is similar to #586 15:34:36 ... on forceful closure of group 15:34:48 ... we are moving it from Director to team 15:35:00 ... perhaps not make the naive substitution 15:35:08 ... might want to spend time thinking. 15:35:26 q? 15:35:27 David: Seems worthy of more thought 15:35:33 q+ 15:35:45 ... it would be nice to work through some examples 15:35:48 q+ 15:35:53 q+ to say "patents" 15:36:01 ... prematurely closing in a controversial way 15:36:15 Florian: In this case, there are different routes for appeal 15:36:22 ... that is explicitly mentioned 15:36:22 ack flo 15:36:28 ack jeff 15:37:40 ack ws 15:37:40 wseltzer, you wanted to say "patents" 15:37:40 David: We have a target of Director-free 15:37:47 ... trying to remove all mentions 15:38:19 Wendy: For forcible stoppage of work, a irresolvable patent assertion could be a reason. 15:38:21 q+ 15:38:37 Florian: "A" way or "The" way 15:38:39 q+ to wrap up 15:38:44 ack jef 15:38:51 Wendy: I can imagine the membership wanting to close in such a case 15:39:41 wseltzer: I could envision a distinct case in which the Membership determines there's no way a group can be successful, and asks the team to force the group to stop 15:39:44 q? 15:39:53 ack ds 15:39:53 dsinger, you wanted to wrap up 15:40:00 Jeff: But Wendy's case is covered by the patent policy 15:40:16 [^ wendy's first case] 15:40:20 David: Chris, we should inform the AB of the discussion 15:40:43 ... there could be two cases - whether the group agrees or not 15:40:45 q+ 15:40:55 ... these two are illuminating 15:41:06 ... we can use as paradigmatic examples 15:41:13 ... can we leave them as open PRs? 15:41:17 Florian: Sure. 15:41:20 ack jef 15:42:32 Jeff: As a practical matter, when a groups wants to keep going, we let them finish the charter, but may not recharter 15:42:41 David: So let's leave it open for now 15:42:51 Florian: But not for too long since there is a lot to do 15:43:01 David: I will not hold forever if it is mere anxiety 15:43:08 ... we need specific improvements 15:43:12 Florian: SGTM 15:43:20 Subtopic: Recusal 15:43:47 https://github.com/w3c/w3process/issues/278#issuecomment-964403752 15:43:50 David: How do we deal with people being on the council which may seem to be inappropriate 15:43:51 q+ 15:44:00 ... I'd like to hear discussion 15:44:02 q+ 15:44:05 ack jef 15:44:06 ... we need to move ahead 15:44:35 scribe+ 15:44:51 jeff: I've supported David's consolidation of ideas 15:45:13 ... propose that we use this process in incubating decision-process 15:45:17 q+ 15:45:20 ... not yet as decided process text 15:45:29 ... if it works well, great, we can put it into Process 15:45:41 ... leave it open for experimental trial 15:45:41 ack flo 15:45:47 David: I don't expect to close the topic after this even if everyone agrees 15:45:54 Florian: Agree with Jeff with a nuance 15:46:10 q+ 15:46:16 ... the DF branch should include this if this is where we are for now 15:46:30 ... the fact that Manu has supported it is noteworthy 15:46:44 q? 15:46:46 ... since he had concerns about DID recusals 15:46:47 ack jr 15:46:58 James: Just scanning this 15:47:24 ... first comment: "no one is required to recuse" 15:47:35 ... usually there are clear requirements to recuse themselves 15:47:48 ... that is quite concerning to me that we have no rules at all that require recusal 15:48:02 David: I would be happy for people to try 15:48:15 Florian: What we are trying to design is not a justice for objective truth 15:48:20 +1 to Florian 15:48:25 ... if you were, you can be aggressive with recusal rules 15:48:33 ... we want broad agreement from the community 15:48:37 q+ 15:48:44 q? 15:48:49 ... there may be points where we are too tainted 15:49:04 ... you also might have missed that there is forceful recusal 15:49:16 ... it is made by group decision 15:49:32 David: I encourage you (James) to read all of the comments in the issues 15:49:54 James: Does the Council decide by unanimous vote 15:50:04 q+ 15:50:14 David: We want unanimity; but don't want to leave without decisions 15:50:25 James: I'm familiar with majority rules 15:50:35 ... COI can usually be identified for common cases 15:50:41 ... such as financial interest 15:50:54 Florian: We all have financial interests 15:51:03 ack jef 15:51:15 scribe+ 15:51:22 jeff: please add further to the thread 15:51:38 ... I find myself agreeing with both Florian and James 15:52:05 q+ to propose the word "dismiss" for what the Council does when it votes 15:52:22 ... from lengthy discussion, understand why it's hard to identify MUSTs 15:52:39 ... even as I recognize those exist in many other circumstances 15:53:04 ... I'm reluctant to fix the text even in a branch before testing 15:53:19 q+ 15:53:21 ... if we test with a few councils, and the community sees it works, then gives useful experience 15:53:30 ack cwli 15:53:31 dsinger: agree we're in try-and-see mode 15:53:36 ack cwi 15:53:36 David: We will wrap up soon. 15:53:42 Chris: We had a good thread 15:53:48 ... beginning to land on some specifics 15:53:59 ... just saw Manu's last comment 15:54:16 ... strict recusal rules with anyone with an interest would obviate half the council 15:54:23 ... we are not looking for that 15:54:33 ... we are looking for gross COIs 15:54:39 q+ 15:54:40 ... the system will address that 15:55:01 ... the mechanics are different because it was a large council 15:55:06 ... lots of voices in the room 15:55:16 ... worked towards a consensus in line with W3C culture 15:55:17 zakim, close the queue 15:55:17 ok, dsinger, the speaker queue is closed 15:55:25 ... don't know if it is perfect yet 15:55:32 ... difficult cases on the table. 15:55:33 ack jr 15:55:49 James: I would like to challenge assertion from Chris 15:56:01 q+ 15:56:04 ... there could be times when no user agent vendor should be on the council 15:56:09 ... can't take that as a given 15:56:17 ... Council may be set up for different purposes 15:56:28 ... could be a technical spec v could be about policy 15:56:35 q? 15:56:38 ack flo 15:56:54 Florian: In terms of including in DF branch 15:57:07 ... I am uncomfortable that the DF branch has something different 15:57:25 ... can include this in DF branch with a wording that it is experimental 15:57:34 [Florian, WFM, thanks.] 15:57:46 David: I suggest "recuse" means they recuse themselves 15:57:53 ... dismiss if it is a Council decision 15:58:05 I would like to understand what kind of cases would mean "all UA vendors should be dismissed" 15:58:10 ... need to decide on reporting - does membership see reasons and vote totals? 15:58:26 ... I will work with Florian to write this up as a PR on DF branch with a warning. 15:58:35 ... agreeable? 15:58:43 +1 15:58:49 +1 to David's proposal 15:58:54 +1 15:59:04 David: If you have issues with that, please put that into the issue. 15:59:10 +1 15:59:23 Subtopic: Other issues 15:59:34 David: Please start attacking 35 other open issues 15:59:40 Topic: New issues 15:59:45 David: Please take a look 15:59:55 ... I will work with Florian and Elika 16:00:06 Topic: Next meeting 16:00:11 David: 8 December 16:00:29 Topic: AoB 16:00:35 David: Congrats on P2021 16:00:36 q? 16:00:40 ack ds 16:00:41 dsinger, you wanted to propose the word "dismiss" for what the Council does when it votes 16:00:45 rrsagent, make minutes 16:00:45 I have made the request to generate https://www.w3.org/2021/11/10-w3process-minutes.html jeff 16:00:59 [adjourned] 18:01:34 TallTed has joined #w3process 18:20:48 Zakim has left #w3process