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. Drupal is built through lots of little tasks. Smaller tasks help people increase confidence and gain experience, which, in turn, leads to more contributions. We'll build on each other's strengths to learn how to navigate the issue queue while having fun trying new things.
But how does one become a contributor?
Together we will go through the process of creating an issue, writing a patch, uploading the fix to Drupal.org, reviewing the patch for RTBC (reviewed and tested by the community) and more. We'll even take a look at the upcoming GitLab contribution process because specific tools and processes change over time.
A basic understanding of Drupal and maybe the command line (but not necessary)
AmyJune is an active contributor in the Drupal community.
A self described "non-coder", she has been a top 20 contributor to the Drupal project two years in a row.
As a Community Ambassador, she believes that giving back to an open source project should be easy and fun.
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.