Re: DRAFT-2 agenda for the regular Process Call Wednesday 11th Sept 7am PDT

possible regrets, may still be at Prospect dinner in China.

On 9/10/2019 2:13 PM, David Singer wrote:
> [Draft 2 has better Registry slides; thanks to Florian for the review]
>
>
> 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/08/28-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) Any needed updates and discussion on Process sessions at TPAC
>   
> Thursday:
> 15:00–15:40 Continuous Specification Development Process for W3C (fantasai, Invited Expert; Philippe Le Hégaret, W3C)
>
> 15:40–16:00 Process 2020 including registries (David Singer, Apple)
>
>  Florian on P2020 at <https://florian.rivoal.net/talks/TPAC-2019/process-2020/>
>  Registry slides attached.
>
>
>
> 16:00–16:20 Director-free operation (Florian Rivoal, Invited Expert)
>
>
>
> 3) Editorials, and (Other) Pull Requests and Issues tagged Agenda+
>
> 3.1) Pull Requests: <https://github.com/w3c/w3process/pulls?q=is%3Aopen+is%3Apr+label%3AAgenda%2B>
>
>
> Add Note about the flexibility of Consensus #323 <https://github.com/w3c/w3process/pull/323>, from issue <https://github.com/w3c/w3process/issues/296>
> Don't require documenting editorial changes since the previous CR #308 <https://github.com/w3c/w3process/pull/308>, from issue <https://github.com/w3c/w3process/issues/307>
> Clarify superseding #213 <https://github.com/w3c/w3process/pull/213/files>
>
> 3.2) Issues:   <https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aopen+is%3Aissue+label%3AAgenda%2B+>
>
> New, need to decide how to proceed: add references to "Open Stand" principles #325 <https://github.com/w3c/w3process/issues/325>
>
> 3.3) Editorials: we still need to make progress on the meaning of Discontinued, and clearer wording for transitions to superseded/obsolete. They are not tagged agenda+
>
> What does the document status "discontinued" mean? #262 <https://github.com/w3c/w3process/issues/262>
> provide clearer/common wording for transitions to Obsolete/Superseded status #141<https://github.com/w3c/w3process/issues/141>
>
> 4) Review of 2020 milestone; who has the action, where are we going, what’s next? Do we expect/hope/intend to finish these in P2020 or should we start slipping them?
>
> 4.1) assigned to someone, please be prepared to give any needed updates (briefly), or if you are blocked by something, explain what it is so we can unblock you:
> <https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aissue+is%3Aopen+milestone%3A%22Process+2020%22+assignee%3A*>
>
> Wendy/Florian, can you update us on the the practice is going here, and whether we should formalize it?
> Define charter review process to require addressing comments as in CR transitions #182 <https://github.com/w3c/w3process/issues/182>
>
> otherwise I think they are in hand
>
> 4.2) unassigned; none.
>
> 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 many; I don’t intend to list them here.
>
> If we reduce to those not either (a) evergreen or (b) director-free, and not (c) Agenda+, we have 4:
>  <https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aissue+is%3Aopen+created%3A%3E2019-03-13+-label%3AEvergreen+-label%3AAgenda%2B+-label%3Adirector-free+>
> #262 is above
>
> What are the rules for where/how W3C publications are developed? #322 <https://github.com/w3c/w3process/issues/322>
> Do we need a lighter-weight process for superseding when it's "obvious"? #324 <https://github.com/w3c/w3process/issues/324>
> Community and Business Groups #326 <https://github.com/w3c/w3process/issues/326>
>
>
> 5.2) updated but not any of:
>  Process2020 milestone
>  nor Evergreen
>  nor director-free
>  nor Agenda+
>  not assigned to the AB (Needs AB Feedback)
> <https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aopen+is%3Aissue+updated%3A%3E2019-05-22+-label%3A%22Needs+AB+Feedback%22+-label%3AAgenda%2B+-milestone%3A%22Process+2020%22+-label%3AEvergreen+-label%3Adirector-free+>
>
> There are a number getting attention:
> #326, #324, #322 are above as new issues
> #262 #141 are above
>
> define "independent" #167 <https://github.com/w3c/w3process/issues/167>
>  — I think we need a task-force, or someone, to collate the issues and formulate the questions
> Should the process include something about Testing? #157 <https://github.com/w3c/w3process/issues/157>
>  — similarly a complex question which needs to balance a host of factors
>
> Clarify the voting process #60 <https://github.com/w3c/w3process/issues/60>
>  (the famous sentence; we have an inconsistent process document, which I find acutely embarrassing)
> We need to consider equal-preference voting #115 <https://github.com/w3c/w3process/issues/115>
>  (probably sitting with the AB)
>
> 6) If we have time, Assigned, but not on the 2020 milestone (cherry-pick, if people have updates or questions for us):
>
> <https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aopen+assignee%3A*+-milestone%3A%22Process+2020%22>)
>
> The usual closers:
>
> 7) Next meeting. formally Wed Sept 25th, week after TPAC. I assume we’ll meet and de-brief.
>
> 8) Any other business.
>
>
>
>
>
>
> David Singer
> Manager, Software Standards, Apple Inc.
>
>
>
>