Page MenuHomePhabricator

Use SecurePoll for the admin election of zhwiki (Oct 2023)
Closed, ResolvedPublic

Description

After the zhwiki admin election in September 2022 made use of SecurePoll (T318147), now the community has decided that SecurePoll will be used for the future elections. The election will be held twice a year.

For Oct 2023 election, the timeline should be:

  • Oct 8 - Oct 20: Election setup
    • Import the question
    • Import the list of eligible voters (should be those who can vote before UTC time 00:00, Oct 1)
    • Make the scrutineers (local suppressors) election admins on votewiki
  • Oct 21 - Nov 3: Voting period
  • Nov 3 - Nov 8 : Tallying period
    • Election exec. committee checks if any vote was cast while the user was locally blocked
    • Scrutineers run necessary checks to strike votes submitted by socks or placed through proxy IP addresses
    • Scrutineers confirm that the result posted on wiki matches the result from the tally

btw, there's some special instructions for this election:

  • We would like to have two votes created during the election, one for sysop, one for other advanced permissions
  • There should be 4 options for each candidates, "support", "oppose", "neutral" and "abstain". The default selection is "abstain".
  • We would like to set voter-privacy to 1

Configurations: https://zh.wikipedia.org/wiki/Wikipedia:申请成为管理人员/Oct2023.json
Candidates:

  • vote 1:
    • ASid
    • 卡达
    • S8321414
    • ATannedBurger
    • Lanwi1
    • HTinC23
  • vote 2:
    • AT (监督员)
    • Peacearth (监督员)

Voter list: P53013

Event Timeline

Thanks for filing this and apologies for a delay in my response. Questions from me...

  • Would the first of these be in October 2023? I ask because the U4C Charter vote will be running from October 2–13. That means we will not have a tally until probably October 27 or later. It could still be possible though might be easier if we push it back a week
  • Would the community expect to use encryption in these elections? If not it might actually be possible to run the election directly on zhwiki rather than on votewiki
  • The community has no special need of a GPG encryption, our previously hosted election use no encryption. It would be really nice if election could be run at zhwiki locally, but I'm not sure if its possible technically - is there any update of T301180?
  • If election is hosted on zhwiki, do we still need to stagger the time slot with U4C vote? If not, I will ask the community for another time
  • The community has no special need of a GPG encryption, our previously hosted election use no encryption. It would be really nice if election could be run at zhwiki locally, but I'm not sure if its possible technically - is there any update of T301180?

My understanding is that the local elections are only stuck on encryption: T209892

Since this wouldn't be encrypted I don't think there would be a barrier to running it locally. I will say though that we haven't really run an election locally for a very long time so the community would have to be OK with that (e.g. something might go wrong in the process).

I can also perhaps run some test elections beforehand to make sure all is OK, assuming this would not be controversial.

  • If election is hosted on zhwiki, do we still need to stagger the time slot with U4C vote? If not, I will ask the community for another time

I think these could run at the same time since there would be no need to use votewiki, but the uncertainty mentioned above still applies. :)

I can also perhaps run some test elections beforehand to make sure all is OK, assuming this would not be controversial.

It would be great for a trial run prior to the estimated election time, personally I think September would be OK. Is there any thing that the community needs to do for this?

Hi @jrbs, kindly asking is there any update of this task?

I can also perhaps run some test elections beforehand to make sure all is OK, assuming this would not be controversial.

It would be great for a trial run prior to the estimated election time, personally I think September would be OK. Is there any thing that the community needs to do for this?

Sorry to miss this. I was researching a bit recently around local elections (and wrote this update, then got somewhat distracted trying to find answers)

