Requests for global permissions

MrJaroslavik (Revocation - Inactivity)

 * The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.
 * Revocation successful. Reception123 (talk) ( C ) 04:36, 25 May 2023 (UTC)

User: MrJaroslavik ( contributions &bull; CA &bull; blocks log &bull; rights log &bull; global rights log )

Reason(s) for request
As is customary when I begin a request of this nature I would like to start by thanking MrJaroslavik for his service as Global Sysop over the years and by saying that this request is not 'personal' but merely a request from a "functionalist" perspective. As I have before mentioned it is my belief that in order to be Global Sysop a person must be active and available to action requests regularly. This does not exclude the possibility that there is simply no request to action as activity outside of the use of the tools is relevant to the consideration. In October 2022 MrJaroslavik asked for a confirmation vote which ended up passing even though the own standards that were set were not met. It can be seen that the votes that supported MrJaroslavik were not enthusiastic and it must be said that at that time it could be argued that he was somewhat semi-active. I am opening this request because since then circumstances have changed.

Just by looking at MrJaroslavik's edits to Meta in the year 2023 there are only 7. There are some log entries related to some maintenance in March 2023 and a few CVT actions in February and March 2023. Since March 2023 MrJaroslavik has largely disappeared from Meta except for one insight.

Reviewing all this I conclude that the activity is insufficient for the role of Global Sysop and that the rights are no longer needed or used. I once again thank MrJaroslavik for his service but I believe that he is no longer interested or no longer has time to fulfill it. As a final reminder the Miraheze Spaces Code of Conduct states: "If something occurs in your life and you can no longer find time to devote to your roles, find a way to step down gracefully. If you don't, other people on your team may always await your opinion and stall things waiting for your very delayed review or response. Some users may become discouraged from seeking advanced roles which they would be a perfect fit for because they think the role is adequately staffed when in reality, it needs more active users.". I have debated whether to attempt to ask MrJaroslavik via his userpage if he considered resigning for these reasons but given the fact that he did not after the confirmation vote I think it was a fair assumption that he did not wish to do so.

Since there was confusion in a past vote: Support means that you support the revocation (you no longer want MrJaroslavik to be Global Sysop). Oppose mean that you oppose the revocation (you want MrJaroslavik to continue to be Global Sysop). --DeeM28 (talk) 17:12, 17 May 2023 (UTC)

Additional comments given by user (if any)
Hello all, reply to all users: Yes, I failed, I am aware of it, there are few reasons why my activity is low - watching of feeds is time consuming, there are reports in #cvt channel, but most of time they are created and processed when i sleep or it are requests for stewards - but that doesn't change the fact that my GS activity is really really low and it's my personal failure. Reason why I didn't is same as before - it looks like alibism and you don't have to believe me that it's not HAT collecting or some kind of show-off - but just because what if something happened and no one else was online, but again, it's my failure. As you may have noticed, I do not agree with direction and changes in the community, it's also reason for my inactivity. I will keep Meta Administrator permission until I complete tasks that i want to do or until i decide if i will continue here.--MrJaroslavik (talk) 10:00, 22 May 2023 (UTC)


 * While the process is by no means complete, it is evident that this request has a strong, unlikely to fail basis for support. It's a shame that the direction of the platform is not to your liking, I'd be happy to discuss in public or private however it may help but it is your prerogative to carry on if you feel it won't really change regardless. Do you wish to resign the GS bit on account of the factors you've explained, or would you wish to see the process continue to its procedural conclusion? --Raidarr (talk) 13:06, 22 May 2023 (UTC)
 * It is surprising to me that you admit to us that you "failed" and that you are inactive but yet do not propose to resign. I would remark that activity is an implicit requirements for all roles and as such I take the admission that you are inactive as an implicit admission that you are no longer able to fulfill the role. I once again thank you for your work but if you do not agree with the direction of Miraheze and no longer wish to continue would it not be easier to resign permissions rather than wait for the community to hold a vote? I do not believe it is very pleasant to hold revocation votes and also not the most effective use of the time of community members. As for administrator I am troubled by the fact that you say you complete tasks "that you want to do" since an administrator should not be doing tasks that they "want" when they want but instead should perform tasks that are relevant and important to the community and be active in that role. I also do not believe it is fair for the community to have to wait until you decide whether to continue as I would contend that you have had many months to do so. I sincerely hope that my observations do not seem unfairly harsh but I strongly believe in the idea that that when users are inactive or no longer motivated it is best for them to give up their hats and potentially regain them in the future if they are later able to participate again. I also believe that the community would be more wiling in the future to vote for someone who resigned voluntarily rather than someone who had to be revoked by a vote. DeeM28 (talk) 14:49, 22 May 2023 (UTC)
 * I personally don't have very high standards in terms of activity requirements of volunteers. For me, trustworthiness, competence (both technical and procedural), and a spirit of collaboration and collegiality to work with both other volunteers, community leaders (i.e., Stewards), and the community at large matter most. To be clear, I think you are both trustworthy and technically and procedurally competent. I can certainly forgive the low activity (my own activity has been intermittent recently), or if someone is completely absent, but if someone is active on other platforms and semi-actively watching the CVT feeds but then not actioning anything, it does give me a bit of pause than, say, someone who is only able to be active on certain days of the week. It's fine to disagree with the current direction of the community, with Miraheze, or in the formulation of policy; I certainly have not agreed with everything, just as I'm sure Agent Isai, for example, doesn't agree with every one of my ideas, but saying you disagree with the direction of the community and that that is a reason for one's low activity/motivation and then that you wish to stay on as a Meta administrator until you've finished with self-identified tasks seem to be at cross-purposes with each other. I tend to agree with DeeM28 here in that is puzzling to say the least. Dmehus (talk) 16:37, 22 May 2023 (UTC)

