Building a central Go modules repository: GoCenter’s back to the future journey.

Every science fiction fan knows that you can’t fix the past. Try to, and it wrecks the balance of events that led to the present. That’s also what we learned while making GoCenter. While trying to correct an early Go modules design choice and improve certainty, we accidentally made things harder for the Go community. So, like every fictional time traveler, we had to retrace our steps to undo the change.

We learned some tough lessons on our GoCenter journey. By telling that story, we can explain our original reasoning, share what we learned, and suggest better practices for creating Go modules for the future.

Transcript

1. Building a central Go modules repository: GoCenter’s back to the future. @jfrog @ankushchadha111 GopherCon 2019 Lightning Talk Ankush Chadha
2. About me • Dev Manager, Community & Partner Engineering team • Love solving devops enablement problems @jfrog @ankushchadha111
3. We Golang @jfrog @ankushchadha111
4. go modules @jfrog @ankushchadha111
5. reproducible builds @jfrog @ankushchadha111
6. Use go modules correctly @jfrog @ankushchadha111
7. @jfrog @ankushchadha111
8. Source of immutable dependencies @jfrog @ankushchadha111
9. https://gocenter.io @jfrog @ankushchadha111
10. Projects that adopted go modules @jfrog @ankushchadha111
11. @jfrog @ankushchadha111
12. Projects that haven’t adopted go modules yet @jfrog @ankushchadha111
13. go mod init go mod tidy @jfrog @ankushchadha111
14. go mod tidy @jfrog @ankushchadha111
15. @jfrog @ankushchadha111
16. desired interoperability between Go Modules Mirror go mod init @jfrog @ankushchadha111
17. @jfrog @ankushchadha111
18. Best Practices • Use populated go.mod file • Avoid pseudo-versions • Tag release, follow semver @jfrog @ankushchadha111
19. @jfrog @ankushchadha111 Thank you