The first step is to ensure that all developers understand Go. In most projects, there will be at least a few developers who are not experienced Go programmers. By understand, I mean not just the theoretical part, but actually trying out various programming constructs to get a feel for the language. https://tour.golang.org/ is a good start. Effective Go (https://golang.org/doc/effective_go.html) is another good resource for learning about the language. Besides an introduction, it also talks about best practices (package-naming convention, state-sharing, and so on).

In addition to learning your way around the language, it is also good to read some non-trivial Go code. You can find this on a lot of projects in GitHub, including the Docker source and the standard library. I find the bytes/buffer.go code (https://golang.org/src/bytes/buffer.go) is particularly well written/documented.

Installing Go on a laptop is easy for all standard distributions. But I recommend using Go version manager (GVM) to easily allow you to navigate versions/GOROOTs/GOHOMEs.