git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Michael Haggerty <mhagger@alum.mit.edu>,
	Felipe Contreras <felipe.contreras@gmail.com>,
	git@vger.kernel.org, git-fc@googlegroups.com
Cc: "Richard Hansen" <rhansen@bbn.com>,
	"Torsten Bögershaus" <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 05:37:47 -0500	[thread overview]
Message-ID: <5370a47bee98c_139611a92fc29@nysa.notmuch> (raw)
In-Reply-To: <53709788.2050201@alum.mit.edu>

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.

Saying you agree with Junio is content-free. You have to say *why* you
agree.

You mention there are good technical arguments against the graduation of
the tools. Surely if you have analyzed those arguments enough to form an
opinion aligned with Junio's, it should be easy to provide a short
summary of those "good technical arguments". Can you do that?

> 1. That subproject has not been maintained to the standards of the Git
> project;

The quality of the subjproject has not been called into question, stop
taiting the discussion with red herrings.

> 2. Moving git-remote-hg into the core would require even *more* of your
> presence on the Git mailing list.

That's not true. I sent my patches at my own pace, it doesn't matter if
they are in contrib or in the core, I would have kept sending them at
the same pace. I have addressed all issues and responded to all
questions as if they were already part of the core, which is why they
have more quality than other tools already in the core. I only stopped
doing that when Junio changed the direction we had since day one.

Also a red herring.

> > [...] 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.

Don't be ridiculous. There is no out-of-tree tool that could possibly
compete in popularity against core tools.

If you think being out-of-tree is not a negative, lets throw out
git-archimport, git-quiltimport, git-p4, git-cvs, git-svn. Let us give
them an "opportunity to shine".

You know that those tools do better in the core, and you know
git-remote-hg/bzr would do better in the core. Don't act as if you
didn't.

> 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.

Let's see how sincere you are in your sentiment. I'll reply to you
personally about the points that I consider to be red herrings and ad
hominem attacks so we don't taint the dicussion. If you don't reply I'll
know you were not being sincere.

Cheers.

-- 
Felipe Contreras

  parent reply	other threads:[~2014-05-12 10:48 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
2014-05-12 10:37   ` Felipe Contreras [this message]
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=5370a47bee98c_139611a92fc29@nysa.notmuch \
    --to=felipe.contreras@gmail.com \
    --cc=apelisse@gmail.com \
    --cc=christophe@kn.gl \
    --cc=dusty@linux.ca \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).