misc/99305: send-pr.html is frustrating/broken

[Jo Rhett]

>Number:         99305
>Category:       misc
>Synopsis:       send-pr.html is frustrating/broken
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jun 22 16:00:34 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Jo Rhett
>Release:        6.0
>Organization:
svcolo
>Environment:
doesn't matter
>Description:
Submitting a PR is an extremely frustrating process, mostly due to the fact that I have to open the form, then cut&paste everything into a second form later.

It's pretty clear that the confirmation codes time out in just a few minutes.  Which means that entering a detailed problem report is impossible in that timeframe.  It's also a killer if you get interrupted by a co-worker and have to come back to it.

>How-To-Repeat:
1. Open the send-pr.html form.
2. Fill out the header fields.
3. Fill in the full description and process text fields with patches and examples.
   *try to do this REALLY FAST to avoid the next ...*
4. Hit submit
5. Read complaint about improperly entering the confirmation code

-then-
6. Open a second window to the same form
7. Cut and paste everything from window 1 to window 2
8. Enter the new code and hit submit
>Fix:
1. Don't report to the user that they entered the code incorrectly when it's actually a time out.  Tell them it's a time out.

2. Don't time out so darn fast!  I'm a freakin speed typist, and there have been times that I missed the timeout interval without being interrupted even once!  Do you want detailed reports or not?

3. AND/OR make it possible to get a new confirmation code without re-entering all of the information.  How about putting the form-supplied data into a new page with a new confirmation code at the bottom?
>Release-Note:
>Audit-Trail:
>Unformatted: