From: James Morris <jmorris@namei.org>
To: linux-security-module@vger.kernel.org
Subject: Maintainer update
Date: Thu, 7 Jul 2022 04:56:31 +1000 (AEST) [thread overview]
Message-ID: <c513dcdb-17f9-377a-1329-2b8fee8dc28c@namei.org> (raw)
Hi Folks,
I'm now a manager and don't get as much time to focus directly on
development work.
I'd like to propose that we add Paul Moore as a maintainer of the Security
Subsystem, and for him to take the lead on that, in addition to his
SELinux and other maintainer work.
With LSMs pushing directly to Linus, this maintainer role is now mostly
about merging new LSMs and major LSM changes, and integrating bugfixes.
Paul has been taking many LSM bugfixes through his SELinux tree for a
while, so this would be somewhat a formalization of things there. In terms
of new LSMs and major changes, this is and will remain a collaborative
process with the LSM community.
Any thoughts, concerns, objections?
--
James Morris
<jmorris@namei.org>
next reply other threads:[~2022-07-06 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 18:56 James Morris [this message]
2022-07-06 19:19 ` Maintainer update Serge E. Hallyn
2022-07-06 20:38 ` Casey Schaufler
2022-07-07 19:04 ` Paul Moore
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=c513dcdb-17f9-377a-1329-2b8fee8dc28c@namei.org \
--to=jmorris@namei.org \
--cc=linux-security-module@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