It'd be even better if CPAN even allowed a "default trust" model ...

I suspect that that would require long and wide-ranging discussions amongst CPAN authors; would probably require the implementation and validation of various checks and balances; and could conceivably have knock-on affects upon corporate views and policies with regard to CPAN. Five years from now you might finally reach a majority consensus, and all that would be left to do is argue about who is going to implement it; and who is going to fund that implementation.

On the other hand, the timeouts could probably be implemented by one person over a weekend and -- as it only requires authors to log in once every six months; or respond to an email once every six months -- should be sufficiently uncontroversial that it wouldn't raise objections.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?

In reply to Re^4: Howto abandon rights to a cpan module and stop getting bug reports for it? (There's the easy way or ...) by BrowserUk
in thread Howto abandon rights to a cpan module and stop getting bug reports for it? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.