Well, obviously I agree (if you click GrAnd's link to the related discussion).
Even the fact that I was directed here to make the request suggests that it is really difficult to know where to post things, and where to go hunting for things.
It certainly seems to me that the most appropriate place to have a child board for bug reports is together with the child boards for all of the different builds. The place you go to find out things about them, to discuss them and ask questions about them would seem the logical place to also report bugs in them.
Also, I would make one further distinction regarding GrAnd's suggestion: I would have two distinct child boards for what he described; one specifically for bug reports, and another for feature requests. They are two distinctly different things; one relates to problems found in existing code, and the other relates to requests for additional code to be written.
Due to the cross-breeding of the various builds, it seems to me (though I certainly could be wrong) that one board should be the central repository for bug reports, as the same bug may occur in more than one of the major builds. (And likewise, feature requests should have one central repository, so that developers can find all requests in one place, instead of hunting all over, or just missing requests because they were not easily found.
As fantastic an amazing as all of these builds are (and they truly are!), if they have bugs that prevent features from being used, that isn't good for anyone. I'm sure that the developers don't want significant bugs in their code, and as a user, I would like the full benefits of fully working builds.
It is in everyone's best interest to have a known place where bugs can be reported and the location of fixes, when available, can be obtained.
Thanks for anyone who can help in this cause.
Tom Friend