From: Cleber Rosa <crosa@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
"Daniel Berrange" <berrange@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
qemu-devel@nongnu.org, "Luiz Capitulino" <lcapitulino@redhat.com>,
"Marc-André Lureau" <mlureau@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
"Eduardo Habkost" <ehabkost@habkost.com>
Subject: Re: [PATCH 3/4] python/qmp-shell: relicense as LGPLv2+
Date: Wed, 30 Mar 2022 12:37:04 -0400 [thread overview]
Message-ID: <87sfqz75wk.fsf@p50.localhost.localdomain> (raw)
In-Reply-To: <20220325200438.2556381-4-jsnow@redhat.com>
John Snow <jsnow@redhat.com> writes:
> qmp-shell is presently licensed as GPLv2 (only). I intend to include
> this tool as an add-on to an LGPLv2+ library package hosted on
> PyPI.org. I've selected LGPLv2+ to maximize compatibility with other
> licenses while retaining a copyleft license.
>
> To keep licensing matters simple, I'd like to relicense this tool as
> LGPLv2+ as well in order to keep the resultant license of the hosted
> release files simple -- even if library users won't "link against" this
> command line tool.
>
> Therefore, I am asking permission from the current authors of this
> tool to loosen the license. At present, those people are:
>
> - John Snow (me!), 411/609
> - Luiz Capitulino, Author, 97/609
> - Daniel Berrangé, 81/609
> - Eduardo Habkost, 10/609
> - Marc-André Lureau, 6/609
> - Fam Zheng, 3/609
> - Cleber Rosa, 1/609
>
> (All of which appear to have been written under redhat.com addresses.)
>
> Eduardo's fixes are largely automated from 2to3 conversion tools and may
> not necessarily constitute authorship, but his signature would put to
> rest any questions.
>
> Cleber's changes concern a single import statement change. Also won't
> hurt to ask.
>
> CC: Luiz Capitulino <lcapitulino@redhat.com>
> CC: Daniel Berrange <berrange@redhat.com>
> CC: Eduardo Habkost <ehabkost@habkost.com>
> CC: Marc-André Lureau <mlureau@redhat.com>
> CC: Fam Zheng <fam@euphon.net>
> CC: Cleber Rosa <crosa@redhat.com>
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
> python/qemu/aqmp/qmp_shell.py | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
Acked-by: Cleber Rosa <crosa@redhat.com>
next prev parent reply other threads:[~2022-03-30 16:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 20:04 [PATCH 0/4] Python: relicense async qmp as LGPLv2+ John Snow
2022-03-25 20:04 ` [PATCH 1/4] python/aqmp: add explicit GPLv2 license to legacy.py John Snow
2022-03-25 20:04 ` [PATCH 2/4] python/aqmp: relicense as LGPLv2+ John Snow
2022-03-25 20:04 ` [PATCH 3/4] python/qmp-shell: " John Snow
2022-03-27 8:45 ` Marc-André Lureau
2022-03-29 11:08 ` Fam Zheng
2022-03-29 16:09 ` John Snow
2022-03-29 16:43 ` Luiz Capitulino
2022-03-30 1:59 ` Eduardo Habkost
2022-03-30 15:06 ` Daniel P. Berrangé
2022-03-30 15:46 ` John Snow
2022-03-30 16:37 ` Cleber Rosa [this message]
2022-03-25 20:04 ` [PATCH 4/4] python/aqmp-tui: " John Snow
2022-03-26 15:27 ` Niteesh G. S.
2022-03-29 16:05 ` John Snow
2022-03-30 17:04 ` [PATCH 0/4] Python: relicense async qmp " John Snow
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=87sfqz75wk.fsf@p50.localhost.localdomain \
--to=crosa@redhat.com \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=eblake@redhat.com \
--cc=ehabkost@habkost.com \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mlureau@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).