"...I'll be looking forward to an actual plan to implement this..."

Feasibility studies come before plans unless you like rewriting plans a lot. First I need to know if it can be done and if it meets projected needs. For instance, maybe there's a technical reason why it simply could not be done at this site and with this site's engine. I can help write a comprehensive plan but I need the warm bodies, attention spans, and midnight oil generation desire to make something like this happen and work.

Since you bring up the idea, what are you going to do to implement this?

That's a fair question. Here's what I'm planning:

Update: Regarding TPF's spending habits...I think the solution here is to use targeted micropayments for specific TPF proposals rather than simply hand TPF money if they are not doing a very good job with it. I suppose that should be the subject of a different thread entirely. What I do know is that with money you can hire developers to solve problems and build systems in Perl that will be publicly released and free for everyone to use if they can afford to do so. Doing so means taking time away from other, more profitable, activities so funds can offset these losses and make developing enhancements for Perl an easier pill to swallow.

Celebrate Intellectual Diversity

In reply to Re^2: Perl(Monks) University by InfiniteSilence
in thread Perl(Monks) University by InfiniteSilence

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.