From: Jamie Lokier <jamie@shareable.org>
To: Harald Welte <laforge@gnumonks.org>
Cc: Ben Slusky <sluskyb@paranoiacs.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-fsdevel@vger.kernel.org, legal@lists.gnumonks.org,
"Robert W. Fuller" <garbageout@sbcglobal.net>,
LKML Kernel <linux-kernel@vger.kernel.org>,
Kyle Moffett <mrmacman_g4@mac.com>,
info@crossmeta.com
Subject: Re: blatant GPL violation of ext2 and reiserfs filesystem drivers
Date: Wed, 4 Jan 2006 11:54:22 +0000 [thread overview]
Message-ID: <20060104115422.GA2562@mail.shareable.org> (raw)
In-Reply-To: <20060104110929.GH4898@sunbeam.de.gnumonks.org>
Harald Welte wrote:
> > The case here appears to be:
> >
> > * Crossmeta offers "add-on" software as a free download from their web
> > site: <URL:http://www.crossmeta.com/downloads/crossmeta-add-1_0.zip>.
> > The zip file contains a text file gpl-license.txt, which says that the
> > add-ons are offered under the terms of the GPL.
> >
> > * User downloads this GPLed software and asks the developer to provide
> > source code. Developer replies that the source code will be provided
> > only to paying customers:
> > <URL:http://www.opensolaris.org/jive/message.jspa?messageID=12277#12277>.
> >
> > That's baad, m'kay?
>
> This is definitely not acceptable. A written offer must be valid to ANY
> 3RD PARTY.
>
> So it wouldn't even be enough to offer the source code to paying
> customers and those who downloaded the binary code, but actually it must
> be made available to anyone who asks for it.
Ah, that depends on whether they provided the source code for download
to paying customers at the time those customers downloaded the binary.
GPL section 3:
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
What this means is that if you make the source code available
alongside the binary, e.g. on a web site under the same conditions of
access, you don't need to provide the written offer to all 3rd
parties; indeed, you don't need to provide the written offer at all.
The above description of what Crossmeta did doesn't clearly say if
Crossmeta provided their customers with the binary and an offer to get
source on request (the written offer), or if those paying customers
were able to download the source at the same time as the binaries.
-- Jamie
next prev parent reply other threads:[~2006-01-04 11:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 16:08 blatant GPL violation of ext2 and reiserfs filesystem drivers Robert W. Fuller
2005-12-22 18:01 ` Kyle Moffett
2005-12-22 20:27 ` Steven Rostedt
2005-12-22 23:12 ` Jeff V. Merkey
2005-12-23 2:56 ` Chris Wedgwood
2005-12-23 3:15 ` Diego Calleja
2005-12-23 3:28 ` Chris Wedgwood
2005-12-23 3:38 ` Steven Rostedt
2005-12-23 3:49 ` Matthew Wilcox
2005-12-23 4:25 ` Jamie Lokier
2005-12-23 3:30 ` Adrian Bunk
2005-12-23 15:35 ` Ben Slusky
2005-12-23 19:34 ` Bryan Henderson
2005-12-23 20:16 ` Scott Mansfield
2005-12-23 22:00 ` Bryan Henderson
2005-12-24 1:48 ` Horst von Brand
2005-12-24 2:41 ` Peter Williams
2005-12-24 3:25 ` Jamie Lokier
2006-01-04 11:09 ` Harald Welte
2006-01-04 11:54 ` Jamie Lokier [this message]
2006-01-04 13:18 ` Harald Welte
2006-01-04 13:46 ` Matthew Wilcox
2006-01-04 17:46 ` Harald Welte
2006-01-04 23:03 ` Gene Heskett
2006-01-04 22:43 ` Jeff V. Merkey
2006-01-04 14:16 ` Jamie Lokier
2006-01-04 14:45 ` Matthew Wilcox
2006-01-04 15:57 ` Jamie Lokier
2006-01-04 17:42 ` Harald Welte
2006-01-05 17:52 ` Bryan Henderson
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=20060104115422.GA2562@mail.shareable.org \
--to=jamie@shareable.org \
--cc=garbageout@sbcglobal.net \
--cc=info@crossmeta.com \
--cc=laforge@gnumonks.org \
--cc=legal@lists.gnumonks.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
--cc=rostedt@goodmis.org \
--cc=sluskyb@paranoiacs.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