Wow. This is an extremely long Note, but I'd like to make a probably-too-general reply, if I may. I agree with many of the problems of CPAN you pointed out, though I'm not entirely sure your major premise (that CPAN needs coordinated, overarching design) is necessarily inferred by those problems. Perhaps some gentle nudging by well-respected members of the Perl community would suffice. Or perhaps all it needs is a small amount of hacking on the Perl community itself. I'm not convinced that the anarchy-like Open Source method of development (which, to me, CPAN is a perfect example of, and ESR likes to call a Bazaar) doesn't have an answer to the problems you cited. In any case, I doubt there's going to be any strong policy put in place on CPAN -- that could be considered overarching design -- anyway. :)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||