Page MenuHomeMiraheze

[ACCESS REQUEST]: New access for AmandaCath
Closed, InvalidPublic

Description

Per discussion on IRC tonight, I would like to formally apply for the MediaWiki Software Engineer position. I have knowledge of MediaWiki and PHP, as well as some background information on CSS and JS, so I believe I meet all of the requirements listed on the vacancies page. I was formerly an IT consultant, so I also have a technical background. I may need a bit of training/guidance at the beginning, as this is my first attempt to really get heavily involved in the technical side of Miraheze, but I believe that I will be able to clear any learning curves and be able to help address some of Miraheze's shortcomings, especially in wake of the recent string of resignations. If the community/SRE would trust me in this role, I would be honored.

If you need any further information please let me know.

Event Timeline

AmandaCath triaged this task as Normal priority.Jun 7 2023, 01:00
AmandaCath created this task.
BrandonWM renamed this task from Application for MediaWiki Software Engineer to {ACCESS REQUEST}: New access for AmandaCath.Jun 7 2023, 01:24

I would support this request, since we really do need more people on the team, now more than ever. @Reception123 and @Void will need to review this though.

Same support here (though not an SRE). I could post the usual questions as well, but the user has shown proficiency in these tasks previously, and it would seem quite unnecessary given recent events.

Assigning to Reception123 as EM for MediaWiki.

BrandonWM renamed this task from {ACCESS REQUEST}: New access for AmandaCath to [ACCESS REQUEST]: New access for AmandaCath.Jun 7 2023, 03:02

I wish you good luck @AmandaCath. Just a little thing, you'll very likely need to sign an NDA (https://meta.miraheze.org/wiki/Board/NDAs) if you haven't already. Or maybe not, given that you'll likely only have github access as a Software Engineer. I'd email the board just in case.

AmandaCath changed the task status from Open to Stalled.Jun 10 2023, 00:32

As Reception123 is on wiki break (link), I don't think my application can be processed unless someone else is qualified to do it.

Also +1 from me, though I'm not a SRE member.

Given their history (around April-May 2017) I would rather not trust this user at all. (And no, I will not change my mind no matter what you say, so you can skip all your excuses.)

In T10931#220639, @revi wrote:

around April-May 2017

This is just not appropriate.

"Well, back in 1912 this user wrote "fuck miraheze" on their userpage, so I'll never trust them at all and I will always remind them of their past".

As we all know, people are just unchanging objects, and it's perfectly appropriate to always hunt them by reminding them of their past, no matter how much time has passed. After all, no one deserves chances, they all deserve to forever be reminded of their mistakes and never be able to break free from them.

I guarantee whatever Amanda did back then is nowhere near bad enough to still talk about it to this day. What, did they kill a person? I'm sure not.

While we wait, it might be worth looking at some open tasks and seeing if you can begin to make contributions to the git repositories in the form of pull requests? Might make an approval process easier if recent work is demonstrated that can be approved and merged in

In T10931#220639, @revi wrote:

around April-May 2017

This is just not appropriate.

"Well, back in 1912 this user wrote "fuck miraheze" on their userpage, so I'll never trust them at all and I will always remind them of their past".

As we all know, people are just unchanging objects, and it's perfectly appropriate to always hunt them by reminding them of their past, no matter how much time has passed. After all, no one deserves chances, they all deserve to forever be reminded of their mistakes and never be able to break free from them.

I guarantee whatever Amanda did back then is nowhere near bad enough to still talk about it to this day. What, did they kill a person? I'm sure not.

@OrangeStar I believe that Amanda was accused of being a sockpuppet of a globally banned user. Whether that's the case, I can't say, but there seems to have been strong behavioral evidence and/or physical evidence as well. I wasn't around at the time, so I can't make a judgement either way, but I believe that was the accusation.

For the record, the globally banned user in question was my late sister, who unleashed a spambot attack against Miraheze on more than one occasion after being banned. Because we were living together at the time, it was next to impossible to distinguish us from each other in terms of technical data/CheckUser. But I was completely uninvolved and took no part in encouraging her disruptive actions. I'd also appreciate it if this wasn't discussed further at this time.

Unknown Object (User) added a comment.Jun 15 2023, 20:26

Ideally, Amanda should tackle some extension (CreateWiki, ManageWiki, etc.) tasks before being granted any access. I've yet to see them do anything related to coding and I've mostly observed her sorting Phabricator tasks or some basic mw-config changes.

In T10931#221129, @Agent_Isai wrote:

Ideally, Amanda should tackle some extension (CreateWiki, ManageWiki, etc.) tasks before being granted any access. I've yet to see them do anything related to coding and I've mostly observed her sorting Phabricator tasks or some basic mw-config changes.

I had been (well, still am) working on T10844, but with the recent decision to terminate the Miraheze project is it even necessary at this point?

In T10931#221129, @Agent_Isai wrote:

Ideally, Amanda should tackle some extension (CreateWiki, ManageWiki, etc.) tasks before being granted any access. I've yet to see them do anything related to coding and I've mostly observed her sorting Phabricator tasks or some basic mw-config changes.

I had been (well, still am) working on T10844, but with the recent decision to terminate the Miraheze project is it even necessary at this point?

I'd recommend not spending time on tasks at the moment until things are clarified.

https://meta.miraheze.org/wiki/Miraheze_is_Not_Shutting_Down, while not a guarantee of Miraheze's survival just yet, makes it very clear there at least are a lot people interested in Miraheze's survival, and that there's a plan for it to survive. So I'd say now is the time to do some of the tasks here as Agent said, and show us what you got.

Note that an non-disclosure agreement is a required prerequisite before this request can even be evaluated

Note that an non-disclosure agreement is a required prerequisite before this request can even be evaluated

Actually per previous discussions with Owen via Discord, an NDA is not required for the Software Engineer position.

Note that an non-disclosure agreement is a required prerequisite before this request can even be evaluated

Actually per previous discussions with Owen via Discord, an NDA is not required for the Software Engineer position.

Technically, this is true, yes, assuming the Software Engineer is not requesting shell access. This is also true of the MediaWiki Engineer position. However, I do not see much point in this, given the low level of recent GitHub PRs/commits and the fact that any user could do software development for Miraheze without a title.

Note that an non-disclosure agreement is a required prerequisite before this request can even be evaluated

Actually per previous discussions with Owen via Discord, an NDA is not required for the Software Engineer position.

Technically, this is true, yes, assuming the Software Engineer is not requesting shell access. This is also true of the MediaWiki Engineer position. However, I do not see much point in this, given the low level of recent GitHub PRs/commits and the fact that any user could do software development for Miraheze without a title.

It's for access to Github repos I believe without needing to PR something, as well as have access to all extension repos. Others would know more though.

It's for access to Github repos I believe without needing to PR something, as well as have access to all extension repos. Others would know more though.

My understanding from @Reception123 is that can't be done because the current SRE policy is such that in order to have merge access to the GitHub repositories, one needs shell access. Shell access does require an NDA.

I don't think you would need shell access to have merge access to extension repos as those aren't auto-deployed.

Unfortunately I'm going to withdraw this request at this time as my RL is becoming exceptionally busy to the point that I don't feel I would have adequate time to be an effective member of SRE. Should things change I may reconsider later on.