Dave - thanks so much for your input - it’s super valuable to have perspective from devs as deeply embedded with Go as yourself, and we’d be happy to continue to chat as we move through the Beta towards a first release - so I hope it’s ok if I ping you for further input at some time!
I quickly wanted to clarify that it is not ActiveState’s intention to fork the language and isolate changes from the wider community - in fact, it is fully part of the plan to push upstream any changes we may make to the core Go code, or any packages within the distro, assuming they’re suitable to push upstream of course. So, everyone will still have the benefit of any contributions we make.
Now, while there haven’t been any core Go contributors yet, I would fully expect that to change as we move forward (despite being new myself, I’m actively looking for ways to get involved!), and I know that in the past previous AS employees have contributed to Go projects (one fellow even pushed a few commits up to one of your packages MDNS). ActiveState has also contributed packages to the community of its own including https://github.com/Komodo/komodo-go and https://devhub.io/repos/ActiveState-doozer (edit: forked from https://github.com/ha/doozer).
Like Jeff said, we have a long history with open source language communities, and are genuinely seeking to partner with each language community to find ways to contribute positively to those communities and to help them grow and prosper - which is beneficial to everyone.