[Django] #22067: bug system "captcha" prompt is misleading
Django
----------------------------------------+--------------------
Reporter: michael.karl.coleman@… | Owner: nobody
Type: Bug | Status: new
Component: *.djangoproject.com | Version: 1.6
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
----------------------------------------+--------------------
The captcha prompt for filing a bug (without logging in) presents puzzles
like "eight plus three minus two", to which a real human would reply
"nine". This answer is not accepted, though, as the captcha wants "9".
The easy fix would be to change the prompt to indicated that the answer
should be a string of digits, not the English spelling. Or,
alternatively, just spell the problem using digits (e.g., "8 + 3 - 2").
It's a good bet that anything that can beat the latter can beat the
former.
And while you're at it, you might as well fix #17791 at the same time
(i.e., fix the prompt to not suggest that the bug report "looks like
spam").
--
Ticket URL: <https://code.djangoproject.com/ticket/22067>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: | Owner: nobody
michael.karl.coleman@… | Status: new
Type: Bug | Version: 1.6
Component: *.djangoproject.com | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
Changes (by aaugustin):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
The real fix would be to force registration. The CAPTCHA kicks in only
when you aren't logged in.
We're in the business of maintaining Django, not writing Trac plugins :-/
--
Ticket URL: <https://code.djangoproject.com/ticket/22067#comment:1>
Django
Reporter: | Owner: nobody
michael.karl.coleman@… | Status: new
Type: Bug | Version: 1.6
Component: *.djangoproject.com | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 1 | UI/UX: 0
Comment (by claudep):
I think that forcing registration would be fine. It adds a small barrier
to reporting bugs, but I think it's acceptable, and many projects have
already chosen to do so.
--
Ticket URL: <https://code.djangoproject.com/ticket/22067#comment:2>
Django
Reporter: | Owner: nobody
michael.karl.coleman@… | Status: new
Type: Bug | Version: 1.6
Component: *.djangoproject.com | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Easy pickings: 1 | UI/UX: 0
Comment (by timo):
I'm in favor of requiring registration as well. When I posed this on IRC,
Aymeric mentioned: "BDFLs were very attached to the ability to report
issues without creating an account." On the other hand, we've seen
anonymously reported issues where we respond and don't know if the
reporter will ever respond since they won't be notified of our response.
There also a fair number of comments and other changes that are
accidentally made anonymously which results in some extra noise.
--
Ticket URL: <https://code.djangoproject.com/ticket/22067#comment:3>
Django
Reporter: | Owner: nobody
michael.karl.coleman@… | Status: new
Cleanup/optimization | Resolution:
Component: *.djangoproject.com | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by timo):
* version: 1.6 =>
* type: Bug => Cleanup/optimization
* easy: 1 => 0
* stage: Unreviewed => Accepted
Comment:
I've proposed requiring registration to perform Trac actions on django-
developers: https://groups.google.com/d/topic/django-
developers/g728g23VI2E/discussion
--
Ticket URL: <https://code.djangoproject.com/ticket/22067#comment:4>
Django
Reporter: | Owner: nobody
michael.karl.coleman@… | Status: new
Type: | Version:
Cleanup/optimization | Resolution:
Component: *.djangoproject.com | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by bjb@…):
It would be great if you could just add words as to what format the answer
is expected in, and what precedence the parens are in. And, words to say
that you may have forgotten to fill in the email field and can avoid all
this with a valid email address.
I had to find out all that stuff just by trying again and again (and
reading this ticket). I was that close >< to just giving up and not
reporting.
(no comments about how useless my problem reports are please : -)
--
Ticket URL: <https://code.djangoproject.com/ticket/22067#comment:5>
Django
Reporter: | Owner: nobody
michael.karl.coleman@… | Status: new
Type: | Version:
Cleanup/optimization | Resolution:
Component: *.djangoproject.com | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by timo):
I tried removing the "TICKET_CREATE" permission from anonymous users, but
this hides the "New Ticket" button at the top of the page which isn't
ideal. Also, if/when we remove these permissions from anonymous, I think
we need to add them to authenticated (authenticated seems to inherit
permissions from anonymous as it is now).
--
Ticket URL: <https://code.djangoproject.com/ticket/22067#comment:6>
Django
Reporter: | Owner: nobody
michael.karl.coleman@… | Status: closed
Type: | Version:
Cleanup/optimization | Resolution: fixed
Component: *.djangoproject.com | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
* status: new => closed
* resolution: => fixed
Comment:
I enabled GitHub auth on Trac and configured permissions to require auth
for all write operations.
To address Tim's last comment, I rewrote the home page, which contained
mostly obsolete information ([/wiki/WikiStart?version=291 before],
[/wiki/WikiStart?version=293 after]).
--
Ticket URL: <https://code.djangoproject.com/ticket/22067#comment:7>