Date: Sun, 6 Feb 2022 13:30:25 +0100 From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= <fernando.apesteguia@gmail.com> To: Neel Chauhan <nc@freebsd.org> Cc: ports FreeBSD <ports@freebsd.org> Subject: Re: security/sssd: Maintainer inactive? Message-ID: <CAGwOe2ZT96BdHGZx3OmZpoNKa2co7LDwQTdp8gm7buMnuV6mYA@mail.gmail.com> In-Reply-To: <4ad930a0fcffffad18a11b6f08b53b5c@FreeBSD.org> References: <4ad930a0fcffffad18a11b6f08b53b5c@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000ae551305d758a633 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable El dom., 6 feb. 2022 7:12, Neel Chauhan <nc@freebsd.org> escribi=C3=B3: > Hi ports@, > > I was looking at the port security/sssd (mainly to connect FreeBSD to a > Windows Server 2022 AD), and noticed the maintainer is inactive. > > sssd has multiple maintainer timeouts: > https://www.freshports.org/security/sssd > > I don't know if we should reset the maintainership of this port or not. > > If we do reset, I'm not 100% sure if I want to take on maintainership of > the port, but can consider it as a last resort. > We could reset and assign to ports@. At least that way users would be aware that the port has no maintainer (something that is already true). > Disclaimer: I work at Microsoft (which is how I got WS2022), but not on > Windows or AD. > > -Neel (nc@) > > --000000000000ae551305d758a633 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr" = class=3D"gmail_attr">El dom., 6 feb. 2022 7:12, Neel Chauhan <<a href=3D= "mailto:nc@freebsd.org">nc@freebsd.org</a>> escribi=C3=B3:<br></div><blo= ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c= cc solid;padding-left:1ex">Hi ports@,<br> <br> I was looking at the port security/sssd (mainly to connect FreeBSD to a <br= > Windows Server 2022 AD), and noticed the maintainer is inactive.<br> <br> sssd has multiple maintainer timeouts: <br> <a href=3D"https://www.freshports.org/security/sssd" rel=3D"noreferrer nore= ferrer" target=3D"_blank">https://www.freshports.org/security/sssd</a><br>; <br> I don't know if we should reset the maintainership of this port or not.= <br> <br> If we do reset, I'm not 100% sure if I want to take on maintainership o= f <br> the port, but can consider it as a last resort.<br></blockquote></div></div= ><div dir=3D"auto"><br></div><div dir=3D"auto">We could reset and assign to= ports@. At least that way users would be aware that the port has no mainta= iner (something that is already true).</div><div dir=3D"auto"><br></div><di= v dir=3D"auto"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"= style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br> Disclaimer: I work at Microsoft (which is how I got WS2022), but not on <br= > Windows or AD.<br> <br> -Neel (nc@)<br> <br> </blockquote></div></div></div> --000000000000ae551305d758a633--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGwOe2ZT96BdHGZx3OmZpoNKa2co7LDwQTdp8gm7buMnuV6mYA>