After thinking about it I agree. The message should probably be done on
closing the bug as INVALID or adding a new status of PLEASETEST (I am not
hugely in favor of this, we already have too many status' IMO). But for
more experienced triagers there's no harm in letting the user know on
marking it as NEEDINFO that the bug will be auto closed after 30 days. No
need to make this a big deal, just for those of us who have been working
with LibO for awhile we can add the friendly message. We don't want to get
too strict or mechanical for many reasons, two that come to mind is pissing
off our user base because we sound like robots and also making it more
difficult for new members to get involved.
We should try to finalize this before our next conference call so we can
move on to more important stuff :)
Joel
P.S. Also, is there an ongoing agenda for the next conference?
On Mon, Aug 27, 2012 at 3:58 AM, Petr Mladek pmla...@suse.cz wrote:
Rainer Bielefeld píše v So 25. 08. 2012 v 11:30 +0200:
Joel Madero schrieb:
when we actually put a bug into NEEDINFO status we put a comment that
has a small blurb on our procedure. Something like we have put this
bug
in NEEDINFO status because we need you to provide.we will leave the
bug in this status for 6 months
I recommend that we agree to a standard sentence like This bug will be
closed after 14 days if requested information will not be provided.
Additional information concerning the reasons for this proceeding and
how you can reopen this Bug you can find at jttp://...Wiki... , to be
inserted by copy /paste from Wiki.
I appreciate you carefulness and sense for details. Well, I am still not
convinced that we need to warn people before. I understand the point but
it has some drawbacks:
+ reporters might get angry that we force them to answer within 30
days and then do not fix bug several months; and we are not able to
fix all 5000 bugs within one month
+ the standard message is yet another thing that bug triagers
should memorize; it makes the process more complicated and harder
to learn
+ it is another message that makes the report longer and harder to
read
I still thing that the best solution would be to tune the closing
message. It has to be short, explanatory, friendly, encouraging. I
suggest something like:
We would like to solve this bug but nobody has provided the requested
information during last 30 days. We can't move forward and close this
bug for now. Feel free to reopen it together with the needed details.
This can be done automatically, so nobody need to memorize it.
Best Regards,
Petr
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
