# Three month suspension for a Core Developer

**URL:** <https://discuss.python.org/t/three-month-suspension-for-a-core-developer/60250>\
**Category:** Committers\
**Created:** [August 7, 2024, 6:23pm UTC](https://discuss.python.org/t/three-month-suspension-for-a-core-developer/60250 "2024-08-07T18:23:29Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![brettcannon](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/brettcannon/32/34895_2.png) [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Post date:** [August 14, 2024, 10:31pm UTC](https://discuss.python.org/t/three-month-suspension-for-a-core-developer/60250/7 "2024-08-14T22:31:01Z")

</div>

> [@pitrou](#):
>
> I might have missed something

Everyone except the person in question has incomplete knowledge of what was said; information asymmetry easily happens when conversations span multiple topics, places, and public/private spaces. At some point I think you have to decide if you trust that the people making the decision had enough information to say and do what they did compared to the information any of us may have been personally privy to.

> [@pitrou](#):
>
> A special mention is deserved for _“discussing bans or removals of community members […] may be seen [by whom?] as publishing private information without permission”_. It’s entirely unspecific, and implies that any discussion of such bans or removals can be reason for banning someone else.

My takeaway from that is you need to make sure that you have permission from the person who was banned or removed to name them publicly, otherwise you risk outing them when they didn’t want to be publicly named.

---

_[View the full topic](https://discuss.python.org/t/three-month-suspension-for-a-core-developer/60250)._
