Andrea Pinski <[email protected]> writes:

> On Sun, Oct 11, 2026 at 2:23 PM Sam James via Gcc <[email protected]> wrote:
>>
>> Hi,
>>
>> This has come up on IRC a few times. I think we should re-enable
>> self-account signup on Bugzilla.
>>
>> Andrea and I at least have seen people put off by having to email to get
>> an account and they end up just not filing a bug at all and only
>> complaining on social media, or not even that.
>
> I am still waiting on this whole miscompile bug with openssl and GCC
> 16+ on aarch64 from the curl folks.
> Still not seen it (or maybe it was an openssl issue in the end).
>
>>
>> I did volunteer along with Arsen to help with the account requests but I
>> don't believe this handles the problem in full. I myself have been put
>> off when I have to email to get an account on someone's self-hosted
>> gitlab.
>
> I agree.
>
>>
>> I already read most Bugzilla activity and I'm happy to tag comments as
>> spam and ban accounts.
>
> Likewise with respect to all of bugzilla activity when I am not busy.
> Even the recent bug reports have been great (some even have the known
> to work and known to fail filled in which is super nice).
>
>>
>> On the Gentoo side, we have had similar problems but it's not too
>> bad. We have a Bugzilla extension [0] which bans URLs from new accounts for
>> 24 hours: we could possibly bring that over here but exempt some
>> sites like stackoverflow, standard reference sites, and godbolt.
>
> Agreed.  I don't know bugzilla enough to be able to help implement this 
> though.

I can implement this part with the overseers as we have an extension on
our side that does almost all of it, it just needs a whitelist added
(which I can do).

Any suggestions for what URLs/domains please? cppreference,
godbolt/compilerexplorer, stackexchange, maybe reddit (as we sometimes
get /r/cpp etc links), what else?

>
>>
>> Another option would be to implement moderation in Bugzilla [1] which both
>> Bugzilla instances would benefit from. IMO neither of these should be
>> blockers to begin with, and we can revisit as we go if it turns out to
>> not work out.
>
> Likewise.
> Both are good ideas but I definitely not the person who can help out
> here though.

This one I can do technically but it'll require a significant amount of
time, so let's try the first option first.

>
> Thanks.
> Andrea
>
>>
>> [0] https://sourceware.org/PR32270
>> [1] 
>> https://public-inbox.gentoo.org/gentoo-dev/[email protected]/T/#u
>>
>> thanks,
>> sam

Attachment: signature.asc
Description: PGP signature

Reply via email to