I enthusiastically agree - this site runs so well, I often don't give it any thought. But that would be a grave disservice to those who maintain and develop perlmonks. They all have my thanks.

With regard to your particular itch, perhaps it would be useful to set up a development version of the perlmonks system, so as to be able to vet experimental patches before they get applied to the stable version. The dev version need to be open to the public, to prevent security disasters. But having some trusted members play around with patches would be helpful in firming up opinions on the quality and usefulness of the patches.

Another idea would be to create a test suite that the perlmonks code would need to pass before going public. Passing a test suite would help build confidence that a patch would not pessimize some aspect of the functionality.