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 14:58:25 -0500 [thread overview]
Message-ID: <20180226195825.GA26808@fieldses.org> (raw)
In-Reply-To: <da8e26ae-aea8-3fd9-2c6e-865f4f85a6d4@RedHat.com>
On Mon, Feb 26, 2018 at 02:03:41PM -0500, Steve Dickson wrote:
> You forgot got to end with... "grasshopper" ;-)
Hah.
> I understand your point... but the old owners would not care if
> we put up a sign to invite more people to the picnic, true?
>
> So I guess the main concern is if Google add the license they
> would own the code and could revoke the use of it down the
> road... hmm.
>
> So since this code has never been licensed, it an never be licensed?
You don't have to do anything special to get copyright in something you
created[1]. And you can't give away copyright without explicitly saying
you are[2]. So the original authors of the code (or their employers)
still hold copyright.
So, no, nobody can just claim they're taking ownership and then use that
to revoke permissions later.
There was never any license on most of it, so we're just assuming we can
get away with continuing to use it the way we used to.
Yeah, I'm just an amateur here, but I'm not hearing anyone claiming to
be an expert, so we should let this be until one happens along.
--b.
[1] https://en.wikipedia.org/wiki/Copyright_formalities#Shift_away_from_formalities
[2] https://www.copyright.gov/title17/92chap2.html#204
prev parent reply other threads:[~2018-02-26 19:58 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
2018-02-26 19:03 ` Steve Dickson
2018-02-26 19:58 ` bfields [this message]
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=20180226195825.GA26808@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).