> What kind of discussion do you mean? As the ECharts community grows, I would expect everyone to have different expertise about different domains and be able to help give different perspectives in different discussions.
For this specific scenario, as a contributor to ECharts, it would have been nice to see some form of discussion about the current pain points of GitHub issues, the potential solutions and why the chosen solution was selected as the way forward. This way the community can help contribute to the direction of the project. This also makes it easier for people from the outside to learn and participate in this project. >From an outside perspective, it seemed like it was just decided by the maintainers internally without giving the community an opportunity to chime in. The only information I could find regarding the issue template change was in the PR [1] which unfortunately did not have much detail as to why or how the decision was made. I hope my explanation was clear. I'd like to see the ECharts community thrive and I think it would be beneficial for the community if it was clear how to see and participate in these kind of discussions. [1] - https://github.com/apache/incubator-echarts/pull/9935 Clement On Fri, Mar 1, 2019 at 2:29 PM Ovilia <[email protected]> wrote: > Hi Clement. > > Thanks for being interested in participation. > > What kind of discussion do you mean? > > If you wish to contribute code, you may filter issues labeled with "bug" > [1], "enhancement" or "new-feature". > If a "bug" issue is not labeled with a "pending" tag, it is checked by our > committers to be a bug and should be fixed. > As for "enhancement" or "new-feature", I guess you should send an email to > the dev mail list asking if this should be supported for now. This is > because some feature requests are used in a limited scenio, so we should > discuss about whether we should provide for all developers and increase the > package size. > I also created a GitHub project [3] containing issues that are easier to be > fixed. So they are suggested for the beginners. > You may also filter with "en" tags for English discription. With the help > of the new issue helper, the "en" tag is created automatically. But for > older issues, we may not have the effort to mark them all. > I'm working on the document about this information. And it will be > available in GitHub document later. > > If it's about a bigger plan, like what's the next step we should take (like > features for next primary version v5.0.0), I guess it's the dev mail list > for now. I'm not sure if we should use something like slack [2] or > gitter [3]. Slack seems a little closed to dev team rather than open to the > public like mail lists, while gitter seems more keen on users rather than > contributors and if we don't have the energy to maintain the how-to > questions in the channels, it may end up with giving users a higher > expectation than we could provide. > I guess slack could be an option for better instant and informal > communication than mail list, although it is also async, of course. There > may also be a concern about not having many people participating in the > discussion. But I guess that is acceptable for the start, and we do wish to > encourage more developers to participate in. > > In conclusion, we are still on the way to find a better solution for > contributing stuff. And you are always welcomed to give advice on it. > And thanks again for asking. :) > > [1] > > https://github.com/apache/incubator-echarts/issues?q=is%3Aopen+is%3Aissue+label%3Abug > [2] https://slack.com > [3] https://gitter.im > [4] https://github.com/apache/incubator-echarts/projects/3 > > Zhang Wenli > http://zhangwenli.com > > > Clement Ho <[email protected]> 于2019年3月1日周五 下午12:27写道： > > > I recently noticed that the issue template for the ECharts GitHub project > > now requests all new issues to be filled through > > https://ecomfe.github.io/echarts-issue-helper > > > > I'm all for better issue management but I was wondering if there was some > > kind of open discussion about this that I could participate in or > observe? > > Is there another mailing list or other form of communication tool that is > > being used apart from this dev mailing list? > > > > > > Clement > > >
