all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: emacs-devel@gnu.org
Subject: Re: Fwd: Hiring a programmer
Date: Fri, 16 Jan 2015 11:33:12 +0900	[thread overview]
Message-ID: <8761c7xxnb.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <20150115103803.GA2717@apertron.net>

... and how to deal with the paperwork of assigning to the FSF.

Zack Piper writes:

 > Probably the programmer keeping their copyright.

I think not; that means that the contributor (employer) has to get the
programmer to sign the papers, and probably the contributor has to
sign a disclaimer of interest in the copyright, too.

IMHO (IANAL, David's advice to ask the FSF copyright clerk is best)
the simplest way is a contract which states that upon payment
copyright transfers to the employer.  Then he can assign to the FSF
himself.

One thing to ask the clerk is about the "automatic licenseback"
clause.  In the FSF assignment, AIUI you will get an automatic license
to use your original code any way you like, including in proprietary
products.  If you want to be mathematically fair to the programmer,
you should give a similar license.  *However*, this is in practice
very complicated because the parts of the code that are "original ==
can be disentangled from Emacs" are likely to be small, disconnected,
and hardly useful, let alone profitable in a proprietary product.  The
*simplest* thing to do is ignore the license grant you get from the
FSF and don't mention it to the programmer.




      reply	other threads:[~2015-01-16  2:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15  9:52 Fwd: Hiring a programmer Vaidheeswaran
2015-01-15 10:06 ` David Kastrup
2015-01-15 10:30   ` Vaidheeswaran
2015-01-15 10:38     ` Zack Piper
2015-01-16  2:33       ` Stephen J. Turnbull [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8761c7xxnb.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.