Bonum Certa Men Certa

IBM/Red Hat Adds Code of Censorship to an Important GNU Project, GCC (the Compiler), Despite Longstanding Opposition From RMS and FSF (the Origins of GNU)

Same time Red Hat is exposed as having begun to set up more obstructions to cloners of RHEL (bypassing GNU using monetary thresholds):

I am pleased to announce that the GCC Steering Committee has decided to adopt a Code of Conduct (https://gcc.gnu.org/conduct.html) for interactions in GCC project spaces, including mailing lists, bugzilla, and IRC. The vast majority of the time, the GCC community is a very civil, cooperative space. On the rare occasions that it isn't, it's helpful to have something to point to to remind people of our expectations. It's also good for newcomers to have something to refer to, for both how they are expected to conduct themselves and how they can expect to be treated.



Summary: A Code of Censorship (CoC) has just been added* as IBM's siege against community participation accelerates even further (they kick out Fedora volunteers this way since 2020 if not earlier); where does this end? IBM has been doing this step by step via what's left of its Red Hat workforce (they also led the campaign of defamation against Richard Stallman, rms for short, who started GNU 40 years ago); They want RHEL to be another proprietary UNIX and all community either banished or simply driven away

____ * Full original text for preservation purposes:




I am pleased to announce that the GCC Steering Committee has decided
to adopt a Code of Conduct (https://gcc.gnu.org/conduct.html) for
interactions in GCC project spaces, including mailing lists, bugzilla,
and IRC.



The vast majority of the time, the GCC community is a very civil, cooperative space. On the rare occasions that it isn't, it's helpful to have something to point to to remind people of our expectations. It's also good for newcomers to have something to refer to, for both how they are expected to conduct themselves and how they can expect to be treated.

More importantly, if there is offensive behavior that isn't corrected immediately, it's important for there to be a way to report that to the project leadership so that we can intervene.

At this time the CoC is preliminary: the code itself should be considered active, but the CoC committee (and so the reporting and response procedures) are not yet in place. Specific suggestions for improvement are welcome, either on the gcc-patches post or by email to conduct@gcc.gnu.org.

If you are interested in serving on the CoC committee, or would like to suggest someone who you think would be a good candidate, please email conduct@gcc.gnu.org.

GCC Code of Conduct FAQ (https://gcc.gnu.org/conduct-faq.html):

Why not just refer to the GNU Kind Communication Guidelines?

The Guidelines are helpful for establishing the kind of behavior we want to see, but it's also important to have a reporting mechanism to help people feel safe and supported in the community, and to help leadership to hear about problems that might otherwise have escaped their notice.

Shouldn't people try to work problems out between themselves first?

Certainly, in many cases. And we hope referring to the CoC might be helpful then, as well. If the problem is successfully resolved, no report is necessary, though individuals might still want to let the CoC committee know about the incident just for their information.

What about the rights of the reportee?

The CoC committee will get their perspective, and any other available information, before taking any action.

Besides which, we expect the response to the vast majority of incidents to be email asking those involved to moderate their behavior. That has been the experience of other free software projects after adopting a code of conduct: see the Linux Kernel CoC reports for an example.

Is this going to be used to drive out people with "wrong" opinions?

No, this is a code of conduct, not a code of philosophy. And it only deals with behavior within the context of the GCC project; for instance, harassment in private email in response to a public discussion is covered, a social media post about politics is not.

Can I report incidents from before the adoption of the CoC?

Yes. We may take no action if the issue seems to have been resolved, but it can be helpful to have context for future discussions.

My question isn't answered here!

Please also see the Reporting Guidelines (https://gcc.gnu.org/conduct-report.html) and Response Guide (https://gcc.gnu.org/conduct-response.html). If they don't answer your question either, feel free to ask here or email conduct@gcc.gnu.org with any additional questions or feedback.



Recent Techrights' Posts

Legal Letters Are Not Postcards
It seems like intimidation, nothing more
 
IAM Magazine is in Effect Dead, It's Now Fused Into Microsoft's Patent Troll (Which It Has Promoted All Along)
Microsoft-connected patent trolls in Europe [...] Now, in his new job, Wild can use his 'expertise' to help guide blackmail/extortion to better harm Europe's industry
A Huge Proportion of 'Articles' in The Register MS Are Actually Paid Spam of the Communist Party of China, Selling Compromised (for Wiretapping) Technology
The Register MS is having a go at becoming a marketing company or "B2B"
Top Officials Have Just Left Microsoft, Layoffs in Anything But Name
Microsoft's debt is very fast-growing
Local Staff Committee The Hague (LSCTH) Meets "Alicante Mafia" at the European Patent Office (EPO)
Report on meeting with VP1 and his team on 21 April 2026
UbuntuPit (ubuntupit.com) Has Deleted Slop Pages, Its Slopfarm Experiment Has Failed (Like Always!)
Turning one's site into a slopfarm is a death knell
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, May 23, 2026
IRC logs for Saturday, May 23, 2026
The "Next Big" Bonus for IBM's CEO Apparently Comes From American Taxpayers While Veteran IBMers Are PIP'd and RA'd (Laid Off)
the next big thing will be the CEO's bonus
Links 23/05/2026: Starbucks Scraps Disastrous Slopfest, Colbert’s Final ‘Late Show’
Links for the day
Gemini Links 23/05/2026: Poetry, Hobbies, ROOPHLOCH, and More
Links for the day
Government Bailouts Won't be Enough to Save IBM
Bailouts from taxpayers in the US
Links 23/05/2026: Social Media Bans and Demise of Userbase of LLM Chatbots
Links for the day
SLAPP Censorship - Part 85 Out of 200: The United Kingdom's Rating for Press Freedom Has Improved, But We Can Do Even Better
we see the US at #64
Sites Realise That Becoming More Active by Using Bots (LLM Slop) is Self-Destructive
We'll soon (maybe next year) also show that some of the 85+ KG of legal papers sent our way are computer-generated garbage, which might run afoul of some rules
European Patent Office (EPO) Strikes Persist, EPO Management Tries to Give False Impression of "Happy Staff"
EPO is trying to broadcast to the world a totally phony image of itself
Gemini Links 23/05/2026: Patience, LLM Chatbts Being Bad, and Unexpected Computer Surgery
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, May 22, 2026
IRC logs for Friday, May 22, 2026
Links 22/05/2026: Ebola Crisis and Samsung Averts a Walkout With Big Bonuses
Links for the day
The End of FOSSPost (fosspost.org), It Has become an LLM Slopfarm Like FOSSLinux
These sites will never get lucky with slop. These experiments always end badly.
Links 22/05/2026: Inflation Fears and Thailand Tightens Visa Rules for Tourists From Dozens of Nations
Links for the day
EPO Staff Representation Speaks of This Week's Discussion With the EPO's Budget and Finance Committee (BFC) Amid Mass Strikes
The Central Staff Committee's outline (prepared in a rush) or the "flash report"
SLAPP Censorship - Part 84 Out of 200: New Legislation Against SLAPPs on the Way (After We Reached Out to Ministers)
They dealt with the matter individually too, but we won't share this in public, at least not at this time
The Corrupt Lecture the Non-Corrupt - Part XXX - Where Was "The Ethics and Compliance Team" When the Family of EPO President Campinos Was Caught Doing Cocaine?
It remains to be seen if national delegates will tolerate this in future meetings
Gemini Links 22/05/2026: Esperanto Music History, Suspicious Adoption of Signal, and Unauthorised LLM Slop in Code
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, May 21, 2026
IRC logs for Thursday, May 21, 2026