From: Chris Perkins <cperkins@medialab.com>
To: Chris Perkins <cperkins@medialab.com>
Cc: Joshua Juran <jjuran@gmail.com>,
Daniel Searles <daniel.paul.searles@gmail.com>,
"Randal L. Schwartz" <merlyn@stonehenge.com>,
Drew Northup <drew.northup@maine.edu>,
oleganza@gmail.com, Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Daniel Searles <dsearles@medialab.com>
Subject: Re: Gitbox
Date: Wed, 13 Apr 2011 23:28:06 -0300 [thread overview]
Message-ID: <4DA65BB6.5080909@medialab.com> (raw)
In-Reply-To: <4DA654D4.5040104@medialab.com>
On 4/13/11 11:02 PM, Randal L. Schwartz wrote:
>>>>>> "Chris" == Chris Perkins <cperkins@medialab.com> writes:
>
> Chris> Is that a violation of the GPL? I would say that it absolutely
> Chris> is.
>
> Which part, then? Name chapter and verse.
Section 2 b). I quoted it in whole in my email:
2 b) You must cause any work that you distribute or publish,
that in whole or in part contains or is derived from the Program
or any part thereof, to be licensed as a whole at no charge to
all third parties under the terms of this License.
and the last paragraph in the "how to" section is even more frank.
> But if the GPL is to be treated as a legally enforceable document, "live
> by the sword, and die by the sword". GPL-desk-pounders can't have it
> both ways.
I'm not a GPL-desk-pounder. I write commercial software for a living.
But I take the efforts I put into my software very seriously. If I were
to release software as free software under a license like the GPL I
would not appreciate someone attempting to profit off my hard work by
putting a bow on it and selling it as their own.
Don't get me wrong. I don't see Gitbox as just a 'bow' atop Git.
Frankly, the type of wrapping that Gitbox is doing seems perfectly
reasonable to me. Gitbox is providing real value to users, it's not
disguising or hiding Git and it's not pretending to be provide the work
of Git as its own and it isn't trying to pretend to be anything that it
isn't.
However, that said, I still think it's a violation of the GPL. That
license lays it out very clearly without much room for interpretation.
You can't make commercial works based on GPL licensed software. Without
Git there is no Gitbox. End of story.
I'm not a lawyer, were I then perhaps I'd know solidly one way or other.
I'm not the author nor one of the contributors to Git. Were I then
perhaps I might feel differently about Gitbox being 'perfectly reasonable'.
But I will add this, some on our team would very much like to
incorporate Git into one of our own upcoming commercial products.
Code-wise in the same manner as Gitbox has done. But we aren't going to
do this, because the GPL license for Git clearly states that we cannot.
Chris
next prev parent reply other threads:[~2011-04-14 2:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTikfCDm-5Yde=2Cm-ROc1dcMwopvOg@mail.gmail.com>
2011-04-13 22:23 ` Gitbox Joshua Juran
2011-04-14 1:58 ` Gitbox Chris Perkins
2011-04-14 2:02 ` Gitbox Randal L. Schwartz
2011-04-14 2:28 ` Chris Perkins [this message]
2011-04-14 2:34 ` Gitbox Randal L. Schwartz
2011-04-14 4:59 ` Gitbox Joshua Juran
2011-04-14 13:55 ` Gitbox Martin Langhoff
[not found] ` <32803572.1897.1302789371873.JavaMail.trustmail@mail1.terreactive.ch>
2011-04-14 14:15 ` Gitbox Victor Engmark
2011-04-14 14:52 ` Gitbox Martin Langhoff
2011-04-15 19:21 ` Gitbox Tim Smith
2011-04-13 18:16 Gitbox Daniel Searles
2011-04-13 18:55 ` Gitbox Joshua Juran
2011-04-13 18:59 ` Gitbox Drew Northup
2011-04-13 19:09 ` Gitbox Joshua Juran
2011-04-13 19:16 ` Gitbox Drew Northup
2011-04-13 19:24 ` Gitbox Joshua Juran
2011-04-13 19:41 ` Gitbox Randal L. Schwartz
2011-04-13 20:04 ` Gitbox Drew Northup
2011-04-13 20:26 ` Gitbox Taylor Hedberg
2011-04-13 20:29 ` Gitbox Joshua Juran
2011-04-13 22:56 ` Gitbox Tim Smith
2011-04-14 9:52 ` Gitbox Sitaram Chamarty
2011-04-14 10:03 ` Gitbox Vincent van Ravesteijn
2011-04-14 12:34 ` Gitbox Drew Northup
2011-04-13 20:43 ` Gitbox Junio C Hamano
[not found] ` <1C18B4FB-BB10-4AC7-8952-D477CB4EF289@medialab.com>
2011-04-13 22:13 ` Gitbox Randal L. Schwartz
2011-04-13 23:10 ` Gitbox Randal L. Schwartz
2011-04-13 19:18 ` Gitbox Jakub Narebski
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=4DA65BB6.5080909@medialab.com \
--to=cperkins@medialab.com \
--cc=daniel.paul.searles@gmail.com \
--cc=drew.northup@maine.edu \
--cc=dsearles@medialab.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jjuran@gmail.com \
--cc=merlyn@stonehenge.com \
--cc=oleganza@gmail.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).