Public Project Meeting - May 07, 2020

Continuing the series of bi-weekly public project meetings…

Continuing the series of bi-weekly public project meetings, here is the timeline of the meeting held on May 07, 2020 (times are on IST).

Meetings are held on the #selenium-tlc channel on Selenium Slack.

The next meeting will be on May 21, 2020, 4:30 PM CET.

adamgoucher 8:00 PM

alright. welcome back. time for another fortnightly chat about the project.

Simon Stewart 8:01 PM


Diego Molina 8:01 PM


Sri Harsha 8:01 PM


adamgoucher 8:02 PM

some general project statistics; open issues: 391 open pull request: 68 (which is the lowest i think ive seen either of those numbers before)


agenda wise, this is going to be more loosey-goosey than normal as i’m swamped with day job so ignoring things. we’ll see is that is a good thing or not.


any overall announcements? new people on committees, have the commit bit, etc?

Simon Stewart 8:04 PM

I’ve landed the update to OpenTracing, which unblocks me


Next step is to wire the tracing into the Docker support And then pick up the websocket forwarding


(Which, to be fair, is “mostly done”)

adamgoucher 8:05 PM

heh. the last 20% takes the other 80% of the time :slightly_smiling_face:

Simon Stewart 8:05 PM

The Pareto Principle in action


I’d be happy pushing a6 before the next meeting

adamgoucher 8:06 PM

what do we think is missing from a6 now?

Simon Stewart 8:06 PM

It’s been a while since we did a release, and there’s progress in there


I’d dearly love the websocket forwarding, but I can live without it @diemol landed the first work with Fail Safe for some more robustness in the Grid


I think @barancev is also making some progress switching the underlying HTTP engine again

adamgoucher 8:08 PM

looks like there was a bunch of plumbing / dependencies updated in the last week especially with .net and python

Simon Stewart 8:08 PM

@jimevans and @AutomatedTester know more than I do

Jim Evans 8:10 PM

yes, the .NET bindings build using bazel should now work cross-platform. you should be able to run .NET tests using bazel test (with caveats, which i’ve yet to fully document). it kinda works within VS code, but one can for certain develop using Visual Studio 2019 on Windows, and Visual Studio for Mac on MacOS.

adamgoucher 8:11 PM (still breaks my head to write .net code on mac)


what more was needed for the http engine stuff? i thought there was a flag in there already?


or did we change it again, again

Simon Stewart 8:13 PM

The underlying library didn’t support http/2 or unix domain sockets, despite it being possible

adamgoucher 8:14 PM

so do we want/need to wait for that work to be done-ish before doing a6? so far that sounds like the only thing that will be confusing to release partially implemented

Simon Stewart 8:14 PM


adamgoucher 8:15 PM

scans commits in another window

Simon Stewart 8:15 PM

As long as it’s in before we start on the betas, we’ll be fine

adamgoucher 8:15 PM

a question i know we dont have an answer for, but do we have a gut feel for how many more a’s there are before we start the b’s?

Simon Stewart 8:16 PM

The major outstanding features are: websocket forwarding graph-ql support

adamgoucher 8:16 PM

thats not that horrid of a list. its been much worse

Simon Stewart 8:17 PM

We’ve been chipping away at it

adamgoucher 8:18 PM

so if a6 is within the next 2 weeks, do we have a trigger condition for releasing it?

Simon Stewart 8:18 PM

No trigger condition


Other than “someone updates the changelog”, I guess

adamgoucher 8:19 PM

do we want to say ‘a6 is next tuesday’ so that all the maintainers are ready to build and tag everything? (feel like we can’t magically do it all from ci but could be making that up)

Simon Stewart 8:20 PM

The graphql piece is to support the ui, so strictly speaking we don’t really need it, but it keeps things flexible


@AutomatedTester, @p0deje, @jimevans, @titusfortner, @harsha509 Cool with shipping an alpha next week?

Jim Evans 8:21 PM

+1 from me.

Sri Harsha 8:21 PM


Diego Molina 8:22 PM

how are we handling the numbers in JS, JS is already in a7, right?

Simon Stewart 8:22 PM


Sri Harsha 8:22 PM

Yes @diemol . Do you have any suggestions @corevo . He should be releasing the next alpha as i know.

Alex Rodionov 8:23 PM

+1 from me

Tomer Steinfeld 8:25 PM

JS has been in alpha for a long time because of historical reasons

adamgoucher 8:25 PM

ok. so thats covers the bulk of the pressing tech stuff. other stuff that could be discussed; when is the next sfc call? (if its happened in the last two weeks, anything to report) did anyone pick up the ball to talk to miki about the go bindings? seconf india seconf us state of the se-ide into the main repo

Tomer Steinfeld 8:25 PM

I think we can land stable 4.0 together, but I don’t see a reason we should release 4 alphas together

adamgoucher 8:26 PM

(or we can keep talking about js too. but that list is just my remaining things)

Marcus Merrell 8:26 PM

