Re: On the need to move to a merge request workflow
On Thu, Mar 26, 2020 at 11:22:11 -0300, Daniel Henrique Barboza wrote:
On 3/26/20 10:10 AM, Peter Krempa wrote:
> On Fri, Mar 06, 2020 at 11:44:07 +0000, Daniel Berrange wrote:
> > We've discussed the idea of replacing our mailing list review workflow
with
> > a merge request workflow in various places, over the last 6 months or so,
>
> One thing I feel the need to voice until this is taken in place is a
> matter of personal preference:
>
> I severely dislike the merge request workflow and I'll be severely
> disappointed once we switch over to it.
>
Thank you for your opinion!
I'm not thrilled about it either, but I believe that once we get
used to the
new workflow we'll learn to appreciate all the possibilities a GitForge tool
brings to the table.
IMO the price to pay for the few good features is too high, but again
that's very subjective in my opinion as I can't counter with credible
technical points against it.
That says that the problems outlined are real, but the replacement is in
no way a clear win either. It solves some of the pain points of the
current process, but it makes the very few, but important things such as
review way more painful.
The unfortunate part is, that I don't feel that the tradeoff is worth
it. And yes, that's an egoistic belief as I worked around the quirks of
the existing process already.
One point that I already made earlier in the thread: having to track
discussions
in two places (mailing list and Gitlab) will be annoying. I understand that the
idea is that we'll organically move move all possible discussions to Gitlab.
I'd rather make it a blunt and quick directive: once we moved to Gitlab, mailing
list is completely discouraged unless it's a topic that needs to be discussed
together with the QEMU or any other mailing list. If we leave to personal
preference we'll have people posting stuff everywhere.
I agree that there should be one place only for discussions. I feel
though that using gitlab for discussions will also be a severe
regression in usability. Again this is from a grumpy guy who likes the
old-school.