Requests for Stewardship

Requests for Stewardship Welcome! This page is a designed to be a place to organize all requests for Stewardship. Notes: New requests should be created via the button below to preload recommended fields Keep in mind that, following the policy, all requests for Stewardships must be commented on by at least 20 unique users and obtain a support ratio of at least 80% There is a fixed time requirement for requests to stay open, 7 days minimum, and 20+ users should be given time to discuss any potential issues, as well as the candidate addressing any concerns raised Important note regarding nominations by third parties: No voting is to occur until after the candidate has indicated their acceptance by adding their signature, provided any additional nomination acceptance statement, and answered any prepared or presubmitted questions. Remember to update Meta:RecentChanges/Requests with the link to your request. To add your request, click the "Add request" button below.

Archives of Requests for Stewardship [e]
Archive 1 – until 26 May 2019 Archive 2 – until 30 July 2021 Archive 3 – until 17 March 2023 Archive 4 – current

Tali64³'s Nomination for Stewardship

User: Tali64³ (contributions • CA • blocks log • rights log • global rights log)

Reasoning for request

only have one steward need a new steward. he is kind and active. Nominator (talk) 01:57, 3 September 2023 (UTC)

Additional comments given by user (if any)

1.  Comment: If I were being nominated for any other role, this is where I would give my acceptance for being nominated; however, my legal status as a minor (I am 15 at the time of writing this) means that it's unclear if any NDA I sign would be legally enforceable and thus allow me to be a Steward (an NDA is required for the role to be given). In any case, I thank the nominator for nominating me for Steward even if I'm not allowed to be one due to the aforementioned issue. Tali64³ (talk | contributions) 02:27, 3 September 2023 (UTC)

So I am not versed in UK law, but I do know in US law which is what the new organization would be subject to, people under the age of 18 cannot enter into a legally binding contract including NDAs. Therefore I’m not sure if this would be possible at this time. Zppix (Meta | talk to me) 03:02, 6 September 2023 (UTC)

Hmm...instead of requiring an NDA to be a Steward, why not a voluntary agreement similar to the currently-existing NDA that comes with an immediate removal of permissions if violated but that isn't legally binding so as to not be considered a legal contract? I think that could remove the de facto age requirement to be a Steward (if it exists since laws on this are vague). Tali64³ (talk | contributions) 11:15, 6 September 2023 (UTC)

Not really an option because without an NDA it severely decrease legal protections on both sides. Zppix (Meta | talk to me) 18:07, 6 September 2023 (UTC)

Comments by other users

1. I think this nomination should be administratively closed. If the steward position requires an NDA for legal protections (of both the platform and the member), but Tali64³ is a minor, making an NDA not legally binding, then qualifications to be a steward cannot be met. Kudos to Tali64³ for being up front on this from the very beginning. Much as I think he'd make a great steward, there's no point to discussing that until he turns 18. Jph2 (talk) 12:59, 7 September 2023 (UTC)

 Comment: US legal code is complicated. In this case, Tali64³, with the consent of a parent or legal guardian, can sign a binding NDA. Otherwise, the NDA is subject to disaffirmance. Justarandomamerican (talk) 16:32, 8 September 2023 (UTC)

Support

1.  Support on the off chance this is valid. Pppery (talk) 15:38, 3 September 2023 (UTC)
2.  Support Trusted user, he can help on Miraheze. Miraheze needs new stewards. AlPaD (talk) 19:55, 3 September 2023 (UTC)
3.  Strongest support Although I'm not on Miraheze Meta as much as I would like to, I believe that ever since Miraheze started falling apart (and before that) Tali64 should become a Seward. I have never had anything negative with him (not including my WC election, I wasn't ready yet; although I might do another election soon) and he is one of the very few people who have been here to save Miraheze in it's days of darkness. I think that he has worked his butt off and then some for Miraheze to survive. My full support. Commetian Empire (talk) 12:14, 7 September 2023 (UTC)
4.  Strong support In this pre-NDA phase, I don't see any reason to oppose or be neutral. My (admittedly few) interactions with Tali have been pleasant, and he would be good at judging community consensus. Justarandomamerican (talk) 16:36, 8 September 2023 (UTC)
5.  Strongest support I think that Tali would make a great steward. Contributor 118,784 (talk) 12:55, 11 October 2023 (UTC)

