[Kde-scm-interest] Git roadmap

[Johannes Sixt]

Thiago Macieira schrieb:
> Johannes Sixt wrote:
>> Why do you think that dashbot would not see your changes? You would have
>> published them in the public repository anyway. I'd even go as far as to
>> say that *before* you ask the libksane maintainer to pull your fix, you
>> ask dashbot to pull them and act as the peer reviewer.
> 
> That sounds like a maintenance nightmare: if dashbot starts merging any 
> and all branches on request, someone will have to "clean up the mess" 
> every now and then. Different people would be working on the same fix 
> because it hasn't made upstream yet. 

A human who merges all branches on request can also clean up the mess behind 
himself. A bot can wait until the fix has made its way upstream.

> That could be a good thing for the maintainer to be able to choose the 
> best fix, but it's also a waste of effort in a project lacking manpower 
> already.

I agree that wasting half an hour for a fix that someone else may have 
published, too, is not thrilling.

But how often does it happen that different people spend hours (or even 
days) on the same problem? I think that task are reasonably separated among 
the relatively few full-timers and regular contributors that this does not 
happen. And if it does happen among the mass of occasional contributors it 
is an *advantage* to be able ask for peer review before the best solution is 
picked.

> But the big problem is dashbot being a bot: not all requested 
> merges will work and so it'll have to reset to a known state, etc.

Big problem? Hey, it's a *bot*, a *machine*. It's *not* sadistic, if you 
choose to ignore it pleading for an _immediate_ fix until the upstream 
maintainer is back from vacation.

-- Hannes