mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rob Landley <landley@trommello.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"Adam J. Richter" <adam@yggdrasil.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: business models [was patent stuff]
Date: Mon, 3 Jun 2002 06:49:15 -0400	[thread overview]
Message-ID: <20020603171808.647527BD@merlin.webofficenow.com> (raw)
In-Reply-To: <200205290321.UAA01482@adam.yggdrasil.com> <1022678126.9255.182.camel@irongate.swansea.linux.org.uk>

On Wednesday 29 May 2002 09:15 am, Alan Cox wrote:

> I would worry much more about the million odd patents IBM have, where
> IBM have no general statement of this nature than the Red Hat ones.
> Perhaps once the Red Hat statement is published IBM can be persuaded to
> show willing ?

I'm is off dealing with patents from Sun, Sony, Apple, and Microsoft.  Their 
patent portfolio is like a nuclear arsenal: mutual assured destruction, so 
nobody actually uses their stockpile.

The down side of the GPL language handling patents implies that they more or 
less put a patent into the public domain.  I.E:

> Finally, any free program is threatened constantly by software patents. We 
> wish to avoid the danger that redistributors of a free program will 
> individually obtain patent licenses, in effect making the program 
> proprietary. To prevent this, we have made it clear that any patent must be 
> licensed for everyone's free use or not licensed at all. 

However, looking at the text of the license, it seems that it might be 
possible to issue a patent license allowing use for the patent only in GPL 
licensed programs.  (Thus IBM could issue a blanket statement saying that any 
of its patents may be used in GPL code, without necessarily unilaterally 
disarming itself with regards to Sony's patents.)

Opinions from Lessig and Stallman and a few random lawyers would be required 
to really get the issue decently clarified, though.  (It would be best if 
such a license could be a one-paragraph addendum to the GPL itself, perhaps a 
GPL V2.1?)  Using the GPL as a patent pool would be extremely useful to free 
software in the long run...

> > 	More importantly, licensing patents only for pure GPL'ed use
> > is unlikely to become a norm that you can expect broad adoption of
> > in free software businesses, as many of them tend to be proponents of
> > slightly different copying permissions.  If we have a bunch of patents
> > licensed for GPL-only, another bunch for MPL-only, another bunch for
> > pure-BSD only, then the patent proliferation that I described
> > yesterday will still probably occur.
>
> I would agree to an extent. Certainly purely GPL is excluding stuff
> which has identical 'all of package' rules like db3, Qt free editions,
> and much of KDE.

That said, a GPL-only patent license looks like the minimal set of permission 
grants required for a patent to be compatable with the GPL, and such a setup 
does start to turn the GPL into a patent pool anyone can join, which isn't 
entirely a bad thing...

And the existence of a less permissive license doesn't prevent the existence 
of a MORE permissive license.  (Dual GPL/BSD, for example...)

The whole patent issue is largely a matter of big fish using patent pools to 
exclude small fish.  A free software patent pool has been proposed repeatedly 
but never had the critical mass to get off the ground.  (On a related note, I 
entirely understand Red Hat seeking defensive patents due to the mexican 
standoff nature of the modern patent landscape, but hope they plan to use 
them wisely for the good of the community...)

Rob

  parent reply	other threads:[~2002-06-03 16:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29  3:21 Adam J. Richter
2002-05-29 13:15 ` Alan Cox
2002-05-29 14:13   ` Jonathan Corbet
2002-05-29 16:15     ` Jamie Lokier
2002-05-29 17:29       ` Nicholas Knight
2002-05-31 20:17         ` Perry The Cynic
2002-06-03 10:49   ` Rob Landley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-29 19:13 Adam J. Richter
2002-05-28 17:13 Adam J. Richter
2002-05-28 17:52 ` Daniel Phillips
2002-05-28 18:22 ` Alan Cox
2002-05-28 17:23   ` Andre Hedrick
2002-05-29 21:44   ` David Weinehall
2002-05-30  4:51     ` Greg KH
     [not found] <50.c105234.2a24c92d@aol.com>
2002-05-28 13:42 ` Gilad Ben-Yossef
2002-05-27 21:52 patent on O_ATOMICLOOKUP [Re: [PATCH] loopable tmpfs (2.4.17)] Adam J. Richter
2002-05-27 22:24 ` business models [was patent stuff] Larry McVoy
2002-05-27 23:15   ` Karim Yaghmour
2002-05-27 23:31     ` Austin Gonyou
2002-05-28  9:29     ` Peter Wächtler
2002-05-28 13:46       ` Mark Mielke
2002-05-29  8:34         ` Peter Wächtler
2002-05-28  7:53   ` Gilad Ben-Yossef
2002-05-28  8:57     ` Daniel Phillips
2002-05-28 11:30       ` Alan Cox
2002-05-28 10:32   ` Ingo Oeser
2002-05-28 12:28   ` Jonathan Corbet
2002-05-28 18:35   ` Eric W. Biederman

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=20020603171808.647527BD@merlin.webofficenow.com \
    --to=landley@trommello.org \
    --cc=adam@yggdrasil.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®