Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <wjhardaker@ucdavis.edu>
Cc: Wes Hardaker <wjhardaker@ucdavis.edu>, ding@gnus.org
Subject: Re: Display X-Face and save space
Date: 28 Sep 2000 09:42:25 -0700	[thread overview]
Message-ID: <sdbsx8zcwe.fsf@wanderer.hardaker.davis.ca.us> (raw)
In-Reply-To: Dave Love's message of "Tue, 26 Sep 2000 14:49:03 +0100"

>>>>> On Tue, 26 Sep 2000 14:49:03 +0100, Dave Love <d.love@dl.ac.uk> said:

WH> Why they need to "own" the copyright makes no sense to me.

Dave> I'm not sure making sense is relevant in law.

Good point.

Dave> The longstanding legal advice -- apparently not just to the FSF
Dave> -- is that for defence in court against violations of the
Dave> licence there should be a single copyright holder, or perhaps
Dave> only a few.  I'm not sure of the exact position; maybe all
Dave> holders of copyright in a combined work have to be involved.  In
Dave> exceptional circumstances there is a specific licence to the FSF
Dave> instead of assignment.
...
WH> Filling out the form once wouldn't prevent me from writing more
WH> code in the future to the same piece and that code wouldn't be
WH> owned by them (unless they explicitly cover future modifications
WH> in their form).

Dave> That's what it normally says.

Yes, but what if I don't trust the FSF to always keep the copyright in
a form that I like it (GPLed).  If they own the copyright, they have
the right to stop distributing future changes made to it under the GPL
(the copyright owner is the *only* person that can do this.  The GPL
only protects *other* people from releasing it under a different
arrangement).

-- 
"Ninjas aren't dangerous.  They're more afraid of you than you are of them."



  reply	other threads:[~2000-09-28 16:42 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-17 13:50 Kai Großjohann
2000-09-17 15:27 ` Raymond Scholz
2000-09-17 22:05   ` Kai Großjohann
2000-09-18 11:02   ` Toby Speight
2000-09-18 11:56     ` Raymond Scholz
2000-09-19 16:34       ` Toby Speight
2000-09-18 16:48     ` Dan Christensen
2000-09-18 16:53       ` Roland Mas
2000-09-18 22:31         ` Kai Großjohann
2000-09-19  1:33           ` Dan Christensen
2000-09-19 10:02             ` Kai Großjohann
2000-09-20  3:23               ` Dan Christensen
2000-09-18 14:27 ` Dave Love
2000-09-18 16:27   ` Kai Großjohann
2000-09-19 16:42     ` Wes Hardaker
2000-09-20  0:36       ` Steve Youngs
2000-09-21 17:08         ` Wes Hardaker
2000-09-23  2:26           ` Steve Youngs
2000-09-25 16:38             ` Wes Hardaker
2000-09-21 19:54       ` Dave Love
2000-09-25 16:42         ` Wes Hardaker
2000-09-26 13:49           ` Dave Love
2000-09-28 16:42             ` Wes Hardaker [this message]
2000-10-03 17:22               ` Per Abrahamsen
     [not found]               ` <200010032202.XAA32394@djlvig.dl.ac.uk>
2000-10-04 20:59                 ` Wes Hardaker
2000-10-05 19:46                   ` Dave Love
2000-10-05 21:59                     ` François Pinard
2000-10-09 21:48                     ` Wes Hardaker
2000-09-21 19:48     ` Dave Love

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=sdbsx8zcwe.fsf@wanderer.hardaker.davis.ca.us \
    --to=wjhardaker@ucdavis.edu \
    --cc=ding@gnus.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).