Public Project Meeting - January 28, 2021
Continuing the series of bi-weekly public project meetings, here is the timeline of the meeting held on January 28, 2021,5:30 PM CET.(Below times are on IST)
Meetings are held on the
#selenium-tlc channel on Selenium Slack.
Diego Molina 9:17 PM
Yes, here is the short agenda:
- General project statistics (Previous meeting: 262 open issues, 54 open PRs, Current: 252, 35 PRs)
- Overall announcements? New people on committees, with the commit bit, etc?
- Pending work that needs to be done for the first Beta?
- CoC, next steps?
Alexei Barantsev 9:44 PM
can the Bot drop the meeting link to the chat, please, I always forget where to get it…
Diego Molina 9:53 PM
this is the written one
Alexei Barantsev 9:58 PM
awesome! I’m in yet I have nothing to add to the agenda
Diego Molina 10:01 PM
sounds good I’ll ping people around and we can wait a couple of minutes, Simon said he was going to be slightly late
@titusfortner @jimevans @mmerrell @manoj9788 @AutomatedTester @harsha509 @luke
Jim Evans 10:03 PM
i’m not going to be able to make the video chat, but i can contribute here if people have questions. the only thing missing from .NET for beta1 is making CDP work via remote, which i don’t think needs to be in beta1 for .NET.
Diego Molina 10:06 PM
this is just the written one, the video chat is just to hangout, that one is next week
Marcus Merrell 10:06 PM
no status chance on the Chicago conference at this point - still looking at COVID numbers to determine whether or not it’s going to be feasible
David Burns 10:07 PM
Diego Molina 10:07 PM
Marcus are we still looking into an online event, Marcus?
Marcus Merrell 10:07 PM
we can look into that haven’t been to this point
Diego Molina 10:08 PM
I only ask because (I think) it was mentioned last time ok, perhaps we can start, the first topic is: Overall announcements? New people on committees, with the commit bit, etc?
Aside from @luke joining recently, there are no more things to announce, right?
Sri Harsha 10:10 PM
I think luke joined recently!
Simon Stewart 10:10 PM
Nothing that I can think off
Alexei Barantsev 10:12 PM
I support @diemol’s appeal to focus attention to the issue tracker. let’s try to clean it up in view of the forthcoming v.4 release
close all outdated issues and PRs, apply everything that worth applying
Diego Molina 10:13 PM
the work done during the recent week on the issue tracker has been great, hopefully we keep that going
we could jump into the next topic perhaps… Pending work that needs to be done for the first Beta? here is the list I have from the last meeting
Client facing changes:
- Make relative locators return elements sorted by proximity
- Fix Java Module System problems (I think @simonstewart did this already)
- Allow locator strategies to be pluggable Enable fallbacks for commands
- Enable retries of commands where necessary using failsafe
- Get the Grid UI looking nice, and returning useful data (@diemol is working on this)
- Allow locator strategies to be pluggable
- Pipe VNC connectors through the websocket plumbing for live video
Simon Stewart 10:15 PM
Relative locators now sort by proximity I think the Java Module stuff is working I’m working on fallbacks for locators
Alexei Barantsev 10:15 PM
I can confirm that java 9 modules are usable now
Simon Stewart 10:16 PM
Locator strategies are pluggable on the server side Once I get the locator strategies falling back on the local end, I’m fine with shipping the beta
Diego Molina 10:17 PM
we had some issue reports related to the Grid, in most of the cases it is a matter of showing the correct information on the UI and I am working on that
Simon Stewart 10:18 PM
Also there’s a nasty issue with starting a large number of sessions concurrently
Diego Molina 10:18 PM
yeah, I was going to point that one out, https://github.com/SeleniumHQ/selenium/issues/9112 I have not had time to research enough, but most of the results when googling point to: either we are creating too many Netty clients or something is wrong with the way the client is created
David Burns 10:20 PM
Feel free to pull in @Puja Jagani on the sessions one, I know she was looking at one about starting up a grid and things not working
(can’t remember the issue #)
Diego Molina 10:20 PM
that’d be great, I can sync with @Puja Jagani later what do you all estimate for a beta release? 3-4 weeks?
Simon Stewart 10:21 PM
Diego Molina 10:23 PM
ok, I think we do not have more things pending for beta 1? the only topic left is the CoC New
Titus Fortner 10:24 PM
Is this a good time/forum to ask about wiki/docs?
Diego Molina 10:24 PM
Titus Fortner 10:25 PM
Diego pointed me at a couple issues @AutomatedTester created for docs & wiki cleanup things did we have an idea for what we want in the language specific wiki page vs in the docs; and user vs developer focused? The Ruby wiki stuff is way out of date, not even just Selenium 4 things :) just want to know where we should be cleaning it up to
Diego Molina 10:28 PM
are those two different things? language specific things and dev docs? (people who want to contribute to Selenium, what technical steps to follow?)
David Burns 10:28 PM
CoC is still waiting on SFC. New
Titus Fortner 10:29 PM
What we did with Watir was to make the wiki about things devs need to know about the project building/deploying, etc and everything user related went into the documentation oh, heh, looks like we ended up deleting the wiki and sending everything to the website
Diego Molina 10:32 PM
Why do we need a language bindings specific things on the user docs? Do they differ too much on how they work?
Titus Fortner 10:33 PM
So our current documentation has tabs to show the examples in each of the languages the wiki is currently just a big page of examples for using Ruby Selenium (https://github.com/SeleniumHQ/selenium/wiki/Ruby-Bindings)
I guess I haven’t spent much time with the docs anyway, so maybe I should play around and see what makes sense. Didn’t know if anyone else had opinions on any of it. :) Guess not
Diego Molina 10:38 PM
ah ok, that Wiki seems to be duplicating the user docs but some parts of the Wiki could evolve to be part of the user docs
Titus Fortner 10:39 PM
yeah, it’s 2 approaches to organization as well; here’s everything in ruby, vs here’s everything, click the tab for each to see the ruby.
Diego Molina 10:39 PM
I think the 2nd could work well someone needs to take the time and take the contents of that Wiki and put them in the docs
Titus Fortner 10:39 PM
I’ll take a look at what might make sense since now that I no longer have any looming work pressing things for the first time in forever
Diego Molina 10:40 PM
cool thank you
I think that was it for today, right?
Thank you everyone!