unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Michal Nazarewicz" <mina86@mina86.com>
Cc: 9423@debbugs.gnu.org, Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: bug#9423: lisp/server.el: Allow custom server-auth-key
Date: Fri, 13 Apr 2012 08:50:12 -0400	[thread overview]
Message-ID: <jwvk41j6bpy.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <op.wcocazz93l0zgt@mpn-glaptop> (Michal Nazarewicz's message of "Fri, 13 Apr 2012 00:48:25 +0200")

>>>> As for legal stuff, the patch is (c) Google Inc. but since Google has
>>>> signed necessary agreement it should be no problem, right?
>> Anybody know?  I've always assumed that the FSF needs assignment from
>> the person who wrote the code, even if their employer claims to own the
>> code.  (That doesn't sound likely, now that I'm typing it...)
> I don't have any copyright over the code, so I'm not sure why I would have
> to assign the copyright to FSF if copyright holder already did that.

The FSF's copyright clerk confirmed that, as long as the copyright
belongs to Google, we're good to go.  So we can install your patch
right away.  Lars, can you take care of that?

> Then again, if required, I can do it.  Could anyone point me to
> necessary paperwork? CONTRIBUTE only says that “The process is
> straightforward -- contact us at emacs-devel@gnu.org to obtain the
> relevant forms.” but gives no details.

That would be even better, since it's sometimes non-trivial to figure
out if your employer owns the copyright or if you do.
The process is as follows: fill the form below and email it as
instructed so the FSF can send you the necessary paperwork to sign.
Thank you for your contribution,


        Stefan


Please email the following information to assign@gnu.org, and we
will send you the assignment form for your past and future changes.

Please use your full legal name (in ASCII characters) as the subject
line of the message.
----------------------------------------------------------------------
REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES

[What is the name of the program or package you're contributing to?]
Emacs

[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]


[Do you have an employer who might have a basis to claim to own
your changes?  Do you attend a school which might make such a claim?]


[For the copyright registration, what country are you a citizen of?]


[What year were you born?]


[Please write your email address here.]


[Please write your postal address here.]





[Which files have you changed so far, and which new files have you written
so far?]





  reply	other threads:[~2012-04-13 12:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1314366861-27398-1-git-send-email-mina86@mina86.com>
2011-09-02  3:39 ` bug#9423: lisp/server.el: Allow custom server-auth-key Stefan Monnier
2012-04-12 19:46   ` Lars Magne Ingebrigtsen
2012-04-12 22:14     ` Glenn Morris
2012-04-14  4:16       ` Richard Stallman
2012-04-14 18:08         ` Glenn Morris
2012-04-15  2:18           ` Richard Stallman
2012-04-12 22:48     ` Michal Nazarewicz
2012-04-13 12:50       ` Stefan Monnier [this message]
2012-04-13 13:00         ` Michal Nazarewicz
2012-04-14 11:16         ` Lars Ingebrigtsen

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=jwvk41j6bpy.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=9423@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=mina86@mina86.com \
    /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).