- all higher-level tasks affecting the Director of Site Reliability Engineering;
- 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.
Test3 is now running as 'staging':
It would also be good if we could allow for the extension to receive other updates and still have the patch remain applied, which may require some research/testing.
If we copy enough logic, it should be fine. In the worst case, you just run git apply after updating but before syncing.
This also saves on running commands many many times and cloning git. We could probably eventually automate it in puppet if mediawiki or config changes
CSP Desicions can take a while
can someone please look at this and tell me what do i need to do.
anybody working here?
can i get some help..
i need this white listed.
I will shortly review each permission and see if we need them or not. For now adding the list here:
@Reception123: any progress on reviewing the rights? I do think this should be done so we don't have unnecessary ones.
Have access now to OVH/RN/Proxmox. I believe that's everything.
Phorge is now becoming a reality at https://we.phorge.it/
Bump. Disallowing Spotify when Google is allowed makes no sense, IMO; Spotify should be trusted enough even though they serve ads.
@Owen Would you be able to provide some comments and suggestions for what you think needs to be considered before opening a security advisory and requesting a CVE from GitHub?
My concerns remain regardless of the impact.
This work is going to the probably the biggest improvement to the way SSL certificate deployments work since the introduction of the ssl repo and turn a near completely manual process into one that could take minutes and now provide near instant feedback to the requestor on whether they're correctly pointing their domain at Miraheze.
While this is an entirely SRE matter, I would like to make my opinion clear that given the complaints raised regarding the user’s attitude, communication abilities, and activity - given SRE’s recent stance of working to build community relationships, I wouldn’t support an access elevation - essentially rewarding - a major contributor of the current endemic SRE is finding itself in.
needs approval from. Site Reliability Engineering
Discussed with Void, remaining rights will be granted during the transfer period.
When would a good time to try again be?
The extension itself is approved but this still needs Site Reliability Engineering to add Spotify to the CSP whitelist.
Since @RhinosF1 has a PR open, assigning to him.
Closing in favour of keeping T7532 to address the specific database-related problem rather than just the 503 whose cause is now known.
Lowering status as this is now very likely temporarily fixed.