Support

 * 1)  Per the reasons I give above in my statement. --DeeM28 (talk) 17:14, 17 May 2023 (UTC)
 * , regrettably. Since his last self-imposed vote of confidence, I was hoping that he would improve in his activity but that is not the case. He is rarely seen, even in his capacity as Meta sysop, when there is plenty to do not only in the CVT field but also in the community. We all had hoped that he would improve his activity but it appears that is not the case and he is rarely active or seen which is of concern. If this is successful, I would hope that he also gracefully resigns as Meta sysop as this inactivity extends to that role too. Agent Isai  Talk to me! 20:30, 17 May 2023 (UTC)
 * 1)  per the above. MrJaroslavik is a valued member of the community but unfortunately, is not active enough to justify the occupation of global sysop. One day in the future, if he becomes active again, I would be happy to see a re-request. BrandonWM (talk • contributions • global • rights) 02:27, 18 May 2023 (UTC)
 * I hope he will be active and we will nominate again (or he will run himself) who knows :D Hey Türkiye  Message? 12:18, 19 May 2023 (UTC)
 * 1)  --Cocopuff2018 (talk) 13:45, 18 May 2023 (UTC)
 * 2)  per @NotAracham, Dmehus Although I regret the retirement of the users, it is obvious that he has done good works for Miraheze behind him. I wish you success in your real life, which will take place from now on, and wish you good luck.  Hey Türkiye  Message? 12:16, 19 May 2023 (UTC)
 * 3)  --Imamy (talk) 15:45, 19 May 2023 (UTC)
 * 4)  per the arguments articulated by the DeeM28, in bringing forth this discussion, as well as what others have said. As Reception123 subtly hinted in his close that MrJaroslavik was free to voluntarily resign as a Global Sysop given the lukewarm reception to his self-requested reconfirmation request. Since then, his activity has, admittedly, not met his own standards. In addition, I would also add that has demonstrated a persistent pattern of conduct in being willing to work with me collaboratively and constructively, when I served as a Steward and an administrator on Meta Wiki. I believe the source of this conflict stems from August 2020 when I responded to Universal Omega's good-intentioned request to delete some duplicate voting templates MrJaroslavik had imported and which were duplicative of the existing voting templates, which had various parameters built into them. As was a Meta Wiki convention, I had discussed it with Universal Omega, Reception123, and perhaps a couple other users, in a public channel, all of whom agreed with the deletion. MrJaroslavik took issue with that and, since then, has essentially copy-pasted self-plagiarized his own community noticeboard discussion regarding his personal annoyances with me, which the community rejected, into a Stewardship revocation request, which the community rejected, into a Meta administrator revocation request, which the community again soundly rejected, and then into a second Stewardship revocation request. The point of demonstrating this is to demonstrate that his support for community consensus is highly conditional—predicated on the condition that it generally fits within MrJaroslavik's personal views. Taken together, not only has MrJaroslavik not adhered to the letter if not the spirit of the Miraheze Spaces Code of Conduct but also the Volunteer Conduct Policy, in which volunteers are to be held to a higher standard in terms of working collaboratively and constructively with colleagues and the community writ large. Dmehus (talk) 03:05, 20 May 2023 (UTC)
 * 5)  By their own criteria laid out in their own request for confirmation, they should have stepped down.  By the terms of the MsCoC, they should have stepped down.  I do appreciate their contributions over the years to the Miraheze project, but even nominal engagement with the community beyond a blip of activity every one or two months would have dissuaded my support. This has not happened, and given their lack of overall activity, I cannot in good faith conclude that they can continue to be effective in the Global Sysop role and must give my support to revocation. --NotAracham (talk • contribs • global) 03:11, 20 May 2023 (UTC)
 * 6)  Unfortunately after having giving this much thought over the last couple days, I have come to the decision to support this request for the reasons articulated above, and failing to meet their own standards set out in their own confirmation. Universal Omega (talk) 08:46, 20 May 2023 (UTC)
 * 7)  This isn't something that should be discussed. Our precious time is being wasted. --   Joseph  TB  CT  CA   05:18, 23 May 2023 (UTC)

