Is there a feature that you would REALLY like to see get into the next release of Backdrop CMS, but you don't think you have the skills to write the code for it (or maybe you do)? Then consider becoming an advocate for that issue. 

The Backdrop community has been experimenting with an "advocacy" program, in which we ask community members to identify an issue they feel strongly about, and volunteer some time to help push that issue forward. Often times, the key to moving an issue forward is the involvement of a single individual that is willing to:

  • Provide a status/progress summary for the issue during the weekly development meetings
  • If the advocate cannot attend dev meetings (different time zone, other obligations), they can alternatively make sure that the original issue summary is up to date
  • Keep an eye on progress in the issue queue, identify blockers, and look for possible solutions
  • Help identify and recruit volunteers with the skills necessary to remove those blockers
  • Draw attention to the issue in Gitter or on Twitter, for example to request testing and/or feedback

Often times features or pull requests fall off the radar screen of the community and core contributors. Sometimes, it only takes a passionate advocate to get others interested in an issue, and help move it forward. What issue/feature would you like to advocate for during the 1.15.0 development cycle?

Ideally, an issue advocate is able to do the following:

  • Attend our weekly development meetings periodically (at least every 2-3 weeks).
  • Update the issue periodically (every 1-2 weeks) in our Github issue queue.
  • Ask clarifying questions or update the issue summary at the top of the page. 
  • Reach out to others in the community, to ask for help when needed.

How to become an issue advocate:

  1. Look over the list of existing feature requests and pick the one you would like to advocate for (or find/create your own).
  2. Let us know you are interested in any of the following ways:
    1. Show up at one of our weekly development meetings, and express interest in becoming an advocate
    2. Drop into our Gitter channel, and let us know (feel free to ask any questions first)
    3. Use the contact form on
    4. Just post a comment in the relative Github issue.

Currently, we require a new feature to have an assigned advocate before we will milestone it for our next release. Individuals can only advocate for one issue at a time, which means that we can only milestone as many features as we have advocates for.

Remember, advocating for an issue does not mean you have to solve it yourself, only that you are taking responsibility to help move the issue forward. 

What issue do you want to advocate for?


EDIT: While advocates do not need to write the code or solve the problem themselves, they may do so. You may advocate for an issue where you wrote the Pull Request and can solve the problem yourself. In this case, your job as advocate is to write occasional updates and potentially reach out to others when you need assistance with reviews and testing.