[PATCH] MAINTAINERS: update SafeSetID entry

[Paul Moore]

On Tue, Jul 4, 2023 at 2:33 PM Micah Morton <mortonm at chromium.org> wrote:
> On Fri, Jun 30, 2023 at 12:25 PM Paul Moore <paul at paul-moore.com> wrote:
> >
> > Micah Morton, the SafeSetID maintainer, last posted to any of the
> > public kernel mailing lists in early August 2022 and has not
> > commented on any SafeSetID patches posted since that time.  Attempts
> > to contact Micah directly over email have also failed.  Until Micah
> > reappears I'll plan to continue accepting SafeSetID patches via the
> > LSM tree, but I'm going to mark SafeSetID as "Odd Fixes" for now,
> > and add the LSM mailing list to the MAINTAINERS entry so that the
> > LSM list will be properly CC'd on any new SafeSetID patches.
>
> Hi Paul, I've moved on from working on ChromeOS and checking my
> @chromium.org email on a regular basis. I was trying to check in once
> per month or so but I guess its been a couple months since I've signed
> on -- sorry about that. This sounds good to me, I can't necessarily
> make any guarantees that I will be a responsive maintainer going
> forward (especially since I expect changes to the SafeSetID code to be
> very few and far between). I'm good with whatever you think is best
> here. Thanks!

Thanks for the update Micah.

Generally speaking, serving as a maintainer requires checking email on
a regular basis.  There isn't a well defined requirement that I'm
aware of, but once every couple months, or even once a month, is
outside what many expect, myself included.  I know you have moved on
from ChromeOS, but do you have a personal desire to continue
maintaining SafeSetID?  Linux has a rich history of maintainers who
maintain subsystems outside of a paying job, and I would be happy to
support you in such a role, but in order to do so I think you would
need to check your email at least once a week.  However, if you aren't
able to commit to that at this point in time we probably should mark
SafeSetID as being in the "Orphan" state, with patches accepted via
the LSM tree until a suitable maintainer can be found.

-- 
paul-moore.com