Today we wrap up this series. If you have any questions about this process, feel free to reach out to me on drupal.org at
Step 7: Repeat steps 4 through 6 until your work is approved.
At this point the process begins again. And remember, once your patch has passed the automated testing, that doesn’t necessarily mean you're finished. Again, if you read my issue you can see several instances where the patch passed, but it wasn’t correct. I received some excellent advice from jhodgdon, and once I really read and understood the SimpleTest module, it was a lot easier to get the patch approved.
Once the patch has passed the automated tests and is approved by other members of the community, the status will be changed to RTBC (Review and Tested By the Community).
Step 8: Get a commit in Drupal core!
At this point, the only thing remaining is for the maintainer(s) of the code to commit it, at which point you will be attributed with a patch to core! I saw the post below in another issue I worked on, and it was beyond thrilling. I’m actually very surprised at how excited I was! It just feels good to give back to this community that has given so much to me.
I hope this helps you contribute to Drupal. My goal was to write the article that I would have wanted to read before I started my first contrib adventure. Good luck, and once you learn the process, keep contributing to Drupal!
The information in this article was imparted to me over the course of several days, by several individuals. I would like to take this opportunity to thank several people for their patience, encouragement, and advice. So, special thanks to my Drupal mentors:
Jesus Manuel Olivas (jmolivas) – Drupal 8 Solutions Engineer at FFW
Clayton “Andrew” Predmore (RoloDMonkey) – Senior Drupal Developer at FFW
Ryan Price (liberatr) – Senior Drupal Developer at FFW
Michael McAuliffe (junipllc) – Drupal Developer at FFW
And extra special thanks to Jennifer Hodgdon (jhodgdon) of Poplar ProductivityWare for her amazing patience and guidance in the issue queue.