 All right. Good morning, everyone. Thanks for coming to my talk as you can see taking a community initiative from ID to success a Bug smash case study quite would I'm Griff. I'm an agile delivery manager previous next and I also work on the skipper hosting platform Cool Firstly a bit about me few things. I love I've read rock deli sweet chili chips and my great-hound Visto You can see those wonderful things up there She's actually quite happy in that position. She just looks ridiculous But I'm not here to talk about any of that. I'm here to tell you about bug smash So today I'm doing a little case study and initiative. Here's what we're going to discuss Firstly, what is bug smash? then Why does bug smash work and finally how can I get involved and I'd like this to be a little back-and-forth audience interaction type thing today guys So sorry, you're all involved So when you see a big question on the screen shortly, you see a big speaking head emoji I'd love for you to shout it out. So let's try it So in three two one Great everyone's involved good reading. All right Excellent question. Well, it's a community run Drupal initiative set up to smash through bugs in Drupal core Good Yeah, triple's great, but over time a few bugs are appeared in core Well more than a few as of this morning. They're about 6,000 active bug reports for Drupal at all for Drupal 8 and 9 and With that many reports, there are bound to be duplicates or items that are no longer relevant Which in turn makes it even harder for us to find and address real bugs in the platform So our solution is to get in there and smash them Runs them really well Well, it's all run by the hashtag bug smash channel on Drupal Slack We've got shy of just shy of 500 members as of this morning in the channel. We run a few separate streams of work There's the daily triage target, which runs twice a day Once at about 10 a in this time zone and then again later in the day So our friends in the US and EU have something to smash when they wake up So you can see me and we talk left up there We do a little tick when it's been smashed or Actioned and you can see later on in the day. So that's 8 30 p.m. We're now time zone Some EU members jumping on Shout out to bub some act bug smash member lend dude for providing us with this handy bug bingo tool And also the graphs you'll see a bit later on in this presentation There is the community triage meeting which is run by the fantastic quiet one Which picks a theme and dugs dives into a few bugs of that type This is a great opportunity for members to learn about triage and getting buddy bugs ready to be smashed or smashing them before they even It worked on Recently the triage meeting targeted the oldest active bugs in Drupal core. This resulted in a 16 year old bug being fixed and closed Yeah, I Just want to highlight bug smashing by triage is very important while not completely fixing bugs It makes it much easier for team members to pick up the tickets when they're ready So it's testing its descriptions. It's things that are that old and Also, there's the fortnightly triage meeting which runs asynchronously so that all global members can contribute His meetings acts as a good catch up on everything bug smash it updates everyone on progress and sets targets for the next few weeks So if you're not sure about the initiative or want some guidance on what to work on this can be a great place to start But really you can bug smash out what you like You as long as you use the bug smash initiative tag on dripper at all. You're contributing There's plenty of opportunities to get involved as a seasoned rippler You can tackle critical older or much more complex bugs or even mentor others on the daily triage threads If you're a newcomer to the community or to Drupal in general We identified beginner tasks that you can cut your teeth on control core country And there are also tasks without for people without dev skills like me So such as handling comms and just getting the word out like this so Right, yeah, it does So here's a graph showing the number of bugs they'll active in Drupal core in October 2020 This is early in the initiative. We start in about May 2020 and here it is now so So we've got stats which is a really important part not talk about that in a second But you can see the bugs smashed across the board. We've got goals for each of those different types But we're over 6,000 issues and you can sort of see this graph is number of years open for the tickets So if you look jump back and forwards like the first sort of five or zero to five years Openage are greater than a thousand and there's quite a substantial drop across the board. So it's yeah, it works It's really good so Yeah, that's a reduction of over 6,000 bugs. I couldn't get the exact number of years It's dropped. I estimate it to about 25,000 years of rug reports. It's ridiculous Okay, so we've discussed what bug smash is so now it's time for why does bug smash work? That's an interesting question That's much isn't the first initiative of its kind in Drupal and it's still growing after two and a half years So why has it been effective? I want to first say that I'm only a tiny part of this community I'm certainly not the leader. I'm just doing a presentation today So I thought I'd ask everyone else for their perspective So I really did what any product manager would do and I made a feedback form Opinions have were varied as you'd expect of a community this size I received responses from senior and junior Drupal community members and members based in Australia, New Zealand, India EU US it's all over the place. Here are some of the highlights The first question I asked was What works in bug smash? The most consistent response that I got was that it's simple We smash bugs the goal of reducing the overall Float and bad stuff in Drupal core. What's there not to love? But I think it's more than that other members add that it's not just about development Which especially for the older and more complex bugs Which take a lot of time and effort to address This creates a barrier for new members or members with less time and just makes overall core contribution just more difficult Another theme in the responses was education and mentorship So bug smash is a coordinated community I've seen here at mid and junior level Drupal developers They're all tackling similar issues and can easily request support or advice to get things across the line So we're all just working together and we're helping each other out There's also the informal and low commitment nature of the initiative So you can contribute as much or as little as you'd like Members can drop in and to contribute on a topic that they're knowledgeable about and provide support Then drop out without disrupting the overall initiative Are people people with families or if work's going on they can do a ticket or two respond to triage red And then you know them leaving again isn't that big of a deal The second question I asked was what keeps you coming back? So it's been open for two for two and a half years. Why do people keep doing it? The responses were actually similar to what works, which makes sense if it works people keep doing it The responses focused on education So members said that they were learning heaps from the threads the meetings back and forth discussions about the bugs um the community Great group of super smart people Um, we don't have to fix the bugs which makes a progress on the goals and that's a big part of the triage component of bug smash And people just said that it was really fun. So people said that it's their favorite things during Drupal which is quite cute Um, also got feedback that bugs have a discrete start and finish point So they're either they open their clothes. They're fixed or they're not And that's different to a task or a feature which is a much more open-ended and requires a lot of random feedback And finally with a graph of four people like seeing the number go up or at least in this case go down So a big motivator for this community has been seeing actively reported metrics and goal stats each fortnight Well in short the initiative works because of its community tough And the community is effective because of the structure of the initiative They kind of help each other out There are a few different non-demanding extremes of work that provide ways to contribute to Drupal without overtaking your day So you don't need to give your whole life up to this And there's always someone around to point you in the right direction if you get stuck So regularly in threads someone's like I need someone's help from migrates or I need someone's help over this thing You know, there's a bit more and they can help in that Seeing the overall number of bugs in Drupal call motivates everyone everyone likes seeing that graph And it makes real bug the mix means that real bugs are smashed sooner It also skills up members of the community either juniors that are looking to get More into core and overall open source contribution Or senior members looking to work alongside their peers and chip away at a few tickets a week Overall The more people working on Drupal and contributing the better it's going to be for all of us So if you want to start your own start your own Drupal or really any sort of open source contribution community These could be some ideas that you don't want Well, the best thing that you can do is join the The best thing you could do is join the hashtag bug smash channel on the Drupal slack and say hi There's a big explainer page On Drupal.org that has all the info about what we do How it works and when the next meeting will be and just on that next meeting They're open for 24 hours. So it doesn't really matter if you're in this time zone It's running extremely so you can jump in whenever you want And I also want to call that that there's going to be a bug smash Table at friday's code sprint. So if anyone wants to meet people see how it works Work alongside people on bug smash tickets. There'll be a table. I'm not sure who's running it. We'll find out for you and Finally if you have any questions, please come and say hi to me. I'm a round I'm the only person named Griffin here or DM me on slack A special thank you to everyone that contributed to that feedback form. It was really useful And thank you all for listening. Cheers Does anyone have any questions about bugs? Yeah We've really only done it in this in Drupal south around the code sprint tables But I know in Malaysia one of the members did an in-person one I think at Drupal con they did they used the bug bingo tool which we use for the daily tree And it's done the like that So, um, yeah, we could probably show you guys how to do it a bug smash on friday and then you can spread wider if you're interested So what we do It's hard to see it But there's a where the graphs are we've got a single Page that has all the graphs and metrics that are reported each fortnight And right at the top of the page it says give me a random bug And we just go to that every morning and then post it in the slack. So Yeah, it's random and I think the filters are based on active and from dribble eight or nine nine or ten. Sorry Yeah, it's great. Yeah Len dude built that and it was really cool. It's very useful Fantastic. All right. Thank you everyone. Thanks for coming