But it's worrysome that a project almost comes to a halt if a single person, for whatever reason, is suddenly unavailable. That's not a sign a project is anywhere near the state of "mature". If I were an IT manager of a company that may consider switching to Perl6 at some time in the future, I'd take notice.
Sigh. Before I go on, I must acknowledge frustration.
On what basis are you saying that Rakudo development has almost come to a halt?
Let's ignore all the work on the overall ecology, like changes to the test suite (lots of that). the spec, the nice work on pod, panda, etc. Let's forget Parrot even though they have stated that their work is driven by Rakudo's needs. Let's forget branches not yet merged back in, even though it's recognised that there are more branches waiting to land than usual.
In the less than 4 months since Patrick paused, there have been something like 1,000 commits to rakudo/rakudo and perl6/nqp (the main parts of the Rakudo compiler).