I was under the impression from T335201: Investigation: What needs to change to allow local wikis to run their own elections? that there was nothing preventing local, unencrypted elections, but I actually believe there is — zhwiki, and indeed all wikis, do not have the electionadmin user right, so it is actually impossible to create a SecurePoll election locally there. I think this would probably be an easy config change, but it exposes some security risks (since electionadmin would be grantable by 'crats and is a right that allows access to IP information).

For that reason I think we actually do need to run this on votewiki if we want to run it at all. That is probably fine if we can get everything ready soon (voter lists, candidates etc.)

I would quite like to avoid last year's issue requiring us to set up 10 different elections if at all possible... Do you know if you will still want to prevent people from voting for themselves?

Thanks for your reply! I have left my comment at T335201.

So this election is still on votewiki, right? Per T342774#9100803, is it means the vote will not start until October 14?

I would quite like to avoid last year's issue requiring us to set up 10 different elections if at all possible... Do you know if you will still want to prevent people from voting for themselves?

This concern has been forwarded to the community. On the bright side there won't be so much candidates in this election :)

Stang renamed this task from Use SecurePoll for the admin election of zhwiki to Use SecurePoll for the admin election of zhwiki (Oct 2022).Oct 2 2023, 1:55 PM
Stang renamed this task from Use SecurePoll for the admin election of zhwiki (Oct 2022) to Use SecurePoll for the admin election of zhwiki (Oct 2023).

So this election is still on votewiki, right? Per T342774#9100803, is it means the vote will not start until October 14?

Thanks for flagging that comment, it is out of date because the U4C vote is now scheduled for Nov 8 – 22.

This means that, ideally, the zhwiki elections would be completed by November 8 if possible. I would perhaps suggest a week earlier than the timeline in the task here:

  • Oct 8 - Oct 20: Election setup
  • Oct 21 - Nov 3: Voting period
  • Nov 3-8 : Tallying period

I would also like to ask that we do not change the language of votewiki to zh. The ballot / question / options can all be in zh, but since we will be setting up the U4C election at the same time it would be much simpler if votewiki is in en. Is that acceptable?

I would quite like to avoid last year's issue requiring us to set up 10 different elections if at all possible... Do you know if you will still want to prevent people from voting for themselves?

This concern has been forwarded to the community. On the bright side there won't be so much candidates in this election :)

Excellent :D Thank you!

@jrbs Some updates, if there's anything not clear in my json file, please let me know.

Thanks, I will set this up. One problem I see though:

There should be 4 options for each candidates, "support", "oppose", "neutral" and "withdrawn". The default selection is "withdrawn".

I am not sure I understand this request. Can someone vote for a withdrawn candidate? Each of these will be a number in the back end (we can still have four options I think, we haven't done it before but I don't see a problem since the tally will give the number of votes with each option)

Edit: I see the option for this is "弃权", which I think means "abstain" or "no vote". Is that right?

Yeah, it is actually "abstain", apologize for my inaccurate word.

Yeah, it is actually "abstain", apologize for my inaccurate word.

No worries, I just wanted to be sure :)

I just need the list of voters now. Who is putting that together?

@jrbs Voter list generated.
Something forgot to mention: We would like to hide the voter list (set voter-privacy to 1) per community consensus

@jrbs Voter list generated.
Something forgot to mention: We would like to hide the voter list (set voter-privacy to 1) per community consensus

Thank you! This list has been imported, and the requested change has been made.

Stang changed the task status from Open to In Progress.Oct 19 2023, 6:46 PM
Stang updated the task description. (Show Details)

@jrbs, the vote duration of "2023年10月中文维基百科管理人员选举-其他管理人员" is incorrect, please fix it.

@jrbs, the vote duration of "2023年10月中文维基百科管理人员选举-其他管理人员" is incorrect, please fix it.

Good catch, changed it.

Just like the previous one (T318147): Please mark me and @jimmyxu as Scrutineers for the vote. Thank you.

Just like the previous one (T318147): Please mark me and @jimmyxu as Scrutineers for the vote. Thank you.

You should both already have access.

Just like the previous one (T318147): Please mark me and @jimmyxu as Scrutineers for the vote. Thank you.

You should both already have access.

thank you. vote 1 completed.

