14:04:50 RRSAgent has joined #w3process 14:04:55 logging to https://www.w3.org/2024/05/22-w3process-irc 14:08:43 JennieM has joined #w3process 14:09:22 scribeNick: plh 14:09:39 Topic: Pull Requests 14:09:45 subtopic: #874 14:10:04 --> https://github.com/w3c/w3process/pull/874/files Require listing chair(s) in charters 14:10:18 Github: https://github.com/w3c/w3process/pull/874/files 14:10:35 Github: https://github.com/w3c/w3process/issues/823 14:10:42 plh: any objection 14:10:53 Resolved: Let's mergeg #874 14:11:04 subtopic: #875 14:11:12 Github: https://github.com/w3c/w3process/pull/615 14:11:29 --> https://github.com/w3c/w3process/pull/875/files Remove note about AC consensus assessment 14:12:15 Florian: outside of AV review, we don't have a process 14:12:40 ... so having a note saying that the CEO does it seems confusing/unecessary 14:13:46 plh: I'd like to get feedback from Seth 14:14:08 ACTION: plh to check with the CEO 14:14:27 Florian: can we agree to do this unless Seth says anything? 14:14:30 plh: sure 14:14:51 Resolved: unless we receive a comment from the CEO, this will get merged 14:15:13 Topic: #873 14:15:20 Topic: #877 14:15:38 Github: https://github.com/w3c/w3process/issues/864 14:15:55 --> https://github.com/w3c/w3process/pull/877/files Add note reminding that the first stage of REC track is WD 14:16:17 Florian: the REC track a few maturity levels, that's WD, CR, PR, REC 14:16:47 .... FPWD is not a maturity level 14:17:12 ... so, you go from Note->WD, not WD->FPWD 14:17:35 .... I looked at the Patent Policy and Process, I believe this is what was meant 14:17:53 ... so this is a clarification 14:18:30 ... this case shouldn't arise most of the time. In the past, we turned REC-track to Note, because we did not have discontinued draft 14:19:05 ... the recent case was Ruby 14:20:01 plh: should we consult PSIG for that? 14:20:13 ... since FPWD has a call for exclusion 14:21:16 florian: while the document is a Note, it's ok. Once it's a WD, you get committed once you join 14:21:52 ... if you republish a FPWD, then what happened to the previous commitment? It's a new document. 14:22:41 plh: I'd feel more comfortable if we were asking for PSIG confirmation 14:23:51 Florian: the patent policy doesn't care if it's outside the REC-track. Once it's back on the REC track 14:24:46 .... if you make normative changes to a Note, that could be a problem but the patent policy doesn't address that 14:27:04 fantasai: I think this is the correct thing to do. If you join the Group when it's a Note, you might not realize that you will have an opportunity later 14:28:57 plh: joining a WG with documents in Note state (or editor's draft state) doesn't create an exclusion opportunity 14:30:26 Florian: it's not obvious how things work around rechartering 14:31:19 plh: I'm fine with making the change and notifying PSIG 14:31:22 +1 14:31:41 Resolved: Let's merge #877 and notify PSIG 14:31:52 ACTION: fantasai to notify PSIG 14:32:07 Topic: #873 14:32:21 Github: https://github.com/w3c/w3process/issues/450 14:33:16 Florian: it seems it's possible to move from CRD to PR if you don't make substantive changes. but the definition of CRD claims that it was only to prepare a CRS 14:33:48 .... the PR makes things clearer 14:34:24 Plh: +1 14:34:45 Resolved: Let's merge #873 14:35:06 Topic: #878 14:35:27 Florian: let's at both #873 and #876 14:35:35 s/873/878/ 14:35:46 Florian: we have classes of changes 14:37:47 ... the pull requests harmonize how revising a recommendation work with those classes. 14:39:47 s/876/865/ 14:40:22 ... I prefer 878 14:45:21 plh: the Note talks about "This prohibition" but the previous paragraph doesn't mention a probihition 14:45:35 Florian: we could rephrase with "This restriction".... 14:46:01 plh: that's fine by me 14:46:54 Resolved: merge #878 after additional editorial tweaks for the Note 14:46:55 +1 to merging and tweaking the note somehow 14:47:24 Topic: #876 14:47:32 Github: https://github.com/w3c/w3process/pull/876 14:48:12 Florian: there is an article in the Guide about Workshops. We have a section about workshop and symposia and doesn't contain much rules 14:48:34 ... that section only has one requirement: how far ahead it is announced 14:49:06 .... I suggest to move the rule into the meeting section, as well as workshop definition 14:49:12 ... and move the rest into the /Guide 14:49:39 ... we have rules about recorded meetings unless people disagree, which will apply to workshop as well 14:50:16 ... currently the rule is 8-weeks advance notice 14:50:28 scribe+ 14:50:41 plh: I agree and disagree. I agree in principle, but disagree because more work for me in /Guide 14:51:05 plh: regarding advance notice, could bypass process by calling it something other than "Workshop" 14:51:31 florian: This PR fixes that loophole, because doesn't say for workshops, but says for open events such as workshops. 14:52:29 florian: open-ended meetings should have enough notice to attend 14:52:44 s/florian:/.../ 14:52:57 ... could make the edits without generalization, but thought it would be a good idea. 14:53:10 plh: I think need more feedback for this, run it by the Team. 14:53:21 florian: Agree, let's be sure about what we're doing 14:53:24 ack fant 14:53:42 fantasai: I think we need an escape hatch 14:53:54 ... a casual/local meeting for example 14:54:13 ... like a WG organizing a dev meetup on the side 14:54:25 ... the pull request is too strict 14:55:20 florian: should we restrict it to workshop? include an exception mechanism? 14:56:07 plh: restrict it to workshop 14:56:41 florian: what about symposia? 14:56:54 plh: we haven't had one for the past 20 years at least.... 14:57:50 ... [missed] 14:57:57 ... but for something like a developer meetup, at most it informs a specific WG, doesn't direct W3C itself 14:58:16 ... that's why I think restriction on Workshop is important, it can impact direction of W3C so need enough notice for Members to be there 14:58:21 ... but for things that are informative, it matters less 14:58:32 ... nowadays also we have a lot of recordings, so if you're not there you can see it afterwards 14:58:43 florian: OK, I'll modify PR to make the advance meeting notice apply only to Workshops 14:58:53 plh: sounds good to me 14:59:12 fantasai: let's come back to this with a new PR 14:59:14 Florian: I'll update the PR