Re: [Libreoffice-qa] request for more boilerplate responses to bug report
Am 10.09.2014 um 02:55 schrieb Terrence Enger: I have noticed that Urmas has been abruptly closing bug reports that are in languages other than English. What an arrogant behavior :-( How about first putting them into NEEDINFO state and asking for translation here or in the l10n list? There were several localization bugs written in German I remember - they were perfectly handled by the NL-Team in their native language without any need to translate them back and forth. This might be true for other bug reports too as there are still many people in the world not speaking english. A NEEDSTRANSLATION keyword could also help if we could somehow report those bugs to an appropriate list (l10n would be my choice if people there agree but qa might even be better as most qa-interested NL-folks at least lurk here). just my2¢ Nino ___ 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/
Re: [Libreoffice-qa] request for more boilerplate responses to bug report
Hi All, Am 10.09.2014 um 02:55 schrieb Terrence Enger: I have noticed that Urmas has been abruptly closing bug reports that are in languages other than English. What an arrogant behavior :-( I do wish he'd do it more tactfully - I close them also but I leave a comment and direct them to their native mailing list for translation. How about first putting them into NEEDINFO state and asking for translation here or in the l10n list? I'm not a 100% fan of this because then the description is not in English and we have to dig down to find where it is translated at. There were several localization bugs written in German I remember - they were perfectly handled by the NL-Team in their native language without any need to translate them back and forth. This might be true for other bug reports too as there are still many people in the world not speaking english. A NEEDSTRANSLATION keyword could also help if we could somehow report those bugs to an appropriate list (l10n would be my choice if people there agree but qa might even be better as most qa-interested NL-folks at least lurk here). At this point I don't see enough of these to add yet another whiteboard/keyword. A total of 6 seems too low for yet more things to track. The French ones are surprising as we have the French BSA, we are talking about other native BSA's also but in all honesty, hard to justify the time when the #'s are this low. Just my thoughts. Best, Joel ___ 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/
Re: [Libreoffice-qa] request for more boilerplate responses to bug report
On Wed, Sep 10, 2014 at 9:47 AM, Joel Madero jmadero@gmail.com wrote: Hi All, Am 10.09.2014 um 02:55 schrieb Terrence Enger: I have noticed that Urmas has been abruptly closing bug reports that are in languages other than English. What an arrogant behavior :-( I do wish he'd do it more tactfully - I close them also but I leave a comment and direct them to their native mailing list for translation. Ideally I'd like all of the reporting/translation work to go on in the same bugtracking tool, but that's beyond the capabilities of Bugzilla (and I don't believe it's on anyone's roadmap). I just chatted w/Sophie in IRC, and she thought the l10n (Localization) list was a good idea. She suggested putting the particular language (if you can identify it) in the Subject: line, to ensure that you get a response. Whatever we decide, we should document it under BugTriage on the wiki :-) Cheers, --R -- Robinson Tryon QA Engineer - The Document Foundation LibreOffice Community Outreach Herald qu...@libreoffice.org ___ 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/
Re: [Libreoffice-qa] request for more boilerplate responses to bug report
Hi all, Le 10/09/2014 16:18, Robinson Tryon a écrit : On Wed, Sep 10, 2014 at 9:47 AM, Joel Madero jmadero@gmail.com wrote: Hi All, Am 10.09.2014 um 02:55 schrieb Terrence Enger: I have noticed that Urmas has been abruptly closing bug reports that are in languages other than English. What an arrogant behavior :-( I do wish he'd do it more tactfully - I close them also but I leave a comment and direct them to their native mailing list for translation. Ideally I'd like all of the reporting/translation work to go on in the same bugtracking tool, but that's beyond the capabilities of Bugzilla (and I don't believe it's on anyone's roadmap). I just chatted w/Sophie in IRC, and she thought the l10n (Localization) list was a good idea. She suggested putting the particular language (if you can identify it) in the Subject: line, to ensure that you get a response. Yes,my suggestion is something like in this message: http://go.mail-archive.com/jWFxpBARvvOlKbeFtTj3jZD9lrA= with bug translation in XX language as a subject. Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org Tel:+33683901545 Co-founder - Release coordinator Certification Committee Member The Document Foundation ___ 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/
[Libreoffice-qa] PT EN translation needed for bug report
Could please someone understanding Portuguese have a look at these bugs and translate them: https://bugs.freedesktop.org/show_bug.cgi?id=83681 https://bugs.freedesktop.org/show_bug.cgi?id=83673 https://bugs.freedesktop.org/show_bug.cgi?id=83629 Thanks, Nino (proof of concept, QA + l10n lists) ___ 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/
Re: [Libreoffice-qa] PT EN translation needed for bug report
I received a translation by PM and added it to the bugs. Though, the reports don't look very clear to me, therefore the whole action was of little value I fear. But perhaps now somebody of the QA experts is able to sort out what the reporters wanted to say. Nino Am 10.09.2014 um 18:26 schrieb Nino Novak: Could please someone understanding Portuguese have a look at these bugs and translate them: https://bugs.freedesktop.org/show_bug.cgi?id=83681 https://bugs.freedesktop.org/show_bug.cgi?id=83673 https://bugs.freedesktop.org/show_bug.cgi?id=83629 Thanks, Nino (proof of concept, QA + l10n lists) ___ 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/ ___ 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/
Re: [Libreoffice-qa] BSA 2.0 - First Draft of Concept Questions
On 09/10/2014 03:16 PM, Joel Madero wrote: We've been talking about this for quite some time. *Idea: *A BSA that gives users a 1 question at a time approach with almost exclusively yes/no answers. By filling out the information the bug report gets appropriate importance, severity, version, attachments, etc . . . The attached document has a first draft of the flow that I envisioned -- suggestions welcome. Best, Joel ___ 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/ Joel, Question about the second step. 2.What was the earliest version of LibreOffice that showed this bug? If there is only to be a checklist for this question, it is important to offer the option I have not done the steps which caused the bug until this version. and/or This is the first version of LibreOffice I have used. I think it isn't wise to make a person think they are remiss for not encountering a bug during the earlier versions of LO. The rest of the sequence seems logical and easy to follow, especially for a novice bug submitter. Will this sequence put off a veteran submitter? --Algot -- - Algot Runeman algot.rune...@verizon.net Web Site: http://www.runeman.org Twitter: http://twitter.com/algotruneman/ Open Source Blog: http://mosssig.wordpress.com MOSS SIG Mailing List: http://groups.google.com/group/mosssig2 ___ 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/
Re: [Libreoffice-qa] BSA 2.0 - First Draft of Concept Questions
Hey Algot, Question about the second step. 2.What was the earliest version of LibreOffice that showed this bug? If there is only to be a checklist for this question, it is important to offer the option I have not done the steps which caused the bug until this version. and/or This is the first version of LibreOffice I have used. +1 The rest of the sequence seems logical and easy to follow, especially for a novice bug submitter. Will this sequence put off a veteran submitter? Well veteran submitters tend to go right to FDO so they wouldn't have to answer these questions :) Best, Joel ___ 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/
Re: [Libreoffice-qa] BSA 2.0 - First Draft of Concept Questions
Hey Joel, Yes i think a step by step process is a nice user friendly way to go. When Calligra Words crashed on me, their step by step bug report was fun to go through. About your doc, here are some thoughts. 1) I'm assuming that many users coming to the BSA are coming through the Help Send Feedback menu item and the libreoffice version number will be provided through this link, so the first question should be for the user to enter in the libreoffice version they are using and that the list be automatically set to the version present in the link. After the user selects his version, or simply clicks ok as his version is already selected, then either it takes him to the 'please upgrade your version' notice or step 2. 2) I think we should ask them to download the latest stable/still version if they are running an EOL version or if they are on an older version of the current stable/still. 3) Step 2 should be asking the user for his operating system, with that being automatically selected by means of javascript through the user's browser agent (florian already has that code). 3) Step 3 should be asking them if this is a bug report or an enhancement request and this step should be skipped if the user clicks the two different links on http://www.libreoffice.org/get-help/feedback/ , as presently they link to the same page. 4) Step 4 is only for users who are submitting a bug report and that asks them if this bug had happened in a previous version and shows the version list with the first entry being something like i'm not sure. 5) I think it would be great to have bug priority set by simple yes/no questions, but think that is the job of the QA team to set that feature, and a simple yes/no question of whether it hangs/crashes is sufficient for BSA bug reporters. Regards, Jay Philips On 09/10/2014 11:16 PM, Joel Madero wrote: We've been talking about this for quite some time. *Idea: *A BSA that gives users a 1 question at a time approach with almost exclusively yes/no answers. By filling out the information the bug report gets appropriate importance, severity, version, attachments, etc . . . The attached document has a first draft of the flow that I envisioned -- suggestions welcome. Best, Joel ___ 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/ ___ 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/
Re: [Libreoffice-qa] BSA 2.0 - First Draft of Concept Questions
On 09/10/2014 04:32 PM, Jay Philips wrote: Hey Joel, Yes i think a step by step process is a nice user friendly way to go. When Calligra Words crashed on me, their step by step bug report was fun to go through. About your doc, here are some thoughts. 1) I'm assuming that many users coming to the BSA are coming through the Help Send Feedback menu item and the libreoffice version number will be provided through this link, so the first question should be for the user to enter in the libreoffice version they are using and that the list be automatically set to the version present in the link. After the user selects his version, or simply clicks ok as his version is already selected, then either it takes him to the 'please upgrade your version' notice or step 2. Not sure I'm following this. 2) I think we should ask them to download the latest stable/still version if they are running an EOL version or if they are on an older version of the current stable/still. I strongly disagree - if it's fixed in Fresh - that is sufficient 95% of the time (ie. we're not going to go dig through to find a backport if stable isn't fixed). The idea here is to lessen the load on QA, not to increase, and this would increase it. Else they download stable, confirm that their minor bug is still in it, report, we find that it's fixed in Fresh, and just set to WFM. This is not the ideal situation. They can always download stable - we'll just direct them to the Fresh page, if they go to the Stable branch, fine. 3) Step 2 should be asking the user for his operating system, with that being automatically selected by means of javascript through the user's browser agent (florian already has that code). Takes more work to implement. Florian's thing is a concept, not currently workable without additional steps by user. 3) Step 3 should be asking them if this is a bug report or an enhancement request and this step should be skipped if the user clicks the two different links on http://www.libreoffice.org/get-help/feedback/ , as presently they link to the same page. Again this takes more work and coding WITHIN LibreOffice but I'm not opposed to the idea. 4) Step 4 is only for users who are submitting a bug report and that asks them if this bug had happened in a previous version and shows the version list with the first entry being something like i'm not sure. Yup agreed. 5) I think it would be great to have bug priority set by simple yes/no questions, but think that is the job of the QA team to set that feature, and a simple yes/no question of whether it hangs/crashes is sufficient for BSA bug reporters. This would just set a quasi setting that could always be changed, I disagree that we can't ask users to help us. Else - the reality is we don't have the time to even triage bugs let alone deal with prioritizing them. A rough idea through 4 questions seems fine and if users are unhappy answering 4 simple questions, I have little patience for taking my time to triage their bugs. Best, Joel ___ 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/
