Russ Cox

Based on the discussion above, this proposal seems like a **[likely accept](https://go.dev/s/proposal-status#likely-accept)**. — rsc for the proposal review group

This proposal has been added to the [active column](https://golang.org/s/proposal-status#active) of the proposals project and will now be reviewed at the weekly proposal review meetings. — rsc for the proposal review...

The new port policy (#53383) will require two maintainers for the port. Assuming that is accepted, is there anyone else who would be willing to be a second maintainer for...

Thanks to @MikaelUrankar, @dmgk, and @mengzhuo for volunteering to be maintainers.

Based on the discussion above, this proposal seems like a **[likely accept](https://golang.org/s/proposal-status#likely-accept)**. — rsc for the proposal review group

No change in consensus, so **[accepted](https://golang.org/s/proposal-status#accepted)**. 🎉 This issue now tracks the work of implementing the proposal. — rsc for the proposal review group

This proposal has been added to the [active column](https://golang.org/s/proposal-status#active) of the proposals project and will now be reviewed at the weekly proposal review meetings. — rsc for the proposal review...

I think the discussion helped a lot with addressing most of people's concerns, but I'm still a bit surprised about how little discussion is happening here. Does anyone have any...

It sounds like we need to resolve how feasible it is and how much work it is to post cross-compiled toolchains for secondary ports. Otherwise it sounds like people are...

> It sounds like we need to resolve how feasible it is and how much work it is to post cross-compiled toolchains for secondary ports. Otherwise it sounds like people...