Page MenuHomeMiraheze

[ACCESS REQUEST] Universal Omega for MediaWiki Engineering
Closed, ResolvedPublic

Description

This is my second access request to return to MediaWiki Engineering. First was T6438

I previously resigned due to personal circumstances and lack of PC/Shell access. I expected to be gone longer but here I am, I am back with PC access now.

SSH public key (regenerated): https://meta.miraheze.org/wiki/User:Universal_Omega/SSH_Public_Key

Thank you!

Event Timeline

Universal_Omega created this task.

I had a few non-technical questions before commenting further:

  1. Regarding activity, do you plan on being active and having access for the foreseeable future?
  2. Are there any areas or things that you plan to specifically focus on?
  3. How will you prioritise the various tasks that you'll have as a MW Engineer - resolving Phabricator tasks (feature rquests, bugs), extension maintenance, reviewing PRs, etc?
  4. Since there have previously been some issues regarding your communication with the Infra team, what do you plan on doing to resolve this and make communication effective? What about communication with the MW team itself?

Regarding activity, do you plan on being active and having access for the foreseeable future?

Yes, I do.

Are there any areas or things that you plan to specifically focus on?

I plan to work on whatever needs it. Phabricator tasks will come first in order to cut down on wait time for users there, and once there isn't much more I can do in tasks I'll work on extension work I've had planned for awhile. (Such as T6699 and T7125)

How will you prioritise the various tasks that you'll have as a MW Engineer - resolving Phabricator tasks (feature rquests, bugs), extension maintenance, reviewing PRs, etc?

  • Phabricator tasks - bugs
  • PR review
  • Phabricator tasks - feature requests (depending on what is requested this may be higher in priority) / extension maintenance (again depending on the type of maintenance, bugs for example would be a higher priority)

Since there have previously been some issues regarding your communication with the Infra team, what do you plan on doing to resolve this and make communication effective? What about communication with the MW team itself?

Well for starters that is something I acknowledge I could've done better with in the past. I definitely plan to have a more effective communication with the infrastructure team, as well as other members of the MediaWiki team. I know communication was never my strong area and something that I definitely intend to work on and communicate effectively.

Regarding activity, do you plan on being active and having access for the foreseeable future?

Yes, I do.

Are there any areas or things that you plan to specifically focus on?

I plan to work on whatever needs it. Phabricator tasks will come first in order to cut down on wait time for users there, and once there isn't much more I can do in tasks I'll work on extension work I've had planned for awhile. (Such as T6699 and T7125)

How will you prioritise the various tasks that you'll have as a MW Engineer - resolving Phabricator tasks (feature rquests, bugs), extension maintenance, reviewing PRs, etc?

  • Phabricator tasks - bugs
  • PR review
  • Phabricator tasks - feature requests (depending on what is requested this may be higher in priority) / extension maintenance (again depending on the type of maintenance, bugs for example would be a higher priority)

Since there have previously been some issues regarding your communication with the Infra team, what do you plan on doing to resolve this and make communication effective? What about communication with the MW team itself?

Well for starters that is something I acknowledge I could've done better with in the past. I definitely plan to have a more effective communication with the infrastructure team, as well as other members of the MediaWiki team. I know communication was never my strong area and something that I definitely intend to work on and communicate effectively.

Sounds good. Regarding developer work, do you plan on discussing major changes to extensions/workflow with the MW team and the EM? And also generally making sure that that communication (also related to prioritisation of tasks) is clear and effective?

Sounds good. Regarding developer work, do you plan on discussing major changes to extensions/workflow with the MW team and the EM? And also generally making sure that that communication (also related to prioritisation of tasks) is clear and effective?

Yes, definitely. I don't plan on making any major changes to extensions without prior discussion.

I know i don't have a say in this but

Omega is a great guy I would definitely support him for system admin again, he has done soo much work at miraheze.

As long as you keep working on your personal development I can support this request. Your help is valuable to Miraheze.

Sounds good. Regarding developer work, do you plan on discussing major changes to extensions/workflow with the MW team and the EM? And also generally making sure that that communication (also related to prioritisation of tasks) is clear and effective?

Yes, definitely. I don't plan on making any major changes to extensions without prior discussion.

@Universal_Omega What about minor changes? Would you also discuss those with relevant parties first (i.e., an Engineering Manager, SRE (Infrastructure), MWE, or, where it impacts others' workflow, non-SRE teams (i.e., Stewards, Trust and Safety, etc.)?

Sounds good. Regarding developer work, do you plan on discussing major changes to extensions/workflow with the MW team and the EM? And also generally making sure that that communication (also related to prioritisation of tasks) is clear and effective?

Yes, definitely. I don't plan on making any major changes to extensions without prior discussion.

@Universal_Omega What about minor changes? Would you also discuss those with relevant parties first (i.e., an Engineering Manager, SRE (Infrastructure), MWE, or, where it impacts others' workflow, non-SRE teams (i.e., Stewards, Trust and Safety, etc.)?

I guess I could've worded that better. I meant major changes or user-facing changes. Basically excluded important bug fixes that doesn't have user-facing changes or very minor changes that are important. Even then I'd be careful what I did without discussion, and only when necessary.

Sounds good. Regarding developer work, do you plan on discussing major changes to extensions/workflow with the MW team and the EM? And also generally making sure that that communication (also related to prioritisation of tasks) is clear and effective?

Yes, definitely. I don't plan on making any major changes to extensions without prior discussion.

@Universal_Omega What about minor changes? Would you also discuss those with relevant parties first (i.e., an Engineering Manager, SRE (Infrastructure), MWE, or, where it impacts others' workflow, non-SRE teams (i.e., Stewards, Trust and Safety, etc.)?

I guess I could've worded that better. I meant major changes or user-facing changes. Basically excluded important bug fixes that doesn't have user-facing changes or very minor changes that are important. Even then I'd be careful what I did without discussion, and only when necessary.

Okay, yeah, bug fixes or security problems shouldn't need a discussion (well, security problems should actually have a private discussion with SRE regarding the security issue, but you know what I mean). Basically, what I mean is making minor changes to extension UI, extension features, or other functionality, without first discussing with at least some of the relevant stakeholders and at least one other SRE team member or EM. But yeah, if that's you meant, then that sounds good to me. :)

Sounds good to me. Per the new appointment policy and given the fact that @Southparkfan is currently acting as EM (I), I'll need to discuss this with him for the 'official' approval (Note to SPF: Feel free to ping me on IRC to discuss).

Discussed with SPF and this has been approved.

Reception123 claimed this task.