All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Grover <agrover@redhat.com>
To: linux-btrfs@vger.kernel.org
Cc: Chris Mason <chris.mason@fusionio.com>
Subject: btrfs.h and btrfs-progs licensing
Date: Mon, 09 Sep 2013 14:13:50 -0700	[thread overview]
Message-ID: <522E3A0E.6080504@redhat.com> (raw)

Hi everybody,

I'd like it to be possible to have a library that configures btrfs 
directly instead of using the cmdline tools. (I think Mark Fasheh and 
David Sterba have already done some work here.)

However, as it stands, the kernel's include/uapi/linux/btrfs.h and 
btrfs-progs are GPLv2, which means that a "libbtrfs" that is based on 
either of these might also be construed to need to be GPLv2, and any 
program *using* libbtrfs might also be construed to need to be GPLv2.

I don't think this was the intent.

I think we'd be better off if we relicense btrfs-progs to LGPLv2, and 
dual-license the kernel btrfs.h header to GPLv2/LGPLv2 (this may not be 
strictly necessary, RMS says it isn't[1], but we probably want to be 
completely clear).

This will involve getting the OK from everyone who has contributed to 
btrfs-progs. Yay git. If someone more closely involved with btrfs dev 
wanted to spearhead this I'd love it, but am willing to do it too (I 
*really* want a libbtrfs. :-)

Any thoughts? Objections?

Regards -- Andy

[1] http://lkml.indiana.edu/hypermail/linux/kernel/0301.1/0362.html

             reply	other threads:[~2013-09-09 21:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-09 21:13 Andy Grover [this message]
2013-09-09 22:50 ` btrfs.h and btrfs-progs licensing David Sterba
2013-09-10 15:31   ` ronnie sahlberg

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=522E3A0E.6080504@redhat.com \
    --to=agrover@redhat.com \
    --cc=chris.mason@fusionio.com \
    --cc=linux-btrfs@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 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.