From: Richard Stallman <rms@gnu.org>
To: andrew@walrond.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why is Nvidia given GPL'd code to use in non-freedrivers?
Date: Tue, 07 Jan 2003 13:44:05 -0500 [thread overview]
Message-ID: <E18Vyhp-0007S3-00@fencepost.gnu.org> (raw)
In-Reply-To: <3E1A16A5.8070903@walrond.org> (message from Andrew Walrond on Mon, 06 Jan 2003 23:52:05 +0000)
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.
1. An open source program may or may not be free software. I'd have
to know what license you would use, and be sure it was a free software
license, in order to expect that this would produce free software.
(See http://www.gnu.org/philosophy/free-software-for-freedom.html.)
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.
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 isn't this exactly what Andre has been lambasted for? Perhaps you
should step in and say a few words in his defence.
I don't know what Andre plans to do. I find it difficult to read
those messages--every sentence seems to have various interpretations.
Maybe it violates the GPL, maybe it doesn't. Maybe it falls within
the permission that the Linux developers have given for non-free
modules. It seems to concern protocols I don't know anything about.
Since the issue does not concern the FSF directly, I don't need to try
to figure it out. I am leaving the issue to others.
Perhaps not. But my 40 software developing staff are still going to be
mightily pissed when I don't make payroll.
In a capitalist system, creation and loss of jobs are normal.
Unemployment is normal too--and the level of unemployment is
controlled by macroeconomic factors. To employ 40 people in one
particular way cannot justify making a program non-free.
It is impossible to tell whether a world of free software would
provide more employment or less employment. There is too much
that we do not know.
next prev parent reply other threads:[~2003-01-07 18:35 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 [this message]
2003-01-07 19:08 ` Disconnect
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=E18Vyhp-0007S3-00@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=andrew@walrond.org \
--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