Again, that's another great question which should be posted to the blog. We'd really like that to be a centralized point for TPF communication so folks can have their "one stop shopping", if you will.

As for Parrot and Pugs, there is no competition. Though related, they're actually in different problem spaces. Further, the Perl 6 design team has been quite grateful for the work Pugs has done to clarify many corner cases which previously had not been considered. However, I haven't paid very close attention to Pugs/Parrot interaction (I've had to be more focused on Parrot) so even though I'm aware there's been some communication there, I don't to what extent.

And no, to the best of my knowledge, TPF is not funding any Pugs development though we've sponsored "Hackathons" for it. I believe we did this for Toronto and it's possible this will also happen for an Israeli Pugs hackathon, but details on the latter are still being worked out. However, those sponsorships are not handled by the grant committee (I turned them over to Jim Brandt, the conference committee head), so I don't know too much about what's involved there.

Cheers,
Ovid

New address of my CGI Course.

In reply to Re^2: TPF and Pugs by Ovid
in thread The Perl Foundation Wants to Hear From You by Ovid

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.