unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yann Hodique <yann.hodique@gmail.com>
To: "Etienne Prud’homme" <e.e.f.prudhomme@gmail.com>
Cc: Jonas Bernoulli <jonas@bernoul.li>,
	Richard Stallman <rms@gnu.org>,
	jwiegley@gmail.com, jean.christophe.helary@gmail.com,
	Yuri Khan <yuri.v.khan@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: comparing code on different branches
Date: Wed, 05 Jul 2017 08:55:56 -0700	[thread overview]
Message-ID: <y9gla84ix4hf.fsf@promb-1s-dhcp228.eng.vmware.com> (raw)
In-Reply-To: <874lurbf9i.fsf@x230.lts> ("Etienne \=\?utf-8\?Q\?Prud\=E2\=80\=99ho\?\= \=\?utf-8\?Q\?mme\=22's\?\= message of "Wed, 05 Jul 2017 01:54:01 -0400")

>>>>> "Etienne" == Etienne Prud’homme <e.e.f.prudhomme@gmail.com> writes:

> Richard Stallman <rms@gnu.org> writes:
>> I wish someone would write a package comparable to Magit that
>> we could get legal papers for and include it in Emacs.

> Although I really like Magit, I’m all for it. Could we make an official
> project with GNU Emacs contributors?

> I could try to contribute to some parts of it.

> Writing it alone would be insane (I need to eat).  I see that there’s
> more than 8k commits on their repository.  Also worth noting the project
> had 200 contributors.  I seriously wonder if hunting down for them would
> be easier than writing it from scratch!

As a former Magit maintainer myself, I would really hate to see much
effort going into rewriting it instead of improving it :)

A few more datapoints, for what it's worth:

- at most ~100 contributors fall in the non-trivial contribution bucket
  if I'm using a total of less than 15 lines changed (even just moved
  around) as a naive threshold.

- probably more that half of the remaining individual contributions (the
  1- or 2-commits bucket) can be either very easily rewritten or have
  already been nuked from the current state of Magit. Not that we
  shouldn't try to collect the paperwork for those, but I suspect the
  occasional failure would be highly manageable.
  So that leaves probably 40 to 50 authors that really need to agree
  before it gets more complicated (if my overall understanding of the
  process is correct).

- eyeballing the top ~20 contributors, it seems to me the vast majority
  of us already have code in Emacs proper, so I assume most of us are
  not opposed to the idea, and have similar paperwork in place.

- the `dash' and `async' dependencies are already in ELPA, leaving only
  packages closely related to `magit' (mostly by the same authors) to be
  taken care of.

So while I'm not trying to diminish the effort needed to get the
paperwork in order (actually the task seems pretty daunting to me :)),
I think it's worth at least asking the question, if that hasn't been
done already.
CC-ing Jonas for a more current perspective.

Thanks

Yann.

-- 
What is each man but a memory for those who follow?

  -- DUKE LETO ATREIDES



  reply	other threads:[~2017-07-05 15:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04  0:53 comparing code on different branches Jean-Christophe Helary
2017-07-04  0:57 ` John Wiegley
2017-07-04  1:14   ` Jean-Christophe Helary
2017-07-04  5:17   ` Tino Calancha
2017-07-04  5:53   ` Marcin Borkowski
2017-07-04  9:30     ` Yuri Khan
2017-07-04 23:05       ` Richard Stallman
2017-07-04 23:48         ` Jean-Christophe Helary
2017-07-05 22:59           ` Richard Stallman
2017-07-05  5:54         ` Etienne Prud’homme
2017-07-05 15:55           ` Yann Hodique [this message]
2017-07-05 16:07             ` Kaushal Modi
2017-07-05 19:56             ` Etienne Prud'homme
2017-07-06 15:58               ` Richard Stallman
2017-07-13 21:48                 ` Etienne Prud’homme
2017-07-04 17:51 ` Stephen Leake

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=y9gla84ix4hf.fsf@promb-1s-dhcp228.eng.vmware.com \
    --to=yann.hodique@gmail.com \
    --cc=e.e.f.prudhomme@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=jean.christophe.helary@gmail.com \
    --cc=jonas@bernoul.li \
    --cc=jwiegley@gmail.com \
    --cc=rms@gnu.org \
    --cc=yuri.v.khan@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).