Re: A bug reporter surprised by their information going to public mailing list.

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: David Rowley <dgrowleyml(at)gmail(dot)com>, pgsql-www(at)postgresql(dot)org
Subject: Re: A bug reporter surprised by their information going to public mailing list.
Date: 2020-09-27 21:53:25
Message-ID: 2d8f8b31-d7ec-2e2d-bcd8-8c41516d4e87@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On 9/27/20 5:37 PM, David Rowley wrote:
> In [1] Brian got a bit caught out when he missed the text on the bug
> reporting form that says:
>
> "By submitting a bug through this form you agree that all contents of
> the bug report, including your personal information as listed, will be
> posted to the public pgsql-bugs mailing list, and archived in the
> public list archives."
>
> I figured that could have been much worse than it was.
>
> Maybe it's not worth spending too many cycles for people that bypass
> the warning text, but I thought I'd mention the idea that this could
> be backed up by a check box just above the submit and send email
> button which has the text "I understand that this report will be
> emailed to a public mailing list". The submit would be disallowed
> until the user checks the checkbox.
>
> Does anyone think it's worth adding?

The patch itself is not difficult (attached), though the formatting on
the page itself is not great, I'd need to figure out the CSS to align
the checkbox and label text, as the general form construct has not
required that to date.

I'm not opposed to adding it.

Jonathan

Attachment Content-Type Size
confirm.patch text/plain 771 bytes

In response to

Browse pgsql-www by date

  From Date Subject
Next Message Tom Lane 2020-09-27 23:39:19 Re: A bug reporter surprised by their information going to public mailing list.
Previous Message David Rowley 2020-09-27 21:37:13 A bug reporter surprised by their information going to public mailing list.