From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: "Etienne Prud'homme" Newsgroups: gmane.emacs.devel Subject: Re: comparing code on different branches Date: Wed, 5 Jul 2017 15:56:46 -0400 Message-ID: References: <9A9EF0AB-8FD3-44C9-AAE8-ACACDEC69059@gmail.com> <87r2xw21eo.fsf@jane> <874lurbf9i.fsf@x230.lts> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="94eb2c0bd7dc6a42e905539766f1" X-Trace: blaine.gmane.org 1499284629 32034 195.159.176.226 (5 Jul 2017 19:57:09 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 5 Jul 2017 19:57:09 +0000 (UTC) Cc: Jonas Bernoulli , Richard Stallman , jwiegley@gmail.com, Jean-Christophe Helary , emacs-devel , Yuri Khan To: Yann Hodique Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 05 21:57:04 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dSqPw-0007hX-GM for ged-emacs-devel@m.gmane.org; Wed, 05 Jul 2017 21:56:56 +0200 Original-Received: from localhost ([::1]:47850 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dSqQ1-0003RQ-PU for ged-emacs-devel@m.gmane.org; Wed, 05 Jul 2017 15:57:01 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50946) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dSqPp-0003RA-GY for emacs-devel@gnu.org; Wed, 05 Jul 2017 15:56:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dSqPo-0002UU-DC for emacs-devel@gnu.org; Wed, 05 Jul 2017 15:56:49 -0400 Original-Received: from mail-pg0-x22c.google.com ([2607:f8b0:400e:c05::22c]:36495) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dSqPo-0002Th-3B; Wed, 05 Jul 2017 15:56:48 -0400 Original-Received: by mail-pg0-x22c.google.com with SMTP id u62so129166235pgb.3; Wed, 05 Jul 2017 12:56:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=K4AobckAd/TyzLtLDp9I2ZEW4XB/HCpBm6POb8aTLtg=; b=R7Zg3ocsUVkT3nz+veA9QisKry+efD33hpkiabEnzG6pY+vi1rVstSZM599kcZXuNK O3WNEad0+Dns5p1wwf9jok2Gc8uuipPN1JQ9qkllA6vC14yFzzNraTxo6lUlvLxGQinx YCc2yvdRaB6iluqZ5vs6Ao/SyavlpVW9PpLuC0OoBipZ9Fs7Y0K5phJquO4DjFWXp/Zi y21UyJElNI1gRsr2czOgaNnZ3udBb721SC+czhbszLil8z/x7zN13wI+h5qAPIfzef7S /spH5VfrfBakijU4hwIFc/gVwIWrFKGP2gK/jU36WDtpEavk1N2eReRvkpKgE9ds25zr O4Dw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=K4AobckAd/TyzLtLDp9I2ZEW4XB/HCpBm6POb8aTLtg=; b=S9PaqSkUh3eW3yuyE/cUEiVZdStcc7HtQkQfFcqNVA7fQe3Zn3vZhnRztEkuLqRDQP +2fn5Mg1t9OaWwywEGdwDC30DNsgh5sVm2TLUYUvCUeFhFN9f8wPCWPAotrp6Q0reFMF LS5dbDezuWIiEzknquOSfhWSzQpBJkUcEOikZgGYQ3L/T6b0q5Jq9KFm/zaitQnTiCeC loUOXY97GPNBSHzQzNNdu8cNRyOjD3akgtcmJusMndJoE3ENXCgavwmeRndbFfG+L5nd t2VJFeJY1fBTaF0gxv1od/oAwFgpVrgL8hEAhBage0dKjS1xGABpTBz9Rmva07DiRa8i hIgQ== X-Gm-Message-State: AIVw11143RCufjWEgxIBkRSMwtdzyBXT2I0ahLM68vqwZvADWM4Gyv56 ScF9cdaBsC0o5RknVoLw7nAGvBXWmQ== X-Received: by 10.98.69.76 with SMTP id s73mr21711348pfa.94.1499284606959; Wed, 05 Jul 2017 12:56:46 -0700 (PDT) Original-Received: by 10.100.160.194 with HTTP; Wed, 5 Jul 2017 12:56:46 -0700 (PDT) Original-Received: by 10.100.160.194 with HTTP; Wed, 5 Jul 2017 12:56:46 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:400e:c05::22c X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:216194 Archived-At: --94eb2c0bd7dc6a42e905539766f1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks for the comments. I wasn't aware of the view of current contributors. Last time asked if a project could be included in elpa (with paper work), it was not a nice experience. I'm not even mentionning non conformance to GPL in some MELPA packages (using a license weak to no copyleft license). -- Etienne Le 2017-07-05 11:56, "Yann Hodique" wrote : >>>>> "Etienne" =3D=3D Etienne Prud=E2=80=99homme writes: > Richard Stallman 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=E2=80=99m all for it. Could we make an of= ficial > 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=E2=80= =99s > 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 --94eb2c0bd7dc6a42e905539766f1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks for th= e comments.=C2=A0 I wasn't aware of the view of current contributors.

Last time asked if a project cou= ld be included in elpa (with paper work), it was not a nice experience.
=

I'm not even mentionning non= conformance to GPL in some MELPA packages (using a license weak to no copy= left license).

--
Etienne


Le 2017-07-05 11:56, "Yann Hodique" <yann.hodique@gmail.com> wrote :
= >>>>> "Etienne" =3D=3D Etienne Prud=E2=80=99homme = <e.e.f.prudhomme@gmail.com<= /a>> 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=E2=80=99m 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).=C2=A0 I see that the= re=E2=80=99s
> more than 8k commits on their repository.=C2=A0 Also worth noting the = project
> had 200 contributors.=C2=A0 I seriously wonder if hunting down for the= m would
> be easier than writing it from scratch!

As a former Magit maintainer myself, I would really hate to see much<= br> 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
=C2=A0 if I'm using a total of less than 15 lines changed (even just mo= ved
=C2=A0 around) as a naive threshold.

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

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

- the `dash' and `async' dependencies are already in ELPA, leaving = only
=C2=A0 packages closely related to `magit' (mostly by the same authors)= to be
=C2=A0 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 bee= n
done already.
CC-ing Jonas for a more current perspective.

Thanks

Yann.

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

=C2=A0 -- DUKE LETO ATREIDES

--94eb2c0bd7dc6a42e905539766f1--