I have some semi-hard sell stuff I put together that you (or anyone else) is welcome to have--send me mail and I'll dig it out. (At some point I'll put it on the web, after I find that sack of tuits that I lost a while back...) I'm also happy to call up anyone you've got that's interested and needs more info or some convincing. Mail me phone numbers and names for that. (dan@sidhe.org)

I'll see about getting a more formal statement together, rather than just referring to my use.perl journal, and get a node posted on it. Probably July 3rd, which'd be tomorrow. (At least for me now)

If it helps, there's potential for quid pro quo to some extent (links and pages on the YAS site, discounted training and consulting work, as well as speaking engagements) for companies that donate. Details depend on the amount donated and the folks you want.

FWIW, my grant can be extended, but it's third in order of importance, after the grant writer and Larry, which is as it should be. (If you or your company really feels strongly about Parrot over Perl 6, talk to the folks at the perl foundation. Or, heck, me directly, though I'm not personally tax-deductible :)

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.