My clear expectations for a communication strategy has 3 tiers:
- casual chatting (Slack, etc…)
- support (Stackoverflow, Discourse, …)
- bug hunting (Redmine aka forge, JIRA, …)
All those products are perfectly made for their purpose.
Consequently we can shut down any forum or mailing list and make them a static lookup archive for Mr. Google.
For support Slack for me is clearly just a “first touch point”. So basically, after asking the question the answer usually should be to create either a stackoverflow question or a forge entry.
There might be only one tough point which would speak against externals services and thats the moment where those are replaced by a newer service. What happens to the TYPO3 knowledge in there?
This would indeed be a strong point for the self-hosted Discourse service instead of using Stackoverflow.
Since I do not expect Slack to be replaced with any other causal chat solution in the near future, I count that one as set. Bug tracking in Redmine works sufficiently well, so that one’s set too.
The remaining question therefore: Discourse vs Stackoverflow.
My personal tendency would indeed go into the Discourse direction as for me the chances to eventually get a dedicated stackoverflow channel for TYPO3 seem to diminish day by day due to several reasons.