How to Prepare and Submit a Haiku Patch That Maintainers Can Review
Choose an issue, build the affected target, follow style, test narrowly, create a clean change, and respond to review.
Start with the current contribution guide and an issue small enough to reproduce. Build the unmodified target, capture the failing behavior, and discuss architectural changes before spending days on an incompatible design.
Follow Haiku style, keep unrelated formatting out, and add a focused test when the subsystem supports it. Build the exact target plus a bootable image if integration can be affected. Commit with a clear problem-and-solution message and no generated artifacts.
Submit through Haiku’s current code-review system, link the issue, state tested architectures, and respond to feedback by updating the same review. Review is technical collaboration, not a final gate after the design is frozen.