Bonum Certa Men Certa

Comment on the Open Letter to Remove RMS, Based on the GNU Kind Communications Guidelines

Reprinted with permission from Elias Rudberg, original in this Web site

About the Author



This text is not supposed to be about me, but let me start with a few words about my own background. I have been programming one way or another for most of my life. The work on my PhD thesis involved a lot of programming related to the Ergo quantum chemistry program, and later I worked on scientific computing research involving the Chunks and Tasks programming model. Over the years I have become more and more fascinated by the concept of free/libre software and I would really enjoy contributing more to such projects. I support organizations like the Free Software Foundation (FSF) and Software Freedom Conservancy. Recently I made some small contributions to Phosh and the Linux kernel, something I was very proud of.



Why I am writing this



Recently, an open letter was published with the title "An open letter to remove Richard M. Stallman from all leadership positions". Many people have signed the letter; at the time of writing, 61 organizations have signed, and there are 3009 individual signatures.

The open letter has triggered a debate within the free/libre software world, a debate that I find both interesting and important. However, as I read the letter and various responses to it, I imagine that many voices on both sides are coming from a place of anger and outrage. I think more thoughtful communication would be helpful in this situation.

Whatever one might think of RMS or the GNU project, I found the GNU Kind Communications Guidelines to be quite good, and so I was wondering what would be different if the debate were following those rules. Since the open letter sparked the debate and was signed by so many people, I find it interesting to look at the letter itself from the perspective of those guidelines.

Part 1: avoiding personal attacks



Quote from the GNU Kind Communications Guidelines:



"Please do not take a harsh tone towards other participants, and especially don't make personal attacks against them. Go out of your way to show that you are criticizing a statement, not a person."


I think under normal circumstances we all see the wisdom in the above, in general. However, there are parts of the open letter that could be interpreted as personal attacks, depending on the mindset of the reader. One such part of the letter is the following sentence: "He has shown himself to be misogynist, ableist, and transphobic, among other serious accusations of impropriety."

There is a risk that the phrasing in that part of the open letter can be interpreted as assigning those labels (misogynist, ableist, transphobic) to the person, as part of his identity, rather than criticizing specific statements or actions.

The advice in the communications guidelines to "go out of your way to show that you are criticizing a statement, not a person", does not seem to have been followed here. Assuming that the statements in the open letter are based on statements and actions, it should be possible to reformulate that part of the letter to make it more clear that the letter is criticizing certain things RMS has said and done, and reduce the personal focus.

Part 2: avoiding exaggerations



Another relevant part of the GNU Kind Communications Guidelines reads as follows:

"Please respond to what people actually said, not to exaggerations of their views. Your criticism will not be constructive if it is aimed at a target other than their real views."


Again, this is hardly something that would normally be under dispute, most people would agree that it is best to avoid exaggerations when formulating criticism. Looking at the open letter, there seems to be room for improvement in this regard.

"The phrasing "misogynist, ableist, and transphobic" quoted earlier is another example of something that may appear as as an exaggeration to readers of the letter."One specific part of the open letter that risks being seen as an exaggeration is the phrase "his hurtful and dangerous ideology". Even if you (who signed the letter) are convinced that RMS has a hurtful and dangerous ideology, it may be worth considering that readers of the letter may think this is an exaggeration.

The phrasing "misogynist, ableist, and transphobic" quoted earlier is another example of something that may appear as as an exaggeration to readers of the letter.

Turning to the appendix of the open letter, linked to with the sentence "We have detailed several public incidents of RMS’s behavior", that contains references that also risk being seen as unfair exaggerations or misinterpretations. To see a specific example of this, consider the reference number 2 in the appendix of the open letter, which points to a vice.com article. Because the headline of that vice.com article mischaracterizes the actual statements, I worry that this citation will increase the defensiveness of readers who are skeptical of the letter's concerns. To read details about these issues, see for example: Cancel We The Web? and On Stallman.

As the quote from the communications guidelines above says, criticism will not be constructive if it is aimed at a target other than the real views of the people criticized. It would have been better to avoid exaggerations, and to avoid referencing something that is partly false, like the reference number 2 mentioned above. More impeccable citations would go a long ways toward increasing the credibility of the letter.

Moving forward



Turning again to the GNU Kind Communications Guidelines, I think the following part can help us move forward in the current difficult situation:

"If other participants complain about the way you express your ideas, please make an effort to cater to them. You can find ways to express the same points while making others more comfortable. You are more likely to persuade others if you don't arouse ire about secondary things."


This applies here: in the recent debate some people have complained about the way you express your ideas in the open letter, and perhaps they have a point. As discussed above, there are some things about the open letter that could have been better.

Regardless of one's position on any controversy, I believe that more careful constructive presentation of arguments will increase the chance of persuading readers.

Contact



Anyone who would like to ask questions or otherwise discuss this with me is welcome to contact me by e-mail: mail@eliasrudberg.se. I am particularly interested in hearing from those who signed the open letter -- the critique above is directed at the letter you signed, and I would very much like to hear how you respond to it. Please do not hesitate to write to me.

Thanks



Thanks to Aaron Wolf for his review and editorial suggestions.

Recent Techrights' Posts

