From: Carlos O'Donell <carlos@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>,
David Edelsohn <dje.gcc@gmail.com>
Cc: Overseers <overseers@sourceware.org>
Subject: Re: GCC Bugzilla accounts
Date: Thu, 25 May 2017 16:37:00 -0000 [thread overview]
Message-ID: <1f9b4a90-04ad-d0c8-cb2f-13ed34ce96f2@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1705251620230.31135@digraph.polyomino.org.uk>
On 05/25/2017 12:26 PM, Joseph Myers wrote:
> I'd suggest replacing "Contact your administrator or the maintainer
> (overseers@gcc.gnu.org) for information about creating an account. Please
> press Back and try again." with something along the lines of "Contact
> <address> to request an account. You should receive a response within 24
> hours.". And the account creation form should not say you can create an
> account through that form when you can't.
Why are we filtering account creation?
We stopped doing that in the default sourceware bugzilla configuration.
Instead there we allow users to create all of their own accounts, but by
default you don't get editbugs. You have to have someone grant you editbugs,
and that can be done by anyone else who previously had editbugs, so you can
just email the list and someone will quickly bless you.
Is the account creation still an anti-spam tactic?
I think it's a terrible one, the editbugs removal seems to have worked much
better. Now spammers cant change any existing bugs. They can still file
new bugs, which we can zap entirely.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2017-05-25 16:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 16:07 David Edelsohn
2017-05-25 16:26 ` Joseph Myers
2017-05-25 16:37 ` Carlos O'Donell [this message]
2017-05-25 16:41 ` Joseph Myers
2017-05-25 20:16 ` Ian Lance Taylor
2017-05-25 20:35 ` Gerald Pfeifer
2017-05-25 21:36 ` Frédéric Buclin via overseers
2017-05-31 11:54 ` David Edelsohn
2017-05-31 12:38 ` Carlos O'Donell
2017-05-31 12:41 ` David Edelsohn
2017-05-31 13:14 ` Frank Ch. Eigler
2017-05-31 13:22 ` David Edelsohn
2017-05-31 14:39 ` Christopher Faylor
2017-05-31 14:49 ` David Edelsohn
2017-06-01 14:19 ` Joseph Myers
2017-06-01 14:44 ` Christopher Faylor
2017-06-01 14:53 ` David Edelsohn
2017-06-01 19:56 ` Christopher Faylor
2017-06-05 15:39 ` David Edelsohn
2017-06-05 15:49 ` Frank Ch. Eigler
2017-06-16 22:02 ` Frank Ch. Eigler
2017-06-17 12:07 ` David Edelsohn
2017-06-20 22:40 ` David Edelsohn
2017-06-21 22:02 ` Frank Ch. Eigler
2017-06-23 13:39 ` David Edelsohn
2017-07-13 18:29 ` David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
2014-12-12 15:53 gcc bugzilla accounts Damien Ruscoe
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=1f9b4a90-04ad-d0c8-cb2f-13ed34ce96f2@redhat.com \
--to=carlos@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=joseph@codesourcery.com \
--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).