public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Mark Wielaard <mark@klomp.org>, Pedro Alves <pedro@palves.net>,
	Joel Brobecker <brobecker@adacore.com>,
	Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: getting spammed on bugzilla
Date: Sun, 28 Nov 2021 12:35:51 -0500	[thread overview]
Message-ID: <20211128173551.GC25576@redhat.com> (raw)
In-Reply-To: <YaO16WhjjuYPIX8u@wildebeest.org>

Hi -

> So how does this work now?  As far as I can see the createemailregexp
> for gcc is ".*" but for sourceware it is "^$".  So gcc allows
> everything, but filters (how?) on the email domain? Would it make
> sense to use the same settings for both?

The GCC side of sourceware uses a domain list to further filter
the .*-accepted ones.  The sourceware side just blocks them all at
the regex level.


> > That's a matter of <template/en/default/account/create.html.tmp>, which
> > is now updated on sourceware-bugzilla.
> 
> I would like to update the text so that it asks people to mention the
> project they want to report a bug for. So that it is more clear
> whether the request is for gcc or a sourceware project. But I don't
> really understand how the templates are updated/generated.

The file name I posted is for the template input: just modify it and
bob is your uncle.  OTOH, only the sourceware bugzilla points people
to overseers@, so it's unambiguous.


> > https://sourceware.org/bugzilla/editusers.cgi?action=add
> 
> I find this hard to use. It seems to demand a password and 'Notify
> User' isn't enabled by default (should it?). Do people need edituser
> permisssion to use this form (who has this and could we maybe make it
> so that anybody with editbugs permissions can bless new users?)?

I don't know.  The people with editusers should be about the same
people as those with editbugs, i.e., bugzilla administrators.  The
higher, the fewer.  The few, the proud.

- FChE


  reply	other threads:[~2021-11-28 17:35 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
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 [this message]
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=20211128173551.GC25576@redhat.com \
    --to=fche@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=mark@klomp.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).