Abstain

1. I respect Tali64, but given the NDA issue, I will not be able to support this request until we get some form of confirmation that an NDA can actually be enforced. --Blad (t • c • g) 02:03, 5 September 2023 (UTC)

   I will also note something I just realized: Board/NDAs states that "you will be required to provide your address and full legal name to the Board Secretary in order to sign." This is actually impossible currently; the position of board secretary is currently vacant, as the last person to fill it (Owen) resigned the position quite a while ago. The only two solutions to this problem I can think of are 1) either Void or Owen (most likely Void as Owen has made it clear that he won't be involved in Miraheze for much longer) act as a board secretary temporarily to allow me to go through the process of receiving and signing an NDA if I am allowed to, or 2) the new organization takes control over Miraheze before this nomination for Stewardship is closed, either filling the role of board secretary or abolishing it entirely, possibly allowing me to receive/sign an NDA that way. The issue of whether any NDA I sign would be legally enforceable due to me being a minor still applies, thus adding another issue that needs to be resolved before I can realistically become a Steward. Tali64³ (talk | contributions) 22:14, 5 September 2023 (UTC)

2. Per above. Redmin Contributions CentralAuth (talk) 15:54, 20 September 2023 (UTC)

Oppose

1.  Oppose, he already has two other request open, and I feel its too early. --Cocopuff2018 (talk) 15:55, 3 September 2023 (UTC)

   I recognize that I already have requests for GS and GIWA open, which is why I wouldn't have run for Steward at this time had another user not nominated me; the fact that Miraheze is only running on one Steward, however, compels me to go ahead with the nomination even if my legal status as a minor (explained above) means that the necessary NDA required is unenforceable (thus disbarring me from becoming a Steward until I turn 18). Tali64³ (talk | contributions) 16:19, 3 September 2023 (UTC)

2.  Oppose As I have also argued in the past even if there is a severe lack of volunteers I do not believe that the correct solution is to support any person who wishes to run and sacrifice quality for quantity. I am of course not trying to suggest anything in relation to this candidate but it appears that the support votes are being made in that sense. Besides that the fact that the reasoning for the request is not even presented as a full sentence and the person being nominated has not provided any acceptance of the nomination or reasoning for why they wish to become Steward and what they wish to do makes me wholly unable to support this request. --DeeM28 (talk) 06:50, 11 September 2023 (UTC)

   The reason why I haven't provided any acceptance of my nomination or my reasoning why I should be a Steward is because of the NDA issue (I am a minor, so it's legally unclear whether I can sign one; one user has stated that I can't sign an NDA, but another stated that I can, with the consent of a parent/guardian). Tali64³ (talk | contributions) 11:00, 11 September 2023 (UTC)

1108-Kiju's Nomination for Stewardship

User: 1108-Kiju (contributions • CA • blocks log • rights log • global rights log)

Reasoning for request

he has kind respon to requests on the Stewards'_noticeboard. i think he will help with the work that has been stalled. Nominator (talk) 02:00, 3 September 2023 (UTC)

Accept nomination: Thank you for the nomination. I accept the nomination. Currently, there is only one steward and SN has many unresolved requests. I have only been a Global sysop for 2 months, but I think my experience would be helpful to the community.

My experience:

• I have participated in outreach activities and dealing with vandalism on Japanese wikis since April 2022 and became a global sysop in June 2023. Also, I'm rollbacker in Japanese wikipedia.
• I am a CheckUser and suppressor on a non-Miraheze wiki and understand the situations where the tool should be used. I have also read and understand Suppression#Usage and CheckUser#Use_of_the_tool very well. Also, I have been a bureaucrat for nearly a year on several Miraheze wikis and knows how to use ManageWiki.
• See Requests_for_global_permissions/Archive_4#Reason(s)_for_request_10 and Requests_for_global_permissions/Archive_5#Reason(s)_for_request for more information on our experience dealing with vandalism.

My downside is that I don't participate much in Discord. This is because 1) my time zone is UTC+9, and few users ask for real-time help during the hours I am active, and 2) my English typing speed is too slow to respond quickly. Naturally, this does not interfere with the communication in SN and CN.

I will do everything I can for the platform. Thank you for reading, --1108-Kiju/Talk 09:59, 4 September 2023 (UTC)

Support

1.  Support Pppery (talk) 15:38, 3 September 2023 (UTC)
2.  Support Trusted user, he can help on Miraheze. Miraheze needs new stewards. AlPaD (talk) 19:55, 3 September 2023 (UTC)
3.  Support 1108-Kiju is a bureaucrat on several wikis and currently a global sysop. I think that demonstrates the ability to further help Miraheze as a steward. Jph2 (talk) 13:01, 4 September 2023 (UTC)
4.  Support Kiju has demonstrated proficiency in the global toolset and good activity, two of the most important qualities of a Steward. Tali64³ (talk | contributions) 16:30, 4 September 2023 (UTC)
5.  Support --Cocopuff2018 (talk) 16:36, 4 September 2023 (UTC)
6.  Support Commetian Empire (talk) 14:03, 7 September 2023 (UTC)
7.  Strong support Trusted GS. Redmin Contributions CentralAuth (talk) 15:52, 20 September 2023 (UTC)
8.  Support a need for further functionaries exists, and 1108-Kiju has demonstrated competence and good judgement in my interactions w/ them. While there may be concerns about their English language proficiency, all interactions demonstrated sufficient speed and aptitude to make this a non-issue in my view. --NotAracham (talk • contribs • global) 16:31, 20 September 2023 (UTC)
9.  Support I love policies and guidelines and English language proficiency is not by any chance one of the criteria for Stewardship nomination/appointment. This user has demonstrated that they're capable of handling community discussions. So, why not? ----  Joseph  TB  CT  CA  07:33, 21 September 2023 (UTC)
10.  Support Strong support 1108-Kiju has been making a lot of contributions for miraheze. and he/she take measures for vandal.so,I can believe this user.--Yakkyou (talk) 10:05, 22 September 2023 (UTC)
11.  Strong support 1108-Kiju is a dedicated and talented steward who would be an asset to the Miraheze community.--春雨 (talk) 11:05, 27 November 2023 (UTC)

Abstain

1.  Abstain as Kiju has not yet accepted the nomination. If they do accept it later, however, I will change this to a support as they've demonstrated good use of global tools. Tali64³ (talk | contributions) 16:24, 3 September 2023 (UTC) Moved to support as Kiju has accepted the nomination. Tali64³ (talk | contributions) 16:30, 4 September 2023 (UTC)
2.  Abstain Per my comments in relation to Tali64³ in the request above. Even though the "reasoning for request" is better here I still cannot find myself able to support a "necessity candidate" in such an important position. --DeeM28 (talk) 06:51, 11 September 2023 (UTC)

Legroom's Request for Stewardship

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

Nomination refused, don't nominate people randomly. Legroom (talk) 12:15, 22 September 2023 (UTC)

---

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

Reasoning for request

He supports many users on Discord. Be a steward. Nominator (talk) 10:11, 22 September 2023 (UTC)

Additional comments given by user (if any)

• Declining this nomination, I can't run for this position for number of reasons. Legroom (talk) 12:15, 22 September 2023 (UTC)

Abstain

•  Neutral Childish behaviour carried over from Discord, I would suggest moving on from the nominations as to not waste anyones time. Possibly increase the protection level of the page. PlatinumYellow (talk) 11:18, 22 September 2023 (UTC)

Oppose

---

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

RhinosF1's Request for Stewardship

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

Nomination refused with prejudice. Please do not reopen or nominate me again without serious discussion. ~ RhinosF1 - _(chat)^{· acc· c} - (on) 11:02, 22 September 2023 (UTC)

---

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

Reasoning for request

According to Legroom, he is a sys admin and knows a lot. I think he could be useful as a steward. Nominator (talk) 10:11, 22 September 2023 (UTC)

Additional comments given by user (if any)

• This nomination is declined. ~ RhinosF1 - _(chat)^{· acc· c} - (on) 11:02, 22 September 2023 (UTC)

Oppose

---

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

ElizatronicWarfare's Request for Stewardship

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

Reasoning for request

He gave me calm advice in Disocord. Be a steward. Nominator (talk) 10:11, 22 September 2023 (UTC)

Comments by other users

• As I write this on 4 December, Elizatronic has not yet accepted the nomination. Accepting the nomination is a prerequisite for the vote to succeed. I don't plan to vote until they do. – Jph2 (talk) 19:35, 4 December 2023 (UTC)

Abstain

•  Neutral Childish behaviour carried over from Discord, I would suggest moving on from the nominations as to not waste anyones time. Possibly increase the protection level of the page. PlatinumYellow (talk) 11:18, 22 September 2023 (UTC)

Oppose

•  Oppose Miraheze desperately needs more stewards, but someone with 87 edits to one Miraheze wiki and none elsewhere is nowhere near enough experience. Pppery (talk) 02:00, 23 September 2023 (UTC)

  Check PlatinumYellow's comment, this user, Nominator, had some attics in Discord over stewardship topic and proceed to spam this page. I think we can safely close this one too and move these entries to archive. Legroom (talk) 05:01, 24 September 2023 (UTC)

1.  Strongest oppose Per above and the abstain. Commetian Empire (talk)

Zppix's Request for Stewardship

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

Nomination refused. Please stop nominating random users, it is disruptive to the community, thanks. Zppix (Meta | talk to me)

---

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

Reasoning for request

He is a moderator on Discord. Very good. Nominator (talk) 10:11, 22 September 2023 (UTC)

Abstain

•  Neutral Childish behaviour carried over from Discord, I would suggest moving on from the nominations as to not waste anyones time. Possibly increase the protection level of the page. PlatinumYellow (talk) 11:17, 22 September 2023 (UTC)

Oppose

---

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

Original Authority's Request for Stewardship

User: Original Authority (contributions • CA • Authority blocks log • rights log • global rights log)

Reasoning for request

I believe at this moment, the current landscape with Miraheze's volunteers is in a sticky situation. There are currently only two Stewards (one of which is no longer a main part of the Platform anymore) and as such, I am requesting Stewardship to alleviate some of the burden on the current team who are dealing with infrastructure etc. I will also make it public for those not aware that I have filed a SRE Access Request also, but I suspect that this will not be actioned for a while due to the move to the US etc.

I am most frequently seen around Discord, providing assistance with user questions, but I am also quite active on Phabricator. Whilst I do not have many edits on Meta in general, this is because the majority of stuff is requests for renames, etc., which cannot really be actioned without elevated rights. Butof course, I will withdraw this request if # of Meta edits is a true blocker for Stewardship. I obviously have a lot of experience with MediaWiki and both ManageWiki/CreateWiki, so there is no question that I have the required expertise and knowledge for the role. If I were to be granted Stewardship, I would assist with some of the main glaring tasks on Phabricator/SN, such as wiki (un)deletions etc. This would probably go a long way of relieving some of the stress from the other volunteers and perhaps reassuring the community that Miraheze is not going anyway in the near future.

Feel free to ask any questions, or oppose if you feel that way inclined :)

