|
|
|
|
|
by vertex-four
3361 days ago
|
|
> That information, Garfield says, made it to Drupal's Community Working Group (CWG), which concluded there was no code of conduct violation. Or, from his own writing on the subject: > Eventually that information made it to the Community Working Group (CWG), who concluded "there was no code of conduct violation present for [them] to take any action on". |
|
> Dries, from what I understand, was first informed, without my knowledge, of the matter in early February, by the CWG.
Curious that the CWG referred the matter to him as part of their documented process (i.e. when an issue exceeds the scope of their charter). You may not be inclined to believe a word they say, but at the very least Larry's timeline does not contradict this detail as provided by Megan / Dries:
> The Community Working Group, which is part of Drupal’s governance structure, provided conflict resolution. When it became clear that some of the issues raised went beyond the scope of their charter, they determined that it was appropriate for the matter to be escalated to Dries. This is consistent with their existing policy and process.
The FAQ section on this post provides the clearest timeline from the "other side" that I've seen: https://www.drupal.org/association/blog/working-through-the-...
Regardless, multiple decisions were made before Dries and Larry talked, and it is your characterization of Dries as a meddler who is circumventing a process that I am declaring untrue by anyone's accounting of the facts.
We don't live in a binary world, there are other options here besides Dries abused his power or Dries did everything right... for example, the process itself may be deficient and in need of reform. Before slinging mud, we should at least consider that possibility.