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

Freedom, Not Fame, is His Goal
pursuit of money can be not only tiring but also involve abandoning one's freedom
Getting Better After 20 Years
Exactly two months from now this site is turning 20
 
Microsoft's Silent Layoffs Are the New Normal at Microsoft
Microsoft has a ton of layoffs all the time, but the media isn't mentioning those as no WARN notices get issued
SLAPP Censorship - Part 175 Out of 200: Implicit and Explicit Coalition Against the UK's SLAPP Industry
SRA recognises the problem
Further Transparency Problems at the EPO
The EPO was never meant to be profitable
Gemini Links 08/09/2026: "Everything Must Go", Announcing Perigee, and Presentations in a Browser
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Monday, September 07, 2026
IRC logs for Monday, September 07, 2026
Alleged Manager at IBM Says "[t]here are likely to be a lot (and I meant, A LOT) of RAs before December."
"We’re getting pressure from above to put some team members on PIPs."
Links 07/09/2026: Amazon Cargo Plane Crash, .org/.net/.com Domains Considered Risky
Links for the day
Gemini Links 07/09/2026: Cheese, Text-based Life, and Icons in Swaybar
Links for the day
Links 07/09/2026: Slop Trashes Memory of Parton, Flock Surveillance Infuriates Everyone
Links for the day
EPO Hiding Cocainegate and Abandoning Transparency (Even Access to Very Basic Information is Denied)
The EPO isn't just becoming like a private for-profit corporation. It's also becoming more secretive.
Richard Stallman Has Resurrected Lost Updates
We didn't ask about it
SLAPP Censorship - Part 174 Out of 200: Cascading Scandals and a Path Towards Much-Needed, Long-Awaited Reform
Reform the UK's law, not "Reform UK"
EPO's Gema Requena Sempere (PD People) Contacted Regarding Children With Disabilities
In the coming week we may be in fruitful contact with some media regarding EPO scandals
Over at Tux Machines...
GNU/Linux news for the past day
Gemini Links 07/09/2026: Music Composition, Free Stuff, and Self-hosting Git Repos
Links for the day
IRC Proceedings: Sunday, September 06, 2026
IRC logs for Sunday, September 06, 2026
People Who Enforce the GPL Banned From Linux Foundation Board (After Bribes From Prolific GPL Violators), Now They're Banned From Giving Talks at Events
about the "LF" ('Linux' Foundation)
Gemini Links 06/09/2026: The Slop Plagiarism 'Holy War' (Hype, Scam, Scheme), Burning CD-Rs, and Hardcopy Mono
Links for the day
Solicitors Regulation Authority (SRA) Inaction and Incompetence - Part IV - Insufficient Resources in the Face of Distributed Denial of Service (DDoS) by Lawyers
it's about 120KG
OpenStreetMap is the Future, Dictatorship is the Past
OpenStreetMap helped us check maps for transport, various overlays with addresses, and there was 0% reliance on GAFAM or "Google" anything
Silent Layoffs, Cool-down, and Cool-off: How GAFAM and IBM Operate (the Law Doesn't Apply to Them)
Laws? What laws?
How Strikes at the European Patent Office Are Seen by Striking Staff in Berlin, Germany
We have some more EPO scandals to cover later this year and next year
Association for Computing Machinery Cites Techrights in Relation to GemText and Gemini Protocol
published yesterday, Open Access
Links 06/09/2026: More XBox Trouble (Microsoft Unrest, Many Silent Layoffs This Month), John Duffy as Next USPTO General Counsel
Links for the day
Gemini Links 06/09/2026: Avoiding 'Smart' 'Phones' and Setting up Gemini for the First Time
Links for the day
Links 06/09/2026: Sabotage by Slop and "What Happens If 'Open' 'AI' Dies?"
Links for the day
How Back Doors Became the 'Normal' or 'Norm'
"We also allowed a lethal monoculture to fester"
Solicitors Regulation Authority (SRA) Inaction and Incompetence - Part III - The SRA is Vastly Worse Than Brits Realise, We Have a "Wild West" in London
In the next part we'll begin looking at correspondence with the SRA
SRA and Manslaughter: How the SRA Contributed to Agony in Proprietary Software Scandals With Clear Misuse of "Without Prejudice"
Trying to prevent the public from finding out the criminal stuff that went on, resulting in many deaths
Canonical (or Ubuntu) Rejecting IRC Isn't the Widespread Trend
Internet Relay Chat (IRC) adoption still growing by some yardsticks
SLAPP Censorship - Part 173 Out of 200: Two Years
It was exactly 2 years ago that we filed lawsuits against Garrett
Linux of America
We could not help but notice GNU/Linux in North America yesterday
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, September 05, 2026
IRC logs for Saturday, September 05, 2026
Gemini Links 06/09/2026: Internet Limiting (Limited Time Allotted) and Solar MiniServer
Links for the day
Eight Months of Strikes in EPO, Organised by the Staff Union (SUEPO) Also in Berlin
In Berlin, only one member of staff voted against the action plan