Oppose

 * . Lets say, for example, this user logs in in a week and finds their Global sysop rights removed. Do you think not having these rights will encourage them to be more active? No, it will discourage them into actively editing ever again. If we want our users to become active again, removing their rights involontarly is not the answer. Globe - (Talk • Contributions • CA) 16:29, 19 May 2023 (UTC) Per Dmehus. Globe - (Talk • Contributions • CA) 03:21, 20 May 2023 (UTC)
 * I Exactly what you said, but each user will also have a final contribution. We will have a job in the future, we will go with other jobs and we will never be active again. Our aim here is not 'No, this is not active, let's take his power and not encourage him to contribute', but 'It is our natural right, myself included, to want to pave the way for the formation of new global operating systems and a bit of new staff. But if we look at it from this Aside; it is really sad that one of us is gone. I can't say anything to him, but everything has an end of course.  Hey Türkiye  Message? 20:35, 19 May 2023 (UTC)
 * But he may be upset if he sees that his authority has been taken unannounced. This is officially unannounced. Based on this, I'm voting for . Hey Türkiye  Message? 20:38, 19 May 2023 (UTC)
 * As you may remember, a few months ago (early 2023?), MrJaroslavik himself submitted a vote of confidence against himself for his inactivity. It failed because of the awkward formatting + the general hopes that after that, he'd improve his activity. He hasn't improved at all (see his contributions) despite the majority saying that his inactivity is worrying and if this fails then I'm worried that the community has fostered a protection for inactive users and is enabling them to stay on indefinitely even if they're chronically inactive. Since I became Steward, I have rarely seen MrJaroslavik in action apart from an occasional lock every few months (I haven't seen him action anything recently). I don't wish him any bad and I have strongly desired to see him active and collaborating with CVT and Stewards but if he is so chronically inactive and nothing has changed since his vote of no confidence a few months ago then I believe it would be graceful to step down if he cannot devote any time to the project. If he doesn't realize a vote is going on right now because of his inactivity then that's quite worrying. Agent Isai  Talk to me! 21:00, 19 May 2023 (UTC)
 * per Globe. It is very disrespectful to take the authorization of this user without any knowledge of it, it will not benefit Miraheze to take the authorization of a 4 year old user just because he is 'inactive' without knowing. If not informed, I will change my strongest opposition to weak opposition. Hey Türkiye  Message? 20:42, 19 May 2023 (UTC)
 * It also does not benefit Miraheze to have an chronically inactive user on rank and file either. Agent Isai  Talk to me! 21:00, 19 May 2023 (UTC)
 * @Agent Isai It does not, it is true, but it is not right to authorise a bidet without its knowledge. Instead of encouraging the user to contribute, you are abusing them. Please do not do this, I ask you. In addition; If the user is not active, he/she can resign from his/her position. Why are you acting in the style of 'he is not active, let me take his authorisation'? I think the measure of activity should be measured by him, not us. I think we should wait until he makes a statement. Hey Türkiye  Message? 21:04, 19 May 2023 (UTC)
 * But it does benefit Miraheze if the user helps out when they are actually available. Removing rights prevents that. Globe - (Talk • Contributions • CA) 00:20, 20 May 2023 (UTC)
 * I have left a nudge discord-side to make him aware of this request directly, someone would be free to take the liberty of notifying him via talk page additionally (I'm surprised that wasn't done initially tbh). As far as the measure of activity, the measure is made when active users see that a user is present or is not - if the person isn't here then they're obviously not in a great position to be making that call in the first place. This is not a circumstance requiring auto-removal for being completely absent in a policy-defined length of time but I must agree that MrJaroslavik's participation has been very low for a long time, further so in recent months, especially subsequent to when he made a bid for WC/a self-initiated ratification vote that has been described above already. It is clearly written in the Code of Conduct: "If something occurs in your life and you can no longer find time to devote to your roles, find a way to step down gracefully. If you don't, other people on your team may always await your opinion and stall things waiting for your very delayed review or response. Some users may become discouraged from seeking advanced roles which they would be a perfect fit for because they think the role is adequately staffed when in reality, it needs more active users. By stepping down, you help encourage more users to take up advanced roles which they may be suitable for." That may or may not be applicable in full here but it is evident that we have multiple functionaries, this case for Global Sysop but the case can be made in several places including meta adminship and operational roles on satellite wikis to Meta, who should reconsider their hats on this basis. --Raidarr (talk) 23:59, 19 May 2023 (UTC)
 * --- I don't know if contacting MrJaroslavik will make a difference. Generally when one disappears, that person really is MISSING and WON'T OPEN MESSAGES.  The reason for this vote is to make it possible to open up a spot for someone who can be an active Global Sysop.  By refusing to revoke when the position is held by a dormant user, in time that may also start a trend of roles filled by a growing population of dormant users.  To create additional positions to offset the dormant positions is not a solution, because over time, the staff collective will just tune out the clutter of dormant roles. ---Imamy (talk) 04:19, 20 May 2023 (UTC)
 * Pinging here as relevant, I have notified MrJaroslavik via his talk page about this request. I do not know if he will see it, or if he will see 's Discord message, but we've done what should be done to notify him. BrandonWM (talk • contributions • global • rights) 04:58, 20 May 2023 (UTC)
 * MrJaroslavik has been online on discord and has at least participated in discussion within the past few months with a long history of showing up 'eventually', and he has also participated recently on Wikimedia 'across the fence' on some wikis. I cannot promise he will respond in a timely manner but I do believe he is not absolutely absent. --Raidarr (talk) 11:57, 20 May 2023 (UTC)


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

HeyTürkiye's Request for Global Sysop

 * The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.
 * Closing per UCP, I will open the next application when someone nominates me, there is no consensus about me yet. I think voting is not important, the important thing is whether that user can do this task, I think it is important. Thanks to everyone who voted. I'm acting on policy, this is not a withdrawal statement. -- Hey Türkiye Message? 18:49, 27 May 2023 (UTC)

User: HeyTürkiye ( contributions &bull; CA &bull; blocks log &bull; rights log &bull; global rights log )

Reason(s) for request
I would like to submit my candidacy by referring to the past Global sysop nomination. I am well versed in the policies on the English Wikipedia, Behavior policy and participate in the RfCs and am mostly active on Discord. I think there is a need for a new Global Sysop as MrJaroslavik has also left us. I would be very grateful if you would definitely let me know your suggestions and comments, Your comments and opinions are very important to me. I wish the result to be beneficial for Miraheze. -- Hey Türkiye Message? 12:20, 27 May 2023 (UTC)

Additional comments given by user (if any)
CV Details:
 * Member of Miraheze since September 2021
 * More than 14,000 Global Regulations (CA)
 * Active participation and comments on Discord and RfC
 * 2000+ edits on Meta Wiki

Oppose

 * 1)  The rationale for my original opposition in January and the following February 2023 request mostly still stands, though I will note your tendency for mistranslations to lead to unnecessary hostility and comprehensibility have both somewhat improved... However, your heavy reliance on translation tools for communication outside of your native Turkish, combined with frequent misunderstanding of English-language communications and translated replies that often confuse your intent, lead me to the conclusion that this remains a role in which you would not thrive at this time. I look forward to the day when I can support your nomination. --NotAracham (talk • contribs • global) 14:52, 27 May 2023 (UTC)
 * How will it cause confusion @NotAracham, I'm waiting for a detailed explanation. Every 3 months, a person needs to change their mind. Hey Türkiye  Message? 16:00, 27 May 2023 (UTC)
 * 1)  Per NotAracham, essentially. There are still standing issues which give me concerns about how you would function in this role. One day, perhaps, you can run for global sysop, but I don't believe that today is that day. BrandonWM (talk • contributions • global • rights) 15:43, 27 May 2023 (UTC)
 * "Unfortunately I have to argue with the same logic as NotAracham. While your answers to my questions are mostly satisfactory, I think it's a little early for Global Sysop. You've only made about 350 edits to the Meta as well, so that number jumps to at least 750 before I request it again. That said, I have to say I like what I've seen regarding your helpfulness in community issues, and if your work there continues, I'd probably be more than happy to support a future request. NotAracham said above, you're definitely heading in the right direction, you just need to go a little further. Thank you" I would like to remind you of the sentence you said to me, BrandonWM. I would appreciate it if you didn't take it as a person who didn't fulfill your promises. Hey Türkiye  Message? 16:05, 27 May 2023 (UTC)
 * I haven't "promised" anything. I definitely didn't promise you a future support vote as soon as you crossed an edit count number. I said I would be more inclined to support it. But I'm still not where I need to be in regards to my comfort level with trusting you with such a senior position and the responsibility that comes with it. And frankly, I would appreciate it if you didn't accuse me of not fulfilling promises when in fact I never made any. An argument could even be made that that comment violates the canvassing policy, attempting to intimidate me into voting support? And telling NotAracham that he needs to change his mind? These are the conduct issues (and now canvassing) that I do not wish to see in a global sysop. Sorry, this is now a strong/strongest oppose for me. BrandonWM (talk • contributions • global • rights) 16:12, 27 May 2023 (UTC)
 * -_- huh @BrandonWM, I just wanted to say that I have honored your wish for me. I've already put a comment mark because it's completely unrelated to the topic. Hey Türkiye  Message? 16:15, 27 May 2023 (UTC)
 * sorry for the misunderstanding. Hey Türkiye  Message? 16:16, 27 May 2023 (UTC)
 * Very well, my apologies on that front, you weren't clear. That also relates to NotAracham's concerns, where intent has been conveyed grossly incorrectly, obviously not a good thing. I'm still confused though, about your response to NotAracham above? "Every 3 months, a person needs to change their mind." If that's not canvassing, I don't know what is, it seems to be a clear request to change his vote. BrandonWM (talk • contributions • global • rights) 16:18, 27 May 2023 (UTC)
 * I fully respect my vote for NotAracham and I didn't say 'change your vote'. I mentioned that people change regardless of their opinions, i.e. when your opinions change. My aim is not to change votes. Hey Türkiye  Message? 16:22, 27 May 2023 (UTC)
 * If you, for example, don't change your mind at all, you can ask a detailed question like 'what is the point of view of your opinion', you have the right. But my aim was definitely not to change my vote, my aim was to ask a question. Hey Türkiye  Message? 16:25, 27 May 2023 (UTC)
 * I would add that I'm still so confused with regards to what you mean. I have removed my strong oppose and mentions of canvassing, with apologies to you, but I'm still confused. I believe you were acting in good faith when you wrote those messages, which is why I have retracted my statements, but to be quite honest, your message previously didn't make much sense. I'll remove the canvassing part of this, but the intent concern has been demonstrated in this thread alone. It's not necessarily your fault, but rather the language discrepancy. BrandonWM (talk • contributions • global • rights) 16:28, 27 May 2023 (UTC)
 * Apart from that, BrandonWM, if you have questions about CVT and sample scenarios, I will be happy to answer. As I mentioned above, the questions you ask are very important to me. -- Hey Türkiye Message? 16:32, 27 May 2023 (UTC)
 * 1) Cocopuff2018 (talk) 18:20, 27 May 2023 (UTC)


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

