Re: Suggested edit to ReportingBugs
On Tue, 2023-06-06 at 10:37 -0700, chris hermansen wrote: > I don't understand how your wording is substantially different from, > nor more clear than what the link you provided already states: > When possible, this will involve running a command 'ubuntu-bug' alias > 'apport-bug' alias 'apport-collect' > ubuntu-bug buggy-package-name > that will collect information from the local system on the > problematic program, and then open a form in a web browser for your > comments. That text was added in response to my email, and actually was quite helpful. Thanks, Nio Wiklund! -B. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Suggested edit to ReportingBugs
Nio, Christopher, list, On Tue, Jun 6, 2023 at 10:42 AM Nio Wiklund wrote: > Den 2023-06-06 kl. 19:37, skrev chris hermansen: > > Christopher and list, > > > > On Tue, Jun 6, 2023 at 10:01 AM Christopher Beland > > wrote: > > > >> I tried to report a bug today and went in circles for quite a while > >> trying to get to the right place in Launchpad to report an ssh bug. But > >> I kept ending up at: https://help.ubuntu.com/community/ReportingBugs > >> > >> It might be helpful to clarify in the "How to report bugs" section > >> something like this (I can't edit it myself): > >> > >> "This will involve running a command that will collect information from > >> the local system on the problematic program, and then open a form in a > >> web browser for your comments." > >> > > > > I don't understand how your wording is substantially different from, nor > > more clear than what the link you provided already states: > > > > When possible, this will involve running a command 'ubuntu-bug' alias > > 'apport-bug' alias 'apport-collect' > > > > ubuntu-bug buggy-package-name > > > > that will collect information from the local system on the problematic > > program, and then open a form in a web browser for your comments. > > > > By my count this text starts three lines down in the second section, > > entitled *How to report bugs.* It seems pretty clear to me, and it's > close > > to the top of the page so no scrolling required. > > > > > > > >> > >> There's a huge number of sections on this page you need to read through > >> before you discover that's what's going to happen, even for a non-crash > >> bug. (I'm used to reporting non-crash bugs for Fedora directly into a > >> web page.) > >> > > > > This doesn't reflect my experience on that page. The basic info you > > suggest is right near the top. > > > > > > Hi Chris, > > I think you are referring to what I edited into the page after Beland > suggested it. > > Please have patience with me, if I misunderstand your response. > > Best regards > Nio > In that case, my apologies to all for my too-slow reactions and please consider my comments as 100% approval of Nio's work! -- Chris Hermansen · clhermansen "at" gmail "dot" com C'est ma façon de parler. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Suggested edit to ReportingBugs
Den 2023-06-06 kl. 19:37, skrev chris hermansen: Christopher and list, On Tue, Jun 6, 2023 at 10:01 AM Christopher Beland wrote: I tried to report a bug today and went in circles for quite a while trying to get to the right place in Launchpad to report an ssh bug. But I kept ending up at: https://help.ubuntu.com/community/ReportingBugs It might be helpful to clarify in the "How to report bugs" section something like this (I can't edit it myself): "This will involve running a command that will collect information from the local system on the problematic program, and then open a form in a web browser for your comments." I don't understand how your wording is substantially different from, nor more clear than what the link you provided already states: When possible, this will involve running a command 'ubuntu-bug' alias 'apport-bug' alias 'apport-collect' ubuntu-bug buggy-package-name that will collect information from the local system on the problematic program, and then open a form in a web browser for your comments. By my count this text starts three lines down in the second section, entitled *How to report bugs.* It seems pretty clear to me, and it's close to the top of the page so no scrolling required. There's a huge number of sections on this page you need to read through before you discover that's what's going to happen, even for a non-crash bug. (I'm used to reporting non-crash bugs for Fedora directly into a web page.) This doesn't reflect my experience on that page. The basic info you suggest is right near the top. Hi Chris, I think you are referring to what I edited into the page after Beland suggested it. Please have patience with me, if I misunderstand your response. Best regards Nio -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Suggested edit to ReportingBugs
Christopher and list, On Tue, Jun 6, 2023 at 10:01 AM Christopher Beland wrote: > I tried to report a bug today and went in circles for quite a while > trying to get to the right place in Launchpad to report an ssh bug. But > I kept ending up at: https://help.ubuntu.com/community/ReportingBugs > > It might be helpful to clarify in the "How to report bugs" section > something like this (I can't edit it myself): > > "This will involve running a command that will collect information from > the local system on the problematic program, and then open a form in a > web browser for your comments." > I don't understand how your wording is substantially different from, nor more clear than what the link you provided already states: When possible, this will involve running a command 'ubuntu-bug' alias 'apport-bug' alias 'apport-collect' ubuntu-bug buggy-package-name that will collect information from the local system on the problematic program, and then open a form in a web browser for your comments. By my count this text starts three lines down in the second section, entitled *How to report bugs.* It seems pretty clear to me, and it's close to the top of the page so no scrolling required. > > There's a huge number of sections on this page you need to read through > before you discover that's what's going to happen, even for a non-crash > bug. (I'm used to reporting non-crash bugs for Fedora directly into a > web page.) > This doesn't reflect my experience on that page. The basic info you suggest is right near the top. -- Chris Hermansen · clhermansen "at" gmail "dot" com C'est ma façon de parler. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Suggested edit to ReportingBugs
Den 2023-06-06 kl. 09:03, skrev Christopher Beland: I tried to report a bug today and went in circles for quite a while trying to get to the right place in Launchpad to report an ssh bug. But I kept ending up at: https://help.ubuntu.com/community/ReportingBugs It might be helpful to clarify in the "How to report bugs" section something like this (I can't edit it myself): "This will involve running a command that will collect information from the local system on the problematic program, and then open a form in a web browser for your comments." There's a huge number of sections on this page you need to read through before you discover that's what's going to happen, even for a non-crash bug. (I'm used to reporting non-crash bugs for Fedora directly into a web page.) Thanks! Beland Hi Beland, I think your tip is good, so I made an edit. Everybody concerned, please check it, and feel free to improve it. Best regards Nio -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
