Drupal Contributions - A Pragmatic Approach to the Issue Queue
Come for the code, stay for the community.
Drupal thrives on community contributions in the form of patches and documentation to both contributed modules and core. This helps the project move forward and stay relevant.
Not everyone who works on open source projects is a senior developer. Smaller tasks help people increase confidence and gain experience, which, in turn, leads to more contributions. Code is very important, but so are all the other parts. Contributing back to Drupal helps folks to become better developers. A more polished Drupal leads to a better overall experience.
But how does one become a contributor? Together we’ll discuss what we can do as a community to help foster new contributors and keep the ones we already have.
There will also be a lightning round demonstrating the process of creating an issue, writing a patch, uploading the fix to Drupal.org, and then reviewing the patch for RTBC (reviewed and tested by the community). We'll even take a look at the upcoming GitLab contribution process, because specific tools and processes change over time.
I am a Support Admin and Community Ambassador for Kanopi Studios. I have been an active participant in the Drupal community for almost 3 years by contributing to projects and helping with documentation.
Other Gems and Oddities include but aren't limited to:
• I am the youngest of five sisters and have survived, proving I am either good at communicating or at talking myself out of deadly situations.
• I eat with my elbows on the table.
• I like to think that I can play the guitar, but mostly I have my headphones on while listening to someone better and imagining its me.