Re: vote 2
according local OS policy, 80% of support vote is needed to grant the access.
75 to 79% of support vote, traditionally, will be counted as borderline case.
Extension of voting period is considered to be one of legitimate solution.
After discussion with Jimmyxu, @jrbs could you please extend the voting period of vote 2 for 1 week.
Thank you.

@Wong128hk A secure poll could not be edited once it has started, so I don't think a prolong is possible technically. The only way seems to be re-run an election.

Well that's a terrible system for RfAs...

Though is it possible to just hold a shorter election that could act as an extension for the current election? 14+7 could still be 21.

Though is it possible to just hold a shorter election that could act as an extension for the current election? 14+7 could still be 21.

You can't know if there's some people who has voted in the previous election votes again in this new "shorter election", so I'm afraid no

@Wong128hk A secure poll could not be edited once it has started, so I don't think a prolong is possible technically. The only way seems to be re-run an election.

It is possible, but only through the database.

Just like the previous one (T318147): Please mark me and @jimmyxu as Scrutineers for the vote. Thank you.

You should both already have access.

thank you. vote 1 completed.

Re: vote 2
according local OS policy, 80% of support vote is needed to grant the access.
75 to 79% of support vote, traditionally, will be counted as borderline case.
Extension of voting period is considered to be one of legitimate solution.
After discussion with Jimmyxu, @jrbs could you please extend the voting period of vote 2 for 1 week.
Thank you.

I have done this as requested. It may result in some strangeness if the election was already tallied (I haven't tried tallying an election twice in this kind of scenario), so proceed with caution.

If necessary it should be pretty easy to simply create a new election.

@Wong128hk A secure poll could not be edited once it has started, so I don't think a prolong is possible technically. The only way seems to be re-run an election.

It is possible, but only through the database.

Just like the previous one (T318147): Please mark me and @jimmyxu as Scrutineers for the vote. Thank you.

You should both already have access.

thank you. vote 1 completed.

Re: vote 2
according local OS policy, 80% of support vote is needed to grant the access.
75 to 79% of support vote, traditionally, will be counted as borderline case.
Extension of voting period is considered to be one of legitimate solution.
After discussion with Jimmyxu, @jrbs could you please extend the voting period of vote 2 for 1 week.
Thank you.

I have done this as requested. It may result in some strangeness if the election was already tallied (I haven't tried tallying an election twice in this kind of scenario), so proceed with caution.

If necessary it should be pretty easy to simply create a new election.

User from zhwiki cannot vote.
I think better create a new election.
@jrbs please help create a new election. Thanks.

Just for note. The reason of cannot vote is that only the poll on the votewiki was extended, but the local one did not extended. Therefore, users cannot follow Special:SecurePoll link on the local wiki to vote. Thanks.

Just for note. The reason of cannot vote is that only the poll on the votewiki was extended, but the local one did not extended. Therefore, users cannot follow Special:SecurePoll link on the local wiki to vote. Thanks.

You are absolutely right. I have made this change and it should now work as expected.

If this is not acceptable, or you require additional time on the vote, please let me know @Wong128hk / @jimmyxu

Just for note. The reason of cannot vote is that only the poll on the votewiki was extended, but the local one did not extended. Therefore, users cannot follow Special:SecurePoll link on the local wiki to vote. Thanks.

You are absolutely right. I have made this change and it should now work as expected.

If this is not acceptable, or you require additional time on the vote, please let me know @Wong128hk / @jimmyxu

The vote should be ended at 15 Nov 23:59 (UTC) since the vote cannot be accessed from local site and not enough notification. Thank you.

I can confirm that votes now can be casted as normal.

The vote should be ended at 15 Nov 23:59 (UTC) since the vote cannot be accessed from local site and not enough notification. Thank you.

I have made this change.

The election has ended now. @jimmyxu / @Wong128hk - feel free to run your scrutiny of the new votes. We will see if the creation of a new tally works as expected once you are ready.

Tally ran without issues afaics. Results posted on wiki with @Wong128hk concurring and vote 2 should be complete.

Stang updated the task description. (Show Details)