[perl #37115] [TODO] document Parrot's requirements

# New Ticket Created by  Joshua Hoblitt 
# Please include the string:  [perl #37115]
# in the subject line of all future correspondence about this issue. 
# <URL: https://rt.perl.org/rt3/Ticket/Display.html?id=37115 >


Parrot's top level requirements and perhaps it's 1st-order derived
requirements need to be documented.  Project goals could also be listed
in the same document but should be clearly differentiated from
requirements.

The top level requirements are likely a very short list.  Along the
lines of:

    * Support 100% of Perl6's features

Other possible items are:

    * Support Perl5's top end
    * Targetable by other languages
    * Loading of compiled bytecode
    * [Easily] Embedded
    * Outperforms VM x
    * Compact memory footprint
    * Portable to platforms x,y,z
    .
    .

I can probably come up with at least dozen more items.  Some of the
items in my example 'possible' list need careful consideration.  For
example, is it really a requirement to be targetable by other languages
or is that just a goal?

Such a document probably won't be very useful for anyone already hacking
on Parrot, as they should already know the 'big plan', but it would make
sure everyone is on the same page.  The real value is in answering the
question, "What are they trying to accomplish?", for someone interested
in getting in involved with the project.

• [perl #37115] [TODO] document Parrot's requirements by Joshua Hoblitt