unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Alex Branham <alex.branham@gmail.com>, emacs-devel@gnu.org
Subject: Re: Including ESS with Emacs
Date: Sun, 25 Nov 2018 12:24:56 -0800	[thread overview]
Message-ID: <d832da7b-5cac-d43b-62d6-a7897b44a8e9@cs.ucla.edu> (raw)
In-Reply-To: <875zwlfeme.fsf@gmail.com>

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



  parent reply	other threads:[~2018-11-25 20:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-25 13:52 Including ESS with Emacs Alex Branham
2018-11-25 16:45 ` Stefan Monnier
2018-11-25 17:11   ` Alex Branham
2018-11-26 13:01     ` Stefan Monnier
2018-11-26  1:40   ` Richard Stallman
2018-11-26 14:39     ` Alex Branham
2018-11-25 20:24 ` Paul Eggert [this message]
2022-09-13  6:29 ` Augusto Stoffel
2022-09-13  8:40   ` Philip Kaludercic
2022-09-13 21:26   ` Stefan Monnier
2022-09-14 10:09     ` Alex Branham
2022-09-14 14:18       ` Stefan Monnier
2022-09-14 14:24       ` Philip Kaludercic
2022-09-14 19:17         ` Sv: " Eric Lindblad

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=d832da7b-5cac-d43b-62d6-a7897b44a8e9@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=alex.branham@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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).