Get involved!
Ask questions, be a part of the conversation, or contribute to Istio’s growth. Istio is an open source project that is driven by the participation of users and contributors. Join in!
How do you want to get involved?
Ask questions
There are a variety of ways to reach out to the community for input.
- Bring your particular Istio questions to the gamified wizards of Stack Overflow1.
- The Istio discussion board2 hosts conversations with other Istio users. Join in to ask questions and discuss Istio.
- Join our Slack3 and interact live with other members of the Istio community.
Join the community
There is so much to talk about around Istio. We welcome your voice!
- Attend an event! Follow our calendar4 to see what is coming up!
- Follow us on Twitter - @IstioMesh5
Bugs and Security
Thank you for helping to improve Istio with bug reports or security vulnerability reports.
- Read this quick explanation on how to report bugs6, in code or in documentation.
- The Istio security team responds rapidly to vulnerability reports. Read how to submit an issue7.
Become a contributor
Code, documentation, community: Istio welcomes your contribution! Use these links as your entry point.
- Familiarize yourself with the Istio code of conduct8 and contribution guidelines9.
- The Istio Community README10 is the starting point for contributors who want to work on code, docs or other parts of Istio.
- You can access our trove of technical content and working documents11 by joining the istio-team-drive-access@ Google Group.
- You can participate in the working groups12 which focus on particular areas of interest, such as docs, security, and networking.
- Interested in helping with Chinese language documentation? Join the ServiceMesher community13.
Understand oversight and planning
Istio has two key committees that oversee the project: Steering and Technical Oversight.
- Governance and advocacy for the project are managed by the Istio Steering Committee14.
- Technical direction and project planning is the role of the Istio Technical Oversight Committee15.