are you at least willing to cede a growing amount of power to others

I've actively worked to do that for years. Even more important to me is working to address aspects of contributing that greatly contribute to volunteer churn here. Appointments to positions of power have been increasingly designed to promote sustainable delegation rather than continuing the parade of churn and replacement (to varying degrees of success).

I keep hoping to get to trying to address much of that directly myself, but I'm still climbing out of 1.5 years of issues that have significantly impacted my effectiveness on volunteer projects (and more time before that which restricted the complexity of projects I could volunteer for).

That extra 30 seconds is all that's required.

There are sure a lot of people who have very low estimates for me about how long it should take me to come up with a sufficient level of eloquence. It indeed would only take 30 seconds of typing. But that isn't the time-consuming (nor tiring) part of the process. Having actually many times added verbiage with a particular goal while only taking a very short time to do it, I find that it very often is beyond not-helpful and can have quite the opposite of the desired effect. So, thanks for the suggestion (sincerely), but I believe that it is neither as easy nor as effective as you believe (in my case).

"I don't have the rest of your answers at my fingertips, but poke me a in a few days if no one has expanded on this to see what I can pull up."

Somehow I don't find it likely that adding "If nobody contributes, don't worry, I'm sure I'll come up with the answers" would actually encourage somebody else to go looking for them. (:

- tye        


In reply to Re^5: Message Inbox: Retain Deleted messages longer (power) by tye
in thread Message Inbox: Retain Deleted messages longer by jdporter

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.