all: refresh CONTRIBUTORS file before release

[rsc]

We should set up a process where CONTRIBUTORS gets updated semiautomatically.
See #10639 for the last time, which I believe was more manual.

[bradfitz]

I wrote a tool for it. But it has to run inside Google (with my credentials refreshed) to hit the CLA server.

[gopherbot]

CL https://golang.org/cl/16824 mentions this issue.

[gopherbot]

CL https://golang.org/cl/16825 mentions this issue.

[bradfitz]

I've added the Google-internal tool to google3/experimental/users/bradfitz/updateac/updateac.go for now so I don't lose it. We can put it somewhere better outside of experimental when it's code reviewed and we decide on a name and location. (which might prove more difficult than writing the tool)

I don't know what it takes to close this bug. I doubt we'll be able to auto-run the tool regularly, given its dependence on Google's internal CLA service.

We can at least run this again right before Go 1.6 is released.

[andygrunwald]

@bradfitz Is this tool open source or public available?

[bradfitz]

Nope. It uses a Google-internal service.

[andygrunwald]

That was fast. Thx.

[gopherbot]

CL https://golang.org/cl/18264 mentions this issue.

[bradfitz]

I also submitted git rev 9a2d717 yesterday but forgot to mention this issue.

It might be okay to close this bug now. @rsc?

[rsc]

It's kind of nice to have a bug open to remind us. I was thinking we could just move the milestone. But whatever you want to do is fine, since you run the tool.