From: Richard Copley <rcopley@gmail.com>
To: Filipe Silva <filipe.silva@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>,
Yuri Khan <yuri.v.khan@gmail.com>
Subject: Re: Please explain the FSF copyright assignment thing
Date: Thu, 13 Jul 2017 21:07:17 +0100 [thread overview]
Message-ID: <CAPM58oiRDmPhRk=wtNy9xVdc5J+ewCLZd5t0F2ssHcjmOQwT=w@mail.gmail.com> (raw)
In-Reply-To: <CAEwkUWPSKXs8ChtMqujGsmQ2pR2f-cZGg+CrD+gEK6W=aZDaHA@mail.gmail.com>
On 13 July 2017 at 20:56, Filipe Silva <filipe.silva@gmail.com> wrote:
> Yes I've tries that. It does not go as deep into the question as this
> thread.
>
> I mean the fact that a copyright owner can go rogue and change a license
> alone without asking if the other copyright owners would agree and at the
> same time all the copyright owners must act in cooperation in order to
> enforce a license. This is is a sad state of affairs.
OK, thanks. That was the paragraph of Karl's email I found least
plausible. Copyright assignment doesn't seem to have anything to do
with it. A declaration that the code is being released under the
appropriate licence should be enough.
next prev parent reply other threads:[~2017-07-13 20:07 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 [this message]
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
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
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='CAPM58oiRDmPhRk=wtNy9xVdc5J+ewCLZd5t0F2ssHcjmOQwT=w@mail.gmail.com' \
--to=rcopley@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=filipe.silva@gmail.com \
--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 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).