From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Chris Perkins <cperkins@medialab.com>
Cc: Joshua Juran <jjuran@gmail.com>,
Daniel Searles <daniel.paul.searles@gmail.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 19:34:10 -0700 [thread overview]
Message-ID: <86r595ef31.fsf@red.stonehenge.com> (raw)
In-Reply-To: <4DA65BB6.5080909@medialab.com> (Chris Perkins's message of "Wed, 13 Apr 2011 23:28:06 -0300")
>>>>> "Chris" == Chris Perkins <cperkins@medialab.com> writes:
>> Which part, then? Name chapter and verse.
Chris> Section 2 b). I quoted it in whole in my email:
Chris> 2 b) You must cause any work that you distribute or publish,
Chris> that in whole or in part contains or is derived from the Program
Chris> or any part thereof, to be licensed as a whole at no charge to
Chris> all third parties under the terms of this License.
Broken pre-condition. See the beginning of 2:
2. You may modify your copy or copies of the Program or any portion of
it, thus forming a work based on the Program, and copy and distribute
such modifications or work under the terms of Section 1 above, provided
that you also meet all of these conditions:
Gitbox is not *modifying*, or creating a work *based on the Program*.
Separate copyrights. The rest of your argument thus falls apart.
Chris> However, that said, I still think it's a violation of the GPL. That
Chris> license lays it out very clearly without much room for
Chris> interpretation.
Bullcrap. See above. Get your preconditions right, and I'll play along.
Chris> You can't make commercial works based on GPL licensed software.
Sure you can. RedHat makes money somehow. Don't play the "we must be
starving artists for the cause of GPL" on me.
Chris> But I will add this, some on our team would very much like to
Chris> incorporate Git into one of our own upcoming commercial products.
Chris> Code-wise in the same manner as Gitbox has done. But we aren't going to
Chris> do this, because the GPL license for Git clearly states that we
Chris> cannot.
Maybe you need better lawyers then.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.posterous.com/ for Smalltalk discussion
next prev parent reply other threads:[~2011-04-14 2:34 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 ` Gitbox Chris Perkins
2011-04-14 2:34 ` Randal L. Schwartz [this message]
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=86r595ef31.fsf@red.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.