* FOR DEVELOPERS: To change duplication of effort into cooperation.
* FOR USERS: To quickly locate existing software which can be reused.
Both are addressed, and very effectively, by search.cpan.org.
The one bit of value that I see in this process is where Graham looks at submissions that people have sent in and, if something seems like it's duplicate effort, tries to redirect the author to reduce the duplication. (http://www.nntp.perl.org/group/perl.modules/34207) Unfortunately, that requires the author to submit a proposal for inclusion, and since fewer than half of the authors submit the modules, it's hardly a complete filter.
I welcome your thoughts. How can we capture the good part of the module list (the human filtering), and remove the obsoleted infrastructure?