The controversial “one week for core dev votes” topic was brought up on python-committers when Victor brought up Stephane’s candidacy. He asked if anyone objected to his proposed one week for that vote, no one objected and I at least personally said I supported the one week amount of time. Based on that I don’t think anyone on the council viewed this as controversial (or at least that’s why I didn’t expect any specific issues with the proposed time length and didn’t worry about bringing it up ahead of time).
The PEP 13 changes has not been brought up previously, but everyone seems fine with 2 weeks. My guess is that since that’s the length we use for steering council elections then that’s become an acceptable amount of time.
That was my motivation for wanting to see it specified, as otherwise the steering council could theoretically manipulate core dev membership or PEP 13 changes by arbitrarily closing votes when the count was in their favour. I.e. PEP 13 doesn’t say vote length has to be specified before voting starts, so technically I could vote myself and then shut the vote down immediately thereafter and be within the guidelines of PEP 13 (although obviously not operating within its spirit).
We actually talked about doing that, but since this is the first time anyone has proposed a change to PEP 13 we weren’t sure if that was what people wanted for similar things like this or if people prefer the PSF board approach of making more rolled-up proposals when things are not considered controversial. In the end we decided to give this approach a go. I know in my head I view this as a single topic to specify voting time frames and not two separate things, so that’s also why I thought about doing it this way.
There’s no real insight. During the last group of votes for core devs the question came up about how long the votes should be open. Some people said “how about a week?” People seemed happy with that, so that’s what we did. It seemed reasonable to write that down and that’s when I realized we would be bringing this up as a vote which also lacked a time frame, so we figured we might as well solve both of them simultaneously.