"Plus ça change, plus c'est la même chose"
-- Jean-Baptiste Alphonse Karr

As a member of pmdev, you certainly have the privileges (and the trust) to contribute whatever code you think would help improve the Monastic experience.

Having said that, I'm not entirely sure it's wise to draw a curtain over the accomplishments of those who established the foundations of something that has persisted (relatively unscathed) for longer than many tech careers.

I would suggest that the history (and the library of existing posts) is part of the site's value. (By way of example, perhaps it's worth pointing out that my first post in a dozen years linked to a previously-posted answer.)

I would further suggest that the open culture of (general) encouragement and support for studious effort exists, in great part, because effort of the current Saints.

Perhaps an alternate approach is worth considering. Have you considered something along the lines of a new "Selected Saints in Our Book"? If you model it after Selected Best Nodes, you would be thematically consistent with that feature and could end up striking a fair balance between encouraging new blood while honoring the legacy of those who laid the foundations.

I realize this is (kinda sorta) what you were alluding to, but I thing it's worth spelling out a little more clearly.

I dislike the idea of reworking the vote count/tally/impact calculation, partly because we have (had?) a strong tradition of not rewriting our history. Limiting the roll to a set number of years seems like not respecting our history.

That's my take. Other mileage may vary.

--f

P.S. As I'm sure you're aware, this sort of conversation isn't new. "Omnia illa et ante fiebant omnia illa et rursus fient."

In reply to Re: Saints in our year book / Selected best recent nodes by footpad
in thread Saints in our year book / Selected best recent nodes by LanX

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.