http://bugs.winehq.org/show_bug.cgi?id=25229
Jörg Höhle hoehle@users.sourceforge.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hoehle@users.sourceforge.ne | |t
--- Comment #2 from Jörg Höhle hoehle@users.sourceforge.net 2010-12-17 03:46:54 CST --- I'd like to suggest renaming "Reject" to "Suspend" or something similar. It was completely obscure to me prior to reading this issue that "Reject" could be used (in theory) to send an e-mail to a submitter *and* leave the submission in the queue, waiting for clarification or additional details. This is want I want to do with half the submissions that I process.
"Reject" sounds final in my mind = "Refuse and be done with it". "Delete" like "get rid of that spam" (which might be identical except no mail is sent).
Of course that supposes that either a) the submitter is still able to get to a page where s/he can refine the submitted data (instead of creating it anew), or b) I refine the data as a maintainer, based on the feedback I got per email from the submitter.
So what's open? - Does AppDB guarantee that a submission is still available for refinement after sending an answer like "We appreciate your submission but it needs to be more detailed before it will be most useful to other users of the Application Database. Please try to improve the entry and resubmit." Or will the user have to retype everything?
- If refinement is possible, how to send an e-mail? Is "Submit" the right button? Is "Reject" the right one?