Maintainer update

Maintainer update

[James Morris]

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>

Re: Maintainer update

[Serge E. Hallyn]

On Thu, Jul 07, 2022 at 04:56:31AM +1000, James Morris wrote:
> 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?

+1 from me.  Thanks for all the time you've put into it!

Re: Maintainer update

[Casey Schaufler]

On 7/6/2022 11:56 AM, James Morris wrote:
> 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?

It was pretty easy to see this coming, and I support it completely.

Re: Maintainer update

[Paul Moore]

On Wed, Jul 6, 2022 at 3:15 PM James Morris <jmorris@namei.org> wrote:
>
> 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.

Thanks James, Serge, Casey.  I promise to do my best not to screw
things up too badly ;)

I'll put together a new LSM tree under my kernel.org account and send
out a MAINTAINERS patch with the updated info.

-- 
paul-moore.com