Bug fixes to Dropbear are welcome if they have been tested and understand the problem.
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, they are a burden.
Do not send any LLM generated security reports without first having a human understand the content and confirm that it is valid.
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
them into the appropriate commit. git log should show a nice
history, not a bunch of "Update for review feedback" commits.
DEVELOPING.md has some more notes on style.