From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: Overseers mailing list <overseers@sourceware.org>,
Joel Brobecker <brobecker@adacore.com>,
Simon Marchi <simon.marchi@polymtl.ca>,
Pedro Alves <pedro@palves.net>
Subject: Re: getting spammed on bugzilla
Date: Thu, 25 Nov 2021 00:40:51 +0100 [thread overview]
Message-ID: <YZ7NgxBkWN7G3Mwr@wildebeest.org> (raw)
In-Reply-To: <YZ5STzESg4PiUQM7@elastic.org>
Hi Frank,
On Wed, Nov 24, 2021 at 09:55:11AM -0500, Frank Ch. Eigler wrote:
> > > Does anyone know how this would work? Do we redirect people to
> > > a mailing-list, and then those in the mailing-list create accounts
> > > for those new users?
> >
> > Unfortunately I don't know how to set this up. [...]
>
> How about let's keep simple and direct people to overseers@ for now.
That is fine if all volunteers are subscribed to overseers and you
aren't afraid it will overwhelm this list. But we also need a way to
disable new user signups, make people aware they need to provide
(which?) information to the mailinglist and a way for volunteers to
take that information and create new accounts.
Cheers,
Mark
next prev parent reply other threads:[~2021-11-24 23:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 3:29 Joel Brobecker
2021-11-11 3:47 ` Andrew Pinski
2021-11-12 4:40 ` Joel Brobecker
2021-11-12 8:55 ` Mark Wielaard
2021-11-12 13:26 ` Carlos O'Donell
2021-11-22 4:03 ` Joel Brobecker
2021-11-24 10:09 ` Mark Wielaard
2021-11-24 14:55 ` Frank Ch. Eigler
2021-11-24 23:40 ` Mark Wielaard [this message]
2021-11-25 0:19 ` Frank Ch. Eigler
2021-11-25 17:49 ` Joseph Myers
2021-11-25 17:54 ` Frank Ch. Eigler
2021-11-25 17:59 ` Joseph Myers
2021-11-28 17:01 ` Mark Wielaard
2021-11-28 17:35 ` Frank Ch. Eigler
2021-11-28 18:07 ` Mark Wielaard
2021-11-29 17:12 ` Joseph Myers
2021-12-17 2:50 ` Joel Brobecker
2021-12-17 17:19 ` Frank Ch. Eigler
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=YZ7NgxBkWN7G3Mwr@wildebeest.org \
--to=mark@klomp.org \
--cc=brobecker@adacore.com \
--cc=fche@elastic.org \
--cc=overseers@sourceware.org \
--cc=pedro@palves.net \
--cc=simon.marchi@polymtl.ca \
/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).