the PLC call happened on Tuesday, it was just me and Jim. We mostly talked about conferences, and we were going to follow up with Simon about the status of the Code of Conduct

Simon Stewart 8:27 PM

Uhh… I thought @AutomatedTester was running with the CoC stuff.

Marcus Merrell 8:27 PM

at this point India is still slated to happen in September, same venue. I don’t know the latest about speakers or progress or anything like that

Simon Stewart 8:27 PM

It’s entirely possible I am mistaken

adamgoucher 8:27 PM

i thought david was on that too

Tomer Steinfeld 8:27 PM

Is there an update from the SFC about the MS store?

Marcus Merrell 8:28 PM

ok, I thought David was on the MS Store issue, and not the CoC, but it wouldn’t be the first time I was mistaken

Diego Molina 8:28 PM

why don’t we take the CoC draft we have, add it to the new site, and iterate on it?

Simon Stewart 8:28 PM

We were going to get a review and some guidance from Sage Sharp

Marcus Merrell 8:29 PM

for Chicago, we’ve got a verbal understanding that the venue will allow us to reschedule the conference for sometime next year with no fees. We’ve already given them a somewhat hefty deposit, and while we could likely fight to get that back, we’d rather just have it next April or October–we’re going to make that decision in late May/early June

Diego Molina 8:30 PM

for the SeleniumConf website, @andrewmkrug has joined the Selenium GitHub org, and he is helping us to push the site code to a private repo

Marcus Merrell 8:30 PM

for the Fall, we’re considering an online-only conference, and we’re waiting for a few pieces of data to come in over the next couple weeks, around TestBash and SauceCon, to gauge how they went, ideas for optimization, pros/cons, do’s don’t’s, etc

Andrew Krug 8:30 PM

was added to #selenium-tlc by Diego Molina.

Marcus Merrell 8:32 PM

I spoke to Deb (from SFC) quite a bit on Friday about tips and pointers for an online-only conference, and I’ve started to develop some opinions for how it should be done. I haven’t yet, however, come up with a firm position on the pricing model for sponsors or attendees–I definitely want to offer all the track sessions/keynotes for free, and offer a paid tier for “something” else, like if people want T-shirts or something else, but it would likely be a model where they pay what they want (to support the project), and the swag they get depends on the tier they buy into


I’m waiting to hear more from Richard Bradshaw before beginning that discussion, probably during our bi-weekly Conference conference call, on May 28th

adamgoucher 8:35 PM

so. CoC — when can we get the review and guidance? if its more than ‘not in may’ we should likely throw it up and start the iteration process

Simon Stewart 8:36 PM

It depends on Sage’s availability, and that of the people working on the CoC

adamgoucher 8:37 PM

(which, sounds like we’re not quite sure of who those are from our end)

Simon Stewart 8:37 PM

Last I checked, @mmerrell, @AutomatedTester, @diemol, @jimevans and I were all interested in being involved


From memory.

adamgoucher 8:38 PM

so the nebulous items seem to be; determine who is actually on the coc stuff

Simon Stewart 8:38 PM


adamgoucher 8:38 PM

doh! no editing. and, determine who is actually doing the ms store stuff


which means, for the next meeting;

  • release a6 (a7 of js)
  • report who is point and who is assisting with the CoC
  • report who is leading the ms store stuff


anyone else have anything they want / need to discuss in public?

Simon Stewart 8:41 PM

I’m good


Though perhaps we should figure out who owns what on that list I hold the build bacon this time

Diego Molina 8:42 PM

maybe we can record how a release is done? and from that I can write docs

Simon Stewart 8:43 PM

I’ll walk you through the process We did have it written up here:

adamgoucher 8:43 PM

from the april 23 meeting, looks like @AutomatedTester is the store person Screen Shot 2020-05-07 at 11.12.57 AM.png Screen Shot 2020-05-07 at 11.12.57 AM.png

David Burns 2 days ago

I am waiting on replies from SFC. I chased up yesterday. Have meeting with MS next week

adamgoucher 8:45 PM

anyone volunteering for CoC lead?

Diego Molina 8:46 PM

ah nice, the release process is written, we “just” need to update it

Simon Stewart 8:46 PM

The java one doesn’t seem wildly inaccurate

adamgoucher 8:48 PM

which means, for the next meeting;

  • release a6 (a7 of js) – simon
  • report who is point and who is assisting with the CoC – tbd
  • report who is leading the ms store stuff - david?

Alexei Barantsev 8:49 PM

sorry to be late, I’m +1 for the next alpha

adamgoucher 8:50 PM

so if there isnt anything else, i say we call this thing done and do it all again in a fortnight.


slack says no one is furiously typing so, see all y’all in two weeks. as ever, if there is something you want discussed, message me directly or just drop it here for us to pickup

Diego Molina 8:53 PM

thank you @adamgoucher!

Simon Stewart 8:54 PM

Thanks, @adamgoucher!

David Burns 9:24 PM

Argh… missed it again!!!


For CoC, I keep dropping the ball on this one. I have been busy with work but hopefully can do something in the next two weeks