# PEP 8012: The Community Model

**URL:** <https://discuss.python.org/t/pep-8012-the-community-model/156>\
**Category:** Committers\
**Tags:** governance\
**Created:** [October 3, 2018, 1:13am UTC](https://discuss.python.org/t/pep-8012-the-community-model/156 "2018-10-03T01:13:58Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![jackdied](https://avatars.discourse-cdn.com/v4/letter/j/b9e5f3/32.png) [@jackdied](https://discuss.python.org/u/jackdied)\
**Post date:** [October 4, 2018, 1:45am UTC](https://discuss.python.org/t/pep-8012-the-community-model/156/5 "2018-10-04T01:45:25Z")

</div>

> [@ambv](#):
>
> New core developer nomination requires there to be no votes cast  
> against it.

“Blackball” does not work outside of very small organizations. Most voters will have had very few interactions with any newly proposed core-dev so they will be working with a very limited data set. We would hope that they would trust the champion who proposed the person for core-dev status (and has interacted with them many times) but you can’t guarantee that. You’ll find that there is one person, or a small group of people, that are responsible for _all_ of the blackballs.

I’m OK with requiring a super-majority of the votes, but allowing one person to jam up the works assures that sooner or later you will have one person who jams up the works.

---

_[View the full topic](https://discuss.python.org/t/pep-8012-the-community-model/156)._