# Governance

## Maintainers

ferro-ta is currently maintained by:

- **@pratikbhadane24** — project creator and lead maintainer

## Decision Making

Decisions about the project are made by the maintainers. For significant
changes (new indicator categories, API changes, roadmap priorities) we welcome
community discussion in GitHub Issues before implementation begins.

For minor bug fixes, documentation improvements, and dependency updates, pull
requests may be merged once CI passes and at least one maintainer approves.

For major features (new roadmap stages), an issue or discussion should
be opened first to agree on scope and approach.

## How to Contribute

See [CONTRIBUTING.md](CONTRIBUTING.md) for instructions on setting up a
development environment, coding style, and the pull request process.

## How to Become a Maintainer

Consistent, high-quality contributions over time may lead to an invitation to
become a maintainer. If you are interested, please reach out via a GitHub Issue
or by contacting the project at **pratikbhadane24@gmail.com**.

## Call for Co-Maintainers

ferro-ta is a growing library with 160+ indicators, an active roadmap, and a
community of traders and developers who depend on it.  We are actively looking
for **co-maintainers** to help with:

- Reviewing pull requests and triaging issues
- Adding new indicators and extending the Rust core
- Improving documentation and tutorials
- Managing CI, releases, and dependency updates

**If you are interested**, please open a GitHub Discussion in the
[**Announcements → Co-maintainer interest**](https://github.com/pratikbhadane24/ferro-ta/discussions)
category, or reach out at **pratikbhadane24@gmail.com**.

Ideal co-maintainers have:
- Familiarity with Rust and/or Python numerical computing
- Experience with open-source project workflows (PRs, issues, CI)
- Interest in algorithmic trading or quantitative finance

We value contributions at all experience levels — there is no minimum bar
beyond genuine interest and consistent engagement.

## Code of Conduct

All contributors and community members are expected to follow the
[Code of Conduct](CODE_OF_CONDUCT.md).

## Roadmap

The project roadmap is documented in [ROADMAP.md](ROADMAP.md). Stages 1–20
define the scope of planned work; the current focus is indicated there.