Filippo Valsorda: github.com/golang/propo... They are issues with tracking labels in github.com/golang/go/is... (and I think there's a GitHub project too. Roughly they go "created (label Proposal)" -> "active (comment saying so and added to minutes)" -> accepted (label Proposal-Accepted) -> implemented (closed).

I really, truly, wish Rust leadership would just stop trying to create more designs for radical changes in the language. And instead work on finishing things that were half started.

I've thought repeatedly about trying to publicly and clearly track RFC's that are approved-but-not-implemented but then been overwhelmed by the amount of work it is to start that lol

After being thoroughly nerd-sniped 😅 here's what the Rust RFC tracking issues look like over their history. Caveats: there exist multiple tracking issues for some RFCs due to subtasks being split out, and there are 9 tracking issues with RFC labels but no obvious associated RFC that I've omitted.

And to cap off the snipe, a barebones website to host and render the Rust RFC tracking issues graph:

Rust RFC Observerrust.rfc.observer

Ooooh do Go proposals, too!

I can totally set up go.rfc.observer. Where do Go proposals live and what is their evolution process?

github.com/golang/propo... They are issues with tracking labels in github.com/golang/go/is... (and I think there's a GitHub project too. Roughly they go "created (label Proposal)" -> "active (comment saying so and added to minutes)" -> accepted (label Proposal-Accepted) -> implemented (closed).

GitHub - golang/proposal: Go Project Design Documentsgithub.com Go Project Design Documents. Contribute to golang/proposal development by creating an account on GitHub.

Okay, first pass is up: go.rfc.observer "Implemented" is any issue closed while labeled Proposal-Accepted, other closures are "Closed". Did the Go Proposal workflow change in late 2015? There's very little label data prior to then. Also, y'all have a lot of proposals! Data fetch takes a minute.

AFAIK there was no real proposal process before 2015. Even current proposal process with Review meeting minutes started in 2019 (see github.com/golang/go/is...)

proposal: review meeting minutes · Issue #33502 · golang/gogithub.com The proposal review group meets regularly (roughly weekly) to review pending proposal issues and move them along in the proposal process. Review consists primarily of checking that discussion is on...

Good to know, thanks. I can't parse meeting minutes etc yet, gonna need persistence to cache the results so rendering is not horribly slow. As long as the current graph is close enough to the Go ecosystem's expectation, it will do for now.

Post