Authoritarian structure in Drupal: a case study

I posted this article in the hope it could contribute to constructive reflection and debate around Drupal's power structure in the current context of governance discussions. I realize though that I don't have the energy for potential acrimony, so I've taken it down.

I'll say simply instead: looking at a moment when a Drupal community member raised questions of lasting import to the project, what can we learn about what's needed to create space for critical perspectives and change?

I'm happy to connect offline with anyone who's interested.

Thanks! Nedjo

Feed: