Yes, it's more about providing the opportunity for people to get involved than people actually getting involved. You facilitate that by working in the open. Tag relevant people to your tickets and PRs, maybe drop a line in a slack channel, and if nobody starts arguing otherwise, you merge without having to call meetings or involving the entire team. IMHO communication and overhead needs to be proportional to the impact of the change.
For bigger teams having separate people doing the merges promotes a culture of reviews. This is exactly how OSS communities function; you don't get to merge your own PRs. Which means you need to communicate effectively to get your work in.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.