[python-committers] Transfer of power
Yury Selivanov
yselivanov.ml at gmail.com
Thu Jul 12 13:29:21 EDT 2018
More information about the python-committers mailing list
Thu Jul 12 13:29:21 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 ]
On Thu, Jul 12, 2018 at 12:58 PM Antoine Pitrou <antoine at python.org> wrote: > > > I'd like to point out that the N-virate idea doesn't handle a key issue: > once you have a N-virate, how do you evolve its composition according to > the implication and motivation of its members - but also to remarks or > frustation by non-virate contributors (especially new contributors who > will feel there's a perpetual category they're locked out of)? Do you > just wait for people to gently step down when required? One way would be to re-elect them every 5 or so years. Essentially, an N-virate is a dictator-like entity for a few years. Yury
- 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