- From: Jeff Jaffe <jeff@w3.org>
- Date: Tue, 13 Aug 2019 11:44:25 -0400
- To: David Singer <singer@apple.com>, W3C Process CG <public-w3process@w3.org>
agenda+ (for wherever you think it fits). Since the Process Document references CEPC, the Process CG should be aware that the PWE task force is considering a major revision to CEPC [1], and that it might be ready for AC review in the process 2020 time frame. Jeff [1] https://w3c.github.io/PWETF/ On 8/13/2019 3:52 AM, David Singer wrote: > [corrected subject, this IS the proposed agenda] > > comments welcome, I am coming off a week of vacation and and a week of AB, so I am curiously fresh and unbiased (which is a euphemism for not yet prepared) > > > > Webex at <https://lists.w3.org/Archives/Member/internal-w3process/2019May/0000.html> > > IRC is #w3process > > Log of prior meeting at <https://www.w3.org/2019/07/24-w3process-minutes.html> > > > Usual meeting time: SECOND and FOURTH WEDNESDAY OF THE MONTH AT 7AM PACIFIC > > > I realize we might not get beyond agenda #3, but… > > 4 is the 2020 Milestone. At some point we’ll have to admit we missed the milestone and decide what to do. > 5 is new issues; one day we should triage newly arrived issues, and newly updated issues. > 6 is stuff we assigned to someone, and at some point we might like to admit we got the wrong victim > > > > 1) Assign scribe, etc., > > 2) Preparing to present Process status at TPAC (not yet for approval): Jeff for the schedule, Florian update > > 3) Editorials, and (Other) Pull Requests and Issues tagged Agenda+ > > 3.1) Editorial: > — decide whether to address or close (PLH action): > #262 What does the document status "discontinued" mean? <https://github.com/w3c/w3process/issues/262> > > — propose to close as Tantek seems to have lost interest: > #141 provide clearer/common wording for transitions to Obsolete/Superseded status <https://github.com/w3c/w3process/issues/141> > > (no other editorial updates exist at time of agenda creation): > <https://github.com/w3c/w3process/labels/Type%3A%20editorial%20improvements> > > 3.2) Pull Requests: <https://github.com/w3c/w3process/pulls?q=is%3Aopen+is%3Apr+label%3AAgenda%2B> > Florian #309 Define how Governing Documents other than the Process are revised <https://github.com/w3c/w3process/pull/309> > Nigel #213 Clarify superseding <https://github.com/w3c/w3process/pull/213> > > 3.3) Issues: <https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aopen+is%3Aissue+label%3AAgenda%2B+> > The only one that’s not Ever* or Registry is > #307 CR change documentation requirement should be for substantive changes only <https://github.com/w3c/w3process/issues/307> > > > #79 (Living Standards) and #168 (Registries) are in hand; should the label Agenda+ be removed? > #271 Does the decision to allow the Evergreen state need to be made in the Charter? <https://github.com/w3c/w3process/issues/271> — is also Evergreen > #272 What is the difference between a PD and a WD? <https://github.com/w3c/w3process/issues/272> — is also evergreen, but maybe we can agree there is none > > > 4) Review of 2020 milestone; who has the action, where are we going, what’s next? > > 4.1) assigned to someone: > <https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aissue+is%3Aopen+milestone%3A%22Process+2020%22+assignee%3A*> > #79, #168 dealt with above > > Florian, Natasha: Substantive changes undefined for Charter and Process reviews #28 <https://github.com/w3c/w3process/issues/28> > Florian: Define charter review process to require addressing comments as in CR transitions #182 <https://github.com/w3c/w3process/issues/182> > Florian: TAG appointment should be via IETF style nomcom #230 <https://github.com/w3c/w3process/issues/230> > > Natasha: Should the process include something about Testing? #157 <https://github.com/w3c/w3process/issues/157> > > Wendy, Ralph, Leonie: Enumerate the requirements for wide review #130 <https://github.com/w3c/w3process/issues/130> > > Wendy: define "independent" #167 <https://github.com/w3c/w3process/issues/167> > > 4.2) unassigned; we should admit we missed the milestone: > <https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aissue+is%3Aopen+milestone%3A%22Process+2020%22+no%3Aassignee> > #307 dealt with above > #183 process should clarify how Superseded state interacts with other maintenance processes (e.g., new versions, edited/amended recommendations) <https://github.com/w3c/w3process/issues/183> > > > 5) new issues and updates. > > 5.1) new since prior check: <https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aissue+is%3Aopen+created%3A%3E2019-03-13+> > There are 35; I don’t intend to list them here. > > If we reduce to those not either (a) evergreen or (b) director-free, we have 5: > #307 is above > #262 is above > > #264 Suggesting a change to horizontal reviews in the Process <https://github.com/w3c/w3process/issues/264> > — Leonie suggests we close in favor of #130 Enumerate the requirements for wide review <https://github.com/w3c/w3process/issues/130> > #296 Add note to Process about flexibility of consensus <https://github.com/w3c/w3process/issues/296> > — we have agreement in principle but we are struggling to find text that does not have other implications > #305 The process does not include any disposition for updating the Patent Policy <https://github.com/w3c/w3process/issues/305> > — we have a more generalized pull request <https://github.com/w3c/w3process/pull/309> > > 5.2) updated but not Process2020 milestone <https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aopen+is%3Aissue+updated%3A%3E2019-05-22+-milestone%3A%22Process+2020%22> > > There are many, but if we take out director-free and evergreen, and issues above, we have very few left: > #251 First meeting of a WG allowed too soon <https://github.com/w3c/w3process/issues/251> > #223 Allow AB to choose its own chair <https://github.com/w3c/w3process/issues/223> > #115 We need to consider equal-preference voting <https://github.com/w3c/w3process/issues/115> > > 6) If we have time, Assigned, but not on the 2020 milestone > > <https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aopen+assignee%3A*+-milestone%3A%22Process+2020%22>) > > Florian #299 Make it clear than any decision can be objected to <https://github.com/w3c/w3process/pull/299> > Florian #260 Further automating transition requests <https://github.com/w3c/w3process/issues/260> > > Wendy #274 Remove reference to stale document <https://github.com/w3c/w3process/pull/274> > > Ralph #120 Process should say how W3T can update NOTES <https://github.com/w3c/w3process/issues/120> > > Natasha #60 Clarify the voting process <https://github.com/w3c/w3process/issues/60> > > Jeff #10 Are W3C hosts members of W3C? <https://github.com/w3c/w3process/issues/10> > > > The usual closers: > > 7) Next meeting. formally Wed August 28th > > 8) Any other business. > > > > > > > David Singer > Manager, Software Standards, Apple Inc. > > >
Received on Tuesday, 13 August 2019 15:44:28 UTC