So my whole view on this is that I agree with Seetaramayya that having a chat channel of some sort is a net benefit. After trying to contribute to projects that don't have an active chat channel you do end up feeling the difference, basically a place where you can ask off the cuff questions without expecting a reply and also general coordination which can be considered too fine grained/detailed for a mailing list, or even github
I do see the issues that PJ Fanning mentioned, to me this is just revealing the underlying chaos and flux the project is in. This is not for bad reasons, but as Jean-Luc Deprez said in another email thread we are moving at light speed and the current slack channel is reflecting that. Ontop of that there are many more open questions and discussion particularly around the release process, I also do imagine that this will subside over time. This rapid pace of development between a small set of committers will hopefully be temporary at least until we make a first release but my point here is don't be too quick to judge the premise of a chat channel based on the current state of affairs. I would also say that if we didn't have the slack chat room, we would not have the current velocity that Pekko is undergoing, certain types of communication is far more efficient in a channel than on a mailing list/github. The thing is, irrespective of what we decide the way the current Apache slack is set up a user has to get invited and this already provides a nice buffer against some of the issues being raised. I personally don't feel too strongly about this, we can make a decision to open up the slack room after a release when (if it occurs) development slows down, or we can invite people transparently at our discretion if they make a post on the mailing list stating they would like to join the chat room. On Thu, Feb 9, 2023 at 2:49 PM PJ Fanning <[email protected]> wrote: > 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] > > -- Matthew de Detrich *Aiven Deutschland GmbH* Immanuelkirchstraße 26, 10405 Berlin Amtsgericht Charlottenburg, HRB 209739 B Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen *m:* +491603708037 *w:* aiven.io *e:* [email protected]
