This is about https://go.dev/doc/contribute#review
As long time Open Source contributor and heavy GitHub user, I struggle with the contribution process for Go because of the Gerrit workflow and UI. The Gerrit UI and process is very different from GitHub. For example, I got patches stuck for weeks just because the answers to reviews I had written were just drafts and not sent to the reviewer.
So it would very helpful to add:
- some basic tutorial for the contributor point of view, with screenshots:
- how to reply to comment
- the workflow state schema
- what to do when a patch in "Your turn" state
- links to a Gerrit UI onboarding
This presentation seems to have good in-depth content, but goes too deep for someone who just want to send one patch to the Go project.
https://docs.google.com/presentation/d/1C73UgQdzZDw0gzpaEqIC6SPujZJhqamyqO1XOHjH-uk/edit#slide=id.g4d6c16487b_31_60
This is about https://go.dev/doc/contribute#review
As long time Open Source contributor and heavy GitHub user, I struggle with the contribution process for Go because of the Gerrit workflow and UI. The Gerrit UI and process is very different from GitHub. For example, I got patches stuck for weeks just because the answers to reviews I had written were just drafts and not sent to the reviewer.
So it would very helpful to add:
This presentation seems to have good in-depth content, but goes too deep for someone who just want to send one patch to the Go project.
https://docs.google.com/presentation/d/1C73UgQdzZDw0gzpaEqIC6SPujZJhqamyqO1XOHjH-uk/edit#slide=id.g4d6c16487b_31_60