Tali64³'s Nomination for Global Sysop

 * The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.
 * The support ratio required for Global Sysop is not met and therefore this request is unsuccessful. Reception123 (talk) ( C ) 17:34, 15 June 2023 (UTC)

User: Tali64³‎ ( contributions &bull; CA &bull; blocks log &bull; rights log &bull; global rights log )

Reason(s) for request
Hi there. I'm excited to nominate Tali64³‎ to be your next Global Sysop at Miraheze. Tali64³‎ has served immensely well as a wiki creator for the past few months, taking care of sometimes 30-40 requests per day. If you're a new-ish user to Miraheze, and you've put in a wiki request recently, chances are it was responded to by Tali64³‎. They've shown competency and skill in responding to requests, and would be an amazing asset in CVT to assist in counter-vandalism activities. We currently have 3 members of CVT, two of which are Stewards (those two are SRE as well), so CVT would be well aided with another few volunteers. As such, I would like to nominate Tali64³‎ to be the next Global Sysop on Miraheze. BrandonWM (talk • contributions • global • rights) 15:22, 7 June 2023 (UTC)

Statement given by nominated user
Thank you so much for the nomination. When I joined Miraheze on September 24, 2019, I wanted to migrate my humor wiki to a better platform; at the time, it was hosted on the legacy version of Google Sites (I still miss the Project wiki theme), but the main drawback was that no one else could contribute to it, which became possible on Miraheze. I had never expected to be nominated for Global Sysop or even be a wiki creator; however, in December 2022, I noticed a large of amount of wiki requests in the queue, so I nominated myself for wiki creator. An SRE member then clarified that requests were on hold due to a hosting provider error causing database issues, but I chose not to withdraw my request for wiki creator. The community wasn't really familiar with me, so I received few supports and lots of abstains, which was what led to my request for wiki creator failing. However, I reapplied a couple of months later with a different goal: to help handle wiki requests as fast as possible; in the meantime, the community had become more familiar with me, and I got weak supports instead of abstains, successfully becoming a wiki creator. Since then, I've handled anywhere from 95% to 99% of all wiki requests that have come in. I have also had some experience fighting spam and vandalism, from Wikipedia to ShoutWiki, with a few reverts in between on Miraheze. If I am elected as Global Sysop, I will make sure that vandalism reports are handled as fast as possible, just like I currently handle wiki requests as fast as possible. I've helped new wikis begin on Miraheze; now I want to help existing wikis continue free of issues. Tali64³ (talk) 15:38, 7 June 2023 (UTC)

