I'll switch us over to mail1 potentially tomorrow or Tuesday

Created and password sent to @MacFan4000 via IRC.

@MacFan4000 sorry about that. Please ping me on IRC when you're around and we'll get it sorted.

If this could please be done sooner rather then later, that would be ideal.

This is blocked on a proper user interface for LDAP which @Paladox is dealing with

WikiLirik sözcüleri eleştirisel pozitif-negatif düşünce karşılaştırma
PyschoLyricWiki Attack Groups
Ben ötesi psikoloji

This is not an issue with Miraheze, emails are being sent out. Either contact your mail administrator or consider using an alternative email provider.

I can't send a reset link because the system only allows one password change per 24 hours (with the initial password counting for the current 24 hour period).

Hi, can you try again please?

Thanks for reporting. We are looking into a possible issue.

Will run a script to update meta links to emails in a few hours.

@John: merge when ready and i’ll handle updating emails on meta

In T5016#95534, @RhinosF1 wrote:

In T5016#95533, @Reception123 wrote:

I'd agree with the new proposal. Of course, we should keep staff@ redirected for a long period as it's been here for 4 years.

Leaving open for objections but will PR tonight.

https://github.com/miraheze/puppet/pull/1167

In T5016#95533, @Reception123 wrote:

I'd agree with the new proposal. Of course, we should keep staff@ redirected for a long period as it's been here for 4 years.

I'd agree with the new proposal. Of course, we should keep staff@ redirected for a long period as it's been here for 4 years.

Updated proposal, all removed emails to be redirected for now.

Per SPF
Ops == SRE
*-admins are their own * team which are part of SRE but *-admins are not SREs themselves

Cc’ing @Southparkfan to clarify what the roles are (see IRC and Discord):

To update on a large IRC debate:

In T5016#95475, @Reception123 wrote:

As I've said before I'm personally for keeping the 'staff' term at least for now because as John said the board will delegate tasks to us so we are still the 'staff' since we don't only do technical tasks.

We don’t legally have a staff team

Personally I am only for the SRE@ change.

In T5016#95473, @John wrote:

But then it starts to become noise that people don't want to receive. The issue with "general help request" emails is they become general for everything and everything will go there - plus if it's general, it's not specific enough for some who might not want the noise.

As I've said before I'm personally for keeping the 'staff' term at least for now because as John said the board will delegate tasks to us so we are still the 'staff' since we don't only do technical tasks.

But then it starts to become noise that people don't want to receive. The issue with "general help request" emails is they become general for everything and everything will go there - plus if it's general, it's not specific enough for some who might not want the noise. Escalation is a decision to be made by someone receiving an email, which then puts the responsibility on them to escalate it appropriately and to include all relevant information.

In T5016#95471, @John wrote:

I believe the Board's stance is separation and heavily delegation, therefore a linked emailed which both receive, would be such a wide purview it would only ever affect one team and not the other. So I don't believe a contact@ email going to both will be beneficial or of use to anyone.

I believe the Board's stance is separation and heavily delegation, therefore a linked emailed which both receive, would be such a wide purview it would only ever affect one team and not the other. So I don't believe a contact@ email going to both will be beneficial or of use to anyone.