public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Disconnect <lkml@sigkill.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Why is Nvidia given GPL'd code to use in non-freedrivers?
Date: 07 Jan 2003 14:08:18 -0500	[thread overview]
Message-ID: <1041966498.15859.18.camel@sparky> (raw)
In-Reply-To: <E18Vyhp-0007S3-00@fencepost.gnu.org>

On Tue, 2003-01-07 at 13:44, Richard Stallman wrote:
>     So If I spend $X developing my game and then sell it closed with the 
>     stated intention of opening the source as soon as it has recouped a 
>     reasonable return on my investment, this would get your official seal of 
>     approval?
> 
> Not quite.  We can't count on this to result in free software.
> 
> 2. There's no time limit.  "As soon as it has recouped a reasonable
> return" could mean years from now, or never.  As a result, even if you
> specify a specific free software license that you will use, we still
> can't count on this to make the package free software in any
> reasonable time.

So if he specifies a specific future license (eg GPL, just to simplify
things) and indicates what 'reasonable return' is (eg "a sale of 8,000
licenses" or some such) that would be ok......

> If these two points were suitably changed, this becomes a plan that I
> might recommend to you if you were otherwise going to keep the
> software non-free and there were no better possibility.  However, I
> could not recommend actually using the software while it is non-free.

....but you'd recommend that people not have the freedom to make their
own price/value decisions AND (added bonus) actively work to PREVENT it
ever becoming GPL'd.

User: "This [game/driver/database/...] is exactly what I need, and its
only $50!  Its worth way more than that to me, this rules."
RMS: "Sorry, you're not allowed to buy that.  Just wait until it becomes
free, then its all yours."
User: "Um.. ok. I need it pretty soon, and $50 is a great deal; it would
cost me at least $2k and time I don't have to recreate it from scratch. 
When will it be free so I can use it?"
RMS: "Well... when a bunch of people piss me off and go buy it."
....

Heh. Hehehehe.  So we're back to the "software developers are evil and
should all starve to death" stance.  Nifty.  Thank [insert diety here]
that you are working so hard to destroy your reputation; I'd hate to see
the number of people following your edicts actually increasing..




  reply	other threads:[~2003-01-07 18:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-05  0:11 Why is Nvidia given GPL'd code to use in non-freedrivers? Steven Barnhart
2003-01-06  3:26 ` Richard Stallman
2003-01-06  9:50   ` Andrew Walrond
2003-01-06 20:50     ` Richard Stallman
2003-01-06 21:13       ` Mark Mielke
2003-01-06 23:52       ` Andrew Walrond
2003-01-07  4:37         ` Oliver Xymoron
2003-01-07 18:44         ` Richard Stallman
2003-01-07 19:08           ` Disconnect [this message]
2003-01-06 23:58   ` Matthias Andree
2003-01-07  0:23     ` Andre Hedrick
2003-01-12 23:44       ` Matthias Andree
2003-01-13  0:28         ` Andre Hedrick
  -- strict thread matches above, loose matches on Subject: below --
2003-01-09 16:36 Edward Kuns

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=1041966498.15859.18.camel@sparky \
    --to=lkml@sigkill.net \
    --cc=linux-kernel@vger.kernel.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