On Fri, Mar 22, 2019 at 4:17 PM Victor Stinner <vstinner@redhat.com> wrote:
Le ven. 22 mars 2019 à 22:42, Brett Cannon <brett@python.org> a écrit :
> I don't think people have to justify their vote. We don't ask that of anyone else in any other votes that we hold.

Ok, I'm fine with that.

I wanted to ask explicitly, since votes on python-committers mailing
required to post a change. It's a change compared to old way to vote.

--

By the way, is the Steering Committee ok with the proposed duration
for the vote (we proposed 1 week)?

I'm personally fine with it, but we haven't formally discussed this. But I doubt anyone else on the council will care so just assume a week is fine. :) There's no need to rush a resolution but there's also no need to drag it out either, and a week guarantees at least one weekend for those that only check their open source emails once a week.
 
I'm asking because the duration was
never really discussed... In the past, sometimes Guido closed
immediately a vote by saying "ok, we got enough +1, <candidate> is
promoted", the duration of the vote wasn't announced in advance.

It's unfortunately a deficiency in PEP 13 as it's not specified in https://www.python.org/dev/peps/pep-0013/#membership . It's probably something we should fix in PEP 13 by following https://www.python.org/dev/peps/pep-0013/#changing-this-document but which also lacks a time frame for votes. :)
 

I like to announce a deadline so people can take their time before
voting, if they want, to see the trend. The ones who missed the
deadline cannot complain since it has been announced from the start
;-)

Go with a week since the poll opened on discuss.python.org.
 

Maybe it's better to let the Steering Committee close the vote.
Honestly, I'm not sure of what is the best :-D

No one does. :) We're all trying to figure this out as a group as we adjust to our new governance situation.

-Brett
 

Victor
--
Night gathers, and now my watch begins. It shall not end until my death.