From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Including ESS with Emacs Date: Mon, 26 Nov 2018 08:01:24 -0500 Message-ID: References: <875zwlfeme.fsf@gmail.com> <87o9adrsiv.fsf@gmail.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1543237190 16839 195.159.176.226 (26 Nov 2018 12:59:50 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 26 Nov 2018 12:59:50 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 26 13:59:46 2018 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 1gRGUL-0004FI-Nt for ged-emacs-devel@m.gmane.org; Mon, 26 Nov 2018 13:59:45 +0100 Original-Received: from localhost ([::1]:35831 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gRGWS-0005h4-DF for ged-emacs-devel@m.gmane.org; Mon, 26 Nov 2018 08:01:56 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55086) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gRGWH-0005gW-AU for emacs-devel@gnu.org; Mon, 26 Nov 2018 08:01:50 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gRGW7-0006O7-Qv for emacs-devel@gnu.org; Mon, 26 Nov 2018 08:01:45 -0500 Original-Received: from [195.159.176.226] (port=34248 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gRGW7-0006Mg-EJ for emacs-devel@gnu.org; Mon, 26 Nov 2018 08:01:35 -0500 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1gRGTv-0003TD-Bd for emacs-devel@gnu.org; Mon, 26 Nov 2018 13:59:19 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 67 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:MTqCCifnMwX016lmejsaC3o6adg= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 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:231390 Archived-At: I'm continuing this discussion off-list, Stefan Alex Branham writes: > On Sun 25 Nov 2018 at 10:45, Stefan Monnier wrote: > >>> We'd like to contribute ESS to the FSF so that it can become part of >>> Emacs. >> >> Yay! >> [ I think it'd be best to include it into GNU ELPA rather than into >> Emacs, tho. ] > > Right, I was including ELPA as "part of Emacs". We'd be completely happy > being in "core" Emacs or on ELPA, whatever the maintainers think is > best. > >> It should be all authors who contributed more than 15 lines-or-so of the >> current code. `git blame` can be a good starting point, but note that it >> can be misleading: someone who just adds a `save-excursion` and reindents >> all the code will cause git-blame to hide the contributors of all the >> reindented code. >> >> The way I went about it in the past is to collect all the known authors. >> Then I remove those who already have signed paperwork, and those who >> contributed less than 15 lines of code (by looking at the >> corresponding commits). >> Then I try to contact all those that remain. >> >> This often involves a fair bit of work and time, to try and find current email >> addresses, to get an answer, to sign the paperwork, to get the FSF to >> process the documents, ... >> >> After that, there are typically some authors still pending, either >> because they refuse to sign, or because you can't find a valid email, or >> because they don't reply. >> >> At that point, you dig into the code in more detail, to try and see >> which part of their contribution remains in the current code and whether >> that can fall under the "15-lines worth of code" (where a renaming of >> a variable counts as 1 line even if it touches 100 lines). That often >> lets you remove a few more from the pending list. >> >> Finally, there will probably be a few hold outs who contributed >> a non-trivial amount of code which is still present but whose copyright >> paperwork we can't get. At that point, we have to take a yet deeper >> look at what to do with it: rewrite the code, drop it altogether, or >> move it to a separate package. >> >> Note that if at the last stage there is still a major contributor, it >> might render the whole effort pointless. So it's best to start with the >> most prolific contributors. > > Thanks, this is very helpful! I'll work on generating such a list of > contributors. What is the best way to go about telling people how to do > the copyright process? I know for a contribution to Emacs they email > yall requesting the copyright form but it might be annoying for yall to > deal with all of ESS's contributors. Does it make sense for you to email > me the form and then when I reach out I can include the form with my > email? > > Thanks again, > Alex