> ## Documentation Index
> Fetch the complete documentation index at: https://aspect.build/llms.txt
> Use this file to discover all available pages before exploring further.

# Contributing

> How to contribute to Aspect's open-source Bazel rulesets and tools, and the tiers Aspect uses to prioritize customer, community, and ecosystem work.

How to contribute to Aspect's open-source Bazel projects, and how we decide what to work on. [Open-source projects](/docs/bazel/open-source) lists the rulesets, tools, and examples we maintain.

## Contributing

We welcome contributions across all of our open-source repositories. Most repositories include a `CONTRIBUTING.md` with project-specific guidelines. General notes:

* **Bug reports and feature requests**: open an issue on the relevant GitHub repo.
* **Pull requests**: include a description of the problem, the approach taken, and any test coverage. We review against the compatibility matrix and supported Bazel versions documented in each repo.

**[Join the Aspect Community Slack](https://slack.aspect.build)**, Aspect's free community support. Ask in `#help` for general support. Join the discussion and see what others are building with the [Aspect CLI](/docs/cli/overview) and [Aspect Extension Language (AXL)](/docs/cli/axl) in the `#cli` and `#axl` channels.

For Bazel and the Bazel rulesets, [Bazel Slack](https://slack.bazel.build) is the best place for support and discussion. Ask about Aspect's [rules\_js](/docs/bazel/javascript) in `#javascript` and [rules\_py](/docs/bazel/python) in `#python`.

## How we prioritize

We take on open-source work in this order:

| Tier | Source | How it's handled |
| - | - | - |
| 1 | Customers with an active statement of work | Scoped and scheduled under the terms of the engagement |
| 2 | [Bazel support](/services) subscribers | Prioritized outside a statement of work. Available consulting hours can fund the change |
| 3 | Other customers | Weighed on impact, feasibility, and fit with the roadmap |
| 4 | Community contributions | Reviewed and merged as capacity allows, after checking quality, test coverage, and compatibility with supported configurations |

These move work ahead of its tier:

* **Ecosystem changes.** Work that keeps a ruleset compatible with the rest of the ecosystem, such as bzlmod migration support, affects every user, so it's prioritized whoever asked for it.
* **Roadmap priorities.** Work on rulesets we've designated strategic can move up regardless of who asked. Current examples: `uv` integration in `rules_py` and platform upgrades in `rules_js`.

## Support

Need more than community support? Aspect offers [commercial Bazel support](/services) in a dedicated Slack channel.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.