Jump to content

Wikipedia talk:Requests for comment/Arbitration Committee Elections December 2019

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
< Wikipedia talk:Requests for comment

This is an old revision of this page, as edited by Xaosflux (talk | contribs) at 17:48, 7 August 2019 (→Users who would like to be notified when the 2019 RFC begins: +*xaosflux). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

2019 Arbitration Committee Elections

Shortcut

Status as of 04:58 (UTC), Sunday, 10 November 2024 (Purge)

  • Thank you for participating in the 2019 Arbitration Committee Elections. The certified results have been posted.
  • You are invited to leave feedback on the election process.

Carry over items for next year

Electoral commissioners

  • Make up of the commission (follow up from prior year 3 vs more than 3 active seats discussion). — xaosflux Talk 16:05, 21 October 2018 (UTC)[reply]
    Should probably remain at three, or at least at an odd number, so the Commission can make a 'ruling' by majority if necessary.  Swarm  talk  00:08, 28 November 2018 (UTC)[reply]
  • Remove the requirement for commissioners to sign the ANIP. We receive absolutely no non-public data, it's positively silly to require a signature. SQLQuery me! 07:28, 18 November 2018 (UTC)[reply]
    Or go the opposite route of handing temporary oversight, and maybe checker, to commissioners for ACE related matters only, given the recent situation on Fred's questions page, to be revoked at the end of the ACE. —CYBERPOWER (Chat) 13:22, 18 November 2018 (UTC)[reply]
    @SQL: I believe it is so that if there are issues that the scrutineers need to raise regarding private information they may discuss them with the commissioners. This is not well codified but could be (i.e. commissioners may receive and evaluate information from checkusers related to the election). — xaosflux Talk 18:49, 18 November 2018 (UTC)[reply]
    @Xaosflux: One of the, probably the original reason would had been because of SecurePoll. If you're an admin for the election, then you see CU like info for all votes. Commissioners are no longer made (or rather no longer retain before the election begin) admin for the election. -- KTC (talk) 19:05, 18 November 2018 (UTC)[reply]
    @SQL: According to the scrutineer instructions, Commissioners, like Scrutineers, are temporarily made Securepoll admins during the election, which "enables access to CheckUser-like data on each vote cast". Is this information incorrect? I'm not even sure who's in charge of granting Securepoll adminship.  Swarm  talk  23:49, 27 November 2018 (UTC)[reply]
    Swarm, It is incorrect, as of this year. SQLQuery me! 23:51, 27 November 2018 (UTC)[reply]
    @SQL: Do we have any idea when or why it was changed? Was it just a fluke, or was it intentional?  Swarm  talk  00:12, 28 November 2018 (UTC)[reply]
    @Swarm: Intentional, and this is not the first vote-wiki SecurePoll election where that's the policy. Underlying reason being security and minimising the number of people who has access to non-public data, the scrutineers being the only people mandated to decide on the validity of a vote, the coordinators thus have no need to have access to the CU-like data that comes with being admin of an election. -- KTC (talk) 11:16, 28 November 2018 (UTC)[reply]
    Swarm, To answer the other half of your question - I'm not 100% sure, but my access was initially set up by JSutherland (WMF). We were notified via email by Jalexander-WMF on Nov. 17th that we would be removed as election admins before the election goes live this year. I'm not sure how much of the email I'm allowed to quote or paraphrase. SQLQuery me! 00:21, 28 November 2018 (UTC)[reply]
    Okay, thanks both. I went ahead and got an on-Wiki clarification for the community to reference, so I'm thinking it should be fairly uncontentious to delete the confidentiality requirement going forward.  Swarm  talk  23:23, 29 November 2018 (UTC)[reply]
  • Void the restrictions on the Electoral Commission's mandate. The 2013 decision to shackle the Electoral Commission, to prevent them from taking "active and ongoing role in the day to day operation of the election" was made by three users and there is no particularly obvious reason maintain these restrictions. These are highly trusted users appointed by the community, and they're already expected to take a leading role in running the election, and they can and should be trusted to oversee and moderate the election at their discretion.  Swarm  talk  00:08, 28 November 2018 (UTC)[reply]
    • As a side note, the original intent of the Electoral Commission was to "deal with unforeseen problems, adjudicate disputes", due to unusual events occurring during the previous election in 2011, after the annual RfC had closed. As far as I recall, the intent was to provide a way to resolve open questions in a timely manner during the election when a community consultation is infeasible without unduly disrupting the election process. Of course, the community could decide for the next election that they want the commission to take a leading role; I don't believe, though, that the commissioners are currently vetted by the community with this in mind. isaacl (talk) 04:46, 28 November 2018 (UTC)[reply]
    @Isaacl: Yeah, the Commission isn't mandated to actively run the election, and I'm not suggesting we change that. However, the Commission's responsibilities to deal with "unforeseen problems" inherently make them the party ultimately responsible for the proper progression of the election. In theory, this means we have a strong team of volunteers handling everything, and the Commission can sit back and do nothing until the unlikely event they're needed, but in practice, it means they have a de facto dual role as election volunteers, due to a notable lack in volunteers.  Swarm  talk  23:23, 29 November 2018 (UTC)[reply]

Voters

  • Voter suffrage - was identified last year that for users with multiple accounts, including bots, may all be 'eligible' so long as their controller does not vote multiple times. — xaosflux Talk 20:56, 26 October 2018 (UTC)[reply]
    • IIRC last year or the year before one user voted with multiple eligible accounts voted with account A and then several days later with account B. The determination was that the vote from account A be discarded and the vote from account B be allowed to stand as if it was an amended vote from account A. Thryduulf (talk) 16:40, 20 November 2018 (UTC)[reply]
  • New voter requirement suggested: Must have 1 live edit within the past 2 years. We are consistently maintaining voter rolls of people that have long left the project. — xaosflux Talk 21:32, 26 October 2018 (UTC)[reply]

Mass-messaging

Candidate requirements

  • What is meant by "good standing" in terms of candidate requirements? Options include:
    • Not blocked or banned - at the time nominations close or at some other time?
    • Not subject to active sanctions - at the time nominations close or at some other time? - any sanctions or just some types?
    • Have the trust of the community - determined how? determined by whom?
    • Not been recently desysopped - what counts as "recent"?
    • Whatever the consensus of the commissioners is - does no consensus mean good standing or not?
    • Some combination of the above. Thryduulf (talk) 11:26, 12 November 2018 (UTC)[reply]
  • This topic has been rendered moot. Per WT:ACE2018#Official statement on Fred Bauder's standing as candidate, the "good standing" verbiage has been removed outright as it was discovered that it was wrongly added unilaterally and without explanation, and it was never formally intended to be implemented by the community, and it remained over the years erroneously and without the community mandate. Theoretically, if we want 'good standing' to be a formal requirement, it can be proposed, but such a proposal would likely not be reasonable. A unilateral admin action such as a block should be able to influence an election.  Swarm  talk  00:21, 28 November 2018 (UTC)[reply]

Committee structure, term lengths

Candidate lists, question pages

  • I appreciate where you're coming from on this — normally I'd say no, get someone uninvolved to take care of it – but that candidate has been the constant target of a vile and ongoing attack for a while now, so this seems perfectly fine to me. ~ Amory (u • t • c) 22:45, 5 December 2018 (UTC)[reply]
  • @Amorymeltzer: There’s no doubt in my mind that his integrity is beyond reproach considering the unwarranted vitriol he’s faced this election, but I still believe it’s a question worth considering, in light of that and everything else involving this year’s election. OhKayeSierra (talk) 01:30, 6 December 2018 (UTC)[reply]
  • I'm wondering about the number of questions. On one candidate's page it looks like there are 35 questions, but one is actually 9 question and another 7, etc. I'd estimate there are at least 70 questions although I think this example is an outlier. Now I wouldn't suggest limiting the number of people who can ask questions, but perhaps the number of questions they can ask. Doug Weller talk 13:04, 16 November 2018 (UTC)[reply]
  • Should questions to candidates be required to be phrased in a neutral manner (i.e. avoiding leading questions)? Even if a non-neutral position is accompanied by evidence? Thryduulf (talk) 16:11, 17 November 2018 (UTC)[reply]
  • Are withdrawn and/or disqualified candidates listed on the candidates page? -- KTC (talk) 13:44, 12 November 2018 (UTC)[reply]
  • Does the community want the Commission to take a more active role in curating the Questions page? -- KTC (talk) 09:50, 15 November 2018 (UTC)[reply]

