When I was first approached about being a Backdrop CMS core committer, I was both humbled and more than a little scared. I'm extremely grateful to the PMC for having the confidence in me to offer me this role in the community, but the amount of responsibility they were handing over made me a bit hesitant. Could I do this? What if I made mistakes? What did they expect of me time-wise? This article aims to pull back the curtain and show how easy (and rewarding) it is to be a Backdrop core committer.
We're excited to have Herb v/d Dool (also known as simply @herbdool on GitHub) join the Backdrop CMS Core Committers team! During the tremendous effort put in by Herb during the Backdrop 1.11.0 release (and before), I noticed again and again how Herb was providing thoughtful, helpful feedback in the Backdrop issue queue. I took the suggestion to make him a core committer to the Backdrop PMC, who approved my suggestion unanimously.
I do not consider myself a coder. My contributions in the issue queues both in drupal.org as well as in the GitHub repository of Backdrop CMS had very little to do with actual code. That was until a few months ago Geoff (a.k.a. @serundeputy) showed me a way to create PRs though the GitHub UI that I find very easy (although not very coder-like).
Sharpening your tools is an important part of any developers life cycle and can help you deliver solid, maintainable sites using best practices, efficiently and on budget. The tools I'll discuss in this post: