From: Axel Beckert <abe@deuxchevaux.org>
To: zsh-workers@zsh.org
Subject: Re: Zsh bugfixes released by RedHat
Date: Thu, 6 Nov 2014 21:15:17 +0100 [thread overview]
Message-ID: <20141106201516.GL5405@sym.noone.org> (raw)
In-Reply-To: <141106083035.ZM3795@torch.brasslantern.com>
Hi,
On Thu, Nov 06, 2014 at 08:30:35AM -0800, Bart Schaefer wrote:
> } Shouldn't they at least offer a patch to you so that it might become
> } official everywhere?
I know of nearly no license requiring that. And if so, at least Debian
would consider such a license as non-free[1].
> Technically they are supposed to offer the patch to us, although zsh's
> license is not as clingy that way as the GNU license for example.
JFTR: The GNU General Public License does not require that any
modification made to software under the GNU GPL is sent back to the
_author_ of the software.
It only requires that those modifications are available to _users_ of
binary compilations based on those modifications. Those users can then
decide to forward those patches back to the original author, but
nobody is required to do that.
There are two common license checks (which the GNU GPL fulfills) which
show why it can be a bad idea to require modifications to be sent back
to the authors. Citing from [1]:
The Desert Island test.
Imagine a castaway on a desert island with a solar-powered
computer. This would make it impossible to fulfill any requirement
to make changes publicly available or to send patches to some
particular place. This holds even if such requirements are only
upon request, as the castaway might be able to receive messages
but be unable to send them. To be free, software must be
modifiable by this unfortunate castaway, who must also be able to
legally share modifications with friends on the island.
The Dissident test.
Consider a dissident in a totalitarian state who wishes to share a
modified bit of software with fellow dissidents, but does not wish
to reveal the identity of the modifier, or directly reveal the
modifications themselves, or even possession of the program, to
the government. Any requirement for sending source modifications
to anyone other than the recipient of the modified binary---in
fact any forced distribution at all, beyond giving source to those
who receive a copy of the binary---would put the dissident in
danger. For Debian to consider software free it must not require
any such "excess" distribution.
[1] https://people.debian.org/~bap/dfsg-faq.html#testing
https://en.wikipedia.org/wiki/Debian_Free_Software_Guidelines#debian-legal_tests_for_DFSG_compliance
Kind regards, Axel
--
/~\ Plain Text Ribbon Campaign | Axel Beckert
\ / Say No to HTML in E-Mail and News | abe@deuxchevaux.org (Mail)
X See http://www.nonhtmlmail.org/campaign.html | abe@noone.org (Mail+Jabber)
/ \ I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web)
next prev parent reply other threads:[~2014-11-06 20:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 15:56 Bart Schaefer
2014-11-06 16:58 ` Jérémie Roquet
2014-11-06 17:04 ` Christian Neukirchen
2014-11-06 18:40 ` Bart Schaefer
2014-11-06 17:13 ` Ray Andrews
2014-11-06 16:30 ` Bart Schaefer
2014-11-06 20:15 ` Axel Beckert [this message]
2014-11-06 20:47 ` Bart Schaefer
2014-11-06 22:10 ` Christian Neukirchen
2014-11-06 22:21 ` Jérémie Roquet
2014-11-07 15:06 ` Christian Neukirchen
2014-11-06 22:10 ` Axel Beckert
2014-11-06 21:57 ` Ray Andrews
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=20141106201516.GL5405@sym.noone.org \
--to=abe@deuxchevaux.org \
--cc=zsh-workers@zsh.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 public inbox
https://git.vuxu.org/mirror/zsh/
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).