The reporting guidelines aren't well fitted

[Alberto Salvia Novella]

https://youtu.be/4HrCfXKyZLo

[Colin Watson (cjwatson)]

(Please consider trying to frame your bug reports in text form; video bugs take much longer for developers to process.)

The text of the Ubuntu bug reporting guidelines is controlled by the Ubuntu team and is not the proper subject of a bug report against Launchpad itself. I'd suggest discussing the details of those guidelines on the ubuntu-bugcontrol mailing list instead of here.

The only part of this that I think is about Launchpad itself is that the bug reporting guidelines appear after you've been prompted to supply the information that they relate to. I think we could be persuaded to move them up the page a bit so that things flow in the right order. Would that help?

[Alberto Salvia Novella (es20490446e)]

Colin Watson:
 > I think we could be persuaded to move them up the page a bit so that
 > things flow in the right order. Would that help?

That depends a lot on what the text would be, if it's something crucial
or just for solving some doubts. I would leave that decision for after
discussing the text.

On the other hand I would change the titles so they suggest including
the key information, as something like this:

"Summary" to "Consequence of the bug"
"Further information" to "Steps to reproduce and relevant info"

Thank you 👍

[Alberto Salvia Novella (es20490446e)]

Colin Watson:
> Please consider trying to frame your bug reports in text form; video
> bugs take much longer for developers to process.

I know it takes longer to study the issue, but it's far more easy to
understand and decide on it.

http://economist.com/node/14299017

[Colin Watson (cjwatson)]

No, this can't depend on the text. The UI here needs to be appropriate for all bug reporting contexts, not just for Ubuntu. If it seems that in general the guidelines should be displayed before some form elements, then we can make that change in general, but it won't be an Ubuntu-specific change.

We'll consider your suggestions for the titles, although I'm not convinced about that rephrasing of "Summary"; the consequences of a bug may often be far too long for a short one-line summary suitable for displaying in bug listings.

Regarding text/video:

 * You don't know other people's circumstances. For instance, I find it uncomfortable to wear headphones for any more than a short period of time and so often don't have them to hand, which means that to watch a video at all I need to be in a quiet place where I'm not disturbing anyone else, which can be pretty challenging since I have small children at home. And what about hearing-impaired or even sight-impaired developers, of which we have none to my knowledge right now but we easily might? Text avoids this problem.
 * Accent comprehension can be difficult. I'm afraid I find yours somewhat hard to follow (this is just a statement of fact and not intended as any kind of insult - I'm sure you might also find mine difficult to follow, as many do!). Text avoids this problem.
 * On the contrary, I can understand and make good decisions on pages of text in a short period of time really quite easily. It's what I do for a living. Video is appropriate for some cases (the results of formal user testing sessions; some cases of complex user interaction bugs), but it's not required to describe most issues with web pages.
 * When you're asking for a developer's time to fix a problem, and they say that they would find it easier if you described things in a different way, it might not make sense to argue with them about what they would find easier?

[Alberto Salvia Novella (es20490446e)]

Colin Watson:
> The UI here needs to be appropriate
> for all bug reporting contexts, not just for Ubuntu. If it seems that
> in general the guidelines should be displayed before some form elements

Makes sense to me.

Colin Watson:
 > We'll consider your suggestions for the titles, although I'm not
 > convinced about that rephrasing of "Summary"; the consequences of a
 > bug may often be far too long for a short one-line summary suitable
 > for displaying in bug listings.

Well you got the point, what's the important part.

Colin Watson:
 > Regarding text/video:

Okay, I will think about that.

Many thanks 🖏