Comments by other users
BrandonWM (talk • contributions • global • rights) 15:30, 7 June 2023 (UTC)
 * The requirements for Global Sysop are the following:
 * Have at least 1000 total global edits on Miraheze (on more than one wiki, unless that wiki is Meta Wiki) (Note: These edits may not consist of directly copy/pasting content from other wikis, they must be edits done by the user); ✅
 * Have had their Miraheze account for at least 2 months; ✅
 * Be involved in some way in community matters (in discussions on Community noticeboard, etc.); ✅

Support

 * 1) As proposer. BrandonWM (talk • contributions • global • rights) 15:32, 7 June 2023 (UTC)
 * 2) In wake of recent events we need additional members in the various community-related roles. I believe that this user is one of the only users who would even qualify to serve in this role, and I trust them to use their best judgement surrounding learning curves and avoid rushing into things if they are unsure. –  AmandaCath  ( talk ) 17:41, 7 June 2023 (UTC)
 * 3) I think and feel this user should get chance. Additionally, i looked at their English Wikipedia edits and there is about 75 vandalism rollbacks (undo tag) from about 700 edits. And there are no recent warnings or anything related to patrolling on their user talk.--MrJaroslavik (talk) 18:02, 7 June 2023 (UTC)
 * Note that sounds like experience potentially more suitable for Global Rollbacker, if I'm being honest. It also doesn't demonstrate any active use of that tool, on Miraheze. Miraheze's Global Sysop role is unique to that of Wikimedia, in that it also includes global IP blocking and user account lock/unlocks, tools customarily used by Stewards on the Wikimedia wikis. This requires both a higher level of competence, demonstrated policy knowledge and capability, technical capability, and, as Agent Isai noted, judgment skills. As well, Global Sysops, through a recent RfC, are active on all public wikis and opt-out is no longer possible (never what the RfC intended; rather, there was some confusion by participants, as I understand it, who thought Global Sysops might not be able to enforce global policies on opted out wikis). Dmehus (talk) 18:10, 7 June 2023 (UTC)
 * 1) To me, Tali64³ demonstrated sound judgment and rapid actions, I see no reason for Tali64³ not to be Global Sysop.--Nobody679 (talk) 06:47, 8 June 2023 (UTC)
 * 2) If they want to do it, why not? Many opposes are mentioning global rollback, but I think that's just a dead-end role, because, compared to GS, they have much less advanced permissions. GR membership isn't going to make anyone's concerns about the advanced permissions GS holds go away. I also see no concerns regarding judgement. They have WC, so they're already trusted as a MH user's first contact with us. OrangeStar (talk) 11:23, 8 June 2023 (UTC)
 * 3) Per above. AlPaD (talk) 19:42, 8 June 2023 (UTC)
 * 4) When I saw that Tali64 was running for GS, I thought for sure there would be all supports and no opposers. I was wrong. This is honestly very sad. Tali64 handles at least 90% of all wiki requests and honestly, Miraheze wouldn’t function with them. They clearly have a very clear understanding of our global policies and have dedicated a lot of time to improving the wiki. AND we have a huge need for more GS/stewards to help fulfill requests. I wouldn’t be surprised if Tali64 sees this opposition to their request and is very discouraged and retires from Miraheze altogether for the same reason BrandonWM did. The community not supporting their most active and frankly most trusted WC is baffling to me. Why do they need to have experience in global tools? They are active and use tools well on other wikis. The only way to gain experience with global tools is to actually have them. I am very disappointed in the Miraheze community for this. Come on people. Globe - (Talk • Contributions • CA) 14:50, 9 June 2023 (UTC)
 * To be honest, I don't know much about CVT. However, I don't think that CVT is the only area that needs volunteers.  CVT is the most developed area.  Just because a position doesn't yet exist and the activity happens to not involve any specialized tools, doesn't mean a need doesn't currently exist.
 * I oppose this proposal because the GS position has already been defined with an established structure and protocol that I don't know much about. At this time, I prefer not to redefine any established positions from what they were originally created and developed for.
 * I think that Tali64 has incredible leadership qualities. Enough so that I'm willing to risk introducing new unknowns that come without checks and balances into our current system.  I put in a request in the Community Noticeboard to post a request to invite more community participation on current open requests.  I considered all the statements made by Supporters and came to realize that we are not all on the same page and the gap is too wide.  If the Community elects Tali64, I will adapt and go with that new perception of what GS position will stand for.
 * With that said, I would still much prefer to see undefined vacancies get developed.
 * --- Imamy (talk) 16:06, 9 June 2023 (UTC)
 * I am not sure if you responded to the relight comment. I said nothing about “ redefine any established positions from what they were originally created and developed for.” Globe - (Talk • Contributions • CA) 16:35, 9 June 2023 (UTC)
 * Hi Globe
 * I was responding to your statement. I felt our requests/proposals were heading down a path where there was only one way to look at issues and I really wanted more diverse opinions and got overzealous in sharing mine.
 * My perception is my own and you made a very good point that volunteers could leave, so when I shared, I went and shared badly. "redefine any established ..." was the thought that popped in my head and I know what I mean when I say it, but ... clearly the message lacked context.  I'm sorry for any aggravation that may have caused. Imamy (talk) 04:48, 10 June 2023 (UTC)
 * 1) Shifting vote to weak(est) support.  I stand by the logic of my original oppose, but recent departures have shifted my thinking that add'l volunteers will be necessary sooner. --NotAracham (talk • contribs • global) 20:38, 9 June 2023 (UTC)
 * 2) I change my vote, agreeing a bit with NotAracham, because most of the CVT staff are involved in SRE. But a lot of the text in my dissenting vote is still valid, but it is not a task that everyone can do in GS. Tali you say you can do it, but dealing with vandalism is not easy. I would like to say this as someone who has experienced it for almost 3 years. But since you have full confidence in GS and you say I can take on this task, let's watch. But you should also try GR if this application is fruitless. But by GS, so it would be beneficial for Tali and Miraheze to change my vote from opposition to support. Good luck with your candidacy. -- Hey Türkiye  Message? 21:08, 9 June 2023 (UTC)
 * 3)  There is a clear necessity for additional help in community roles right now and I feel that Tali64³ has shown that they are capable already with their Wiki Creator hat. Redmin Contributions CentralAuth (talk) 11:46, 10 June 2023 (UTC)
 * 4) Tali64 has the competence needed for GS. GR and GS are not the same, not similar, and frankly, doesn't really count as experience in my opinion. I have no oppositions toward the request, and fully  it. --  Bukkit  [ cetacean needed ] 19:09, 10 June 2023 (UTC)
 * 5)  Miraheze's future is yours!
 * 6)  Tali64³ has clearly demonstrated an interest in Miraheze and a willingness to devote time to the project overall. At a time when depth in volunteers seems rather critical for Miraheze, absent anything disqualifying, I don't see why we wouldn't let Tali64³ invest his talents helping wikis beyond just creating them. Jph2 (talk) 15:31, 12 June 2023 (UTC)
 * 7)  Because there is a new nominee for Global Sysop.  Since I may confuse people about the reason, the most I can do is point to a point that was made a while back in a different RfC regarding my feelings toward teams.  "promote several active members simultaneously" --- Imamy (talk) 06:57, 13 June 2023 (UTC)

