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

Incidentally, my belated regrets for not making it to the call this
morning.  I came back from vacation late last night, on a flight that was
already going to put me in somewhat late, but took off an hour late and was
diverted twice while in the air (in the end, back to our original
destination, so at least that was good), so did not get up early this
morning.  :/

On Tue, Jul 23, 2019 at 4:42 PM David Singer <singer@apple.com> wrote:

> comments welcome, I am coming off a week of vacation and two weeks of
> other meetings, 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/06/26-w3process-minutes.html>
>
>
> Usual meeting time: SECOND and FOURTH WEDNESDAY OF THE MONTH AT 7AM PACIFIC
>
>
> 1) Assign scribe, etc.,
>
> 2) Ever-whatever update. Florian, Jeff et al. to give us a state-of-play
> update; please see https://www.w3.org/wiki/Everwhat_dashboard before the
> call.
>
> 3) Registries. see
> https://github.com/w3c/w3process/issues/168#issuecomment-514413308 for
> both Process text and supporting Guidelines.
>
> <https://github.com/w3c/w3process/issues/168>
>
> I would like consensus to take this
> a) into Process-text drafting
> b) back to the people who said they needed a registry process, to see if
> they have comments
>
> 4) Schedule update. Where are we likely to be, when, and what do we do at
> TPAC. [Jeff].
>
> Usual business follows, as time permits:
>
> 5) Editorials, and (Other) Pull Requests and Issues tagged Agenda+
>
> 5.1) Approving in bulk the editorial updates, please review offline as we
> won’t have time on the call:
>    <
> https://github.com/w3c/w3process/labels/Type%3A%20editorial%20improvements
> >
>
> 5.2) Pull Requests: <
> https://github.com/w3c/w3process/pulls?q=is%3Aopen+is%3Apr+label%3AAgenda%2B
> >
> 5.3) Issues:            <
> https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aopen+is%3Aissue+label%3AAgenda%2B+
> <https://github.com/w3c/w3process/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3AAgenda%2B+>
> >
>
> 6) If we have time, Review of 2020 milestone; who has the action, where
> are we going, what’s next?
>
> 6.1) assigned to someone:
> <
> https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aissue+is%3Aopen+milestone%3A%22Process+2020%22+assignee%3A*
> <https://github.com/w3c/w3process/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+milestone%3A%22Process+2020%22+assignee%3A*>
> >
>
> 6.2) unassigned:
> <
> https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aissue+is%3Aopen+milestone%3A%22Process+2020%22+no%3Aassignee
> <https://github.com/w3c/w3process/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+milestone%3A%22Process+2020%22+no%3Aassignee>
> >
>
> 7) If we have time, new issues and updates.
>
> 7.1) new since prior check: <
> https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aissue+is%3Aopen+created%3A%3E2019-03-13+
> <https://github.com/w3c/w3process/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+created%3A%3E2019-03-13+>
> >
>
> 7.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
> <https://github.com/w3c/w3process/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+updated%3A%3E2019-05-22+-milestone%3A%22Process+2020%22>
> >
>
> 8) 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
> <https://github.com/w3c/w3process/issues?utf8=%E2%9C%93&q=is%3Aopen+assignee%3A*+-milestone%3A%22Process+2020%22>
> >)
>
>
> The usual closers:
>
> 9) Next meeting. formally Wed August 14th; (I will be in Korea but should
> be able to do an 11pm call, especially if someone kicks me if I don’t turn
> up)
>
> 10) Any other business.
>
>
>
>
>
>