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.
For the past 5 years Backdrop has been growing. It's been a slow but steady increase in adoption, contributors, and those involved in core development. It's time we added some new faces to our leadership team. On behalf of the Backdrop Project Management Committee, I'm happy to announce that we have added a new core committer, and 3 new people on the PMC.
Hey folks, I started working on Backdrop not knowing how to participate in a large open source project, and now I'm writing a formal communication to a community! What a ride :D
I'm stepping down from the PMC, my life has pulled me in a lot of directions in the last few years, and I haven't had the time or sanity to be very helpful as a PMC member or a contributor for a while. I'd like to promise I'll be back, but I'm not sure what the future holds; I definitely have the desire and a few ideas I wanted to try, but we'll see.
Before causing any unnecessary concern, I'll say upfront that I am not leaving the Backdrop project, nor leaving my role as a core committer and Technical Lead, nor reducing my involvement. This is merely a pivot in my responsibilities.
Hello Backdrop Community!
Hats off to Mike McCaffrey for his four years of service on Backdrop's Project Management Committee! Mike was a founding member of the PMC and has helped build, shape and promote Backdrop since the earliest days of the project. His BackdropCMS.org account is a whole seven years old as of writing this post, and he's the person who came up with the name Backdrop!