From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Istvan Gyurjan <istvan.gyurjan@flex.com>
Cc: "linux-sctp@vger.kernel.org" <linux-sctp@vger.kernel.org>
Subject: Re: lksctp-tools licensing
Date: Wed, 12 Oct 2022 18:04:04 -0300 [thread overview]
Message-ID: <20221012210404.v5e4cprel47nc5fm@t14s.localdomain> (raw)
In-Reply-To: <PH0PR08MB724105AD73E9AFB3F12A0679E7419@PH0PR08MB7241.namprd08.prod.outlook.com>
On Wed, Sep 07, 2022 at 10:32:38AM +0000, Istvan Gyurjan wrote:
> Dear lksctp-tools Maintainer team,
>
> We are planning to develop an application where lksctp-tools would be used together with other OSS components that uses Apache License 2.0 and The OpenSSL License. Those are in conflict with the GPL-2.0-only
> license of lksctp-tools.
> Do you have any plan to update the license to GPL-2.0-or-later?
Actually.. all the library files are LGPL. Isn't that enough already?
Marcelo
prev parent reply other threads:[~2022-10-12 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 10:32 lksctp-tools licensing Istvan Gyurjan
2022-09-27 20:30 ` Marcelo Ricardo Leitner
2022-09-27 21:20 ` Xin Long
2022-10-12 21:04 ` Marcelo Ricardo Leitner [this message]
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=20221012210404.v5e4cprel47nc5fm@t14s.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=istvan.gyurjan@flex.com \
--cc=linux-sctp@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).