Certbot Issues and Discussions Policy

Users are not allowed to create Issues directly in this repository. Please open a [GitHub Discussion](https://github.com/certbot/certbot/discussions) first for feature requests and potential bugs. This is due to the recent influx of [AI-assisted contributions](https://www.eff.org/about/opportunities/volunteer/coding-with-eff#ai-policy) and our experiences with them.

**Feature Requests**
To avoid under specified feature requests which may not be relevant to Certbot’s userbase, we’re requiring that all requests begin as discussions that both users and maintainers can weigh in on. Once a discussion reaches a point where a well-understood, actionable item is identified, a maintainer will convert it to an Issue for you. This helps Certbot developers use their time more efficiently and makes it easier for contributors to find issues to work on since every issue is ready to be worked on.

**Bugs**
Our experience maintaining open-source projects shows that many reports that look like bugs turn out to be misunderstandings, environment-specific problems, or configuration issues. If your Discussion clearly identifies a reproducible problem in Certbot’s scope, a maintainer will convert it to an Issue for you.
For any general questions, go to the [Let’s Encrypt Community forum](https://community.letsencrypt.org/) to tap into a group of helpful people with experience and expertise who will respond more quickly than the small development team.

For more details, see [CONTRIBUTING.md](https://github.com/certbot/certbot#contributing) and the [Discussions](https://github.com/certbot/certbot/discussions) tab in this repository.

Read CONTRIBUTING.md and the repository's Discussions tab for the stated contribution process. This issue contains policy guidance rather than a requested documentation change, so no implementation or completion test is identified.

Written by the indexing model from the issue text.