all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Rankin <hello@paulwrankin.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Adding advisory notification for non-ELPA package.el downloads
Date: Fri, 21 Jul 2017 00:36:40 +1000	[thread overview]
Message-ID: <1500561400.523072.1047139192.217F8F40@webmail.messagingengine.com> (raw)
In-Reply-To: <834lu7b35o.fsf@gnu.org>

On Fri, 21 Jul 2017, at 12:20 AM, Eli Zaretskii wrote:
> > From: Paul Rankin <hello@paulwrankin.com>
> > Cc: rms@gnu.org, emacs-devel@gnu.org
> > Date: Fri, 21 Jul 2017 00:01:48 +1000
> > 
> > On Thu, 20 Jul 2017, at 11:42 PM, Eli Zaretskii wrote:
> > > I think you might misunderstand the nature and the essence of the
> > > copyright assignment: it doesn't in any way diminish the author's
> > > rights on his/her code.  Here's a direct citation from
> > > 
> > >  https://www.fsf.org/bulletin/2014/spring/copyright-assignment-at-the-fsf
> > > 
> > >   Sometimes contributors are concerned about giving up rights to their
> > >   work. As the assignment is a gift to the free software community,
> > >   they don't want it to come at the expense of having flexibility in
> > >   the use of their own code. Thus, we grant back to contributors a
> > >   license to use their work as they see fit. This means they are free
> > >   to modify, share, and sublicense their own work under terms of their
> > >   choice. This enables contributors to redistribute their work under
> > >   another free software license. While this technically also permits
> > >   distributing their work under a proprietary license, we hope they
> > >   won't.
> > > 
> > > I can confirm that every one of my assignments I got back signed by
> > > the FSF includes a specific clause about the above rights granted back
> > > to me.
> > 
> > Eli you've missed the point completely.
> 
> Maybe so, but then how about explaining what I missed?
> 
> From my POV, you expressed a concern about giving up the rights for
> your code, and I pointed out that by assigning you don't give up any
> rights.  Given that Clément pointed out the "Author" and/or "Written
> by" records in the sources, what other concerns remain?

Copyright is not merely functional, and you're reducing it to even
lesser functional purposes by arguing that given assigning copyright to
the FSF retains the subset of functional purposes of copyright that are
important to you, then they are effectively the same and should be
treated the same for everyone. Copyright is not its function, rather its
functions arise as the manifestations of the importance we see in
authorship as ownership. That's a symbolic importance, and while that
may not mean much to you, it's where all the functional purposes above
come from. Owning a thing, and having rights to that thing as if you
owned it, are not the same thing.



  reply	other threads:[~2017-07-20 14:36 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20 12:29 Adding advisory notification for non-ELPA package.el downloads Paul Rankin
2017-07-20 12:37 ` Clément Pit-Claudel
2017-07-20 13:42 ` Eli Zaretskii
2017-07-20 13:49   ` Jean-Christophe Helary
2017-07-20 14:17     ` Eli Zaretskii
2017-07-20 14:48       ` Jean-Christophe Helary
2017-07-20 14:57         ` Eli Zaretskii
2017-07-24  2:52       ` Richard Stallman
2017-07-20 14:01   ` Paul Rankin
2017-07-20 14:20     ` Eli Zaretskii
2017-07-20 14:36       ` Paul Rankin [this message]
2017-07-20 14:47         ` Jean-Christophe Helary
2017-07-20 15:09           ` Paul Rankin
2017-07-20 15:08         ` Eli Zaretskii
2017-07-20 15:58           ` Paul Rankin
2017-07-20 17:56             ` Eli Zaretskii
2017-07-21 11:21               ` Nikolaus Rath
2017-07-20 14:27     ` John Wiegley
2017-07-20 15:19 ` Stephen Berman
2017-07-20 16:19 ` Radon Rosborough
2017-07-24  2:52   ` Richard Stallman
2017-07-24  3:05     ` Radon Rosborough
2017-07-25  1:32       ` Richard Stallman
2017-07-20 21:20 ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2017-07-08  1:59 John Wiegley
2017-07-08 10:29 ` Dmitry Gutov
2017-07-08 12:57   ` Kaushal Modi
2017-07-08 17:03   ` Richard Stallman
2017-07-08 22:12     ` Jean-Christophe Helary
2017-07-08 22:50       ` Tim Cross
2017-07-10  9:29         ` Richard Stallman
2017-07-13 15:07         ` Jean Louis
2017-07-10  9:29       ` Richard Stallman
2017-07-09  0:39     ` Dmitry Gutov
2017-07-10  2:07       ` Chad Brown
2017-07-10  9:27       ` Richard Stallman
2017-07-10 13:02         ` Dmitry Gutov
2017-07-11 11:45           ` Richard Stallman
2017-07-11 15:00             ` Yuri Khan
2017-07-11 18:01               ` John Wiegley
2017-07-11 18:37                 ` Yuri Khan
2017-07-11 22:57               ` Richard Stallman
2017-07-12  7:56                 ` Yuri Khan
2017-07-12 16:12                   ` Richard Stallman
2017-07-11 22:57               ` Richard Stallman
2017-07-12 23:12                 ` Nicolas Petton
2017-07-13 12:26                   ` Richard Stallman
2017-07-13 19:12                     ` Nicolas Petton
2017-07-15  1:33                       ` Richard Stallman
2017-07-17  8:16                         ` Nicolas Petton
2017-07-24  2:54                           ` Richard Stallman
2017-07-10 15:36         ` Ken Manheimer
2017-07-10 23:32           ` Richard Stallman
2017-07-08 14:57 ` Clément Pit-Claudel
2017-07-09  3:04   ` Yann Hodique
2017-07-10  9:29     ` Richard Stallman
2017-07-10 15:41       ` Ken Manheimer
2017-07-10 23:30         ` Richard Stallman
2017-07-10 16:48       ` Yann Hodique
2017-07-10 20:43   ` Joost Kremers
2017-07-11 22:57     ` Richard Stallman
2017-07-12  0:40       ` Stefan Monnier
2017-07-12 16:13         ` 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=1500561400.523072.1047139192.217F8F40@webmail.messagingengine.com \
    --to=hello@paulwrankin.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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.