Welcome to the TiDB Community! We're thrilled to have you here :-) This is a place where users, developers, and the TiDB team connect, share ideas, ask questions, and grow together. Whether you're here to learn, collaborate, or contribute, there's a space for you.
Join real-time conversations on Discord or Slack to connect with TiDB users, developers and the team. Share ideas, ask questions, and get answers to help you grow. If you encounter any problems while opening a PR or creating an issue, feel free to ask for help in discussions!
Stay in the loop! To learn about upcoming events and activities, check out our Discord #event channel. You can also visit our events page for the latest details on meetups, webinars, and more.
Stay updated with TiDB news and discussions by following us on YouTube for tutorials & webinars, and on X for the latest updates.
As will all great open source projects, contributions to TiDB can come in many forms and are always appreciated. Whether it's helping other users, writing blogs, providing feedbacks, reporting bugs, improving documentation, organizing events, etc., every effort makes a difference. Your involvement plays a vital role in shaping TiDB's future.
- We encourage users to support each other by answering questions in the #help channel on Discord and Slack. By helping others, you make the community more valuable for everyone.
-
Share your TiDB experiences, case studies, or insights through blog posts or articles on platforms like Dev.to, Medium, and others. Your content helps the community grow.
-
Host or speak at community events to connect with others and share your expertise. If you have an event or speaking topic in mind, reach out to us, and we'll gladly assist you in bringing it to life.
-
Your feedback helps us make TiDB better! If you encounter a bug or have suggestions, please open an issue in our TiDB repository. Before submitting a new issue, take a moment to check if it's already been reported to avoid duplicates. If you find something similar, feel free to add your thoughts or extra details to the existing thread.
-
If you need assistance during this process, join our discussions to connect with us and other contributors.
-
We invite you to help improve TiDB's documentation! Whether it’s fixing typos, clarifying explanations, or adding new content to reflect recent updates, your contributions make a big difference in keeping the community well-informed and up-to-date.
-
To contribute documentation changes, you can:
-
Use the "Request Docs Changes" Button: For quick edits, go to the specific docs page, and click the "Request Docs Changes" button in the upper-right corner.
-
Submit a Pull Request: For larger updates, fork the repository and create a branch for your changes. After making improvements or adding new content, submit a pull request. Be sure to include a clear description of your changes and the problem they address.
-
-
Ready to contribute code? Review the contribution guidelines and follow the detailed instructions to get started.
-
If you need any help while contributing to our repository, feel free to join our discussions to ask questions, share ideas, and connect with other contributors.
- About Governance:
- Technical Oversight Committee (TOC) serves as the main bridge and channel for coordinating and information sharing across companies and organizations. It is the coordination center for solving problems in terms of resource mobilization, technical research and development direction in the current community and cooperative projects.
- Teams are persistent open groups that focus on a part of the TiDB projects. A team has its reviewer, committer and maintainer, and owns one or more repositories. Team level decision making comes from its maintainers.
Here you'll find everything you need to learn about TiDB. We recommend starting your journey with the following:
-
Online courses:
Thank you to the Kubernetes, Apache and Docker community pages for providing us with inspirations.