Hi Patil, We sincerely appreciate your interest in contributing to the ECharts project! Here are some important guidelines: You can directly engage in discussions with the community in GitHub issues. ECharts Committers may not always be able to keep track of all issues and Pull Requests. Thus, if you need the help of Committers, the most straightforward way is to let us know on the mailing list, just as you did in this email. If you plan to attempt fixing the ECharts source code, it is recommended that you start with issues labeled "difficulty: easy". These are issues we've identified as bugs and are relatively easy to fix. However, please note that some of these issues might be quite old. You need to first check if the problem still persists in the latest version. Here is a recent issue you can try to fix: https://github.com/apache/echarts/issues/21418 Our main communication channels are the mailing list and GitHub issues. We suggest giving priority to communicating in GitHub issues, as it makes it convenient for those who come across the problem later to follow up. If an issue or PR doesn't receive a timely response, you can inform us on the mailing list. That's all for now. You can let us know whenever you encounter any problems. Once again, thank you for your support to the ECharts project. We highly rely on community contributions, and your efforts can greatly assist a large number of developers.
Thanks *Ovilia* On Sat, Dec 13, 2025 at 3:33 AM Vedant Patil <[email protected]> wrote: > Hi ECharts Community, > > My name is *Vedant Patil*. I am a full-stack developer (MERN Stack), and I > would like to contribute to the ECharts website. > > *Current Status:* > > - > > *Documentation:* I have reviewed the Code of Conduct, Contribution > Guidelines, and Coding Standards. > - > > *Local Setup:* I have partially set up the development environment with > *echarts-www,* *echarts-website.* > > I have already identified a few bugs and potential UI improvements on the > website. > > *Questions:* > > 1. > > *Workflow:* Should I open a GitHub Issue for these bugs first, or can I > discuss here and submit a Pull Request with fulfilled issue directly? > 2. > > *Tasks:* Are there any specific "good-first-issues" for the website you > recommend I start with? > 3. > > *Communication:* Aside from this mailing list, are there other active > channels (like Slack or Discord) to connect with maintainers? > 4. > > *Setup: *Are there any suggestions/guidelines related to the GitHub repo > setup apart from the mentioned wiki pages? > > Looking forward to your guidance. > > Best regards, > > *Vedant Patil* >
