Selenium Blog

August 13, 2020 by Harsha

Public Project Meeting - August 13, 2020

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

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

The next meeting will be on August 27, 2020, 4:30 PM CET.


Diego Molina 7:58 PM :wave:

  • Here is the agenda for today
  • General project statistics (Previous meeting: 338 open issues, 73 open PRs)
  • Overall announcements? New people on committees, with the commit bit, etc?
  • Improving workflow (Reviewing PRs, Improving design requirements)
  • Selenium Conf website in GitHub org? (README is pending)
  • IDE to the main repo?
  • Users/passwords, access keys, etc… to distribution and release repositories.
  • Anything new to report from the last PLC/SFC call?
  • Conferences. Status for SeConf India & SeConf Chicago?
  • Pending work that needs to be done for Alpha 7?
  • Pending work that needs to be done for the first Beta?
  • Selenium Branding guide
  • Selenium marketing strategy (e.g: Webpack)
  • CoC, next steps?
  • Did anyone talk to Miki about the go bindings? (This topic has been skipped in the previous meetings but it is good to keep it on the agenda so we act on it when we have more bandwidth)

8:00 PM

Let’s start with the 1st item General project statistics (Previous meeting: 338 open issues, 73 open PRs)

8:01 PM

Current statistics 334 open issues, 63 open PRs Next item Overall announcements? New people on committees, with the commit bit, etc? Not that I am aware, anyone else?

David Burns 8:02 PM

No, but I would like to propose to create a new team on github for my team to at least have triage ability on bugs

8:03 PM

I can’t assign bugs unless they are somehow associated to the org

Diego Molina 8:03 PM

That is a good idea, I had the thought of creating a triage team and add people who are helping already in the #selenium channel, like @Salmon Mode :+1:

Simon Stewart 8:03 PM

+1 for a triage team

Diego Molina 8:04 PM

We should add that to the governance model

David Burns 8:04 PM

we can always discuss commit bit for my team at a later stage but I want them in the org

Diego Molina 8:04 PM

as a way to be part of the team without the need of explicitly be a committer

8:05 PM

who wants to take that task? add this to the governance model?

David Burns 8:05 PM

I can

Diego Molina 8:05 PM

:thumbsup:

8:06 PM

next topic? Improving workflow (Reviewing PRs, Improving design requirements)

David Burns 8:06 PM

that’s mine

8:07 PM

I would like to see if there is a way we can get designs for what people want descrribed better in issues I have noticed people misinterpretting requests in bugs that my team are working on

8:08 PM

and I dont know if it’s tribal knowledge that is missing or general experience or what can we get more definitive process for this

Simon Stewart 8:08 PM

“misinterpreting”?

David Burns 8:09 PM

well, we started down the observability issue and there are cases where work was done based on what their intrepretation was and it turned out to be different they didnt have the same context and motivation behind the changes

Simon Stewart 8:10 PM

It really helped when we had a conversation about the event stuff And since I’d planned to do that work myself, it seemed more lightweight not to fully describe everything in the issue

David Burns 8:10 PM

I agree, and I want to see if there are times we can front load that in to the issue rather than go down, write code , it’s wrong, try again

Simon Stewart 8:10 PM

Maybe if we make clear that they’re a placeholder for a conversation and identify who to speak to?

Diego Molina 8:11 PM

what I am missing in general about this, is that the decisions made through conversations in Slack are not being written in the GitHub issues or in the PRs, which makes things hard to review and move on

David Burns 8:11 PM

there is that too

8:12 PM

but having a converrsation requires the person that needs to be spoken to being free which isnt always a realistic expectation due to numerrous factors

Simon Stewart 8:13 PM

True, but front-loading all the design work is also impractical

David Burns 8:13 PM

I guess if we add more context and motivation that would be a good halfway point

8:13 PM

motivation being the main one for me.

Diego Molina 8:13 PM

what we also need to realise is that we did not have something that looked like a roadmap before, Simon helped with his brain dump that turned into the GitHub issues we have for the Selenium 4 release project so we are in a better place than the one we were but I agree that more detail on what is intended in the issues is needed, a natural next step in the iteration :+1:

David Burns 8:14 PM

agreed

8:15 PM

because, and this is my next item, if we can have some more info in issues it’s easierr to review there are changes that I can review and I go for correctness in the java server but it might be the wrong idea and we have PRs that sit, again due to people having lives and can’t always be here

Diego Molina 8:16 PM

do you think we should back to the open issues and find ways to extend them and make them more clear?

Simon Stewart 8:17 PM

Select the subset that are needing clarification and ask?

David Burns 8:17 PM

I have started doing that with some of the next load of work that I want my team to work on my goal, like everyone, is to ship se4

Simon Stewart 8:17 PM

Agreed And I want to help make that happen

8:18 PM

But I’m under some weird time constraints

David Burns 8:18 PM

I know, I am not blaming anyone

Simon Stewart 8:18 PM

I know :slightly_smiling_face:

David Burns 8:18 PM

I just want to make your life easier and my team’s and you’re kinda in both

8:19 PM

so… since code is mutable… can we go with I review for correctness, if it’s wrong and we spot then a new issue is raised with more context/motivation? and I will put it on my team’s stack?

8:20 PM