Comments by other users

1. I won't lodge a vote as a largely-retired user on this platform, but I would raise three three key items for consideration:

• Original Authority runs a competing wiki platform (telepedia) that, while narrower in scope, has made no secret of its plans to expand. Even without such plans, this is enough of a conflict of interest to raise concerns.
• There is also a grand total of 20 edits globally for this user. While the majority of their interactions have been on Discord, this still gives a vanishingly small body of work to understand their temperament and likely behavior as Steward if elected.
• During the potential window of an MH shutdown, they were eager to purchase up the Orain domain for use on their wiki project due to the lingering SEO benefits. (see Discord, June 15, general chat here) While I wouldn't consider this disqualifying, it would put them closer to having decision-making capacity (or at least greater input) on whether to retain that domain under Miraheze.

I don't doubt their intentions, a successful Miraheze is better for everyone, but these are concerns I feel are valid to raise for an accurate community accounting before reaching a decision. --NotAracham (talk • contribs • global) 19:56, 23 November 2023 (UTC)

In regards to your specific comments:

1. Fair play for your comment re: Telepedia, but I largely think that this isn't really a valid point you raise. Firstly, there are several volunteers with global rights and elevated access that run "competing" services as you put it, and still have the rights. Secondly, if my intentions were truly to "compete" with Miraheze, then I wouldn't spend as long in Discord as I do assisting users and delving into technical issues, opening PR's to Miraheze's GitHub etc. I think this comment is well intentioned but sadly and observably is not true. I would also like to just add that Telepedia runs on the same CW/MW extension as Miraheze and without the continous delevelopment that goes into those two extensions by MH SRE then Telepedia would potentially be screwed, so it generally just doesn't make sense for me to be out-to-get Miraheze.
2. As noted in the original request, I am aware of my small number of edits, and I stated that if edit count requires a mandatory milestone, I will withdraw the request. As I also mentioned, I spend the majority of time helping out in Discord and on Phabricator, which should be factored into the decision.
3. This comment is unbased; what does that have to do with anything? If Miraheze shut down, the domain would no longer have been in use and post-expiration would have become available to the public anyway. Further, I'd argue that control of such domain would be purview of the Board and thus my involvement as a steward would have no impact on that decision. Furthermore, it seems you have mis-interpreted the conversation. I did not state anywhere in aforementioned Discord conversation that I would use the Orain domain for anything to do with MediaWiki—that is a conclusion you have arrived at on your own.

