public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Mike Stump <mrs@apple.com>
Cc: Biagio Lucini <lucini@phys.ethz.ch>,
	gcc@gcc.gnu.org, gomp@nongnu.org,  gcc-patches@gcc.gnu.org
Subject: Re: OpenMP licensing problem: a solution
Date: Wed, 24 Nov 2004 01:03:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.60.0411231944000.29669@dberlin.org> (raw)
In-Reply-To: <D17D35C7-33A7-4DD0-B889-7920EFDC942C@apple.com>



On Tue, 23 Nov 2004, Mike Stump wrote:

> On Nov 23, 2004, at 12:16 AM, Biagio Lucini wrote:
>> I have made an enquiry to the OpenMP ARB, appended is the answer I 
>> received.
>> My understanding of the meaning of "public domain" is that we are free to 
>> put the code under GPL+exceptions.
>
> My take, I think their email reply is evidence that they have no clue 
> what-so-ever.  I'd suggest that you ask them a yes or no question, and that 
> you accept no another answer other than yes or no.  Now, as to the question, 
> can I do X, where X is all the code that you think might infringe.  Also, 
> bear in mind, what the person says has no legal weight, if they person you 
> are talking to has no legal standing.

It's never a good idea to make assumptions about what principles the law 
follows :).

In this case, what you've said isn't necessarily or even usually true.
Take a gander at the law of agency, in particular the principle of 
"apparent authority" (and also the principles of various forms 
of estoppel). Of course, you'd end up in court in this case, which you'd 
want to avoid, but you don't get to hold yourself out and give legal 
answers on behalf of your employer without any consequences :).

Which brings us to the part where i say this isn't legal advice, doesn't 
represent IBM, blah, blah, blah, blah :)


--Dan

  reply	other threads:[~2004-11-24  0:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23  9:31 Biagio Lucini
2004-11-24  0:03 ` Mike Stump
2004-11-24  1:03   ` Daniel Berlin [this message]
2004-11-24  2:09     ` Joe Buck
2004-11-24  3:20     ` Mike Stump
2004-11-24  5:35       ` Daniel Berlin
2004-11-24  7:52         ` Joe Buck

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=Pine.LNX.4.60.0411231944000.29669@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gomp@nongnu.org \
    --cc=lucini@phys.ethz.ch \
    --cc=mrs@apple.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 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).