[PATCH] MAINTAINERS: update SafeSetID entry

[PATCH] MAINTAINERS: update SafeSetID entry

[Paul Moore]

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.

Cc: Micah Morton <mortonm@chromium.org>
Signed-off-by: Paul Moore <paul@paul-moore.com>
---
 MAINTAINERS | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 35e19594640d..ad910c462cd0 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -18599,7 +18599,8 @@ F:	include/media/drv-intf/saa7146*
 
 SAFESETID SECURITY MODULE
 M:	Micah Morton <mortonm@chromium.org>
-S:	Supported
+L:	linux-security-module@vger.kernel.org
+S:	Odd Fixes
 F:	Documentation/admin-guide/LSM/SafeSetID.rst
 F:	security/safesetid/
 
-- 
2.41.0

Re: [PATCH] MAINTAINERS: update SafeSetID entry

[Micah Morton]

On Fri, Jun 30, 2023 at 12:25 PM Paul Moore <paul@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!

>
> Cc: Micah Morton <mortonm@chromium.org>
> Signed-off-by: Paul Moore <paul@paul-moore.com>
> ---
>  MAINTAINERS | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 35e19594640d..ad910c462cd0 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -18599,7 +18599,8 @@ F:      include/media/drv-intf/saa7146*
>
>  SAFESETID SECURITY MODULE
>  M:     Micah Morton <mortonm@chromium.org>
> -S:     Supported
> +L:     linux-security-module@vger.kernel.org
> +S:     Odd Fixes
>  F:     Documentation/admin-guide/LSM/SafeSetID.rst
>  F:     security/safesetid/
>
> --
> 2.41.0
>

Re: [PATCH] MAINTAINERS: update SafeSetID entry

[Paul Moore]

On Tue, Jul 4, 2023 at 2:33 PM Micah Morton <mortonm@chromium.org> wrote:
> On Fri, Jun 30, 2023 at 12:25 PM Paul Moore <paul@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

Re: [PATCH] MAINTAINERS: update SafeSetID entry

[Serge E. Hallyn]

On Wed, Jul 05, 2023 at 01:03:05PM -0400, Paul Moore wrote:
> On Tue, Jul 4, 2023 at 2:33 PM Micah Morton <mortonm@chromium.org> wrote:
> > On Fri, Jun 30, 2023 at 12:25 PM Paul Moore <paul@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.

Note also that the email address in MAINTAINERS file can be updated :)
So if chromium.org email is the sticking point, it doesn't have to be.

-serge

Re: [PATCH] MAINTAINERS: update SafeSetID entry

[Paul Moore]

On Wed, Jul 5, 2023 at 3:45 PM Serge E. Hallyn <serge@hallyn.com> wrote:
> On Wed, Jul 05, 2023 at 01:03:05PM -0400, Paul Moore wrote:
> > On Tue, Jul 4, 2023 at 2:33 PM Micah Morton <mortonm@chromium.org> wrote:
> > > On Fri, Jun 30, 2023 at 12:25 PM Paul Moore <paul@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.
>
> Note also that the email address in MAINTAINERS file can be updated :)
> So if chromium.org email is the sticking point, it doesn't have to be.

Very good point.  People are the important part, not necessarily what
is listed in MAINTAINERS.  We can always find new ways to record
things in MAINTAINERS, finding good maintainers is much more difficult
;)

-- 
paul-moore.com

Re: [PATCH] MAINTAINERS: update SafeSetID entry

[Micah Morton]

On Wed, Jul 5, 2023 at 12:48 PM Paul Moore <paul@paul-moore.com> wrote:
>
> On Wed, Jul 5, 2023 at 3:45 PM Serge E. Hallyn <serge@hallyn.com> wrote:
> > On Wed, Jul 05, 2023 at 01:03:05PM -0400, Paul Moore wrote:
> > > On Tue, Jul 4, 2023 at 2:33 PM Micah Morton <mortonm@chromium.org> wrote:
> > > > On Fri, Jun 30, 2023 at 12:25 PM Paul Moore <paul@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.

I think setting a calendar reminder once per week to check this
mailing list for any SafeSetID related patches/mail sounds reasonable
and something I can commit to. Keeping the same @chromium.org email
for me is fine, I'll let you guys know if I lose access or have
trouble logging in at some point and we can get the email updated, but
I don't anticipate that happening.

Thanks,
Micah

> >
> > Note also that the email address in MAINTAINERS file can be updated :)
> > So if chromium.org email is the sticking point, it doesn't have to be.
>
> Very good point.  People are the important part, not necessarily what
> is listed in MAINTAINERS.  We can always find new ways to record
> things in MAINTAINERS, finding good maintainers is much more difficult
> ;)
>
> --
> paul-moore.com

Re: [PATCH] MAINTAINERS: update SafeSetID entry

[Paul Moore]

On Mon, Jul 10, 2023 at 2:15 PM Micah Morton <mortonm@chromium.org> wrote:
> On Wed, Jul 5, 2023 at 12:48 PM Paul Moore <paul@paul-moore.com> wrote:
> > On Wed, Jul 5, 2023 at 3:45 PM Serge E. Hallyn <serge@hallyn.com> wrote:
> > > On Wed, Jul 05, 2023 at 01:03:05PM -0400, Paul Moore wrote:
> > > > On Tue, Jul 4, 2023 at 2:33 PM Micah Morton <mortonm@chromium.org> wrote:
> > > > > On Fri, Jun 30, 2023 at 12:25 PM Paul Moore <paul@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.
>
> I think setting a calendar reminder once per week to check this
> mailing list for any SafeSetID related patches/mail sounds reasonable
> and something I can commit to. Keeping the same @chromium.org email
> for me is fine, I'll let you guys know if I lose access or have
> trouble logging in at some point and we can get the email updated, but
> I don't anticipate that happening.

That's great news Micah, thanks!

-- 
paul-moore.com