We were lacking guidance on go_package naming. Since we have a dedicated team to managing this code, API producers shouldn't generally be deciding on this themselves, but the general pattern of our best practices can still be documented.
Also adds a link to the Protobuf langauge package docs, since we don't mention every single option in this AIP, nor do we want to.
We were lacking guidance on
go_packagenaming. Since we have a dedicated team to managing this code, API producers shouldn't generally be deciding on this themselves, but the general pattern of our best practices can still be documented.Also adds a link to the Protobuf langauge package docs, since we don't mention every single option in this AIP, nor do we want to.