From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mark@klomp.org>
Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184])
 by sourceware.org (Postfix) with ESMTPS id D2DC93858C27
 for <overseers@sourceware.org>; Sun, 28 Nov 2021 17:01:31 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D2DC93858C27
Received: from reform (deer0x11.wildebeest.org [172.31.17.147])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by gnu.wildebeest.org (Postfix) with ESMTPSA id 109BE30006B1;
 Sun, 28 Nov 2021 18:01:29 +0100 (CET)
Received: by reform (Postfix, from userid 1000)
 id 831382E800D6; Sun, 28 Nov 2021 18:01:29 +0100 (CET)
Date: Sun, 28 Nov 2021 18:01:29 +0100
From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: "Frank Ch. Eigler" <fche@elastic.org>,
 Simon Marchi <simon.marchi@polymtl.ca>,
 Joel Brobecker <brobecker@adacore.com>, Pedro Alves <pedro@palves.net>
Subject: Re: getting spammed on bugzilla
Message-ID: <YaO16WhjjuYPIX8u@wildebeest.org>
References: <YYyOJhziKpa5jBgo@adacore.com>
 <CA+=Sn1k3GWexDuxMnmbj-zPGboLanzUGNpAH8mth_BH17vuEyA@mail.gmail.com>
 <YY3wQQQ/R/th3Dki@adacore.com> <YY4r/kPvrr20RsZV@wildebeest.org>
 <6bf0f483-ce3a-3c03-f889-15c8b2eef14f@redhat.com>
 <YZsWrdgpSdzZ2bNy@adacore.com>
 <bef80927056caf1f3fb27e1a35f1d5b6ea56415f.camel@klomp.org>
 <YZ5STzESg4PiUQM7@elastic.org> <YZ7NgxBkWN7G3Mwr@wildebeest.org>
 <YZ7WjTrabqNd8DEN@elastic.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <YZ7WjTrabqNd8DEN@elastic.org>
X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 server2.sourceware.org
X-BeenThere: overseers@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Overseers mailing list <overseers.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/overseers>,
 <mailto:overseers-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/overseers/>
List-Post: <mailto:overseers@sourceware.org>
List-Help: <mailto:overseers-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/overseers>,
 <mailto:overseers-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Nov 2021 17:01:35 -0000

Hi Frank,

On Wed, Nov 24, 2021 at 07:19:25PM -0500, Frank Ch. Eigler via Overseers wrote:
> > > 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
> 
> Ummmmmmmmmmmm about that.  How is this part supposed to work on gcc's
> bugzilla?  I just made myself a test user there, with no one else's
> approval, and ended up with a user that could append to an existing
> bug.  I think someone may have pooched the bugzilla administrative
> setting "createemailregexp", setting it to ".*", at some point.
> Should these be set to a magic value to actually impose restrictions?

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?

> > make people aware they need to provide (which?) information to the
> > mailinglist and
> 
> 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.

> > a way for volunteers to take that information and create new
> > accounts.
> 
> That's a matter of any bugzilla administrator reading this mailing list
> and doing the deed on the administrative Users/New form:
> 
> 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?)?

GCC seemed to have a specialized form (although I cannot find it now)
that had more defaults setup correctly. It seems to be defined in
gcc-bugzilla/data/template/extensions/GCC/template/en/default/pages/gcc/addusers.html.tmpl
but I don't know how it is being used.

Cheers,

Mark