Abstain

 * 1)  I have decided to exceptionally abstain in this case. The main reason behind this is that I observe that there are many well respected users who have decided to oppose this request and have concerns about the requestors judgment but sadly those claims have not been substantiated enough for me to be able to join them. At the same time I believe that such a large number of concerns must indicate that something is not right and consequently I do not believe that I would be able to support in good conscience either. --DeeM28 (talk) 12:44, 11 June 2023 (UTC)

Oppose

 * 1)  Tali64 hasn't demonstrated the ability to use global tools just yet. I additionally share the concern about judgement at times which can be impaired and potentially problematic as he sometimes overreacts on things and acts rather bluntly. At most, I would advise trialing as Global rollbacker but Global Sysop is a no-go from me.  Agent Isai  Talk to me! 15:26, 7 June 2023 (UTC)
 * I admit that I have had no experience with global tools. However, I believe that I make up for it with my experience using admin tools on the many wikis I own; global tools are just an extension of those. I also believe that I have pretty good judgement; for example, I have processed thousands of wiki requests in the four months I've been a wiki creator, and the other wiki creators (including you) have only expressed concern for a very small fraction of those (less than 10). There have also been few incidents in which I have overreacted to something. One of those was the time I attempted to move one of my wikis to independent hosting due to a report made by an anonymous user who had been vandalizing that wiki; I admit that it was partially my fault for not stating that the user had been vandalizing, but I eventually decided to cancel the move. The other was actually a few messages in the Miraheze Discord server I had sent earlier this morning when I thought that I'd lost access to my account after enabling 2FA, which is reasonable. Generally, I try to be as kind and level-headed as best as I can. Tali64³ (talk) 15:59, 7 June 2023 (UTC)
 * 1)  exactly what Agent Isai said. Tali64 is generally collaborative, well-liked, helpful, and courteous, but my concerns are around judgment for this role. For global interwiki administrator, I could happily support. Dmehus (talk) 15:34, 7 June 2023 (UTC)
 * 2)  I would like to see Tali64³‎ serve as global interwiki administrator before taking on global sysop.   Clearly, Tali64³ is very task driven.  However, since all the global positions interact with each other, it would be good to get a feel for the issues that administrators address, especially in terms of conflict resolution involving communities. ---Imamy (talk) 17:16, 7 June 2023 (UTC)       Because there are 2 candidates for GS. --- Imamy (talk) 06:51, 13 June 2023 (UTC)
 * I would note that GIWA isn't really an administrative role, rather a role for adding interwiki links. It doesn't persay deal with issues that administrators address, including conflict resolution. You wouldn't be able to gain a sense of conflict resolution skills from interwiki administrator. Hope that clarifies. BrandonWM (talk • contributions • global • rights) 19:02, 7 June 2023 (UTC)
 * @BrandonWM: To clarify, I don't get the sense that Tali64 is comfortable with discussions. I would find it easier to come to you about a problem because you are more willing to be specific about my concerns.  Feeling-wise, that will move my issue towards resolution much more quickly regardless of whether I get my wish or not. Imamy (talk) 20:56, 7 June 2023 (UTC)
 * 1)  too early --Cocopuff2018 (talk) 19:12, 7 June 2023 (UTC)
 * 2)  for the same reasons as already stated by others.  While Tali is prolific in their role as WC with minimal errors and gives me no doubt that they would work as diligently if appointed to Global Sysop, their handling of and line of reasoning on ambiguous cases does not give me full confidence at this time.  I would wholeheartedly support a run for Global Rollbacker for them to gain deeper familiarity with CVT nuances, though. --NotAracham (talk • contribs • global) 22:17, 7 June 2023 (UTC) EDIT: Striking opposition. --NotAracham (talk • contribs • global) 20:34, 9 June 2023 (UTC)
 * 3)  I can't support this for the reasons outlined above by Agent, Dmehus, and NotAracham. Universal Omega (talk) 06:50, 8 June 2023 (UTC)
 * Striking as now a nonexistent user on Miraheze. BrandonWM (talk • contributions • global • rights) 03:43, 11 June 2023 (UTC)
 * I have reverted this good-faith edit, as we don't do that. The !vote was cast by a duly qualified !voter as at the timestamp of their !vote. Dmehus (talk) 03:55, 11 June 2023 (UTC)
 * The only policy that discusses how votes by people without accounts should be counted is the RfCP and it instructs Stewards against counting them. The !voter's qualification when the vote was not cast should not matter if they are no longer a member of the community when a Steward determines consensus. That said, I agree with not striking this particular comment due to the unique circumstances. Redmin Contributions CentralAuth (talk) 15:04, 11 June 2023 (UTC)
 * 1)  Per the rationale of other. Maybe if a little soon for now to take the GS but as we have now the Global Rollbacks, it may be a good start for you. HeartsDo (Talk / Global) 09:12, 8 June 2023 (UTC)
 * 2) per Agent and Universal Omega. Zppix (Meta &#124; talk to me) 15:13, 8 June 2023 (UTC)
 * 3)  I've been seeing @Tali64 very active on Miraheze lately, and I congratulate Tali64 for his prompt response to wiki requests, his instant replies to my comments on Discord, and his participation in important community forums such as Miraheze's RfC. However, the Global Sysop role, as @NotAracham has said many times in my applications, is a role aimed at combating vandalism, and it is not something that many budding users can handle. The Global Sysop has a lot of duties (like dealing with CVT, visiting wikis, knowing the policy on Wikipedia and applying it). Apart from that, I have an important note for you: I suggest you to be more active in the community, to stand out. Right now your edit count is around 800-900. I think you should reach at least 1500 edits here. Apart from that, I suggest you try the Global Rollbacker group in the next applications. Then I will give you my support. But as soon as you feel that you have fulfilled the need to become a Global sysop (when I see that you have fulfilled it), I will give you the strongest support in your next application. Let me put this as a note. Apart from that, I agree with NotAracham and Agent Isai, but this process will take some time. (It's like being active in the community, every user has these moments) I wish you Good luck until your next application Tali. -- Hey Türkiye  Message? 05:23, 9 June 2023 (UTC) NOTE: I changed my vote. -- Hey Türkiye  Message? 21:06, 9 June 2023 (UTC)
 * Edit count is not very important when determining suitability to a role; instead, activity is one of the key factors in determining such suitability, and I have clearly met and perhaps even exceeded any activity expectations. I know the duties of Global Sysops and believe I am ready to help with the workload; to prepare for this, I have started monitoring the CVT feed to combat any vandalism I see. Several users have suggested that I apply for global rollbacker instead, but that role wouldn't help me much with helping the current CVT team handle their workload, which is one of my main reasons for applying for GS. Tali64³ (talk) 15:35, 9 June 2023 (UTC)
 * 1) per above. by Buehl106·Talk·e-mail 12:43, 9 June 2023 (UTC)


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

