From: Florian Weimer <fw@deneb.enyo.de>
Cc: ding@gnus.org
Subject: Re: Copyright/license issues (was: [COMMIT] sign & encrypt changes)
Date: Thu, 02 May 2002 19:48:10 +0200 [thread overview]
Message-ID: <87wuum1lwl.fsf@deneb.enyo.de> (raw)
In-Reply-To: <bsbyfo2o.fsf_-_@mail.ru> (Dmitry Bely's message of "Thu, 02 May 2002 21:37:35 +0400")
Dmitry Bely <dbely@mail.ru> writes:
>>> Ahh... I did not noticed that it has University Of Stuttgart copyright. But
>>> why this is so bad? Anyway it's GPL'ed so I see no problem here. They are
>>> going to sell it under different license? Good luck! :-)
>>
>> I wrote gpg.el in order to have something which could be integrated
>> into GnuPG or GNU Emacs some day. Back then, I was told that the
>> university wouldn't oppose assigning the copyright...
>
> Probably this is a bit of offtipic, but could you explain me why
> transfering the copyright to FSF is necessary? Why some GPL'ed sources,
> those copyright is holded by somebody else, cannot be supplied with Gnus?
That's official FSF policy we cannot change.
> What you are afraid of?
The copyright owner might claim that it never released the source
under the GPL, and try to extract royalties or damages from the FSF.
A valid assignment contract makes this extremely unlikely, but without
such a contract, you are in the mercy of the copyright owner to some
extent.
next prev parent reply other threads:[~2002-05-02 17:48 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 22:22 [COMMIT] sign & encrypt changes Josh Huber
2002-05-02 6:46 ` Florian Weimer
2002-05-02 13:13 ` Josh Huber
2002-05-02 14:14 ` Florian Weimer
2002-05-02 15:02 ` Josh Huber
2002-05-02 16:06 ` Dmitry Bely
2002-05-02 16:16 ` Josh Huber
2002-05-02 17:44 ` Dmitry Bely
2002-05-02 17:57 ` Florian Weimer
2002-05-02 16:49 ` Florian Weimer
2002-05-02 17:11 ` Dmitry Bely
2002-05-02 17:19 ` Florian Weimer
2002-05-02 17:37 ` Copyright/license issues (was: [COMMIT] sign & encrypt changes) Dmitry Bely
2002-05-02 17:48 ` Florian Weimer [this message]
2002-05-02 18:04 ` Jorgen Schaefer
2002-05-03 13:57 ` Dmitry Bely
2002-05-03 14:10 ` Kai Großjohann
2002-05-03 14:45 ` Dmitry Bely
2002-05-03 15:20 ` Paul Jarc
2002-05-03 17:46 ` Kai Großjohann
2002-05-04 14:15 ` Per Abrahamsen
2002-05-04 14:37 ` Simon Josefsson
2002-05-06 8:20 ` Dmitry Bely
2002-05-06 8:37 ` Matthieu Moy
2002-05-06 11:44 ` Dmitry Bely
2002-05-06 12:27 ` Matthieu Moy
2002-05-06 11:53 ` Per Abrahamsen
2002-05-06 12:31 ` Sean Neakums
2002-05-06 14:09 ` Wes Hardaker
2002-05-06 15:31 ` William M. Perry
2002-05-06 15:43 ` Wes Hardaker
2002-05-06 21:22 ` Florian Weimer
2002-05-07 13:50 ` Per Abrahamsen
2002-05-06 13:07 ` Dmitry Bely
2002-05-06 13:25 ` Simon Josefsson
2002-05-06 13:48 ` Dmitry Bely
2002-05-06 14:09 ` Simon Josefsson
2002-05-06 21:31 ` Florian Weimer
2002-05-07 13:56 ` Per Abrahamsen
2002-05-07 14:54 ` Simon Josefsson
2002-05-07 17:16 ` Dmitry Bely
2002-05-07 18:21 ` Wes Hardaker
2002-05-08 8:46 ` Dmitry Bely
2002-05-08 19:06 ` Russ Allbery
2002-05-13 13:40 ` Per Abrahamsen
2002-05-08 2:37 ` Russ Allbery
2002-05-06 18:56 ` Russ Allbery
2002-05-06 18:55 ` Russ Allbery
2002-05-06 19:50 ` Amos Gouaux
2002-05-06 20:06 ` Wes Hardaker
2002-05-06 20:25 ` Russ Allbery
2002-05-06 21:14 ` Wes Hardaker
2002-05-06 21:20 ` Russ Allbery
2002-05-06 21:37 ` Florian Weimer
2002-05-07 3:24 ` Wes Hardaker
2002-05-07 10:57 ` Kai Großjohann
2002-05-06 21:18 ` Florian Weimer
2002-05-03 19:18 ` Florian Weimer
2002-05-03 22:44 ` Wes Hardaker
2002-05-04 8:57 ` Florian Weimer
2002-05-04 14:27 ` Per Abrahamsen
2002-05-06 14:05 ` Wes Hardaker
2002-05-07 13:39 ` Per Abrahamsen
2002-05-08 15:29 ` Copyright/license issues Werner Koch
2002-05-03 19:21 ` [COMMIT] sign & encrypt changes Florian Weimer
2002-05-06 15:25 ` Josh Huber
2002-05-08 15:32 ` Werner Koch
2002-05-08 16:26 ` Josh Huber
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=87wuum1lwl.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--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).