Hi Andrew,, I'm happy with mailing list but the only point is when people outside the Apache eco-system want to interact with us. They use to post on social media networks, or direct emails and so on, and then we need to derive here, what could be something they want or not.
It would be great to use some tool that will be more easily accessible by all people or that most of new comers would have directly. But don't know what could be. Real time chats does not seems to me something to drive discussion for the same reason Alex mentioned. We are all in different time zones and some times responses delay 10-12 hours. Regarding Slack tool in concrete, my main concern is that my experience is really bad with it since most of the times I don't get push notifications on my iPhone. While other tools like Telegram works always, Slack don't, and that means sometimes I don't notice a conversation for days. With that in mind is a surprise for me that Slack get so popular, or maybe I have something wrong with it in my devices... Anyway, If we want to use Slack, I think it's ok since as many channels we have the better. Just warn people that maybe not all of us will be there. Or not always available. And key discussions should come to the list. Helping there could be in some cases more easy to do. Thanks! El vie., 6 dic. 2019 a las 21:23, Alex Harui (<[email protected]>) escribió: > > > On 12/6/19, 12:00 PM, "Andrew Wetmore" <[email protected]> wrote: > > I recently had some dealings with ASF staff on the ASF Slack workspace > ( > the-asf.slack.com). Some projects seem to maintain channels there for > coordinating work, but not Royale. Would we gain anything by creating > and > using such a channel as opposed to running all discussions through > email > threads? Or would this just add one more thing to worry about? > > I've seen lots of concern about Slack on the board list. One key > principle of Apache projects is that committers should be able to follow > the project by only being subscribed to dev@. You shouldn't have to be > subscribed elsewhere, not even users@ and especially private@. Some > projects have gotten in trouble for using Slack and other IRC too much. It > isn't that every discussion has to be on dev@, really, only refined > proposals leading to decisions need to be on dev@, but then those who > aren't involved in the early discussions feel left out, or the early > discussion gets voided by input from those not on the channel or not on > during the interactive discussion. > > That said, the ASF is probably going to be forced to reconsider that rule > as chat-based development discussions are the norm in some countries like > China. > > I'm not opposed to a Slack channel for Royale, but I will try to not use > it mainly to make sure there is enough traffic on dev@. Also, the vast > majority of active committers are not in the US where I am, so I won't be > around to interact most often. But if it helps you and others roughly in > your time zone get work done, go for it. > > -Alex > > > -- Carlos Rovira http://about.me/carlosrovira
