From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 42235 invoked by alias); 25 May 2017 16:26:22 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 42197 invoked by uid 89); 25 May 2017 16:26:20 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=U*overseers, sk:oversee, volunteers, overseers@gcc.gnu.org X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 25 May 2017 16:26:14 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=SVR-IES-MBX-03.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1dDvaa-0006ST-8X from joseph_myers@mentor.com ; Thu, 25 May 2017 09:26:16 -0700 Received: from digraph.polyomino.org.uk (137.202.0.87) by SVR-IES-MBX-03.mgc.mentorg.com (139.181.222.3) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 25 May 2017 17:26:13 +0100 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.86_2) (envelope-from ) id 1dDvaS-0000tE-Eq; Thu, 25 May 2017 16:26:08 +0000 Date: Thu, 25 May 2017 16:26:00 -0000 From: Joseph Myers To: David Edelsohn CC: Overseers Subject: Re: GCC Bugzilla accounts In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To SVR-IES-MBX-03.mgc.mentorg.com (139.181.222.3) X-SW-Source: 2017-q2/txt/msg00082.txt.bz2 On Thu, 25 May 2017, David Edelsohn wrote: > What can be done to improve this situation? It seems that it would be > helpful to provide a specific email address for GCC Bugzilla account > requests, especially one that accepted HTML email messages, and > specific individuals to confirm and approve requests. This also might > be a good task for new GCC volunteers. In addition, the message given when you try to create an account - after submitting the account creation form - is not helpful: "User account creation filtered due to spam. User account creation has been restricted. Contact your administrator or the maintainer (overseers@gcc.gnu.org) for information about creating an account. Please press Back and try again.". "your administrator" is too ambiguous about who it refers to. "for information about creating an account" is also unhelpful. "Please press Back and try again." gives a misleading impression that trying the account creation form again could help. Also, the fact that the account creation form says To create a GCC Bugzilla account, all you need to do is to enter a legitimate email address. You will receive an email at this address to confirm the creation of your account. You will not be able to log in until you receive the email. If it doesn't arrive within a reasonable amount of time, you may contact the maintainer of this Bugzilla installation at overseers@gcc.gnu.org. when it doesn't in fact let you create an account is thoroughly misleading. 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
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. (Obviously you need enough people covering the account creation address, not all away simultaneously, to create the accounts within the declared time.) -- Joseph S. Myers joseph@codesourcery.com