 Can you hear me at the back? Can you hear me at the back? Nope. One, two, three, four, five, 17. I love brain in India. Does that work? Right. Thank you. All right. So we've been having a bug bash for the last two days. Joti. Just at least stand up and smile at people. For those people who haven't met Joti in the bug bash, you've been missing, working with a great person. So she's been diligently helping people, dealing with a bunch of the problems and tracking the bugs. So thank you very much. We have these two beautiful specimens. I think to be a committer on Selenium, you have to have a beard. Or at least to keep committing on Selenium, you need a beard. So Simon and Luke, again, have been in the room for most of the two days, in between photo calls and working on the code base and cursing. Mainly about some of the bugs that have been found, and they'll get into that later on. So we had 21 people registered yesterday, 62 registered by today. So today was definitely the live year of the two days. We had 29 bugs logged and already 15 bugs closed. So pretty fast turnaround from the team, which is great. This is documentation, agile style, I think it's called. So essentially explaining some of the details that we discovered as part of the onboarding of getting people to start working with Selenium 3. So this is actually really important, because there are thousands and thousands of people struggling with these sort of challenges as they're trying to get their test to work with Selenium 3. So here it is as a start and all the details for how we filed the bugs. We did have a virtual team as well working on this, which is also a good encouragement. A bunch of handsome people sitting with the computers, occasionally doing work together. So I'm going to hand over to Luke in a second to explain why we picked these three bugs. There's a mic somewhere. A talky talky mic. Thank you. Thanks actually to everyone who came out to the bug bash. It was interesting at times. But we certainly did appreciate people trying out the Selenium 3 alpha. It was very much an alpha. We're trying to get to a beta release. These three issues are things that were identified by some of the members there that I was not aware of beforehand, and they are barriers to our beta release. And that's why they're pretty important. And I'm glad that these got identified. The second one on the list is what caused Simon to spew profanities all day. And it's fixed now. Simon develops by breaking, and then fixing, and then breaking, and then fixing, and then it's defect driven development. So the top one, I don't believe that's the right one, but that's okay. Okay. So there was an issue with the version in the jar. That's the main one that Simon's been working on. There was an issue with transitive dependencies not getting included appropriately. So we are missing some classes in the main jar that gets distributed. And there was another issue related jar. I'm trying to remember. That's okay. The other things that we've been working on, that Simon and I have been working on, is we've been changing to a buck, our build system to use buck. There's been some minor details in that, especially with publishing to Maven, and I've been working on that all day. One of the main things that we were encountering a lot was the difference in how Firefox driver is in Selenium 3. One of the key things that we're doing is we're enabling by default the Gecko driver. Not everybody understands the implications of that. So Gecko driver is Mozilla's implementation of the Firefox driver to run the automation against that browser. What we have in the open source project, what you have been using, is an extension-based implementation that we have hosted in the Selenium HQ source repo. What is currently in the Selenium HQ repo is only working up to Firefox 46 right now. Many of you have encountered that 47 does not work with it. It's going to continue likely to not work with 47, but it's also not going to work with Firefox 48. So we know that the future of Firefox versions are not going to work with what's currently in the Selenium HQ repo for the driver implementation. That's why we need to move to Gecko. But we've also been encountering many issues with Gecko driver. Not all the APIs are implemented or behavior isn't quite as expected. So everyone be aware, we did find lots of Gecko driver bugs, which are great, but they're also logged against Mozilla itself. So if you are running with Firefox Gecko driver, know that if you log an issue against the Selenium repo, it's going to get closed and you're going to be redirected to log it against Mozilla. So you could save yourself and myself a little bit of time by just, if you're using Gecko driver, log straight with Mozilla. That's about it. Good. Thank you, Luke. So for the people who filed these bugs, I just double checked, this was your very official numbering system. Two, three, five, seven. Dyslexia rules KO. Right. Anyway, for the three people who filed these bugs, if you're in the room, can you put your hand up? You have one, two, two of them. So come forward. We've got a little something to say thank you. And which is your bug, sir? Yeah, my only. Just which is your bug? Actually, I didn't know about the bug. It's on to the time. Good. Thank you. So on behalf of your team, then, can I? Whoa, whoa, whoa, whoa, whoa. No one goes away empty-handed, whether you like it or not. So here are a couple of books. I've been involved in writing both of them. So you're very welcome to these. Take them back to your team. The electronic copies are available for free online as well. So thank you very much. So introduce yourself and which is your bug? I am Abhinav from Gemolto, Noida. And mine was 2357. Good. Well, thank you. That was the one we were arguing about numbers. Thank you very much, then. And we're missing the third person. So we'll sort that out later. Thank you very much, everyone. Playground of applause for Julian Jyoti and the whole Selenium team. I think these are great opportunities for everyone to kind of participate and start contributing. We were hoping as part of the bug bash, maybe we'll end up with few contributors or committers from India. That's something we're still lacking. So maybe we'll try again next year to see if we can make it through to get the commit bit on the project. They exist, okay? There are a handful of committers who have done, had successfully merged pull requests. And there are, I believe, two individuals that have the commit bit that are in or from India. Okay. I was not aware. So that's good to know.