Page MenuHomeMiraheze

[ACCESS REQUEST] New access for Original Authority
Closed, ResolvedPublic

Description

Shell name: luke
SSH Key (if new access): ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAILD0e5CCa8BhhAmKvIHPjhN6+dMU0uQ1Z/ZHcfmqoUVP original.authority0@gmail.com

Requested access: SRE

Rationale for access: I've been pretty active on Miraheze for the majority of 2023, albeit having been around on the platform since 2022. I'm often most active in Discord and Phabricator, and have opened quite a few PRs on GitHub. I'd now like to help with maintaining Miraheze and ensuring there is enough volunteers to keep up with the workload and the increasing number of tasks on Phabricator.

That's all, ask questions, or roast me I guess :) Also not entirely sure what you're meant to put in the "requested access" section so if someone wants to update the task with that or discuss that, then feel free!

  • shell
  • icinga
  • ldap
  • on wiki rights
  • staffwiki
  • GitHub
  • phab projects/badges

Event Timeline

What position are you applying for? Site Reliability Engineer? MediaWiki Engineer? Software Engineer?

Just confirming what position you mean as SRE can mean the group and the role and in this case, the role is what you're applying for.

Apologies, that's my bad — reading my reply back, it does sound passive aggressive from my side but I did not intend it to come across that way :)

Original_Authority renamed this task from [ACCESS REQUEST] New/Expanded access for Original Authority to [ACCESS REQUEST] New access for Original Authority.Nov 3 2023, 23:35

Unfortunately an NDA is required for SRE access, and to my knowledge, we aren't currently in a position to process new ones at the moment.

Unfortunately an NDA is required for SRE access, and to my knowledge, we aren't currently in a position to process new ones at the moment.

Pretty sure Void can issue NDA's, but he can confirm this, I guess.

Putting this back into consideration.

If you want an NDA following this request being approved, please email me.

Hi. A few questions:

  1. What do you plan on doing if you gain access? (i.e. resolving regular tasks, developer work, etc.) Are there any specific larger tasks that you plan on doing?
  2. Do you expect to be active in the near future?
  3. How would you manage interpersonal relationships and dynamics among SRE members to ensure a positive environment?
  4. What previous experience do you have?

Hi. A few questions:

  1. What do you plan on doing if you gain access? (i.e. resolving regular tasks, developer work, etc.) Are there any specific larger tasks that you plan on doing?
  2. Do you expect to be active in the near future?
  3. How would you manage interpersonal relationships and dynamics among SRE members to ensure a positive environment?
  4. What previous experience do you have?

Firstly, welcome back! It's nice to see you 'home' again.

  • Resolving regular tasks, definitely. I don't have any overbearing ideas on development work at the moment, but I'm pretty familiar with CW and MW and would like to improve them as time goes on and ideas spring about what users want out of the two extensions; or developing new extensions that could be useful.
  • Yes.
  • I'm not entirely sure what you're asking here; I'm pretty approachable and friendly with most of the SRE members already; although I doubt they would, if tensions were to arise I would take a step back and approach the situation rationally—at the end of the day ensuring the Platform is running well and the users are happy is above personal grudges etc. (Not that I have any).
  • I'm pretty familiar with MediaWiki development, developing extensions, etc., and have gotten pretty good at understanding how puppet and other infrastructure tools MH uses over the last couple of months. I've made several PRs and commits to MH's GitHub as evidence.

Since NDA is now signed, and per our conversations, this is now approved for mw-admins, and ssl-admins. I will begin on-boarding shortly.

Please don't hesitate to ask your colleagues if you have any questions or are unsure about something. A second opinion for things can never hurt.

Universal_Omega updated the task description. (Show Details)