Contributing

Mojo is developed in the open. Contributions are welcome in the compiler, the standard library, and the docs. Each area has its own review bar, so start from the contribution guide before you write a large patch.

Find work

• Read open issues tagged for new contributors.
• Docs fixes are a good first patch: broken samples, missing constraints, unclear error text.
• Standard-library changes need tests and a note about stability.
• Compiler changes need a short design comment, because they affect every user.

How to send a change

1. Fork modular/modular. 2. Branch from the current main line. 3. Run the formatter and the tests that cover your change. 4. Open a pull request that explains why the change exists.

Behavior

Discussion on issues, pull requests, and community channels follows the code of conduct. Disagree about the design, and leave the person alone.

See the roadmap for the kinds of work the project is trying to finish, and the vision for the tradeoffs that decide reviews.