Re: DRAFT agenda for the regular Process Call Wednesday 12th June 7am PDT

My regrets for this call.

On Tue, Jun 25, 2019 at 5:36 AM Jeff Jaffe <jeff@w3.org> wrote:

>
> On 6/24/2019 6:29 PM, David Singer wrote:
> > Trying again on a regular call…what did I forget this time?
> >
> >
> > 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/05/22-w3process-minutes.html>
> >
> >
> > Usual meeting time: SECOND and FOURTH WEDNESDAY OF THE MONTH AT 7AM
> PACIFIC
> >
> >
> > 1) Assign scribe, etc.,
> >
> > 2) We need to make progress on Registries. Please review the Wiki text at
> > <https://www.w3.org/wiki/Repositories#Recommendation>
> >   and its supporting issue
> > <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
> Right now, we have made the Evergreen proposal a bit more complex as a
> way of making it possible to accommodate registries as a simplified
> special case.  If we now plan to create text for registries, does the
> Process CG want us to simplify the Evergreen proposal to remove the
> treatment of registries as part of Evergreen?
> >
> > 3) Editorials, and (Other) Pull Requests and Issues tagged Agenda+
> >
> >   3.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
> >
> >
> >    3.2) Pull Requests: <
> https://github.com/w3c/w3process/pulls?q=is%3Aopen+is%3Apr+label%3AAgenda%2B
> >
> >    3.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+>
> >
> >
> > 4) If we have time, 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*
> <https://github.com/w3c/w3process/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+milestone%3A%22Process+2020%22+assignee%3A*>
> >
> >
> >   4.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>
> >
> >
> > 5) If we have time, 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+
> <https://github.com/w3c/w3process/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+created%3A%3E2019-03-13+>
> >
> >
> >   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
> <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>
> >
> >
> > 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
> <https://github.com/w3c/w3process/issues?utf8=%E2%9C%93&q=is%3Aopen+assignee%3A*+-milestone%3A%22Process+2020%22>
> >)
> >
> > 7) Next meeting. formally Wed July 10th; I will be at MPEG so we need to
> find a replacement chair, or defer
> This is a very important meeting as the AB expects a final CG proposal
> of Process 2020 to come into the AB's early August meeting.
> >
> > 8) Any other business.
> >
> >
> >
>
>