doc: contribute.html is long and wordy #17802
Comments
|
Yes please. Anything we can do to make the barrier to entry lower will help a lot. We lose a lot of talented (and thus busy) potential contributors at step 1. |
|
It's also longer than it could be because there are several "git aficionados" and "git terms" bits. Perhaps you should make a very short guide for newbies, ignoring all git internals, and a separate advanced information page for those who are already familiar with |
quentinmit
added
Documentation
|
No reason to tie this to Go 1.8. We can backport the docs later too, so it can go live on the website unrelated to the Go release cycle. |
|
CL https://golang.org/cl/36626 mentions this issue. |
Updates #17802 Change-Id: I65ea0f4cde973604c04051e7eb25d12e4facecd3 Reviewed-on: https://go-review.googlesource.com/36626 Reviewed-by: Ian Lance Taylor <[email protected]> Reviewed-by: Chris Broadfoot <[email protected]>
…to a guide Updates #17802 Change-Id: I65ea0f4cde973604c04051e7eb25d12e4facecd3 Reviewed-on: https://go-review.googlesource.com/36626 Reviewed-by: Ian Lance Taylor <[email protected]> Reviewed-by: Chris Broadfoot <[email protected]> Reviewed-on: https://go-review.googlesource.com/38312
|
CL https://golang.org/cl/45078 mentions this issue. |
Updates golang/go#17802 Change-Id: Ieb4be41039d414a3ba6766d98ed95a6154f964f4 Reviewed-on: https://go-review.googlesource.com/45078 Reviewed-by: Steve Francia <[email protected]>
|
CL https://golang.org/cl/45079 mentions this issue. |
Updates golang/go#17802 Change-Id: I70d30c5ff12837d51d13b5ca7e73be96eb535286 Reviewed-on: https://go-review.googlesource.com/45079 Reviewed-by: Steve Francia <[email protected]>
|
CL https://golang.org/cl/45080 mentions this issue. |
Updates golang/go#17802 Change-Id: Ic5278804203029926dd5a26e571f79aaafb13110 Reviewed-on: https://go-review.googlesource.com/45080 Reviewed-by: Steve Francia <[email protected]>
|
CL https://golang.org/cl/45082 mentions this issue. |
…eckout Updates golang/go#17802 Change-Id: I8eeae42f395dee4eedd17114f10bb56536783089 Reviewed-on: https://go-review.googlesource.com/45082 Reviewed-by: Steve Francia <[email protected]>
|
CL https://golang.org/cl/45083 mentions this issue. |
Updates golang/go#17802 Change-Id: I2b5473bc0539a760c26889497a301808deb5e5ae Reviewed-on: https://go-review.googlesource.com/45083 Reviewed-by: Steve Francia <[email protected]>
|
CL https://golang.org/cl/45084 mentions this issue. |
|
Bumping this to Go 1.10 for now. The recent reorganization helped. The |
|
CL https://golang.org/cl/45652 mentions this issue. |
|
Actually, we can drop the note in Go 1.9. |
Tracking bug for making the contribution process seem less intimidating, forked from #17794.
Observations:
Maybe we need a high-level summary at the top showing the brief steps, with links to more info, rather than making users read a book first.
Also, I had an idea to write a go-gettable tool to walk people through the contribution process step-by-step, inspecting their httpcookies (for Gerrit), CLA state, git config, git-codereview, etc, and telling them what to do next. I want the instructions for contributors to just be:
And then the tool would say what needs to be done next.
/cc @quentinmit @robmccoll
The text was updated successfully, but these errors were encountered: