Page MenuHomeMiraheze

[ACCESS REQUEST] New access for MacFan4000
Closed, ResolvedPublic

Description

With @Reception123 currently actioning nearly all MediaWiki-related Phabricator requests, due in part to other online and offline priorities of the MediaWiki volunteer team, there is a rather urgent need for an additional MediaWiki Engineer. Having spoken with MacFan4000 on IRC, I'm pleased to be able to nominate @MacFan4000 to the role of MediaWiki Engineer, with the puppet-user additional access reinstated as well so he can again assist with handling custom domain requests. I believe MacFan4000 will be cautious, measured, and only handle requests where he is technically able to and has the knowledge and experience to handle such requests. I have complete confidence he will immediately report any server issues of partial or complete server downtime, and overall will be a net positive to the MediaWiki Engineer team.

I'll let him detail his volunteer availability per week, his requested shell access username, and link his public SSH key.

Access

  • email
  • irc
  • github
  • ldap
  • grafana
  • graylog
  • matomo
  • hund
  • acl*security
  • sysadmin wiki group
  • staffwiki
  • betawiki - already have an account would just need rights assigned
  • twitter
  • facebook
  • google account

Event Timeline

In my further time as a MirahezeBots SRE member, I have better learned things like puppet.

I accept the nomination.

@Reception123 I thought it said which in the task description but its MediaWiki engineer and puppet-users (basically the same two roles I had before)

@MacFan4000 You'd first need to define what role you're applying for. See https://meta.miraheze.org/wiki/Tech:Organisation

Yeah, MediaWiki Engineer, with puppet-user. You likely just missed the nomination rationale and his reply

@Reception123 I thought it said which in the task description but its MediaWiki engineer and puppet-users (basically the same two roles I had before)

Ah sorry, I got confused myself. The new system means that technically 'mw-admins' and 'puppet-users' rights are 'access' while something like MWE is a role. So then I'll assume you're questing mw-admins and puppet-users + the MWE role.

As is usual with these requests, here are some questions before making a decision:

  1. What do you mainly plan on doing if you are to return in the MediaWiki team? Are there any specific tasks that you plan on undertaking?
  2. What would you do if there was a task that you thought you knew how to do but were quite uncertain about? (especially one that involves running a script, making a DB change, etc.)
  3. If you are to return, do you expect to be active? Around how much time do you think you would be able to dedicate to Miraheze, approximately?
  4. Have you had a chance to read the new sysadmin guides / rules created since you were last sysadmin?
Universal_Omega renamed this task from [ACCESS REQUEST] New/Expanded access for MacFan4000 to [ACCESS REQUEST] New access for MacFan4000.Feb 19 2022, 21:30
Universal_Omega updated the task description. (Show Details)
Universal_Omega moved this task from Radar to Access on the Site Reliability Engineering board.
Universal_Omega added a subscriber: John.
Universal_Omega added a subscriber: Universal_Omega.

As is usual with these requests, here are some questions before making a decision:

  1. What do you mainly plan on doing if you are to return in the MediaWiki team? Are there any specific tasks that you plan on undertaking?

Handling configuration/extension/skin/custom domain requests and assisting with upgrades as needed. Nothing specific just general handling of requests and helping to maintain our in-house extensions.

  1. What would you do if there was a task that you thought you knew how to do but were quite uncertain about? (especially one that involves running a script, making a DB change, etc.)

Talk to the other SRE members about it. If they aren’t sure either ask in channels such as MediaWiki.

  1. If you are to return, do you expect to be active? Around how much time do you think you would be able to dedicate to Miraheze, approximately?

At least a few hours a week, I am a bit busy with college at the moment but I should be able to spare a bit of time.

  1. Have you had a chance to read the new sysadmin guides / rules created since you were last sysadmin?

Yes I have now read them.

After talking to @Reception123 I approve of this request provided past mistakes are learned from and not repeated. Another MWE is definitely needed. Especially with myself inactive lately, however I may decide to return fully within the near future as well, as I don't want to abandon responsibilities within MWE, which after some of what was said here being that Reception123 has been doing mostly all tasks, I feel that's kind of unfair, and wasn't my intention when I announced my break. I likely won't restore my full activity on IRC, but I may restore my full system administrator duties. Especially it would make it easier for me should this be approved, because it would mean someone else able to assist with some of what only I have been able to do prior. So I definitely approve with the stipulation of confirmation that past mistakes aren't going to be repeated again and they have been learned from.

Additionally, having another puppet-user would be highly beneficial for Reception123 not to have to handle 99% of those requests, as he has for as long as I've been here. I only say 99% because there has been just a couple handled by others like Paladox, John, and Zppix while they were here. But mainly Reception123 has handled them all.

To @Universal_Omega: I hear you're on leave for the next three months. What's been keeping you busy otherwise lately?

P.S. Keep up the great work when you return! (If you have time, I've already filed several DPL3 bugs upstream, still unaddressed.)

P.P.S. I'm guessing Betaheze left for a while when you did days ago, right?

To @Universal_Omega: I hear you're on leave for the next three months. What's been keeping you busy otherwise lately?

P.S. Keep up the great work when you return! (If you have time, I've already filed several DPL3 bugs upstream, still unaddressed.)

P.P.S. I'm guessing Betaheze left for a while when you did days ago, right?

My leave is indefinite, as I have no set return date. I would likely return fully before 3 months, and considering returning much sooner, but not sure yet. As for betaheze, that is still an active project. As for DPL3, hopefully I can get to them eventually though for easier tracking it would be better to create issues using https://github.com/Universal-Omega/DynamicPageList3/issues/new if possible. But this has gotten a bit off-topic for this task, so for further discussion this you may leave a message on my Miraheze Meta talk page or use Special:EmailUser on-wiki on Miraheze.

After talking to @Reception123 I approve of this request provided past mistakes are learned from and not repeated. Another MWE is definitely needed. Especially with myself inactive lately, however I may decide to return fully within the near future as well, as I don't want to abandon responsibilities within MWE, which after some of what was said here being that Reception123 has been doing mostly all tasks, I feel that's kind of unfair, and wasn't my intention when I announced my break. I likely won't restore my full activity on IRC, but I may restore my full system administrator duties. Especially it would make it easier for me should this be approved, because it would mean someone else able to assist with some of what only I have been able to do prior. So I definitely approve with the stipulation of confirmation that past mistakes aren't going to be repeated again and they have been learned from.

Additionally, having another puppet-user would be highly beneficial for Reception123 not to have to handle 99% of those requests, as he has for as long as I've been here. I only say 99% because there has been just a couple handled by others like Paladox, John, and Zppix while they were here. But mainly Reception123 has handled them all.

Yes I will do my best not to repeat the mistakes.

After discussing with @John we are satisfied that this request can be approved as long as care is taken and past mistakes are avoided. +1

I will just say add that I particularly liked MacFan4000's response to question # 3, where he said, "At least a few hours a week, I am a bit busy with college at the moment but I should be able to spare a bit of time.." That's what I consider an A+ answer to that question. SRE aren't expected to commit massive amounts of time to the project. The key is to set reasonable expectations in terms of one's volunteer commitments. In short, it's better to under promise and modestly over deliver than over promise and under deliver. At the core, SRE are all volunteers, so as long as SRE are able to take on portions of the work and maintain close collaboration, the project will run smoothly.

Reception123 claimed this task.
Reception123 updated the task description. (Show Details)

On-boarding should be complete.