Update team label triage designations
TODO: provider deeper guidance for what each label means (list more specific examples than "Issues for XYZ team"). That's suitable for a followup PR. This PR is just to maintain basic accuracy.
Fixes bazelbuild/bazel#14684.
Ported from https://github.com/bazelbuild/bazel-website/pull/342.
PiperOrigin-RevId: 431524684
diff --git a/site/en/contribute/maintainers-guide.md b/site/en/contribute/maintainers-guide.md
index 669bb41..071fbf5 100644
--- a/site/en/contribute/maintainers-guide.md
+++ b/site/en/contribute/maintainers-guide.md
@@ -148,7 +148,7 @@
* [**P2**](https://github.com/bazelbuild/bazel/labels/P2){: .external} - Defect or feature
that should be addressed but we don't currently work on. Moderate live issue
in a released Bazel version that is inconvenient for a user that needs to be
- addressed in an future release and/or a easy workaround exists.
+ addressed in an future release and/or an easy workaround exists.
* [**P3**](https://github.com/bazelbuild/bazel/labels/P3){: .external} - Desirable minor bug
fix or enhancement with small impact. Not prioritized into Bazel roadmaps or
any imminent release. May never be fixed.
@@ -169,19 +169,25 @@
* Contact: [ahumesky](https://github.com/ahumesky){: .external}
* [`team-Bazel`](https://github.com/bazelbuild/bazel/labels/team-Bazel){: .external}: General Bazel product/strategy issues
* Contact: [sventiffe](https://github.com/sventiffe){: .external}
+* [`team-Build-Language`](https://github.com/bazelbuild/bazel/labels/team-Build-Language): Issues for the BUILD and .bzl APIs
+ * Contact: [brandjon](https://github.com/brandjon)
* [`team-Configurability`](https://github.com/bazelbuild/bazel/labels/team-Configurability){: .external}: Issues for Configurability team
* Contact: [gregestren](https://github.com/gregestren){: .external}
* [`team-Core`](https://github.com/bazelbuild/bazel/labels/team-Core){: .external}: Issues for Core team
* Contact: [janakdr](https://github.com/janakdr){: .external}
* [`team-Documentation`](https://github.com/bazelbuild/bazel/labels/team-Documentation){: .external}: Issues for Documentation team
* Contact: [communikit](https://github.com/communikit){: .external}
+* [`team-ExternalDeps`](https://github.com/bazelbuild/bazel/labels/team-ExternalDeps): External dependency handling, Bzlmod, remote repositories, WORKSPACE file
+ * Contact: [meteorcloudy](https://github.com/meteorcloudy)
* [`team-Local-Exec`](https://github.com/bazelbuild/bazel/labels/team-Local-Exec){: .external}: Issues for Execution (Local) team
* Contact: [meisterT](https://github.com/meisterT){: .external}
+* [`team-OSS`](https://github.com/bazelbuild/bazel/labels/team-OSS): Issues for Bazel OSS team: installation, release process, Bazel packaging, website, docs infrastructure
+ * Contact: [meteorcloudy](https://github.com/meteorcloudy)
* [`team-Performance`](https://github.com/bazelbuild/bazel/labels/team-Performance){: .external}: Issues for Bazel Performance team
* Contact: [meisterT](https://github.com/meisterT){: .external}
* [`team-Remote-Exec`](https://github.com/bazelbuild/bazel/labels/team-Remote-Exec){: .external}: Issues for Execution (Remote) team
* Contact: [coeuvre](https://github.com/coeuvre){: .external}
-* [`team-Rules-CPP`](https://github.com/bazelbuild/bazel/labels/team-Rules-CPP){: .external}: Issues for C++ rules
+* [`team-Rules-CPP`](https://github.com/bazelbuild/bazel/labels/team-Rules-CPP): Issues for C++ rules, including native Apple rule logic
* Contact: [oquenchil](https://github.com/oquenchil){: .external}
* [`team-Rules-Java`](https://github.com/bazelbuild/bazel/labels/team-Rules-Java){: .external}: Issues for Java rules
* Contact: [comius](https://github.com/comius){: .external}
@@ -189,10 +195,10 @@
* Contact: [comius](https://github.com/comius){: .external}
* [`team-Rules-Server`](https://github.com/bazelbuild/bazel/labels/team-Rules-Server){: .external}: Issues for serverside rules included with Bazel
* Contact: [lberki](https://github.com/lberki){: .external}
-* [`team-Starlark`](https://github.com/bazelbuild/bazel/labels/team-Starlark){: .external}: Issues for Starlark language + Build API
- * Contact: [lberki](https://github.com/lberki){: .external}
-* [`team-XProduct`](https://github.com/bazelbuild/bazel/labels/team-XProduct){: .external}: Issues for Product Excellence team: installation, Bazel packaging, website, command line processing, Bazel CI, Windows, releases / distributions, external repositories
- * Contact: [philwo](https://github.com/philwo){: .external}
+* [`team-Starlark-integration`](https://github.com/bazelbuild/bazel/labels/team-Starlark-integration): Non-API Bazel + Starlark integration. Includes: how Bazel triggers the Starlark interpreter, Stardoc, builtins injection, character encoding. Does *not* include: BUILD or .bzl language issues.
+ * Contact: [brandjon](https://github.com/brandjon)
+* [`team-Starlark-interpreter`](https://github.com/bazelbuild/bazel/labels/team-Starlark-interpreter): Issues for the Starlark interpreter (anything in [java.net.starlark](https://github.com/bazelbuild/bazel/tree/master/src/main/java/net/starlark/java)). BUILD and .bzl API issues (which represent Bazel's *integration* with Starlark) go in `team-Build-Language`.
+ * Contact: [brandjon](https://github.com/brandjon)
For new issues, we deprecated the `category: *` labels in favor of the team
labels.
