Sustainable process for community support

I'm starting to understand that this repository is about process, how we encourage or steer desired behaviors that result in community success. One thing I noticed yesterday (my time) was that no one answered questions on the collector slack. I pinged my colleagues and of course folks pitched in, but I got the impression that while we raise issues about how to not confuse users, how to define vocabulary etc, maybe we haven't focused on the critical support aspect?

Close this out if I just missed something, but I suspect there's a way of incentivizing community support in ways that show up very loudly as much as or even more than things like PR stats or comment counts in devstats. In my history of OSS, slack support is a very large part of community success and I'd love to see folks who do well on this, either individually, as friends or even as companies become better incentivised and recognized for this.

Start by reviewing support activity in the collector Slack and how devstats currently recognizes PRs and comment counts. Define a sustainable support-incentive and recognition process, with a clear way to evaluate whether community support is being acknowledged.