From: Chris Mason <chris.mason@oracle.com>
To: ivo welch <ivowel@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: licenses (for apple OSX and others)?
Date: Mon, 15 Aug 2011 11:15:05 -0400 [thread overview]
Message-ID: <1313420602-sup-9846@shiny> (raw)
In-Reply-To: <CAPr7RtVfNtNno=7KTJvyvNFnkumHd3PiJSo8eoswBZT-0vwFQA@mail.gmail.com>
Excerpts from ivo welch's message of 2011-08-14 20:34:14 -0400:
> curiosity question---could btrfs be licensed in multiple ways to allow
> Apple and other vendors to adopt it? as end users, having one good
> file system that works everywhere as a main root system would be
> heaven...
One of the ways you can tell people like the project is when they wish
they could use it everywhere. Thanks for this question ;)
There are a few problems with relicensing btrfs under something other
than the GPL.
Large parts of the btrfs code that deal with the VFS were copied from
ext2 and ext3. These are GPL and would have to be reimplemented. The
code that deals with the page cache was also lifted and adapted from
different parts of the kernel, and it is surprising how far the roots of
the page cache spread into the rest of the code.
More importantly, btrfs has major contributions from many companies and
individuals. I intentionally set things up so there wouldn't be a
single place you could go and say 'xyz' owns the btrfs code, we'll
ask them for permission.
Just like most of the kernel, we have maintainers and contributors,
but not a single owner. This is a big part of why others feel
comfortable contributing to btrfs, and to be honest it's one of my
favorite parts of the project.
None of this prevents others from using btrfs outside of linux, but if
they do it'll be under the GPL.
-chris
next prev parent reply other threads:[~2011-08-15 15:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 0:34 licenses (for apple OSX and others)? ivo welch
2011-08-15 2:00 ` Edward Ned Harvey
2011-08-15 2:27 ` ivo welch
2011-08-15 2:53 ` Billy Crook
2011-08-15 5:54 ` C Anthony Risinger
2011-08-15 7:40 ` Roman Mamedov
2011-08-15 15:15 ` Chris Mason [this message]
2011-08-15 17:39 ` Billy Crook
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=1313420602-sup-9846@shiny \
--to=chris.mason@oracle.com \
--cc=ivowel@gmail.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.