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

Writing and Coding Isn't Always Enough
Last year we had to assume a role we didn't have before: litigants
Autumn Has Come
Autumn should be exciting in all sorts of ways; it'll also mark our anniversary
IBM Has Taken Control of GNOME
Don't expect a successor to be found any time soon
 
Links 01/09/2025: Fresh Backlash Against Slop and "Norway’s Electricity Crisis is About to Hit Britain"
Links for the day
Links 01/09/2025: Catching Up (Mostly via Deutsche Welle), "Windows TCO" Effect in UK
Links for the day
Gemini Links 01/09/2025: Linguistic Barriers and "Web 1.0 Hosting"
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Sunday, August 31, 2025
IRC logs for Sunday, August 31, 2025
The UEFI 9/11 - Part IV - External Interference
They all seem to be playing a role in crushing Software Freedom and self-determination for users
Links 31/08/2025: Baggage Claim Scams, an Insurrectionist’s War on Culture, and a Sudden Robotics Hype
Links for the day
Gemini Links 31/08/2025: Reviewing Netsurf and Slightly Less Historic Ada Design
Links for the day
Links 31/08/2025: Google Gmail Data Breach and LF Puff Pieces for Pay
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, August 30, 2025
IRC logs for Saturday, August 30, 2025
This is What Google News Has Become
Moments ago
The Slopfarm WebProNews Has Turned Google News Into a Laughing Stock Full of Plagiarism by Slop
If Google News dies of neglect, that's one thing. It's starting to seem like active neglect by Google is a form of participation.
Do What is Moral, as What's Legal Isn't Always Moral
Do what's objectively moral, no matter the costs and the risks
Slopwatch: Google News Assisting Plagiarism and Anti-Linux FUD, Serial Slopper Rips Off Linux-Centric Journalists
This makes the Web a much worse place and lessens the incentive to do journalism
Links 30/08/2025: NVIDIA Fakes Results to Hide a Bubble Already in Implosion Phase, Data Breaches Galore, Important Win for Workers' Union in Canada
Links for the day
Representing and Speaking for Animals
If I ever choose to take this matter to tribunal with animals-centric NGOs on my side, it'll get some press coverage for sure
The UEFI 9/11 - Part II - Campaign of Censorship and Defamation Against Critics
In dictatorships, humour serves an important role. It's tragic.
In Kazakhstan, Yandex Estimated to be 20 Times Bigger Than Microsoft
Bing is measured as down this month
Shutterstock Not Enough? The Register MS Uses Slop Images in Articles (Seemingly More and More Over Time)
Cost-saving trajectory amid office shutdown?
Gemini Links 30/08/2025: Games, PostmarketOS, and Slop
Links for the day
Links 30/08/2025: Imgur Uproar and Many Ukraine Updates (Mediazona Reports Over 200,000 Russians Died for Putin)
Links for the day
How Not to Build Software
code forges that need a Web browser perhaps fill some 'niche' demand
GAFAM and "MATA"
The use of dark humour there hopefully helps illuminate what a lot of "modern" technology became like and how it interacts with human civilisation (to what ends and whose gain)
Birds Are Not "Pests and Vermin", Privacy is Not a Crime, and GNU/Linux is Not 'Hacking Platform'
I could not help but think of Free software analogies
The Sites Should Be Very Fast Again
That issue is now resolved
Flying in 2025
worse than ever before
Activists, Including Technical Activists, Need Not Pursue Affirmation
Techrights doesn't play or participate in a "popularity contest"
The UEFI 9/11 - Part III - Chaos is Scheduled to Happen Second Thursday of September (No Matter What the Microsofters Tell You)
The clock is ticking
Downplaying the Impact of "UEFI 9/11" is a Losing Strategy
we won't publish much whilst on holiday
Government Sites Should Run Free Software
Not proprietary bloatware with buzzwords
LLM Slopfarms Take No Breaks
When people run sites by bots they don't need to worry about "breaks"
GNOME Having a Meltdown Again
Thanks and farewell to Steven Deobald
Gemini Links 30/08/2025: Low Tech and Hunchbin 1.0.6
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, August 29, 2025
IRC logs for Friday, August 29, 2025