Re: [discuss] So what does Gerrit actually get us, anyway?
toggle quoted messageShow quoted text
Sukhdev, we are not looking for a philosophical discussion. We are trying to understand if Gerrit is really the best solution for what the community needs.
Another discussion for over beers, but the fact that the boat is not being rocked may be part of why, a year later, the community is still struggling to work with the project.
Chief Technology Officer
Ha ha. You want to drag me into philosophical discussion:-)
Short answer- this is how the world was when Contrail started.
So, the short answer is - "that is the way it has been done in the past"
Gerrit is not known to being user friendly, really? Says who? I would entertain that debate over a beer, not here :-):-)
I do not want to engage in to philosophical discussion. We all have certain religions about tools, programming languages, development methodologies. So, let’s leave it at that.
Let’s not rock the boat. If someone has extra cycles to spare, I can suggest several improvements that we can make that will make TF great.
From: dev@... on behalf of Will Stevens <wstevens@...>
Sent: Monday, June 10, 2019 4:53 PM
Subject: Re: [TF Dev] [discuss] So what does Gerrit actually get us, anyway?
The motivation is to understand if there is a real reason we MUST use Gerrit, or if it was chosen simply because "that is the way it has been done in the past". Gerrit is not known for being user friendly or intuitive for contributors, so what
are the roots that hold Gerrit in place as our standard? Are there alternatives which would better suit the communities needs going forward?
There may be many very good reasons for using Gerrit, but if there are not, it seems prudent to understand that now before we adopt it en masse.
That is my understanding of the motivation behind this question...
Join email@example.com to automatically receive all group messages.