I went through and checked all the go-* packages, they are all executable binaries not modules, hence they use the name of the project, which is as per guidelines.
The golang-* packages seem to be using an interesting naming scheme. They do use the full module name but strip out the TLD - hence 'golang.org/x/text' becomes golang-golang-x-text, or 'github.com/alecthomas/units' becomes golang-github-alecthomas-units. It would be good to document *that* transformation in the guidelines explicitly. As for AUR packages, I believe they are also following this same pattern (regular apps use the project name, modules use the fully qualified module name with TLD omitted). AUR/golang-glide appears to violate this at first, but the naming is to distinguish from extra/glide (completely unrelated). Similar case with AUR/golang-mockery. Hence it seems even the AUR packages are following the guidelines. So for your question, Polarian, it would depend on what type package you're posting as well as if there's a naming conflict. But I do not see this varied naming as indicative of an upcoming guideline change. Besides, packages should follow the current guidelines, not speculative future ones :) - éclairevoyant
