9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Thomas Bushnell, BSG" <tb+usenet@becket.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] one reason ideas from Plan 9 didn't catch on
Date: Mon, 12 Nov 2001 10:33:20 +0000	[thread overview]
Message-ID: <873d3ntsnw.fsf@becket.becket.net> (raw)
In-Reply-To: <a3db6b24.0111090613.2276d2b4@posting.google.com>

"T. Kurt Bond" <tkb@tkb.mpl.com> writes:

> I'd just like to emphasize that this part of the Plan 9 license seems
> to have changed since Richard Stallman first wrote the article.  Now
> the Plan 9 license says:

This is better, but unfortunately still not quite good enough, I
think.  The problem again is that people might want to distribute
privately, and not have a positive obligation to send copies to
Lucent.  (Whether the recipients of those copies choose to send
something out is their business.)

There seems to be a great fear that private modifications will somehow
take off, and Lucent would get left out of the loop, and not get to
benefit from all the nifty work that would be done.  That's a
reasonable fear; it's exactly the reason the GPL exists.  A copyleft
has the practical effect of allowing you to get changes back almost
always, without actually infringing on freedoms to do it.

A license like the BSD or X Consortium license, by contrast, does
indeed tend to encourage private modifications that never get rolled
back into the original source base, because it's possible with those
licenses to create non-free private modifications.

If the clause were changed into a request instead of a requirement,
it would be no problem at all.

The real killer, of course, is the "you promise never to sue Lucent
for any IP thing" clause.  That's so awful by itself that it dwarfs
the other problems in the license.

I know that Rob Pike and the others who pressured Lucent to make the
code as free as it is were trying to make it more available and to
make it free software.  But the result seems as if they weren't really
aware of what the community actually wants in free sofware, and so
they failed to extract from the lawyers what would actually work.

If there's another go round with the Lucent lawyers (and I certainly
hope there will be), it might be useful to invite Eric Raymond or
someone else of that ilk to help with the process to avoid this kind
of problem.


  parent reply	other threads:[~2001-11-12 10:33 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-08 10:40 Thomas Bushnell, BSG
2001-11-08 12:55 ` Jim Choate
2001-11-09 10:17   ` Thomas Bushnell, BSG
2001-11-09 14:34     ` T. Kurt Bond
2001-11-10  2:00       ` Jim Choate
2001-11-12 10:33         ` Thomas Bushnell, BSG
2001-11-12 11:29           ` Ralph Corderoy
2001-11-13 10:27             ` Thomas Bushnell, BSG
2001-11-12 10:42         ` T. Kurt Bond
2001-11-12 20:24           ` Steve Kilbane
2001-11-13  0:03             ` Jim Choate
2001-11-12 10:33       ` Thomas Bushnell, BSG [this message]
2001-11-12 10:41 ` [9fans] " Douglas A. Gwyn
2001-11-13 10:26   ` Thomas Bushnell, BSG
2001-11-08 13:46 [9fans] " forsyth
2001-11-09  0:51 ` Jim Choate
2001-11-08 14:55 presotto
2001-11-09 10:17 ` Thomas Bushnell, BSG
2001-11-09 10:17 ` John S. Dyson
2001-11-09  7:42 Russ Cox
2001-11-09  9:21 Fco.J.Ballesteros
2001-11-09 11:23 ` pac
2001-11-12 10:32 ` Thomas Bushnell, BSG
2001-11-12 10:45 ` David Rubin
2001-11-12 15:34   ` Ronald G Minnich
2001-11-09  9:38 okamoto
2001-11-12 11:12 Fco.J.Ballesteros
2001-11-12 13:48 ` Jim Choate
2001-11-13 10:27 ` Thomas Bushnell, BSG
2001-11-13 16:21   ` Scott Schwartz
2001-11-12 12:17 geoff
2001-11-13 10:25 ` Thomas Bushnell, BSG
2001-11-12 13:14 nigel
2001-11-13  0:03 ` Jim Choate
2001-11-13 18:04   ` Skip Tavakkolian
2001-11-14  9:52     ` Thomas Bushnell, BSG
2001-11-12 15:10 presotto
2001-11-12 17:06 anothy
2001-11-12 19:15 David Gordon Hogan
2001-11-12 19:18 David Gordon Hogan
2001-11-13  0:19 ` Jim Choate
2001-11-13  2:02   ` Dan Cross
2001-11-13  2:16     ` Jim Choate
2001-11-13  2:27       ` William Josephson
2001-11-13 10:34     ` Thomas Bushnell, BSG
2001-11-12 19:24 anothy
2001-11-14  9:52 ` Eyal Lotem
2001-11-13 19:58 presotto
2001-11-13 20:14 ` William Josephson
2001-11-13 21:39 ` Mike Haertel
2001-11-13 22:54 ` George Michaelson
2001-11-14  0:19   ` William Josephson
2001-11-13 20:17 David Gordon Hogan
2001-11-13 22:38 ` Jim Choate
2001-11-13 20:18 David Gordon Hogan
2001-11-13 21:44 presotto
2001-11-13 21:47 ` andrey
2001-11-13 21:46 Sape Mullender
2001-11-13 21:46 Russ Cox
2001-11-13 21:50 presotto
2001-11-14  0:40 ` Dan Cross
2001-11-13 22:18 forsyth
2001-11-13 23:27 ` Chris Hollis-Locke
2001-11-14  4:38   ` Lucio De Re
2001-11-13 23:46 forsyth
2001-11-14  4:42 Russ Cox
2001-11-14  5:12 ` Dan Cross
2001-11-14  5:24 David Gordon Hogan
2001-11-14  8:29 okamoto
2001-11-14  9:29 Fco.J.Ballesteros
2001-11-14 14:29 rob pike
2001-11-15 10:41 ` Thomas Bushnell, BSG
2001-11-14 14:43 presotto
2001-11-14 16:08 anothy
2001-11-14 18:02 forsyth
     [not found] <20011112170104.719C619ABA@mail.cse.psu.edu>
2001-12-29  4:03 ` Andrew Simmons
2001-11-13 11:13   ` Boyd Roberts
2001-11-13 15:53     ` Douglas A. Gwyn
2001-11-13 17:21     ` Thomas Bushnell, BSG

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=873d3ntsnw.fsf@becket.becket.net \
    --to=tb+usenet@becket.net \
    --cc=9fans@cse.psu.edu \
    /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).