Drupal Contributions - A Pragmatic Approach to the Issue Queue

58:37
8
0
0
0
1
Share
Nov 24, 2020

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 and 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 issue queue workflow:
Create an issue
Write a patch
Upload the fix to Drupal.org
Review 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.

Hi! I'm Karim Boudjema, the developer and site-builder of this site.

I was wondering how could I giving back to the Drupal community all what it gave to me during the last 10 years, that's how the idea of this site came to me ... (read more)

Hi! I’m Santiago Rico, the web designer and themer of this site.

When Karim proposed me to design and theme this site for the Drupal community, I accepted immediately because the community is the main reason why I love Drupal so much.