SLAPP Censorship - Part 136 Out of 200: Lawyers That Get Paid to Mess About
They were already outnumbered and understaffed
 
The Cyber Show on the Slop Bubble
new article about the implosion of the slop bubble
Links 01/08/2026: New York Times Trying to Inflate the Slop Pyramid Scheme (at Cost to Its Own Reputation) and "Iran Appears to Be Blasting Amazon Data Centers Off the Map"
Links for the day
Positive Political Momentum
Daniel Pocock is taken seriously by many people who contact us privately
Google "AI" is Plagiarism, the Case of Richard Stallman (RMS)
Why would anyone choose LLM slop over the originals, curated and fact-checked by domain experts?
Explaining That Software Patents Are Neither Legal Nor Desirable
Many of our readers work in the legal sector
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, July 31, 2026
IRC logs for Friday, July 31, 2026
Gemini Links 01/08/2026: Retirement, Bike Trips, Quake Stuff, Usenet Reborn
Links for the day
Links 31/07/2026: Microsoft Now Says Slop is Bad (LinkedIn Cracks Down on It), LinkedIn Narrows Down Size (No Expansion)
Links for the day
European Patent Office (EPO) Series: From Alicante to Munich: Another Smooth Ride
Campinos is intent on transforming what was originally envisaged as a temporary public office into his own permanent personal feather-bed
Daniel Pocock and the Important Observation About Threats of Cult-Like Behaviours (No Rationality, No Reason, Just "Mob Rule")
It's a threat to Europe's sovereignty
The "PIP Parade" of IBM's Lousy Management, Which Said "Blockchain" Was the Future
In a healthy company such a CEO would be punished for utterly wrong visions and predictions. Not at IBM...
SLAPP Censorship - Part 135 Out of 200: Limited Liability Partnership (LLP) That Does Not Disclose Financial Activities Before August
It certainly looks like they keep losing the remaining women that still exist in the firm
Links 31/07/2026: "Climate Cover-Up Continues" and Pesticides "Cook the Planet"
Links for the day
Datacentre 'Boom' Sceptics Aren't Luddites, They Recognise a Threat to Human Survival (Not Limited to Climate Change)
Archaeologists very well know that no species will survive forever
Microsoft's Claims Are Based on a Big Lie
the bubble is coming to its hard limits
Don't Lose Sight of the Impact of "End of 10" (Vista 10)
GNU/Linux has taken off fast
Microsoft's Debt Continues to Steadily Increase, Not Counting Hundreds of Billions in Secret/Hidden Debt
The mass layoffs will carry on, maybe labelled LITE
IBM is Circling Down the Drain, the 'Growth' Comes From Beancounting Tricks and Salary Cuts
IBM was down 2.17% yesterday
Microsoft's "Headcount" Distracts From How Big a Cull It Had This Month
It also speaks of numbers "[a]s of June 30" though the "buyouts" were effective July 1 and since then well over 10,000 workers have vanished
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, July 30, 2026
IRC logs for Thursday, July 30, 2026
Gemini Links 31/07/2026: Music, Journaling, and Longing
Links for the day
More Fake News From (and for) IBM, Nobody Ever Held Accountable for Fraud
Companies that turn a blind eye to their own corruption end up recruiting more corrupt people and sacking those who object to the corruption
Links 30/07/2026: Smol Document Server and More PalmOS-ing
Links for the day
Links 30/07/2026: Microsoft Refuting Its Own Slop Hype and "Amazon Is Gutting Its Hey Hi (AI) Division" (GAFAM Bubble)
Links for the day
Today The Register MS Published "AI" Spam and Fake Article by "Senior Technical Marketing Engineer"
unethical practices
Cult inquiry parliament leak fallout
Reprinted with permission from Daniel Pocock
Techrights Will Always Protect Sources
Our #1 priority is sources
European Patent Office (EPO) Series: Legal Concerns and Suspicions of Irregularities
complaints submitted to OLAF
The Era of Silence
So stay silent, remain hidden
GAFAM and IBM Dying in Massive Debt, Hence the Mass Layoffs (Increasingly Silent Layoffs That the Media Fails to Mention)
the integrity of this economy is only as good as its leaders or those who govern the market
TheLayoff.com Deletes Comment That Called IBM's Previous CEO, Ginni Rometty, "Gin 'n Tonic"
It is hard to believe the comment was deleted for being a duplicate (in another thread)
The Mainstream Media Continues to Overlook or Intentionally Ignore Hundreds of Billions in Hidden/Secret Microsoft Debt
the issue is that Microsoft's crisis is a lot greater and broader than this
SLAPP Censorship - Part 134 Out of 200: What "Majority Rules" Tell Us About the Litigant
we press on with this series
Overshoot Day Sites That Contribute to the Problem
Some of these are not even accessible (at all) without JavaScript
Microsoft May Have Gotten Rid of 8% of Its Workforce This Month
It's hard to know what's really going on because there's no transparency due to NDAs
Links 30/07/2026: "Age of Irrationality", Google Losing Money, and "House of Ellison is on the Brink"
Links for the day
Gemini Links 30/07/2026: Homeworlds Notes and Manuscript Submitted
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Wednesday, July 29, 2026
IRC logs for Wednesday, July 29, 2026