I'd like to propose introducing some form of common communication channel for anything related to php-rdkafka extension, enqueue kafka transport, and this adapter - by reusing existing slack/gitter channel or creating a new one - and adding it to all related repositories to help with answering cross-repository, general phprdkafka questions, and coordinating new features.
My reasoning for this is that we need some form of cross-repository cooperation between enqueue-dev and this transport adapter at the very least.
What channels currently exist:
Enqueue-dev has a Gitter channel that can be used for discussion, but it is often about other enqueue extensions (see ).
At the same time, there exists a Gitter channel for php-rdkafka, but it's not used often ().
I'd like to propose introducing some form of common communication channel for anything related to php-rdkafka extension, enqueue kafka transport, and this adapter - by reusing existing slack/gitter channel or creating a new one - and adding it to all related repositories to help with answering cross-repository, general phprdkafka questions, and coordinating new features.
My reasoning for this is that we need some form of cross-repository cooperation between enqueue-dev and this transport adapter at the very least.
What channels currently exist: