The best answer to this question can be found in a Be Newsletter article by Melissa Rogers titled "Bugs!".
You can also read about what makes a good bug report (with good being defined as "likely to be looked at seriously") in a more recent Newsletter article, by one of the folks who reads those bug reports, in BYOB (Bring Your Own Bugs)
Ideally, you'll take the time to enter the bug into our database via the web form (one bug at a time, please!) at:
This is the best way for you to report a bug to us, as it ensures that it gets into our tracking system.
Failing that, please submit bug reports to us via e-mail, at firstname.lastname@example.org (these take more time for us to examine, though).
The more detailed and specific you are in your bug report, the more likely we are to be able to track it down and fix it. Taking a few extra minutes to fully describe what you were doing, what happened, why this isn't what you expected, and to describe your system configuration is extraordinarily helpful to us, and we really appreciate it when you are able to do it.
You can see the fruits of your labors and learn even more about how Be handles bugs by viewing the BeOS Bugs On-Line database of public BeOS bugs at: