I agree with Johannes' comments. I can see Slack having a role - I'm just wary about opening it up to too many people.
I can certainly see benefit in inviting contributors like Seetaramayya to the Slack channel. If I could suggest that we start with a policy like inviting people who have been active for a few weeks and maybe not yet opening up Slack invites to anyone who asks, just yet. I can do up a short page on cwiki.apache.org about the various comms channels and where common types of question/discussion should go. This will obviously have some of my own biases in it and I don't mind if people edit it or comment on it. On Thu, 9 Feb 2023 at 14:17, Johannes Rudolph <[email protected]> wrote: > > I agree we shouldn't rely on chat too heavily, it's much too easy to > bury information in there and it doesn't scale to more people. It's > nice to quickly coordinate on something or clarify some immediate > questions but it should never get to the point of being the reference > of anything. Once you see a link to slack info in Github or the > mailing list, it's already a smell that we don't information where it > belongs. It's ok to quickly discuss something and then put a > conclusion or state of current thinking into the right ticket or > mailing list discussion. > > It's a completely different question if we want a user-level chat room > somewhere for easy access and feedback (which needs volunteers for > moderation and monitoring for questions etc). Personally, nothing for > me but other people are better (or more tolerant) with sync > communication. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
