Contributing
Contributing
Learn how to contribute to lomi. through code contributions, documentation improvements, and community engagement.
Roles: developer vs contributor vs operator
| Role | Who | CLI / MCP |
|---|---|---|
| Developer (integrator) | Engineer at a merchant building on lomi. | Yes: primary audience for CLI and MCP |
| Merchant (non-technical) | Dashboard-only user | No: use the web dashboard |
| Contributor | Open-source contributor to the monorepo | Sometimes: dogfood integration flows; maintain packages via Maintaining CLI and MCP |
| Platform admin | Internal apps/admin operators | No |
Rule: CLI and MCP help you integrate with the hosted merchant API. They do not operate lomi.’s platform, admin stack, or payment infrastructure.
Writing the docs
Editorial contract for hand-authored guides, API pages, and agent-oriented documentation on docs.lomi.africa.
Maintaining CLI and MCP
Guide for lomi. contributors and operators who develop or deploy apps/cli and apps/mcp, not for merchant integrators.
REST API reference authoring
How we maintain the hand-written REST API section, keep it aligned with OpenAPI, and avoid accidental destructive generation.
Best practices
Following these best practices helps maintain code quality, consistency, and security across lomi. project.
Branching strategy
We follow a Git workflow inspired by GitFlow but simplified for continuous delivery and integration.
Code of conduct
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
Code reviews
Our code review process ensures code quality, knowledge sharing, and maintainability.
Using git
Use Git from the command line when collaborating on your lomi. integration or open-source contributions.
Versioning
We follow Semantic Versioning (SemVer) for all our packages and APIs.