Contribute

My open source work lives on GitHub. Pick the repository you care about and pick the contribution that fits your time.

Where everything lives

Each repository is the canonical source of truth for its code, docs, issues, and discussion.

You don’t have to write code to be useful.

File an issue when something is wrong on this site. Broken link, wrong status, missing info, typo, accessibility problem — file against mlaify/mlaify.github.io.
Run something on your own hardware and tell me what happened. Real-world reports on real devices and real deployments are how validation coverage grows.
Watch a repo. Releases are announced through GitHub releases.

Improve a page on this site. Spotted a thin section? PR welcome. Content is markdown.
Reproduce and narrow a bug. A clear reproduction against a known version is worth more than a report.

Send a substantive patch to whichever repo you’ve been using. Bug fix, new feature, doc improvement — every repo has issues tagged for help.
Harden something. Test coverage, reliability runs, threat-model review, or documentation for an additional validated environment — the issues list what still needs proving.

License. Each repo’s license is in its LICENSE file (MIT unless specified otherwise). Contributions follow the repo’s license.
PR style. Match the existing style. Run formatters/linters. Keep PRs scoped — small, single-purpose changes get reviewed faster.
Security disclosure. For security-impacting issues, follow the disclosure policy in the relevant repo’s SECURITY.md. Do not file public issues for unpatched vulnerabilities.
Code of conduct. Treat people well. Mistakes are expected; bad faith is not.

Issues — open in the relevant repository.
Discussions — every repo has GitHub Discussions enabled.
Security — SECURITY.md in the relevant repository for disclosure protocol.
Everything else — reach out to me at mlaify@mlaify.io.

Conversation lives next to the code it’s about. I don’t run a shared chat, mailing list, or Slack.