If you want to contribute to Drupal but are not sure where to start, or if you are frustrated by a core bug and want to see it fixed, join us in the Bug Smash Initiative!

Prerequisite
None but some familiarity with the Drupal core contribution process would be beneficial.

Outline
In the four years that the Bug Smash Initiative has been active, the number of open bugs in Drupal has actually *fallen* by more than 2,000. This is a truly astonishing achievement by an informal sub-community focused simply on reducing the number of bugs in Drupal core.

In this session, I will give a brief overview of the initiative and how it has been successful. The focus will be on what I consider to be one of the key reasons: a low barrier to entry.

This means that contributions of all types are valued and you can see firsthand the most seemingly minor contributions make a difference. For example, updating an issue summary with steps to reproduce is often enough for a bug to go from >5 years stale to fixed. (And it is often enough to get you a core commit credit!)

Whether you're a coder or not, anyone with Drupal experience can contribute to cleaning up the issue queue. And the satisfaction of seeing a bug fixed is sure to see you stick around for more. Take it from me, having worked on somewhere around 700 core issues, and counting!

Learning Objectives
1. Introduction to core issue queue
2. How to triage a core bug
3. Overview of the many ways to contribute to the Bug Smash Initiative, and core generally
Attendees should be able to attend the community sprint day with a clear idea of how they can participate in a Drupal core issue