In my opinion, here are the most important issues: 1. English/Chinese documentation website divergents 2. Lack of good tests in the codebase 3. Unclear instructions on how to contribute effectively and the workflow 4. Difficult to surface/track what is being worked on in each release in GitHub 5. Difficult to understand release timeline/cadence
On Mon, Aug 26, 2019 at 4:23 AM Ovilia <oviliazh...@gmail.com> wrote: > I've opened a few JIRA tickets in Echarts project that should be done > recently. [1] > You are all welcomed to add more. > > As about the website speed, I've compressed the image resources. But the > main problem remains that sometimes the request is not handled at all so > that compressing resources may not be helpful in this situation. > Currently, waiting for infra with > https://issues.apache.org/jira/browse/INFRA-18919 . > > [1] > > https://issues.apache.org/jira/projects/ECHARTS/issues/ECHARTS-3?filter=allopenissues > > Wenli > > > On Mon, Aug 26, 2019 at 2:14 PM Willem Jiang <ningji...@apache.org> wrote: > > > On Mon, Aug 26, 2019 at 10:56 AM Ovilia <oviliazh...@gmail.com> wrote: > > > > > > Hi Willem, > > > > > > Thanks for the help! > > > > > > We will try our best to put our discussion and conclusion to mailing > > list to let more people know what's going on. > > > > > > > As there are lots of gitbox mail in the dev mailing list, we may > > consider to send these emails to commits@ list instead of flooding the > > dev@. > > > How can we do so? Should I open a JIRA ticket? > > > > You can do it by creating a JIRA in the INFRA. > > > > > > > > > Please don't close the issue if they are not follow the stander > > template by robot. > > > The robot was designed to guide them to ask questions properly to save > > time for both who ask questions and us maintainers. The consideration was > > that that required information (what's expected, what's wrong, demo to > > reproduce) was frequently missing, and without that information, we could > > hardly help, thus ended up with many times of communication. > > > I guess we should start a new thread in dev@ to discuss whether which > > one is a better solution. > > > > > I agree, let's discuss about it in another email thread. > > > > > Thanks! > > > > > > Wenli > > > > > > > > > On Sun, Aug 25, 2019 at 10:54 PM Willem Ning Jiang < > ningji...@apache.org> > > wrote: > > >> > > >> Hi ECharts PPMC, > > >> > > >> I'm really appreciate WuSheng spent a lot of time to point out current > > issues. It's good to see Echart PPMC is planning to do some work to solve > > these issues. > > >> > > >> In Apache we should avoid the internal discussion and keep all the > > develope related information being public. In this way, anyone can join > the > > discussion in any time from any place. It's easy to say but it's hard to > > do if the main developer force are from one company. So we need to some > > adjustment on our daily work, please keep all the project development > > discussion in the mailing list or github issues. > > >> As there are lots of gitbox mail in the dev mailing list, we may > > consider to send these emails to commits@ list instead of flooding the > > dev@. > > >> > > >> To be friendly to the contributor is another part we need to improve. > > >> I found there are bunch of PRs which were not accepted due to the code > > quality. This is common case in the open source world. We should be nice > to > > the new contributor, my suggestion is we could try to accept the PR (if > > most parts are OK) and then we can modify the code later. Please don't > > close the issue if they are not follow the stander template by robot. We > > need to spend some time on the community to help the newbee as community > is > > over code in Apache. > > >> > > >> BTW, I'm willing to offer my help to this project as mentor. Please > > ping me if you need any help from my side. > > >> > > >> Willem > > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org > > For additional commands, e-mail: dev-h...@echarts.apache.org > > > > >
