I understand that there are too many places to monitor but I don't see a quick way of communication (such as slack or gitter). For example, I would like to request someone to retrigger the build.
Another scenario, once the community starts adopting pekko then they might have questions that are not addressed in docs (or a person overlooked the docs). How can they approach for help? As a user / contributor, I feel a slack or gitter kind of communication is needed but at the same time (from mainter point of view) I see the pain of multiple ways of communication. Just added my thought Regards, Seeta On Thu, Feb 9, 2023 at 8:32 AM Claude Warren, Jr <[email protected]> wrote: > I have to agree with PJ. I think we should try to limit the discussion > areas to as few as possible so that we don't miss questions. There are > already lots of places for discussion, adding one more feels like just > adding to the noise. > > On Wed, Feb 8, 2023 at 6:25 PM PJ Fanning <[email protected]> wrote: > > > My preference is not to use Slack this way > > > > * it's already hard to keep track of conversations that flit between the > > mailing lists, Github issues, Github PRs, Github Discussions - and Slack > > adds another place > > * All ASF discussions should be public (with a small number of > exceptions) > > and Slack is still closed unless we invite people - and only a finite > > number of people will be invited > > * with Github, we have integrations copying conversations to ASF mailing > > lists - we don't have this for Slack - see > > https://lists.apache.org/[email protected] > > * it is important for the conversations to be archived in ASF locations > > because Github and Slack may choose to close down access to ASF and our > > users at a time of their choosing in the future and ASF needs to have a > > record of these discussions on our own managed resources (eg ASF mailing > > lists) > > > > On 2023/02/08 17:26:31 Matthew Benedict de Detrich wrote: > > > This was discussed in the Pekko ASF Slack channel, but as of now only > > Pekko > > > committers are in the Slack channel. The idea is to open this up to the > > > public, as I believe this would best serve the community and is also > the > > > appropriate place for communication whose format is too "casual" for > > > mailing list discussion/github issues. There are TLP projects that are > > > already doing this, i.e. Apache Kafka. > > > > > > Do note that if agreed upon, it's not possible to make the account > > > completely public since an existing ASF slack user needs to invite a > > person > > > to join (see https://infra.apache.org/slack.html), such instructions > > would > > > be documented in the relevant places. > > > > > > -- > > > > > > 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] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > -- Regards, Seeta Ramayya Vadali
