Re: [DISCUSS] Concerns about the Arrow Slack channel

ing" rather than seeking out the mailing > >> list or JIRA. We'd rather capture the information somewhere rather > >> than lose it. We have an issue template asking people to either use > >> the mailing list or JIRA, but a lot of people ignore it unfortunately: &

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 i

Re: [DISCUSS] Concerns about the Arrow Slack channel

me way that makes it > easy to go back and look at specific topics without having to piece > together a topic's history from a large tapestry of interactions. If > anything, I view chat as *more* intrusive since there's IMO an expectation > of a faster response given that chat i

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

[jira] [Created] (ARROW-2358) API for Writing to Multiple Feather Files

Dhruv Madeka created ARROW-2358: --- Summary: API for Writing to Multiple Feather Files Key: ARROW-2358 URL: https://issues.apache.org/jira/browse/ARROW-2358 Project: Apache Arrow Issue Type: New