On May 5, 2016 11:26 AM, "Arseniy Seroka" wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> I'm working with PR for more than 1,5 years. I saw maybe once that a
person completely lost his interest.
I just really didn't have time / intention to support what I was packaging
:D
>
> O
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I'm working with PR for more than 1,5 years. I saw maybe once that a person
completely lost his interest.
On 5 May 2016 12:13:45 GMT+03:00, zimbatm wrote:
>This paragraph in the article sums the problem pretty much:
>
>> What’s even more frustrati
This paragraph in the article sums the problem pretty much:
> What’s even more frustrating is that even though Jane provides feedback
quickly, often contributors lose interest and/or forget about taking their
Pull Requests the final step after initially contributing them. The
apparent triviality o
I've found this post insightful (disregard the title) about how to not be too
much of a stickler with new committers:
https://blog.spreedly.com/2014/06/24/merge-pull-request-considered-harmful/
Graham
> On May 4, 2016, at 6:26 AM, zimbatm wrote:
>
> Each contributor has his own motivations and
Nowadays probably almost everyone writes commit names that follow our rules.
So it's not so hard to ping somebody to fix the name for the beauty sake of
git's log.
--
Sincerely,
Arseniy Seroka
On 4 May 2016 14:26:45 zimbatm wrote:
Each contributor has his own motivations and every round w
On Wed, May 4, 2016 at 12:26 PM, zimbatm wrote:
> Each contributor has his own motivations and every round were we provide
> feedback is another one where we might lose the contributor. He might run
> out of energy, or have moved onto other things.
>
> Even after improving the CONTRIBUTING.md, nam
Each contributor has his own motivations and every round were we provide
feedback is another one where we might lose the contributor. He might run
out of energy, or have moved onto other things.
Even after improving the CONTRIBUTING.md, naming of commits is still a
really big friction to getting v
