Requests for global rights

Requests for global rights This page is designed to be a place to organize all requests for global rights. Rights which can be requested: Global Sysop Interwiki administrator Note: Stewardship is requested at Requests for Stewardship only. Global IP block exemption requests can be made at Stewards' noticeboard, if the user is able to edit on-wiki, or via e-mail to stewardsmiraheze.org, if the user is not able to edit on-wiki, provided there is both a well articulated rationale and need for an exemption Notes: New requests should be created via the button below to preload recommended fields. There is no fixed time requirement for requests to stay open, but a 7 day period is often recommended in order to give users time to discuss any potential issues, and the candidate should address any concerns raised by members of the community. Remember to update Meta:RecentChanges/Requests with the link to your request. To add your request, click the "Add request" button below.

Closed requests for global rights [e]
Archive 1 - until 19 December 2019 Archive 2 - until 3 June 2021 Archive 3 - current

Ugochimobi's Request for Global Sysop

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.

Unsuccessful; does not meet the requirement for ten (10) unique users, other than the candidate themselves, to have expressed a view. Though Magogre has replied to Anpang and may or may not count towards one of the unique users, it still is not met because that would only be nine (9) users, other than the candidate themselves. Aside from that, chief concerns seem to be the candidate's ability to not only understand but interpret and apply our global policies as well as a lack of a Counter Vandalism Team activity, though the candidate is thanked for their efforts as an interwiki administrator globally. Dmehus (talk) 22:21, 30 December 2021 (UTC)

---

User: Ugochimobi (contributions • CA • blocks log • rights log • global rights log)

Reason(s) for request

I'd like to express my interest in joining Miraheze's Counter Vandalism Team of Global Sysop and also assisting current Stewards.

After speaking with some active community members and of course, looking at my unsuccessful request for stewardship, when I was advice to go with the GS role, I have decided to request this bit at this time.

