# PEP 8016 - The steering council model **URL:** \ **Category:** Committers\ **Tags:** governance\ **Created:** [November 6, 2018, 2:36am UTC](https://discuss.python.org/t/pep-8016-the-steering-council-model/394 "2018-11-06T02:36:17Z")\ **Posts on this page:** 1\ **Showing post:** 36
**Author:** ![xiangz](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/xiangz/32/4868_2.png) [@xiangz](https://discuss.python.org/u/xiangz)\ **Post date:** [November 17, 2018, 7:17am UTC](https://discuss.python.org/t/pep-8016-the-steering-council-model/394/36 "2018-11-17T07:17:37Z")
Thanks for the reply. 🙂 > [@njs](#): > > The council votes are always simple majority ([reference](https://www.python.org/dev/peps/pep-8016/#powers)), except for the special case of ejecting an existing core team member, [which requires a supermajority](https://www.python.org/dev/peps/pep-8016/#ejecting-core-team-members). So a veto requires a simple majority. In the PEP I only see the word _strict majority_: > [@njs](#): > > To use its powers, the council votes. Every council member must either vote or explicitly abstain. Members with conflicts of interest on a particular vote must abstain. Passing requires a strict majority of non-abstaining council members. Are they the same thing? _simple majority_ has a definition in wikipedia, not _strict majority_. > [@njs](#): > > Imagine there’s some developer who has a good public reputation, but you know that in private they’re an abusive manipulator who does terrible things to people. Not sure in open source world we should take such real life things into consideration. It’s complicated. > [@njs](#): > > This kind of procedural edge case is tiresome and unpleasant, so maybe we should merge the two powers to keep things simpler. +1. The council could use their power later if there is really a problem. Promoting core devs could be frequent but not ejecting one. I think so. --- _[View the full topic](https://discuss.python.org/t/pep-8016-the-steering-council-model/394)._