IMPORTANT: To view this page as Markdown, append `.md` to the URL (e.g. /docs/manual/basics.md). For the complete Mojo documentation index, see llms.txt.
Skip to main content
For the complete Mojo documentation index, see llms.txt. Markdown versions of all pages are available by appending .md to any URL (e.g. /docs/manual/basics.md).

Mojo contributor guide

Welcome to the Mojo community! 🔥 We're very excited that you're interested in contributing to the project.

The following procedures and guidelines aim to create an environment where open source contributors and the teams at Modular can work together effectively toward the continued improvement of Mojo.

Before you start

  1. Check the contribution areas to see whether the part of the codebase you want to improve is accepting contributions, and which kinds of change it accepts.

  2. For any non-trivial change, open an issue to discuss it before you open a pull request. For a significant change, start with the proposal process instead.

  3. Read our issue and PR etiquette. It sets out what we expect from you when engaging with the modular/modular repository, including our rules on AI-assisted contributions.

  4. Read the Code of Conduct on GitHub.

How a contribution works

The contribution process takes you from signaling your intent on an issue through to your change shipping in a nightly.

For the mechanics of forking, branching, and opening a pull request against this repository, see the Modular contributor guide on GitHub.

Developer guides

If you're reading this page on GitHub, you might find it easier to explore all contributing docs online at mojolang.org/community/contributing/.

Our priorities

  • Our vision document describes the guiding principles behind our efforts.
  • Our roadmap identifies concrete short-, medium-, and longer-term development goals.

Thank you for your contributions! ❤️