From: Carlo Wood <carlo@alinoe.com>
To: Bernard Dautrevaux <Dautrevaux@microprocess.com>
Cc: "'rms@gnu.org'" <rms@gnu.org>,
gcc@gcc.gnu.org, license-discuss@opensource.org
Subject: Re: GPL and NDA
Date: Fri, 20 Jul 2001 06:36:00 -0000 [thread overview]
Message-ID: <20010720153615.A1158@alinoe.com> (raw)
In-Reply-To: <17B78BDF120BD411B70100500422FC6309E2F4@IIS000>
On Fri, Jul 20, 2001 at 08:02:23AM +0200, Bernard Dautrevaux wrote:
> Company A provides, under an NDA, information to company B.
>
> Using this information, B develop, based on some GPLed code,
> a program for A.
>
> B then distribute this program (which IS GPLed) to A, but is
> prohibited to distribute it to anybody else (due to the NDA).
>
> Is this a violation of the GPL or is it possible, provided that B distribute
> the program to A with the normal GPL provision of the access to the source
> code?
>
> Of course if A decide to redistribute the program in any form, then this
> must be done witout requiring an NDA to conform with the GPL. My question is
> about the initial "distribution" of the NDA-covered code by B to A.
Imho, it works as follows:
anything + GPL can not be distributed unless it is first GPL-ed.
If 'anything' disallows changing the license, then it can not be
distributed period. However, if the NDA allows B to perform the
following atomic operation: distibute it back to A and GPL it at
the same time, then there is no incompatibility with the GPL.
However, and that is certainly an interesting legal question,
can something like that be atomic? If you first GPL it and THEN
distribute it to A, then there CAN NOT be a restriction to also
distribute it to C. While when you first distribute it to A and
then GPL it, you violated the GPL. And even when the operation
can be atomic, A can not distribute it anymore of course - if he
does that then the orginal authors of the GPL-ed code as well as
B can legally request a copy - which would be GPL-ed.
Imho, this is only possible when the transfer from B back to A
is not considered a distribution as per GPL.
--
Carlo Wood <carlo@alinoe.com>
next prev parent reply other threads:[~2001-07-20 6:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 23:28 Bernard Dautrevaux
2001-07-20 6:36 ` Carlo Wood [this message]
2001-07-20 11:08 ` Joern Rennecke
2001-07-21 0:48 ` Chris Sloan
2001-07-20 8:17 ` GPL and NDA Q:what defines an "organization" Robert E. Hartley
2001-07-20 8:31 ` DJ Delorie
2001-07-20 12:38 ` GPL and NDA Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2001-07-21 11:46 dewar
2001-07-21 11:42 dewar
2001-07-21 4:51 dewar
2001-07-21 8:53 ` Randy Kramer
2001-07-21 9:40 ` Carlo Wood
2001-07-20 14:38 dewar
2001-07-20 8:36 Julian Hall
2001-07-19 4:07 Richard Stallman
2001-07-19 9:13 ` Mark Mitchell
2001-07-19 20:00 ` Richard Stallman
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=20010720153615.A1158@alinoe.com \
--to=carlo@alinoe.com \
--cc=Dautrevaux@microprocess.com \
--cc=gcc@gcc.gnu.org \
--cc=license-discuss@opensource.org \
--cc=rms@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).