[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-community
Subject:    Re: [kde-community] Write our own pull request bot?
From:       Laszlo Papp <lpapp () kde ! org>
Date:       2015-09-19 17:42:21
Message-ID: CAOMwXhOMNGZH-eqBxb_miKZ7-4cAtq2JwStN-vbn1P2hBRk5aw () mail ! gmail ! com
[Download RAW message or body]

On Sat, Sep 19, 2015 at 6:37 PM, Martin Klapetek
<martin.klapetek@gmail.com> wrote:
> On Sat, Sep 19, 2015 at 1:28 PM, Sune Vuorela <nospam@vuorela.dk> wrote:
>>
>>
>> What happens if contributor doesn't follows? How do I as a reviewer know
>> why the contributor doesn't follow on? How can I reach them?
>>
>> No. let's just say no to pull requests.
>
>
> Same thing as when someone emails you a patch and you reply and ask
> questions and never hear back. That happens quite often already.

Sure, but why would increase this situation further on?

I agree with everything that Sune wrote. Reaching them might be
particularly important when changing license just for one of those.
There could be numerous other valid examples.

Why put energy into making sure that they can diverge from the normal
workflow rather than putting energy on making sure that the workflow
is known and easy to get?

There used to be life before github, too. This is exactly the vendor
lock-in, when some people can no longer breat without it for such
simple things.

>
> Cheers
> --
> Martin Klapetek | KDE Developer
>
> _______________________________________________
> kde-community mailing list
> kde-community@kde.org
> https://mail.kde.org/mailman/listinfo/kde-community
_______________________________________________
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
[prev in list] [next in list] [prev in thread] [next in thread]