public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Lehmann <pcg@schmorp.de>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Cameron Patrick <cameron@patrick.wattle.id.au>,
	Michael Frank <mhf@linuxmail.org>, Pavel Machek <pavel@suse.cz>,
	Software Suspend - Mailing Lists 
	<swsusp-devel@lists.sourceforge.net>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [Swsusp-devel] lzf license
Date: Mon, 22 Mar 2004 19:21:21 +0100	[thread overview]
Message-ID: <20040322182121.GA21521@schmorp.de> (raw)
In-Reply-To: <1079948988.5296.8.camel@laptop.fenrus.com>

On Mon, Mar 22, 2004 at 10:49:48AM +0100, Arjan van de Ven <arjanv@redhat.com> wrote:
> > The licence so described looks to me the same as LZF's licence.
> 
> however at least I would prefer the author to dual license it ANYWAY,
> because compression stuff generally is riddled with patents; the author
> GPL licensing it at least gives all users a license of the authors
> patents (if any). 

I would like to avoid dual-licensing and instead change the existing
license to suit any needs, if at all possible. (Note that relicensing
should be possible, at least this was my original goal).

If patents are an issue, how about adding this:

   4. The author is unaware of any existing patents and disclaims any
      patents, or other restrictions, on the LZF algorithm or this
      implementation.

I would add this clause to both future lzf distributions as well as the
file that is part of the lzf patch.

If there are unavoidable reasons why the GPL is required, then I'd bite
the bullet and dual-license it, in the hope that further bugfixes or
modifications will be contributed under both licenses.

-- 
      -----==-                                             |
      ----==-- _                                           |
      ---==---(_)__  __ ____  __       Marc Lehmann      +--
      --==---/ / _ \/ // /\ \/ /       pcg@goof.com      |e|
      -=====/_/_//_/\_,_/ /_/\_\       XX11-RIPE         --+
    The choice of a GNU generation                       |
                                                         |

  parent reply	other threads:[~2004-03-23 11:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-22  9:18 Michael Frank
2004-03-22  9:40 ` [Swsusp-devel] (no subject) Cameron Patrick
2004-03-22  9:49   ` Arjan van de Ven
2004-03-22 10:02     ` LZF inclusion in kernel Michael Frank
2004-03-22 18:21     ` Marc Lehmann [this message]
2004-03-23 11:47       ` [Swsusp-devel] lzf license Arjan van de Ven
2004-03-25 15:02         ` Marc Lehmann
2004-03-24 22:20       ` Nigel Cunningham
2004-03-25 14:26         ` Marc Lehmann
2004-03-25 14:56           ` Pavel Machek
2004-03-28  0:43             ` Marc Lehmann
2004-03-22 10:15   ` [Swsusp-devel] (no subject) Pavel Machek
2004-03-25 15:18 ` Marc Lehmann

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=20040322182121.GA21521@schmorp.de \
    --to=pcg@schmorp.de \
    --cc=arjanv@redhat.com \
    --cc=cameron@patrick.wattle.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhf@linuxmail.org \
    --cc=pavel@suse.cz \
    --cc=swsusp-devel@lists.sourceforge.net \
    /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