Skip to content

Conversation

Kobzol
Copy link
Member

@Kobzol Kobzol commented Sep 27, 2025

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

jieyouxu commented Sep 28, 2025

I'm hesitant on this because WG-triage membership has bascially no sustaining-contribution requirements (i.e. anyone could request to join). WDYT?

cc @Dylan-DPC

@Kobzol
Copy link
Member Author

Kobzol commented Sep 28, 2025

Hmm. Maybe we could have two teams then, or different roles within the team?

@jieyouxu jieyouxu added needs-team-repo-admin-review This change requires one of the `team-repo-admins` to review. S-has-concerns Status: has outstanding concerns that need to be addressed. S-waiting-on-team Status: waiting on team labels Sep 29, 2025
@jieyouxu
Copy link
Member

At least to me, it seems to make sense to either have two teams or roles. One for the "low bar" that just makes it easy to adjust labels via UI, and another for members with sustained contributions that at least I'd feel more comfortable providing try permissions to.

Zalathar added a commit to Zalathar/rust that referenced this pull request Sep 29, 2025
tests: Remove ignore-android directive for fixed issue

rust-lang#120567 is marked as fixed, so let's see if we can remove the ignore directives tied to that issue.

<!-- Note to self: wait for rust-lang/team#2002 -->

try-job: arm-android
@Noratrieb
Copy link
Member

Noratrieb commented Sep 29, 2025

I don't think "triage" needs try permissions at all. The original triggering PR was a normal compiler contribution PR, that the person happened to be on the triage wg is more of a coincidence than indicative of a permission problem with the triage WG.

If they make regular contributions where it would be useful to have try perms, they should be added to the compiler team.

@Kobzol
Copy link
Member Author

Kobzol commented Sep 29, 2025

My idea was that if you want to test if some issue happens, try builds can be a useful tool for that, especially if it's on an arch/OS that you don't have access to. But this probably doesn't come up often enough..

@davidtwco
Copy link
Member

I'd like to see more examples of cases where this would have been useful

rust-timer added a commit to rust-lang/rust that referenced this pull request Sep 29, 2025
Rollup merge of #147100 - Enselic:ignore-less, r=jieyouxu

tests: Remove ignore-android directive for fixed issue

#120567 is marked as fixed, so let's see if we can remove the ignore directives tied to that issue.

<!-- Note to self: wait for rust-lang/team#2002 -->

try-job: arm-android
@Enselic
Copy link
Member

Enselic commented Sep 29, 2025

I was admittedly supporting giving wg-triage try rights mostly so I wouldn't have to keep asking for it myself on a case by case basis, which is inconvenient both for me and for others.

After reading this it seems like adding me as a Compiler Team Member is a reasonable way to give me try permission (and more). But I understand if I do not meet the qualifications for such membership.

Here are examples of when permissions had to be explicitly delegated to me (both r+ and try), stretching 3 years back:

To give a sense of what my contribution history looks like, it's probably best to browse this list, stretching 3.5 years back. Some examples:

github-actions bot pushed a commit to rust-lang/miri that referenced this pull request Sep 30, 2025
tests: Remove ignore-android directive for fixed issue

rust-lang/rust#120567 is marked as fixed, so let's see if we can remove the ignore directives tied to that issue.

<!-- Note to self: wait for rust-lang/team#2002 -->

try-job: arm-android
@Kobzol
Copy link
Member Author

Kobzol commented Sep 30, 2025

It seems like there's a better way to handle this than giving try permissions to wg-triage. Closing.

@Kobzol Kobzol closed this Sep 30, 2025
@Kobzol Kobzol deleted the triage-try branch September 30, 2025 14:42
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-has-concerns Status: has outstanding concerns that need to be addressed. S-waiting-on-team Status: waiting on team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants