all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: "Andreas Röhler" <andreas.roehler@online.de>, emacs-devel@gnu.org
Cc: Yuri Khan <yuri.v.khan@gmail.com>
Subject: Re: Please explain the FSF copyright assignment thing
Date: Tue, 18 Jul 2017 00:53:08 -0700	[thread overview]
Message-ID: <25b4532b-b2db-e813-7c4c-ee75770e98d6@cs.ucla.edu> (raw)
In-Reply-To: <87b29866-51a6-05b5-c08f-94201bce3d89@online.de>

Andreas Röhler wrote:
> What would stop FSF to assist defending the authors rights?

The FSF would not have standing. The authors would, but might not be available.

>> If you have assigned copyright to FSF, then FSF can sue that violator
>> and have a probability of winning and forcing them to either publish
>> their improvements under GPL, or stop distributing their derived work.
> 
> 
> Could you point me at some example? 

http://www.fsf.org/news/2009-05-cisco-settlement.html



  reply	other threads:[~2017-07-18  7:53 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEwkUWP29A+L2g5i2asCd8Qb2PS1zvhPrsaeEN93tGt-5M05jg@mail.gmail.com>
     [not found] ` <CAEwkUWN8+N6B6uacvXvPeLHwU6RjMYVc3DGZiCexHePUpMPphw@mail.gmail.com>
     [not found]   ` <CAEwkUWN4NUEoBe5JotLctkF=FLG2N6qpknmpncrg8uWehLUSyw@mail.gmail.com>
     [not found]     ` <CAEwkUWOSeK-yny-9qft4yTb=0H3EbXK7atqL9ifoGOnfZt_z7Q@mail.gmail.com>
     [not found]       ` <CAEwkUWMLL8YqiRdqtthgKEzcyn69Ji_bNuq-x0Z-h+MqQKfuUA@mail.gmail.com>
     [not found]         ` <CAEwkUWPD1T7MLAcDPduSpXm34e-GzjFxrcrZat4a0s0fTarrUA@mail.gmail.com>
2017-07-13 17:16           ` Please explain the FSF copyright assignment thing Filipe Silva
2017-07-13 17:49             ` Óscar Fuentes
2017-07-13 18:06               ` Filipe Silva
2017-07-13 18:25               ` John Yates
2017-07-13 18:32                 ` Filipe Silva
2017-07-13 18:36                 ` Karl Fogel
2017-07-13 18:48                   ` Filipe Silva
2017-07-13 19:08                     ` Karl Fogel
2017-07-13 19:11                       ` Filipe Silva
2017-07-13 19:12                     ` Paul Eggert
2017-07-13 19:42                 ` Óscar Fuentes
2017-07-14  5:59                   ` Eli Zaretskii
2017-07-13 19:12             ` Yuri Khan
2017-07-13 19:23               ` Filipe Silva
2017-07-13 19:31                 ` Richard Copley
2017-07-13 19:56                   ` Filipe Silva
2017-07-13 20:07                     ` Richard Copley
2017-07-15  1:36                     ` Richard Stallman
2017-07-15  1:36                 ` Richard Stallman
2017-07-13 20:15               ` Dmitry Gutov
2017-07-14 10:12                 ` Yuri Khan
2017-07-14 12:17                   ` Dmitry Gutov
2017-07-18  6:16               ` Andreas Röhler
2017-07-18  7:53                 ` Paul Eggert [this message]
2017-07-18 17:04                   ` Andreas Röhler
2017-07-18 17:42                     ` Stefan Monnier
2017-07-19  3:32                       ` Richard Stallman
2017-07-19  9:20                         ` Andreas Röhler
2017-07-19 11:56                           ` tomas
2017-07-19 14:34                           ` Richard Stallman
2017-07-14  1:20             ` Richard Stallman

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=25b4532b-b2db-e813-7c4c-ee75770e98d6@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=andreas.roehler@online.de \
    --cc=emacs-devel@gnu.org \
    --cc=yuri.v.khan@gmail.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 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.