Thanks for your response :) --Original Authority (talk) 20:07, 23 November 2023 (UTC)

Thanks for taking time out of your day to respond. I personally don't agree with the retention of those global rights by those who have left for other platforms, but this is largely an artifact of the offer made to remain on-board in a limited capacity to help with wind-down of services (when that was the original plan) and should not be taken as proof of permissibility.

I appreciate that we have differing opinions on this matter, but still maintain that holding advanced permissions w/ global reach while operating a competitor is not a thing that should be done, as a best practice. It's precisely why I divested myself of those same rights once successors were available. --NotAracham (talk • contribs • global) 20:31, 23 November 2023 (UTC)

Support

1.  Strongest support Let me start the ball rolling. I can attest to Original Authority's helpfulness and technical expertise and familiarity with the MediaWiki software. In looking at the Stewards page, I don't see where the number of Meta edits comes into play. Even if it did, I would support making an exception since Meta edits don't really relate to the skills needed for a steward. I suspect where there's a stipulation on Meta edits the intent is for the community to be able to know the candidate. I think Original Authority's other efforts to help the community already speak to that. Now we just need 19 more members to weigh in. – Jph2 (talk) 20:01, 23 November 2023 (UTC)
2.  Strong support I see can that Original Authority has been making an effort to be quite helpful, and I believe that the amount of edits on Meta doesn't really matter here, and that it matters more of the intent given to the tasks and a clear level of understanding human activity, which I can see quite clearly. I do understand about the concern surrounding the short list of edits, but I see that as minor compared to the possibility of abuse, which I don't see for this candidate. I've been wrong before, but I don't want to abstain or oppose just because of that. I have a good feeling about this. TwoRats (talk) 23:24, 2 December 2023 (UTC)
3.  Strong support I see Original Authority on Discord often, helping frequently. I think this amount of experience and technical knowledge is just what we need to help the existing technical volunteers.
   Xena (talk)
   15:23, 4 December 2023 (UTC)

Abstain

1.  Neutral while NotAracham raises some valid points, I do not believe its enough for me to oppose this request, however, while I do appreciate the help that OriginalAuthority has been giving, I would like to see a bit more interaction with the global community overall on-wiki before I can confidently support the request, but I also don’t want my vote to discourage them from trying other areas out first. I am very picky when it comes to RfS because I would like to avoid the mistakes that have been made in the past of putting people in very advanced global groups too soon. So at this point in time I am going to remain neutral and abstain from voting in support, or in opposition of this request. Zppix (Meta | talk to me) 14:26, 25 November 2023 (UTC)