Last updated 19 August 2017. Created on 19 March 2014.
Edited by mlhess,, Mindewen, kattekrab. Log in to edit this page.

Here are some hints/tips on how to engage the larger Drupal community with various governance discussions. Please feel free to add your tips here too!

Communication strategy can largely be grouped into the following buckets. Use this as a guide to pick the right strategy and communication mediums for the communication task at hand.

Personal Touch

When feedback is needed by one or more specific individuals, it's best to reach out to them directly, using their preferred communication medium, rather than using a more "broadcast" medium which may be "lossy" for them.

Examples of relevant communication mediums:

  • E-mail
  • IRC (use a "ping" if online; use a "tell" if not)
  • Twitter (only if preferred medium, else this can be seen as publicly harassing)

Day-to-Day Operations

Sometimes information is really only of interest to "insiders" who are closely following a particular topic day-to-day. In this case, it's best to use the existing communication channels those insiders are already following.

Examples of relevant communication mediums:

  • Specific issue queue for the topic at hand
  • Mailing lists/g.d.o groups of choice for the "insider" team (e.g. infrastructure mailing list, Testing and QA group)

Wider Feedback

If interested in receiving some "outsider" feedback on a given change/proposal, one should transition outside of the typical "insider" communication mediums to those used by the specific sub-community/communities they're trying to reach. This type of communication should also generally be followed up with a "personal touch" communication with specific individuals whose feedback is needed, to ensure they got the message.

Examples of relevant communication mediums:

Global Broadcast

For changes or proposals of interest to a large part of the community, we want to follow a communication strategy that reaches as many folks as possible.

Examples of relevant communication medium include all of the above, plus:


For changes that will directly impact a huge portion of Drupal's community, we need to do a global broadcast multiple times and in multiple ways to ensure coverage.

Examples of relevant communication mediums:

  • All of the above, plus:
  • Governance group (all governance group members should have access; if not, ping webchick)
  • @drupal Twitter account (automatically, for posts to that group)
  • Drupal Association newsletter (??? - not sure how to do this)
  • Re-blogging by working group members/prominent community members (reach out via "personal touch")
  • Major Podcasts/blogs: request a plug or presentation slot (reach out via "personal touch")
  • DUG announcements: Communicate large announcements via the DUGs (??? - not sure how to do this)

Repeated at least weekly in different time zones to ensure message is getting out there.

Looking for support? Visit the forums, or join #drupal-support in IRC.