From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: "Felipe Contreras" <felipe.contreras@gmail.com>,
git@vger.kernel.org, git-fc@googlegroups.com,
"Richard Hansen" <rhansen@bbn.com>,
"Torsten Bögershausen" <tboegi@web.de>,
"Antoine Pelisse" <apelisse@gmail.com>,
"Christophe Simonis" <christophe@kn.gl>,
"Dusty Phillips" <dusty@linux.ca>, "Jeff King" <peff@peff.net>,
"John Keeping" <john@keeping.me.uk>
Subject: Re: Should git-remote-hg/bzr be part of the core?
Date: Mon, 12 May 2014 12:35:05 +0200 [thread overview]
Message-ID: <1399890905.11985.51.camel@seahawk> (raw)
In-Reply-To: <53709788.2050201@alum.mit.edu>
Michael,
Thank you for writing this, I have to see I agree completely. As a
mostly lurker on this list, I tend to skip any thread Felipe is
participating in, as it tends to quickly spiral out of control.
This is also the main reason for me not to actively participate a bit
more, I prefer reasonable discussions over fighting.
On ma, 2014-05-12 at 11:42 +0200, Michael Haggerty wrote:
> On 05/12/2014 01:34 AM, Felipe Contreras wrote:
> > Recently Junio said he was willing to hear the opinion of other people
> > regarding the move from contrib to the core[1]. This move is already
> > under way, but suddenly Junio changed his mind.
>
> I agree with Junio. There are good technical arguments for and against
> moving git-remote-hg out of contrib. Those arguments were discussed at
> length and I think their weight is on the side of not moving it. But
> there are two other (in my opinion, stronger) reasons for keeping
> git-remote-hg out of the core:
>
> 1. That subproject has not been maintained to the standards of the Git
> project; specifically, Git project standards include good commit
> messages and a willingness to engage with the community on a friendly
> and constructive way and to welcome feedback. Because of your
> confrontational and nit-picking style, Felipe, many people who have
> tried to help you improve your work are rebuffed and end up giving up
> out of frustration or exhaustion. Because of this, your commits do not
> benefit from the usual amount of help from the community and therefore
> their quality is not as high as required for commits to core Git.
>
> 2. Moving git-remote-hg into the core would require even *more* of your
> presence on the Git mailing list. But your very presence is detrimental
> to the rest of the community. You insult and frustrate people who are
> trying to help you. You attribute malign motivations to people who are
> trying to be scrupulously fair. You string out enormous threads of
> nit-picking, legalistic argumentativeness that have little to do with
> the real issues at hand.
>
> The last big "Felipe eruption" in the summer of 2013 caused an enormous
> amount of strife, wasted an inordinate amount of time of other community
> members, and caused at least one valued contributor to temporarily
> rage-quit the community. That episode only ended when Junio asked you
> to leave the community [1], which, thankfully, you did for a while.
>
> After you left, the atmosphere of the mailing list soon returned to its
> usual friendly, collegial, and efficient norm.
>
> Recently you returned to the mailing list. In my opinion everybody on
> the list, including especially Junio, interacted with you in a very
> polite and businesslike manner. I believe you were given an honest
> chance at a fresh start in the community. I wish you had taken it. The
> Git project could really benefit from the help of a skilled and
> energetic developer like you!
>
> But it didn't take long before you started the same theatrics again.
> And now again, dealing with your caustic attitude is wasting an order of
> magnitude more time of the other core developers than your contributions
> could possibly bring in benefits.
>
> For me, the conclusion is unfortunate but clear: Felipe Contreras is (by
> far) a net liability to the Git project. Specifically:
>
> * The Git project will progress faster without you because the other
> contributors will have to waste less time dealing with your antics.
>
> * The Git community will grow faster without you, because your presence
> will not cause existing contributors to withdraw and dissuade new
> contributors from joining.
>
> * The community will be a lot more pleasant without you.
>
> Therefore, I am happy that you have apparently decided to split
> git-remote-hg into a separate project. I wish you success with the
> project and I see no reason that it shouldn't continue to be successful.
> But I am glad that I will not have to interact with you anymore.
>
> > [...] Does it make sense to you that
> > you get thrown in jail for a crime you haven't committed merely because
> > someone thinks it's likely you will?
>
> Being the leader of your own valuable open-source project is nothing
> like jail. It is an opportunity for you to shine in an environment that
> is more suited to your personality.
>
> > Given the huge amount of work I've put in these remote helpers, and the
> > fact that Junio said since day 1 he wanted these in the core[5] (and I
> > was operating under that assumption), I think the demotion back to the
> > contrib area (and therefore out-of-tree) should be made carefully, and
> > not from one day to he next as it happened.
>
> None of the work was wasted. git-remote-hg can live on.
>
> This email is written in sorrow, not in anger. Felipe, you seem to have
> so much potential. If you would put as much effort in conducting social
> interactions as you do in coding, the whole balance would change
> entirely, and any software project would be happy to have you. With all
> my heart I truly wish you the best in your future endeavors.
>
> Michael
>
> [1] http://article.gmane.org/gmane.comp.version-control.git/227750
>
--
Dennis Kaarsemaker
http://www.kaarsemaker.net
next prev parent reply other threads:[~2014-05-12 10:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 23:34 Should git-remote-hg/bzr be part of the core? Felipe Contreras
[not found] ` <CA+55aFwf9iAKxbvdPV9Up_T709KwBXJWW4g-F829CRQP4YkivQ@mail.gmail.com>
2014-05-12 7:42 ` Felipe Contreras
2014-05-12 8:12 ` Felipe Contreras
2014-05-12 10:28 ` Stefan Beller
2014-05-12 12:05 ` Felipe Contreras
2014-05-12 9:42 ` Michael Haggerty
2014-05-12 10:35 ` Dennis Kaarsemaker [this message]
2014-05-12 10:37 ` Felipe Contreras
2014-05-12 12:05 ` Michael Haggerty
2014-05-12 12:29 ` Felipe Contreras
2014-05-12 13:12 ` David Kastrup
2014-05-12 17:12 ` Felipe Contreras
2014-05-12 13:43 ` Michael Haggerty
2014-05-12 17:13 ` Felipe Contreras
2014-05-12 11:00 ` David Kastrup
[not found] ` <CAHVLzcmqdkf4fMTok+HsXcDOQ5Oz2QdZti3FuzgBUa2T6AWnfA@mail.gmail.com>
2014-05-12 12:48 ` Felipe Contreras
2014-05-12 13:45 ` Paolo Ciarrocchi
2014-05-12 16:13 ` Stefan Beller
2014-05-12 16:40 ` Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1399890905.11985.51.camel@seahawk \
--to=dennis@kaarsemaker.net \
--cc=apelisse@gmail.com \
--cc=christophe@kn.gl \
--cc=dusty@linux.ca \
--cc=felipe.contreras@gmail.com \
--cc=git-fc@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.net \
--cc=rhansen@bbn.com \
--cc=tboegi@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.