here is an example of exactly what *not* to do if you want people to fix bugs in your open-source project:
Conversation
you lost me at βDecide on a single Google Account you will be using to contribute to Go.β
5
5
161
then you lost me again at βdownload our weird custom git subcommandβ
4
136
Replying to
This is how you submit Gerrit change requests with git, no commit access needed:
git push upstream HEAD:refs/for/master
Most projects will enforce having a Change-Id in commit message so you need the tiny hook to generate them. Need it to do revisions to your commits anyway.
1
Something to be said for Gerrit having working code review with rebase support, not needing to use another social media site, and not needing the weird GitHub model where you have both your local clone with both 'origin' and 'upstream' remotes and a rotting remote fork on GitHub.
Replying to
sure, but on the other hand, itβs different from the thing i use for my dayjob, so i donβt want to do it
2
1
Replying to
I think avoiding writing Go is a good enough reason.
It's worth spending 15 minutes trying Gerrit simply so that you can properly despise GitHub and the fact that you have to use it for almost everything and lose a lot of potential contributors by not hosting projects on it.
2