The Ursa Zulip is not an "official" channel, which is to say that community discussions there about what to build, whether there is consensus about something, etc., are not valid from a governance / Openness standpoint. Those need to take place either on the mailing list or the issue tracker (which at present is Jira).
Arrow had a Slack instance early in its life but it led to behavioral antipatterns — people were asking questions or having discussions about the project in a place where only a small fraction of the community was present. We discussed and deemed that the presence of an Arrow Slack channel was harmful to the community as it was then operating, and so we shut it down. I personally will not use Slack if I have any alternative. The best way to communicate whether someone is working on an issue is to assign it to themselves, and if it is not assigned then it can be assumed to be free to pick up. If any of you want to use a Slack instance somewhere to chat in an IRC like fashion that's completely fine, just please move discussions to ASF channels when something of relevance to the community is being discussed. On Wed, Mar 10, 2021 at 12:15 PM Antoine Pitrou <anto...@python.org> wrote: > > > > Le 10/03/2021 à 19:15, Antoine Pitrou a écrit : > > > > Le 10/03/2021 à 19:04, Antoine Pitrou a écrit : > >> > >> Hi Andy, > >> > >> Le 10/03/2021 à 19:00, Andy Grove a écrit : > >>> We had a discussion on the Arrow Rust Sync call about the best place to > >>> co-ordinate on work. For example, quick questions like "is anyone working > >>> on ARROW-12345? should I pick this up?". > >>> > >>> I know that Ursa Lab hosts Zulip and I have used that in the past for > >>> these > >>> types of discussion. > >>> > >>> I also found out today that there is an official ASF slack with multiple > >>> Arrow channels, but this is only open to people who already have an > >>> apache.org email address (committers / PMC). > >> > >> I didn't know that the ASF had an official Slack. I suppose that's the > >> Apache way of favoring open source software. > >> > >> I find Slack uncomfortable and annoying to deal with, and I wouldn't go > >> there. > > > > That said, and to answer your question a bit more completely, I don't > > there a requirement that all Arrow implementations use the same chat system. > > Wow, sorry: I don't think there's a requirement that ... >