Voting system

  • I think we should consider replacing the current voting system with some kind of ranked-choice system that allows users to fine-tune their votes, e.g. to denote which candidates they would like to see on the Committee if their preferred choices don't gather enough support and/or which candidates they definitely don't want to serve. Regards SoWhy 08:12, 20 November 2018 (UTC)[reply]
    @SoWhy: If it's not a voting system that SecurePoll supports, then you would need to propose this well in advance of the election, gain consensus support, and have someone volunteer to code it up and reviewed. Alternatively, you would need to gain consensus to move away from SecurePoll altogether as part of the proposal. -- KTC (talk) 12:46, 20 November 2018 (UTC)[reply]
    @KTC: As far as I can tell, ranked-choice was (supposed to be) added during mw:SecurePoll/Redesign. Maybe Anomie, Jorm or RobLa who worked on the redesign according to MediaWiki-wiki can confirm this? I don't see a way to test SecurePoll myself. Regards SoWhy 13:46, 20 November 2018 (UTC)[reply]
    The project you refer to did not include adding any voting methods. But, looking at the extension, I see it includes the Schulze method (without any tie breaker), which appears to be the only method using ranked voting currently available. The extension also supports Approval voting, Plurality voting, and two variations of Range voting (sum and average). As far as I can tell SecurePoll doesn't support the S/(S+O) method directly, so I guess it must be done by people taking the histogram output by the averaging Range voting method and manually calculating S/(S+O). It looks like there was a tallier for Instant-runoff voting (where the wikilink ranked-choice redirects) at one point, but it was removed in 2015 per T107400.

    If you want to test SecurePoll, probably the easiest way is to request adminship on testwiki. Anomie⚔ 15:25, 20 November 2018 (UTC)[reply]

    @Anomie: that might be broken right now? I tried making some and it always fails with "Our servers are currently under maintenance or experiencing a technical problem.". — xaosflux Talk 16:11, 20 November 2018 (UTC)[reply]
    Looks like that's being tracked as phab:T209804. Anomie⚔ 19:01, 20 November 2018 (UTC)[reply]
    If it were to be necessary for a new voting system to be implemented, I suggest considering Ranked pairs, which is also a Condorcet method and is pretty straightforward to implement. It satisfies all the voting system criteria met by Schulze according to its Wikipedia article. Of course, there are always going to be scenarios where one method is worse than another; I can't recall at the moment if those that are worse with Schulze are considered by experts to be more likely that those that are worse with Ranked Pairs. isaacl (talk) 23:19, 20 November 2018 (UTC)[reply]
    (+1) ∯WBGconverse 12:37, 21 November 2018 (UTC)[reply]
    @Isaacl and Winged Blades of Godric: if you would like this option in the 2019 RFC then you will need to ensure either that it is supported by SecurePoll before the RFC begins or get consensus to use some other system that does support it. The same goes for any other proposed voting system of course. Thryduulf (talk) 10:09, 22 November 2018 (UTC)[reply]
    It's not a decision solely for me; I think interest should be gauged far ahead of time before a request is made to add it to SecurePoll. Otherwise it would be a waste of effort to add an unused feature to SecurePoll. isaacl (talk) 18:25, 22 November 2018 (UTC)[reply]
    I propose Meek STV which is arguably the fairest multi-winner voting system. Please also see Phab:T117127. Furthermore, we are holding our elections using Schulze method and SecurePoll at Persian Wikipedia: 2016, 2017, and 2018. 4nn1l2 (talk) 07:35, 22 November 2018 (UTC)[reply]
    Yes, SecurePoll already supports Schulze but Meek STV or Ranked pairs (or even Schulze STV) has to be implemented yet. Point is, at the 2019 RFC we should discuss a) whether to switch to some kind of ranked choice at all and then b) which system to use (from those that were implemented in SecurePoll by that time). Considering that T117127 is open since 2015 with no takers, we might have no choice but to use the system that is currently implemented. Regards SoWhy 10:21, 22 November 2018 (UTC)[reply]
    Given the lead time required to support a new voting system, I suggest a discussion on it should be started earlier rather than later (though I would wait until after the current elections are over). I agree that it's quite possible a decision to change to a new system may have to be suspended until support is implemented. isaacl (talk) 18:30, 22 November 2018 (UTC)[reply]
    I think the best thing to do is, work on getting one or more different vote systems supported by SecurePoll as soon as possible, then when they are added have a discussion about picking one or two (at most) of those systems to run off against the current system in next year's main RFC. I suggest you make that first discussion a centralised discussion, notifying those who've commented on voting systems here and on the election talk page, those listed in the below asking to be notified and anyone else you know to be interested. Thryduulf (talk) 23:06, 22 November 2018 (UTC)[reply]
    The trick would be in getting people to do the work of implementing, reviewing, and merging code for multiple voting systems, on the chance that the community might later decide to use one of them. Anomie⚔ 02:10, 23 November 2018 (UTC)[reply]
    I agree with Anomie; I think it will be challenging to get multiple systems implemented on spec. As Schulze is already in use, my guess is that trying to get a consensus for that will be the (relatively) easier approach. Not sure if there is really enough desire to switch, though. isaacl (talk) 03:58, 23 November 2018 (UTC)[reply]
    According to T117127, the change would only require adding a different tallying mechanism since the other parts could be copied from Schulze, so it might be easier than writing the whole thing from scratch. Still, you need someone to actually add a different tallying mechanism. Regards SoWhy 10:14, 23 November 2018 (UTC)[reply]
    Even better, SecurePoll separates the "ballot" and "tallier" so you wouldn't even need to copy the code for the ballot. Anomie⚔ 19:21, 23 November 2018 (UTC)[reply]
    The ballot can be reused for methods where the voter specifies a simple ranked order. For methods where the candidates are given scores, a new ballot would be needed. (I am dubious about whether a method requiring scoring could gain consensus agreement, given the additional work it would require of voters, but maybe I'm overestimating the effort of using say a simple 5-star scale.) isaacl (talk) 19:35, 23 November 2018 (UTC)[reply]
    FYI, that ballot already exists too. It's the ballot we use for the current ArbCom elections, with the three values labeled "Oppose", "Neutral", and "Support" instead of "-1", "0", and "1". Anomie⚔ 20:21, 23 November 2018 (UTC)[reply]
    Your best bet might be to see if someone would be willing to commit to implementing one new voting method for enwiki ArbCom elections, with the specific method to be determined by the result of an RFC. That could avoid both the "developers do a bunch of work that won't be used" and "we hold an RFC that can't be implemented" problems. You might try asking volunteer User:Huji who is currently maintaining the extension, or WMF's Community Tech team (since enwiki ArbCom elections are related to "administrative layers of the Wikimedia projects"). Anomie⚔ 19:22, 23 November 2018 (UTC)[reply]
    There's a little bit of chicken-and-egg problem: personally I'd like to first see a bit more interest within the community as a whole (versus a few voting system fanpersons :). I don't have a good feel yet if there's even a small chance of a change gaining consensus. isaacl (talk) 19:40, 23 November 2018 (UTC)[reply]
  • Unsure if it has been discussed here in the past or not (it is likely that User:4nn1l2 has mentioned it before, though probably not on this page), but to make sure everyone is aware: for the last three years (2016-2018), we have been using Schulze and a ranked-choice system for the fawiki Arb. Com.-equivalent elections. It has been successful and, despite some initial nay-sayers, it has been well received. I would like to repeat 4nn1l2's point that Meek is the better solution but implementing it requires tens of hours of work, which neither myself nor other SecurePoll maintainers have not been able to set aside. huji—TALK 22:21, 23 November 2018 (UTC)[reply]
    As the person who implemented Schulze in BoardVote (predecessor to SecurePoll) for the 2008 WMF Board Election, I would like to point out that Schulze is technically designed for a single winner election even if that's not how Wikimedia have used it. -- KTC (talk) 22:58, 23 November 2018 (UTC)[reply]
    @KTC: Schulze method can also be used in multi-winner elections because it generates a ranked list of candidates. In fact, any single-winner voting system can be used for multi-winner elections. The only advantage of a genuine multi-winner voting system such as STV is guaranteeing proportional representation (i.e. fairness). Having said that, the current voting system of the English Wikipedia ArbCom and Board elections is a simplified version of score voting which is also a single-winner voting system. 4nn1l2 (talk) 10:22, 24 November 2018 (UTC)[reply]
proportional representation should be a goal of this election. It is generally not a good idea to use a single-winner method to select multiple candidates for a committee, since 51% of the voters can completely determine the outcome, leaving 49% completely unrepresented. I think basing the form of the ballot off of Approval voting rather than requiring voters to rank choices would be easier, considering how many voters don't know as much about the candidates or have a nuanced a set of comparisons of them as in other election situations. It would seem worthwhile to adapt a method like Proportional approval voting for this election. I have written open-source software (https://github.com/nealmcb/pr_voting_methods) to calculate the optimal committee to represent as many voters as possible, and represent them as fully as possible, as outlined here. I would think it could take into account the 50% requirement for ArbCom by simply dropping candidates who received less than that level of support from the pool from which the optimal set of winners is identified.e ★NealMcB★ (talk) 01:33, 25 November 2018 (UTC)[reply]
@Nealmcb: As outlined above, not only does the community have to decide to switch voting systems, the chosen system needs to have a software implementation. So unless you are willing to implement PAV into SecurePoll, this won't be even an option. Regards SoWhy 12:31, 25 November 2018 (UTC)[reply]
@SoWhy: Yes indeed. I've inquired on the SecurePoll Talk page about whether the necessary data is available. I think it best to do some investigation of how it might work (there?), along with community conversation around the desired goals (here) in order to proceed. ★NealMcB★ (talk) 01:45, 26 November 2018 (UTC)[reply]
Nealmcb, were you able to get an answer about this? StudiesWorld (talk) 11:02, 1 July 2019 (UTC)[reply]
  • Perhaps Meek is best for single transferable vote methods. Personally I prefer methods that take into account the ranked preferences of all voters, not just some of them (those who voted for candidates that exceeded quota, or for candidates that are getting excluded for finishing last). But this can be discussed further at a later time. isaacl (talk) 23:02, 23 November 2018 (UTC)[reply]

General/Other

ACERFC decisions to date

  • In discussion about issues, prior year RfC's were noted by some participants - but the community shouldn't be expected to find the rules for the election by having to go through every past RfC should they? Current version of all decision should be published in one location. (examples include how to deal with block and their timing during the various phases, curation of candidate questions, etc). — xaosflux Talk 14:06, 12 November 2018 (UTC)[reply]
    Just list them at the start of the RFC before the RFC starts, like in 2013. I've gone through and noted the decisions. I'll post it later when I've translated it into actual English from my chicken scratch. -- KTC (talk) 15:01, 12 November 2018 (UTC)[reply]
ACERFC decisions to date
  • Election: There will be 13 arbitrators, six seats on "Tranche Alpha" from the 2018 elections and seven seats on "Tranche Beta".[1] A maximum seven 2-years term are up for elections each year,[2] with the seventh seat switching tranche if necessary.[3] Any additional vacancies which open before voting begins[4] will be filled by a 1-year term.[2] A minimum 50% support is required to be elected for a 1-year term, with a minimum 60% support is required for a 2-years term.[5] Successful candidates with the lowest support percentages are given the 1-year term if any.[6] If there are more vacancies than candidates with the required minimum, the extra seats will remain unfilled.[α][7]
  • Candidates: Registered account with 500 mainspace edits,[β] editor in good standing "that is"/"and is"[γ] not under block or ban, meets Foundation's Access to nonpublic personal data policy,[δ] and has disclosed alternate accounts (or disclosed legitimate accounts to Arbcom).[8][9]
  • Electoral Commission: A RFC to appoint 3 Electoral Commission officials who will solve disputes and problems during the election.[10] Commission should only intervene when there is a problem that needs resolving, and either discussion isn't working, the rules are unclear, or there isn't time.[11] Open to anyone who is over 18, meets Foundation's Access to nonpublic personal data policy,[δ] and otherwise be eligible to vote.[12] Appointments to the Commission should be confirmed by the Arbitration Committee per the CheckUser policy.[δ][ε][12]
  • Timeline:
    • ACE RFC: (30 days of September)
    • Electoral Commission RFC: 7 days nominations, 7 days evaluation, selection by 7 days after close of evaluation.[ζ][12] (October)
    • Nominations: 2nd Sunday of November (10 days)[13]
      • Nomination is hard deadline for creation and transclusion of nomination statement. How to handle any site-wide disruption is at the discretion of the Electoral Commission[14]
    • Fallow period: (5 days)[13]
    • Voting period: (14 days)[13]
    • Scrutineering: No deadline for releasing or announcing the results.[15]
  • Guides: Allowed but with some strong suggestions.[16] Must be allowed reasonable visibility.[17]
  • General Guide: Wikipedia:5 Minute guide to ArbCom Elections created and advertised.[18]
  • Voting: A voter needs 150 mainspace edits by 1 November and registered an account before 28 October,[η][19] not currently blocked at the time of voting.[19][20] Voting system of (Support/Abstain/Oppose) will be used[21] with percentages calculated via Support/(Support + Oppose).[22] Secret ballots[23] via SecurePoll will be used.[θ]
  • Scrutineering: 3 functionaries[ι] from outside en.wiki as scrutineers.[24]
  • Ordering: The order of candidates are software randomised on the candidate page, and on the ballot.[25]
  • Warning: Potential candidates are warned of risks from standing for election with message similar to that on WP:CUOS2015 to be incorporated into the candidate instructions page.[26]
  • Questions: No standard questions for every candidates.[27] No limits on the number of questions, but candidates are not obligated to answer every questions.[28] Electoral Commission (as a group not individually) have the discretion to remove offensive (eg. WP:POLEMIC-style statements) or off-topic questions from question pages, following discussion among the Electoral Commission members. While other editors can obviously remove clear vandalism, egregious personal attacks, etc., the determination of what is inappropriate or off-topic is clearly to be left to the Commission.[29]
  • Advertising: Traditional notices posted to various community noticeboards,[30] watchlist notice and/or central notice banner[31][32] for election in general (not individual candidates),[31] Mass Message - eligible voters, have edited last 12 months before nominations.[33] Extra care should be taken in wordings of advertising to make sure it's neutral.[34]
  • Blocking: Blocking policy applies normally, but a candidate shouldn't be disqualified for being blocked (except for sockpuppetry) after nominating him/herself.[35]
  1. ^ De facto carried over from pre-2012.
  2. ^ Transcription error from 2011 to 2012 election. De facto since. Consensus against proposed changes in 2016.
  3. ^ Changes during transcription from 2010 to 2011 elections.
  4. ^ a b c WMF's requirement.
  5. ^ Not in practice.
  6. ^ De facto community evaluation from start of nominations.
  7. ^ Left-field supervote on account registration date.
  8. ^ De facto since 2009.
  9. ^ Stewards de facto since pre-2012

References

  1. ^ 2018#Number of arbitrators
  2. ^ a b 2013#Length of terms
  3. ^ 2013#Handling of the 8th Vacant Seat
  4. ^ 2012#How should vacancies be handled?
  5. ^ 2018#Percentage support needed for appointment
  6. ^ 2012#How many seats should be 2-year terms, and how many 1-year terms?
  7. ^ 2011#Fundamental mechanics
  8. ^ 2012#What should the requirements be for candidates to run for the election?
  9. ^ 2014#Disclosure of Previous/Alternate Accounts of the candidates
  10. ^ 2012#How should we deal with unforeseen problems?
  11. ^ 2013#Role of the Election Commission
  12. ^ a b c 2014#How should the selection of the election commission be conducted?
  13. ^ a b c 2013#Schedule
  14. ^ 2015#How should nomination deadlines be handled?
  15. ^ 2012#Deadline for releasing the results
  16. ^ 2012#How should voter guides be handled for the election?
  17. ^ 2014#Should voter guides be included in the official template?
  18. ^ 2018#Write a short general guide to voting
  19. ^ a b 2012#What should the requirements be to vote in the election?
  20. ^ 2011#What should the requirements be to vote in the election?
  21. ^ 2013#Voting procedure: proposing change "No vote" to "Abstain"
  22. ^ 2012#What should the method of voting be?
  23. ^ 2012#Secret balloting?
  24. ^ 2015#Should adjustments be made to expedite the election results?
  25. ^ 2016#Should the names of candidates appear in randomized order, and if not, how should they be ordered?
  26. ^ 2016#Should we warn the candidates about the risks involved?
  27. ^ 2014#The standard questions
  28. ^ 2014#Should there be a limit to the number of questions posed to candidates?
  29. ^ 2017#Should election committee members be allowed to remove questions where appropriate?
  30. ^ 2012#Advertising
  31. ^ a b 2015#Should there be a change in the methods of publicity for the election?
  32. ^ 2016#Should we continue or modify the practice of notifying eligible voters by mass message?
  33. ^ 2018#Mass message
  34. ^ 2014#Should the site notice be changed when voting begins?
  35. ^ 2013#Blocking candidates

Users who would like to be notified when the 2019 RFC begins

This initial list was based on comments at Wikipedia talk:Arbitration Committee Elections December 2018. Notification will likely take the form of a talk page message, which will be in addition to all the usual watchlist notices and other publicity. Anyone may add or remove themselves as they wish at any time. Thryduulf (talk) 12:00, 14 November 2018 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Requests_for_comment/Arbitration_Committee_Elections_December_2019&oldid=909798999"