[racket-dev] planet bug reporting interface
[This is intentionally stream-of-consciousness...] The planet home page doesn't say anything about how to report bugs (the word bug really only appears in package descriptions, and error doesn't at all). The same is true of individual packages. So it's really not clear what one should do. There is also a Top Bug Closers [Trac], which is a bit confusing because it looks like it *might* be a mechanism for submitting bug reports, but the Trac interface does not make this obvious. In addition, clicking on the author's page says what tickets they have open but not how to create a new one. To me it's even more confusing that the package's description lists the # of tickets but doesn't have a link to where/what. Okay, after nearly eight minutes of searching I found that I need to look for the New Ticket link! It was under the fold (ie, I needed to scroll down) in my browser. This was all probably completely intuitive to the designer, but it wasn't at all so to me even though, as outlined, I was trying my darndest to find a way to report a problem, but couldn't find how. I suggest that there are already enough words floating around (bug, error, problem, issue) that adding one more (ticket) is unnecessary. I recognize that ticket is more neutral (eg, can include a feature request), but still. Also, I think a prominent link entitled something like Report a problem (ideally the same text as in the Help menu -- so I guess Submit Bug Report...) would be good. Of course, that then takes you to to the open bugs portion of the package. In the CSS styling there, a little more space around the line with [All Tickets] [New Ticket] would also make it easier to find the latter. Shriram _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] planet bug reporting interface
FWIW, ticket is a trac term and while I agree that it would be good to avoid another piece of vocab, that's not something I think we'll change before planet 2.0. Robby On Tue, Sep 6, 2011 at 8:20 AM, Shriram Krishnamurthi s...@cs.brown.edu wrote: [This is intentionally stream-of-consciousness...] The planet home page doesn't say anything about how to report bugs (the word bug really only appears in package descriptions, and error doesn't at all). The same is true of individual packages. So it's really not clear what one should do. There is also a Top Bug Closers [Trac], which is a bit confusing because it looks like it *might* be a mechanism for submitting bug reports, but the Trac interface does not make this obvious. In addition, clicking on the author's page says what tickets they have open but not how to create a new one. To me it's even more confusing that the package's description lists the # of tickets but doesn't have a link to where/what. Okay, after nearly eight minutes of searching I found that I need to look for the New Ticket link! It was under the fold (ie, I needed to scroll down) in my browser. This was all probably completely intuitive to the designer, but it wasn't at all so to me even though, as outlined, I was trying my darndest to find a way to report a problem, but couldn't find how. I suggest that there are already enough words floating around (bug, error, problem, issue) that adding one more (ticket) is unnecessary. I recognize that ticket is more neutral (eg, can include a feature request), but still. Also, I think a prominent link entitled something like Report a problem (ideally the same text as in the Help menu -- so I guess Submit Bug Report...) would be good. Of course, that then takes you to to the open bugs portion of the package. In the CSS styling there, a little more space around the line with [All Tickets] [New Ticket] would also make it easier to find the latter. Shriram _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] planet bug reporting interface
By the way, something happened recently (in the past week or two) to the tickets on planet. I had opened two tickets in early August to remind myself of things to fix, but a few days ago when I looked, there were no open tickets listed anymore for the package (http://planet.racket-lang.org/display.ss?package=racketui.pltowner=nah22). I still have the confirmation emails (one is below), and the trac ticket URLs now go to some completely unrelated ticket and I can't seem to find mine by searching the trac site. --- nadeem #343: removing entry from empty list of saved entries causes error +--- Reporter: nadeem@…|Owner: nah22 Type: defect | Status: new Priority: minor |Milestone: Component: nah22/racketui.plt | Keywords: Planetversion: (1 5) | Pltversion: +--- removing entry from empty list of saved entries causes error -- Ticket URL: http://planet.racket-lang.org/trac/ticket/343 PLaneT Issue Tracking System http://planet.racket-lang.org/ A Trac-based issue-tracking system for PLaneT, the package repository for Racket _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] planet bug reporting interface
I'm not sure what happened here, but it could have been that I accidentally deleted them because of all of the spam tickets that we get (ie I messed up and thought they were spam or I typed the wrong numbers). I'm very sorry if that was the case. I do try to be careful (and nearly all of the spam goes to a specific package (not yours) so it is usually a big red flag when I'm deleting a ticket that didn't go to that package). Anyways, if that did happen, I'm very sorry. Please do re-file them. Robby On Tue, Sep 6, 2011 at 9:23 AM, Nadeem Abdul Hamid nad...@acm.org wrote: By the way, something happened recently (in the past week or two) to the tickets on planet. I had opened two tickets in early August to remind myself of things to fix, but a few days ago when I looked, there were no open tickets listed anymore for the package (http://planet.racket-lang.org/display.ss?package=racketui.pltowner=nah22). I still have the confirmation emails (one is below), and the trac ticket URLs now go to some completely unrelated ticket and I can't seem to find mine by searching the trac site. --- nadeem #343: removing entry from empty list of saved entries causes error +--- Reporter: nadeem@… | Owner: nah22 Type: defect | Status: new Priority: minor | Milestone: Component: nah22/racketui.plt | Keywords: Planetversion: (1 5) | Pltversion: +--- removing entry from empty list of saved entries causes error -- Ticket URL: http://planet.racket-lang.org/trac/ticket/343 PLaneT Issue Tracking System http://planet.racket-lang.org/ A Trac-based issue-tracking system for PLaneT, the package repository for Racket _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] planet bug reporting interface
OK, no problem. Thanks, --- nadeem On Tue, Sep 6, 2011 at 10:30 AM, Robby Findler ro...@eecs.northwestern.edu wrote: I'm not sure what happened here, but it could have been that I accidentally deleted them because of all of the spam tickets that we get (ie I messed up and thought they were spam or I typed the wrong numbers). I'm very sorry if that was the case. I do try to be careful (and nearly all of the spam goes to a specific package (not yours) so it is usually a big red flag when I'm deleting a ticket that didn't go to that package). Anyways, if that did happen, I'm very sorry. Please do re-file them. Robby On Tue, Sep 6, 2011 at 9:23 AM, Nadeem Abdul Hamid nad...@acm.org wrote: By the way, something happened recently (in the past week or two) to the tickets on planet. I had opened two tickets in early August to remind myself of things to fix, but a few days ago when I looked, there were no open tickets listed anymore for the package (http://planet.racket-lang.org/display.ss?package=racketui.pltowner=nah22). I still have the confirmation emails (one is below), and the trac ticket URLs now go to some completely unrelated ticket and I can't seem to find mine by searching the trac site. --- nadeem #343: removing entry from empty list of saved entries causes error +--- Reporter: nadeem@… | Owner: nah22 Type: defect | Status: new Priority: minor | Milestone: Component: nah22/racketui.plt | Keywords: Planetversion: (1 5) | Pltversion: +--- removing entry from empty list of saved entries causes error -- Ticket URL: http://planet.racket-lang.org/trac/ticket/343 PLaneT Issue Tracking System http://planet.racket-lang.org/ A Trac-based issue-tracking system for PLaneT, the package repository for Racket _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
Re: [racket-dev] planet bug reporting interface
Understood. Hopefully the UI/UX comments in my message will help as you're designing 2.0. On Tue, Sep 6, 2011 at 9:25 AM, Robby Findler ro...@eecs.northwestern.edu wrote: FWIW, ticket is a trac term and while I agree that it would be good to avoid another piece of vocab, that's not something I think we'll change before planet 2.0. Robby On Tue, Sep 6, 2011 at 8:20 AM, Shriram Krishnamurthi s...@cs.brown.edu wrote: [This is intentionally stream-of-consciousness...] The planet home page doesn't say anything about how to report bugs (the word bug really only appears in package descriptions, and error doesn't at all). The same is true of individual packages. So it's really not clear what one should do. There is also a Top Bug Closers [Trac], which is a bit confusing because it looks like it *might* be a mechanism for submitting bug reports, but the Trac interface does not make this obvious. In addition, clicking on the author's page says what tickets they have open but not how to create a new one. To me it's even more confusing that the package's description lists the # of tickets but doesn't have a link to where/what. Okay, after nearly eight minutes of searching I found that I need to look for the New Ticket link! It was under the fold (ie, I needed to scroll down) in my browser. This was all probably completely intuitive to the designer, but it wasn't at all so to me even though, as outlined, I was trying my darndest to find a way to report a problem, but couldn't find how. I suggest that there are already enough words floating around (bug, error, problem, issue) that adding one more (ticket) is unnecessary. I recognize that ticket is more neutral (eg, can include a feature request), but still. Also, I think a prominent link entitled something like Report a problem (ideally the same text as in the Help menu -- so I guess Submit Bug Report...) would be good. Of course, that then takes you to to the open bugs portion of the package. In the CSS styling there, a little more space around the line with [All Tickets] [New Ticket] would also make it easier to find the latter. Shriram _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev _ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
