As a bug wrangler, I see a lot of do not come with a build log attached, which requires us to ask them again and again. It keeps bugs from getting to the maintainers, they unnecessarily stay in our list for some days. Looking at the guided report, I see: > Add any additional information you feel may be relevant to thisbug, such as what other programs you had running, and/or information about your computer's configuration. Any information longer than a few lines, such as a stack trace, should be added using the "Create a new Attachment" link on the bug, after it is filed. > Please paste all information from 'emerge --info' in this section! It doesn't matter if you bold it or not, half of the people won't read it anyway. Therefore, I'm asking you to instead continue the flow of the form there and provide an "add an attachment" box that is checked by default. Like this: ---------------------------------------------------------------------- Add attachments | [X] Add an attachment (Complete build log, | Paste the text to be added ... (or attach ...). stack trace, ...) | ----------------------------------------------- | | | | | | | | | | ----------------------------------------------- | Description: [................................] | REST OF THE ATTACHMENT FORM HERE +------------------------------------------------ | [ ] Add another attachment ---------------------------------------------------------------------- When the user unchecks the first box, the attachment sub form should disappear. When the user checks the second box, another attachment sub form will appear. I don't know how reasonable this is to implement, but I'm willing to help with it if you point me out where I can find the source code, how to test my code and where to report a patch. Another change that would be helpful is making New-[Ex] more explicit such that new users are aware which option they picked, currently a lot of unaware users will unintended prefer to click on [Ex] (maybe because it has shiny brackets around it?) whereas they should really have clicked on New. Those users often also set half of the bug form to wrong values, ranging from weird priorities to unrelated Gentoo Developers being CC-ed. Thank you very much in advance...
Can we do something to help with this? Is there a repo to write changes against?
+1, Oh, your proposal would significantly improve user's bugs reporting experience, I would certainly welcome this. never to say it's not convenient to copy-and-paste the output of "emerge --info", but have to attach other info (ususally build log) in another run comment which is quite tedious..
