[python-committers] Transfer of power
Antoine Pitrou
antoine at python.org
Thu Jul 12 15:20:06 EDT 2018
More information about the python-committers mailing list
Thu Jul 12 15:20:06 EDT 2018
- Previous message (by thread): [python-committers] Transfer of power
- Next message (by thread): [python-committers] Transfer of power
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Le 12/07/2018 à 21:17, Doug Hellmann a écrit : > > If the primary approach to decision making is to delegate unless > an arbiter is absolutely necessary, then long-term consistency and > stability comes less from finding individuals to commit to serving > for very long terms on the N-virate as it does from everyone having > a good understanding of the history of discussions and from a > willingness to keep the status quo in situations where consensus > isn't reached (note "consensus" rather than "unanimous agreement"). > > Building the system to support and encourage turnover, like we do > with release managers, lowers the level of effort someone is signing > up for when they agree to serve. Given the *many* discussions of > burnout in the Python community and open source in general, that > seems like an important feature. +1. Ongoing consistency is achieved through a strong culture. Regards Antoine.
- Previous message (by thread): [python-committers] Transfer of power
- Next message (by thread): [python-committers] Transfer of power
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list