@XAMPPRocky I was talking with @Pietro Albini about the wg-leads mailing list
@Pietro Albini says it works and we were checking the code and it seems it does the right thing
you told me that it doesn't work?
you know what happens exactly?
@Santiago Pastorino Wrong stream?
Either way. People haven’t been getting mail about all hands. That was just my guess. There’s definitely something wrong with all
“Wrong” as in doesn’t match what I would expect.
Santiago Pastorino Wrong stream?
well unsure where to place this, could have been in #rust-all-hands-2020 (public)
but it's a general issue, unrelated to t-compiler so ... unsure :)
looked at mailgun, I don't see recent bounces either
@Pietro Albini Anyone who's in a team working group seems to be the one correlation.
oh working groups were explicitly meant not to be in all@
regardless of whether they were team or domain wgs
Well we need to include the team wg members. As it seems to be everyones expectation, that they are supposed invited in to the all hands. I suspect in the future this is solved by making these project groups and including those in all, and leaving domain wgs as is.
well this was not what I was told when I created all@ with the team repo :sweat_smile:
like, all@ is working as intended, it's just not suitable for all hands invitations
@Pietro Albini I don't doubt that, I suspect this is a result of working groups and all hands changing from last year.
I would like to make all@ the single source of truth as it were for contacting rust-lang members.
team members, or just people involved in the project?
Well in my mind it should mimic the policy of all hands. If you're someone that should be qualified to attend all hands you should be in all.
Which I believe is teams, sub-teams, and wg-leads.
@Pietro Albini People who are in team working groups.
Or at least that’s the one thing that connects them