> I was told—with a straight face—that it was unnecessary because it’s simple enough to read the RFC and do it yourself.
This peaked my interest, because it didn't match my experience at all.
https://github.com/golang/go/issues/12292
It was an initial reply to another user, which was immediately reconsidered and accepted when the request was clarified to include colons. There was concern about the breadth of a single package, and if this should be included in a sibling package. This was all in one morning.
The original user closed the ticket, and was reopened after your comment.
> On the other hand, if I have to read a five-page document, sign up for a third-party code review tool, install strange and mysterious new git commands, and send a diff to a mailing list, only to invariably need to argue endlessly to get a ~15-line function added to a x/ package, hopefully you'll understand why I don't.
Indeed, this was recognized a large obstacle for contributors, and the process changed. The community now accepts contributions via GitHub. Unfortunately, this change happened after your contribution, but is now available should you decide to contribute in the future.
https://golang.org/doc/contribute.html#sending_a_change_gith...