Re: [EXTERNAL] Automation Summit in Berlin [action required from implementors by 9 August]

Thanks for the heads up!

Logistics: could you please clarify the time bounds for the meetings?

There will be 6 people for our (Google) side.

Let's add agenda items to the wiki page:
https://www.w3.org/wiki/WebDriver/2022-08-BiDi-Automation-Summit-Berlin


On Thu, Aug 11, 2022 at 10:49 AM David Burns <david.b@browserstack.com>
wrote:

> As Chair I am happy for Selenium members who are not part of the WG to
> join the meeting. There is no value in excluding them. I will discuss with
> Christian about long term being an invited expert.
>
> David
>
> On Wed, Aug 10, 2022 at 9:32 PM Sam Sneddon <gsnedders@apple.com> wrote:
>
>>
>>
>> On 10 Aug 2022, at 21:09, Titus Fortner <titus.fortner@saucelabs.com>
>> wrote:
>>
>> Sauce Labs has reserved a conference room (capacity 18) at the Warschauer
>> Platz WeWork where our office is located.
>>
>> We can provide lunch if we get a headcount. Is this right:
>> Apple: 2
>> Mozilla: 2
>> Google: 5
>> Sauce Labs: 3
>>
>> Also, if this is official, how do we add Christian Bromann as an invited
>> expert now that he no longer works at Sauce?
>>
>>
>> The theoretical answer is “the chair needs to approve any non-WG member”,
>> which I don’t think is a high bar to meet for someone with long-standing
>> contributions to WebDriver and/or Selenium!
>>
>> Do we need an explicit agenda? Hopefully we can focus a little more on
>> the Selenium collaboration bits since it sounds like there will be TPAC as
>> well as another meeting in Europe soon.
>>
>>
>> My suggestion is definitely we lean heavily into Selenium collaboration
>> bits given the timing (and the entire reason for the meeting happening),
>> potentially inviting others if they can/want to attend?
>>
>> /Sam
>>
>>
>> Thanks, I'm looking forward to this.
>>
>>
>> *_____________________________*
>> *Titus Fortner*
>> Sr. Developer Experience Engineer | Sauce Labs <http://saucelabs.com/>
>> Core Contributor | Selenium <http://github.com/seleniumhq/selenium> &
>> Watir <http://github.com/watir/watir>
>>
>> Austin, TX
>> (M) 97-TESTER-98 / (978) 378-3798
>> <https://twitter.com/titusfortner>
>> <https://www.linkedin.com/in/titusfortner/>
>>
>> Sauce Labs <http://saucelabs.com/> | Sauce blog
>> <https://saucelabs.com/blog>
>>
>>
>>
>> On Wed, Aug 10, 2022 at 1:04 PM David Burns <david.b@browserstack.com>
>> wrote:
>>
>>> This was discussed in the meeting today we are going to go ahead with a
>>> WG meeting there. I will get everything in place over the next few days..
>>> Our friends from Saucelabs will need to make sure we have a meeting space
>>> booked, which I think they have already done.
>>>
>>> I will send a later email about a future meeting so we can try get
>>> everyone together in time as there are members who haven't had enough time
>>> to organse getting to Berlin.
>>>
>>> David
>>>
>>> On Wed, Aug 10, 2022 at 9:32 AM Mathias Bynens <mths@google.com> wrote:
>>>
>>>> Now that August 9th has passed, what’s the decision?
>>>>
>>>> On Mon, Aug 8, 2022 at 6:13 PM Brandon Walderman <
>>>> brwalder@microsoft.com> wrote:
>>>>
>>>>> Microsoft won't be able to attend. However, we'd also prefer this as
>>>>> an official WG meeting, or at least one with the notes publicly available
>>>>> so that we can follow any outcomes and discussions.
>>>>>
>>>>> Thanks,
>>>>> Brandon
>>>>>
>>>>> ------------------------------
>>>>> *From:* Philip Jägenstedt <foolip@google.com>
>>>>> *Sent:* Monday, August 8, 2022 4:38 AM
>>>>> *To:* Sam Sneddon <gsnedders@apple.com>
>>>>> *Cc:* James Graham <james@hoppipolla.co.uk>;
>>>>> public-browser-tools-testing@w3.org <
>>>>> public-browser-tools-testing@w3.org>
>>>>> *Subject:* [EXTERNAL] Re: Automation Summit in Berlin [action
>>>>> required from implementors by 9 August]
>>>>>
>>>>> Alright, since Apple would be happier with this as an official WG
>>>>> meeting, we (Google) are good with this. Let's follow up on organizing
>>>>> another WG meeting after this.
>>>>>
>>>>> David, to confirm explicitly, I can confirm that some Googlers can
>>>>> attend, no concerns from us.
>>>>>
>>>>> Best regards,
>>>>> Philip
>>>>>
>>>>> On Fri, Aug 5, 2022 at 8:48 PM Sam Sneddon <gsnedders@apple.com>
>>>>> wrote:
>>>>>
>>>>>
>>>>> > On 5 Aug 2022, at 14:29, James Graham <james@hoppipolla.co.uk>
>>>>> wrote:
>>>>> >
>>>>> > To be concrete, my proposal at this point (which I think agrees with
>>>>> what foolip said) is:
>>>>> >
>>>>> > * The SauceLabs meetup returns to its original scope as a chance to
>>>>> work with Selenium implementors on BiDi support. It is not a WG meeting,
>>>>> just a chance to talk to that constituency and gather feedback on our
>>>>> progress.
>>>>> >
>>>>> > * Since there appears to be interest in a F2F in Europe, especially
>>>>> given the limited in-person attendance at TPAC, we begin the process of
>>>>> planning a formal F2F meeting in Europe. This would not be earlier than
>>>>> October (but could be later; date, location, etc. to be decided among the
>>>>> group).
>>>>> >
>>>>>
>>>>> As mentioned before, we would be much happier with an actual WG
>>>>> meeting, bound by normal W3C participation rules (per Process). Given the
>>>>> relatively close relationship between Selenium and WebDriver, it seems
>>>>> comparatively plausible that non-participants will end up recommending
>>>>> changes to BiDi, and these changes should go through the normal process
>>>>> with license grants etc.
>>>>>
>>>>> Additionally, we still have some concern if the majority of
>>>>> browser-side implementers are represented at the Sauce Labs hosted meeting
>>>>> and the extent to which it may practically become a WG meeting, regardless
>>>>> of the intent.
>>>>>
>>>>> /Sam
>>>>>
>>>>>
>>>
>>> --
>>> David
>>>
>>
>>
>
> --
> David
>


-- 

Maksim Sadym

Software Engineer

sadym@google.com
+49 157 54803490

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.