- From: Ian Clelland <iclelland@google.com>
- Date: Mon, 16 May 2022 12:39:02 -0400
- To: Noam Rosenthal <noam.j.rosenthal@gmail.com>
- Cc: Yoav Weiss <yoavweiss@google.com>, Nic Jansma <nic@nicj.net>, public-web-perf <public-web-perf@w3.org>
- Message-ID: <CAK_TSXKHHBZjfg81C_+6dQpErhad7+6hiTbjwgdJDtG+CDhk6w@mail.gmail.com>
10:30 ET works for Google folks, I think. I'll send out a calendar invite this week to folks here. Noam -- I appreciate the value in being able to do this asynchronously; I've been thinking about how to use this kind of meeting as a forcing function to ensure that all issues get proper timely attention, but to also ensure that it can support asynchonous work as well. I'm setting up a GitHub project for triaging all of the issues, with as much automation as possible. Ideally, a synchronous meeting can be spent ensuring that everyone agrees that issues are in the right buckets (new issues are properly assigned, that issues blocked on WG discussion are noted and scheduled, and that old issues aren't blocked unreasonably). Any relevant updates to the issues should be visible in the project, so my hope is that this should handle anyone working asynchronously that way. Ian On Fri, May 13, 2022 at 1:28 AM Noam Rosenthal <noam.j.rosenthal@gmail.com> wrote: > Hi Ian > TBH I prefer to avoid calendar meetings for tasks that can be done > asynchronously. > I started going over the LCP issues myself to see if I have input, I > didn't know it required triage. > > If other folks prefer a synchronized triage these timings are OK with me, > I think biweekly is more than enough. > Note that I'm on leave for the next 4 weeks though, but I can try to join > if there is an opportunity, or respond to issues asynchronously. > > On Thu, May 12, 2022 at 9:41 PM Yoav Weiss <yoavweiss@google.com> wrote: > >> Thanks Ian!! >> Are you planning for this to be a weekly call or a bi-weekly one? >> >> On Thu, May 12, 2022 at 5:18 PM Ian Clelland <iclelland@google.com> >> wrote: >> >>> Hey WebPerf Folks! >>> >>> I'm setting up a recurring meeting to triage all of the outstanding >>> WebPerf spec issues (and there are a bunch) -- to make sure that we are >>> making progress on old issues, and not letting new ones go unnoticed. >>> >>> I'm expecting it to be a pretty dry, functional meeting, so I'm >>> explicitly just inviting a few people, but anyone's welcome to attend. >>> >>> Tentatively scheduling this to replace a previous triage meeting; >>> Mondays at 11:00 ET, 08:00 PT, 15:00 UTC. I'm really open to changing that >>> around as needed, though. >>> >>> I figure that we can start by tackling some of the bigger repos first -- >>> Reporting has ~40 outstanding issues, LCP has ~25, and we can work our way >>> down from there. >>> >>> If people are agreeable to the times, I'll send out a calendar invite, >>> and hopefully see folks next week! >>> >>> Ian >>> >>
Received on Monday, 16 May 2022 16:39:26 UTC