One concern of encouraging users to ask how-to questions on the mailing list is that there are not many developers subscribing the mailing list now, and us PPMC members alone may not have enough time to answer the questions by ourselves.
As about Stack Overflow, I don't think the licensing issue is related here because the document talks about copying code from Stack Overflow and contribute to the project, while we are talking about asking how-to-use questions on Stack Overflow to help the users to use. Encouraging users to ask these questions on Stack Overflow rather than the mailing list can help with later users with similar problems to get helped more efficiently since the Stack Overflow has much better SEO than the mailing list. These are my opinions, others are welcomed to discuss the topic here. Wenli On Thu, Aug 15, 2019 at 6:41 AM Dave Fisher <w...@apache.org> wrote: > Hi - > > As part of being an Apache project there are somethings to discuss in > these automated messages. > > > On Aug 12, 2019, at 8:37 PM, GitBox <g...@apache.org> wrote: > > > > <!-- > > Please Use https://ecomfe.github.io/echarts-issue-helper < > https://ecomfe.github.io/echarts-issue-helper> to create the issue. > > This should move to the echarts.apache.org website. > > > Otherwise, it will be closed immediately. > > You really should encourage the use of dev@echarts.apache.org if the user > has questions about how to contribute or if a feature makes sense. > > > Questions in the form of *How to use ...* should be at Stack Overflow > rather than GitHub issue list. > > The Apache Legal Committee recommends the following should a developer > wish to use code from a question or answer on Stack Overflow in the > project. [1] This was discussed a few months back. [2] Here is the > licensing from Stack Overflow. [3] > > The Echarts team should be aware of this requirement. > > Regards, > Dave > > [1] http://www.apache.org/legal/resolved.html#stackoverflow > [2] https://issues.apache.org/jira/browse/LEGAL-459 > [3] https://stackoverflow.com/legal/terms-of-service/public#licensing > > > >