1108-Kiju's Nomination for Global Sysop
User: 1108-Kiju ( contributions &bull; CA &bull; blocks log &bull; rights log &bull; global rights log )

Reason(s) for request
I am opting to nominate for the role of Global Sysop. In my time at Miraheze they have been a constant presence in CVT activities, regularly providing clear and detailed reports of vandals from our non-English-language wikis. In my interactions with them they were timely, courteous and willing to oblige on providing native context I would otherwise lack without cultural fluency. Should they accept this nomination, I would be glad to see them take on this mantle as an evolution of their current help to the platform. --NotAracham (talk • contribs • global)

Statement given by nominated user
I accept the nomination and am running for candidate. Thank you NotAracham for nominate.
 * Currently, there appear to be only two stewards and one Global Sysop. I hope that by becoming a Global Sysop I can help in some small way to deal with the vandalism.
 * The Japanese community is relatively large, and vandalism is common. However, Japanese is a complex language and it is often difficult to distinguish between well-intentioned edits and vandalism, so vandalism response is often late. Also, I have been a Global Rolebacker since March 2023 and when I discovered vandalism, I could only rv and report it to #CVT and wait for the steward or Global Sysop to respond.
 * I often monitor #global-wiki-feed, so if there is vandalism on a Japanese wiki or reported to #cvt, I can address it quickly.

