From: "bfields@fieldses.org" <bfields@fieldses.org>
To: Steve Dickson <SteveD@RedHat.com>
Cc: Trond Myklebust <trondmy@primarydata.com>,
"sumitgt@google.com" <sumitgt@google.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] Add LICENSE for Connectathon test suite
Date: Mon, 26 Feb 2018 10:06:41 -0500 [thread overview]
Message-ID: <20180226150641.GH15876@fieldses.org> (raw)
In-Reply-To: <10fdcb85-66dd-1a13-8a86-735e605dcd0c@RedHat.com>
On Mon, Feb 26, 2018 at 09:04:53AM -0500, Steve Dickson wrote:
> On 02/25/2018 08:29 PM, Trond Myklebust wrote:
> > On Sun, 2018-02-25 at 18:47 -0500, J. Bruce Fields wrote:
> >> On Sun, Feb 25, 2018 at 03:41:48PM -0500, Steve Dickson wrote:
> >>> On 02/23/2018 10:35 PM, Trond Myklebust wrote:
> >>>> I therefore suspect that if you were to talk to your employer's
> >>>> legal
> >>>> department, they would strongly advise to let these particular
> >>>> sleeping
> >>>> dogs lie.
> >>>
> >>> If the google lawyers are good with this...
> >>
> >> I've seen no evidence that google has any ownership of any of the
> >> Connectathon test suite code.
> Who owns the code now? The same people that owned it way back when?
Probably.
> >> We need to leave this alone unless we get a much better explanation.
> >
> > If Google does want to contribute, then perhaps they might volunteer to
> > write an Apache licensed and independently developed version of the
> > testsuite? That would break the deadlock that we have today without
> > risking offending any of the original copyright holders, and would
> > allow us to resume contributing further extensions.
> >
> By no means am I a lawyer... Actually I avoid as much as possible ;-)
> But you are saying if Google adds this license they now own the code?
Basically there's a little bit of land out in the country where we've
been meeting for regular picnics a few times a year. The old owners
were OK with that and the place seems kinda abandoned, so we figure
nobody will mind if we keep holding the picnics. But we're not going to
encourage anyone to build a house there, either. Or start putting up
signs saying what people can or can't do with the property, as if it
were ours.
--b.
next prev parent reply other threads:[~2018-02-26 15:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 1:07 [PATCH] Add LICENSE for Connectathon test suite Sumit Gouthaman
2018-02-24 3:13 ` Trond Myklebust
[not found] ` <CAKVgptYWbvrf6+PUm55id8vBGAkHYaxHRQ8Rx8wURK6cTRSkEg@mail.gmail.com>
2018-02-24 3:35 ` Trond Myklebust
2018-02-25 20:41 ` Steve Dickson
2018-02-25 23:47 ` J. Bruce Fields
2018-02-26 1:29 ` Trond Myklebust
2018-02-26 14:04 ` Steve Dickson
2018-02-26 15:06 ` bfields [this message]
2018-02-26 19:03 ` Steve Dickson
2018-02-26 19:58 ` bfields
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=20180226150641.GH15876@fieldses.org \
--to=bfields@fieldses.org \
--cc=SteveD@RedHat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=sumitgt@google.com \
--cc=trondmy@primarydata.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 NNTP newsgroup(s).