From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Philip Oakley <philipoakley@iee.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Jonathan Smith <Jonathan.Smith@fphcare.co.nz>,
git@vger.kernel.org
Subject: Re: GPL v2 authoritative answer on stored code as a derived work
Date: Thu, 28 Jan 2016 09:16:45 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1601280913450.2964@virtualbox> (raw)
In-Reply-To: <C0429EC95C2F44528E2A1336FB7A2D98@PhilipOakley>
Hi Philip,
On Wed, 27 Jan 2016, Philip Oakley wrote:
> From: "Junio C Hamano" <gitster@pobox.com>
> > Jonathan Smith <Jonathan.Smith@fphcare.co.nz> writes:
> >
> > > It's pretty clear that code stored in a Git repository isn't
> > > considered a derived work of Git, regardless of whether it is used
> > > in a commercial context or otherwise.
>
> I'm guessing here, but I suspect that while its 'pretty clear' to Jonathan,
> that he has met others who aren't so clear or trusting, and it's that
> distrustful community that would need convincing.
It is not so much distrust as something you could take to court, I guess,
because an *authoritative* answer was asked for. Now, the question is a
legal one, so it is pretty clear (;-)) to me that only a lawyer could give
that answer.
Having said that, I know of plenty of companies storing their proprietary
code in Git repositories, and I would guess that they cleared that with
their lawyers first.
Jonathan, please do not take that as any indication that I try to give
this answer: if you want an authoritative answer to your question, you
really need to consider asking a lawyer.
Ciao,
Dscho
next prev parent reply other threads:[~2016-01-28 8:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 3:08 GPL v2 authoritative answer on stored code as a derived work Jonathan Smith
2016-01-25 19:06 ` Junio C Hamano
2016-01-27 23:58 ` Philip Oakley
2016-01-28 8:16 ` Johannes Schindelin [this message]
2016-01-31 20:51 ` Philip Oakley
2016-01-31 21:00 ` [RFC/PATCH] Git doc: GPL2 does not apply to repo data Philip Oakley
2016-01-31 22:08 ` Junio C Hamano
2016-01-31 22:15 ` Jonathan Smith
2016-02-01 7:35 ` Johannes Schindelin
2016-02-01 7:49 ` Matthieu Moy
2016-02-01 8:14 ` Jeff King
2016-02-01 8:16 ` Jeff King
2016-02-01 10:57 ` Philip Oakley
2016-02-01 10:53 ` Philip Oakley
2016-02-01 11:34 ` Philip Oakley
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=alpine.DEB.2.20.1601280913450.2964@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=Jonathan.Smith@fphcare.co.nz \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=philipoakley@iee.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 NNTP newsgroup(s).