Roadmap

With ale-py being transferred to farama foundation, we wish to outline our plan going forward.
If you are interested in contributing, please join our discord and put a message in the ale-py channel

- [x] Create a website for documentation on c++ / python interface, usage / install, single and multi-agent environments
- [x] Add native support for Gymnasium (and probably remove support for Gym)
- [ ] Move multi-agent PettingZoo environments to ale-py
- [x] Include ROMs in the PyPI releases (but on not GitHub) then archive AutoROM project
- [x] Add built-in vectorizer based on EnvPool

From Jesse

- [x] Support Linux arm64 builds / possibly other architectures with cibuildwheel
- [ ] Replace pybind11 with [nanobind](https://github.com/wjakob/nanobind) to see if it'll have noticeable performance gains
- [ ] Implement frame maxing in the emulator (I have a PR for this I'll send shortly)
- [ ] Check if we can implement abi3 wheels so we don't have to perform a release when Python releases
- [ ] Add pyi stubs for ale_py.roms ROM imports so users get proper type hints.

This is a multi-item roadmap rather than a single change; begin by reviewing the unchecked plans in the issue, especially PettingZoo environments, nanobind, emulator frame maxing, abi3 wheels, and pyi stubs. No files, tests, or entry points are named, so confirm the scope and relevant project locations with maintainers before starting. Done would mean completing one agreed roadmap item and validating it in the project.

Written by the indexing model from the issue text.