As the lead of the Selenium project, I wanted to kick off a new blog serial leading up to the freeing of Selenium 4. During this series, I ’ ll talk all about how the Selenium project works, who is involved, how you—yes, you! —can get involved, and we ’ ll get a surreptitious peek at what ’ s new in Selenium 4. I & # x27; ve been mouth about this off and on for a while, but now the 4.0 release is looming I wanted to start partake in more depth.

In this maiden station, we ’ ll start off with a brief give-and-take about how the Selenium project itself runs and who does what, because that ’ s a really helpful piece to understand how and why things pass the way they do on the project. In future posts, we ’ ll look at the new IDE, and then we ’ ll talking about Selenium 4 in more depth, including the fact that it should be a drop-in replacement for you. I ’ ll also review some new features that we ’ ve contribute to Selenium 4, and talk a bit about the modernized Selenium Grid. So let ’ s get started!

About the Selenium Project

Selenium is an Open Source projection. It & # x27; s run under the aegis of the Software Freedom Conservancy (SFC). The SFC is a radical dedicated to pushing forwards Free and Open Source software. Besides Selenium, they have a handful of project you may have heard of, including Samba, Mercurial and Git. The SFC allows us to focus on writing codification and fixing bugs by plow all the legal and financial stuff we ’ re not good at. They ’ re the ones that help us negotiate contracts for when we require to run SeleniumConf, for representative.

Acting as a bridge between the project and the SFC is the Project Leadership Committee (PLC). Currently, it ’ s make up of Jim Evans, Alexei Barantsev, Marcus Merrell, Manoj Kumar, and myself. What do we do? Effectively, the PLC is about provide a smaller grouping of citizenry for the SFC to talk to when decisions require to be do about funding a conference, or how best to respond to sponsorship accord. Because we like to do as much work in the open as possible, you can observe us on the # selenium-plc Slack channel, and almost every conversation and issue is discussed hither.

One of the key qualifications for being on the PLC is a demonstrated commitment to helping the Selenium project improve and follow, and we recognise that the project is more than just “ code. ” It ’ s a community, and the make up of the PLC reflects that.

The Technical Leadership Committee (TLC) includes the citizenry who set the technical way for the project. If you come over to the Selenium Slack, you can find the # selenium-tlc channel, which is where a lot of the technical conversations pass for the project. The TLC include Jim Evans, Alexei Barantsev, David Burns, Diego Molina, Titus Fortner, and me.

How do you get on the TLC? Although the project governance papers goes into more detail, it can be summed up as simply as someone who ’ s demonstrated technical leaders on the labor, over an extended period of time. Just as with the PLC, being on the TLC doesn ’ t give someone more authority, but they ’ re the ace who can merge PRs, and who can (if require be) commit directly to the tree.

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

Again, the TLC endeavour to do as much employment as possible in the exposed. If you ’ re ever interested in watching the design treatment, or asking why a bit of the Selenium code base is structured the way it is, then arrive and join us in the # selenium-tlc Slack channel. There ’ s normally someone from the task there who ’ ll be able to respond your questions!

I wanted to share how the project work for one elementary understanding: to highlight one of the really important things with Open Source, which is that anyone can contribute! You don & # x27; t need to be drop codification around in order to be contributing, andyou don ’ t need to be specialin order to contribute your time and try.

So patently there & # x27; s the people running the projects and publish code, but we couldn & # x27; t do that all on our own. Every release includes contributions from a potpourri of people, not just the core ontogeny team. Also, we & # x27; re constantly happy to accept patches. If you & # x27; re not quite certain where to start, I recommend you lead to ourGitHub pageand take a look at the project tab. That ’ s where you can see the things that need to be done and what we & # x27; re work on.

The other way to get involve is the way that everyone used to get involved with Open Source, which is by what & # x27; s cognize as “ scratching your own scabies ”. It & # x27; s if there & # x27; s something about the labor, something about the product you suppose could be a little bit better, download the source, edit it, and then send us a PR.

We encourage you to get involved and contribute! On the Selenium website, there is apagethat outlines in detail the steps to join the Selenium squad. Join the Selenium Slack groove to interact with us and ask questions. If you want to discuss something, or if you don & # x27; t understand why the code is written the way it is, feel free to arrive on to that Slack channel and talking to us. Also, if you & # x27; d like to see how the decision fashioning is made, then please do feel free to come on to the # selenium-tlc or the # selenium-plc channels to see those radical. Because we & # x27; re Open Source, we try and do everything in the open.

If you ’ d like to put faces to people ’ s Slack or IRC handgrip, then please billet that there ’ s a regular team meeting every early Thursday on Google Meet at 4:30pm (UK time!) We tend to just natter and discuss everything from the undertaking to the conditions, but that ’ s a great way to get to cognize citizenry a little better!:)

Finally, if you ’ re having fuss getting to clutch with the Selenium code base, then delight do come and ask us for help. We ’ ve done our best to make the on-ramp as easy to take as possible, but the project can seem complicated and daunting when you ’ re become depart. We ’ re here to facilitate!

I trust you savour this presentation to the Selenium project. Succeeding workweek, we ’ ll talk aboutwhy the major version jut to Selenium 4. Stay tuned!

========

Other posts in this series: