TL;DR: Both the community and Dries Buytaert, Project Lead, see a need to evolve Drupal community governance. The Drupal Association can help in a support role. We will start by hosting mediated community discussions so everyone around the world can participate, be heard and understood, and share their ideas. Creating a new governance model will take many months and will require an agile approach as we all feel our way through the proper steps. The Drupal Association will continue to find ways to support this process as we all move through it together.


Over the last several weeks, the Drupal Association has been in listening mode — and we still are. We’re hearing community members say they need clarity and understanding, and that our community governance needs to change. As we process what we’re hearing, we want to find the best way to help the community address the issues being raised, within the boundaries of the Drupal Association charter.

The Drupal Association’s mission is to unite the global community to help build and promote the software. We do that in two very specific ways: DrupalCon and We’re determining how best to meet the community’s needs as it relates to these two key community homes. In the near future, I will publish blogs with ideas on how we might address the various needs we are hearing.

Evolving Community Governance

There is one need that we hear loud and clear that we can address today: The community needs support to evolve community governance structures and processes. Both the community at large, and Dries Buytaert, Project Lead, have expressed this need, and we are glad to see this alignment.  

It’s important to note that the Drupal Association has a very limited role in community governance. Our only role in governance stems directly from our charter to manage DrupalCon and

It’s not within our charter to oversee community governance or drive its evolution. The last thing the Drupal Association wants is to step outside of our charter or accidentally take away the community’s agency in self-organizing to create the new community governance model. However, we do want to facilitate forward movement. And so, we can take a support role.

We hear that many in the community want to come together to talk. We can support this by providing a meeting place (both in person and online), and a mediator for community discussions.

We have asked Whitney Hess, a coach who has worked with the Drupal community before, to facilitate and mediate community discussions, where people can come together to talk about current community issues and explore ideas for improved governance. These discussions will start at DrupalCon Baltimore and continue in a series of online meetings, scheduled at different times so members around the world can participate. [see more details below]

To provide transparency for those who cannot attend the discussion sessions, we will post meeting minutes and summaries from each community discussion here:

As facilitator of these community discussions, Whitney Hess will provide a summary to give us a broad perspective on the “voice of the community.” We hope these conversations will ground the community as it begins architecting its new governance model.

Once we have had these discussions we can decide together on the appropriate next steps, and how the Association can help the community continue to move forward, together.

Join Community Discussions

We hope you'll join the conversation as these discussions begin. Again, our overarching aim is to support the community so it can be healthy and continue to thrive. We believe that open conversation is essential to the wellbeing of any community and we look forward to hosting Community Discussions mediated by Whitney Hess. Please join fellow community members to talk through recent community issues and to be part of co-creating Drupal’s new governance model.

Here are the discussions you can join. Please note the ground rules below:

At DrupalCon Baltimore         

Location: Pratt Street Show Office


  • Tuesday, 12-1pm, max 45 participants

  • Tuesday, 2:15-3:15pm, max 15

  • Tuesday, 5-6pm, max 15

  • Wednesday, 2:15-3:15pm, max 15

  • Wednesday, 3:45-4:45pm, max 15

  • Thursday, 10:45-11:45am, max 15

  • Thursday, 1-2pm, max 45

Virtual Meetings after DrupalCon

Sign Up Here:

  • Tuesday, May 9: 4pm EDT / 1pm PDT / 9pm BST / 10pm CEST / 6am +1 AEST

  • Wednesday, May 10: 8am EDT / 1pm BST / 2pm CEST / 5:30pm IST / 10pm AEST

  • Thursday, May 11: 9:30am EDT / 2:30pm BST / 3:30pm CEST / 7pm IST / 11:30pm AEST

  • Friday, May 12: 2pm EDT / 11am PDT / 7pm BST / 8pm CEST / 11:30pm IST

  • Tuesday, May 16: 8pm EDT / 5pm PDT / 10am AEST

  • Wednesday, May 17: 12pm EDT / 9am PDT / 5pm BST / 6pm CEST / 9:30pm IST

  • Thursday, May 18: 3pm EDT / 12pm PDT / 8pm BST / 9pm CEST

Ground Rules for Community Discussions

Key Principles of Nonviolent Communication

  • Responsibility for Our Feelings: We aim to move away from blame, shame, judgment, and criticism by connecting our feelings to our own needs. This recognition empowers us to take action to meet our needs instead of waiting for others to change.

  • Responsibility for Our Actions: We aim to recognize our choice in each moment, and take action based on seeing how it would meet our needs to do so; we aim to move away from taking action based on fear, guilt, shame, the desire for reward, or any “should” or “have to.”

  • Prioritizing Connection: We aim to focus on connection instead of immediate solutions, and to trust that connecting with our own and others’ needs is more likely to lead to creating solutions that meet everyone’s needs.

  • Equal Care for Everyone’s Needs: We aim to make requests and not demands; when hearing disagreement with our request, or when disagreeing with another’s request, we aim to work towards solutions that meet everyone’s needs, not just our own, and not just the other person’s.

  • Self-Expression: When expressing ourselves, we aim to speak from the heart, expressing our feelings and needs, and making specific, doable requests rather than demands.

  • Empathic Hearing: When we hear others, we aim to hear the feelings and needs behind the expressions, even when they express judgments or demands.

  • Protective Use of Force: We aim to use force only to protect, not to punish others or get our way without the other’s agreement, and only in situations where the principles above were not sufficient to meet immediate needs for safety. We aim to return to dialogue as soon as safety is re-established

How These Ground Rules Work

  • Ground rules will be stated at the beginning of each session.

  • If you are not in agreement with the ground rules, please do not participate in the session.

  • If a participant is repeatedly disruptive of respectful, productive discussion, they will be asked to leave; if they do not leave, the session will be terminated immediately.


Jose Reyero’s picture

I'm glad to hear this:

It’s important to note that the Drupal Association has a very limited role in community governance. Our only role in governance stems directly from our charter to manage DrupalCon and

Still I'd say managing the discussion about Drupal Governance is not your role either.

Btw, the "Protective use of force" part sounds really scary, I wouldn't get into those meetings, but I'm not attending the Con anyway, so never mind...

Anyway, I think this is a possitive step ahead overall. 

nod_’s picture

Still I'd say managing the discussion about Drupal Governance is not your role either.

They're not managing the discussion. They're making tools, places, and people available (none of which are free) that community members can use to discuss this very sensitive topic.  They're not forcing anyone to attend or make use of those things. If nobody wants to use what the DA propose, it'd be a shame, but I'm pretty sure they'd be cool with it.

Think of the alternative, people wanting to discuss this but DA doesn't facilitate it… pitchfork time. With everything that went down lately, this is what helping looks like. Thank you to the DA.

jgirault’s picture

Great read, really good news. I second Jose's comments! 

yukare’s picture

Just simple: make something like the php itself does with rfc. Make the decisions to be made by a group of pleople from community, not by dries only, not by people choosen by dries, and not by employes of Acqua only as we have now. But i really doubt that there will be any real change.

Fernando Correa da Conceição

hgurol’s picture

I liked that simplification, thank you !!

Not by Dries, not by people chosen by Dries, not by Acquia employees...

podarok’s picture

Thanks for starting this discussion

I'm sorry for not attending Baltimore's DrupalCon, but I believe in wise of the community. These discussions should bring a new understanding of how the community should behave in the future.

I'd love to participate in these discussions remotely.

Andrii Podanenko
web(uk, en)
personal blog(uk)

gauravmishra7’s picture

All virtual discussions is very difficult for IST timezone to attend. Can we move ro early EST or PST?

soulsesa’s picture

we hope that our participation will be useful . we have so to share ! thank you for this initiative.

wturrell’s picture

Suggest mentioning what software or website is being used to conduct "virtual" discussions so people can get themselves setup/registered if necessary. 

cgmonroe’s picture

As a long time committer and now Apache/DB Project committee member, I think Drupal should look at the ASF model.  Basically it works like this:

It is a meritocracy, if you submit enough patches, write docs, help in support forums enough... an existing member can nominate you and there is a vote to allow membership.

From the members, a Board of Directors is elected.

Officers are appointed by the BoD to 'keep the lights on' (mostly what the Drupal Assoc does).

Each project (e.g. ant, db, httpd, and many more) has "VP" as the lead, and requires at least 3 Project Committee Members (people, including VP, tagged with keeping the project alive and adding committers, vetting and voting on new releases).

The VP is responsible for presenting a regular report (Quarterly I think?) to the board stating what the project has done.  If there is no VP, no report, or no activity in a project for a while, the board can ask that the project community either prove why they stay a project (via vote generally) or become an 'archived' project (via vote or lack there of).

New projects are started in an incubator.  If they are popular enough and have a supporting community, they can be voted up to a standard project.. or in some cases added to a "group project", e.g. the DB project contains Derby, Torque, JDO, and some retired projects.

How would this map to Drupal?  I would think that for core, there could be some each major grouping of components that would have a VP/Project Committee for it.

Major contrib modules would have to have VP and project committee.  

Minor contrib modules who don't have enough community would become 'incubator' modules.

Why would this be good?  Because it will clairify a lot of things.  E.g. who can approve a RTB patch.. the module committee.  Who is responsible for seeing that modules have regular releases... the module commitee + committers.

Also, by having clear labeled positions encourages people to join the community. You're not just a maintaner... your a PCM in the community.  A clearer indication of your support.

Just pointing out a long running working open source governance model that might be considered / modified for us.

A vast majority of stuff done in Drupal is easy...
it's finding the trick that makes it easy that takes Sooo much time.

h2cm’s picture

Governance is something you can't put down or fail to pay attention to - even as peripheral vision. If you do not attend to governance it will sooner or later trip you up. That said, given the cussedness of human nature and 'life', no matter the care we take, we can all find ourselves mid-fall and guilty of a faux pas or more seriously crisis-bound.

This is why in being 'professional' it is helpful to occasionally be reminded, say through continuing professional development and training of legalistic duties, obligations and responsibilities. It's helpful for example to have case studies and examples ('what-ifs') highlighting how, for example, confidentiality and security have been compromised and damage results to integrity that can be personal, ethical, organisational and community-wide in impact.

There is a conceptual framework that might support the community's deliberations on this important and often difficult and sensitive matter? The framework, known as Hodges' model is one of those 2x2 tables beloved of psychologists and management consultants. Please find the model illustrated on the link below:

In the model, the INDIVIDUAL is contrasted with the GROUP. Whatever physical and virtual environments we navigate the POLITICAL domain may (must - as a check on personal governance) raise questions through which individual accountability must be ascribed and subject to ethical and moral consideration. As is often stated in the literature here is a tool that can provide a series of lenses for an overview on some issue or other. The difficulty and 'sensitivity' of this might be disclosure and the nature of this occurrence (in healthcare this is a frequent concern).

The model's horizontal axis draws out the distinction between the person / people AND technology, often referred as the SOCIO-TECHNICAL.

The model is conceptual and can be applied to any situation or context. While developed in healthcare the model is generic in its potential application.

I still aspire to create a web platform using Drupal to explore this model.

In the meantime - I am enjoying the journey and value greatly joining in with this vibrant and welcoming community as I can.

Best wishes in this latest initiative.