From: Victor Engmark <victor.engmark@terreactive.ch>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Chris Perkins <cperkins@medialab.com>,
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: Thu, 14 Apr 2011 16:15:11 +0200 [thread overview]
Message-ID: <4DA7016F.5070308@terreactive.ch> (raw)
In-Reply-To: <32803572.1897.1302789371873.JavaMail.trustmail@mail1.terreactive.ch>
On 04/14/2011 03:55 PM, Martin Langhoff wrote:
> On Wed, Apr 13, 2011 at 9:58 PM, Chris Perkins <cperkins@medialab.com> wrote:
>> Let's look at this at a slighty different way. Let's say someone writes
>> a GUI wrapper for Git, bundles it with Git, and then offers for sale a
>> new proprietary SVC system. They list off all the wonderful features
>> that it has. On the back page of their website is a small 'Licenses'
>> disclosure and the source code to Git comes with the download buried in
>> a subdirectory. None of the users realize the software is using Git.
>>
>> Is that a violation of the GPL? I would say that it absolutely is.
>
> It absolutely is not. Lots of companies do this, and it is perfectly
> kosher -- either bundle the src somewhere or offer a link to download
> the source somewhere.
>
> While IANAL, and specifically not _your_ lawyer, I have been in this
> field for >10 years, and studied law @ masters level on software
> licensing. You are reading the GPL wrong, and you're not aware of
> widespread industry practices around it.
>
> Anyone who is curious about this gitbox thing, and interested in
> *facts* instead of fiction, could advance our knowledge with a simple
> procedure:
>
> - Download the "free" version (or payfor the paid version!). It's a
> zipfile, no need to hurt any Macs.
>
> - See if it includes the src or a link to download the src -- it will
> probably be in a corner of the documentation or license. Maybe there's
> an offer to provide the src in a different way, but a download link is
> the usual trick.
>
> - Does the link work? Can you effectively get the src?
>
> - Does the src match the binaries you got?
Excellent answer; it would be great to know in detail what would be an
effective (and efficient, if possible) procedure for validating GPL
compliance. Something like a cartoon guide to the GPL for developers
and/or users. I don't even know if my own GPL'ed projects are within the
letter of the law here.
--
Victor
next prev parent reply other threads:[~2011-04-14 14:16 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 ` 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 ` Victor Engmark [this message]
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=4DA7016F.5070308@terreactive.ch \
--to=victor.engmark@terreactive.ch \
--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=martin.langhoff@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).