Contributors are essential. Here is some advice to help you help the project.
We try to keep mmlib as lean and fast as possible and to conform as close as possible to POSIX.
We use gerrit for code review. If you are unfamiliar with it, please look at this gerrit walkthrough
Debian provides a package git-review that helps submitting git branches to
gerrit for review.
The core mmlib library code follows a coding style enforced by uncrustify with a configuration file written in tools/uncrustify.cfg
You can also use the build targets checkstyle and fixstyle to do the check
for you.
Please consider adding tests for your new features or that trigger the bug you are fixing. This will prevent a regression from being unnoticed.
Maintainers tend to be picky, and you might feel frustrated that your code (which is perfectly working in your use case) is not merged faster.
Please don't be offended, and keep in mind that maintainers are concerned about code maintainability and readability, commit history (we use the history a lot, for example to find regressions or understand why certain decisions have been made), performances, integration, API consistency (so that someone who knows how to use mmlib will know how to use your code), etc.
Thanks for reading, happy hacking!