From: Andy Grover <agrover@redhat.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Btrfs-progs Relicensing effort has begun
Date: Wed, 15 Jan 2014 10:18:59 -0800 [thread overview]
Message-ID: <52D6D113.10308@redhat.com> (raw)
Hi all,
We want to relicense btrfs-progs, using the LGPLv2.1 instead of GPLv2.
We can then build btrfs-progs code as a shared library, libbtrfs, and
this library can be used by other code -- GPLv3+, BSD/Apache, and
non-free, without causing the GPLv2 to apply to the other code.
This will allow btrfs support to be more tightly integrated into other
management tools.
Chris Mason, as well as Oracle, have approved this change and are
on-board, but we also need *all* contributors to agree.
I will be emailing all contributors (as shown by git) over the next few
weeks. Progress will be shown here:
https://docs.google.com/spreadsheet/ccc?key=0AuE18RMM7JeKdFF4OVdsYU9GVmVEOGNKajdPYThHSWc&usp=sharing
Instead of waiting for the email, you can also email me now
(agrover@redhat.com) with the below phrase, or something similar:
-I grant permission to re-license my contributed code to btrfs-progs
under the GNU LGPLv2.1 license.-
or with any questions.
Thanks! -- Regards -- Andy
reply other threads:[~2014-01-15 18:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52D6D113.10308@redhat.com \
--to=agrover@redhat.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.