Earlier quoted context omitted.
Absolutely, yes. A growing community needs healthy management in order to avoid reputational damage to the core language. There's no shortage of guidance to "stay away from X tech because the community is toxic and non-serious"
In my experience the people who, when asked about the technical merits of X, immediately dive into value judgements of a “community” around it are best ignored. If these types of people are in leadership positions, it’s too late and you need to move. If they’re below you, then you need to limit their reach and upward mobility. Usually fair application of performance standards will flush them out anyways. Often people…
The community does play a role in the ecosystem you’re buying into. You will most likely need to send PR’s / bug reports in at some point. If the core team tends to ignore bugs/external contributions, it is a point to consider.
Furthermore, if your first knee-jerk reaction to the behaviour you think undesirable in reports is to “limit their reach and upward mobility” I think you need to think seriously about what mentorship means.