Currently we don't have a good definition of what a marker team is, or when it should be used. I think it would be helpful to define that more clearly.
Marker teams were introduced in #135 to accommodate the addition of icebreakers-llvm in #123, which was hooked up with triagebot to provide a way for people to ping a group of individuals who otherwise would not be members of the rust-org.
Over time, the use of marker-team has expanded organically to generally identify a group of people that need some kind of integration into our infrastructure, but otherwise are not members of the org. Some examples:
- Infrastructure accommodation:
- docsrs-ops for permissions to manage docs.rs infrastructure, and crates-io-on-call and
crates-io-admins for crates.io infrastructure.
- cloud-compute to grant access to cloud computers
foundation-email-redirectsinfra-adminsrustconf-emailsteam-repo-adminscouncil-librarians -- Permissions to leadership-council repo.hiring -- to create an email list
- Meta groups (to consolidate other groups for some purpose):
- inside-rust-reviewers is a consolidation of other teams/members to provide an easier way to grant permissions.
all, leads, alumni, wg-leads, project-group-leads
- Ping groups:
android, windows, apple, arm, arm-maintainers, fuchsia, loongarch, risc-v, rust-for-linux, relnotes-interest-group, wasi, wasm, emscripten, icebreakers-llvm, icebreakers-cleanup-crew
- Things that probably should be teams:
- Satellite groups -- Groups with permissions (like GitHub), closely related, but not part of the org:
goal-ownersgsoc-contributorsmentors -- Not entirely sure what this does.ospp, ospp-contributors
Another thought I had was to split marker-team into different classifications, like "meta-team" or "ping-group".
Currently we don't have a good definition of what a marker team is, or when it should be used. I think it would be helpful to define that more clearly.
Marker teams were introduced in #135 to accommodate the addition of icebreakers-llvm in #123, which was hooked up with triagebot to provide a way for people to ping a group of individuals who otherwise would not be members of the rust-org.
Over time, the use of marker-team has expanded organically to generally identify a group of people that need some kind of integration into our infrastructure, but otherwise are not members of the org. Some examples:
crates-io-adminsfor crates.io infrastructure.foundation-email-redirectsinfra-adminsrustconf-emailsteam-repo-adminscouncil-librarians-- Permissions to leadership-council repo.hiring-- to create an email listall,leads,alumni,wg-leads,project-group-leadsandroid,windows,apple,arm,arm-maintainers,fuchsia,loongarch,risc-v,rust-for-linux,relnotes-interest-group,wasi,wasm,emscripten,icebreakers-llvm,icebreakers-cleanup-crewemacs,vim,arewewebyetgoal-ownersgsoc-contributorsmentors-- Not entirely sure what this does.ospp,ospp-contributorsAnother thought I had was to split marker-team into different classifications, like "meta-team" or "ping-group".