-
Notifications
You must be signed in to change notification settings - Fork 332
Create T-all zulip user group
#1969
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create T-all zulip user group
#1969
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
b344a00 to
46df291
Compare
|
I would perhaps rather have an (either implicit or explicit) opt-out of the Zulip ID check for |
We have recently been moving things that weren't on Zulip to Zulip. I wonder if maybe we are at or near the point we could do this. |
|
I don't know if everyone in But at least from a technical point of view, I think that requiring people in |
Okay, that sounds reasonable. Though I think that change will need to land after #1977. Requiring everyone to have a zulip-id seems reasonable as well, though I'd defer that decision to the council. For this purpose, we can just use the T-all-won't-hard-require-everyone-to-have-zulip-id I suppose. Do you think we should nominate this for the council, or should we just go with T-all-is-special for now? |
f549303 to
b28635e
Compare
|
Remaining: |
|
We could just put these people into the ignore list for now (I added that concept in #2040). |
|
Yeah, that's my plan, just ran out of time yesterday. |
b28635e to
7c1cbab
Compare
Dry-run check results |
|
Council FCP on rust-lang/leadership-council#228 has completed, so no longer blocked. |
I'm using |
teams/all.toml
Outdated
|
|
||
| [[zulip-groups]] | ||
| name = "T-all" | ||
| # Exclude the following people from the Zulip group for grandfathering |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what does "grandfathering" mean in this context? Can you explain this in simpler terms in the comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previously there was no T-all Zulip group, and we didn't require all project team members to have a Zulip ID in their people/ entry prior to rust-lang/leadership-council#228. I clarified this in the comment.
|
I approved this but later realized that probably this needs more a team repo admin to approve? |
|
Hm, probably. I'll wait for another team-repo-admin to review. |
This is needed to configure the infra announcement channel so the zulip user group membership is synced automatically with project team membership. This notably does not include working groups, project groups, or marker teams.
7c1cbab to
f899817
Compare
This is needed to configure the infra announcement channel so the zulip user group membership is synced automatically with project team membership.
This notably does not include working groups, project groups, or marker teams.
See #t-infra > Communication method for dev desktops @ 💬 for more details.