Adding a "deadline" for seconding a vote of no confidence

[hugovk (Hugo van Kemenade)]

@pradyunsg

Is there something procedural that needs to happen so that this is an item to vote for on the same vote cycle as the SC vote? (eg: an update to PEP 8106)

I don’t think we need to update PEP 8106.

Procedurally, to modify PEP 13:

Changes to this document require at least a two-thirds majority of votes cast in a core team vote which should be open for two weeks.

This does not necessarily have to be part of the SC vote or using Helios, it can be a Discourse poll in the Committers category along with an email for visibility. See How to enact changes to PEP 13 for discussion and agreement on this.

And see Changing PEP 13 to adopt Bloc STAR voting for a similar vote to modify PEP 13 to adopt STAR voting (aside: will come into effect after this SC election).

So it might be easier doing a Discourse poll than using Helios? In any case, it would make sense for the two-week PEP 13 vote to coincide with the two-week SC election vote.

@pradyunsg

Somewhat relatedly, one way to resolve the one week vs two week selection is having this be an approval vote with two options (2 weeks / 1 week) rather than a yes/no question.

Since we have a threshold requirement already, we don’t need a “none of the above” option (one can vote for none of them, which will reduce odds of the vote reaching threshold). If both cross the threshold, we can pick the one with the higher approval count. And, in case of a tie, pick one at random.

I think we should include an option for the status quo (that is, no defined deadline). If you see two options (2 weeks/1 week) it looks like those are the only options, and there should be a way to actively vote for the status quo.