public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: "Frank Ch. Eigler" <fche@elastic.org>,
	Overseers <overseers@sourceware.org>,
		"Carlos O'Donell" <carlos@redhat.com>,
	"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: GCC Bugzilla accounts
Date: Wed, 31 May 2017 14:49:00 -0000	[thread overview]
Message-ID: <CAGWvnymQN9tNacOmo9zUP188iBhE+o5T7vHuFzLHP_DGuXpzyQ@mail.gmail.com> (raw)
In-Reply-To: <20170531143913.GA1254@ednor.casa.cgf.cx>

On Wed, May 31, 2017 at 10:39 AM, Christopher Faylor
<cgf-use-the-mailinglist-please@sourceware.org> wrote:
> On Wed, May 31, 2017 at 09:22:47AM -0400, David Edelsohn wrote:
>>On Wed, May 31, 2017 at 9:14 AM, Frank Ch. Eigler <fche@elastic.org> wrote:
>>> On May 31, 2017 8:41:55 AM EDT, David  >[...] current requests for account creation
>>>>either are being lost or not responded.
>>>
>>>This is not true.  Every request that comes into overseers@ gets
>>>addressed.  We just don't spam you with a visible ack cc.
>>
>>Something is going wrong because I and others are seeing numerous
>>reports on social media of requests that receive no response.  As
>>mentioned earlier in the thread, some people report that they receive
>>automated bounce replies because their email clients send HTML
>>messages.  People are resorting to reporting bugs through social media
>>and Stackoverflow because they cannot report them through the proper
>>channels.  This needs to be fixed.
>
> There certainly are people who send html-only email to overseers asking
> to have an account created.  That is an issue that they can fix for
> themselves and many do.

Is there a reason that mail to overseers must reject HTML-only email?
Or maybe we need a separate email alias for GCC Bugzilla account
requests without the restriction.

One hypothesis: "bounce" messages due to HTML are being categorized as
SPAM or junk email and the user never receives the message.  The user
believes that the request was ignored.

Even if users can changes the email client settings, it's not clear
that this makes a good impression on users who want to contribute bug
reports.

>
> Back when I thought I had some free time for sourceware, I started on a
> all-in-one web form intended to sign up for a new account, add a new
> group, or gain bugzilla access:
>
> https://sourceware.org/account/
>
> The intent was that requests for a new account would be sent to a list
> of people who could act on the request and automatically create an
> account without necessarily getting someone from overseers involved.
>
> The above is just a stub.  It reflects my journey as I learned
> javascript and php for my new job so it may be buggy.  However, would
> something like the above be acceptable for at least an interim solution?

That definitely would be an improvement.  Of course, that form could
get overwhelmed with SPAM without some "I am not a Robot" test.

Thanks, David

  reply	other threads:[~2017-05-31 14:49 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
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 [this message]
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=CAGWvnymQN9tNacOmo9zUP188iBhE+o5T7vHuFzLHP_DGuXpzyQ@mail.gmail.com \
    --to=dje.gcc@gmail.com \
    --cc=carlos@redhat.com \
    --cc=fche@elastic.org \
    --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).