Freenode scandal mostly seems to boil down to logos
I've spent the past week speaking to many of the parties involved over IRC, E-mail and some social (control) media. In the process I rushed to publishing a number of posts about Freenode, culminating in some videos and articles last week. Those were done in a hurry and with limited consultation (enquiring and reaching out to involved parties). I am extremely saddened to see Freenode coming under an attack which bears many of the same hallmarks I saw in the "cancel RMS" lobby, initiated partly by former FSF insiders (which gave it legitimacy, at least on the thin surface).
"In the same way that “cancel RMS” in 2019 was about some tactless E-mails (seen as insensitive towards victims) and in 2021 “cancel RMS” was all about the man coming back to the FSF’s Board (anger superficially boosted and artificially floated by the set of new claims, shifting to a whole different set of poor-quality accusations)."I've long known about the real owner of Freenode. That owner stayed in the shadows, uninvolved in any direct way. That sort of changed lately when the owner of Freenode wanted to promote his brother's business, Shells, which basically helps raise awareness of GNU/Linux. They liaised with SUSE earlier this month. Shells isn't something I'd personally use; it's not for me. Whether Freenode should be in the business of endorsing Shells, even as a sort of sponsor, is a legitimate ethical question. But it seems like pretty much the whole catastrophe right now boils down to that. In the same way that "cancel RMS" in 2019 was about some tactless E-mails (seen as insensitive towards victims) and in 2021 "cancel RMS" was all about the man coming back to the FSF's Board (anger superficially boosted and artificially floated by the set of new claims, shifting to a whole different set of poor-quality accusations).
This afternoon somebody told me about the "shitstorm" brewing -- something we had anticipated since last week. Long story short, many Freenode volunteers (the word "staff" does not imply salary) created their own alternative to Freenode over at libera.chat (they decided on this domain a long time ago). Interestingly enough, about half of all resignations were announced in a proprietary software platform of Microsoft, namely:
As a result, Mr Lee now has operational control over the freenode IRC network. I cannot stand by such a (hostile?) corporate takeover of the freenode network, and I am resigning as a staff volunteer along with most other freenode staff. We simply do not feel that the network now remains independent after two heads of staff appear to have been compelled to make changes to our git repo for the website[4].
Seemingly by the minute today there are more free software projects leaving the Freenode IRC network and moving to alternative IRC networks or other chat platforms.
The Freenode IRC network has been around for more than two decades and very popular with free/open-source software projects for engaging over development discussions, user support, and more. But now due to a "hostile takeover" and most/all of the volunteer staff leaving the network, projects are scrambling to move to alternative chat platforms.
Posted on Freenode Limited on the morning of May 12, 2021 US PST:
Approximate timeline:
1. Shells sponsors freenode providing 3k/mo.
2. Freenode lists the shells logo.
3. Tomaw's team attacks christel, who had run Freenode since early 2000, and she resigns, unable to deal with the persistent harassment.
4. Rather than allow for a usual grace period after resignation (e.g. as we speak, several resigned former-staffers are still OPd in here), or allow for a reasonable transition from one head of Freenode staff to the next (something reasonable and responsible to do to ensure proper continuity of operations), Tomaw's crew abruptly cuts christel's access while she is asleep that night.
5. Tomaw turns around and asks me a bunch of questions if I'm going to challenge his control. He also says he understands I am the owner. I suggest that freenode needs decentralization and good governance, to prevent the kinds of hasty destabilizing things that have transpired.
6. I hear whispers that Tomaw is up to something and reach out to prawnsalad (kiwiirc) who has nothing but good to say about Tomaw. He schedules a meeting with tomaw and me to mediate.
7. In the meeting Tomaw and I disagree entirely about freenode domain ownership (which we've since come to an agreement on), but we both clearly agree in writing not to make any changes to ownership, governance, or project trajectory until we speak again. I created a document detailing the discussion on April 8 and general plan on Google Docs (dated).
8. Rather than wait until we speak again, Tomaw turns around and changes up the staff and website.
9. Upset that tomaw has renegged on his commitments and acted rashly, prawnsalad says he's not going to deal with tomaw and discussion ends; the mediator drops out.
10. I ask tomaw wtf and he brushes me off.
11. I get a lawyer and tomaw says he understands and is sorry etc and sends me a letter.
12. Meanwhile some other story is being told to the staff that doesn't match the truths listed here.
Given the millions I have injected into freenode thus far, the fact I own it and the fact that I protected the freenode staff with professional legal work and funding when they needed help and they could still lie and slander like this... says a lot about who they are. It saddens me that christel was forced out, and I wish she'd feel safe returning. I'm frustrated that tomaw's hostile takeover seems likely to succeed, in spite of all. I simply want freenode to keep on being a great IRC network, and to support it financially and legally as I have for a long time now.
So this is where we are. I passionately want freenode to survive. I have serious concerns about the stability of the project with tomaw here, given his duplicitious and rash actions. But I also have faith and trust in the freenode staff as a general body. So it's my hope we can resolve this leadership issue. I proposed a way to decentralize freenode in the past and would love to embark on that journey still. Perhaps if tomaw could be forthright with everyone about what's happened, the staff could decide for themselves, but I fear he has been far less than forthright. I do not want to interfere, but I also want to protect freenode from what appears to be a pretty hostile set of moves that I believe threaten the network. This concern might point to larger issues we'll need to address about governance in general, and I'm open to having those discussions and formalizing fair and reasonable processes. But for now in the short term, I would really like to work together to find a resolution to this. Freenode must survive in tact, not torn to pieces.