git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Collin Funk <collin.funk1@gmail.com>
Cc: "D. Ben Knoble" <ben.knoble@gmail.com>, Git <git@vger.kernel.org>
Subject: Re: Signed-off-by & the law
Date: Fri, 17 Oct 2025 00:18:50 -0400	[thread overview]
Message-ID: <20251017041850.GD786497@mit.edu> (raw)
In-Reply-To: <87tszylem4.fsf@gmail.com>

On Thu, Oct 16, 2025 at 02:29:39PM -0700, Collin Funk wrote:
> I think this section from an article written by the FSF addresses your
> concern [1]:
> 
>     Some developers worry that assigning copyright will strip them of
>     all their rights to the code they've created. To address this, the
>     FSF includes a "license grantback" to the developer in the agreement
>     contract. For the developer, a license grantback means they can
>     continue to modify and share their code, and technically, they could
>     even distribute their software under a different license. In other
>     words, by assigning copyright to the FSF, the developer does not
>     give up any of these sorts of rights.

That's not the only concern.  The reason why I have chosen to never to
sign an FSF Copyright Assignment is the following:

  "I hereby indemnify and hold harmless the Foundation, its officers,
  employees, and agents against any and all claims, actions or damages
  (including attorney's reasonable fees)...."

If you ever see the word "indemnify" in a legal document that someone
asks you to sign, I strongly suggest that you first talk to a lawyer
to understand what this might mean.  Speaking for myself, if I were to
give the FSF my intellectual output, under NO circumstances would I be
willing to risk my assets, my house, etc. on an indemnification
guarantee.

In any case, as I mentioned in my comment to Ben's Law Stack Exchange
answer, before the DCO was drafted for the Linux Kernel's
SubmittingPatches process documentation, it was vetted by lawyers at
the Linux Foundation and various LF Member Companies.  Those lawyers
certainly viewed the DCO as being legally useful.

	  	     	    	  	  - Ted

P.S.  The FSF has gotten more flexible over time; when I first got
involved with FOSS, the FSF required copyright assignments, and so I
didn't contribute to FSF projects.  Perhaps because enough people,
including large companies, have said "no way, Jose", the FSF will now
accept copyright disclimers, or even unlimited perpetual copyright
licenses.  More recently, they've even said that limited number of
code contributions with a DCO might be acceptable[1].

[1] https://www.fsf.org/blogs/licensing/FSF-copyright-handling

  reply	other threads:[~2025-10-17  4:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16 20:15 Signed-off-by & the law D. Ben Knoble
2025-10-16 20:55 ` Collin Funk
2025-10-16 21:16   ` D. Ben Knoble
2025-10-16 21:29     ` Collin Funk
2025-10-17  4:18       ` Theodore Ts'o [this message]
2025-10-16 21:04 ` Junio C Hamano
2025-10-16 21:06   ` D. Ben Knoble

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=20251017041850.GD786497@mit.edu \
    --to=tytso@mit.edu \
    --cc=ben.knoble@gmail.com \
    --cc=collin.funk1@gmail.com \
    --cc=git@vger.kernel.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.
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 NNTP newsgroup(s).