- From: Nigel Megitt <nigel.megitt@bbc.co.uk>
- Date: Tue, 21 May 2019 14:03:28 +0000
- To: "Siegman, Tzviya" <tsiegman@wiley.com>, David Singer <singer@apple.com>, W3C Process CG <public-w3process@w3.org>
I see that the final digit wrapped to the following line, which probably broke the URL. Thanks for resending on a line by itself so that doesn’t happen again, Tzviya. On 21/05/2019, 14:41, "Siegman, Tzviya" <tsiegman@wiley.com> wrote: >The timeanddate.com form showed the time several hours off for me. >Perhaps this one will work better? >https://www.timeanddate.com/worldclock/fixedtime.html?msg=Process+CG&iso=2 >0190522T07&p1=224 > >Tzviya Siegman >Information Standards Lead >Wiley >201-748-6884 >tsiegman@wiley.com > >-----Original Message----- >From: Nigel Megitt <nigel.megitt@bbc.co.uk> >Sent: Tuesday, May 21, 2019 5:36 AM >To: David Singer <singer@apple.com>; W3C Process CG ><public-w3process@w3.org> >Subject: Re: DRAFT agenda for the regular Process Call Wednesday 22nd May >7am PDT > >That meeting time in your time zone: >https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190522T07&p1=2 >2 >4 > >On 21/05/2019, 00:01, "singer@apple.com on behalf of David Singer" ><singer@apple.com> wrote: > >>Webex at >><https://lists.w3.org/Archives/Member/internal-w3process/2019May/0000.h >>tml >>> >> >> >> >>IRC is #w3process >> >>Log of prior meeting at >><https://www.w3.org/2019/05/08-w3process-minutes.html> >> >> >>Usual meeting time: SECOND and FOURTH WEDNESDAY OF THE MONTH AT 7AM >>PACIFIC >> >> >>1) Assign scribe, etc., >> >>2) Pull Requests and Issues tagged Agenda+ >> >><https://github.com/w3c/w3process/labels/Agenda%2B> >> >>The evergreen and registry issues are ‘on the table’. >> >>3) Review of 2020 milestone; who has the action, where are we going, >>what’s next? >> >>3.1) assigned to someone: >><https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aissue+is%3Aopen+ >>mil estone%3A%22Process+2020%22+assignee%3A*> >> >>3.2) unassigned: >><https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aissue+is%3Aopen+ >>mil estone%3A%22Process+2020%22+no%3Aassignee> >> >>4) Assigned, but not on the 2020 milestone >> >><https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aopen+assignee%3A >>*+- >>milestone%3A%22Process+2020%22>) >> >>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+ >>cre >>ated%3A%3E2019-03-13+> >> >>5.2) updated but not Process2020 milestone >><https://github.com/w3c/w3process/issues?utf8=✓&q=is%3Aopen+is%3Aissue+ >>upd ated%3A%3E2019-03-13+-milestone%3A%22Process+2020%22> >> >>6) Next meeting. formally Wed June 2nd. >> >>Note, at a meeting soon we should formally approve Editorial Pull >>Requests, which I’ll do ‘in bulk’. >> >><https://github.com/w3c/w3process/labels/Type%3A%20editorial%20improvem >>ent >>s> >> >>7) Any other business. >> >> >
Received on Tuesday, 21 May 2019 14:04:40 UTC