I'd take this as a moment to celebrate a guy who's done a lot of great work without having his name bathed in limelight. Not a prompt to wring hands about succe

I'd take this as a moment to celebrate a guy who's done a lot of great work without having his name bathed in limelight. Not a prompt to wring hands about succession or security bobbles in other people's projects. I don't think it's somehow also Philip's burden to find or vet or train a successor. The code is out there. His license terms are unobjectionable. If and when Philip stops work, let someone else who cares pick it up. Perhaps under new and different names. The links between the names Philip chose and Philip himself as the person behind the work will have been broken, anyway. Follow-on forks won't take away from Philip's legacy one bit. They might even help raise attention that new groups or individuals worthy of gratitude have stepped up.