Parrot Developer Summit, May 14 2011: Summary
James E Keenan
jkeen at verizon.net
Sun May 15 15:10:49 UTC 2011
A Parrot Developer Summit (PDS) was held online in #parrotsketch
starting on Saturday, May 14, 2011 at 2100 UTC. Here is a summary;
please post corrections to this thread on parrot-dev. Full log:
http://irclog.perlgeek.de/parrotsketch/2011-05-14
I. Evaluation of progress since preceding PDS on Jan 29 2011.
A. Roadmap Goals
1. Deprecations as Data: Goal largely achieved. Next step would be to
establish a web interface to better use tools developed.
2. IMCC Isolation: Substantial progress. Degree to which IMCC pokes
into Parrot guts is far lower. Parrot does not depend on IMCC anymore.
We can run libparrot without ever initializing or using IMCC, and it's
feasible that we can build libparrot completely without IMCC. No urgent
next steps.
3. M0 Prototype: Final prototype and test suite are under development.
See https://gist.github.com/972649.
B. Other Goals and Work Done/Not Done
1. Garbage Collection: Substantial work done. GMS is now default GC
mechanism.
2. Rakudo presented data evincing showdown in Perl 6 on Parrot between
3.0 and 3.3 releases.
II. Next PDS: Weekend of Sat-Sun, July 30-31 2011; exact date/time TBD.
III. New Policies and Roadmap Goals
A. Benchmarking
Policy: The Parrot project will collaborate with HLLs to develop ways of
benchmarking the performance of the HLLs as targeted to monthly Parrot
releases and the expressed needs of those HLLs.
B. Profiling
Roadmap Goal: Parrot project will establish a team to pursue goal of
better profiling. By 3.6 we will have studied our existing profiling
tools, determined their strengths and limitations and developed a plan
for significant improvements in later supported releases. Initial team
members: whiteknight, cotto.
C. Relationship Management
Policy: The Parrot project will designate two people to serve as
managers of our relationship with Rakudo, our principal HLL client.
Rakudo will do likewise. The relationship managers should be each
project's principal contact point for resolution of problems with regard
to breakage or deterioration of performance.
More information about the parrot-dev
mailing list