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:

• Post the idea on Perlmonks and illicit feedback.
• Ask PerlMonks Gods to comment
• Process responses
• Reformulate concept and create go/no-go criteria
• If concept is a go formulate team (board of directors, system architect, developers, testers, documenters)
• Publish roadmap and release schedule
• Build system prototype
• Beta release prototype
• Process user reviews/bug fixes
• Beta release
• Rinse and repeat

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.