Resolve Go/go/golang-related issues and PRs as a group

[johnmhoran]

We have 7 open issues and PRs that involve Go/go/golang (all tagged type: golang). (Some also involve other topics as well.) These could be handled one-by-one or as a group.

Please share your views on how we can most effectively and efficiently address this set of issues/PRs.

• Issue How are golang sub-modules supposed to be expressed by purl? #63

• Issue Go is called Go, not Golang #67

• Issue Should we support a leading v in golang packages? #294

• Issue [PURL-TYPE: golang] fix type spec regarding path segments #308

• PR add an example with / in namespace to README and SPEC #176

• PR Go suggestions for PURL-TYPES.rst #196

• PR Add new spec for go package URLs #338

[johnmhoran]

As new Go-related issues/PRs are added, you can see the current group at type: golang Proposed new type as well as component discussions .