For the Love of Go: How to Contribute Really

on YouTube ↗25m

" summary

Implements a new test logging API called T output, navigating Gerrit-style reviews via Garrett, local toolchain pitfalls and path hacks, and the proposal board instead of the 9k-plus issue swamp (over 9,000 open issues). Describes a prototype that gets scooped, a later two-part refactor that lands after ~3 months and dozens of review rounds (merged, briefly reverted, fixed and merged again), ~500 lines changed and ~86 review comments.

AI-written summary · about

" chapters (12)

1. 0:00Introduction
2. 1:23Go contributions and issue tracker
3. 3:11Local setup and early wins
4. 6:04Go dev group and toolchain
5. 8:13T output proposal and setbacks
6. 10:44Being scooped and refocusing
7. 12:52Code review with Garrett
8. 15:00Final push for T output
9. 16:49Review comments and code freeze
10. 19:03Merging struggles and recovery
11. 20:31Lessons and personal growth
12. 23:01Future outlook and closing

" related talks

• 32mContributing to Open Source: A GuidePaul Ganssle · PyData NYC 2018
• 43m'ProTalking' Your Way into Open SourceMichelle Sanver · PHP UK Conference 2014
• 33mCode review for Open SourceAlex Gaynor · Open Source Bridge 2014
• 16mMaintaining an OSS Project (Babel)Henry Zhu · JSConf EU 2017
• 32mYour First Open-Source ContributionRachael Wright Munn · RubyConf 2021
• 21mÜber Tech Lead On Code ReviAlex Martelli · OSCON 2008
• 35mTending Your Open Source GardenBrandon Keepers · Red Dot Ruby Conference 2014
• 28mGet yourself heard in Open SourceEmma Karayiannis · Frontend United 2016