From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Dmitry Kasatkin <dmitry.kasatkin@gmail.com>
Cc: linux-integrity@vger.kernel.org, a.mardegan@omp.ru,
git@andred.net, dbaryshkov@gmail.com, ebiggers@google.com,
sorenson@redhat.com, gcwilson@linux.ibm.com,
James.Bottomley@hansenpartnership.com, kgoldman@us.ibm.com,
zohar@linux.ibm.com, patrick.ohly@intel.com,
patrick@puiterwijk.org, petr.vorel@gmail.com,
roberto.sassu@huawei.com, stefanb@linux.ibm.com,
stephen.smalley.work@gmail.com, tianjia.zhang@linux.alibaba.com,
vt@altlinux.org, vgoyal@redhat.com, z.jasinski@samsung.com
Subject: Re: [ima-evm-utils: PATCH v1 1/1] Change license to LGPL-2.0-or-later and GPL-2.0-or-later
Date: Wed, 21 Feb 2024 08:18:40 +0000 [thread overview]
Message-ID: <ZdWx4CyUrnsMlzwA@srcf.ucam.org> (raw)
In-Reply-To: <9205ed32da8814d8c4d9bde5a03d92c7588f1d9a.1708503094.git.dmitry.kasatkin@gmail.com>
On Wed, Feb 21, 2024 at 10:11:34AM +0200, Dmitry Kasatkin wrote:
> Currently libimaevm provided by this project is used by the tool evmctl,
> which is also provided by this project.
>
> An issue was reported about using libimaevm with other software. Its
> GPL2-only license makes it incompatible to use with other licenses, in
> particular GPL3-only.
>
> To address this issue, change the project license to GPL-2.0-or-later
> and libimaevm to LGPL 2.0 or later.
I'm completely supportive of this, but do you need explicit permission
from every copyright holder? I don't think I have any code in the
library, but if I did it probably technically belongs to a former
employer and I'd need to figure out who's still employed in the relevant
office to get them to agree.
next prev parent reply other threads:[~2024-02-21 8:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 8:11 [ima-evm-utils: PATCH v1 1/1] Change license to LGPL-2.0-or-later and GPL-2.0-or-later Dmitry Kasatkin
2024-02-21 8:18 ` Matthew Garrett [this message]
2024-02-21 13:35 ` Dmitry Kasatkin
2024-02-21 9:28 ` Petr Vorel
2024-02-21 13:37 ` Dmitry Kasatkin
2024-02-23 17:42 ` Mimi Zohar
2024-02-23 17:43 ` Stefan Berger
2024-02-23 23:51 ` James Bottomley
2024-02-23 18:30 ` Vitaly Chikunov
2024-02-23 21:54 ` Ken Goldman
2024-02-25 15:14 ` Bruno Meneguele
2024-02-26 16:07 ` Roberto Sassu
2024-02-26 16:21 ` George Wilson
2024-02-26 20:27 ` Tergel Myanganbayar
2024-02-26 21:26 ` André Draszik
2024-02-29 20:58 ` Frank Sorenson
2024-03-01 16:10 ` Stephen Smalley
2024-03-13 14:44 ` Vivek Goyal
2024-03-14 14:11 ` Mimi Zohar
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=ZdWx4CyUrnsMlzwA@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=a.mardegan@omp.ru \
--cc=dbaryshkov@gmail.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=ebiggers@google.com \
--cc=gcwilson@linux.ibm.com \
--cc=git@andred.net \
--cc=kgoldman@us.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=patrick.ohly@intel.com \
--cc=patrick@puiterwijk.org \
--cc=petr.vorel@gmail.com \
--cc=roberto.sassu@huawei.com \
--cc=sorenson@redhat.com \
--cc=stefanb@linux.ibm.com \
--cc=stephen.smalley.work@gmail.com \
--cc=tianjia.zhang@linux.alibaba.com \
--cc=vgoyal@redhat.com \
--cc=vt@altlinux.org \
--cc=z.jasinski@samsung.com \
--cc=zohar@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox