a more robust proposal process · golang go · Discussion #80580 · GitHub
Skip to content You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert a more robust proposal process #80580 aclements announced in Discussions a more robust proposal process #80580 aclements Jul 27, 2026 · 27 comments · 53 replies Return to top Discussion options Uh oh!
There was an error while loading. Please reload this page . Uh oh! There was an error while loading. Please reload this page . aclements Jul 27, 2026 Maintainer Short link: https://go.dev/s/proposal-proposal-2026 Since I took over leading Go's proposal process in late 2024, I've been thinking deeply about its strengths and faults. I believe deeply in its goals of transparency and community involvement, but that while its foundations are solid, its process failures mean it doesn't always live up to its goals.
I don't think these process failures are something that can be addressed piecemeal, so this is my attempt at a holistic update to the proposal process. The basic outline isn't so different: anyone can file a proposal, discussion all happens in the open, and decisions are made after careful consideration by a small group of experts. This proposal is largely about technical updates throughout the process to better achieve its goals.
Abstract The proposal process is Go’s engine of change. It’s a critical way the community shapes and informs the evolution of Go. But it also has some clear flaws: a backlog that is growing 23% year-over-year with a median age of over two years, and a manual prioritization process that is neither transparent nor community-informed. To resolve these bottlenecks, this proposal refines the process by: Establishing a formal triage process to engage proposals quickly and make fast, early decisions, Using weighted community emoji voting to transparently prioritize proposals for review, Splitting proposal review into domain-specific tracks to scale throughput and create the capacity to bring in community .
Background The Go proposal process is a vital mechanism for ensuring the Go project’s development remains transparent and community-driven, and for maintaining the Go platform’s incredibly high standards of compatibility and simplicity. The proposal process was first formalized in 2015 and evolved between 2015 and 2019 for better transparency and to handle large and contentious changes. This period also marked a shift from rigid stability bordering on ossification to pragmatic evolution .
The proposal process is a careful balance of many factors. It is designed to make irreversible decisions that are subject to the Go compatibility promise , while also maintaining Go’s uniformity of design. Over the past several years, we’ve introduced technical mechanisms to lower the risk of making such decisions, such as language versions, forward compatibility , and GOEXPERIMENT , but the proposal process is necessarily heavyweight because “yes is forever.” The process is also designed to protect the attention of the small proposal review group and prevent receive livelock by strictly balancing our intake of proposals with our output of decisions.
At the same time, anyone can file a proposal, and this openness is at the heart of the proposal process. The public proposal process has critically shaped the Go project, but these factors, combined with time and growth, have led to several problems. These problems are felt by the community and many of them can be seen in the data, such as in figure 1. The backlog of unreviewed proposals is growing by 23% year over year, and the median age of a proposal in the backlog now exceeds two years.
Today, there’s no process for prioritizing this massive backlog, so which proposals enter review and when is frustratingly opaque and fails to broadly account for community input. Meanwhile, this backlog would be growing far faster were it not for the heroics of a few self-nominated contributors triaging incoming proposals. This triage work is thankless and often leads to conflict (nobody likes having their proposal closed!).
At the same time, accepted proposals also often languish, leading to confusion and wasted work. Finally, since the proposal review committee itself is small while covering diverse expertise, often only one or two people have the expertise to evaluate any given proposal and there are inevitable gaps. Figure 1. The proposal process by the numbers. “New” shows the number of new proposals filed in each year. “Backlog” shows the total number of proposals that have been filed but not reviewed as of Jan 1 each year.
“Early reject” shows how many proposals were closed without review in each year, including by ad hoc triage. “Review” shows how many proposals passed through the proposal review committee within each year. The last four rows show the outcomes of the review process. “Backlog”, “Hold”, and “Accepted” are inventory states that show the total number of proposals in that state on Jan 1. “Early Reject”, “Implemented”, and “Declined” are terminal states and only show the proposals that entered that state in a given calendar year.
Overview of the proposed process Figure 2. An overview of the flow of a proposal through the proposed process. The four columns represent the phases a proposal passes through. Blue boxes represent people processes and green pills represent decisions, often with supporting data. We propose a refined process to align the mechanics of proposals with our principles. This process divides a proposal's lifecycle into four distinct phases (figure 2): Incoming : The entry point for a newly filed proposal.
Here, an asynchronous, lightweight triage decides if a proposal meets the bar for review or should be closed with a standard rationale. Ready : Where proposals wait in a public queue and the community can indicate interest using emoji voting. The triaged priority is combined with weighted emoji votes to determine how quickly a proposal enters active review. Active : Domain-specific review tracks meet weekly to review active proposals.
Sessions are timeboxed by proposal controversy to isolate “easy” proposals from “hard” ones. As these groups decide on proposals, they pull in Ready proposals based on priority, track, and controversy. Decided : Like now, proposals have a one week final comment period after a review track recommends “accept” or “decline.” A final review group also checks all proposals recommended for “accept” for uniformity of design.
The specific mechanics and rules for each phase are detailed in the following sections. Detailed mechanics Proposal triage The newly formed proposal triage group will consist of 3–5 individuals. Their role is twofold: reviewing new proposals to determine whether they meet the bar for proposal review and providing initial prioritization. By formalizing this process and establishing a small, designated group, we aim to distribute the workload more equitably, provide a consistent framework for triage, and ensure decisions reflect a wider range of perspectives while also officially recognizing the efforts of triage members.
Unlike proposal review—a stringent process for making high-confidence, irreversible decisions—proposal triage is designed for making reversible decisions through asynchronous and lightweight voting rather than consensus. For each proposal, each member of the proposal triage can select one of three actions: Vote to close , with a rationale. Closure requires a ⅔ supermajority with a minimum of two “close” votes ( v c ≥ ⅔ n ∧ v c ≥ 2).
Vote ready for proposal review , with a track, initial priority, and a controversy level. Promoting a proposal to proposal review requires a vote of at least ⅓ of the group, again with a minimum of two “ready” votes ( v r > �
The rest of this page is on the live site.