Re: [discuss] So what does Gerrit actually get us, anyway?
toggle quoted messageShow quoted text
Valentine, I think your comments are quite accurate.
I know the CLA process has been a major blocker for contribution, and that is not a Gerrit thing per-say, but more of a process issue. I think Vicky and I finally got the CCLA that CloudOps signed a YEAR ago working its way through the system. So, I would agree that this is not a knock against Gerrit.
That said, I think your comment that "In a nutshell, Gerrit is (a bit clunky) code review tool which also does
code hosting, Github is code hosting tool which also does review." is very accurate. The one thing that Gerrit does do very well is gating commits into the main line code. The rules that can be defined around review and validation of PRs is absolutely an area were Gerrit offers a good deal of flexibility. So in Gerrit the reviews and PRs are the first class objects, while in Github, the code is the first class object.
So I guess the question comes back to, is the +2 feature that Gerrit offers a critical feature? Are the strengths of Gerrit really what the community needs?
One of the reasons that the grand majority of open source projects run on Github is because it is easy. It is easy for users to learn the code. It is easy for users to fix documentation issues. It is easy for users to get familiar with the code to then consider becoming an actual code contributor.
If I am a user of TF and I want to dig into some code, I have to do the following:
- Find review.opencontrail.org (through some documentation probably, searching in google wont find it).
- There is no mention of repositories there, you have to figure out that the code is under "Projects".
- But clicking Projects doesn't do anything, oh wait, it made a "List" menu option appear.
- Click the "List" menu option.
- Click on one of the repos. Ok, I can clone it, but where is the code? Where is a README to give me context of what I am looking at.
- Ok, there is no way to get to the code from this screen, lets start over and see if I can find the code.
- Click, click, click, ... oh, what is the 'gitweb' thing on the right, click.
- Ok, great now I see some stuff relevant to this project, but where is the code?
- After much trial and error they are likely to FINALLY find the 'tree' link which actually points them to the code.
- Ok, lets read the README file to make sure I am in the right place. Oh wait, there is not MD renderer, so I have to know how to read Markdown.
- Ok, lets check the code. OMG, my eyes, there isn't even syntax highlighting. Who can read this?
- Why am I here again? Maybe I will just tell my boss that I looked at TF and its not right for us.
VS on Github:
- Google for a project. Oh look, the code.
- A README introduces me to the project, this looks right.
- Now I can browse the code and figure out what is going on.
- Let me link the line of code that is the problem to my coworker so they can have a look.
What is important for the users and the community? I think the visibility and usability of the tooling we are expecting our users and contributors to use is extremely important.
Have you ever seen a Gerrit repo show up in a google search? Nope, because even google gave up looking for the code in that mess...
My two cents as an open source contributor of many projects...
On Tue, Jun 11, 2019 at 3:08 AM Valentine Sinitsyn <valentine.sinitsyn@...> wrote: