Bug fixes and bug reports to Dropbear are welcome.
New features may be accepted, depending on whether they fit with the style of the project. Remember that every new feature has maintenance burden and future bug surface.
Concise PR messages and Issues are more likely to be read - plain text is usually better than formatted markdown (code blocks are an exception).
LLM contributions are not wanted. Please do not open Issues or PRs
written by LLMs.
Do not send any LLM generated security reports without first having a
person understand the content and confirm that it is valid.
High impact security issues should be reported privately via email. Low impact issues can be reported as normal bugs. Email is fine if you're uncertain of the impact.
Commit messages should be written to match the style of the project. Pay attention to describing the change, and also formatting such as line wrapping.
"Fixup" commits shouldn't be pushed to PRs - instead squash and rebase the PR as you go. Avoid merging main branch back into a PR branch, that makes it more work to rebase later.
DEVELOPING.md has some more notes on style.