Thanks, Dave. I actually would like to know if we could have a more informal and short conversation form rather than mail list. Because we usually have to write a long email to state our point of view. And this may take too much time for some cases. I'm not sure if ASF would disapprove on this.
Here's a description about slack: https://slack.com/features Zhang Wenli http://zhangwenli.com Dave Fisher <[email protected]> 于2019年3月1日周五 下午1:30写道： > Hi - > > Sent from my iPhone > > > On Feb 28, 2019, at 9:24 PM, Ovilia <[email protected]> wrote: > > > > I would also like to know the opinions of our mentors. > > Does ASF suggest we have the discussion in something like slack, or > should > > it always be in the mail list for more people to access? > > The Mailing List allows for global asynchronous communication. > > A project may have multiple Git repositories. If there is trouble using > Apache Git facilities then that needs discussion too. > > Regards, > Dave > > > > Zhang Wenli > > http://zhangwenli.com > > > > > > Ovilia <[email protected]> 于2019年3月1日周五 下午1:18写道： > > > >> 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 > >>> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
