There is some great data in here, I love the detailed presentation of results rather than just presenting a summary. Some interesting questions and responses here:

What changes would most improve the Go documentation?

Collectively examples gets 26% and docs gets 6% - would be nice to see the data cleaned up a bit here, as there are multiple examples entries.

What Go libraries do you need that aren't available today?

Interesting to see such demand for UI support and mobile support - these are the two hardest parts to crack, given that cross platform UIs typically please no-one. I'd like to see the go team take a radically different approach here playing to Go's strengths - define some framework for presenting web UIs with a Go backend on Android and iOS.

What changes would improve Go most?

The G word makes an entrance as the top request. I'd prefer if they took a step back and prepared a Go 2.0 which removed some of the inevitable cruft (comments as directives, struct tags), and rethought some other features - mostly taking things out rather than adding things, though it would be nice also to see a solution to generics/better containers.

Everyone is reasonably happy with editing it seems.

And finally golangnews is somewhere in the middle as a news source for gophers - thanks to all the readers!

Splitting the write-in responses into individual keywords is a little confusing - it's weird for example to see words like 'great' without seeing the context they were used in (e.g. docs need a great deal of work, docs are great already etc).. It'd be great to see the data available from this (in anonymised form if necc.) so that others can also look at the responses.