Re: [DISCUSS] Concerns about the Arrow Slack channel

Copying the list of issues with Slack from the vote thread: * Semi-private * Not indexed in search engines * Not managed by the ASF or archived in a public place * Not frequented by many Arrow developers I think because of these things there is no way to claim that Slack is an equivalent

Re: [DISCUSS] Concerns about the Arrow Slack channel

Brian, Leo, and I yesterday discussed creating an ArrowJS channel in the Graphistry Slack as an alternative. Graphistry doesn't mind being the channel admins, we just don't want to run afoul of any ASF guidelines for project organization. On 07/09/2018 11:47 AM, Uwe L. Korn wrote: Bumping

Re: [DISCUSS] Concerns about the Arrow Slack channel

Bumping this thread again as we still have to discuss how to deal with the JavaScript community in Slack. The main difference here with all other parts of the Arrow community is that they are very active users and also use Slack for communication between developers. Paul, Brian & co: Is there

Re: [DISCUSS] Concerns about the Arrow Slack channel

I have just started a vote about closing the channel. On Tue, Jun 26, 2018 at 11:03 AM, Wes McKinney wrote: > I would personally prefer to have all questions on the mailing list > for now. I don't know if the community is large enough to provide > consistent attention on an additional

Re: [DISCUSS] Concerns about the Arrow Slack channel

I would personally prefer to have all questions on the mailing list for now. I don't know if the community is large enough to provide consistent attention on an additional communication channel. If there end up being too many user-centric questions on dev@, we can activate and use user@ as some

Re: [DISCUSS] Concerns about the Arrow Slack channel

It might be nice to have the discourse option before shutting it down. As someone who asks, that would be a nice way to get me to migrate On Tue, Jun 26, 2018 at 10:53 AM, Wes McKinney wrote: > hi folks, > > How would you like to proceed on the Slack channel discussion? It > seems there is

Re: [DISCUSS] Concerns about the Arrow Slack channel

hi folks, How would you like to proceed on the Slack channel discussion? It seems there is reasonable consensus to close the channel. Should we have a vote? It would be a good idea to export the data / chat history from the channel before closing it down. Thanks Wes On Thu, Jun 21, 2018 at

Re: [DISCUSS] Concerns about the Arrow Slack channel

It's sort of unrelated to this conversation, but since someone mentioned MXNet I want to call attention to a thread on their podling mailing list about JIRA vs. GitHub issues: https://lists.apache.org/thread.html/b4d174223d68c5822ea538f2609281c8023c7cc1eaef298bb2c4c186@%3Cdev.mxnet.apache.org%3E.

Re: [DISCUSS] Concerns about the Arrow Slack channel

Thanks all. I'm intrigued by Discourse (for some reason I keep typing "discourge.org"); we should inquire with ASF infra to see if they would be willing to support it for us. It's important that we develop a public record for the project, and for that data to be archived and indexed in some place

Re: [DISCUSS] Concerns about the Arrow Slack channel

Hi everyone, I heard from Kou that you’re discussing to stop using Slack. So I want to propose another way to use Discourse. On 2018/06/21 18:46:54, Dhruv Madeka wrote: > The issue with discourse is that you either have to host it or pay for them > to host it Discourse provides free hosting

Re: [DISCUSS] Concerns about the Arrow Slack channel

The issue with discourse is that you either have to host it or pay for them to host it but still +1 for discourse, its a really nice format (I actually +1'ed the PyTorch forum on this thread too) Dhruv On Thu, Jun 21, 2018 at 2:09 PM, Travis Oliphant wrote: > Hi everyone, > > I'll be chiming

Re: [DISCUSS] Concerns about the Arrow Slack channel

Hi everyone, I'll be chiming in from time to time as Anthony Scopatz and I help several people from Quansight become more integrated to community Arrow development. I'm a fan of Arrow's goals and have similar goals for a cousin project called http://xnd.io. I'm eager to find ways to collaborate

Re: [DISCUSS] Concerns about the Arrow Slack channel

+1 for dropping slack On Thu, Jun 21, 2018 at 11:54 AM, Anthony Scopatz wrote: > I am +1 for dropping slack as well, for all of the reasons mentioned. > > On Thu, Jun 21, 2018 at 11:53 AM Dhruv Madeka wrote: > > > Here's my best guess, emails force everyone on the list to read it, so > they >

Re: [DISCUSS] Concerns about the Arrow Slack channel

I am +1 for dropping slack as well, for all of the reasons mentioned. On Thu, Jun 21, 2018 at 11:53 AM Dhruv Madeka wrote: > Here's my best guess, emails force everyone on the list to read it, so they > have to meet a higher bar of importance? > > Pure guess there, im just channeling my

Re: [DISCUSS] Concerns about the Arrow Slack channel

Here's my best guess, emails force everyone on the list to read it, so they have to meet a higher bar of importance? Pure guess there, im just channeling my experiences- I dont mind mailing dev lists personally Dhruv On Thu, Jun 21, 2018 at 11:28 AM, Phillip Cloud wrote: > Dhruv, > > I'm

Re: [DISCUSS] Concerns about the Arrow Slack channel

Dhruv, I'm curious why the dev mailing list is considered intrusive. Can you expand a bit on that? I've always thought of mailing lists to be *the* place where people go to ask questions about a project in a way that is open to all. They are also archived and organized in some way that makes it

Re: [DISCUSS] Concerns about the Arrow Slack channel

Hi, I didn't know we had a Slack channel. I agree we shouldn't use something that has poor or inexistent archival as a communication channel. The Discourse-based option(s) look better at least in that regard, and probably also for categorization and navigation. Regards Antoine. Le

Re: [DISCUSS] Concerns about the Arrow Slack channel

Not to jump in too randomly, but for jupyter-widgets/bqplot - we haven't found an optimal solution to this. - The dev mailing list is often considered to be intrusive - GitHub issues arent really used for simple questions or non-bug fixes - Gitter remains our

Re: [DISCUSS] Concerns about the Arrow Slack channel

Wes thanks for bringing this up. +1 from me. I rarely use Slack and mostly use the mailing list for communication (for the similar reason that Wes mentioned). Li On Thu, Jun 21, 2018 at 4:25 AM, Wes McKinney wrote: > hi all, > > I wanted to bring up some concerns I have about the Slack room

[DISCUSS] Concerns about the Arrow Slack channel

hi all, I wanted to bring up some concerns I have about the Slack room hosted at http://apachearrow.slack.com. Corporate communications have changed a lot in recent years with the new wave of IRC-like chat systems such as HipChat and Slack. In many companies, Slack has become a preferred form of