From: Chuck Lever <chuck.lever@oracle.com>
To: kernel-tls-handshake <kernel-tls-handshake@lists.linux.dev>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
netdev@vger.kernel.org
Subject: ktls-utils project change in Contributor's agreement
Date: Mon, 19 May 2025 11:20:40 -0400 [thread overview]
Message-ID: <2d9c6d1d-81a8-4c57-ba0a-40a2f5d5fcb4@oracle.com> (raw)
I am pleased to announce that Oracle has allowed us to remove the
requirement for non-Oracle contributors to ktls-utils to sign the Oracle
Contributor's Agreement. Please see commit:
https://github.com/oracle/ktls-utils/commit/e9b0b68439a497c3055f3be32aaf58e5a6765c30
The only contribution requirement is now the same as the Linux kernel:
an acknowledgement of the developer certification of origin via a
Signed-off-by: tag in the patch description.
This change is in recognition that ktls-utils has become a critical part
of the Linux kernel's security infrastructure. We wish to continue to
reduce the friction needed to contribute to the ktls-utils code base.
I thank Greg Marsden for making this happen, and many thanks to all
contributors to the oracle/ktls-utils project.
--
Chuck Lever
reply other threads:[~2025-05-19 15:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2d9c6d1d-81a8-4c57-ba0a-40a2f5d5fcb4@oracle.com \
--to=chuck.lever@oracle.com \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@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