Revision as of 15:37, 31 October 2026 view source Maintenance script (talk \| contribs) 9,325 edits Adapt local policies, template notices and guidance for independent Elite Dangerous Wiki; preserve index layout		Latest revision as of 16:56, 1 November 2026 view source EliteMaintenanceBot (talk \| contribs) Bots 1,091 edits Set up local noticeboards, elections and community request workflows
Line 1: {{Governance navigation}} '''Bureaucrat elections and appointments''' provides guidance for considering a bureaucrat role on this independent Elite Dangerous Wiki. Read it with [[Project:Administrators]], [[Project:Requests for permissions]], [[Project:Consensus]] and [[Project:Community standards]]. '''Bureaucrat elections''' records nominations, candidate acceptance, community discussion and decisions. Read [[Project:User groups]] and [[Project:Consensus]] before nominating. == Role and authority ==▼ The name “bureaucrat” may describe a local governance role, but its existence and technical capabilities must not be assumed. The actual groups and actions configured on this wiki are shown in [[Special:ListGroupRights]]. This page does not create a bureaucrat group or grant the ability to change user rights. ▲== Role ~~and authority~~ == ~~== Nominations and consideration ==~~ Bureaucrats manage bounded local appointments, including administrators and approved bots. Only a site operator can implement a bureaucrat appointment. Bureaucrats cannot appoint another bureaucrat or grant interface, privacy or site-operator access. A request to appoint or elect a bureaucrat should be raised openly on this page's discussion page. A nomination requires the candidate's agreement. The candidate should explain their relevant community contributions, understanding of local policies, approach to careful and accountable handling of permissions, and any relevant conflicts of interest. Other editors may ask questions and discuss the evidence respectfully. == Start a nomination == Consider the candidate's judgement, reliability, impartiality, and willingness to explain consequential decisions. Consider reasoned contributions on their merits; a count of support comments alone does not establish consensus. Follow [[Project:Consensus]] and allow a reasonable opportunity for discussion. Use a subpage named for the candidate and date, for example <code>Candidate name/2026-11</code>. Enter that suffix below. Check the active nominations first to avoid duplicates. <inputbox> type=create prefix=Elite Dangerous Wiki:Bureaucrat elections/ preload=Elite Dangerous Wiki:Bureaucrat elections/Preload buttonlabel=Create nomination placeholder=Candidate name/YYYY-MM width=40 break=no </inputbox> The candidate must accept before discussion starts. A nominator may nominate themself. Describe relevant contributions, judgement, policy knowledge and conflicts. No automatic edit-count qualification or percentage vote threshold applies. Suggest a review date that leaves time for participation, normally at least seven days after acceptance; extend it if participation is insufficient. Reaching that date never appoints anyone or forces closure. == ~~Decision~~Active ~~and implementation~~nominations == <categorytree mode=pages>Open bureaucrat elections</categorytree> The discussion should state whether the outcome is an appointment, an election result, or no change, and summarise the reasons. This guidance sets no numerical vote threshold, fixed candidacy requirement, or term of office. Do not infer one from imported templates or examples. == Discussion and decision == A community decision and a technical permission change are separate steps. Only an account with the actual configured authority can make a group change, and the live permission list and rights log are the records of what was technically changed. If an agreed change cannot be made under the current configuration, record that constraint and do not imply that a community decision itself changes permissions or makes the role technically available. Ask questions and give reasoned support, opposition or neutral comments with evidence. Sign comments with four tildes. Do not canvass for a predetermined outcome or create additional accounts to influence discussion. Comment counts do not establish consensus. An uninvolved bureaucrat or site operator should close administrator nominations; a site operator closes bureaucrat nominations. A closer who is the candidate or nominator must seek independent review. If no eligible uninvolved closer is available, leave the nomination open and ask for assistance on the bureaucrats' board. Explain the consensus, or record no consensus, withdrawal or need for more discussion. Do not infer approval from silence. The closer sets <code>status=closed</code> in the banner and records a signed rationale. The authorised rights manager performs any agreed change through [[Special:UserRights]] and adds the rights-log link to the nomination. The bot only reports dates and maintains archives; it cannot decide elections or grant rights. == Past nominations == [[Special:PrefixIndex/Elite Dangerous Wiki:Bureaucrat elections/\|Browse nomination subpages]] · [[:Category:Closed local elections\|Closed nominations]] == Review and resignation == Raise evidence-based concerns or a voluntary resignation at [[Project:Bureaucrats' noticeboard]]. An authorised rights manager may remove access where needed and must record a reason. Ask an uninvolved authorised editor to review a disputed outcome. There is no automatic term of office.

Elite Dangerous Wiki:Bureaucrat elections: Difference between revisions

EliteMaintenanceBot (talk | contribs)