logo

drewdevault.com

[mirror] blog and personal website of Drew DeVault git clone https://hacktivis.me/git/mirror/drewdevault.com.git

2024-04-09-FDO-conduct-enforcement.md (9722B)


  1. ---
  2. title: FDO's conduct enforcement actions regarding Vaxry
  3. date: 2024-04-09
  4. ---
  5. freedesktop(.org), aka FDO, recently banned Hyprland maintainer Vaxry from the
  6. FDO community, and in response Vaxry has taken his case to the court of public
  7. opinion, publishing their email exchanges and writing about it on his blog.
  8. It saddens me to bear witness to these events today. I wrote [in September of
  9. last year][0] about problems with toxicity in the Hyprland community. I
  10. initially reached out to Vaxry to discuss these problems in private in February
  11. of last year. I failed to get through to him, leading to that blog post in
  12. September. I spent some time in the following weeks talking with Vaxry on his
  13. behavior and his community's social norms, again in private, but again, I was
  14. unable to get through to him. Unfortunately, we find ourselves again leaving the
  15. private sphere and discussing Vaxry's behavior and the problem posed by the
  16. Hyprland community once again.
  17. [0]: https://drewdevault.com/2023/09/17/Hyprland-toxicity.html
  18. The fact of the matter is that Hyprland remains a toxic community, enabled and
  19. encouraged by its toxic leadership, namely Vaxry. FDO's decision to ban Vaxry is
  20. ultimately a consequence of Vaxry's behavior, and because he has elected to
  21. appeal his case in public, I am compelled to address his behavior in public. I
  22. hereby rise firmly in defense of FDO's decision.
  23. I invite you to start by reading the two email threads, [one][1], and [two][2],
  24. which Vaxry has published for your consideration, as well as Vaxry's follow-ups
  25. on his blog, [one][3], and [two][4].
  26. [1]: https://web.archive.org/web/20250306212807/https://blog.vaxry.net/resource/articleFDO/RHMails.pdf
  27. [2]: https://web.archive.org/web/20240412194128/https://blog.vaxry.net/resource/articleFDO/lyudeReply.pdf
  28. [3]: https://blog.vaxry.net/articles/2024-fdo-and-redhat
  29. [4]: https://blog.vaxry.net/articles/2024-fdo-and-redhat2
  30. Here's my read on the situation.
  31. The FDO officer that reached out to Vaxry did it after Vaxry's problematic
  32. behavior was brought to her attention by members of the FDO community, and was
  33. acting on her mandate within the FDO conduct enforcement board by investigating
  34. complaints submitted to her by this community. It is not a stretch to suggest a
  35. close relationship between these communities exists: FDO is the steward of both
  36. the Wayland protocol and implementation and the wlroots library, essential
  37. dependencies of Hyprland and sources for collaboration between Hyprland and FDO.
  38. Vaxry and other members of the Hyprland community had already participated
  39. extensively in these projects (mainly in discussions on IRC and GitLab issues)
  40. at the time of the email exchange, in spaces where the code of conduct applies.
  41. The FDO officer duly investigated the complaints she had received and found, in
  42. collaboration with the other members of the FDO conduct enforcement team, that
  43. they were credible, and worrying. There are numerous examples of behavior from
  44. Vaxry that contravenes the FDO code of conduct in several different respects,
  45. and any number of them would be grounds for an immediate ban. Since these
  46. behaviors are concerning, but did not take place in the FDO community, the
  47. conduct board decided to issue a warning in private, stating that if this sort
  48. of behavior was seen in the FDO community that it would result in enforcement
  49. action from the conduct team.
  50. All of the actions from the FDO conduct team are reasonable and show
  51. considerable restraint. Vaxry could have taken it in stride with no consequences
  52. to himself. Instead, he immediately escalated the situation. He construes the
  53. FDO officer's polite and well-reasoned warning as threats and intimidation. He
  54. minimizes examples of his own hate speech by shrugging them off as a joke. He
  55. belittles the FDO officer and builds a straw man wherein her email is an
  56. official statement on behalf of RedHat, and cites a conspiracy theory about
  57. <abbr title="diversity, equity, and inclusion">DEI</abbr> programs at RedHat as
  58. justification for calling the FDO officer a hypocrite. He is insulted on my
  59. behalf that my name was cited in the FDO officer's email in lowercase, "drew",
  60. and feels the need to address this.
  61. The FDO officer responds to Vaxry's unhinged rant with a sarcastic quip
  62. clarifying that it was indeed within the FDO conduct team's remit to ban Vaxry
  63. from their GitLab instance -- I confess that in my view this was somewhat
  64. unprofessional, though I can easily sympathize with the FDO officer given the
  65. context. Following this, Vaxry states that Hyprland will cease all communication
  66. with FDO's conduct team and _ignore_ (emphasis his) any future emails from them.
  67. Finally, he threatens legal action (on what basis is unclear) and signs the
  68. email.
  69. Regardless of how you feel about the conduct team issuing a private warning to
  70. Vaxry on the basis of activities outside of FDO community spaces, the email
  71. thread that ensues most certainly is within the scope of the FDO code of
  72. conduct, and Vaxry's behavior therein is sufficient justification for a ban from
  73. the FDO community as far as I'm concerned. The conduct team cites Vaxry's stated
  74. intention to ignore any future conduct interventions as the ultimate reason for
  75. the ban, which I find entirely reasonable on FDO's part. I have banned people
  76. for far less than this, and I stand by it.
  77. Vaxry's follow-up blog posts only serve to underscore this point. First of all,
  78. he immediately opens with a dog-whistle calling for the reader to harass the FDO
  79. officer in question: "I don't condone harassing this person, but here is their
  80. full name, employer and contact details":
  81. > I do not condone any hateful messages sent towards any of the parties
  82. > mentioned.
  83. >
  84. > Recently I have received an email filled with threats to my inbox, from a
  85. > member of the X.org board, Freedesktop.org, and a Red Hat employee. Their name
  86. > is [redacted].
  87. Moreover, Vaxry claims to have apologised for his past conduct, which is not
  88. true. In lieu of an apology, Vaxry has spent the "1.5 years" since the last
  89. incident posting angry rants on his blog calling out minority representation and
  90. "social justice warriors" in light of his perceived persecution. Meanwhile the
  91. Hyprland community remains a toxic place, welcoming hate, bullying, and
  92. harassment, but now prohibiting all "political" speech, which in practice means
  93. any discussion of LGBTQ topics, though this is largely unenforced. In the end,
  94. the Hyprland community's fundamental problem is that they're all "just having
  95. fun", and it seems that they can't have "fun" unless it's at someone else's
  96. expense.
  97. The FDO team is right that Hyprland's community reflects poorly on the Linux
  98. desktop community as a whole. Vaxry has created a foothold for hate,
  99. transphobia, homophobia, bullying, and harassment in the Linux desktop
  100. community. We are right to take action to correct this problem.
  101. Every option other than banning Vaxry has been exhausted over the past year and
  102. a half. I personally spent several weeks following my last blog post on the
  103. matter discussing Vaxry's behavior in confidence and helping him understand how
  104. to improve, and at my suggestion he joined a private community of positive male
  105. role models to discuss these issues in a private and empathetic space. After a
  106. few weeks of these private discussions, the last thing he said to me was "I do
  107. believe there could be arguments to sway my opinion towards genocide".[^1]
  108. [^1]: Yes, this is taken out of context. But, if you raise this objection, I
  109. struggle to imagine in what context you think this statement can be read
  110. sympathetically.
  111. There's nothing left to do but to build a fence around Hyprland and protect the
  112. rest of the community from them. I know that there's a lot of good people who
  113. use and contribute to Hyprland, and I'm sorry for those of you who are affected
  114. by this problem. But, in the end, actions have consequences. The rest of the
  115. community has no choice but to sanction Vaxry.
  116. And, to Vaxry -- I know you're reading this -- there are going to continue to be
  117. consequences for your actions, but it's still not too late to change. I know
  118. it's humiliating to be called out like this, and I really would rather not have
  119. had to do so. FDO is probably not the last time you're going to be banned if you
  120. don't change course, and it would reflect better on you if you took it on the
  121. chin and didn't post inflammatory rants on your blog -- trust me, you don't look
  122. like the good guy here. You are trapped in an echo chamber of hate, anger, and
  123. bigotry. I hope that you find a way out, and that someday you can build a
  124. community which is as great as your software is.
  125. And, to the FDO officer in question: I'm so sorry that you're at the ass end of
  126. all of this hate and abuse. You don't deserve any of it. You did a good job, and
  127. I'm proud of you and the rest of the FDO conduct team. If you need any support,
  128. someone to talk to, don't hesitate to reach out and ask, on IRC, Matrix, email,
  129. whatever. Don't read the comments.
  130. And on that note, I condemn in the harshest terms the response from communities
  131. like /r/linux on the subject. The vile harassment and hate directed at the FDO
  132. officer in question is obscene and completely unjustifiable. I don't care what
  133. window manager or desktop environment you use -- this kind of behavior is
  134. completely uncalled for. I expect better.
  135. ---
  136. *P.S. The Hyprland community has already descended on me before even publishing
  137. this post, after I called Vaxry out on Mastodon a few hours ago. My
  138. notifications are not full of reasonable objections to my complaints, but
  139. instead the response is slurs and death threats. This only serves to prove my
  140. characterization of the Hyprland community as deeply toxic.*