Hi Rolf,
Thanks for your comments. I didn't see your message until Simon Quigley told me about it just now, on IRC and he send me the link to the webpage. Why did you close 1770587? My reason for closing the bug report was that the workaround solved the problem for the reporter. But I understand you in that it is still an open issue upstream. I have linked the bug report to the upstream bug and made a comment at the upstream bug to provide the link to the launchpad bug, and let them know the workaround solved the problem for the user at our end. I will leave the launchpad bug report open, pending resolution at the upstream level. I will also set a bring forward date in my own tracking system to see what progress has been made. Is there anything else I should do on this one? Regarding 379015, that is absolutely not an issue appropriate for papercuts. I was addressing the reporter when I said âperhaps the "papercuts" project.â When I looked again at the papercuts criteria, I realized that it did not apply to this bug and I did not pursue it for this bug report. I agree with you that this bug should not be associated with the papercuts project. 671835 is not even a bug report in it's current form. I submitted this one in the application as demonstration of my ability to respond to a bug reporterâs emotional submission with a diplomatic answer, not as a demonstration of a well triaged bug. I did not assign it a high importance. Right now it is âundecidedâ importance. Asking for apport information I was advised on the IRC ubuntu-bugs channel to use the standard replies for old bugs. https://wiki.ubuntu.com/Bugs/Responses#Old_untouched_bugs That standard response for old untouched bugs, asks for the apport information. I use this standard reply as the basis of my usual âblurbâ for the old bugs. Thanks for your insight into the bug triaging process, Rolf. I applied to be part of the bug control group as I was invited to do so by one of the bug control members, while in conversation on the ubuntu-bugs IRQ channel. I agree that I do have a lot to learn and and am happy for your advice and guidance. Take care Glady -------- Re: Application to Join the Ubuntu Bug Control Team  Thread Previous ⢠Date Previous ⢠Date Next ⢠Thread Next To: gf@xxxxxxxxxxxxxx, ubuntu-bugcontrol@xxxxxxxxxxxxxxxxxxx From: Rolf Leggewie <foss@xxxxxxxxxxxxxxxxx> Date: Tue, 14 Aug 2018 01:58:05 +0800 In-reply-to: <c72809d4c528f2210b904b41dd352...@webmail.look.ca> Openpgp: preference=signencrypt Hello Glady, thank you for being active in bug triage. I'm certainly happy you are attempting to clean out some of the old cruft. I had a look through the list of bugs you provided. Why did you close 1770587? That looks like a valid bug to me. Regarding 379015, that is absolutely not an issue appropriate for papercuts. No nitpick from my end on 912262.  671835 is not even a bug report in it's current form. It is absolutely unclear what happened or where the problem is. Saying this would be high importance is totally premature. I'm not even convinced this is or rather was ever a bug and not simply PEBKAC. Even if this was a bug, there's nothing to make it clear it was a bug in TB. In my opinion, the holy grail of bug triage is to reproduce and understand so that the next step of fixing it can be done. Coming to any conclusions before understanding is entirely premature. In most of the bugs you ask for apport information. Personally, I find that annoying when it happens to me and is not necessary if it's done routinely. 1251059 doesn't really need this, for example. The rare times I consider apport information important is crasher bugs or when I suspect an incompatibility of package versions (or worse, third party packages). Personally, I value some kind of control over my data and don't want it plastered all over the internet. You've done some good work, thank you. You are absolutely on the right track. I disagree with some of the judgements you made but those aren't dealbreakers for the most part except for the closure of 1770587. I'd cast my vote as neutral at this point. I certainly assume that given a few more months, I'd give you an endorsement. Regards Rolf<style type="text/css">td p { margin-bottom: 0in; }h2.cjk { font-family: "Noto Sans CJK SC Regular"; }h2.ctl { font-family: "Lohit Devanagari"; }pre.cjk { font-family: "DejaVu Sans Mono", monospace; }p { margin-bottom: 0.1in; line-height: 115%; }a:link { }</style>
_______________________________________________ Mailing list: https://launchpad.net/~ubuntu-bugcontrol Post to : ubuntu-bugcontrol@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-bugcontrol More help : https://help.launchpad.net/ListHelp
