<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Oh, yeah, I guess I wasn’t clear there. I am not suggesting that release managers add this new responsibility. I’m suggesting that a release cycle length is an amount of time the community is used to dealing with, and therefore might make a good cadence for elections or whatever other rotation mechanism is selected for the new group.<div class=""><br class=""></div><div class="">Sorry for the confusion.</div><div class=""><br class=""></div><div class="">Doug<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jul 13, 2018, at 5:30 AM, Anthony Baxter <<a href="mailto:anthonybaxter@gmail.com" class="">anthonybaxter@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="auto" class="">As someone who's not been involved for some time now, but was release manager for a three or four years (2.3.1 through to 2.5.1), trying to have the release manager also be a decider of potentially controversial things doesn't seem scalable. <div dir="auto" class=""><br class=""></div><div dir="auto" class="">Getting a release out is a heck of a lot of work, both the actually cutting the alphas, betas, &c, and also triaging issues that comes up and chasing people up for fixes.<div dir="auto" class=""><br class=""></div><div dir="auto" class="">I'm not sure what the proper governance structures should be, but they absolutely shouldn't be dumping extra load onto the release manager.</div></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Fri, Jul 13, 2018, 3:49 AM Doug Hellmann <<a href="mailto:doug@doughellmann.com" class="">doug@doughellmann.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Excerpts from Yury Selivanov's message of 2018-07-12 13:29:21 -0400:<br class="">
> On Thu, Jul 12, 2018 at 12:58 PM Antoine Pitrou <<a href="mailto:antoine@python.org" target="_blank" rel="noreferrer" class="">antoine@python.org</a>> wrote:<br class="">
> ><br class="">
> ><br class="">
> > I'd like to point out that the N-virate idea doesn't handle a key issue:<br class="">
> > once you have a N-virate, how do you evolve its composition according to<br class="">
> > the implication and motivation of its members - but also to remarks or<br class="">
> > frustation by non-virate contributors (especially new contributors who<br class="">
> > will feel there's a perpetual category they're locked out of)? Do you<br class="">
> > just wait for people to gently step down when required?<br class="">
> <br class="">
> One way would be to re-elect them every 5 or so years. Essentially,<br class="">
> an N-virate is a dictator-like entity for a few years.<br class="">
> <br class="">
> Yury<br class="">
<br class="">
We've had good luck in the OpenStack community tying leadership to<br class="">
release cycles. It causes elections more often (our cycles are 6<br class="">
months long), but people tend to step up for several cycles in a<br class="">
row so that hasn't been a cause of excessive turnover. Having<br class="">
frequent opportunities for folks to step down gracefully when they<br class="">
need or want to also means no one feels like they are signing up<br class="">
for an indefinite time commitment.<br class="">
<br class="">
For a multi-person group, staggered elections where only a portion<br class="">
of the group is up for election at one time, also provides some<br class="">
consistency when there is turnover.<br class="">
<br class="">
Doug<br class="">
_______________________________________________<br class="">
python-committers mailing list<br class="">
<a href="mailto:python-committers@python.org" target="_blank" rel="noreferrer" class="">python-committers@python.org</a><br class="">
<a href="https://mail.python.org/mailman/listinfo/python-committers" rel="noreferrer noreferrer" target="_blank" class="">https://mail.python.org/mailman/listinfo/python-committers</a><br class="">
Code of Conduct: <a href="https://www.python.org/psf/codeofconduct/" rel="noreferrer noreferrer" target="_blank" class="">https://www.python.org/psf/codeofconduct/</a><br class="">
</blockquote></div>
</div></blockquote></div><br class=""></div></body></html>