I want to be a plus one to the current global sysops, in fighting cross-wiki spam and vandalism. I believe I have a sufficient understanding of and command of MediaWiki to use pages like Special:Multilock (where I need to fill in the box with a list of spambot or vandal accounts, one per line, select lock, and provide a good reason.) and Special:GlobalBlock (which blocks the IP address across all of Miraheze based on what was set; does not apply on meta unless the option on meta is ticked, which should only be used for good reason because it removes the IP's ability to appeal on meta). In accordance with the policy of Global Sysops, I comprehend that I will have limited sysop-style rights across all wikis, and that I should only use my tools if the local sysop or crat fails to respond to vandalism, If global or local filters are triggered and not responded to in a reasonable amount of time, or if I receive a direct request for assistance from a member in good standing with that wiki community. I am capable of dealing with issues on a global scale, and I have demonstrated this ability. Because I live in Africa, specifically Nigeria, I am going to be able to cover the UTC+1 timezone. I regularly monitor all wikis' recent changes feeds via IRC/Discord, which has aided me in personally determining when something happens on Miraheze. I have a competent knowledge of the current global policies, including but not limited to our Code of Conduct, User accounts policy, Username Policy and of course the Global Sysop's policy. I am generally active accross all Miraheze's platforms (Noticeboards, Discord, IRC, et cetera.) I believe even in my deepest "I know what to do", that I wouldn't hesitate to seek advice from a fellow Global Sysop.

Please do not hesitate to use the comment section below to leave your comments, Thank you very much. --  Joseph  TB  CT  CA  00:22, 23 December 2021 (UTC)

Questions for candidate

1. Global Sysops chiefly work in the field of counter vandalism. What previous experience do you have in global counter vandalism? Agent Isai ^{Talk to me!} 00:31, 23 December 2021 (UTC)

   Thanks for this question. Counter vandalism from a global viewpoint is a serious part of Miraheze that needs a close headup. I normally watch the feeds and report any fishy behaviour I see from there. Globally, since I haven't been a global sysop before, I haven't directly handled requests to lock or block any account. However, with my technical understanding of how the role works, I can handle global counter vandalism. --  Joseph  TB  CT  CA  01:08, 23 December 2021 (UTC)

2. Did you speak with any members of the Counter Vandalism Team about your Request for Global Sysop before you filed it? If so, have they mentored you about this? Agent Isai ^{Talk to me!} 00:31, 23 December 2021 (UTC)

   Yes, I spoke with a current CVT member, and No, I was not mentored (perhaps I misinterpreted what you meant by mentored). --  Joseph  TB  CT  CA  01:08, 23 December 2021 (UTC)

3. Recently, a dispute occured in a wiki you helped manage which resulted in you mass deleting pages, could you clarify why that was and additionally assure us (and demonstrate) you can keep a cool head under stressful situations? Agent Isai ^{Talk to me!} 00:31, 23 December 2021 (UTC)

   Oh yes, I normally have a cool head under stressful situations. I mean that incident occurred when He (the other user) started threatening me on telegram with sort of words, although I don't want to go deeply into that, but I don't think that has to do with my request. But in a nutshell, I don't easily get tensed under stressing and pressing situations, I am normally cool tempared. --  Joseph  TB  CT  CA  01:08, 23 December 2021 (UTC)

4. Under what circumstances would you apply a global lock/block and why? When global locks/blocks should not be used and why? --Magogre (talk) 03:06, 23 December 2021 (UTC)

   Thanks Mag for this question, I'm am not the wordy type, but my reply to this in a nutshell is that Global locks/blocks should only been used on IPs or accounts that have spammed cross-wiki (globally), or account(s) that's was created as a suckpuppet of a globally locked or block user (and that should be obvious) for example this Abigblueworld's case that has been ongoing for the past weeks now, or an account that violates the Username Policy (before a total block/lock, the user should be notified that their username violates our username policy), et cetera. This action shouldn't be taken if the account vandalises just one wiki, perhaps a local block by a local staff of that wiki would be better. --  Joseph  TB  CT  CA  05:13, 23 December 2021 (UTC)

5. What is long term and cross wiki abuse? What does the word abuse mean to you as the global sysop? How would you deal with it (LTA, X-Wiki and abuse)? --Magogre (talk) 03:06, 23 December 2021 (UTC)

   Generally Long Term/CrossWiki Abuse is when a user uses their account to continuously spam, vandalise, disrupt wikis for a long time probably after a notice or warning. Abuse isn't just about misusing an opportunity, abuse is to repeatedly misuse an opportunity. But for LTAs, I wouldn't mind giving them a warning on their talk page about their editing behaviour. --  Joseph  TB  CT  CA  05:36, 23 December 2021 (UTC)

6. How will you find out if an account is a spambot or not? --Magogre (talk) 03:06, 23 December 2021 (UTC)

   If an account is bad egg, it would be visible and clear to anyone watching the Global Recent changes feed. Their editing behaviour could also tell. (I might have more reply to these later on, as I'm currently on mobile). --  Joseph  TB  CT  CA  05:36, 23 December 2021 (UTC)

Support

1. Support I was waiting for him to answer here. In general, I have never seen this user doing anything wrong and we may need global sysops (2) these days. He helps by putting interwikis on the table by discord (as joseph) and on the wiki. If he's already made a serious mistake (I never noticed), it's normal and you learn from mistakes. --YellowFrogger • (Talk — ✐) 02:29, 23 December 2021 (UTC)
2. Support Helpful and kind. Generally seems to be a helpful guy, so this is my !vote.  However, if any sketch happens regarding canvassing I'll move to oppose. I hope you get Global Sysop. -- Cheers, Bukkit ^{( Talk • All Contribs )} 00:21, 24 December 2021 (UTC)

Abstain

1.  Neutral leaning weak oppose  Anpang📨  01:05, 23 December 2021 (UTC)

   Anpang, will you please describe why are you neutral and leaning towards weak oppose on this request. Your reasoning may be helpful for other to determine their !vote. --Magogre (talk) 14:41, 23 December 2021 (UTC)

2.  Neutral I thank Ugochimobi for his boldness and willingness to help undertake the counter-vandalism workload but I do believe this is a very strong case of WP:NOTQUITEYET, particularly in the field of Ugochimobi's global countervandlism work. I would strongly suggest Ugochimobi first participate in the work more by reporting global vandalism and reverting it before requesting tools once he's demonstrated a clear need for them as I do not see any a valid need in this case for tools due to his general lack of global counervandalism work. I spoke with Ugochimobi in private who said a current Global Sysop told him to wait and I do agree with that assessment, it would be better if he waited and participated more in the work before requesting the Global Sysop hat. Additionally, the recent incident on FAMEPedia does make me question his ability to maintain a cool head so I would like for Ugochimobi to work during this time to assure the community he can keep a cool head during stressful situations to prevent taking rash decisions. Agent Isai ^{Talk to me!} 08:43, 23 December 2021 (UTC)

Oppose

1. I cannot support this >> [1] <<,--MrJaroslavik (talk) 12:11, 23 December 2021 (UTC)
2. Oppose Sorry Ugochimobi, but I have to agree with what MrJaroslavik has said in his oppose. Maybe come back in about 6 months when everything is squared away. --DarkMatterMan4500 (talk) (contribs) 00:53, 24 December 2021 (UTC)

   @DarkMatterMan4500: Hi, I have full respect for your oppose, also, I'm not the candidate but this little problem cited occurred 5 months ago, so we should give it a chance. Since then he must have changed a lot. --YellowFrogger • (Talk — ✐) 00:57, 24 December 2021 (UTC)

3. Oppose After thinking about this request for some time, I feel I have to NOTYET this request. Looking over your CA and the associated contribs, I also don't see much evidence of effort within global countervandalism. As I frequently express, learn to use "undo" to the best of your ability before requesting additional tools. dross (t • c • g) 05:49, 28 December 2021 (UTC)
4. Oppose I have to concur with Dross here. I don't think it's necessarily fair to still hold the previous canvassing over you, which occurred 5 months ago, but I do feel that the lack of demonstration to the need of these tools and the ability to perform in counter-vandalism leads me to oppose this request. I encourage you to do to the best of your ability counter-vandalism without these tools before re-requesting.
   —［ Universal Omega ］［ Talk | Contributions | Guestbook  05:55, 28 December 2021 (UTC) ］ |

---

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section

Arcversin‎'s Nomination for Global Sysop

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.

There is a strong consensus here that the candidate is trusted, technically competent if not very proficient, amicable, and generally well liked. It's so strong, in fact, that this view is unanimous, as far as I can tell from my read of the salient points of this community discussion. The community's principle concern is Arcversin's relatively modest number of global edits on Miraheze and on Meta Wiki together with the relative new-ness of his account. It's important to stress, though, that as Arcversin rightly pointed out, to which Agent Isai concurred, it is edit quality over quantity that matters. That being said, quantity does matter to a certain extent when it comes to assessing current and recent Miraheze counter-vandalism experience, as the community does not want another "fly-in, fly-out" Global Sysop as several users, including DeeM28 but chiefly Agent Isai, have pointed out. They want to know the user will be here to stick around over the medium- to long-term and maintain a reasonable level of volunteer activity for the specific role. Sadly, though, to do an effective job actual counter-vandalism and spam remediation work as a Global Sysop requires global permissions. To obtain an advanced permission such as Global Sysop requires activity and on-wiki Miraheze counter-vandalism experience. Without even a minimum of global user rights as a counter-vandalism volunteer, one is at a strategic disadvantage against a vandal, vandalism only account or LTA. This presents the age old catch-22 situation where the situation is difficult either way. We do struggle with attracting and retaining active, technically competent, policy-compliant, and policy knowledgeable community volunteers as well as technical volunteers, especially technical volunteers, but the community, and, indeed, Stewards as well, have set a particularly high bar of expectation for the Global Sysop role, chiefly because the role has the centralauth-lock user right and assists Stewards with enforcing our global policies, so are expected to have solid analytical and judgment skills. So, this global permission request actually underscores that we don't have a sufficient number of global groups able to assist Stewards and serves to inform an RfC I will aim to bring forward in the next several weeks to establish another global counter-vandalism role. As an alternative, I would also present an alternative proposal for the community's alternate consideration, which would be to instead remove certain high competency, "high bar" user rights (i.e., centralauth-lock) from the Global Sysop toolkit, but the current situation of having two very "high bar," high community expectation global user groups is insufficient to continue with Miraheze's growth (and no, Bukkit, I've already got the draft partially started, so do not create one). Additionally, as permitted by the Stewards policy, I will be consulting with existing Stewards regarding the potential creation of a Steward-delegated global-abusefilter-helper global group, as Arcversin clearly has the technical skills (as evidenced by this abuse filter suggestion implemented) the Steward and Global Sysop groups (excluding Void, of course, who clearly has the technical competency/proficiency when it comes to JavaScript and abuse filters that Arcversin does). Stewards would then, in turn, consult with the community on the ways in which this group should be used, any prerequisites that should be required, and any revocation criteria. That being said, Arcversin is thanked for agreeing to have raidarr put his name forward for consideration, and for all that he does for Miraheze, whether it be improving or adding Lua modules on Meta Wiki, gadgets on TestWiki and Meta Wiki, or with approving and declining wiki requests (for which he's one of the most active wiki creators). Dmehus (talk) 02:52, 7 April 2022 (UTC)

Addendum to address one of Agent Isai's points with respect to Username Policy: Global Sysops can, and do, enforce Username Policy. This is likely just a case where the policy language has not caught up with more contemporary events, so I will aim to correct that this weekend as well. That being said, Global Sysops should only be enforcing only the clearest cut Username Policy violations, leaving the more edge cases (in terms of potential offensiveness and the trolling criterion) to Stewards. Dmehus (talk) 03:01, 7 April 2022 (UTC)

---

User: Arcversin‎ (contributions • CA • blocks log • rights log • global rights log)

Reason(s) for request

Greetings Miraheze. After conferring with the candidate and a few others, I have decided to nominate Arcvee as a platform Global Sysop. I believe he has a more than adequate understanding of global policies, and importantly judgement to oversee them properly and defer when uncertain, or communicate when multiple opinions are needed. Aside from that he has considerable experience on Miraheze and a strong background, quite acceptable activity and invaluable knowledge in handling abuse filters and other technical issues that would be a boon to have in CVT duties and in assisting Stewards. Thus, I first request that he accept this nomination - I don't expect trouble - and for the community to see his potential, as well as the value of more talent and more hands on deck as Miraheze grows. Thank you for your consideration. --Raidarr (talk) 23:56, 28 March 2022 (UTC)

I accept this nomination, and am grateful to Raidarr for his kind words. I welcome the community's questions. — Arcversin (talk) 00:19, 29 March 2022 (UTC)

Questions for candidate

1. Global Sysops are chiefly a countervandalism role. What previous countervandalism experience (if any) do you have that would make you a good candidate for the bit? Judging from a quick glance at your Miraheze and Wikimedia CentralAuth, you do not seem to have any so is there something I am missing potentially? Agent Isai ^{Talk to me!} 00:54, 29 March 2022 (UTC)

   In terms of countervandalism experience, I am an antivandalism patroller and rollbacker on the English Wikipedia, and on Miraheze, I am engaged in combating vandalism and LTA activity (particularly on Meta, as you can see from my activity), and have in fact designed a userscript to assist in combating RequestWiki vandalism. Furthermore, I actively monitor Miraheze's IRC feeds, which are important tools in monitoring for vandalism and responding to user reports. — Arcversin (talk) 01:14, 29 March 2022 (UTC)

   Thank you for your response. Reviewing your English Wikipedia contribtions, I will note many contributions are concentrated in on certain days/few days before a total halt in them for a while and then a repeat in the cycle a few weeks/months later. I see you make use of tools such as Huggle extensively to make the bulk of your edits. Do you primarily use tools all the time when engaging in any countervandalism duties on the English Wikipedia or any other wiki? Agent Isai ^{Talk to me!} 00:11, 30 March 2022 (UTC)

   I find tools to be incredibly useful in countervandalism activities on the English Wikipedia, given their ability to automate common tasks such as warning and filing reports, and to digest sheer quantity of edits on enwiki. — Arcversin (talk) 01:32, 30 March 2022 (UTC)

2. Do you plan on staying active should this request be successful? We do not need another Global Sysop who pops up once in a blue moon. Agent Isai ^{Talk to me!} 00:54, 29 March 2022 (UTC)

   I already plan on remaining active, and will necessarily become more active should this request succeed given the assumption of greater responsibilities. — Arcversin (talk) 01:14, 29 March 2022 (UTC)

   Thank you for your reassurance. I look forward to that commitment should this request be successful. Agent Isai ^{Talk to me!} 00:11, 30 March 2022 (UTC)

3. Global Sysops "assist Stewards in supporting the community and working with communities to address issues facing them locally," based on your interpretation of policy, what is the scope of Global Sysops and when do they become involved in matters? Agent Isai ^{Talk to me!} 00:54, 29 March 2022 (UTC)

   As defined by policy, Global Sysops have the responsibility to assist local communities and the Stewards by becoming involved in situations in which local sysops/bureaucrats have not responded to disruptive activities in a reasonable amount of time. A Global Sysop thus becomes involved in local matters when their involvement would be unambiguously welcomed by the local community, which primarily consists of combating routine vandalism and LTA activity. What exactly is meant by a reasonable amount of time is dependent both on the egregiousness of the vandalism and whether the local sysops merely haven't responded, or are inactive long-term. In situations where the local sysops merely haven't responded, Global Sysops should lean towards deference, preferring only short-term blocks in most cases, while if the local sysops are inactive, Global Sysops should be more willing to take action. This balance also takes into account the severity of the disruptive, as, for example, porn vandalism is essentially always worthy of immediate involvement. In situations which are ambiguous or controversial, ultimate discretion lies with the Stewards, and Global Sysops should refrain from taking unilateral action, and consult with others. Furthermore, Global Sysops have the responsibility to enforce global policies and counter disruptive actions on a global basis, which ranges from blocking LTAs, cross-wiki vandals, and particularly egregious single-wiki vandalism-only-accounts, to enforcing the Username Policy and the No open proxies policy. Situations in which a wiki itself is engaged in the violation of global policies are the responsibility of the Stewards, and the situations in which I can imagine GS action being warranted (goatse on the main page, malicious scripts, that sort of thing) moreso resemble account compromises or someone requesting a wiki for trolling purposes. — Arcversin (talk) 02:49, 29 March 2022 (UTC)

   Thank you for your response. I have no issues with your understanding of the Global Sysops policy page though I will note that Username Policy enforcement action should only be carried out by Stewards though Global Sysops are well within their right to warn any offending user and request they change their username. Additionally, please note that Global Sysops do not enforce all global policies. Policies like the Terms of Use are rather obviously enforced by Trust and Safety and there are also a few other policies which are not enforced by Global Sysops either. Agent Isai ^{Talk to me!} 00:11, 30 March 2022 (UTC)

4. To those who would point out that you have little edits on Meta (~360) and globally (~1500) and a very short track record, what would you say to them? Agent Isai ^{Talk to me!} 00:54, 29 March 2022 (UTC)

   I would remind them that it is the quality, not the raw quantity of edits that matter, and that neither logged actions, such as wiki creations, nor off-wiki engagement with the community, are included in ones edit count. I would also ask them to define what they mean by a "very short track record", and to substantiate that claim. I would also ask them to elaborate as to why they disagree with the judgment made in the nominating statement. — Arcversin (talk) 03:10, 29 March 2022 (UTC)

   Indeed, edits are not always a good way to measure a candidate's preparedness but they can assist in gauging the amount of community interaction one has had. After all, the community cannot agree to promote someone who they've barely interacted with. In order to assess a candidate, the community should be well acquainted with them in order to be able to determine whether their behavior, their knowledge and application of local and global policies, along with other factors make them a good candidate. For that reason, I would argue that community engagement is very important for this role and that edit counts are one way to, at a glance, get a gist of the user's interactions with the community and to know whether they've been around enough to help the community get a good glimpse of them. As for "very short track record," one could argue that you have a little countervandalism track record that mainly concentrates on clusters of edits on the English Wikipedia and not many here on Miraheze apart from the occasional rollback here on Meta. What would you say to them? That may not paint a good image of commitment to some or, if you were requesting the bit yourself, could paint an image of hat-collecting. Agent Isai ^{Talk to me!} 00:11, 30 March 2022 (UTC)

5. This request reminds me very much of your very recent previously unsuccessful requests for administrator (1, 2) where your main points for the bit was your experience in Abuse Filter and the main points against you were that it was too soon to be requesting the bit. What makes this request different to those? What has changed in the past month from both of those requests that allows you to take on a much higher global role? Agent Isai ^{Talk to me!} 00:54, 29 March 2022 (UTC)

   I would disagree with your assertion that the primary point of opposition was WP:NOTYET (which is about early closures for very new users), rather, it was a lack of a properly articulated rationale alongside a feeling that there wasn't much of a need for additional Meta sysops. — Arcversin (talk) 03:25, 29 March 2022 (UTC)

   Fair, the main points of opposition to your RfP were that there wasn't really a need demonstrated in your request reason which could stem from a lack of articulation but there were a few points raised against you in the area of low activity (other than wiki creations which is your main specialty currently) which could correlate into the request being done too soon. This still does not answer my question of what makes this request different from that and what makes you feel confident that you can tackle a higher global role. Additionally, to those who may question why despite low activity (apart from wiki requests), locally and globally, you are seeking the bit, what would you tell them? Agent Isai ^{Talk to me!} 00:11, 30 March 2022 (UTC)

6. Are there any recent examples that can allow us to see clearly that you are well acquainted with both local and global policies? Agent Isai ^{Talk to me!} 00:54, 29 March 2022 (UTC)

   Would you mind asking a specific policy question? This is quite broad and I'd like to know what you're looking for here. — Arcversin (talk) 03:47, 29 March 2022 (UTC)

   Any really. Whether it's a good example of you being able to mediate a dispute using a policy, citing a policy correctly, handling a difficult wiki request correctly in accordance with policy and global convention/best practice, etc. Agent Isai ^{Talk to me!} 00:11, 30 March 2022 (UTC)

   One example in which I applied the Content policy would be in the case of wiki request #23690. The Miraheze Content policy requires that Content on wikis must be fairly balanced, meaningful or substantiated by independent referencing, although Wikis which have a clearly identifiable comedic or satire value are exempt from needing to substantiate claims. The (initial) contents of this request indicated that the user was requesting a Wikipedia-style general encyclopedia (as opposed to an ideological encyclopedia such as socdemwiki) in which the contents of the wiki would "follow Beijing's official stance on all issues". The request indicated that this "official stance" would be presented as factual information in the wiki's own voice, as opposed to being presented as the stance of the Chinese government. As this characteristic was defining, the requested wiki thus ran afoul of the aforementioned provision, and considering that the wiki did not fall under the exception for comedic wikis, I declined the wiki request citing said provision. — Arcversin (talk) 04:07, 30 March 2022 (UTC)

Support

1. Strong support This user has shown knowledge of the policies, and in my opinion, would fit for Meta Sysop. With their knowledge of JS, policies, and AF, they would help with the CVT work significantly. -- Cheers, Bukkit ^{( Talk • All Contribs )} 00:03, 29 March 2022 (UTC)
2. Support Has been very supportive, and helped out with handling wiki requests alongside a few other things that I can't really list from the depths of my head at the moment. It would feel more of a headache if I listed them all, but yeah. All-in-all, I hereby support this. --DarkMatterMan4500 (talk) (contribs) 00:59, 29 March 2022 (UTC)
3. Support silly me, obviously as nominator. --Raidarr (talk) 12:54, 29 March 2022 (UTC)
4. Support Trusted user Silicona (talk) 15:21, 29 March 2022 (UTC)
5. Support Thanks for your help! AlPaD (talk) 13:56, 30 March 2022 (UTC)
6. Support A trusted user. It seems that he also understands miraheze policy.--1108-Kiju/talk 16:48, 31 March 2022 (UTC)
7. Weak support while I believe they are trusted and understand global polcies, I'd also have to agree with some of the opposes below that it may be a bit early for this. Nonetheless I still give my support (albeit semi-weakly) here.
   —［ Universal Omega ］［ Talk | Contributions | Guestbook  07:07, 5 April 2022 (UTC) ］ |

Oppose

1. Oppose – Looking at their CA, I don't see any x-wiki counter vandaliam work and would expect some before going to RfGR. Startus (talk) 03:49, 30 March 2022 (UTC)
2. Weak oppose Even if I think it is absolutely a welcome change that the candidate has not nominated themselves as was the case for the administrator requests since that was a very repetitive process I would unfortunately still not feel comfortable supporting this request at this time. I would like to first thank Arcversin for their detailed and reasoned responses to all the questions being asked which prove that the knowledge of Miraheze policies is certainly not the issue here. The main issue which is why I do not feel comfortable supporting is the fact that even if Arcversin seems to be qualified in theory for this role my perception is that he does not have enough experience in practice and is not active enough in discussions on Meta. I unfortunately was not able to access #miraheze-cvt IRC logs in order to check whether Arcversin has been active there because of to an error ("No logs found, try a different filter") but if he has not been then my argument stands. If he has been active on IRC by way of reporting vandalism, etc. I would doubtlessly reconsider my vote to a support as due to my belief the main aspect that is missing for Arcversin is that interaction which I believe is chiefly important for Global Sysops whose main role is to rapidly respond to reports and resolve them. Finally I would like to point out that I understand that it is hard for Global Sysop candidates to understand what is needed from them in order to become Global Sysop but it is also important for there to be a bar set somewhere otherwise anyone who appears to know Miraheze policies and has been on Miraheze for a few months could qualify for Global Sysop. For me that bar should be good knowledge of Miraheze policies, activity and interactions with users and the current Global Sysop and Stewards team. I would consider supporting such a request in the future if this step is taken or alternatively if I am mistaken and the user has indeed been active on IRC or Discord in terms of Global Sysop reporting. --DeeM28 (talk) 06:19, 30 March 2022 (UTC)

   I am active in reporting vandalism in #miraheze-cvt, and I monitor the IRC channels (including the both -cvt and the varioys feeds) consistently while online, so I would be available and ready to rapidly action reports. — Arcversin (talk) 12:23, 30 March 2022 (UTC)

   I confirm as well he is reasonably active and helpful in IRC CVT, as well as present on the irc/discord channels in general, and I find his communication (at least with me as a Steward) to be quite satisfactory. Direct reporting is infrequent, but often times it's not necessarily the reporting that is the key in my experience, and he tends to be useful in followup advisory. The technical background that is limited in CVT ranks helps as well. Not unlike John, I consider his strength to be in his measured approach and knowledge more than 'quantity'. --Raidarr (talk) 14:04, 30 March 2022 (UTC)

3. Oppose, sadly. I have spent the past few days thinking about this, consulting others on the topic, and reviewing everything pertinent to this topic and I cannot support you just yet. I think it is great that Raidarr is going around recruiting people to Global Sysop but I cannot support this nomination. While it is great that you have a good understanding on the Global Sysops policy page, I think you still need more experience for this role. Unlike Raidarr when he made his RfGS, you do not have the commitment, community engagement, or edits I would look for in a potential candidate. It's great that Raidarr is vouching for your communication with him (as expected with him being your nominator) but I haven't really seen you around much on #miraheze-cvt doing much reporting apart from, say, a potential Username Policy violation or two once every week or two. You say that you've engaged with the community on Discord/IRC but as a Discord/IRC regular who is on those two platforms every single day answering questions, I have not seen you around too much. Your activity has risen a bit but only in this past month. Your activity mainly consists of just wiki creations, nothing more. You cite your English Wikipedia contributions but most of them are concentrated in a cluster of a day or two/three of tool usage before disappearing once more for months. I would like to see more commitment from your part for the bit before thinking about requesting it. We already have one Global Sysop who pops up once every blue moon, we do not need another one who artificially inflates the count without actually doing anything. I would also like to see some more long-term community engagement, on-wiki or Discord/IRC and more cross-wiki vandalism work. How can the community support somehow who might disappear randomly and who they're not too acquainted with? I believe it is too early for you to be running for the bit and ask you to consider and address these outstanding points, all of which are absolutely crucial to being a Global Sysop. With all this being said, Arcversin, do not think this is criticism of you. I am simply stating that I feel that it is way too early to be requesting the bit. I encourage you to continue your contributions to Miraheze, especially in non-wiki creation fields, before thinking of requesting advanced permissions. Make no mistake, your contributions are very valued and I encourage you to continue on Miraheze and remain undaunted. Agent Isai ^{Talk to me!} 04:35, 3 April 2022 (UTC)
4. Oppose I agree with Agent Isai. I think it is NOT ELIGIBLE FOR GLOBAL SYSOP YET! --小美粉粉 (Talk) (Contribs) (Sandbox) (My Wiki) (Global Contribs) 1004065811 bytes of data NOTE: Do not {{ping}} me! 06:10, 5 April 2022 (UTC)
5. OpposeI just think its still early --Cocopuff2018 (talk) 14:04, 5 April 2022 (UTC)
6. Oppose I have put more thought into it, and has decided, as per the above, and my careful consideration, have decided that it is a not quite yet case. I do not change my above points about the candidate, but I believe that he should wait a bit more after this request (a month or so). -- Cheers, Bukkit ^{( Talk • All Contribs )} 00:56, 7 April 2022 (UTC)

---

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section