Re: All-day WG meeting in May

Agreed! Will set things up then :)

On Wed, Jun 7, 2023 at 11:36 AM Mathias Bynens <mths@google.com> wrote:

> Ok for me. I view this dedicated roadmap sync as a one-off, separate from
> the usual WG meeting.
>
> On Wed, Jun 7, 2023 at 12:34 PM David Burns <david.b@browserstack.com>
> wrote:
>
>> Before I go ahead and set everything up are we still planning on having
>> the usual WG meeting?
>>
>> We have a request from Bocoup to talk about AT-Driver and I am wondering
>> if we should show the finalised roadmap to those who can't make the meeting.
>>
>> David
>>
>> On Tue, Jun 6, 2023 at 3:03 PM Henrik Skupin <hskupin@mozilla.com> wrote:
>>
>>> Mathias Bynens wrote on 30.05.23 13:51:
>>>
>>> Hi all,
>>>
>>> > Based on the responses here I think a face-to-face meeting is unlikely
>>> > to happen. Still, I think it would be useful to have a dedicated remote
>>> > meeting to specifically discuss the roadmap
>>> > <https://github.com/w3c/webdriver-bidi/issues/403> for longer than
>>> fits
>>> > our regular meetings. Perhaps 3 hours is sufficient.
>>> >
>>> > Riffing on Maksim’s proposed time slot, who would be interested in a
>>> > remote meeting @ *Wednesday 2023-06-14 12:00–15:00 UTC (14:00–17:00
>>> CET,
>>> > 05:00–08:00 AM PDT)* with the specific goal to nail down next steps
>>> > w.r.t. the roadmap?
>>>
>>> We discussed internally and this sounds fine for Mozilla folks. Lets
>>> have the meeting at the proposed time.
>>>
>>> Henrik
>>>
>>> >
>>> > On Thu, May 25, 2023 at 11:56 AM Philip Jägenstedt <foolip@google.com
>>> > <mailto:foolip@google.com>> wrote:
>>> >
>>> >     I also think it would be valuable to meet for a longer discussion
>>> >     than we can fit in the regular WG meetings. Like Maksim, I think
>>> the
>>> >     roadmap is the most important thing, and it was very productive
>>> when
>>> >     we worked on that in Berlin last time.,
>>> >
>>> >     On Mon, May 15, 2023 at 10:53 AM Maksim Sadym <sadym@google.com
>>> >     <mailto:sadym@google.com>> wrote:
>>> >
>>> >         The primary purpose of the meeting is to allocate a specific
>>> >         time and venue for focused discussions, making tangible
>>> >         progress, and ideally reaching a consensus on extending our
>>> >         shared roadmap
>>> >         <https://github.com/w3c/webdriver-bidi/issues/403>. If there
>>> are
>>> >         concerns about the logistics of physical hubs, we can opt for a
>>> >         fully-remote meeting format.
>>> >
>>> >         Alternatively, we can continue with the iterative approach
>>> using
>>> >         GitHub issues and regular working group meetings, which would
>>> be
>>> >         more accommodating to participants across different time zones.
>>> >         However, it's important to note that this alternative approach
>>> >         may potentially extend the overall timeline of the process.
>>> >
>>> >         Looking forward to inputs from other participants about their
>>> >         preferences.
>>> >
>>> >         On Thu, May 11, 2023 at 12:41 PM David Burns
>>> >         <david.b@browserstack.com <mailto:david.b@browserstack.com>>
>>> wrote:
>>> >
>>> >             I didn't see this in the agenda otherwise would have sorted
>>> >             it first so me not being there for part of the meeting
>>> seems
>>> >             unrelated.
>>> >
>>> >             We haven't come to a conclusion. I know a lot of people
>>> >             can't travel for just one day so do we see value in a 1 day
>>> >             meeting still or continuing with our monthly meetings?
>>> Would
>>> >             there be value in increasing the cadence of these meetings
>>> >             to be fortnightly?
>>> >
>>> >             David
>>> >
>>> >             On Thu, May 11, 2023 at 10:53 AM Sam Sneddon
>>> >             <gsnedders@apple.com <mailto:gsnedders@apple.com>> wrote:
>>> >
>>> >                 Did we ever come to a conclusion here? This appears to
>>> >                 be the latest suggestion, but we never decided whether
>>> >                 or not we’re actually doing this, and David skipping
>>> >                 much of the meeting yesterday probably didn’t help.
>>> >
>>> >                 /Sam
>>> >
>>> >>                 On 13 Apr 2023, at 10:25, Maksim Sadym
>>> >>                 <sadym@google.com <mailto:sadym@google.com>> wrote:
>>> >>
>>> >>                 As discussed yesterday during our monthly WG meeting,
>>> >>                 we have an updated suggestion for the all-day WG
>>> >>                 meeting 2023Q2:
>>> >>
>>> >>                 1. Date and time: 2023-06-14 12:00 UTC (14:00 CET, 5
>>> >>                 am PDT). We are open for other dates and times.
>>> >>                 2. As usual, remote-friendly.
>>> >>                 3. We would gladly host a hub in Berlin or Munich.
>>> >>                 4. Hubs in other locations are very welcome (London?,
>>> >>                 SF?).
>>> >>                 5. Agenda to be discussed.
>>> >>
>>> >>                 On Mon, Mar 27, 2023 at 6:19 PM Patrick Angle
>>> >>                 <pangle@apple.com <mailto:pangle@apple.com>> wrote:
>>> >>
>>> >>                     The spring has in past years been an incredibly
>>> >>                     busy time for me and my coworker as historically
>>> >>                     we have held our developer’s conference in early
>>> >>                     June (although I do not know when it will be this
>>> >>                     year, I await the public announcement like anyone
>>> >>                     else). So dedicating a full day to anything is
>>> >>                     very difficult until the second half of June most
>>> >>                     years.
>>> >>
>>> >>                     Keen on the idea of another virtual F2F though,
>>> >>                     and scheduling difficulties aside I'd also be
>>> >>                     happy to participate!
>>> >>
>>> >>                     – Patrick
>>> >>
>>> >>                     > On Mar 27, 2023, at 7:13 AM, James Graham
>>> >>                     <james@hoppipolla.co.uk
>>> >>                     <mailto:james@hoppipolla.co.uk>> wrote:
>>> >>                     >
>>> >>                     > On 21/03/2023 10:58, Maksim Sadym wrote:
>>> >>                     >> Good morning dear colleagues!
>>> >>                     >> Last all-day WG meetings were super productive,
>>> >>                     both in Berlin and in Vancouver. And as such, we
>>> >>                     suggest planning another in May or June. We are
>>> >>                     happy to host those who want to attend in-person
>>> >>                     in our offices in Munich or Berlin. Of course it
>>> >>                     will be online-friendly.
>>> >>                     >> We suggest the *4th of May* (/may the
>>> force.../).
>>> >>                     >> Please let us know if you would like to join
>>> >>                     virtually or in-person, and in which location if
>>> >>                     in-person.
>>> >>                     >
>>> >>                     > We're excited about keeping the momentum going
>>> >>                     for BiDi.
>>> >>                     >
>>> >>                     > International travel for a single day meeting is
>>> >>                     quite hard to justify. On the other hand, having a
>>> >>                     full day virtual meeting in the late spring sounds
>>> >>                     like a good opportunity to make more progress, and
>>> >>                     we'd be happy to participate.
>>> >>                     >
>>> >>                     > In terms of date, I think we are quite flexible,
>>> >>                     however it would be good to pick one that works
>>> >>                     for as many WG participants as possible.
>>> >>                     >
>>> >>                     > I also note that there's a W3C TPAC planned for
>>> >>                     September. I hope we're able to organize a
>>> >>                     BTT/WebDriver F2F at that meeting.
>>> >>                     >
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>                 --
>>> >>                 Maksim Sadym
>>> >>                 Software Engineer
>>> >>                 sadym@google.com <mailto:sadym@google.com>
>>> >>                 +49 157 54803490 <+49%201575%204803490>
>>> <tel:+49%201575%204803490>
>>> >>
>>> >>                 Google Germany GmbH
>>> >>                 Erika-Mann-Straße 33
>>> >>                 80636 München
>>> >>
>>> >>                 Geschäftsführer: Paul Manicle, Liana Sebastian
>>> >>                 Registergericht und -nummer: Hamburg, HRB 86891
>>> >>                 Sitz der Gesellschaft: Hamburg
>>> >>
>>> >>                 Diese E-Mail ist vertraulich. Falls Sie diese
>>> >>                 fälschlicherweise erhalten haben sollten, leiten Sie
>>> >>                 diese bitte nicht an jemand anderes weiter, löschen
>>> >>                 Sie alle Kopien und Anhänge davon und lassen Sie mich
>>> >>                 bitte wissen, dass die E-Mail an die falsche Person
>>> >>                 gesendet wurde.
>>> >>
>>> >>
>>> >>
>>> >>                 This e-mail is confidential. If you received this
>>> >>                 communication by mistake, please don't forward it to
>>> >>                 anyone else, please erase all copies and attachments,
>>> >>                 and please let me know that it has gone to the wrong
>>> >>                 person.
>>> >
>>> >
>>> >
>>> >             --
>>> >             David
>>> >
>>> >
>>> >
>>> >         --
>>> >
>>> >         Maksim Sadym
>>> >
>>> >         Software Engineer
>>> >
>>> >         sadym@google.com <mailto:sadym@google.com>
>>> >         +49 157 54803490 <+49%201575%204803490>
>>> <tel:+49%201575%204803490>
>>> >
>>> >
>>> >         Google Germany GmbH
>>> >
>>> >         Erika-Mann-Straße 33
>>> >
>>> >         80636 München
>>> >
>>> >
>>> >         Geschäftsführer: Paul Manicle, Liana Sebastian
>>> >
>>> >         Registergericht und -nummer: Hamburg, HRB 86891
>>> >
>>> >         Sitz der Gesellschaft: Hamburg
>>> >
>>> >
>>> >         Diese E-Mail ist vertraulich. Falls Sie diese fälschlicherweise
>>> >         erhalten haben sollten, leiten Sie diese bitte nicht an jemand
>>> >         anderes weiter, löschen Sie alle Kopien und Anhänge davon und
>>> >         lassen Sie mich bitte wissen, dass die E-Mail an die falsche
>>> >         Person gesendet wurde.
>>> >
>>> >
>>> >
>>> >         This e-mail is confidential. If you received this communication
>>> >         by mistake, please don't forward it to anyone else, please
>>> erase
>>> >         all copies and attachments, and please let me know that it has
>>> >         gone to the wrong person.
>>> >
>>>
>>> --
>>> Henrik Skupin
>>> Staff Software Engineer
>>> Mozilla Corporation
>>>
>>>
>>
>> --
>> David
>>
>

-- 
David

Received on Wednesday, 7 June 2023 10:40:18 UTC