- From: David Singer <singer@apple.com>
- Date: Fri, 13 Mar 2020 07:48:35 -0700
- To: Léonie Watson <lwatson@tetralogical.com>
- Cc: W3C Process CG <public-w3process@w3.org>
> On Mar 12, 2020, at 1:08 , Léonie Watson <lwatson@tetralogical.com> wrote: > > I'm not sure if the issues on the deferred list are deferred from 2020 > to 2021, or deferred from 2021 to the future, No Milestone assigned: we have not yet decided Specific year Milestone assigned: we want to do it in that year Deferred Milestone assigned: we have (previously) decided not to do it in a specific year The ‘deferred’ category needs periodic re-examination, specially when we open a new ’specific year’, which is what we’re doing now. > but either way I'd really > like to add #130 (requirements for wide and horizontal review) to 2021. > > There is proposed language for the Process document. It's been > reasonably well discussed and reviewed by people here plus people > involved in either requesting or doing reviews, and I think at the AB > F2F we left it that I'd talk with Florian about moving the proposed text > into a PR (which I can do if helpful). > https://github.com/w3c/w3process/issues/130 > > > > > > On 11/03/2020 17:29, David Singer wrote: >> Friends >> >> We are late in the cycle now; normally we review the Process in the fall meeting, for ballot and adoption early in the year. We’re late (for good reason) on P2020. But we hope to stay on schedule for Process2021. >> >> That means we are limited in what we’ll achieve. >> >> We intend to do Registries; we didn’t quite make it in 2020. >> >> We can do other urgent work, easy bug fixes, editorials, and so on. >> >> We have milestones for each revision. The way we use them: >> * assigned to the 2020 or 2021 Milestone, we intend/hope/expect to address them in that process revision >> * assigned to the ‘Deferred’ Milestone, we have triaged this and explicitly have not put it in a specific year (yet) >> * unassigned, we have not triaged into a year or explicitly deferred (yet) >> >> So, I am asking you to look at whether the milestone 2021 is correct, in your opinion. >> >> 1. should we address the issues assigned to 2021, in 2021; are there any that we should not try to address in this list: >> >> <https://github.com/w3c/w3process/milestone/6> >> >> 2. are there other issues that we should address in this short-cycle? Candidate include: >> >> 2a. issues currently explicitly deferred: >> >> <https://github.com/w3c/w3process/milestone/7> >> >> 2b. There may be issues that are related to Director-free operation that can be done before we decide on and adopt our approach to becoming Director-free: >> >> <https://github.com/w3c/w3process/labels/director-free> >> >> 2c. There may be new issues that are not yet assigned to a milestone (none as I write this): >> >> <https://github.com/w3c/w3process/issues?q=is%3Aopen+no%3Amilestone> >> >> >> * * * * >> >> For myself, I would like to address the following in 2021: >> >> <https://github.com/w3c/w3process/issues/324> >> <https://github.com/w3c/w3process/issues/60> >> >> and this one in Process 2020, as it’s editorial: >> >> <https://github.com/w3c/w3process/issues/376> >> >> David Singer >> Manager, Software Standards, Apple Inc. >> >> > > -- > Director @TetraLogical David Singer Manager, Software Standards, Apple Inc.
Received on Friday, 13 March 2020 14:48:53 UTC