unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Zhu Zihao <all_but_last@163.com>
To: Zach Pearson <zach@zjp.codes>
Cc: Eli Zaretskii <eliz@gnu.org>, Matt Bisson <mbisson@ccs.neu.edu>,
	emacs-devel@gnu.org
Subject: Re: Looking for copyright assignment paperwork
Date: Thu, 12 Sep 2019 17:10:04 +0800	[thread overview]
Message-ID: <87impxnamr.wl-all_but_last@163.com> (raw)
In-Reply-To: <A3681313-8E78-4486-AE01-9658219210D1@zjp.codes>

On Thu, 12 Sep 2019 03:13:13 +0800,
Zach Pearson wrote:
> 
> I was also looking for this, would you mind sending it to me as well?
> 
> Thank you
> 
> Zach 
> 
> > On 11 Sep 2019, at 14:03, Eli Zaretskii <eliz@gnu.org> wrote:
> > 
> >> Date: Wed, 11 Sep 2019 14:22:28 -0400 (EDT)
> >> From: Matt Bisson <mbisson@ccs.neu.edu>
> >> 
> >> I'm looking to make some contributions to Emacs, but I first need to assign the copyright for those changes to FSF (I'm in the US if that matters).  Mostly what I'm finding online is that I need to ask this mailing list for information.
> >> 
> >> Can someone help me out with some pointers?  Thanks,
> > 
> > Form sent off-list.
> > 
> 
> 

You can check Org-mode's instruction,
https://orgmode.org/worg/org-contribute.html. In fact Org and GNU ELPA are part
of Emacs, you when you assign to Org(or GNU ELPA), you just assign to Emacs.

If you want to contribute to other project of GNU(e.g GCC), you need another
assignment. 

> (I'm in the US if that matters)

FSF now offering paperless option for assignment, so it doesn't matter at all
wherever you are.




      reply	other threads:[~2019-09-12  9:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11 18:22 Looking for copyright assignment paperwork Matt Bisson
2019-09-11 19:03 ` Eli Zaretskii
2019-09-11 19:13   ` Zach Pearson
2019-09-12  9:10     ` Zhu Zihao [this message]

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=87impxnamr.wl-all_but_last@163.com \
    --to=all_but_last@163.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mbisson@ccs.neu.edu \
    --cc=zach@zjp.codes \
    /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).