Right - to get those issues fixed and PR’s dealt with, we need the community to step in and help. I’m sure Mitar will welcome any help. I was just saying that I don’t think we need to find someone else to take point, unless of course Mitar thinks we should. Anyone can step in and help at any point, and if someone is dedicated enough to get 1 or 2 PR’s merged (and shows a willingness to help triage issues and generally move the project forward), we’ll give them commit access.
Regarding having someone on the payroll maintain Blaze, that would be awesome! But at the same time it would also be awesome to have someone on the payroll maintaining an official Vue integration, Svelte integration, update the Angular integration, etc. As great as this would all be, MDG’s team is small, and is focused in other areas right now. The good news is that view layer integrations can almost entirely be designed, built and maintained outside of core, and wired in to work well with Meteor.
Stepping back and thinking about this a bit - many people are still using Blaze successfully in production, including large companies. Some of those companies have large budgets, and are active open source contributors across many projects. The thing is that even though they could afford the time and resources to help contribute back to Blaze, and help take it to a new level, they don’t. This isn’t because they don’t believe in contributing back to the community, it’s because they honestly don’t see the need. Blaze is doing exactly what it’s supposed to do - help them successfully meet their business requirements and deliver awesome products. Honestly, I think this speaks volumes about the ingenuity and amazing forethought that went into Blaze’s design/development.
But again - if anyone is interested in taking Blaze to a new place, please just raise your 
and dive head first into the repo.