PR https://github.com/miraheze/CreateWiki/pull/447, potentially stalled waiting on a member of SRE to review — perhaps this can be pushed to betaheze?

In T10844#221750, @AmandaCath wrote:

Unfortunately my RL is becoming exceptionally busy to the point that I don't think I'll have the time to actually finish this. Whoever ultimately picks this up, if you want any part of the code that I had partially developed, please contact me.

Unfortunately my RL is becoming exceptionally busy to the point that I don't think I'll have the time to actually finish this. Whoever ultimately picks this up, if you want any part of the code that I had partially developed, please contact me.

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.

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

In T10931#221560, @BrandonWM wrote:

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.

In T10931#221554, @Dmehus wrote:

In T10931#221553, @BrandonWM wrote:

In T10931#221552, @Dmehus wrote:

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.

In T10931#221553, @BrandonWM wrote:

In T10931#221552, @Dmehus wrote:

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.

In T10931#221552, @Dmehus wrote:

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

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.

In T10931#221328, @AmandaCath wrote:

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.

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'm working on this, though it'll take me a few days before I actually publish a PR (I'm developing code incrementally off-site).

In T10844#220686, @AmandaCath wrote:

I'd assume that this would go in here https://github.com/miraheze/CreateWiki/blob/1f993cc82cc9b1649d195ac614e962bc19f1add7/includes/RequestWiki/SpecialRequestWiki.php

If I'm right about that, I can try to write at least an initial version of something like this for T10931#220644 when I have some spare time (should have this week).

I'd assume that this would go in here https://github.com/miraheze/CreateWiki/blob/1f993cc82cc9b1649d195ac614e962bc19f1add7/includes/RequestWiki/SpecialRequestWiki.php

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.

In T10931#220642, @OrangeStar wrote:

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

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.)

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

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

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.

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.

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.

For now, I'm erring on the side of declining while we see how IP Masking rolls out. Once we have more information on that and how it'll work/look like in MediaWiki, we can reconsider this as it'll be a hassle to suddenly yank this from users in the future.

Going to cc @Owen into this conversation as this is also a legal question concerning personally identifiable information.

IPInfo is most definitely going to expose private data once IP Masking starts but it's minimal (geographic location and ISP). The WMF are asking users to agree not to share the data but no full NDA needs signing.

Unfortunately due to IRL circumstances I don't currently have the time to build or maintain the wiki, so I'm not going to go through with any major changes right now.

Will you proceed with this? Otherwise, this task will be closed soon.

Once RequestSSL is completed and all SSL requests are done via the extension, I propose that we remove it from Diffusion as it won't really serve a purpose anymore.

Can someone else please confirm that ManageWiki backups aren't restorable? Not that I don't trust you, but it seems like a major bug that should be addressed.