Re^3: When comment turns into disaster

It does, partially. My question has to do with his absence as it seems effective immediately. How do you protect perl from special interests without a pumpking? Are all patches on hold until another pumpking is found? I can only hope P5P has enough oversight to bridge the immediate gap.

I, too, offer my thanks for his service. My concern is limited to the present.

Comment on Re^3: When comment turns into disaster

Replies are listed 'Best First'.
Re^4: When comment turns into disaster by moritz (Cardinal) on Jul 06, 2009 at 17:38 UTC
How do you protect perl from special interests without a pumpking? The number of hackers who have direct commit access to the perl source code repository is fairly limited (and limited to trust-worthy people), so the chances of abuse are rather small. And don't forget that we use a version control system, which makes it rather easy for the next pumpking to revert any potential damage. Also note that the stable 5.10.* branch still has a pumpking, so we're not entirely leader-less. I can only hope P5P has enough oversight to bridge the immediate gap. I'm sure they have. I mean the pumpking is not the only sensible core hacker ;-)	[reply]
Re^5: When comment turns into disaster by JavaFan (Canon) on Jul 06, 2009 at 17:49 UTC
Yeah, but the number of people that have both the knowledge, the time, the willingness and the stamina to be a pumpking is rather limited. I don't think I need more than one hand to count them.	[reply]