Radu, could you expand what you mean with: "...
but is there something wrong with mattermost, which I'm seeing that some projects have already adopted, for example https://www.eclipse.org/che/community/ "
Emily, I disagree with your statement on light usage of Slack for Jakarta. If with this Slack, they point is to trigger CALL-2- ACTION and being ok to be contacted privately to get stuff done, they how is that beneficial to the project and what it actually means to be scalable and enable others to become DOERS without barriers of communication debt?
For everyone, lets watch with care our discipline and ownership of the OSS tools we might choose to adopt. Just because something is meant to be tried it doesn't mean that it is meant to be protected if it is proven terrible for the project's goal. Sometimes, we fear to move on and cut debt, thats a choice but it is a human choice.
None can dictate how Jakartees will come together and find the most fantastic way to be inclusive and patient while cooperating. Not EF, not a single one of us. Our actions will provide the best feedback b/c each single time, actions lead to results. Value will be seen with tracind adding to. I am always a proponent of fluid process and rustless adjustments in OSS> I have and bare no loyalty to tooling or processes that do not work to braid healthy ecosystems.