So you might be interested in contributing to Otomi, awesome! This guide will help you understand the overall organization of the project, and direct you to the best places to get started contributing. You'll be able to pick up issues, write code to fix them, and get your work reviewed and merged.
All feedback is welcome!
This document is the single source of truth for how to contribute to the following code bases:
- otomi-core: The heart of Otomi, a monorepo containing all the apps and configurations
- otomi-tasks: The tasks used by core to massage apps to adhere to the configurations
- otomi-clients: The openapi generator for the clients used by the tasks
Before submitting code to Otomi, you should first complete the following prerequisites. Completing these steps will make your first contribution easier:
Code of Conduct
Setting up your development environment
It is not required to set up a developer environment in order to contribute to Otomi, but if you do plan to contribute code changes, follow the readme of the respective
redkubes/otomi-* repo of interest for how to set up your environment.
Community Expectations and Roles
Otomi is a community project. Consequently, it is wholly dependent on its community to provide a productive, friendly and collaborative environment.
Please read and review the Community Expectations for an understanding of code and review expectations.
Otomi is just starting its open-source community. As many open source projects often do, it depends on new people becoming members and regular code contributors. Please consider joining Otomi!
We use the following channels for communication:
- Discord (needs the Discord client)
- Gitter (doesn't need a client, just a browser and your github login)
Events and meetups
Otomi participates in KubeCon and other events and meetups (mostly online nowadays) all over the world. Information about these and other community events is available on the Redkubes community page.