All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hubert Chan <hubert@uhoreg.ca>
To: reiserfs-list@namesys.com
Subject: Re: reiser4progs 0.5.4 for Debian
Date: Tue, 08 Jun 2004 22:28:21 -0400	[thread overview]
Message-ID: <871xkppire.fsf@uhoreg.ca> (raw)
In-Reply-To: 20040608184559.GM4990@nysv.org

License> "Finally, nothing in this license shall be interpreted to allow
License> you to fail to fairly credit me, or to remove my credits such
License> as by creating a front end that hides my credits from the user
License> or renaming mkfs.reiser4"

>>>>> "Markus" == Markus Törnqvist <mjt@nysv.org> writes:

Markus> On Tue, Jun 08, 2004 at 03:02:32PM +0530, Amit Shah wrote:
Amit> This isn't DFSG-free.

Markus> So is the case that Debian must somehow say they will honor
Markus> Hans' request to make it GPL/DFSG free?

No.  Debian's actions do not affect the DFSG free-ness of a license.

Markus> Well.. how can it not be DFSG free if it says that it's GPLv2

It is GPLv2 with "clarifications".

Markus> and Stallman agrees with what Hans said?

Stallman agrees with Hans' right to dual-/triple-/etc. license.  I
haven't heard his opinion on disallowing the removal or hiding of
credits.  Disallowing the removal of copyright notices is a standard
restriction, but credits isn't that clear.

Disallowing the renaming of mkfs.reiser4 could be a problem -- if
someone writes a hobby filesystem from scratch (or based on some ideas
from Reiser4), but uses significant (or even insignificant, but still
enough for copyright to be claimed) code from mkfs.reiser4, he may be
compelled to keep his program named "mkfs.reiser4", even though his
filesystem is not compatible in any way with Reiser4.  This violates
DFSG clause 3 ("Derived works").

IANAL, but to me, disallowing creating a frontend that hides the
credits seems more like a _use_ restriction than a _copy_ restriction,
and hence smells more like a EULA than a copyright license.  The author
of the front end does not have to do any copying or modification of
mkfs.reiser4 in order to create the front end.

Markus> Or is Debian more about DFSG than GPL?

Yes.  Debian and the FSF seem to have slightly different opinions on
what "Free" is.  For example, the FSF's GNU FDL (Free Documentation
License) is said to be non-DFSG-free.  But the GPL with no other
modifications or clarifications or interpretations is generally
regarded as DFSG-free.

-- 
Hubert Chan <hubert@uhoreg.ca> - http://www.uhoreg.ca/
PGP/GnuPG key: 1024D/124B61FA
Fingerprint: 96C5 012F 5F74 A5F7 1FF7  5291 AF29 C719 124B 61FA
Key available at wwwkeys.pgp.net.   Encrypted e-mail preferred.


  reply	other threads:[~2004-06-09  2:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03 19:41 reiser4progs 0.5.4 for Debian mjt
2004-06-03 19:58 ` Chris Dukes
2004-06-07 19:33 ` Domenico Andreoli
2004-06-07 20:02   ` mjt
2004-06-08  9:32     ` Amit Shah
2004-06-08 18:46       ` mjt
2004-06-09  2:28         ` Hubert Chan [this message]
2004-06-09  3:46           ` Hans Reiser
2004-06-09 20:36             ` Hubert Chan
2004-06-09 21:50               ` Domenico Andreoli
2004-06-09 21:56                 ` mjt
2004-06-09 23:00                   ` Hubert Chan
2004-06-09 23:06                   ` Domenico Andreoli
2004-06-09  8:08           ` mjt
2004-06-09 20:57             ` Hubert Chan

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=871xkppire.fsf@uhoreg.ca \
    --to=hubert@uhoreg.ca \
    --cc=reiserfs-list@namesys.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.
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.