Creating this ticket to track work for generating a voter list for T400228.
Criteria (from T400228#11113763):
The account must not be blocked on any Wikimedia projects at the moment of the vote (between Sep 22- Oct 5 2025) The account must not be a bot-account. The sum of edits on all Wikimedia projects must be greater than 300 edits on September 21, 2025. The account must have done 200 edits between March 21, 2025 and September 21, 2025.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | None | T400228 SecurePoll for Wikimédia France board of administrators seat | |||
| Invalid | SD0001 | T403809 Create voter list for Wikimedia France board of administrators election |
Simple criteria like in AELECT2 work for any wiki, sure (and should only take 2-3 seconds, the 87 seconds seems to be from Quarry's NFS lag + unnecessary use of ORDER BY / DISTINCT). But with the complex criteria, there are no indexes so Quarry will take forever even for "small" wikis that have only a million user accounts.
and do some filtering and merging offline
Even if Quarry hypothetically worked, you seem to be underestimating the effort of merging. Taking the union of the output from multiple wikis would skip over users who are eligible due to their combined activity across projects. So, you'd need to merge the counts across wikis for each user. At that point, you end up re-implementing populateEditCount.php + makeGlobalVoterList.php or the code in https://gitlab.wikimedia.org/sd/global-election-list-builder!
@asirac I didn't notice this earlier, but the criteria you've given refers to dates in the future:
The sum of edits on all Wikimedia projects must be greater than 300 edits on September 21, 2025. The account must have done 200 edits between March 21, 2025 and September 21, 2025.
We won't be able to know if an account passes the check until after September 21 has passed. There's no time to run the script after that as the voting begins on September 22.
For the WMF Board elections, the criteria usually have the month shifted back by 1 (i.e. if it's starting on Sep 22, the criteria would require X edits before Aug 21, and Y edits between Feb 21 and Aug 21). Can you consider making a similar amendment (maybe shift it back by 2 weeks if not a month)?
I ran the first part of the script (populate-edit-count), which finds the edit counts in the intervals of interest, for these amended criteria:
The sum of edits on all Wikimedia projects must be greater than 300 edits on September 7, 2025. The account must have done 200 edits between March 7, 2025 and September 7, 2025.
I ran into an error with commonswiki and testwiki because of a bug in wiki replicas: T404473. Once that is resolved, I'll re-run the script for those two wikis. Following that, the final step is to run the second part (make-global-list) to compute the global edit counts for each user and determine who all are eligible.
Hi. As there is only one candidate, we do not need the vote anymore. So we can close this task. Thanks, and sorry for bothering you.