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)
- A laptop
AmyJune HinelineCommunity Ambassador @ Kanopi Studios
I have been an active participant in the Drupal community for 3 years. A self described "non-coder", I have been a top 20 contributor to the Drupal project two years in a row.
Outside of doing "the drups", I enjoy mycology, geocaching, and have a love for air-cooled volkswagens.