I feel this issue could raise it’s head with Sauce if they expand their team

Diego Molina 8:20 PM

uh, I need the simple English translation for that phrase

David Burns 8:21 PM

heh… sorry since I can review code, and make sure we have tests. If I feel it’s ok to merge I will, after a few days

8:22 PM

if others in this group disagree with the change, let me know, I will add it to our work and will get it sorted The issue of missing context and motivation could happen to anyone joining this group e.g. Sauce expanding their OSS team

Diego Molina 8:24 PM

got it, thanks for the translation I don’t see any issue with that, I think it makes sense in the end we can always improve things after merging code

David Burns 8:24 PM

cool. there are a few PRs from my team that have been sitting for a while

8:25 PM

and didn’t feel I could merge as I didnt have confidence in the serverr (give me a browser any day)

Diego Molina 8:26 PM

I am finding ways to help a bit more there, but we should follow your suggestion, I would appreciate a comment in the PR before merging it, like “hey, this has been sitting for while, it looks correct to me, I’ll merge it tomorrow unless someone has something against” :+1:

David Burns 8:27 PM

deal and we can get to a stage where my team can review each other which would be even better

Diego Molina 8:27 PM

:thumbsup:

8:28 PM

Next topic? Selenium Conf website in GitHub org? (README is pending)

8:29 PM

Quick update here, Andrew gave me an intro on how to make changes, the setup is more complex than I thought. We are in the process of documenting it. We should in the near future formalise a team in the governance model for the Selenium conference, there is a lot of work happening there that should be more recognised :+1:

8:30 PM

Next topic IDE to the main repo?

8:30 PM

I’ve seen @AutomatedTester and @rajendra moving the IDE repo into bazel, right?

David Burns 8:31 PM

bazel work is hand once that is done we can move it over wholesale I think the bazel work is 40% of packages. Tests still need doing but we’re touch the rough edges of bazel here

8:32 PM

we’ve both been chatting to people on the bazel slack

Diego Molina 8:32 PM

thanks for the update next topic?

8:33 PM

Users/passwords, access keys, etc… to distribution and release repositories. I added this one

8:34 PM

A few weeks ago I changed the way docker-selenium is released, moved it to GitHub actions, since I did not know the password used to push the images to Docker Hub, I had to reset the password and use it there

8:35 PM

which means that I am the only one who has the password now, and I believe this is the case for many other things we have (npm, python and ruby stuff, stores for Google/Firefox etc..) is there a way the ones in the TLC can have access to this information?

Simon Stewart 8:35 PM

We have some of the passwords stored in LastPass

Diego Molina 8:35 PM

and also consolidate it?

Simon Stewart 8:36 PM

We can share out individual credentials as needed

Diego Molina 8:36 PM

the thing is that the “as needed” moment usually comes when the one who has the credentials is not available

Simon Stewart 8:37 PM

That’s why we share them on LastPass :slightly_smiling_face:

Titus Fortner 8:37 PM

We could create a selenium account for Rubygems and share the password, right now it is giving individual accounts permission manually

Diego Molina 8:38 PM

Who has access to LastPass and can give access to all the TLC members?

Simon Stewart 8:38 PM

I do. Everyone in the PLC should have it too

Diego Molina 8:38 PM

I am only referring to credentials needed for releases and so on do we want to have different types of credentials mixed?

Simon Stewart 8:38 PM

(Sinking into a meeting where I need to talk at work. Dropping out of here)

Diego Molina 8:39 PM

Ok, then we can touch this topic again in the next meeting, but we already started it :slightly_smiling_face: Next topic: Anything new to report from the last PLC/SFC call?

8:40 PM

Seems not :slightly_smiling_face: Next topic: Conferences. Status for SeConf India & SeConf Chicago?

David Burns 8:42 PM

@mmerrell or @manoj9788 ?

Diego Molina 8:42 PM

I know India is virtual and there is a schedule already, I think they are figuring out if workshops will be done :+1::skin-tone-4:

Diego Molina 8:43 PM

and I saw that Chicago is officially postponed to 2021

David Burns 8:43 PM

in that case, move this topic to just india and then post that conference drop it from the agenda for a while

Diego Molina 8:44 PM

ok, makes sense next topic: Pending work that needs to be done for Alpha 7? Pending work that needs to be done for the first Beta? I am not sure if there are many updates here

8:44 PM

I think we need to land those PRs that are sitting to move to the last alpha

Marcus Merrell 8:46 PM

Yeah–we’ve moved out all SeConf Chicago meetings until November. We’re working to choose a new date with the venue for next year, and working on language in the contract that will allow us “ultimate cancel ability” if this thing continues to be a problem. We can move that off of the agenda for the time being :+1:

8:47 PM

I don’t have any new information about India - as far as I know there are no changes to the plan

Diego Molina 8:48 PM

thanks Marcus!

8:49 PM

So, I know that the 4 remaining topics in the agenda have no updates, so I suggest we skip them and we end the meeting early what do you think?

David Burns 8:49 PM

fine @mmerrell hey… friendly poke about that draining PR

Diego Molina 8:51 PM

ok, thanks everyone for your time!

Tags

slack meeting tlc

Categories

general governance

Search blog

Categories

Selenium Level Sponsors

All rights reserved, Software Freedom Conservancy