Forum:Vote: User rights request policy addendum 1.1

	This forum page has been archived. Please do not make any further edits unless they are for maintenance purposes.

The vote below determines support for the proposal discussed here. Gaining approval, the following will be reflected in the user rights request policy. Thank you for your time in voting on the following. -kdarrow ^{take her for a spin!} 20:58, 27 January 2022 (UTC)

Proposal

This proposal seeks to add a new user rights role entitled technical moderator. This role is intended to run parallel with content moderator as an edit-focused staff member, the scope of which comprises of technical aspects of the wiki as opposed to the content within the articles.

Those who are proficient with MediaWiki, CSS/JS, and advanced template functions cannot function autonomously as these namespaces are protected by default. Historically, has been implemented on our wiki on a temporary case by case basis and this proposal moves to create a designated role among existing user rights distinctions.

Function

Serving to bridge the gap between content moderator and administrator, this proposal aims to provide technical moderators access to sysop-level tools without expectations of serving in the same capacity as an administrator. Use of tools outside of the intended scope, such as placing user blocks, will not be expected or allowed. With the exception of access to MediaWiki level articles, the role will function parallel to content moderators both wiki side and in Discord.

Requirements

Conclusion

The role will benefit our wiki by offering tools to our most technically proficient users, empowering those with technical expertise to troubleshoot and implement fixes proactively, assist with requests and technical inquiries, as well as act as a liaison, engaging with Fandom and our wiki representative regarding potential issues and solutions. It will be ideal for those who have the technical capabilities and enthusiasm for improving the wiki behind the scenes, but who do not wish to serve in an administrative capacity. Thank you for reviewing this proposal regarding this new role and feel free to cast your vote below.

Vote

Poll finished on 7:42 pm February 2, 2022 (UTC). A consensus must be reached by voting before any action is taken. You can vote by placing one of the following lines in the appropriate section: Use # {{yes}} ~~~~ if you support the proposal. Use # {{no}} ~~~~ if you are against the proposal. Use # {{neutral}} ~~~~ if you wish to abstain. Please do not edit other user's votes.

Yes

1. -kdarrow ^{take her for a spin!} 21:55, 27 January 2022 (UTC)
2. Rubbinmahbelly (talk) 22:31, 27 January 2022 (UTC)
3. This is going to make things so much easier for those of us who have to bug admins/crats to make changes to the css/js files since we don't have access. Not to say that we are annoying, but I can TOTALLY get annoying about it XD. -Eckserah ^{Head Dataminer} 23:12, 27 January 2022 (UTC)
4. The Appalachian 08:59, 28 January 2022 (UTC)
5. Under the premise that the tools actually get used. –Findabair^{The benefit of the doubt is often doubtful.} 10:15, 28 January 2022 (UTC)
6. Aok plan my dood bow burger box 00:32, 29 January 2022 (UTC)
7. shore JustDoggo2 The Warden of the Escapists Wiki 01:42, 29 January 2022 (UTC)
8. LovinglyGaslight (talk) 22:52, 29 January 2022 (UTC)
9. -SeriousHex Having someone who knows their stuff to help troubleshoot things, yes please.
10. Agent c (talk) 23:13, 29 January 2022 (UTC)
11. ---bleep196- (talk) 00:53, 30 January 2022 (UTC)
12. Scribe-Howard (waster_93) (talk) 23:37, 30 January 2022 (UTC) - This is a common sense split, especially as our toolbox keeps expanding.
13. Sounds good to me boss -Dare Rodeo IX 06:45, 31 January 2022 (UTC)
14. Gilpo1 (talk) 15:09, 31 January 2022 (UTC)
15. The Dyre Wolf (talk) 15:40, 31 January 2022 (UTC)

No

Neutral

Result

This vote passes and will move to implementation. -kdarrow ^{take her for a spin!} 09:13, 5 February 2022 (UTC)