All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Davis <reiser-list@empires.org>
To: reiserfs-list@namesys.com
Subject: Re: reiser4 non-free? (I throw in the towel)
Date: Tue, 11 May 2004 02:59:15 -0700	[thread overview]
Message-ID: <1084269555.22047.138.camel@jeff> (raw)
In-Reply-To: <200405110004.05704.reiser@namesys.com>


> Debian's efforts to make licensing into inflexible dogma are bad, based on a 
> lack of understanding of the tradeoffs inherent in licensing, and deserve 
> opposition.  However, in all teams there is a need to give ground even when 
> one is right, and fighting Microsoft is my priority much more than fighting 
> Debian.  If Debian offers to provide credits in practice but not theory, and 
> there is some possibility of getting into a debian installer in the near 
> future, then I can probably lose a little and risk a little and put both 
> progs and kernel code into GPL V2 for now despite it being a license with  
> flaws that beg for fixing.
> 

I have read most of this discussion in the mail archives. I support your
position no matter whether you chooses plagarizable or not. Even if the
license allows potential to create non-free software, the fact is that,
to me as a user, software from Namesys (and contributors) is free. Until
Namesys (and contributors) uses the license to prevent me from using,
modifying (by myself or hiring someone else), or distributing the
software how I want to, it always will be free.

The freedom of software is the combination of the license, the software
itself, and the developers.

People can even abuse the GPL to a degree, and much GPL software is less
free than reiserfs. Some code is constructed in a very convoluted way
that only the initial developers understand. Some projects have made
architectural choices that, for all practical purposes, eliminate the
ability to make a certain kind of change (a common example is software
for which porting is virtually impossible). Some groups make it
difficult for outsiders to contribute. Some people put their modified
GPL software on their own servers, never distribute the changes, and
then just allow people network access to those servers.

The GPL is a powerful and valuable tool, but if the developers don't
want it to be free, it won't be, even if it's GPL.

I suppose experimentation is required, since people did raise some
interesting questions (such as language translation of credits). You are
in the rare position in which you can change licenses as you wish; most
projects don't have the ability to experiment with licenses.

As far as Debian is concerned, I don't think you give them quite enough
credit. Those people just want a base of freedoms which a normal person
can understand that covers all the software. It's very helpful to have
an OS where you don't have to turn a development project into a legal
investigation, tracking down hundreds of licenses. Now, that "base of
freedoms" may not be agreeable to everyone, but we can't ignore the
value of consistant licensing in an OS. And many of the problems with
DFSG are mitigated by having a well-integrated non-free section
(unfortunately that doesn't solve the problems for reiserfs, which needs
to be in the OS install).

Regards,
	Jeff



  reply	other threads:[~2004-05-11  9:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-08 14:13 reiser4 non-free? Humberto Massa
2004-05-09 18:47 ` Richard Stallman
2004-05-11  7:04 ` reiser4 non-free? (I throw in the towel) Hans Reiser
2004-05-11  9:59   ` Jeff Davis [this message]
2004-05-11 10:49     ` mjt
2004-05-11 15:52     ` Hans Reiser
2004-05-11 13:09   ` Raul Miller
2004-05-11 13:50     ` Paul Wagland
2004-05-11 18:41     ` mjt
2004-05-12  2:30   ` Michael Milverton

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=1084269555.22047.138.camel@jeff \
    --to=reiser-list@empires.org \
    --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.