All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Taylor <steveftaylor@gmail.com>
To: ceph-devel@vger.kernel.org
Subject: Librbd licensing
Date: Fri, 30 May 2014 17:29:35 +0000 (UTC)	[thread overview]
Message-ID: <loom.20140530T192820-478@post.gmane.org> (raw)

I am working with a company that wants to utilize librbd in a project to
interact with Ceph storage. For the purposes of this integration,
LGPL-licensed open source code is acceptable, but GPL-licensed code is not.
Well, at least not without other changes to the project, which can be
accomplished if necessary.

The COPYING file distributed with the Ceph source code seems to indicate
that librbd would fall under LGPL 2.1, but some of the source files in
librbd reference GPL 2.1 in their copyright headers.

From what I have found so far, it appears to me that the sources in
question were probably originally LGPL, but were switched to GPL a few
years back to comply with FUSE licensing, which is GPL. Is my understanding
correct that these librbd source files are now GPL? If so and FUSE is the
reason behind it, is it possible to dual-license those files so they could
be LGPL when not used with FUSE?

I just want to make sure I understand the licensing properly. I apologize
if this has been discussed previously. I am new to the list and can't seem
to get the archive search feature to work.

Steve


             reply	other threads:[~2014-05-30 17:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-30 17:29 Steve Taylor [this message]
2014-05-30 17:43 ` Librbd licensing Sage Weil
2014-06-02 16:15   ` Steve Taylor
2014-06-02 17:02     ` Loic Dachary
2014-06-02 17:15       ` Steve Taylor
2014-06-02 17:22         ` Sage Weil
2014-06-02 18:00           ` Josh Durgin
2014-06-02 18:21             ` Gregory Farnum

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=loom.20140530T192820-478@post.gmane.org \
    --to=steveftaylor@gmail.com \
    --cc=ceph-devel@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.