Congratulations!

[Valid Atom 1.0] This is a valid Atom 1.0 feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://news.perlfoundation.org/atom.xml

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <feed xmlns="http://www.w3.org/2005/Atom">
  3.    <title>The Perl Foundation</title>
  4.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/" />
  5.    <link rel="self" type="application/atom+xml" href="http://news.perlfoundation.org/atom.xml" />
  6.    <id>tag:news.perlfoundation.org,2010-03-22://18</id>
  7.    <updated>2015-05-21T00:50:58Z</updated>
  8.    
  9.    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 4.38</generator>
  10.  
  11. <entry>
  12.    <title>Deadline Extended - Call For Grant Proposals</title>
  13.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/05/deadline-extended---call-for-g.html" />
  14.    <id>tag:news.perlfoundation.org,2015://18.3630</id>
  15.  
  16.    <published>2015-05-21T21:00:00Z</published>
  17.    <updated>2015-05-21T00:50:58Z</updated>
  18.  
  19.    <summary>Re: Call For Grant Proposals (May 2015 Round) We have not got grant proposals. We are extending the deadline until the end of May. If you need ideas, rjbs&apos;s article is still relevant apart from the Gist one. If you have any questions, let us know at tpf-grants-secretary at perl-foundation.org....</summary>
  20.    <author>
  21.        <name>Makoto Nozaki</name>
  22.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  23.    </author>
  24.    
  25.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  26.    
  27.    
  28.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  29.        <![CDATA[<p>Re: <a href="http://news.perlfoundation.org/2015/05/call-for-grant-proposals-may-2.html">Call For Grant Proposals (May 2015 Round)</a></p>
  30.  
  31. <p>We have not got grant proposals. We are extending the deadline until the end of May.</p>
  32.  
  33. <p>If you need ideas, <a href="http://rjbs.manxome.org/rubric/entry/1964">rjbs's article</a> is still relevant apart from the Gist one.</p>
  34.  
  35. <p>If you have any questions, let us know at tpf-grants-secretary at perl-foundation.org.</p>
  36. ]]>
  37.        
  38.  
  39.    </content>
  40. </entry>
  41.  
  42. <entry>
  43.    <title>Hague Grant Accepted</title>
  44.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/05/hague-grant-accepted.html" />
  45.    <id>tag:news.perlfoundation.org,2015://18.3628</id>
  46.  
  47.    <published>2015-05-20T09:43:59Z</published>
  48.    <updated>2015-05-20T09:50:13Z</updated>
  49.  
  50.    <summary>I am pleased to announce that Bart Wiegmans&apos; recent Hague Grant Application, Advancing the MoarVM JIT has been successful. I would like to thank everyone who provided feedback on this proposal....</summary>
  51.    <author>
  52.        <name>Karen Pauley</name>
  53.        <uri>http://martian.org/karen</uri>
  54.    </author>
  55.    
  56.        <category term="Perl 6 Development" scheme="http://www.sixapart.com/ns/types#category" />
  57.    
  58.    <category term="perl6haguegrant" label="perl6 hague grant" scheme="http://www.sixapart.com/ns/types#tag" />
  59.    
  60.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  61.        <![CDATA[<p>I am pleased to announce that Bart Wiegmans' recent Hague Grant Application, <a href="http://news.perlfoundation.org/2015/04/perl-6-hague-grant-application.html">Advancing the MoarVM <span class="caps">JIT</span></a> has been successful.</p>
  62.  
  63. <p>I would like to thank everyone who provided feedback on this proposal.</p>]]>
  64.        
  65.    </content>
  66. </entry>
  67.  
  68. <entry>
  69.    <title>Maintaining the Perl 5 Core: Report for Month 19</title>
  70.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/05/maintaining-the-perl-5-core-re-16.html" />
  71.    <id>tag:news.perlfoundation.org,2015://18.3624</id>
  72.  
  73.    <published>2015-05-14T07:08:01Z</published>
  74.    <updated>2015-05-14T07:11:40Z</updated>
  75.  
  76.    <summary><![CDATA[Dave Mitchell writes: I spent the month mainly fixing issues that were 5.22 blockers. Summary 2:18 [perl #120950] Apparent failure to localize %^H 2:13 [perl #123619] Bleadperl v5.21.6-89-gd648ffc breaks autobox 4:33 [perl #123737] S_no_op: Assertion `s &gt;= oldbp' failed 1:25 [perl #123954] Perl_pp_substcont: Assertion failed 1:21 [perl #123976] [Win32] Unable to build 64-bit blead using gcc-4.8.2 1:21 [perl #124207] Perl_ck_stringify: Assertion `!((((kid)-&gt;op_sibling) ? 10:57 [perl #124216] Perl_sv_clear: Assertion 0:37 [perl #124368] Perl_sv_2pv_flags: Assertion .... 2:09 [perl #124385] null ptr deref...]]></summary>
  77.    <author>
  78.        <name>Karen Pauley</name>
  79.        <uri>http://martian.org/karen</uri>
  80.    </author>
  81.    
  82.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  83.    
  84.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  85.    
  86.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  87.        <![CDATA[<p><em>Dave Mitchell writes:</em></p>
  88.  
  89. <p>I spent the month mainly fixing issues that were 5.22 blockers.</p>
  90.  
  91. <p><b>Summary</b></p>
  92.  
  93. <blockquote><p>2:18 [perl #120950] Apparent failure to localize %^H<br />
  94. 2:13 [perl #123619] Bleadperl v5.21.6-89-gd648ffc breaks autobox<br />
  95. 4:33 [perl #123737] S_no_op: Assertion `s &gt;= oldbp' failed<br />
  96. 1:25 [perl #123954] Perl_pp_substcont: Assertion failed<br />
  97. 1:21 [perl #123976] [Win32] Unable to build 64-bit blead using gcc-4.8.2<br />
  98. 1:21 [perl #124207] Perl_ck_stringify: Assertion `!((((kid)-&gt;op_sibling) ?<br />
  99. 10:57 [perl #124216] Perl_sv_clear: Assertion<br />
  100. 0:37 [perl #124368] Perl_sv_2pv_flags: Assertion ....<br />
  101. 2:09 [perl #124385] null ptr deref -&gt; Perl_cv_forget_slab (pad.c:500)<br />
  102. 0:20 fix t/uni.parser.t under <span class="caps">EBCDIC</span><br />
  103. 10:02 more op_siblings stuff<br />
  104. 7:27 process p5p mailbox<br />
  105. 5:10 review 5.22 blocker issues<br />
  106. 5:34 setjmp corruption with recent clang<br />
  107. 3:36 valgrind error in re_op_compile()</p></blockquote>
  108.  
  109. <p><b>59:03 Total (HH::MM)</b></p>]]>
  110.        <![CDATA[<p>As of 2015/04/30: since the beginning of the grant:</p>
  111.  
  112. <blockquote><p>80.6 weeks<br />
  113. 1071.5 total hours<br />
  114. 13.3 average hours per week</p></blockquote>
  115.  
  116. <p>There are 128 hours left on the grant</p>]]>
  117.    </content>
  118. </entry>
  119.  
  120. <entry>
  121.    <title>Maintaining Perl 5: Grant Report for March 2015</title>
  122.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/05/maintaining-perl-5-grant-repor-16.html" />
  123.    <id>tag:news.perlfoundation.org,2015://18.3622</id>
  124.  
  125.    <published>2015-05-13T09:58:16Z</published>
  126.    <updated>2015-05-13T10:42:53Z</updated>
  127.  
  128.    <summary>Tony Cook writes: Approximately 25 tickets were reviewed or worked on, and 2 patches were applied. This was a short month since my old grant ran out, and a new grant started. [perl #123788] was interesting to me because is illustrated how perl tracks which globs (or package) a given @ISA is present in - and how that was broken in this case. Each @ISA has isa magic. If the @ISA is only present in a single GV, then mg_obj...</summary>
  129.    <author>
  130.        <name>Karen Pauley</name>
  131.        <uri>http://martian.org/karen</uri>
  132.    </author>
  133.    
  134.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  135.    
  136.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  137.    
  138.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  139.        <![CDATA[<p><em>Tony Cook writes:</em></p>
  140.  
  141. <p>Approximately 25 tickets were reviewed or worked on, and 2 patches were applied.</p>
  142.  
  143. <p>This was a short month since my old grant ran out, and a new grant started.</p>
  144.  
  145. <p>[perl #123788] was interesting to me because is illustrated how perl tracks which globs (or package) a given @ISA is present in - and how that was broken in this case.</p>
  146.  
  147. <p>Each @ISA has isa magic.  If the @ISA is only present in a single <span class="caps">GV, </span>then mg_obj for the magic is a pointer to that <span class="caps">GV, </span>if there are multiple GVs then mg_obj is an AV (not an RV pointing to an AV) of GVs.  In neither case are the references counted in the <span class="caps">GV'</span>s reference count.</p>
  148.  
  149. <p>In the case of the bug, the magic wasn't being updated when the @ISA was removed from the <span class="caps">GV, </span>and the GV was then deleted, leaving a dangling pointer in the mg_obj of the @ISA's isa magic.  Later when the SV head of the GV was re-used for a PV SV and the original @ISA was modified perl would crash attempting to use it as a <span class="caps">GV.</span></p>]]>
  150.        <![CDATA[<table><tr><td>Hours</td><td>Activity</td></tr><tr><td>0.18</td><td>#119125 review</td></tr><tr><td>0.12</td><td>#119533 comment and close</td></tr><tr><td>2.64</td><td>#122136 test each dist, produce tickets/patches for</td></tr><tr><td></td><td>unfixed dists and comment</td></tr><tr><td></td><td>#122136 follow-up, comment</td></tr><tr><td>3.30</td><td>#123145 work out a fix</td></tr><tr><td></td><td>#123145 tests, make a patch and comment</td></tr><tr><td>0.67</td><td>#123475 research and comment</td></tr><tr><td>0.25</td><td>#123528 review, find it was already committed and close</td></tr><tr><td>6.92</td><td>#123788 review discussion, review code</td></tr><tr><td></td><td>#123788 debugging</td></tr><tr><td></td><td>#123788 produce a patch and comment</td></tr><tr><td></td><td>#123788 write tests and comment with new patches</td></tr><tr><td>0.93</td><td>#123947 diagnose and fix</td></tr><tr><td>0.68</td><td>#123958 review, research and comment</td></tr><tr><td>3.03</td><td>#123971 try to understand why generated code is producing</td></tr><tr><td></td><td>rubbish, try to produce a simple reproducer, comment</td></tr><tr><td></td><td>#123971 try to fix long double packing on gcc 5</td></tr><tr><td>3.91</td><td>#123976 try to debug</td></tr><tr><td></td><td>#123976 debugging</td></tr><tr><td>0.32</td><td>#123977 review</td></tr><tr><td>4.14</td><td>#123981 research, testing</td></tr><tr><td></td><td>#123981 more testing and adjustments, comment with patch</td></tr><tr><td></td><td>#123981 review and comment</td></tr><tr><td>0.33</td><td>#124062 review and comment</td></tr><tr><td>0.55</td><td>#124064 review and comment</td></tr><tr><td>0.20</td><td>#124065 try to reproduce, diagnose and comment, closing ticket</td></tr><tr><td>1.07</td><td>#124069/#124068 review, testing, research and comment</td></tr><tr><td>0.22</td><td>#124081 review, test, push to blead</td></tr><tr><td>0.28</td><td>#124131 review and apply to post-5.22 branch</td></tr><tr><td>0.53</td><td>#124181 try to reproduce and comment</td></tr><tr><td>0.07</td><td>#124188 review and apply to post 5.22 branch</td></tr><tr><td>0.22</td><td>#124189 review and comment</td></tr><tr><td>0.07</td><td>#124202 review and comment</td></tr><tr><td>0.61</td><td>Review 5.22 blockers</td></tr><tr><td></td><td>Review 5.22 blockers</td></tr><tr><td>1.53</td><td>review OP_SIGNATURE thread and comment</td></tr></table>
  151.  
  152. <p><b>32.77 hours total</b></p>]]>
  153.    </content>
  154. </entry>
  155.  
  156. <entry>
  157.    <title>Call For Grant Proposals (May 2015 Round)</title>
  158.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/05/call-for-grant-proposals-may-2.html" />
  159.    <id>tag:news.perlfoundation.org,2015://18.3618</id>
  160.  
  161.    <published>2015-05-02T22:01:01Z</published>
  162.    <updated>2015-05-06T02:00:12Z</updated>
  163.  
  164.    <summary>Contribute to Perl and get some $$! The Grants Committee is accepting grant proposals all the time. We evaluate them every two months and another evaluation period has come. If you have an idea for doing some Perl work that will benefit the Perl community, consider sending a grant application. The application deadline for this round is 23:59 May 15th UTC. We will publish the received applications, get community feedback and conclude acceptance by May 30th. The format will be...</summary>
  165.    <author>
  166.        <name>Makoto Nozaki</name>
  167.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  168.    </author>
  169.    
  170.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  171.    
  172.    
  173.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  174.        <![CDATA[<p>Contribute to Perl and get some $$!</p>
  175.  
  176. <p>The Grants Committee is accepting grant proposals all the time.  We evaluate them every two months and another evaluation period has come.</p>
  177.  
  178. <p>If you have an idea for doing some Perl work that will benefit the Perl community, consider sending a grant application. <strong>The application deadline for this round is 23:59 May 15th UTC.</strong> We will publish the received applications, get community feedback and conclude acceptance by May 30th.</p>
  179.  
  180. <p>The format will be the same as the previous rounds in 2014-2015.</p>
  181.  
  182. <p>To apply, please read <a href="http://www.perlfoundation.org/how_to_write_a_proposal">How to Write a Proposal</a>.  <a href="http://www.perlfoundation.org/rules_of_operation">Rules of Operation</a>
  183. will also help you understand how the grant process works.</p>
  184.  
  185. <p>We will confirm the receipt of application within 24 hours.</p>
  186.  
  187. <p>If you have further questions, please comment here.  If your comment
  188. does not show up here within 24 hours, the chances are that the spam
  189. filter did something bad. Get in touch with me at tpf-grants-secretary
  190. at perl-foundation.org.</p>
  191. ]]>
  192.        
  193.  
  194.    </content>
  195. </entry>
  196.  
  197. <entry>
  198.    <title>Perl 6 Core Development Grant Accepted</title>
  199.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/05/perl-6-development-grant-succe.html" />
  200.    <id>tag:news.perlfoundation.org,2015://18.3620</id>
  201.  
  202.    <published>2015-05-02T07:58:13Z</published>
  203.    <updated>2015-05-06T15:08:12Z</updated>
  204.  
  205.    <summary>I am happy to announce that Jonathan Worthington&apos;s grant proposal, Perl 6 Release Goals, has been accepted. This is the first grant awarded under the new Perl 6 Core Development Fund. Thanks goes to the community members who took time to provide feedback on this proposal. I would also like to thank Patrick Michaud and Liz Mattijsen who have agreed to help with the management of this grant....</summary>
  206.    <author>
  207.        <name>Karen Pauley</name>
  208.        <uri>http://martian.org/karen</uri>
  209.    </author>
  210.    
  211.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  212.    
  213.    <category term="perl6developmentfund" label="perl 6 development fund" scheme="http://www.sixapart.com/ns/types#tag" />
  214.    
  215.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  216.        <![CDATA[<p>I am happy to announce that Jonathan Worthington's grant proposal, <a href="http://news.perlfoundation.org/2015/04/grant-proposal-perl-6-release.html">Perl 6 Release Goals</a>, has been accepted.  This is the first grant awarded under the new <a href="http://www.perlfoundation.org/perl_6_core_development_fund">Perl 6 Core Development Fund</a>.</p>
  217.  
  218. <p>Thanks goes to the community members who took time to provide feedback on this proposal.  I would also like to thank Patrick Michaud and Liz Mattijsen who have agreed to help with the management of this grant.</p>]]>
  219.        
  220.    </content>
  221. </entry>
  222.  
  223. <entry>
  224.    <title>ZipRecruiter Supports The Perl Foundation and YAPC::NA as a Silver Sponsor</title>
  225.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/04/ziprecruiter-supports-the-perl.html" />
  226.    <id>tag:news.perlfoundation.org,2015://18.3616</id>
  227.  
  228.    <published>2015-04-29T12:34:58Z</published>
  229.    <updated>2015-04-29T12:35:59Z</updated>
  230.  
  231.    <summary>Earlier this month The Perl Foundation&apos;s Board Treasurer Dan Wright announced that ZipRecruiter (@ZipRecruiter) has joined to support TPF and YAPC::NA as a Silver Sponsor. Not only will their sponsorship assist with YAPC::NA::2015 in Salt Lake City, but they will be supporting the efforts of The Perl Foundation year-round.</summary>
  232.    <author>
  233.        <name>TPF Conferences Staff</name>
  234.        
  235.    </author>
  236.    
  237.        <category term="Conferences" scheme="http://www.sixapart.com/ns/types#category" />
  238.    
  239.        <category term="Marketing" scheme="http://www.sixapart.com/ns/types#category" />
  240.    
  241.        <category term="Perl Foundation" scheme="http://www.sixapart.com/ns/types#category" />
  242.    
  243.    
  244.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  245.        <![CDATA[<p>Earlier this month The Perl Foundation's Board Treasurer Dan Wright announced that ZipRecruiter (@ZipRecruiter) has joined to support <span class="caps">TPF </span>and <span class="caps">YAPC</span>::NA as a Silver Sponsor. Not only will their sponsorship assist with <span class="caps">YAPC</span>::NA::2015 in Salt Lake City, but they will be supporting the efforts of The Perl Foundation year-round.</p>
  246.  
  247. <p>"ZipRecruiter has used perl from our company's inception, and we've benefitted greatly from the language, <span class="caps">CPAN </span>and the perl community," said Will Redd, Co-Founder at ZipRecruiter. </p>
  248.  
  249. <p>ZipRecruiter's web-based platform streamlines the hiring process by enabling companies to post a job to 100+ job boards with 1 click and to manage all applicants through a simple online interface. By providing a central location for finding, screening and tracking applicants, ZipRecruiter helps employers make the best hiring decisions quickly and at a fraction of the cost of traditional job boards.</p>
  250.  
  251. <p>By supporting The Perl Foundation year-round, ZipRecruiter's sponsorship will not only be applied to <span class="caps">TPF </span>conferences, but also to the development of Perl, training of new Perl programmers, and other <span class="caps">TPF </span>initiatives. "Perl has been an important factor in our success, and we're happy to be able to give back to the community.  We're also sponsoring <span class="caps">TPF </span>to help get the word out to Perl programmers that there's another company that's doing significant new software development projects using perl," added Redd. </p>
  252.  
  253. <p>To learn more about ZipRecruiter visit www.ziprecruiter.com or follow them on Twitter @ZipRecruiter. Would you like to be a Perl Foundation or <span class="caps">YAPC</span>::NA sponsor? More information can be found at http://www.yapcna.org/yn2015/sponsors.html#become-sponsor</p>]]>
  254.        
  255.    </content>
  256. </entry>
  257.  
  258. <entry>
  259.    <title>Perl::Lint Significant Improvements</title>
  260.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/04/perllint-significant-improveme.html" />
  261.    <id>tag:news.perlfoundation.org,2015://18.3612</id>
  262.  
  263.    <published>2015-04-28T18:25:49Z</published>
  264.    <updated>2015-05-06T14:30:06Z</updated>
  265.  
  266.    <summary>It&apos;s a while since our last report on Perl::Lint, but Taiki has made considerable progress since then, releasing 3 new versions of this Perl source code analyser. Perl::Lint doesn&apos;t yet support everything described in Taiki&apos;s original proposal for this TPF grant as it needs a few small improvements to match Perl::Critic. Despite this, Taiki has written a fast alternative to Perl::Critic that&apos;s easy to use, well documented and now has an associated test module. I would like to suggest to...</summary>
  267.    <author>
  268.        <name>Tom Hukins</name>
  269.        
  270.    </author>
  271.    
  272.    
  273.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  274.        <![CDATA[<p>It's a while since our <a href="http://news.perlfoundation.org/2015/02/perllint-bug-fixes-and-new-pol.html">last report on Perl::Lint</a>, but Taiki has made considerable progress since then, releasing 3 new versions of this Perl source code analyser.</p>
  275.  
  276. <p>Perl::Lint doesn't yet support everything described in <a href="http://news.perlfoundation.org/2014/03/grant-proposal-perllint---yet.html">Taiki's original proposal for this TPF grant</a> as it needs <a href="https://github.com/moznion/Perl-Lint/issues/69">a few small improvements</a> to match Perl::Critic.</p>
  277.  
  278. <p>Despite this, Taiki has written <a href="https://metacpan.org/pod/Perl::Lint#PERFORMANCE">a fast alternative to Perl::Critic</a> that's easy to use, well documented and now has <a href="https://metacpan.org/pod/Test::Perl::Lint">an associated test module</a>.</p>
  279.  
  280. <p>I would like to suggest to The Perl Foundation's Grants Committee that we treat this grant as a success.  Please leave a comment on this post if you support or oppose this.</p>
  281.  
  282. <p>Finally, I would like to thank everyone who has experimented with Perl::Lint so far, particularly those who have raised reports of problems they encountered, and most of all Taiki for fixing these problems along with the rest of his good work.</p>
  283. ]]>
  284.        
  285.    </content>
  286. </entry>
  287.  
  288. <entry>
  289.    <title>Maintaining the Perl 5 Core: Report, Months 17, &amp; 18</title>
  290.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/04/maintaining-the-perl-5-core-re-15.html" />
  291.    <id>tag:news.perlfoundation.org,2015://18.3610</id>
  292.  
  293.    <published>2015-04-27T00:53:10Z</published>
  294.    <updated>2015-04-27T00:59:30Z</updated>
  295.  
  296.    <summary>Dave Mitchell writes: I spent the month mainly fixing issues reported by the Coverity static code analyser, and fixing assorted bugs that were in the main 5.22 blockers. Some notable highlights: Coverity reported an issue related to MEM_WRAP_CHECK(): although it turned out to be harmless, looking at it gave me an idea to make the wrap check be constant-folded at compile time more often, and since this macro (via its use in Newx(), Copy() etc) is used in many places...</summary>
  297.    <author>
  298.        <name>Karen Pauley</name>
  299.        <uri>http://martian.org/karen</uri>
  300.    </author>
  301.    
  302.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  303.    
  304.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  305.    
  306.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  307.        <![CDATA[<p><em>Dave Mitchell writes:</em></p>
  308.  
  309. <p>I spent the month mainly fixing issues reported by the Coverity static code analyser, and fixing assorted bugs that were in the main 5.22 blockers.</p>
  310.  
  311. <p>Some notable highlights:</p>
  312.  
  313. <p>Coverity reported an issue related to <span class="caps">MEM</span>_WRAP_CHECK(): although it turned out to be harmless, looking at it gave me an idea to make the wrap check be constant-folded at compile time more often, and since this macro (via its use in Newx(), Copy() etc) is used in many places in the source, this meant that the run-time check was eliminated in many places. Indeed the object code shrank by about 8K on my x86_63 build, implying that this happened often.</p>]]>
  314.        <![CDATA[<p>RT #123743 concerned regexes going quadratic that start with /.*/ . These are special-cased to avoid quadratic-ness, but it turns out that when the pattern is intuitable (has a fixed or floating constant substring for quick rejection or determination of earliest possible start position), the intuit interfered with the special-casing, causing the pattern to go quadratic. An optimisation in 5.18.0, that made some //i patterns intuitable, indirectly caused a bunch of /.*.../i pattens to go quadratic too. Now fixed.</p>
  315.  
  316. <p>RT #123840 was a regression in 5.20 that could cause re_intuit_start() to go into an infinite loop for certain obscure types of pattern having a floating substring, a leading char class, an  where the string is utf8,<br />
  317. e.g.</p>
  318.  
  319. <pre><code>&quot;\x{100}a\x{80}a&quot; =~ /w\zxy?\z/i;</code></pre>
  320.  
  321. <p>RT #124109 was a regression in 5.21.x that could cause the values of $1,$2,$3 to get altered if a perl function like lc($1) called out to utf8.pm</p>
  322.  
  323. <p><b>Summary</b></p>
  324.  
  325. <blockquote><p>3:17 <span class="caps">SEGV </span>with -Dst and sort and multideref<br />
  326. 0:07 [perl #123685] Question regarding the '#!' argument passing.<br />
  327. 8:36 [perl #123743] RegEx ".*" Backtracking slow since 5.18 (maybe 5.17.?)<br />
  328. 0:56 [perl #123783] overwrite past end of string in scan_const<br />
  329. 10:05 [perl #123840] hang in re_intuit_start<br />
  330. 3:42 [perl #123860] smartmatch with %!<br />
  331. 1:37 [perl #123918] regex end of line match very slow<br />
  332. 1:11 [perl #123922] OP_MULTIDEREF leak<br />
  333. 4:09 [perl #123996] pp_repeat issue<br />
  334. 6:43 [perl #124109] panic: swash_fetch got swatch of unexpected bit width<br />
  335. 1:44 fix -Dx failing to dump top-level subs<br />
  336. 17:28 look at Coverity issues<br />
  337. 2:01 make last op_sibling point to parent<br />
  338. 3:37 more op_siblings stuff<br />
  339. 30:54 process p5p mailbox<br />
  340. 0:52 review [perl #123616] Weed out needless <span class="caps">PERL</span>_UNUSED_ARG<br />
  341. 2:21 silence compiler warnings</p></blockquote>
  342.  
  343. <p><b>99:20 Total (HH::MM)</b></p>
  344.  
  345. <p>As of 2015/03/31: since the beginning of the grant:</p>
  346.  
  347. <blockquote><p>76.7 weeks<br />
  348. 1014.0 total hours<br />
  349. 13.2 average hours per week</p></blockquote>
  350.  
  351. <p>There are 186 hours left on the grant</p>]]>
  352.    </content>
  353. </entry>
  354.  
  355. <entry>
  356.    <title>The Perl Foundation Announces DreamHost YAPC::NA Sponsorship</title>
  357.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/04/the-perl-foundation-announces.html" />
  358.    <id>tag:news.perlfoundation.org,2015://18.3608</id>
  359.  
  360.    <published>2015-04-25T18:39:10Z</published>
  361.    <updated>2015-04-27T01:05:43Z</updated>
  362.  
  363.    <summary>The Perl Foundation is pleased to announce DreamHost (dreamhost.com) as one of the newest sponsors of YAPC::NA::2015</summary>
  364.    <author>
  365.        <name>TPF Conferences Staff</name>
  366.        
  367.    </author>
  368.    
  369.        <category term="Conferences" scheme="http://www.sixapart.com/ns/types#category" />
  370.    
  371.        <category term="Perl Foundation" scheme="http://www.sixapart.com/ns/types#category" />
  372.    
  373.    
  374.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  375.        <![CDATA[<p>The Perl Foundation is pleased to announce DreamHost (dreamhost.com) as one of the newest sponsors of <span class="caps">YAPC</span>::NA::2015. DreamHost uses Perl in their custom-built control panel, for managing a big part of their server infrastructure, and for distributing calculations between machines. They also use Perl for their hosting platform, as well as a web application platform. "DreamHost is honored to be sponsoring <span class="caps">YAPC</span>::NA!  DreamHost was built upon a solid foundation of Perl back in our earliest days," said Brett Dunst, VP of Brand and Community at DreamHost. "Perl was the very best option at the time for our needs and we continue to use it heavily in 2015! The <span class="caps">CPAN </span>ecosystem allows us to get a lot done very quickly, rather than writing everything from scratch."</p>
  376.  
  377. <p>Since 1997 DreamHost has helped entrepreneurs and developers the world over bring their dreams to life on the Internet. From domain registrations to web hosting and even powerful cloud storage and computing services, more than 400,000 customers trust DreamHost to be their online home. Packed with unbelievable value, DreamHost is the best place to launch a blog, website, or web application into the stratosphere.</p>
  378.  
  379. <p>"DreamHost is a huge proponent of open source software, and <span class="caps">CPAN </span>is one of the largest collections of open source functionality that is free to use," Dunst added. "Not only that, the Perl community is extremely friendly and welcoming!"</p>
  380.  
  381. <p>Interested in learning more about DreamHost? Visit www.dreamhost.com or follow them on Twitter @dreamhost. Would you like to be a Perl Foundation or <span class="caps">YAPC</span>::NA sponsor? More information can be found at <a href="http://www.yapcna.org/yn2015/sponsors.html#become-sponsor">http://www.yapcna.org/yn2015/sponsors.html#become-sponsor</a></p>]]>
  382.        
  383.    </content>
  384. </entry>
  385.  
  386. <entry>
  387.    <title>Perl 6 Hague Grant Application</title>
  388.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/04/perl-6-hague-grant-application.html" />
  389.    <id>tag:news.perlfoundation.org,2015://18.3606</id>
  390.  
  391.    <published>2015-04-19T10:00:10Z</published>
  392.    <updated>2015-04-19T10:19:11Z</updated>
  393.  
  394.    <summary>We have received the following Hague Grant application from Bart Wiegmans. Before we vote on this proposal we would like to have a period of community consultation for 10 days. Please leave feedback in the comments or if you prefer send email with your comments to karen at perlfoundation.org. Name: Bart Wiegmans Project Title: Advancing the MoarVM JIT Synopsis: Implement an advanced code generation algorithm for the MoarVM JIT compiler, leading to more efficient machine code for JIT compiled frames....</summary>
  395.    <author>
  396.        <name>Karen Pauley</name>
  397.        <uri>http://martian.org/karen</uri>
  398.    </author>
  399.    
  400.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  401.    
  402.    <category term="perl6haguegrant" label="perl6 hague grant" scheme="http://www.sixapart.com/ns/types#tag" />
  403.    
  404.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  405.        <![CDATA[<p>We have received the following Hague Grant application from Bart Wiegmans.  Before we vote on this proposal we would like to have a period of community consultation for 10 days. Please leave feedback in the comments or if you prefer send email with your comments to karen at perlfoundation.org.</p>
  406.  
  407. <p><b>Name</b>: Bart Wiegmans</p>
  408.  
  409. <p><b>Project Title</b>:  Advancing the MoarVM <span class="caps">JIT</span></p>
  410.  
  411. <p><b>Synopsis:</b></p>
  412.  
  413. <p>Implement an advanced code generation algorithm for the MoarVM <span class="caps">JIT </span>compiler, leading to more efficient machine code for <span class="caps">JIT </span>compiled frames.</p>
  414.  
  415. <p><b>Benefits to Perl 6 Development:</b></p>
  416.  
  417. <p>This project will enable the MoarVM <span class="caps">JIT </span>compiler to generate smaller and more efficient code, producing greater performance and less memory traffic during execution. This will help to make Perl 6 more competitive with other languages. (Speed is generally regarded as a feature).</p>
  418.  
  419. <p>As a secondary benefit this will decouple the <span class="caps">JIT </span>intermediate representation from the MoarVM bytecode and the x64 machine code making it easier for developers to extend or to port the <span class="caps">JIT </span>to architectures other than x64, such as <span class="caps">ARM.</span></p>
  420.  
  421. <p>As an example of the potential speedup I've created the following example demonstrating a 5x speedup on tight numeric code. Although that example is highly artificial it does demonstrate the limits of the current <span class="caps">JIT </span>rather well.  Note also that the original hot loop uses 22 instructions whereas the new hot loop uses only 7 instructions.</p>]]>
  422.        <![CDATA[<p><b>Deliverables:</b></p>
  423.  
  424. <p>These deliverables are not ordered chronologically.</p>
  425.  
  426.  
  427.  
  428. <ol>
  429. <li>An implementation of the code generation algorithm described below, including instructio  selection tables for the x64 architecture </li>
  430. <li>A runtime representation of machine operations ('expressions') that will form the input to the code generator and is suitable for targeting to different architectures</li>
  431. <li>A patched version of DynASM capable of addressing the extended registers of x64</li>
  432. <li>Conversion of large parts of the current <span class="caps">JIT </span>to the new algorithm</li>
  433. <li>An extension <span class="caps">API </span>for <span class="caps">REPR </span>ops to insert (inline) expressions into the <span class="caps">JIT </span>in place of some operations</li>
  434. <li>A set of automated tests known to trigger <span class="caps">JIT </span>compilation to either the <span class="caps">NQP </span>or Rakudo Perl 6 test suite.</li>
  435. <li>Reports and documentation explaining the <span class="caps">JIT </span>and it's <span class="caps">API </span></li>
  436. </ol>
  437.  
  438.  
  439.  
  440.  
  441. <p><b>Project Details:</b></p>
  442.  
  443. <p>Since September 2014 MoarVM implements a <span class="caps">JIT </span>compiler for optimised frames. This <span class="caps">JIT </span>compiler has proven to be reliable after it became the default option in October 2014, but it does not generate very efficient machine code. This is because it is very simple (simplistic perhaps) and generates code by pasting together preformed blocks of machine code.</p>
  444.  
  445. <p>Because these machine code fragments are necessarily independent, they must store and load values from memory every time they execute, even if these values are never read afterwards or if they are only temporarily useful. This results in large code size and heavy memory traffic. Moreover, because each part is independent, even very simple optimizations across fragment boundaries are impossible or very hard. Thus, the potential performance increase gained by <span class="caps">JIT </span>compilation is limited by the current design.</p>
  446.  
  447. <p>In this project I propose to implement a more advanced code generation algorithm based on the paper by Aho et al, which I will not describe in detail here. What is relevant for this proposal is that I intend to embed it into the existing <span class="caps">JIT </span>compiler as an additional node type. This means that the current <span class="caps">JIT </span>compiler can be converted to use this new algorithm in small pieces. This also means that the new algorithm must be written to use the DynASM bytecode generation library. This in turn means that DynASM must be extended to support register addressing on x64 (it currently only does so on x86).</p>
  448.  
  449. <p>Although this is a large project it, it can be divided into 'inchstones' relatively cleanly, each of which can be divided further:</p>
  450.  
  451.  
  452.  
  453. <ul>
  454. <li>Implement a 'proof of concept' code generator using DynASM with limited register addressing. This is intended to find any limits to DynASM (or my understanding) beyond the register addressing limitation already discussed.</li>
  455. <li>Eliminate the register addressing limitation. In practice this comes down to conditionally adding register extension prefix bytes before the actual instructions. Last year I discussed briefly how this should be done with Mike Pall, the author of DynASM and luajit.</li>
  456. <li>Implement a machine-level expression graph data type, suitable for expressing MoarVM- evel concepts close to machine-level operations. </li>
  457. <li>Actually implement the algorithm, including components like register selection, instruction selection, and value spills.</li>
  458. <li>Convert current <span class="caps">JIT </span>compiler fragments to the new expression trees. Areas of specific interest include branching, C calls, VM routine calls, GC barriers, deoptimization and exception handlers. Each of these is a goal onto itself. The current <span class="caps">JIT </span>fragments can function as templates for the expression graph.</li>
  459. <li>Implement an extension <span class="caps">API </span>for <span class="caps">REPR'</span>s (object representations) to inline operations into <span class="caps">JIT </span>expressions.</li>
  460. </ul>
  461.  
  462.  
  463.  
  464.  
  465. <p>Automated tests will be developed during development of features and collected over time. Given enough time and less-than-expected difficulties in implementation, I have many more ambitions, but I think this should provide enough work for now.</p>
  466.  
  467. <p><b>Project Schedule:</b></p>
  468.  
  469. <p>I estimate that this project will take 10 weeks of full-time work, excluding time spent studying in preparation. Around two to three weeks will be spent on creating a proof of concept code generator and extending DynASM for x64 register addressing. If this is successful I think around 2 weeks will be spent on implementing this for MoarVM, of which one week will be spent on the algorithm and another week on instruction and register tables. After this I'll be able to demonstrate a simple <span class="caps">JIT</span>-compiled frame using the new algorithm.</p>
  470.  
  471. <p>The next three weeks will be spent converting more complex parts until a large part of the current <span class="caps">JIT </span>has been converted. Finally in the last two weeks I will implement the extension <span class="caps">API </span>as well as implement one or more of such extensions, for example inlined array access.</p>
  472.  
  473. <p>I can begin working in the week starting Sunday June 14 2015, meaning I intend to finish Saturday August 22. The halfway milestone should then be reached Saturday July 18.</p>
  474.  
  475. <p><b>Report Schedule:</b></p>
  476.  
  477. <p>I will report on my work using my blog as I have done last year during GSoC. Blog entries will appear at least every two weeks and preferably more often. This blog is syndicated on the <a href="http://pl6anet.org/">pl6anet.org</a> news aggegration site. Furthermore, I will report often to the #perl6 and #moarvm channel of freenode to discuss my progress. I'm also willing to provide mailing-list announcements (e.g. on perl6-announce) in case of milestones.</p>
  478.  
  479. <p><b>Public Repository:</b></p>
  480.  
  481. <p>The final code will be hosted in the MoarVM public git repository at github.com/MoarVM/MoarVM as well as in MoarVM's fork of DynASM. Changes to DynASM will also be offered to the luajit project from which DynASM has been extracted. Initially work will be done in a separate branch so as to not disturb 'regular' users. Any proof-of-concept code will be hosted at my personal github account.</p>
  482.  
  483. <p><b>Grant Deliverables ownership/copyright and License Information:</b></p>
  484.  
  485. <p>MoarVM is licensed under the Artistic 2.0 license. DynASM is licensed under <span class="caps">MIT.</span> Copyright on MoarVM belongs to Jonathan Worthington and others (according to the current <span class="caps">LICENSE </span>file). Copyright to DynASM belongs to Mike Pall. I have naturally no authority to change the copyright on these projects. The Perl Foundation may of course have copyright on the patches applied for this project (although I don't know if that works out legally).</p>
  486.  
  487. <p><b>Bio:</b></p>
  488.  
  489. <p>I was the author of the current MoarVM <span class="caps">JIT </span>compiler during the 2014 edition of GSoC. Thus, I know it very well. I consider myself to have been a member of the Perl 6 community since 2012, when I wrote the mod_parrot module for apache httpd during the 2012 edition of GSoC. I wrote my first interpreter around 10 years ago. </p>
  490.  
  491. <p>In real life I've been studying physics, biology, and currently environmental science. I have, in general, lots of time available in the summer. Lastly, I obsess about speed and MoarVM / Rakudo Perl 6 not being as fast as they can bothers me.</p>
  492.  
  493. <p><b>Amount Requested:</b></p>
  494.  
  495. <p>I request $10.000 for 2,5 months of work. I'd suggest payment of $5000 after the first halfway milestone and $5000 after the project is finished. </p>
  496.  
  497. <p><b>Suggestions for Grant Manager:</b></p>
  498.  
  499. <p>Jonathan Worthington (jnthn), who also mentored me during the 2014 edition of Google Summer of Code. He is the lead developer on MoarVM and a large contributor to the Rakudo Perl 6 compiler, on which he has given many talks at Perl conferences and elsewhere.</p>]]>
  500.    </content>
  501. </entry>
  502.  
  503. <entry>
  504.    <title>Grants Update - April 2015</title>
  505.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/04/grants-update---april-2015.html" />
  506.    <id>tag:news.perlfoundation.org,2015://18.3604</id>
  507.  
  508.    <published>2015-04-17T21:00:00Z</published>
  509.    <updated>2015-04-29T23:07:02Z</updated>
  510.  
  511.    <summary>For the March round, we got no applications. The next round will be in May. Grant updates: Start ACT - Voyager by Theo van Hoesel: Enjoy his report and give feedback - April 1 - Act Perl::Lint - Yet Another Static Analyzer for Perl5 by Taiki Kawakami: We got an update and the report will be posted next week. Modern Object Oriented Programming in Perl by Toby Inkster: No update from the grantee. The grant manager has been trying to...</summary>
  512.    <author>
  513.        <name>Makoto Nozaki</name>
  514.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  515.    </author>
  516.    
  517.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  518.    
  519.    
  520.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  521.        <![CDATA[<p>For the March round, we got no applications. The next round will be in May.</p>
  522.  
  523. <p>Grant updates:</p>
  524.  
  525. <ul>
  526. <li><a href="http://news.perlfoundation.org/2014/07/grant-proposal-start-act---voy.html">Start ACT - Voyager by Theo van Hoesel</a>: Enjoy his report and give feedback - <a href="http://news.perlfoundation.org/2015/04/april-1---act.html">April 1 - Act</a></li>
  527. <li><a href="http://news.perlfoundation.org/2014/03/grant-proposal-perllint---yet.html">Perl::Lint - Yet Another Static Analyzer for Perl5 by Taiki Kawakami</a>: We got an update and the report will be posted next week.</li>
  528. <li><a href="http://news.perlfoundation.org/2014/05/grant-proposal-modern-object-o.html">Modern Object Oriented Programming in Perl by Toby Inkster</a>: No update from the grantee. The grant manager has been trying to get in touch with Toby.</li>
  529. </ul>
  530. ]]>
  531.        
  532.  
  533.    </content>
  534. </entry>
  535.  
  536. <entry>
  537.    <title>Grant Proposal: Perl 6 Release Goals</title>
  538.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/04/grant-proposal-perl-6-release.html" />
  539.    <id>tag:news.perlfoundation.org,2015://18.3602</id>
  540.  
  541.    <published>2015-04-07T16:06:28Z</published>
  542.    <updated>2015-04-07T16:52:20Z</updated>
  543.  
  544.    <summary>Jonathan Worthington has submitted a grant proposal under our new Perl 6 Core Development Fund. Before we vote on this proposal we would like to get feedback and endorsements from the Perl community. Please leave feedback in the comments or send email with your comments to karen at perlfoundation.org. Name: Jonathan Worthington (jnthn) Project Title: Work towards the 2015 Perl 6 release goals Synopsis: Fund a leading Rakudo Perl 6 and MoarVM contributor to work on key implementation tasks and...</summary>
  545.    <author>
  546.        <name>Karen Pauley</name>
  547.        <uri>http://martian.org/karen</uri>
  548.    </author>
  549.    
  550.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  551.    
  552.    
  553.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  554.        <![CDATA[<p>Jonathan Worthington has submitted a grant proposal under our new <a href="http://www.perlfoundation.org/perl_6_core_development_fund">Perl 6 Core Development Fund.</a></p>
  555.  
  556. <p>Before we vote on this proposal we would like to get feedback and endorsements from the Perl community. Please leave feedback in the comments or send email with your comments to karen at perlfoundation.org.</p>
  557.  
  558. <p><b>Name</b>: Jonathan Worthington (jnthn)</p>
  559.  
  560. <p><b>Project Title:</b> Work towards the 2015 Perl 6 release goals</p>
  561.  
  562. <p><b>Synopsis:</b></p>
  563.  
  564. <p>Fund a leading Rakudo Perl 6 and MoarVM contributor to work on key implementation tasks and keep other contributors unblocked, in the period leading up to the release of the Perl 6.0 language specification along with a conforming implementation. Funding is being requested for an initial 3 month period, with a view to extending the grant provided the work done under it is successful and funds are available.</p>]]>
  565.        <![CDATA[<p><b>Benefits to Perl 6 Development:</b></p>
  566.  
  567. <p>Perl 6 development will benefit in numerous ways if I am able to spend more time on Perl 6 for the remainder of 2015. There are a number of key implementation tasks that remain to be done in order to achieve the release goals set by the Perl 6 development team for 2015. As an experienced contributor to the Perl 6 effort, I'm in a good place to rapidly deliver the work needed to complete them. Further, there are a good number of stability improvements, bug fixes, and other smaller improvements to be made. Again, having deep knowledge of the whole implementation stack, I am in a strong place to work on them. Furthermore, by taking on blockers in the way of other contributors - by answering questions or jumping in to debug issues - I can help keep others moving.</p>
  568.  
  569. <p><b>Deliverable Elements:</b></p>
  570.  
  571. <p>Much of the work in the first 3 months of this grant will center around three key areas identified by the Perl 6 development team: <span class="caps">NFG </span>strings, native/shaped arrays, and list/array performance and semantic improvements. I will deliver:</p>
  572.  
  573.  
  574.  
  575. <ul>
  576. <li>A Normal Form Grapheme strings implementation in MoarVM, along with tests in the Perl 6 spectest suite</li>
  577. <li>The remaining work needed on native arrays (including support for small int types and fixing pre-compilation issues), followed by planning, implementation work, and tests for sized/shaped arrays</li>
  578. <li>Contributions as needed towards list and array performance/semantic improvements (the majority of this work is currently the goal of another contributor)</li>
  579. </ul>
  580.  
  581.  
  582.  
  583.  
  584. <p>I will also deliver support to other contributors working on the Rakudo Perl 6 compiler and MoarVM, in order to unblock them where needed and thus enable more progress.</p>
  585.  
  586. <p>The following deliverables also fall under the scope of this grant, but are<br />
  587. a secondary focus for the initial 3 months:</p>
  588.  
  589.  
  590.  
  591. <ul>
  592. <li>Stabilizing and hardening our concurrency, parallel programming, and asynchronous programming support</li>
  593. <li>Reviewing and fixing various outstanding issues surrounding module pre-compilation</li>
  594. <li>Reducing memory footprint</li>
  595. <li>Reducing startup time</li>
  596. <li>Improving I/O performance</li>
  597. <li>Reviewing issues in the bug queue, identifying those that are likely to have notable impact on Perl 6 users, and dealing with them</li>
  598. <li>Working on, and overseeing, enhancements to the MoarVM dynamic optimizer (which performs type specialization, inlining, <span class="caps">JIT </span>compilation, and so forth)</li>
  599. </ul>
  600.  
  601.  
  602.  
  603.  
  604. <p><b>Project Details:</b></p>
  605.  
  606. <p>At <span class="caps">FOSDEM </span>in 2015, Larry Wall announced that the Perl 6 development team intend to deliver a 6.0 language specification along with an implementation meeting it by the end of 2015. The Rakudo Perl 6 compiler running on MoarVM was selected as the implementation to focus on for this goal.</p>
  607.  
  608. <p>While much is already in place, there are three key tasks remaining, along with a good amount of polishing and stability work. This grant is intended to allow me, as a key contributor to Rakudo and MoarVM, to dedicate much more time to this effort, with a focus on the three key tasks, unblocking the work of other contributors where needed, and stability/polish.</p>
  609.  
  610. <p><b>Project Schedule:</b></p>
  611.  
  612. <p>I have arranged with my employer to drop to 50% of full-time hours for the period April through December 2015, freeing me up to take funding to spend the rest of my time on the Perl 6 project. I'm ready to begin work on this grant with immediate effect. As a rough guide, in the first 3 months:</p>
  613.  
  614.  
  615.  
  616. <ul>
  617. <li>I expect to have substantial progress on <span class="caps">NFG </span>strings by late April to mid May</li>
  618. <li>I expect to have substantial progress on sized/shaped arrays by late May to mid June</li>
  619. <li>I expect to have made notable contributions to the list/array work, as needed</li>
  620. <li>I expect to have undertaken some work towards improving parallel and asynchronous feature completeness and stability</li>
  621. </ul>
  622.  
  623.  
  624.  
  625.  
  626. <p>Alongside working on these key goals I will also be working to unblock the work of others and addressing numerous smaller issues.</p>
  627.  
  628. <p><b>Bio.:</b></p>
  629.  
  630. <p>I am the architect and lead developer of MoarVM, one of the lead developers of the Rakudo Perl 6 compiler, and did the initial work porting <span class="caps">NQP </span>and Rakudo to run on the <span class="caps">JVM.</span> Between the MoarVM, <span class="caps">NQP, </span>and Rakudo repositories, I have made over 10,000 commits. I hold a degree in Computer Science from the University of Cambridge, and my academic focus was on compilers, programming language semantics, and concurrency. I also have a strong conference speaking track record. Put together, I have the background to make good design and implementation choices, experience with the projects at hand, and an ability to inform the community at conferences and workshops about what I am doing.</p>
  631.  
  632. <p><b>Endorsed by:</b> Patrick Michaud</p>
  633.  
  634. <p><b>Amount Requested:</b><br />
  635. $10,000 - $40 <span class="caps">USD </span>/ hour, working around 50% of full time</p>
  636.  
  637. <p><b>Suggestions for Grant Manager:</b><br />
  638. Elizabeth Mattijsen or Patrick Michaud</p>]]>
  639.    </content>
  640. </entry>
  641.  
  642. <entry>
  643.    <title>WenZPerl Donate 10,000 EUR to new Perl 6 Core Development Fund</title>
  644.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/04/wenzperl-donate-10000-eur-to-n.html" />
  645.    <id>tag:news.perlfoundation.org,2015://18.3600</id>
  646.  
  647.    <published>2015-04-04T12:29:11Z</published>
  648.    <updated>2015-04-04T14:46:41Z</updated>
  649.  
  650.    <summary>I am pleased to announce the launch of a new fundraising drive to raise money for Perl 6 development. Its immediate focus is the target of releasing a Perl 6 language specification along with a conforming implementation in 2015; beyond this, funds will be used to support maintenance and improvement of Perl 6 implementation. The initial goal is to raise $25,000 to fund the work of Jonathan Worthington. Jonathan is a core developer of the Rakudo Perl 6 compiler and...</summary>
  651.    <author>
  652.        <name>Karen Pauley</name>
  653.        <uri>http://martian.org/karen</uri>
  654.    </author>
  655.    
  656.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  657.    
  658.        <category term="Perl 6 Development" scheme="http://www.sixapart.com/ns/types#category" />
  659.    
  660.    <category term="perl6coredevelopmentfund" label="perl 6 core development fund" scheme="http://www.sixapart.com/ns/types#tag" />
  661.    
  662.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  663.        <![CDATA[<p>I am pleased to announce the launch of a new fundraising drive to raise money for Perl 6 development. Its immediate focus is the target of releasing a Perl 6 language specification along with a conforming implementation in 2015; beyond this, funds will be used to support maintenance and improvement of Perl 6 implementation.</p>
  664.  
  665. <p>The initial goal is to raise $25,000 to fund the work of Jonathan Worthington.  Jonathan is a core developer of the Rakudo Perl 6 compiler and the architect and lead developer of MoarVM. </p>
  666.  
  667. <p>The 2015 push for a first Perl 6 language specification (defined by a conformance test suite) and a conforming implementation was announced by Larry Wall at <span class="caps">FOSDEM </span>(February 2015). The Rakudo Perl compiler along with the Moar Virtual Machine have been selected as the focus for implementation effort.</p>
  668.  
  669. <p>We would not have been able to create this fund without the generous donation of 10,000 <span class="caps">EUR </span>pledged by WenZPerl.  </p>
  670.  
  671. <p>WenZPerl BV is the Dutch open source consultancy company of Elizabeth Mattijsen and Wendy van Dijk, specialised in Perl programming and development.  WenZPerl has years of expertise in the development of (toolkits for development) interactive programs and websites. Further experience includes project management, <span class="caps">HRM, </span>and marketing.  WenZPerl is a proud supporter of open source and in particular a regular sponsor of Perl conferences, workshops and hackathons.</p>
  672.  
  673. <p>If you are interested in supporting the <a href="http://www.perlfoundation.org/perl_6_core_development_fund">Perl 6 Core Development Fund</a> please contact karen (at) perlfoundation.org.</p>]]>
  674.        
  675.    </content>
  676. </entry>
  677.  
  678. <entry>
  679.    <title>April 1 - Act</title>
  680.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/04/april-1---act.html" />
  681.    <id>tag:news.perlfoundation.org,2015://18.3598</id>
  682.  
  683.    <published>2015-04-01T08:21:47Z</published>
  684.    <updated>2015-04-02T08:27:27Z</updated>
  685.  
  686.    <summary>Since the beginning of the year, some smaller steps had been made and things are looking good! First of all the the database schema had been changed to provide some additional things on request of some organisers. Now I realise that I also need to make new versions of the Act-out-of-the-Box vagrant-image once in a while. The DBIx::Class has been updated accordingly and it all works like a charm Secondly, I started playing around with the DBIx::Class implementation and natural...</summary>
  687.    <author>
  688.        <name>Elizabeth Mattijsen</name>
  689.        
  690.    </author>
  691.    
  692.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  693.    
  694.    <category term="act" label="act" scheme="http://www.sixapart.com/ns/types#tag" />
  695.    
  696.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  697.        <![CDATA[<p>Since the beginning of the year, some smaller steps had been made and things are looking good!</p>
  698.  
  699. <p>First of all the the database schema had been changed to provide some additional things on request of some organisers. Now I realise that I also need to make new versions of the Act-out-of-the-Box vagrant-image once in a while. The <span class="caps">DBI</span>x::Class has been updated accordingly and it all works like a charm</p>
  700.  
  701. <p>Secondly, I started playing around with the <span class="caps">DBI</span>x::Class implementation and natural stumbled upon the first hurdle... Conferences are not in the database, those are neatly stored in a bunch of <span class="caps">INI </span>files. Adding another table to the database which will be populated from the <span class="caps">INI</span>-files is giving Act-Voyager at least a top-level entry point for the relation databases, finally there are relations between the rows in the separate tables.</p>
  702.  
  703. <p>Those <span class="caps">INI </span>files provide much more information and only some is really about the conference itself, like dates and location. Other things that are in it are the number of rooms what names they have, the price tiers and tickets or other products. Information that will have to end up in other tables soon. But, this all sounds like the start of the admin-tool, which I had given a lower priority.</p>
  704.  
  705. <p>While playing with the <span class="caps">DBI</span>x::Class schema and being very pleased that I could build simple scripts showing me a list of talks or users related to some conference, I started to write the first bit of the <span class="caps">REST </span>api, as a starting point... and here a whole new story unfolds itself:</p>
  706.  
  707. <p>Do You Speak-a My Language?</p>
  708.  
  709. <p>For entire population groups on planet earth it looks like they do not have to concern about language difference, for them there exists only 1 language, 1 language to rule all... And for those people it is fine to organise a conference or workshop in their local language. And it's perfectly okay to let Act perform in a way as if your local language would be the only one to consider. However, as organiser of the Dutch Perl Workshop, we care about being open to people that do not come from the Netherlands and do not speak Dutch and therefore run our web-site bilingual and provide most of the texts in English as well. I even suggested to one of our people to set it up in German.</p>
  710.  
  711. <p>Act caters for all that, no problem - only a technical design problem here.</p>
  712.  
  713. <p>Retrieving data in multiple languages from a <span class="caps">REST </span>api is not uncommon, and the <span class="caps">IETF </span>even came up with a solution called Content-Negotiation. Basically, 1 single canonical <span class="caps">URI </span>for 1 resource, using the"Accept-Language" header-field to let client and server decide what content will be delivered. There is no need to put a language tag inside the <span class="caps">URL </span>to do so. But it makes you wonder if there is the same way to create update or delete resources in a specific language... so, without causing url-polution.</p>
  714.  
  715. <p>Nope, no answer is to be found!</p>
  716.  
  717. <p>Until lately, when I figured out how to do <span class="caps">HTTP</span>-Authoring in a multilingual <span class="caps">REST </span>api, simply by using the 'Content-Language' header-field in the request. It is possible within the restraints of the <span class="caps">RFC</span>s to update a resource with a representation in another language, or only delete the language variant for a resource instead of entirely whipping it of the database.</p>
  718.  
  719. <p>In Cluj (Romania) and lately at AmsterdamX I gave a demonstration, a proof of concept. The implementation is quite easy and simple. Moreover it does also separate the <span class="caps">REST </span>api objects from the internal data structure. So many <span class="caps">API </span>designers couple their tables directly to <span class="caps">REST </span>resources, which is a big mistake on itself. Such solutions make it impossible to change underlying structures without corrupting the <span class="caps">REST </span>api. Having said that... for Act it is essential to have them separate because once the new version is up and running on top of the current database there will come a migration to a new database.</p>
  720.  
  721. <p>On GitHub you can find the AnimalSanctuary that does show some implentations on the above concept. Separating the <span class="caps">REST </span>objects and methods from the underlying structure, allowing complex class builders - and using the 'Content-Language' header-field to work with multilingual environments.</p>
  722.  
  723. <p>Now that these hurdles have been taken, it becomes time to start implementing the <span class="caps">REST </span>api and create 'Act::REST::Object builders'</p>
  724.  
  725. <p>Act Voyager has been exploring some interesting area's - time to move forward in warp-speed and see you next month, hopefully with most of the <span class="caps">API </span>ready.</p>
  726.  
  727. <p>Captain Theo</p>]]>
  728.        
  729.    </content>
  730. </entry>
  731.  
  732. </feed>
  733.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid Atom 1.0" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://feedvalidator.org/check.cgi?url=http%3A//news.perlfoundation.org/atom.xml

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda