PortingPolicy, TestFailures: make port-maintainers links more direct Link directly to the 'Teams' tab instead of the default 'Members' tab. It's more useful, since the top-level golang/port-maintainers team is not really used; it just holds the port-specific sub-teams. The link at https://go.dev/wiki/PortingPolicy#maintaining-a-port already does this, and this CL updates the other two. Change-Id: I3c0167089f809345e7afd6fe786739e19cc6d2f0 Reviewed-on: https://go-review.googlesource.com/c/wiki/+/767942 Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Keith Randall <khr@golang.org>
diff --git a/PortingPolicy.md b/PortingPolicy.md index 7473c2d..881db10 100644 --- a/PortingPolicy.md +++ b/PortingPolicy.md
@@ -15,7 +15,7 @@ - A [proposal](https://go.dev/s/proposal) must be filed and accepted in which the Go team accepts overall responsibility for having the new port in the core Go tree. In general, each new port carries an upkeep cost separate from the direct maintenance. That cost varies by port, depending on how similar a new port is to existing ones. The cost must be balanced by an overall benefit in the form of potential new users or use cases for Go. - At least two developers must be named (and agree) to maintain the port, by making required updates in a timely manner as architecture or operating system requirements change. - - Port maintainers are listed in the subteams of [@golang/port-maintainers](https://github.com/orgs/golang/teams/port-maintainers). To be added or removed as a maintainer for an existing port, please [file an issue](https://go.dev/issue/new). + - Port maintainers are listed in the subteams of [@golang/port-maintainers](https://github.com/orgs/golang/teams/port-maintainers/teams). To be added or removed as a maintainer for an existing port, please [file an issue](https://go.dev/issue/new). - Changes that are specific to a particular port should normally be reviewed first by one of the port maintainers (though not the one who wrote the change, of course). We currently require two reviews for each change, so changes will still typically be reviewed by someone who is not a port maintainer, but ideally that can be a more casual review by someone less familiar with the port details. - A developer must be named (and agree) to maintain the builder, the machine trying each git revision and providing data for https://build.golang.org.
diff --git a/TestFailures.md b/TestFailures.md index 2234d8f..7e689f5 100644 --- a/TestFailures.md +++ b/TestFailures.md
@@ -105,7 +105,7 @@ If the failure appears to be specific to a `GOOS` or `GOARCH` label the issue with the corresponding GOOS and/or GOARCH labels, and mention the relevant subteam(s) of -[@golang/port-maintainers](https://github.com/orgs/golang/teams/port-maintainers) +[@golang/port-maintainers](https://github.com/orgs/golang/teams/port-maintainers/teams) on the issue. If the failure appears to affect at least one