A post by Guido van Rossum removed for violating Python community guidelines
A briefly hidden post on Python’s official forum — referencing a core developer currently serving a three‑month suspension — triggered anger over perceived censorship, opaque moderation and the growing power of non-elected Code of Conduct bodies in major open source projects. Commenters debate whether such enforcement shows that “no one is above the rules” or instead signals bureaucratic overreach that could damage community trust, governance, and Python’s long‑term health. Later clarification that the removal was attributed to an automated moderation mishap did little to quiet broader worries about how social and political norms are reshaping technical communities.
Incident Overview
- Thread is about governance voting; a prominent community member’s comment was auto-hidden on the official forum.
- The hidden comment (as reported by readers) merely noted that an expert on voting systems was currently under a 3‑month suspension and suggested consulting them later.
- Because moderated posts are now fully hidden from non‑moderators, this triggered concern and speculation about censorship and “un‑persons.”
Moderation, Transparency, and “Censorship”
- Many see fully hidden posts and bans for even oblique references to a suspended contributor as a “massive red flag” and trust‑eroding.
- Others argue the comment could be read as passive‑aggressive or as re‑litigating a previous CoC decision, so hiding it was within the rules.
- Disagreement over whether “no one above the rules” is reassuring or whether the rules are being used to shield leadership from embarrassment.
Governance and Power Structures
- Debate over the elected steering council vs. earlier “benevolent dictator” model:
- Some want the founder to retain a soft veto or sovereign role as a backstop.
- Others insist on democratic, community‑elected governance and that core members must follow the same rules.
- Concerns about the unelected Code of Conduct work group, its overlap with other power centers, and opaque enforcement procedures.
Broader Concerns about CoCs and Community Politics
- Several commenters generalize this to a pattern across projects (Python, NixOS, Linux, Go, Debian): CoCs and HR‑style governance allegedly enabling cliques, “activists,” or bureaucrats to capture projects and silence dissent.
- Others push back, saying some drama is inevitable in any human committee and that CoCs are needed to handle real misconduct.
Impact on Python and Follow‑up
- Some fear a “Perl‑like” decline or call for forks and corporate-maintained variants; others say most users won’t notice and the language will continue regardless.
- There is side debate about Python’s technical direction and readability vs. complexity, but that’s secondary to the governance issue.
- Later in the thread, the original poster (whose comment was hidden) states it was a moderation automation mishap, the post was restored, and a moderator apologized.
- Some say this shows early reactions were overblown; others argue it’s part of a longer worrying pattern rather than an isolated mistake.