Project for:
- all higher-level tasks affecting Site Reliability Engineering management;
- tasks requiring pro-active engagement of both the Infrastructure and MediaWiki sub-teams;
- a funnel point for initial triage if sub-team scope is unknown.
Project for:
Withdrawing this.
In T11375#228523, @MacFan4000 wrote: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.
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 :)
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.
@Agent_Isai — SRE as above.
What position are you applying for? Site Reliability Engineer? MediaWiki Engineer? Software Engineer?
No longer necessary, per discussion on Discord. Paladox will re-open the task when needed.
Orain.org seems to have been renewed until 2024, so the consensus seems to be in keeping the domain at least for now. Closing this task to clear the backlog until it can be evaluated again.
We have a inactivity policy: https://meta.miraheze.org/wiki/Tech:Inactivity_policy
**This is the truth Miraheze is burning like a house and the suppoesed firefighters are sitting relaxing having a coffee instead of helping
I'm withdrawing this request.
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
Even though I don't currently have any roles and am not sure if I will in the future I think the concerns raised by myself and Dmehus should be addressed and not ignored.
Conduct and behavior has been raised as one of the main issue in SRE and the source of people leaving so it really isn't something that can be "swept under the rug" and ignored.
Public key set, it's the same one I used before resigning.
This is going to take a while. At the very least, this is pending on there being someone with both the power and the will to process these requests. So this will probably not happen until Labster and the others deal with the org problems.
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.
So as a long-lasted wiki farm, Miraheze is seemed to be coming to an end by losing so many volunteers in such a short time?
In T10935#221463, @Dmehus wrote:Naleksuh was a generally globally disruptive user (particularly on Meta Wiki and Phabricator), who Stewards should've globally locked as such prior to the events getting out of hand, so I can appreciate they have a tendency to ruffle peoples' feathers and cause them to act with some degree of irrationality. As such, I can partially forgive Orange Star for that irrationality, but at the same time and given the recency of the events, we're handing a lot of significant technical access with the MWE role, it does give me pause as to consider the likelihood for similar actions, either community or technical. So, while I would not necessarily oppose this request, perhaps only weakly, at the same time, I cannot support it, either
Naleksuh was a generally globally disruptive user (particularly on Meta Wiki and Phabricator), who Stewards should've globally locked as such prior to the events getting out of hand, so I can appreciate they have a tendency to ruffle peoples' feathers and cause them to act with some degree of irrationality. As such, I can partially forgive Orange Star for that irrationality, but at the same time and given the recency of the events, we're handing a lot of significant technical access with the MWE role, it does give me pause as to consider the likelihood for similar actions, either community or technical. So, while I would not necessarily oppose this request, perhaps only weakly, at the same time, I cannot support it, either
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?
Per T10969#221218