Sending in bug reports.
Try to pin-point the exact problem. Never give vague instructions,
or detail vague problems like "it crashes" or "I get strange interrupt
issues on this one box that I built." Talk to others on IRC or some
other forum to confirm that it is new, repeatable, etc. and make sure
it is not a local problem. And please don't start fixing problems that
require significant work until you are sure you understand them, especially
during our release periods when we must not change major sections of code.
If you are going to write significant amounts of code, check various
forums to make sure that someone else is not working on the problem
(saving duplication of effort).
New features are accepted, especially with code that implements
your suggested new feature.
If someone else writes code for your new feature, the chances are that
it will be misunderstood and created so that you will not recognize it.
Please remember that projects resources are limited.
Donations accepted.
Types of bug reports in order of desirability:
- Repeatable problems with source fixes are the best.
- Repeatable problems that are not specific to your hardware/software
layout.
- Repeatable problems specific to your software layout.
- Repeatable problems specific to your hardware layout.
- Non-repeatable problems -- or problems you do not wish to repeat.