HN user
[ my public key: https://keybase.io/fhs; my proof: https://keybase.io/fhs/sigs/Clj-miP2Jv0wJCF1RGYdc_2zaazOwveh-QDt9B9yTHc ]
Yes, of course. Acme also.
This seems to be a copy of the blog post from January 2019. Previous discussion: https://news.ycombinator.com/item?id=18979596
What the blog post neglected to mention is that you can force module usage, even inside $GOPATH, by setting the environment variable GO111MODULE=on. I have a go command wrapper script called vgo that sets GO111MODULE=on, which I use when I want to use modules inside $GOPATH. More info here: https://github.com/golang/go/wiki/Modules
Slides if you want to follow along: http://talks.golang.org/2014/static-analysis.slide#1
They're using one issue tracker for everything: https://github.com/golang/go/issues Issues for sub-repositories like this go there also.
Keep in mind that contributing to Go requires that you sign a contributor license agreement, something people might not want to go through (no pun intended) for small changes.
This is the repository: https://bitbucket.org/rsc/vx32 although it's not as up-to-date as some of the forks on bitbucket.
Here is the video of the presentation: https://www.youtube.com/watch?v=VJSlvoUFkBA