When publishing Go code, the usual practice is to distribute the sources directly from the forge that hosts them: github.com/org/project, framagit.org/org/project, …
It is convenient, but it durably ties the import path to the chosen provider: the day you migrate from one forge to another, all your users have to update their imports, while every historical fork keeps pointing at the old address.
Fortunately, the go-import mechanism lets you decouple the import path from the actual hosting location of the code.
All it takes is exposing, on a domain of your choosing, an HTML page containing a <meta name="go-import"> tag that describes where the sources live.





