public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Mark Wielaard <mark@klomp.org>
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: move bugzilla account request email to another list?
Date: Fri, 2 Sep 2022 10:50:41 -0400	[thread overview]
Message-ID: <20220902145041.l6shzwd2fr5ndtfs@cgf.cx> (raw)
In-Reply-To: <5c9b5cd2c4207bf049727e90578a265762a08935.camel@klomp.org>

On Fri, Sep 02, 2022 at 12:32:12PM +0200, Mark Wielaard wrote:
>Hi Chris,
>
>On Thu, 2022-09-01 at 12:30 -0400, Christopher Faylor via Overseers
>wrote:
>> I think we've reached the point where the bugzilla account request email
>> should be moved to another list.  As it stands now, I have a tendency
>> to ignore this list because most of the traffic does not really pertain
>> to overseeing sourceware.org.
>
>Right. Thanks for creating the admin-requests@ mailinglist and for
>updating the bugzilla template/maintainer parameter (I git committed it
>because the data dir changes are not automatically snapshotted).

That was fche but, you're welcome.

>Now that overseers@ is more public/advertised it is also a good idea to
>keep the admin-requests list non-public so people's addresses and ssh
>pubkeys aren't unnecessarily advertised.

It's not published, just like a couple other mailing lists on this site.

cgf


  reply	other threads:[~2022-09-02 14:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 16:30 Christopher Faylor
2022-09-01 17:35 ` Carlos O'Donell
2022-09-01 17:42   ` Christopher Faylor
2022-09-02 10:32 ` Mark Wielaard
2022-09-02 14:50   ` Christopher Faylor [this message]
2022-09-02 14:58     ` Carlos O'Donell
2022-09-02 21:09       ` Mark Wielaard

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=20220902145041.l6shzwd2fr5ndtfs@cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=mark@klomp.org \
    --cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).