From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Including ESS with Emacs Date: Sun, 25 Nov 2018 12:24:56 -0800 Organization: UCLA Computer Science Department Message-ID: References: <875zwlfeme.fsf@gmail.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1543177425 2887 195.159.176.226 (25 Nov 2018 20:23:45 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 25 Nov 2018 20:23:45 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 To: Alex Branham , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 25 21:23:41 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 1gR0wP-0000df-Bb for ged-emacs-devel@m.gmane.org; Sun, 25 Nov 2018 21:23:41 +0100 Original-Received: from localhost ([::1]:32876 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gR0yV-0006gN-HS for ged-emacs-devel@m.gmane.org; Sun, 25 Nov 2018 15:25:51 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60713) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gR0xi-0006g7-Qy for emacs-devel@gnu.org; Sun, 25 Nov 2018 15:25:03 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gR0xe-0001RH-S1 for emacs-devel@gnu.org; Sun, 25 Nov 2018 15:25:02 -0500 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:53652) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gR0xe-0001QV-Le for emacs-devel@gnu.org; Sun, 25 Nov 2018 15:24:58 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 778DE16015B; Sun, 25 Nov 2018 12:24:57 -0800 (PST) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id WdRyTKKvzjAO; Sun, 25 Nov 2018 12:24:56 -0800 (PST) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 7666E16009E; Sun, 25 Nov 2018 12:24:56 -0800 (PST) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id wd_zwDT_2vja; Sun, 25 Nov 2018 12:24:56 -0800 (PST) Original-Received: from [192.168.1.9] (cpe-23-242-74-103.socal.res.rr.com [23.242.74.103]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 4D989160093; Sun, 25 Nov 2018 12:24:56 -0800 (PST) In-Reply-To: <875zwlfeme.fsf@gmail.com> Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 131.179.128.68 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:231371 Archived-At: Alex Branham wrote: > Is there a process for figuring out who exactly needs to sign the FSF > copyright paperwork? Is it just authors of the current code according to > git-blame, or everyone who's contributed 15 lines of code, or something > else? If we accept just the latest version of ESS, we'd need permission only from people who have made significant contributions to that version. We wouldn't need permission from people who made past contributions that haven't survived into the current version. Unfortunately, though, the question of "who contributed to this line of code?" cannot in general be answered by "look at the git blame output for this line", as the line may have most recently been touched by person X even though its main author was person Y earlier. I don't know how many contributors we're talking about here, but one possible option is to ask for permissions from everybody, and then if you can't get permission from persons P, Q and R then you look at every commit that they made and see whether any significant part or those commits have survived into the current version. If some bits of code have survived, take them out or rewrite them from scratch (ideally via a cleanroom approach). > 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? Sure, here's the form I usually use. Other forms might apply depending on your contributors' concerns. https://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign.future