> For the complete documentation index, see [llms.txt](https://docs.pinot.apache.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pinot.apache.org/release-1.2.0/resources/community.md). # Community Most Pinot related discussion happens on the [dev mailing list](https://lists.apache.org/list.html?dev@pinot.apache.org), [Github Issues](https://github.com/apache/pinot/issues) and [Slack](https://communityinviter.com/apps/apache-pinot/apache-pinot). ## Mailing lists For project development: * (subscribe to pinot-dev mailing list) * (posting to pinot-dev mailing list) For general questions and announcement: * (subscribe to pinot-user mailing list) * (posting to pinot-user mailing list) ## Github Star us at [apache/pinot](https://github.com/apache/pinot) to follow Pinot development, ask questions, raise issues, or contribute pull requests. See [Developers and Contributors](/release-1.2.0/for-developers/developers-and-contributors.md) section if you're interested in development. ## Slack Channel Ask questions on [Apache Pinot Slack](https://communityinviter.com/apps/apache-pinot/apache-pinot). ## Twitter Follow us on Twitter [@ApachePinot](https://twitter.com/ApachePinot). ## Meetups See [Apache Pinot on Meetup.com](https://www.meetup.com/apache-pinot/) for upcoming meetup events. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.pinot.apache.org/release-1.2.0/resources/community.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.