From: Piotr Karbowski <slashbeast@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] pam: thoughts on modernizing pam_limits configuration that Gentoo ships with
Date: Sun, 11 Dec 2022 16:38:11 +0100 [thread overview]
Message-ID: <e5e12ead-cd18-661b-b5d2-9b0cf45b1c7d@gentoo.org> (raw)
In-Reply-To: <FC4618C0-28F2-4C41-A730-DA07AA9963F9@gentoo.org>
Hi,
On 11/12/2022 13.46, Sam James wrote:
> You should still file a bug for two reasons:
> 1. Paper trail
> 2. sys-auth/pambase has another maintainer who*is* active :)
>
> As for the question in your post, I'll have a think. Thanks!
I am not against creating a bug, I do see it however as inefficient in
this very case.
I do know however if I were to create bug and assign it to current
single pam maintainer, it would hardly get noticed by other people,
greatly reducing the feedback. Changing defaults will affect vast
majority of Gentoo users, so gentoo-dev ml was the place I choosen.
I didn't realized that you are maintainer of pambase, though the
/etc/security/limits.conf belongs to sys-libs/pam that has only zlogene.
I did mail zlogene regarding another package recently and got no
response, thus pam itself seems maintainer-needed to me, and because of
it a candidate for me to join as another maintainer and do the changes.
I do not think it would make much sense for me to then create bug for
myself to make this change of defaults, paper trail would be the commit
subject and message itself, or perhaps I did not understood of what you
meant here by paper trail, would appreciate clarification.
It would be great if you were interested in joining pam itself, and I am
interested to also joining pambase, since those are so co-dependent it
does not make sense to have split maintainers there.
-- Piotr.
next prev parent reply other threads:[~2022-12-11 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 8:28 [gentoo-dev] pam: thoughts on modernizing pam_limits configuration that Gentoo ships with Piotr Karbowski
2022-12-11 12:46 ` Sam James
2022-12-11 15:38 ` Piotr Karbowski [this message]
2022-12-12 5:52 ` Robin H. Johnson
2022-12-12 21:55 ` Piotr Karbowski
2022-12-12 22:06 ` Sam James
2022-12-12 22:26 ` Piotr Karbowski
2022-12-12 22:53 ` Sam James
2022-12-13 3:24 ` John Helmert III
2022-12-13 5:18 ` Joonas Niilola
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=e5e12ead-cd18-661b-b5d2-9b0cf45b1c7d@gentoo.org \
--to=slashbeast@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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