I suggest the documentation that is currently scattered in the chapters "Gentoo Handbook", "Installation docs", and "Documentation" to be summarized into one consistent Gentoo user manual in the style other software products have. Then I suggest this manual to be made available on the website in a one-page edition the same way as there's a one-page edition of the Gentoo handbook (which however covers only part of the topic, mostly installation) at http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1 For example I wanted to search the word "debugging" to learn how to compile an application for debugging in Gentoo. The only one-page doc I found was that Gentoo handbook which of course doesn't contain any mention of the thing I need to know.
The handbook format is laid out the way it is to improve readability. Endless scrolling isn't conducive to readers keeping track of chapters. Content needs to be separated per appropriate subject/topic. You don't buy 500-page books on one long sheet of printout, do you?
Printed books are irrelevant here, this is an electronic document. For example Glibc has a single-page 5MB HTML which is handy for searching. I didn't suggest to have only 1-page version, but I suggest to have also 1-page version (for purpose of searching).
I think we've had enough spam from you for at least a month. Thank you.
Please stop with your personal insults. They don't really help anything. If you think my bugreport is invalid, please explain why.
You have already been given an explanation.
An explanation has been given, but such that I believe to be incorrect. See counterarguments in the post #2. I don't understand why you are acting this way. If you don't want to cope with the report for lack of time, why not set the priority to minimum and leave it for some beginner-janitor to pick it up in the future? I think my original report is reasonable. From my experience on the Ronja build-yourself guides at http://ronja.twibright.com I see that it's the numerous details that make up the website usability and ergonomy. I am not writing these reports to take your time, but to help you to make your website better.
(In reply to comment #6) > An explanation has been given, but such that I believe to be incorrect. See > counterarguments in the post #2. Comment #2 represents your opinion which unfortunately is not the same as ours. We aren't convinced about the importance of a one-page huge guide consisting of great deal of unrelated topics. > I don't understand why you are acting this > way. If you don't want to cope with the report for lack of time, why not set > the priority to minimum and leave it for some beginner-janitor to pick it up in > the future? We do not want to "fix" it because we don't beleive that it's a bug. Is it so hard to understand? > I think my original report is reasonable. From my experience on the Ronja > build-yourself guides at http://ronja.twibright.com I see that it's the > numerous details that make up the website usability and ergonomy. I am not > writing these reports to take your time, but to help you to make your website > better. Thanks for your efforts, but we don't agree with you and thus we do refuse to make the proposed changes. There's no point in playing ping-pong with bugzilla resolution (and we do consider such a behavior abusive).
