Question: project maintenance status and recommended contact channels

## Context

From what we can see in the repository:

- The project is **not archived**, but recent activity on `master` appears limited to automated commits (dependency bumps and CI updates). The last non-automated commit was on **2025-03-25** ([#555](https://github.com/google/slo-generator/pull/555)).
- There are several **open issues and PRs with no maintainer response**, including bug reports and feature contributions (e.g. [#612](https://github.com/google/slo-generator/issues/612), [#608](https://github.com/google/slo-generator/issues/608), [#605](https://github.com/google/slo-generator/issues/605)).
- [CONTRIBUTING.md](https://github.com/google/slo-generator/blob/master/CONTRIBUTING.md) describes the contribution workflow (PRs, CLA, code review) but does not list a maintainer team or preferred support channel.
- GitHub Discussions appears to be enabled, but we couldn't find dedicated contact links or a security/support policy pointing to a specific team.

## Questions

1. **Is this project still actively maintained?**
If so, what is the expected response time for issues and PRs?

2. **What is the recommended contact channel** for reaching the maintainers?

3. **Is there a public roadmap or prioritization criteria** for incoming contributions (e.g. new backends/exporters, v2 API changes)?

4. **If maintenance is limited**, is there guidance on:
- Whether the project is in "best effort" / community-driven mode
- Whether users should prefer filing issues here vs. using an internal Google channel
- Whether forks or downstream maintenance are encouraged

## Why we're asking

We're considering adopting `slo-generator` in our SLO workflow and want to set expectations with our team around support, contribution turnaround, and the right place to escalate blockers.

Thanks for any clarification, and thank you for open-sourcing this tool.

Start with CONTRIBUTING.md and the repository's enabled GitHub Discussions, then review the open issues and pull requests cited in the message. Done means maintainers document the project's maintenance status, expected response time, recommended contact channel, roadmap or prioritization guidance, and any policy for forks or downstream maintenance.

Written by the indexing model from the issue text.