The top of the Enter Bug page says: "Before reporting a bug, please read the bug writing guidelines, please look at the list of most frequently reported bugs, and please search for the bug." with links to important pages describing the info needed in a bug report (preprocessed source, output of "gcc -v" etc.) as well as suggesting checking for compiler warnings before reporting a non-bug. Many first-time bug reporters apparently don't read the guidelines because they don't submit testcases, don't provide the compilation command, don't say which compiler version they're using etc. which requires a maintainer to reply asking for that info and set the bug to WAITING, wasting time and effort for the reporter and maintainers. I think the notice at the top of the page could be far more prominent, maybe it could even duplicate some of the most important info from the top of the http://gcc.gnu.org/bugs page.
If you attach a mockup, I can easily write the corresponding code. This new big notice should only be visible to users with no privileges, right? I guess that all users with editbugs privs know what is appropriate to report and what is not.
I was assuming it would be visible to everyone because it's harmless and can be ignored (I'm sure many users will still ignore it!) but if other privileged users don't want to see it and it's easy to do then it could be hidden from them
Here's a rubbishy mock up misusing <fieldset> and an existing CSS class, but it makes it much easier to notice http://www.kayari.plus.com/gcc/enter_bug.cgi-1.html
If everybody is happy with this mockup, I can push it live later today. Does it need any formal approval?
I'm certainly not able to approve the change, it'll need some kind of agreement from the lead maintainers, which is why I raised it on the mailing list. I don't know if anyone except me and you has bothered to look at it yet :)
Well the only global maintainer who commented was in favour of it, so let's try the change.
This is why we need it: http://gcc.gnu.org/ml/gcc-bugs/2012-10/msg02459.html
(In reply to comment #7) > This is why we need it: > http://gcc.gnu.org/ml/gcc-bugs/2012-10/msg02459.html I agree we need it but I don't think the above one is a good example as the summary for that bug is "please submit full bug report" :).
(In reply to comment #8) > I agree we need it but I don't think the above one is a good example as the > summary for that bug is "please submit full bug report" :). Close that bug as invalid. I personally don't hesitate to kill such bugs when doing triage in bugzilla.mozilla.org.
I'm in favor of this change and I'll approve it but I don't know how to actually do it.
Instead of a fieldset, I simply put a solid border. Also, I didn't reuse the comment class but hardcoded the style for this block. Are you happy with the color, or do you want something else?
Click the URL link above to see how it looks like. The change has already been applied to GCC Bugzilla.
(In reply to comment #12) > Click the URL link above to see how it looks like. The change has already been > applied to GCC Bugzilla. Is there any way to make the text red rather than yellowish? I am having a hard time to focus on the text.
That looks great to me (I was just being lazy reusing the existing FIELDSET style) Thanks for doing this!
The text is now a bit more reddish. Fixed!
Thanks!
(In reply to comment #15) > The text is now a bit more reddish. Fixed! Thanks that is much better and thanks again for adding this text.