 So, like my note, just thank you all very much for coming. It's fantastic to see you all. This is my third trip to India, and every time it seems to get bigger and better and more well-organized and stuff like that. So thank you, and the Organizing Committee, for all you've done to make this just as spectacular. People at the back, if you want to just come grab a seat. There's some right down near the front. It's really good to see. Oh, look, Manoj is a clicker. So if I'm taking too long to say things, then the slides just move forward. So let's take a look at Selenium over time. And the project has been going now for something like 12, 13 years. It's a fairly ancient project. But in 2014, this is a representative slide showing people that were committing to the main Selenium project. You can see that Alexi was well in the lead with Jason Labor, Jim Evans. I was relatively low down in that because at the time I was working at Facebook and a lot of my work at Facebook had nothing to do with Selenium. And therefore, I couldn't contribute quite as much as I'd been planning to. However, in 2016, I was no longer working for Facebook. And you can see here that I'd managed to leap back up the chart of committers. This was when we were on the path towards Selenium 3. And now we're in 2018. And you can see quite clearly that the project is alive. It's thriving. There's lots of people contributing. There's progress being made, lots of exciting things, which we will tell you more about later today. But one of the things I wanted to highlight was that these four people, and I am... These are the only people who have been contributing to the project since 2014, who have appeared consistently in each of the years that I picked. And that's always a little bit worrying. It's not that worrying, however. I think we're going through these slides a little fast. Breathe. Breathe. It's very exciting, isn't it? So these four people represent the actual owners of some of the components of Selenium. So you've got Jim Evans, who owns .NET, and wrote the Internet Explorer server. Alexi and myself, who work on the Java bindings. And Jason Laver, who is in semi-retirement, is basically driving forward the JavaScript bindings that we have. So these people have been around with the project for a long, long time. If they were employees of a company, the average time that people work for a company is three years. So in a tech company, we would have expected to lose far more people than this over the course of the period of time, just through normal attrition. So it's a real testament to the dedication of these people and the work they put in and the work of the project that they're still here even after all this time. Now we can go to the new one. There we go. So, you know, there I am. I'm a little bit concerned. Sorry. Yeah, we apparently missed the years that I especially contributed. Yeah. Sorry. Was there a reason? Was there a reason for the picking of the years? Yeah. Yes. 2014 was the first Selenium Comp for India. 2016 was the second one. And now we're back in 2018. Just a reminder, I missed all three years. You missed all three years. This time. Yes. Although you almost missed it. Yeah, I almost missed it. To be fair, I almost missed it as well. Yeah, so these years are obviously the years that we've been in India and I thought it would be nice just to sort of have that local connection. 2018 so far. I am worried about the number of people that we have committed to the project, but things like this are really healthy. All these people are almost new to the project. Lucas and Alex obviously, they've been doing a lot of work already. So we're growing slowly the next group of people who will be leading the project. And it's really nice to see that. But if you compare these numbers with the numbers we have for the people who have been long established, they're significantly lower. So progress is slowing even as we start bringing up new members of the project. So, you know, why would we slow? Why would we have this? And why do I worry about where we're going with the project? And really, to answer that question, we need to think about what has changed since we started working on Selenium 13 years ago. It's a long, long time. And taking a step back and thinking, what has changed? Everything has changed. Like, the entire world of IT and tech has moved forward. When we started, if you had a machine which had more than one CPU, that was a powerful machine. When we started, if you had a machine with 16 gig of memory, that was probably a server. When we started, you know, 1024x768 was the standard resolution you would have for a high-res display. When we started, there were no mobile phones that people used to connect to the Internet like we do right now with our iPhones and so on and so forth. And when we started, we didn't realize we would end up here. We didn't realize that the world of tech would move forward, that DevOps would become a thing, that Kubernetes, Docker, AWS were even things that would have been created. We had no idea. And the web was a far simpler world. The web was just static HTML pages. If you were really exciting and dynamic, you might have some JavaScript in it. But the idea of a sort of single-page web app just didn't exist. That had to wait until Google Maps came along. And so the world that we live in is not the world that Selenium started in. And we do our best to move with the times. So if we take a look and we think, you know, how have we moved with the times? And I think one of the first things is, if we go to the next slide, thank you, the W3C WebDriver standard. Now, every year, I don't know how many years. It's six years. I've been standing on this stage saying, very soon we will have a W3C standard for WebDriver. And that finally happened. And you may wonder why I've chosen to highlight this with two photos of gin, one with Simon written underneath it and one with David written underneath it. Is anyone wondering that? I mean, you're very quiet, so I'm going to assume you're just lost in thought trying to consider why this might be. The answer is that the WebDriver working group at the W3C, the testing tools and browser tools working group, when we meet, we have these two-day face-to-face sessions at W3C's annual get-together. And that annual get-together is called TPAC, the Technical Plenary and Advisory Committee sessions. Now, if you've ever been to one of these, you will know they are deeply exciting. Normally, the rooms have no windows. Normally, the meetings go on for two days. Can you imagine a two-day long meeting arguing about the minutiae of how do you do a click or what does it mean to get text or the nature of desire, which is a serious conversation that we had. And after these long-day discussion without fresh air and sunlight, we like to sort of go outside and just have a catch-up and relax socially. We were in Lisbon, and it had been a long and fraught day, and we went for dinner together and we were relaxing and stuff like that. And at the end of dinner, we sort of sat back and it was like, should we just get one drink to round out the evening? Because I think we've done some good stuff and tomorrow is going to be a long day, so just one drink. I was like, yeah, all right. So there we were in Lisbon. We found ourselves a bar. It was hot. It was warm. I thought a gin and tonic would be really nice. Now, in the UK, you order a gin and tonic and you get like a long glass, and that's it. It's not a huge drink. They brought out goblets of gin, like huge palm-sized glasses filled with ice and gin and tonic, and everyone looked at each other and we all ordered gin like at that point. And then whenever we talk to each other and we have something to celebrate, we sort of raise a glass of gin to each other. And it turns out, on the 5th of June, when the specification moved to become a recommendation, David and I were both flying, and so what we did is, when they came along with a drinks trolley and they said, what would you like? Both of us independently, and without talking to each other, should probably get a gin and tonic. And then we each took a photo of it and we each sent each other these photos. So this was our way of high-fiving each other after five years of hard work, with the effort put in not only by the Selenium project, but also the browser vendor. Opera helped kick this process off. Mozilla have done an awful lot. They did the first implementation of the W3C standard, the Gecko driver. And it was a rough road because the specification was still evolving as they were attempting to implement it. I've met a lot of people who sort of had sort of some bumps with those early drivers, but they did their best. And then the Google Chrome team a long time ago came up to me and went, how come the Opera driver is so much faster than the Chrome driver? I sat there and went, well, Opera wrote the Opera driver and my intern, Daniel, who is a genius, wrote the Chrome driver, but he hasn't got direct access to the internals of the browser, so the fact it works as well as it does is a miracle. And I went, hm? And a few days later, there was the Chrome team working with the W3C driver. There's a team at Google working on implementing Chrome driver. I have seen the diffs. They are ready to land. They are doing their W3C implementation coming up. But I think they'll be beaten to the punch by Microsoft, who've released the Edge driver, the Microsoft web driver. The next version of that, which is already available as a preview, implements the W3C standard and the team have been very active in the W3C working group. They've helped move us forward incredibly quickly and they've been very thoughtful and considered. And I think because Microsoft were part of the team that were working with the W3C, Apple felt comfortable to come on board and they have embraced web driver. If you have a recent release of OS X, on your laptop right now, you have Apple's own Safari driver and it ships as part of the technology preview. And if you have the technology preview, I know it's awesome, right? If you have the technology preview right now, you have the preview of Apple's W3C implementation of the web driver standard on your machine. With the next major release of Safari, that W3C standard version will be the one that ships on everyone's operating system. So, I mean, the spec adoption is going really well, I think. I think it is. Not to miss. Dan is right here. He'll be unhappy about it. Are we missing out on the Appium? Oh, Appium? Yes, it is. I forgot about Appium. Right there. Dan, give us a wave. Dan, there is the creator of Appium. If you do any testing on a mobile device, you are likely using probably some version of Appium. It's been an enormous success. And one of the reasons why it's grown is because it's really easy for people to take their experience with Selenium and apply it to the mobile testing. And it's also grown because it's a lovely bit of technology, right? It works. So, Appium adopted the W3C standard. The new actions API has been hooked into various places. And Appium, of course, is not just mobile phones. There's also WinAppDriver, which, again, is developed by Microsoft. And the WinAppDriver has also embraced the W3C standard. So what we're seeing is we're seeing the sort of wholesale migration of the various vendors and the people making these devices and the things that we use from the original JSON wire protocol that we had all those years ago. We've seen the ecosystem has been growing up where we see people develop the driver for testing apps on TV. We've seen no testing apps on TV. Fantastic. A few people. Yeah. Yeah. It's amazing. So, like, to get to where we are right now has been an enormous journey. It's been a lot of fun. But, you know, you can't spend your life looking backwards because that way you never move forwards. And we should be looking to the future. We should be looking to see all the things to help make WebDriver and Selenium move forward. Now, the very first thing we're going to do is continue the work with the W3C. So the Browser Tools and Testing Working Group is going to be meeting in Lyon in France at TPAC. And we're going to be discussing some of the bits and pieces that we need. Yesterday during the fix bug we're coming into workshop my microphone is slowly going. Can you all hear me okay? Good. Okay. Thank you for standing up. Thank you. So, at the fix-a-bug-become-a-committer workshop somebody came up to me and they were asking about logging. Like, how do I get information out of the drivers and stuff like that? It is something we've discussed before and it's something that we felt we didn't have time to put into level one. It is one of those things that we think we should put into level two. There's also enhancements so right now if an element is off the screen there's no way to pull it into view. So you can't say scroll this element into view while in the middle of an action chain. That is one of the things that we want to add. And we also want to add the ability to pause in the middle of the actions which is basically there but it would be nice to expose it in a more pleasant way. And then the other thing that's coming is Cyprus and Puppeteer and stuff like that. A lot of the capabilities they get is because they hook into the Chrome debugging protocol. And there isn't yet a standardized debugging protocol that's shared by all the browsers but there is an effort to head towards that and we would really like it if there was a mechanism in WebDriver the W3C WebDriver to allow that sort of bi-directional communication to allow you to have events be fired by the browser and be received by your client on the local end on your tests. And so one of the discussions we're going to have is around having how do we enable that sort of bi-directional communication. Do you want to touch upon who involves making those decisions with the W3 spec? How to do it? Who is involved? In the W3C working group we have Apple, we have Mozilla, we have Microsoft, we have Google, we have the Selenium project there have been representatives from source labs there before so there's a nice widespread of bits and pieces. And the nice thing is all this work is being done on GitHub. If you go to github.com slash W3C slash WebDriver you can put in pull requests so you as individuals can go here's a feature I really need here's a pull request that describes that feature in great detail and if it's something that gets accepted into the spec by the browser vendors now we'll probably ask you to write tests because who doesn't write tests? Who doesn't write tests? I mean there are some hands going up which I find deeply ironic at this conference. But yeah, I mean there's a way forward for you to have an influence on the direction of the WebDriver specification. So looking forward we have Selenium 3 we really Selenium 3.13 today we are heading towards our PI release 3.14 and we're figuring out what we should do with Selenium 4 and we have a handful of ideas now the main one is a wholesale switch from the old JSON wire protocol which has been around since we invented it 8 or 9 years ago to the new WebDriver W3C protocol the two are very, very similar so the translation is pretty easy to do and as you can see most of the browser vendors have already adopted that protocol so it's something that we should be doing but what you will probably see is when we ship the JavaScript bindings, the Python bindings the Ruby bindings, the .NET bindings they will almost definitely drop support for the old wire protocol and they will only speak the W3C WebDriver protocol I am a stickler for backwards compatibility and the Java libraries have always been where we maintain that backwards compatibility so there will be a legacy protocol Java that we will ship but the Java bindings will also mainly focus on the new protocol and that's going to be kind of fun we're going to be able to delete code we'll be able to move to a newer thing and you'll be able to use the new actions APIs consistently across every browser which I think should be really nice now the really nice thing with changing from one protocol to another is that APIs the things that you write your tests against they remain stable so hopefully the plan is the move from 3 to 4 will just be a drop in replacement you don't need to change anything about code the only thing I would say is that anything that is marked as deprecated will almost definitely be removed as we make that move so although you don't need to make any change now if something is being marked as deprecated it means that we intend to remove it when we move from 3 to 4 but that's part of our process anyway we always deprecate something for one release and then we delete it so we've always had that sort of quite aggressive mechanism for removing things that we think are a bad idea moving forward who here uses Selenium Grid okay quite a lot of hats in the room impressive so Selenium Grid was the original version was written by a Frenchman the second version was also written by a Frenchman Francois Reynard we are now out of Frenchman in the Selenium project so we have to write it ourselves and if you take a look at the code base of Selenium there are actually two trees of code that are married together the first one is the original Selenium server so when you run Selenium in the standalone mode you get that original server when you run it as a hub or a grid you get the the second server which is the grid server and that's configured in such a way to make life easy for you to set up a grid and we ship it as a single jar because from the beginning the vision has always been that the standalone server should be a grid of one machine and that machine is the local machine now we haven't implemented that if you take a look at the code the thing about the Selenium grid code is it is terrifying when it shipped there were lots of thread safety bugs and stuff like that two contributors spent a better part of six to eight months just worked on thread safety issues thread safety issues and making it safe and clean and stable and they managed to do that but the consequence was that people are feeling pretty nervous when they go in and make changes to that code and given these two facts that we have two separate code bases and one of those code bases is pretty terrifying and the other code base is approximately 13 years old what we're doing is we're going through and we're reworking the internals of Selenium grid to make it easier for people to work on and we're trying to keep as much of the existing code as possible it's not a rewrite but it's going to be a refactoring the cleaning up of the internals of that to make it easier, cleaner, nicer to finally bring together that vision of standalone being a grid of one the other thing that we need there's one more thing docker images can I miss that it's been a full day workshop yesterday we had 40 plus people turning out such an amazing set of folks so when we started Selenium like I said a single machine was big and you used to have servers in racks when we released Selenium 2 we had big machines in racks that ran virtual machines and so the habit was we'll have these long running servers and they became the nodes in the grid and they would be able to fire up virtual machines and manage them and stuff like that what's happened since then is containerization and docker right now starting up a new Linux virtual machine on OS 10 is as simple as docker run and away you go we also see the rise of things like Kubernetes and stuff like that it would be absolutely foolish for the Selenium project not to embrace these new technologies that are coming in and these new ways of working that people like to have so the Selenium grid the next version of it will have better support for docker and eventually Kubernetes as well and now we can move there you go when was the last time you looked at the Selenium console when I was happened to see an internet explorer icon on a Linux machine we fixed that we fixed the wrong icon being displayed but if you go and fire up Selenium server or Selenium grid or Selenium node and you go to the host you'll see this page this is the console it looks like it was written in the 90s that's because it was written in the early 2000s and by people who did their best web designers moved forward so one of the things that would be quite nice to do is to refresh this console it's not easy to see how much spare capacity there is on the grid it's not easy to see how many of the sessions are actually in flight getting hold of the configuration behind things we think there's a lot of UX work that could be done to make this a lot more interesting and useful for you for example it would be nice to be able to mark a node as draining so you can take a node out of the cluster replace it, reboot it, do whatever it is you need in a controlled and managed way so refreshing the console is one of the important things that we're aiming for in Selenium 4 and bam who's heard of observability as a concept in DevOps okay who's heard of logging and monitoring logging and monitoring is like one of the building blocks for observability one of the other building blocks is log analysis anyone do log analysis have anyone heard of distributed tracing so as we move to a world where we have microservices you have a request and it flows through one machine to another machine to another machine to the database and probably to various message queues and then it comes back and that's your response and when you're trying to debug this in production that's really difficult you need some sort of flow of control you need to understand what happened and distributed tracing gives you a diagram of okay we started this here went to this machine, this machine, this machine there's a bottleneck here and you can do some analysis so part of observability is this ability to do distributed tracing and it's really useful as grid scale and as you head towards a microservice architecture now we are not a microservice architecture I guarantee you that but that concept of being able to figure out what was the flow of control for this request through my grid is something that's really useful and it's something that we want so as part of the Selenium 4 effort one of the things that's really important to me is that we improve the observability of Selenium so you can hook it into your systems, Datadog StatsD whatever it is, Honeycomb for example they do distributed tracing and you can take a look at various bits and pieces using the normal diagnostic tools you have available for you and that will include doing things like structured logging onto the command line so you can hook into the Elks stack or whatever it is it takes you fancy so better observability is coming in Selenium 4 and there's one other really important thing that we need to do for Selenium 4 Documentation Documentation Documentation is the only part that's been missing all the years and any project success is determined by its value and documentation is one such value where we look forward any new starter will look for documentation to get started and as a Selenium project we have been missing documentation for years you all know we had the seleniumhq.org where we have the Selenium RC documentation still up there and it's around 2014 and Selenium WebDriver is all about so if you go and check out the WebDriver project page it still has a definition about what Selenium WebDriver is apparently it is Selenium 1 plus the WebDriver is equal to Selenium 2 which is what I that was my first comment to the project and it's still up there and we had no one coming up including me to change it up and yes as you see on the screen the Selenium project on GitHub where we are writing a complete fresh refresh documentations and not to mention Paul Paul Grandgine is the main guy who's been putting stellar efforts in bringing up the old documentation and we have been trying to cope up with that and unfortunately we don't have anyone to lead the documentation efforts and also to respond to the pool request and if that's something of interest to you and we look forward to speaking to you contributing to the project Yep Andreas Tolson here who you see leading the charge with the commits works at Mozilla he and Santi who has the second most commits on the new documentation they aren't as active as they used to be they have other things going on in their lives they find it hard to contribute but yeah, if you want to make an impact on the Selenium project this documentation, this refresh documentation is super important so lots of the stuff that we've been working on has been developer focused grids the changes, observability, things like that documentation primarily something that developers will consider but perhaps you could tell us about the next generation of the IDE Yes Selenium IDE or just started with Selenium IDE being your first tool to get into the Selenium ecosystem amazing how many of you miss Selenium IDE now? Interesting, if you ask that question in Europe nobody puts their hands up, they're all a little bit embarrassed but Selenium IDE is such a good way to get started with Selenium Exactly and we have the new Selenium IDE so a bit of a history so we had the old XPI extension in Selenium Firefox as you all know which got its end of life August last year when Firefox had the version 55 where they turned completely out changing the old XPI format into the widely and the more adopted web extensions and there's been no efforts put up and then public tools came up that contributing building a fresh new Selenium IDE TNG the next generation how the name will be changed to be a better name Yeah, we need a better name and there's a screenshot for you how it looks and all these years you have been seeing Selenium IDE only on Firefox and this screenshot for you is on Chrome, yes now you can use Selenium IDE on both Chrome and Firefox and right now it's at an alpha stage so we welcome all feedbacks and we haven't get a proposal and we know a few issues like the exporting the code it's still not right there and we are building up and we almost get 1500 downloads per month which is quite good and all these efforts being led by two gentlemen called Tomer, Stanfield and Dave Heifner if you can give a huge round of applause for them to get them going next we have the demo of the Simon's favorite cheese test it's happening on Chrome got it working it got it working yeah, this is on Chrome if you remember Firefox the Selenium IDE used to be just tied to Firefox now it's a web extension any browser that supports web extension in theory supports the Selenium IDE and I think that's a huge step forward so that's why Manoj pointed out that test was running on Chrome what's new in Selenium IDE? well we have three main distinct features as you see we have the new plugin system so any browser vendors or anyone in the ecosystem can easily plug into the new Selenium IDE you can have your own locator strategy so not to pick about the old legacy it's not a legacy but angular one we had new locators like by.model and all angular elements now you can easily plug in for your own customizable locators right in Selenium IDE with the new plugin system and we have a new command line runner it's not the old HTML based runner so this CLI runner is completely based on Node.js so you will have capability to run all your Selenium IDE tests on your command line using this command line runner which is based on Node.js completely and it does support parallel fonts and it's completely based on WebDriver and not the old school Selenium HTML runner also a demo on how the actual IDE the parallel thing works on the command line we have a high level test suite getting kicked off and actually see the Wikipedia test running that's quick but I do have the screenshots to see what happens so parallel.side society is the new format that we came up with the Selenium IDE parallel.side kick off your tests and as you can see the test coming up here with the current runs marked as runs and then the pass and then we do have total time and all that information and there we go with all the tests being completed so that's about Selenium IDE the next generation so going forward Selenium 4 are we getting back the HTTP status codes in Selenium 4 HTTP status codes I'll certainly give it the consideration it's worth we're not getting status codes how many of you want status codes Marcus put your hand down Marcus Selenium community so it's basically it's a group of concentric circles where we in 2004 where we just started the project from ThoughtWakes you know all the history it basically started with the person and then eventually evolved with a group of people that we saw in earlier slides different people contributing to the project and without which we will not be have awesome sort of people right there in the room so the Selenium committee is all about the users, the developers the browser vendors all in one place I mean I've been working on Selenium since 2006 was when I started on the web drive code and started looking at Selenium 2007 was where we did the original release anyone who knows me will know my attention span is not like 11 years long no one has an attention span but lots of people do I don't the reason why I'm still part of this project is because the community is so lovely and so thoughtful and such a fun place to be if you go to the Slack channels, the IRC channels you'll see people not only talking about Selenium but being friends to each other if someone's having a hard day they'll be offered a hug if someone wants to have a quick vent about something their support if someone's struggling with something again people try and help them and try and do the best things one of the nicest things I've seen on the IRC channel was a poor chap who appeared and he went I've got to write some Selenium tests and people went go and write some Selenium tests and he goes I don't know how to code but my manager tells me I need to do this and the channel worked together and helped him identify the best programming language that he should use helped him get started learning that programming language and helped him start writing Selenium tests in that programming language and as he was writing them they were giving him guidance on how to use page objects here's how you do this and the thing that was really wonderful is several months later somebody else came to the channel and they were in a similar predicament they didn't know how to write Selenium tests they didn't know how to pick stuff and this first person stepped in and he goes I can give you a hand I can help you move forward and I think that's a really lovely thing I love that fact that this is a supportive community where people are nice to each other I also really appreciate the fact it's a diverse community we really try hard particularly with the Selenium conference to represent the fact that the world of IT and the world around us is not just Western European males sitting in rooms you will see that we make a real effort with the Selenium conference towards gender diversity and speak diversity in general and we do a lot of work and one of the things I'd quite like to do is just acknowledge some of the contributions that Indians have made to the Selenium project here are some faces that you may or may not recognize I think you should give them a round of applause so there's AJ who was one of the Java committers he contributed code and helped move that project forward and Kita who's on the program selection committee and the organizing committee for this conference and where would we be without our community these are enormous contributions Krishnan who's active in the user groups who's done a lot of work on various bits and pieces and he's contributed code toward grid so if using Selenium grid there's some Indian code in there that's cool he's been the one man army in the Selenium user group how many of you remember the name Krishnan on the user group they said Krishnan hey there's Pooja who is also on the program selection and organizing committee you know again this conference is our opportunity as a community to meet each other and talk so that contribution is enormous Srinivasan who is the Appium Java client-maintainer does anyone use the Appium Java bindings as Indian code go on there's Taren we've been speaking a lot about how important documentation is to the project that's the way that people sort of come in and they go I've got a problem and then they can read and MX and feel supported and Taren was an ex-committer on that and he's far too modest to put his name on the slide but Manoj as well he's on the project leadership committee the PLC next slide go on then there we go why have you put yourself as a question mark I wanted people to come forward and it could be you and hence the question mark ah Indian contributed as you see of course we have people like Sai Krishnan who's been running the workshop and have different open source projects and of course I would have been missing a few names and yes we need more people and hence the question mark there and we documentation or any such projects that interest you we look forward talking to you Manoj has done an awful lot for the project including he frequently reminds me committing code to the JavaScript bindings in 2017 and we missed that should we go to the next slide yeah okay SFC not to mention here it's a charitable home for the Selenium project it's a it's a neutral home for all the open source projects as you see in the tree there SFC is the group of people who manage all the open source projects so we do have a license on every open source project and you might be wondering what someone breached those license and yes they're part of legal folks who take care of all financials legal administrative issues and those are SFC folks yeah the SFC are dedicated towards open source and making open source better those projects that you see there in tiny writing you can see Selenium on there but there's Git in there there's Boost is part of it as well there are all these key projects in the open source ecosystem who are part of the software freedom and they really help move it forward and two of the key people are Karen and Bradley who are one of the two of the people that help represent the SFC on our project leadership committee so the Selenium project needs to talk to the SFC and the way we do that is not through a massive bun fight but through these five people we have Ashley who who helps organize these conferences Ashley is her major contribution is just making sure that there is a community for the project to be part of there's Jim who is just an absolute whiz if you use .net you're using his code if you use the internet explorer driver you're using his code he's one of those sort of strong steady people that's always there he's also contributed quite extensively to the W3C working group there's our good friend Manoj who has done a little bit of everything I think really code, docs, community project, a conference organizing it's an amazing mixed bag then you have Simon Stewart needs no introduction but a formal introduction we've been here for years and the main man getting behind Selenium 3 getting merged and Selenium 4 coming up and we have Alexi and Alexi is just a hard core Java developer he knows so much about the internals of Selenium and bits and pieces and he's one of the key people driving forward the project now one of the things I'd like to highlight with this leadership committee there are many people who's focused their main contributions around code but two of those people on that committee have nothing to do with day to day coding they have everything to do around building community and stuff like that and so I think it would be good for us to talk about how people can contribute so one of the questions that we see often pop up is how can we contribute well as Simon mentioned contributing code is not the only option we have different forums and options to have you handle around the Selenium ecosystem of course you can revamp the docs we talked about refreshing documentation we're expecting to get it revamped Selenium 4 is released by the way is it next Christmas it's going to be a Christmas a Christmas and yes we can answer questions Christian is a good example and can show people how to use Selenium a lot of people have blogs on Selenium and we do also have an official Selenium blog where we have an opportunity to write so write a guest post flick a flick to them and we will get them published and you can write a blog yes and not only writing docs and blogs right so people who are super active and passionate about organizing yes you can join our workhorse committee so the workhorse committee is the real doc host behind all the conference happening around the world not forget to mention the Ashley we have Marcus we have Andrew we have Anand being the main guy for the Indian conference being the co-chair along with me picking up the program selection Anand pretends to be busy right there yeah and we have Pooja and Ankita you can also join the planning committee with us on doc2s and contributions yes sponsoring not to forget our sponsors without which we will not be having a beautiful conference like this so not to mention with the alphabetical order up the tools browser stack cross browser testing xperi test, micro focus new relics sauce labs and subject 7 so they are all Selenium level sponsors and what do we do with the money that's a good question so the Selenium level sponsors pay towards this conference what do we do with that money well the major thing that we do is we run Selenium we've gone from being once a year organized entirely by volunteers to twice a year with the help of companies to help us make a professional comfortable experience we try and make sure that we can do all sorts of fun things so we help fly speakers over we help provide hotel rooms like this isn't a conference where the speakers are expected to give up their free time and they're not expected to travel here under their own steam we make sure that if you're speaking at the conference that the least we can do is make sure you're here and we poke your hotel room and your flight and organizing these conferences is hugely expensive like just arranging all this time it takes quite a lot of money one of the things we were passionate about from the very beginning was to try and keep the cost as low as humanly possible with the first Selenium conference we ran it literally at break even the idea being that if we were to come to where the people are we should allow the people to come in to the conference and participate and be part of it by having a price that only people who work for Oracle or Microsoft or one of the really big tech companies or the consulting companies can pay we want people who are dedicated and interested to if possible be able to pay for it out of their own pocket if their company won't support them and so keeping that price low is really really important the other thing that we really care about is also the Selenium Fellowship so we came up with the concept called the Selenium Fellowship and the Microsoft project is all about passionate pet projects where we spend our own time not getting paid for it and we do have a lot of features and especially with Selenium we have the W3 spec moving pieces which need a lot of attention and getting the code up merged and we came up with Selenium Fellowship where we wanted someone to make use of the sponsorship money using pieces up and running without being incompered and the first member of the Selenium Fellowship is Simon Stewart and yes he does what do I do so two days every week I set aside trying to work on Selenium and to work on Selenium you will see that the project is moving forward significantly faster than it has done in previous years we are gearing up for Selenium 4 which is going to be a lot of fun I'm also still part of the W3C working group so I still contribute towards that I'm on the IRC channel I answer questions in fact I'm on the IRC channels most days at Slack I say IRC because I am a comudgently old man who doesn't like new things but we mirror that onto Slack so if you are on the Selenium Slack channel I'm also there and when I'm travelling I occasionally fire up the Slack plant and use that so I'm doing my best to support the community and move it forward and I do that two days a week one of the things I'm not very good at is anything to do with user experience and anything to do with design what we did a while ago as the project leadership committee is we paid for a designer to come up with a new look for the project a new branding for the project they've got everything they came up with a new site design which doesn't show up very well on that screen I'm afraid but it looks lovely on a monitor but what we really need is some help transforming these mock-ups and these outlines into a proper site design and we have two choices we could spend some of the project money on that and that would be money well spent I think but if you're a person who feels passionately about design who is happy to come on board and wants to make a contribution to Selenium there isn't about documentation there isn't about code but place to your strengths then maybe coming in and giving us a hand with the site redesign would be really really helpful and we'd really appreciate that you're actually finding this past the actual time I'll be past five minutes of actual time so we should probably finish should we just do these slides quickly yes we do the important thing here the reason why I'm saying we could spend money but we'd like it if it was a contribution from the community if someone came on board is that open source really does depend on people like being part of an open source project like Selenium is a great way to build out a circle of friends a circle of experience and to also make a real positive impact on the work that people do and we can only do that if we do it collaboratively and together there is a real risk in the world of open source of open source just being donations from wealthy companies we don't want everything to just be Google throwing code over the wall we don't want everything being Facebook going here's a nifty thing we wrote and gave out the nice thing about it's more important like handing out those tools has helped move forward we build Selenium on top of Guava which is Google's contribution to open source and we would be lost without that we use infer to find resource leaks and bits and pieces from Facebook so those are really useful tools but open source back in the day used to be about individuals contributing work towards their communities to make those communities bigger and better and brighter and we're in serious danger of losing that and one of the things I really love about the Selenium project is although there are corporate contributions and those contributions are large Apple tools and their work on the IDE the contributions that source labs make in order to help us run our continuous integration tests all those things it's still very much a project led by individuals who are focused on the community and part of that and I'd like to continue growing that community to be larger and better and so now I think thanks for joining us we hope you enjoy a direct conference thanks a lot thank you very much for being here