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
