Kanai - Back-end Engineer (with Go) - Eureka, inc. - Thank you for the opportunity to talk!! - This talk is.. - My first Go presentation - Talking about Go in English - Contribute to projects related to Go twitter: @rennnosuke_rk GitHub: rennnosuke
started contributing to OSS in Oct. 2021 - Our team found out the Go ORM library we use had some bugs - So we started fixing them (including me) - Some members have already contributed to OSS before - So I was able to get my contribution reviewed by them beforehand - I was able to get some bugs fixed and merged - Go conference 2022 Spring had just started to look for speakers
I continue to contribute to OSS? - I continued to contribute to OSS after my first contribution - OSS is supported by the contributions of many people - As a developer, I also wanted to contribute to OSS at least once
I continue to contribute to OSS? - I continued to contribute to OSS after my first contribution - OSS is supported by the contributions of many people - As a developer, I also wanted to contribute to OSS at least once - Fun - People in OSS help us to solve problems - I can fix OSS more easily - Since I can fix things myself, I don't need to wait for a new OSS update Actually…
about… - Feeling pressure - What if I'm wrong? - What if I'm causing trouble? - Not knowing something… - What to contribute - How to contribute - Language (English) - Communication - Available time - etc… The Go gopher was designed by Renée French.
🚀 - The smaller the contribution, the smaller the amount of trouble - You can learn about contributing to OSS - Contribution is not only about fixing code but also… - Documentation - Important - https://opensourcesurvey.org/2017 - Reporting issues - Discussion - Operating projects - No problem to contribute without complex & large code
mentor 👨💻 - It’s a better way to be taught about OSS projects you want to contribute to - You’ll be able to get pretty good start - Share and discuss issues of OSS project you are interested - Pair program and review - Asking about contribution process Where are they? - In your office - Tech organizations you know - SNS
- fix document (via GitHub) - Go repository is following: https://go.googlesource.com/go - You need to prepare: - Google account to contribute - Sign and submit a CLA (Contributor License Agreement) - You can get code reviews on both Gerrit and GitHub - https://go.dev/doc/contribute
- fix code (via Gerrit) - You can use `git-codereview` - Easy to push code while following Go contribution conventions - git codereview change - git codereview mail - You can get code reviews on Gerrit only
- fix code (via Gitea) - ORM library - You can contribute in the same way as GitHub - Differences in project culture… - Contribution guide: https://gitea.com/xorm/xorm/src/branch/master/ CONTRIBUTING.md - You can create issues/pull requests casually
in golang/go - e.g. When I just want to contribute to golang/go… - Search - label:NeedsFix -commenter:gopherbot - NeedsFix: the issue is fully understood and code can be written to fix it - https://go.dev/doc/contribute#check_tracker - gopherbot: sync Gerrit repo status - https://go.dev/doc/contribute#sending_a_change_github - If there’s no gopherbot comment, usually the issue is not fixed yet - Try new features & related documents - A lot of points you can fix
got from contributing to OSS - Get to know the project better - Improved skills in contributing to OSS itself - Your favorite OSS has more problems than you think - Let’s contribute to OSS!
sat
shonansurvivors
shigashiyama
puhitaku
fujiwara3
kasada
ytaka23
grimoh
sadonosake
asflash8
tamaiyutaro
jnunemaker
lauravandoore
jonrohan
panda_program
mongodb
csswizardry
ufuk
tammyeverts
sergeychernyshev
kneath
lynnandtonic
sugarenia