Please feel free to ask me any questions. Thank you for reading. --1108-Kiju /Talk 04:48, 13 June 2023 (UTC)
 * Since becoming a member of CVT, I have learned more about how CVT works. I have the knowledge and experience needed for Global Syop.
 * My time zone is UTC+9. I can cover UTC+9 time zone.
 * I understand global policy and have been involved in correcting global policy violations on Japanese wiki.
 * My experience
 * Discord - CVT - I have also reported them to CVT on Discord when necessary. Please search for "from: Kiju#5889".
 * Special:CentralAuth/1108-Kiju - Please search for "sysop". I am a sysop on several wikis and have experience dealing with vandalism there. For example: mh:ysmwiki:Special:Contributions/1108-Kiju, mh:wikisitewiki:Special:Contributions/1108-Kiju, mh:another:Special:Contributions/1108-Kiju, mh:chakuriki:Special:Contributions/1108-Kiju. See also Requests_for_global_permissions/Archive_4.
 * mh:chizunet:Special:Contributions/1108-Kiju - I was involved in resolving disputes.

Support

 * 1) as nominator. --NotAracham (talk • contribs • global) 04:54, 13 June 2023 (UTC)
 * 2)  For the reasons listed above. 1108-Kiju has proven to be a highly competent user and given these turbulent times on Miraheze, I believe he is well positioned to help with either a wind down or about-face of the current system on Miraheze. So, for those reasons, I'm happy to support. BrandonWM (talk • contributions • global • rights) 05:01, 13 June 2023 (UTC)
 * 3)  Active and good user.His experience is enough to be gs.Good luck.I welcome to this request as Japanese cvt. by Buehl106·Talk·e-mail 05:07, 13 June 2023 (UTC)
 * 4)  --- Imamy (talk) 07:01, 13 June 2023 (UTC)
 * 5)  As NotAracham said, having Global Sysop would be a hit for Miraheze. Good luck. -- Hey Türkiye  Message? 07:34, 13 June 2023 (UTC)
 * 6)  --Nobody679 (talk) 09:11, 13 June 2023 (UTC)
 * 7)  Language variety in CVT is welcome, especially among global sysops. OrangeStar (talk) 12:07, 13 June 2023 (UTC)
 * 8)  per above. Tali64³ (talk) 12:56, 13 June 2023 (UTC)
 * 9)  A Japanese speaker is clearly needed. Redmin Contributions CentralAuth (talk) 14:15, 13 June 2023 (UTC)
 * 10)  for all the reasons already noted. Jph2 (talk) 16:22, 13 June 2023 (UTC)