Skip to content

Conversation

@jieyouxu
Copy link
Member

@jieyouxu jieyouxu commented Aug 30, 2025

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.

@jieyouxu jieyouxu added needs-team-repo-admin-review This change requires one of the `team-repo-admins` to review. S-waiting-on-review Status: waiting on review from a team/WG/PG lead, an infra-admin, and/or a team-repo-admin. T-infra Relevant to the infrastructure team. labels Aug 30, 2025
@jieyouxu jieyouxu added S-blocked Status: blocked and removed S-waiting-on-review Status: waiting on review from a team/WG/PG lead, an infra-admin, and/or a team-repo-admin. labels Aug 30, 2025
@jieyouxu

This comment was marked as outdated.

@jieyouxu jieyouxu marked this pull request as draft August 30, 2025 05:08
@jieyouxu jieyouxu force-pushed the infra-announcement-all branch from b344a00 to 46df291 Compare September 15, 2025 11:55
@Kobzol
Copy link
Member

Kobzol commented Sep 26, 2025

I would perhaps rather have an (either implicit or explicit) opt-out of the Zulip ID check for t-all specifically. Otherwise every new team member added without a Zulip ID will trigger the Zulip check on this team. That being said, if we wanted to make Zulip membership "more mandatory", then that would actually be nice.

@traviscross
Copy link
Contributor

traviscross commented Sep 26, 2025

That being said, if we wanted to make Zulip membership "more mandatory", then that would actually be nice.

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.

@Kobzol
Copy link
Member

Kobzol commented Sep 26, 2025

I don't know if everyone in team is actively on Zulip (most likely not), and we still didn't resolve the wg-embedded situation, which is an organization that is currently in team, and we kind of manage their GitHub repos, but they are completely separate and operate mostly on Matrix.

But at least from a technical point of view, I think that requiring people in team to have an associated Zulip handle (even if they don't actually actively use Zulip) would not be such a problem, especially since it's quite easy to create a Zulip account using a GitHub account, which we already require for everyone. So we could say that to be in the Project, you must have GitHub + Zulip (while now it's just GitHub).

@jieyouxu
Copy link
Member Author

jieyouxu commented Oct 2, 2025

I would perhaps rather have an (either implicit or explicit) opt-out of the Zulip ID check for t-all specifically. Otherwise every new team member added without a Zulip ID will trigger the Zulip check on this team. That being said, if we wanted to make Zulip membership "more mandatory", then that would actually be nice.

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?

@jieyouxu
Copy link
Member Author

Remaining:

[ERROR rust_team::validate] validation error: person `U007D` in 'all' is a member of a Zulip user group 'T-all' but has no Zulip id
[ERROR rust_team::validate] validation error: person `andrewpollack` in 'all' is a member of a Zulip user group 'T-all' but has no Zulip id
[ERROR rust_team::validate] validation error: person `arshiamufti` in 'all' is a member of a Zulip user group 'T-all' but has no Zulip id
[ERROR rust_team::validate] validation error: person `bnchi` in 'all' is a member of a Zulip user group 'T-all' but has no Zulip id
[ERROR rust_team::validate] validation error: person `celaus` in 'all' is a member of a Zulip user group 'T-all' but has no Zulip id
[ERROR rust_team::validate] validation error: person `opeolluwa` in 'all' is a member of a Zulip user group 'T-all' but has no Zulip id
[ERROR rust_team] 6 validation errors found

@Kobzol
Copy link
Member

Kobzol commented Nov 11, 2025

We could just put these people into the ignore list for now (I added that concept in #2040).

@jieyouxu
Copy link
Member Author

Yeah, that's my plan, just ran out of time yesterday.

@jieyouxu jieyouxu force-pushed the infra-announcement-all branch from b28635e to 7c1cbab Compare November 12, 2025 01:08
@github-actions
Copy link

Dry-run check results

[WARN  sync_team] sync-team is running in dry mode, no changes will be applied.
[INFO  sync_team] synchronizing github

@jieyouxu
Copy link
Member Author

Council FCP on rust-lang/leadership-council#228 has completed, so no longer blocked.

@jieyouxu jieyouxu added S-waiting-on-review Status: waiting on review from a team/WG/PG lead, an infra-admin, and/or a team-repo-admin. and removed S-blocked Status: blocked labels Nov 12, 2025
@jieyouxu jieyouxu marked this pull request as ready for review November 12, 2025 01:20
@jieyouxu
Copy link
Member Author

We could just put these people into the ignore list for now (I added that concept in #2040).

I'm using excluded-people for now, didn't want to pull those changes into this PR.

teams/all.toml Outdated

[[zulip-groups]]
name = "T-all"
# Exclude the following people from the Zulip group for grandfathering
Copy link
Member

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

Copy link
Member Author

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.

marcoieni
marcoieni previously approved these changes Nov 13, 2025
@marcoieni
Copy link
Member

marcoieni commented Nov 13, 2025

I approved this but later realized that probably this needs more a team repo admin to approve?

@jieyouxu
Copy link
Member Author

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.
@Mark-Simulacrum Mark-Simulacrum added this pull request to the merge queue Nov 15, 2025
Merged via the queue into rust-lang:main with commit 30f9bf5 Nov 15, 2025
3 checks passed
@jieyouxu jieyouxu deleted the infra-announcement-all branch November 16, 2025 07:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-team-repo-admin-review This change requires one of the `team-repo-admins` to review. S-waiting-on-review Status: waiting on review from a team/WG/PG lead, an infra-admin, and/or a team-repo-admin. T-infra Relevant to the infrastructure team. T-leadership-council Relevant to the leadership council.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants