Thanks for the summary, Lee. To clarify my intention, I propose the user mailing list out of the goal of making DataSketches graduated to TLP. Apache mailing list might has drawbacks comparing to the others. But it's a consistent way for user discussions across all ASF projects. Moreover, I have an argument from the ASF's point of view:
To be an TLP operating under ASF, it's important to show the user that the project has enough diversity so that no one single player can greatly impact the project. On the other side, the project should also be sustainable under ASF's support w/o being effected by other 3rd party orgs. If we're leverage other tools such as google forum as our official user discussion mailing list, what if google changed the policy or start to charge us? What if google decided not to continue to run forum? Can we get the full dump and import all the historical data back to ASF mailing list? Although the chance of my concern is tiny. I think my point stands. I'm neutral to your proposal of using Slack + archive daily digest to our mailing list. ;) Comments are welcome. Best, Evans leerho <[email protected]> 於 2019年10月24日 週四 上午4:53寫道： > Here is a summary of our Public Communications Channels for DataSketches: > > *Apache Mailing Lists at @datasketches.apache.org > <http://datasketches.apache.org>* > > - commits > - dev > - issues //for all users > - notifications > > *the-asf.slack.com <http://the-asf.slack.com> channels* > > - datasketches //for all users > - datasketches-dev > > *Google Forum for all users* > > - https://groups.google.com/forum/#!topic/sketches-user > > *Every GitHub repository has an "issues" tab available to all users:* > > Open Closed > incubator-datasketches-java 4 31 > incubator-datasketches-memory 1 45 > incubator-datasketches-cpp 0 7 > incubator-datasketches-hive 1 4 > incubator-datasketches-pig 1 4 > incubator-datasketches-postgresql 0 0 > incubator-datasketches-vector 0 0 > incubator-datasketches-characterization 0 0 > incubator-datasketches-website 0 0 > > *In addition, we also track issues on some major external sites where they > have integrated our library such as:* > > - Apache Druid > - Postgresql.org > > I'm not sure we need another one, unless we eliminate some. The advantage > of the Google forum is that it allows separation by topic and is searchable > by Google search and keeps issues forever. The disadvantage of the Apache > mail lists is that it has no organization structure other than threads > (which is quite clumsy). The issue lists in GitHub offer even more > organizational and cross referencing tools and are markdown compatible. > > If we were to have one primary user Q&A "channel" I would favor our new > slack channel "datasketches". Especially once we figure out how to archive > daily digests. > > Comments? > > Lee. > > > > On Wed, Oct 23, 2019 at 11:52 AM Jon Malkin <[email protected]> wrote: > >> I certainly appreciate the idea, but I worry that in practice it will be >> just another way to reach us and need to be supported along with all the >> others. I am wary of adding yet another place that the team needs to keep >> monitoring. >> >> Lee has expressed interest in having a daily digest of the slack channel >> pushed to the mailing list, so maybe that would allow the channel contents >> to be treated as a searchable archive? >> >> jon >> >> On Wed, Oct 23, 2019 at 1:57 AM Evans Ye <[email protected]> wrote: >> >>> Hi team, >>> >>> I was exploring the functionality of DataSketches and I got a question I >>> want to ask. I found right now we use Slack and Google Forum for user >>> interaction: >>> >>> * Google: https://groups.google.com/forum/#!forum/sketches-user >>> * Slack: https://app.slack.com/client/T4S1WH2J3/CHWKFEHUZ >>> >>> I wonder what's the preferred way for the community? >>> I think Slack might not be a good way for "StackOverflow" like Q&A, nor >>> good for searching and cross timezone collaboration, but is very efficient >>> for deep-dive discussions. Google is OK but it does not integrate with >>> ASF's tool for stats and archiving. >>> >>> So, what I'm thinking is to create a [email protected] >>> mailing list for users. What do the community think? >>> >>> Best, >>> Evans Ye >>> >>
