From: Loic Dachary <loic@dachary.org>
To: Steve Taylor <steveftaylor@gmail.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Librbd licensing
Date: Mon, 02 Jun 2014 19:02:12 +0200 [thread overview]
Message-ID: <538CAE14.4060602@dachary.org> (raw)
In-Reply-To: <CADXiVcpM8GJcCbDkdOPWzXPoJrDdyiQn0-q4nDH6o0zpg_u8gg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3826 bytes --]
Hi,
The missing "Lesser" is a nice typo :-) There has never been a GPLv2.1 ( https://en.wikipedia.org/wiki/GNU_General_Public_License#Version_2 ) and I guess it helps disambiguate the interpretation.
Cheers
On 02/06/2014 18:15, Steve Taylor wrote:
> Sorry, my previous reply was rejected by the list because it wasn't in
> plain text. Let's try again.
>
> librbd.cc:
> /*
> * Ceph - scalable distributed file system
> *
> * Copyright (C) 2011 New Dream Network
> *
> * This is free software; you can redistribute it and/or
> * modify it under the terms of the GNU General Public
> * License version 2.1, as published by the Free Software
> * Foundation. See file COPYING.
> *
> */
>
> librbd.h:
> /*
> * Ceph - scalable distributed file system
> *
> * Copyright (C) 2011 New Dream Network
> *
> * This is free software; you can redistribute it and/or
> * modify it under the terms of the GNU General Public
> * License version 2.1, as published by the Free Software
> * Foundation. See file COPYING.
> *
> */
>
> librbd.hpp:
> /*
> * Ceph - scalable distributed file system
> *
> * Copyright (C) 2011 New Dream Network
> *
> * This is free software; you can redistribute it and/or
> * modify it under the terms of the GNU General Public
> * License version 2.1, as published by the Free Software
> * Foundation. See file COPYING.
> *
> */
>
> These are the three that I've noticed poking around librbd so far. My
> understanding from COPYING is that they should be LGPL, but these
> copyright headers obviously state GPL instead. I'm just trying to
> understand definitely which it is. :)
>
> If a change is in order, of course I'll be happy to make the change
> myself and submit a pull request if you like.
>
> Steve
>
> On Fri, May 30, 2014 at 11:43 AM, Sage Weil <sage@inktank.com> wrote:
>> Hi Steve,
>>
>> On Fri, 30 May 2014, Steve Taylor wrote:
>>> 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.
>>
>> Which files? If there are disparities we should correct them. To the best
>> of my knowledge everything in librbd is LGPL.
>>
>> Thanks!
>> sage
>>
>>
>>>
>>> >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
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2014-06-02 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 17:29 Librbd licensing Steve Taylor
2014-05-30 17:43 ` Sage Weil
2014-06-02 16:15 ` Steve Taylor
2014-06-02 17:02 ` Loic Dachary [this message]
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=538CAE14.4060602@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=steveftaylor@gmail.com \
/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.