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>2017-02-08T04:43:36Z</updated>
  8.    
  9.    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 6.2.2</generator>
  10.  
  11. <entry>
  12.    <title>Maintaining the Perl 5 Core: January 2017 report</title>
  13.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/02/maintaining-the-perl-5-core-ja.html" />
  14.    <id>tag:news.perlfoundation.org,2017://18.3850</id>
  15.  
  16.    <published>2017-02-07T23:00:00Z</published>
  17.    <updated>2017-02-08T04:43:36Z</updated>
  18.  
  19.    <summary>Dave Mitchell writes: There are two main things I did in December (along with the usual day-to-day stuff). First I sorted out infrastructure for ops which are called in boolean context. Currently PADHV and RV2HV ops are flagged specially if they are not only used in scalar context, but where the result they return will only ever be used as a boolean value; for example &apos;if (%h) {...}&apos; This was originally done since a hash in scalar context returned a...</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-us" xml:base="http://news.perlfoundation.org/">
  29.        <![CDATA[<p><em>Dave Mitchell writes:</em></p>
  30.  
  31. <pre>
  32. There are two main things I did in December (along with the usual
  33. day-to-day stuff).
  34.  
  35. First I sorted out infrastructure for ops which are called in boolean
  36. context.
  37.  
  38. Currently PADHV and RV2HV ops are flagged specially if they are not only
  39. used in scalar context, but where the result they return will only
  40. ever be used as a boolean value; for example 'if (%h) {...}'
  41.  
  42. This was originally done since a hash in scalar context returned a bucket
  43. usage ratio, which became expensive to calculate when we no longer
  44. stored the bucket occupancy count with each hash.
  45.  
  46. In 5.25.x we've changed it so that in scalar context it now only returns a
  47. key count, which is always known and doesn't need to be calculated on the
  48. fly. But it can still be quicker to return just a boolean value in
  49. these cases rather than an integer.
  50.  
  51. My work took this special-case boolean context detection code in the
  52. peephole optimiser, and improved it so that:
  53.  
  54. * it fixes a bunch of bugs - e.g. if (!%h) {...} wasn't recognised as
  55.   boolean;
  56. * it expands the number of situations that are recognised as boolean
  57.   context, such as grep:  e.g. grep %$_, @AoH;
  58. * it adds a reasonably comprehensive set of tests for checking that ops
  59.   have been flagged as boolean under various boolean scenarios;
  60. * it allows other ops to be easily added to the boolean detection in the
  61.   optimiser; and to the test suite.
  62.  
  63. I've also tweaked RV2HV so that in the negative case it just returns
  64. &PL_sv_no rather than sv_2mortal(newSViv(0)))
  65.  
  66. I've also pushed a branch davem/boolref2 that allows the ref() function to
  67. be optimised in boolean context; so 'if (ref $r) {...}' doesn't have to
  68. generate a temporary string like "Foo=ARRAY(0xc8afd8)". I intend to merge
  69. this after 5.26, and maybe booleanise a few more ops too (like length()).
  70.  
  71. The other notable thing I did last month was to change the output format
  72. produced by the op_dump() function (and perl -Dx). It now displays an
  73. ASCII-art tree structure, and more low-level information is displayed,
  74. such as each op's address and class.
  75.  
  76.  
  77. SUMMARY:
  78.      3:21 RT #129285 Perl_gv_fullname4 assertion
  79.      0:36 RT #130617 Perl_rpeep: Assertion ....
  80.      0:55 RT #130621 Segfault in Perl_vwarner (util.c:2051)
  81.      0:49 RT #130648 S_pat_upgrade_to_utf8 Assertion ...
  82.      1:17 RT #130651] regcomp.c:6881 Assertion `expr' failed
  83.      1:19 RT #130661 perly.c:341: Perl_yyparse: Assertion failed
  84.      1:03 RT #130667 Perl_sv_clear Assertion `SvTYPE(sv) != ...
  85.      0:52 RT #130669 Perl_sv_2nv_flags: Assertion `SvTYPE(sv) != ...
  86.      5:18 [perl #130198] chop(@x =~ tr///)
  87.      3:00 [perl #130584] Slow pos function in taint mode with \G
  88.     22:53 [perl #78288] ref and other ops are inefficient in boolean context
  89.     12:08 change output format of op_dump()
  90.      3:20 factor out common optree finalisation code
  91.      4:30 general housekeeping
  92.     10:41 process p5p mailbox
  93.      2:51 review security tickets
  94.    ------
  95.     74:53 TOTAL (HH::MM)
  96.  
  97. 172.3 weeks
  98. 2376.7 total hours
  99.  13.8 average hours per week
  100.  
  101. There are 423 hours left on the grant
  102. </pre>
  103. ]]>
  104.        
  105.    </content>
  106. </entry>
  107.  
  108. <entry>
  109.    <title>January 2017 Grant Votes</title>
  110.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/january-2017-grant-votes.html" />
  111.    <id>tag:news.perlfoundation.org,2017://18.3849</id>
  112.  
  113.    <published>2017-01-31T23:00:00Z</published>
  114.    <updated>2017-02-07T05:24:27Z</updated>
  115.  
  116.    <summary>The Grants Committee has concluded the voting of the January round. Proposal in this round ProposerRequested AmountLink to the Details Standardization, Test Coverage, and Documentation of Perl 6 I/O RoutinesUSD 999Proposal Voting Results TitleYesNoScore Standardization, Test Coverage, and Documentation of Perl 6 I/O Routines7035 = 5 + 5 + 5 + 5 + 5 + 5 + 5 + 0 + 0 Definition of the score is found in 3.2 of the rules. Details We approve this grant. This is...</summary>
  117.    <author>
  118.        <name>Makoto Nozaki</name>
  119.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  120.    </author>
  121.    
  122.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  123.    
  124.    
  125.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  126.        <![CDATA[<p>The Grants Committee has concluded the voting of the January round.</p>
  127.  
  128. <h3>Proposal in this round</h3>
  129.  
  130. <p><p><table border=1 style="border:1px solid black;border-collapse:collapse;"><tr><th>Proposer<th>Requested Amount</th><th>Link to the Details</th>
  131. <tr><td>Standardization, Test Coverage, and Documentation of Perl 6 I/O Routines<td style="text-align:right">USD 999<td><a href="http://news.perlfoundation.org/2017/01/grant-proposal-standardization.html">Proposal</a></tr>
  132. </table></p>
  133.  
  134. <h3>Voting Results</h3>
  135.  
  136. <p><p><table border=1 style="border:1px solid black;border-collapse:collapse;"><tr><th>Title</th><th>Yes</th><th>No</th><th>Score</th>
  137. <tr><td>Standardization, Test Coverage, and Documentation of Perl 6 I/O Routines<td style="text-align:right">7<td style="text-align:right">0<td>35 = 5 + 5 + 5 + 5 + 5 + 5 + 5 + 0 + 0</tr>
  138. </table></p>
  139.  
  140. <p>Definition of the score is found in 3.2 of the <a href="http://www.perlfoundation.org/rules_of_operation">rules</a>.</p>
  141.  
  142. <h3>Details</h3>
  143.  
  144. <p>We approve this grant.</p>
  145.  
  146. <p>This is an area that needs work in Rakudo Perl 6, and Zoffix has a history of delivering tangible improvements to the compiler and the infrastructure in the community.</p>
  147.  
  148. <p>Our next round will be in March. You can <a href="http://www.perlfoundation.org/how_to_write_a_proposal">submit proposals</a> now. If you want to help funding, one of the options is <a href="http://news.perlfoundation.org/2014/03/tpf-is-now-participating-on-am.html">Amazon Smile</a>. We appreciate all the donors which made the grant program possible. Also see the <a href="http://www.perlfoundation.org/press_releases">press releases</a> for the recent major donations.</p>
  149. ]]>
  150.        
  151.    </content>
  152. </entry>
  153.  
  154. <entry>
  155.    <title>Dave Mitchell&apos;s Grant Extended</title>
  156.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/dave-mitchells-grant-extended-2.html" />
  157.    <id>tag:news.perlfoundation.org,2017://18.3848</id>
  158.  
  159.    <published>2017-01-29T14:00:00Z</published>
  160.    <updated>2017-01-29T19:32:21Z</updated>
  161.  
  162.    <summary>Dave Mitchell recently requested an extension of his Maintaining Perl 5 grant. I&apos;m pleased to announce that the Board of Directors approved extension of another $20,000. I would like to thank the community members who took time to comment on this grant extension request and our sponsors who made funding the grant possible through our Perl 5 Core Maintenance Fund....</summary>
  163.    <author>
  164.        <name>Makoto Nozaki</name>
  165.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  166.    </author>
  167.    
  168.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  169.    
  170.    
  171.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  172.        <![CDATA[<p>Dave Mitchell recently <a href="http://news.perlfoundation.org/2017/01/grant-extension-request-mainta-2.html">requested an extension of his Maintaining Perl 5 grant</a>.</p>
  173.  
  174. <p>I'm pleased to announce that the Board of Directors approved extension of another $20,000.</p>
  175.  
  176. <p>I would like to thank the community members who took time to comment on this grant extension request and our sponsors who made funding the grant possible through our Perl 5 Core Maintenance Fund.</p>
  177. ]]>
  178.        
  179.    </content>
  180. </entry>
  181.  
  182. <entry>
  183.    <title>Grants Committee needs a new member</title>
  184.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/grants-committee-needs-a-new-m.html" />
  185.    <id>tag:news.perlfoundation.org,2017://18.3847</id>
  186.  
  187.    <published>2017-01-25T22:00:00Z</published>
  188.    <updated>2017-01-26T05:08:38Z</updated>
  189.  
  190.    <summary>The Perl Foundation&apos;s Grants Committee is looking for a new member. The new member will work at the committee in this large, high-profile nonprofit organization with other 13 members (see the bottom for the list) who include 4 White Camel Award recipients. The committee has presence in all the global regions and major Perl development threads. It&apos;s a volunteer position with no compensation. We would like to elect either one of 1) the Committee Secretary 2) Committee Member. If you...</summary>
  191.    <author>
  192.        <name>Makoto Nozaki</name>
  193.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  194.    </author>
  195.    
  196.        <category term="Perl Foundation" scheme="http://www.sixapart.com/ns/types#category" />
  197.    
  198.    
  199.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  200.        <![CDATA[<p>The Perl Foundation's Grants Committee is looking for a new member.</p>
  201.  
  202. <p>The new member will work at the committee in this large, high-profile nonprofit organization with other 13 members (see the bottom for the list) who include 4 White Camel Award recipients. The committee has presence in all the global regions and major Perl development threads. It's a volunteer position with no compensation.</p>
  203.  
  204. <p>We would like to elect either one of 1) the Committee Secretary 2) Committee Member. If you are interested, please read the below.</p>
  205.  
  206. <p><p></p>
  207.  
  208. <h2>Nomination procedure</h2>
  209.  
  210. <p>Candidates must be nominated by a member (voting/non-voting) of the Grants Committee.</p>
  211.  
  212. <p>If you would like to be nominated, please get in touch with one of the members below or the Secretary (makoto@perlfoundation.org).</p>
  213.  
  214. <p>The nomination process will be closed on Feb 1st.</p>
  215.  
  216. <p><p></p>
  217.  
  218. <h2>Position Details</h2>
  219.  
  220. <p><strong>Committee Secretary</strong></p>
  221.  
  222. <p>Your roles will include 1) grant management 2) the committee management 3) grant scheduling 4) budget management 5) anything that will improve the grant program.</p>
  223.  
  224. <p>Note that the Secretary doesn't vote except for the casting vote and usually doesn't express opinion on each grant.</p>
  225.  
  226. <p>You are expected to spend at least 2 hours per week. The opportunity is unlimited and you may spend as many hours as you want.</p>
  227.  
  228. <p><strong>Committee Member</strong></p>
  229.  
  230. <p>You will be responsible for voting to decide which grants to fund using the community money. You will also work with other members to improve the grant program.</p>
  231.  
  232. <p><p></p>
  233.  
  234. <h2>Frequently Asked Questions</h2>
  235.  
  236. <p>Q1: Will the nomination and selection be made in public?</p>
  237.  
  238. <p>A1: No. Only the selected individual will be announced.</p>
  239.  
  240. <p>Q2: What if I have further questions?</p>
  241.  
  242. <p>A2: Feel free to contact me at makoto@perlfoundation.org or comment here.</p>
  243.  
  244. <p><p></p>
  245.  
  246. <h2>Current Members List</h2>
  247.  
  248. <ul>
  249. <li>Makoto Nozaki (Secretary)</li>
  250. <li>Will "Coke" Coleda</li>
  251. <li>Rafael Garcia-Suarez</li>
  252. <li>Perrin Harkins</li>
  253. <li>Thomas Klausner</li>
  254. <li>Daisuke Maki</li>
  255. <li>Elizabeth Mattijsen</li>
  256. <li>Ricardo Signes</li>
  257. <li>Alberto Simões</li>
  258. <li>Sawyer X</li>
  259. <li>Alan Alavi (non-voting)</li>
  260. <li>Tom Hukins (non-voting)</li>
  261. <li>Mark A. Jensen (non-voting)</li>
  262. </ul>
  263. ]]>
  264.        
  265.    </content>
  266. </entry>
  267.  
  268. <entry>
  269.    <title>Maintaining Perl 5: Grant Report for December 2016</title>
  270.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/maintaining-perl-5-grant-repor-36.html" />
  271.    <id>tag:news.perlfoundation.org,2017://18.3846</id>
  272.  
  273.    <published>2017-01-25T21:00:00Z</published>
  274.    <updated>2017-01-26T05:10:06Z</updated>
  275.  
  276.    <summary>Tony Cook writes: Approximately 21 tickets were reviewed or worked on, and 2 patches were applied. [Hours] [Activity] 4.33 #127149 re-work patch to fix a related issue, debugging #127149 debugging, comment on Encode #59 14.98 #127663 testing, minor polish, re-check, comment with patch #127663 reply to comment, work on additional patch for env control of the internal seed #127663 more internal seed env, comment with patch #127663 work on patch updates, testing #127663 more patch updates, work on patch to...</summary>
  277.    <author>
  278.        <name>Makoto Nozaki</name>
  279.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  280.    </author>
  281.    
  282.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  283.    
  284.    
  285.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  286.        <![CDATA[<p><em>Tony Cook writes:</em></p>
  287.  
  288. <pre>
  289. Approximately 21 tickets were reviewed or worked on, and 2 patches
  290. were applied.
  291.  
  292. [Hours]         [Activity]
  293.  4.33          #127149 re-work patch to fix a related issue, debugging
  294.                #127149 debugging, comment on Encode #59
  295. 14.98          #127663 testing, minor polish, re-check, comment with
  296.                patch
  297.                #127663 reply to comment, work on additional patch for env
  298.                control of the internal seed
  299.                #127663 more internal seed env, comment with patch
  300.                #127663 work on patch updates, testing
  301.                #127663 more patch updates, work on patch to optionally
  302.                disable hash randomization env vars
  303.                #127663 *at probes, bang head against metaconfig a bit,
  304.                directly modify Configure instead
  305.                #127663 more Configure, re-work in-place editing code to
  306.                use the new functions, testing
  307.                #127663 work on chdir test
  308.                #127663 config fixes
  309.  1.23          #128093 testing an comment
  310.  0.65          #129788 testing, apply patch to blead
  311.  0.27          #130056 review discussion, comment
  312.  2.35          #130122 partly review patch
  313.                #130122 review the rest, testing
  314.  1.53          #130169 review, testing, apply to blead
  315.  1.22          #130195 review discussion, patch
  316.                #130195 testing (and it turns out Dave applied it)
  317.  0.25          #130242 research and comment
  318.  0.27          #130256 (sec) testing, comment
  319.  0.67          #130262 (sec) testing, produce a fix, comment with patch
  320.  1.80          #130270 testing, debugging
  321.  0.50          #130321 (sec) review, debug, comment
  322.  0.27          #130328 comment
  323.  0.27          #130332 (sec) testing, minify, comment
  324.  1.98          #130335 review issue, write a test, work on a patch
  325.                #130335 debugging, fixes, comment with patch
  326.  0.47          #130336 (sec) testing, minify, comment
  327.  1.55          #130344 (sec) testing, minify, debugging, comment
  328.  1.72          #130367 work on a patch, testing, comment
  329.  0.37          perldelta update
  330.  0.32          security list discussion
  331. ======
  332. 37.00 hours total
  333. </pre>
  334. ]]>
  335.        
  336.    </content>
  337. </entry>
  338.  
  339. <entry>
  340.    <title>Final Grant Report : RPerl User Documentation #2 </title>
  341.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/final-grant-report-rperl-user-.html" />
  342.    <id>tag:news.perlfoundation.org,2017://18.3845</id>
  343.  
  344.    <published>2017-01-25T02:38:34Z</published>
  345.    <updated>2017-01-25T02:53:45Z</updated>
  346.  
  347.    <summary><![CDATA[Will Braswell has submitted his final report (below) on his grant RPerl User Documentation, Part 2. The Grants Committee welcomes comments from the community before it votes on completion of the grant. MAJ RPerl User Documentation, Part 2, Final Report Deliverables Inch-stones Completeness Criteria RPerl User Documentation, Part 2, Final Report Name: Will Braswell Amount Requested: USD 1,600 Deliverables Deliverables for this grant proposal are: 1. Complete Learning RPerl Chapter 2 CHAPTER 2: SCALAR VALUES &amp; VARIABLES (NUMBERS &amp; TEXT)...]]></summary>
  348.    <author>
  349.        <name>Mark A Jensen</name>
  350.        
  351.    </author>
  352.    
  353.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  354.    
  355.    <category term="grants" label="grants" scheme="http://www.sixapart.com/ns/types#tag" />
  356.    <category term="rperl" label="RPerl" scheme="http://www.sixapart.com/ns/types#tag" />
  357.    
  358.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  359.        <![CDATA[<p>Will Braswell has submitted his final report (below) on his grant
  360. <a href="http://news.perlfoundation.org/2016/02/grant-proposal-rperl-user-docu-1.html">RPerl User Documentation, Part 2</a>.</p>
  361.  
  362. <p>The Grants Committee welcomes comments from the community before it
  363. votes on completion of the grant.</p>
  364.  
  365. <p>MAJ</p>
  366.  
  367. <hr>
  368.  
  369. <ul id="index">
  370.  <li><a href="#RPerl-User-Documentation-Part-2-Final-Report">RPerl User Documentation, Part 2, Final Report</a>
  371.    <ul>
  372.      <li><a href="#Deliverables">Deliverables</a></li>
  373.      <li><a href="#Inch-stones">Inch-stones</a></li>
  374.      <li><a href="#Completeness-Criteria">Completeness Criteria</a></li>
  375.    </ul>
  376.  </li>
  377. </ul>
  378.  
  379. <h1 id="RPerl-User-Documentation-Part-2-Final-Report">RPerl User Documentation, Part 2, Final Report</h1>
  380.  
  381. <dl>
  382.  
  383. <dt id="Name">Name:</dt>
  384. <dd>
  385.  
  386. <p>Will Braswell</p>
  387.  
  388. </dd>
  389. <dt id="Amount-Requested">Amount Requested:</dt>
  390. <dd>
  391.  
  392. <p>USD 1,600</p>
  393.  
  394. </dd>
  395. </dl>
  396.  
  397. <h2 id="Deliverables">Deliverables</h2>
  398.  
  399. <p>Deliverables for this grant proposal are:</p>
  400.  
  401. <p>1. Complete Learning RPerl Chapter 2</p>
  402.  
  403. <p><a href="http://rperl.org/learning_rperl.html#CHAPTER_2%3A_SCALAR_VALUES_%26_VARIABLES_(NUMBERS_%26_TEXT)">CHAPTER 2: SCALAR VALUES &amp; VARIABLES (NUMBERS &amp; TEXT)</a></p>
  404.  
  405. <p>2. Write Learning RPerl Chapter 3</p>
  406.  
  407. <p><a href="http://rperl.org/learning_rperl.html#CHAPTER_3%3A_ARRAY_VALUES_%26_VARIABLES">CHAPTER 3: ARRAY VALUES &amp; VARIABLES</a></p>
  408.  
  409. <p>3. Write Learning RPerl Chapter 4</p>
  410.  
  411. <p><a href="http://rperl.org/learning_rperl.html#CHAPTER_4%3A_ORGANIZING_BY_SUBROUTINES">CHAPTER 4: ORGANIZING BY SUBROUTINES</a></p>
  412.  
  413. <h2 id="Inch-stones">Inch-stones</h2>
  414.  
  415. <p>Chapter 2 Scalar Data</p>
  416.  
  417. <p>1a. Numbers; Strings; RPerl&rsquo;s Built-in Warnings; Scalar Variables</p>
  418.  
  419. <p><a href="http://rperl.org/learning_rperl.html#Section_2.1%3A_Numeric_Data_%26_Operators">Section 2.1: Numeric Data &amp; Operators</a></p>
  420.  
  421. <p><a href="http://rperl.org/learning_rperl.html#Section_2.2%3A_Text_Data_%26_Operators">Section 2.2: Text Data &amp; Operators</a></p>
  422.  
  423. <p><a href="http://rperl.org/learning_rperl.html#Section_2.3%3A_RPerl%B4s_Phases%2C_Warnings_%26_Errors">Section 2.3: RPerl&acute;s Phases, Warnings &amp; Errors</a></p>
  424.  
  425. <p><a href="http://rperl.org/learning_rperl.html#Section_2.4%3A_Variables_With_Scalar_Values">Section 2.4: Variables With Scalar Values</a></p>
  426.  
  427. <p>1b. Output with print; The if Control Structure; Getting User Input; The chomp Operator</p>
  428.  
  429. <p><a href="http://rperl.org/learning_rperl.html#Section_2.6%3A_Displaying_Output_Using_The_print_Operator">Section 2.6: Displaying Output Using The print Operator</a></p>
  430.  
  431. <p><a href="http://rperl.org/learning_rperl.html#Section_2.7%3A_Program_Control_Using_The_if_Conditional_Statement">Section 2.7: Program Control Using The if Conditional Statement</a></p>
  432.  
  433. <p><a href="http://rperl.org/learning_rperl.html#Section_2.8%3A_Receiving_Input_From_The_User_%26_STDIN">Section 2.8: Receiving Input From The User &amp; STDIN</a></p>
  434.  
  435. <p><a href="http://rperl.org/learning_rperl.html#Section_2.4.13%3A_chop_%26_chomp_Operators">Section 2.4.13: chop &amp; chomp Operators</a></p>
  436.  
  437. <p>1c. The while Control Structure; The undef Value; The defined Function</p>
  438.  
  439. <p><a href="http://rperl.org/learning_rperl.html#Section_2.9%3A_Program_Control_Using_The_while_Loop">Section 2.9: Program Control Using The while Loop</a></p>
  440.  
  441. <p><a href="http://rperl.org/learning_rperl.html#Section_2.4%3A_Variables_With_Scalar_Values">Section 2.4: Variables With Scalar Values</a></p>
  442.  
  443. <p>Chapter 3 Lists and Arrays</p>
  444.  
  445. <p>2a. Accessing Elements of an Array; Special Array Indices; List Literals; List Assignment</p>
  446.  
  447. <p><a href="http://rperl.org/learning_rperl.html#Section_3.3%3A_How_To_Access_Array_Elements">Section 3.3: How To Access Array Elements</a></p>
  448.  
  449. <p><a href="http://rperl.org/learning_rperl.html#Section_3.4%3A_Array_Length_%26_Negative_Indices">Section 3.4: Array Length &amp; Negative Indices</a></p>
  450.  
  451. <p><a href="http://rperl.org/learning_rperl.html#Section_3.1%3A_Lists_vs_Arrays">Section 3.1: Lists vs Arrays</a></p>
  452.  
  453. <p><a href="http://rperl.org/learning_rperl.html#Section_3.7%3A_Array_Assignment">Section 3.7: Array Assignment</a></p>
  454.  
  455. <p>2b. Interpolating Arrays into Strings; The foreach Control Structure</p>
  456.  
  457. <p><a href="http://rperl.org/learning_rperl.html#Section_3.11%3A_Converting_From_Array_To_String">Section 3.11: Converting From Array To String</a></p>
  458.  
  459. <p><a href="http://rperl.org/learning_rperl.html#Section_3.12.3%3A_The_foreach_Loop">Section 3.12.3: The foreach Loop</a></p>
  460.  
  461. <p>2c. Scalar and List Context; &lt;STDIN&gt; in List Context</p>
  462.  
  463. <p><a href="http://rperl.org/learning_rperl.html#Section_3.16%3A_Scalar_%26_Array_Contexts">Section 3.16: Scalar &amp; Array Contexts</a></p>
  464.  
  465. <p><a href="http://rperl.org/learning_rperl.html#Section_3.17%3A_STDIN_%26_Arrays">Section 3.17: STDIN &amp; Arrays</a></p>
  466.  
  467. <p>Chapter 4 Subroutines</p>
  468.  
  469. <p>3a. Defining a Subroutine; Invoking a Subroutine; Return Values; Arguments</p>
  470.  
  471. <p><a href="http://rperl.org/learning_rperl.html#Section_4.1%3A_Subroutine_Definitions">Section 4.1: Subroutine Definitions</a></p>
  472.  
  473. <p><a href="http://rperl.org/learning_rperl.html#Section_4.2%3A_Subroutine_Calls">Section 4.2: Subroutine Calls</a></p>
  474.  
  475. <p><a href="http://rperl.org/learning_rperl.html#Section_4.3%3A_Subroutine_Return_Values">Section 4.3: Subroutine Return Values</a></p>
  476.  
  477. <p><a href="http://rperl.org/learning_rperl.html#Section_4.4%3A_Subroutine_Arguments">Section 4.4: Subroutine Arguments</a></p>
  478.  
  479. <p>3b. Private Variables in Subroutines; Variable-Length Parameter Lists; Notes on Lexical (my) Variables</p>
  480.  
  481. <p><a href="http://rperl.org/learning_rperl.html#Section_4.5%3A_Subroutine_Variables%2C_Variable_Scope_%26_Persistence">Section 4.5: Subroutine Variables, Variable Scope &amp; Persistence</a></p>
  482.  
  483. <p><a href="http://rperl.org/learning_rperl.html#Section_4.4.1%3A_Variadic_Subroutines">Section 4.4.1: Variadic Subroutines</a></p>
  484.  
  485. <p><a href="http://rperl.org/learning_rperl.html#Section_4.5.1%3A_my_Intermittent_Variables">Section 4.5.1: my Intermittent Variables</a></p>
  486.  
  487. <p>3c. The use strict Pragma; The return Operator</p>
  488.  
  489. <p><a href="http://rperl.org/learning_rperl.html#Section_4.6%3A_use_strict%3B_use_warnings%3B_Pragmas_%26_Magic">Section 4.6: use strict; use warnings; Pragmas &amp; Magic</a></p>
  490.  
  491. <p><a href="http://rperl.org/learning_rperl.html#Section_4.3.1%3A_return_Operator">Section 4.3.1: return Operator</a></p>
  492.  
  493. <p>3d. Non-Scalar Return Values; Persistent, Private Variables</p>
  494.  
  495. <p><a href="http://rperl.org/learning_rperl.html#Section_4.3.2%3A_Multiple_Return_Values">Section 4.3.2: Multiple Return Values</a></p>
  496.  
  497. <p><a href="http://rperl.org/learning_rperl.html#Section_4.5.2%3A_Persistent_State%2C_Pseudo-State_Variables">Section 4.5.2: Persistent State, Pseudo-State Variables</a></p>
  498.  
  499. <h2 id="Completeness-Criteria">Completeness Criteria</h2>
  500.  
  501. <p>I will release a new version of RPerl to CPAN with the new documentation.</p>
  502.  
  503. <p><i>[ RPerl v2.41 on CPAN contains chapters 2 and 3, while chapter 4 has already been published on RPerl.org; chapter 4 will be uploaded to CPAN as part of the next stable release of RPerl in February. ]</i></p>
  504.  
  505. <p><a href="https://metacpan.org/pod/release/WBRASWELL/RPerl-2.410000/lib/RPerl/Learning.pm">Learning RPerl</a> (CPAN)</p>
  506.  
  507. <p>I will release a new version of the RPerl website with the new documentation.</p>
  508.  
  509. <p><a href="http://rperl.org/learning_rperl.html">Learning RPerl</a> (RPerl site)</p>
  510. ]]>
  511.        
  512.    </content>
  513. </entry>
  514.  
  515. <entry>
  516.    <title>Grant Report : RPerl User Documentation #2 - Dec 2016</title>
  517.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/grant-report-rperl-user-docume-12.html" />
  518.    <id>tag:news.perlfoundation.org,2017://18.3844</id>
  519.  
  520.    <published>2017-01-23T00:06:46Z</published>
  521.    <updated>2017-01-23T00:22:37Z</updated>
  522.  
  523.    <summary>Will Braswell reports that he has completed the deliverables for RPerl Docs #2: &quot;Lots of big news for RPerl! First, Christmas saw the release of the new Perl-powered platform CloudForFree.org ;v1.0, codename Nimbostratus. Secondly, on New Years Day we released RPerl v2.4, codename Aurora. And last but not least, we are proud to announce the publication of Learning RPerl chapter 4, thereby completing part 2 of the TPF grant! Over 160 pages of brand new material has been written under...</summary>
  524.    <author>
  525.        <name>Mark A Jensen</name>
  526.        
  527.    </author>
  528.    
  529.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  530.    
  531.    <category term="grants" label="grants" scheme="http://www.sixapart.com/ns/types#tag" />
  532.    <category term="rperl" label="RPerl" scheme="http://www.sixapart.com/ns/types#tag" />
  533.    
  534.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  535.        <![CDATA[<p>Will Braswell reports that he has completed the deliverables for
  536. <a href="http://news.perlfoundation.org/2016/02/grant-proposal-rperl-user-docu-1.html">RPerl Docs #2</a>:</p>
  537.  
  538. <p>"Lots of big news for RPerl!
  539. First, Christmas saw the release of the new Perl-powered platform <a href="http://CloudForFree.org">CloudForFree.org</a> ;v1.0, codename Nimbostratus.
  540. Secondly, on New Years Day we released <a href="https://metacpan.org/release/WBRASWELL/RPerl-2.410000">RPerl v2.4</a>, codename Aurora.
  541. And last but not least, we are proud to announce the publication of Learning RPerl chapter 4, thereby completing part 2 of the TPF grant!
  542. Over 160 pages of brand new material has been written under this grant for chapters 2, 3, and 4 of Learning RPerl.</p>
  543.  
  544. <p><a href="http://rperl.org/learning_rperl.html#CHAPTER_4%3A_ORGANIZING_BY_SUBROUTINES" >CHAPTER 4: ORGANIZING BY SUBROUTINES</a><span ></span><ul ><li ><a href="http://rperl.org/learning_rperl.html#Section_4.1%3A_Subroutine_Definitions" >Section 4.1: Subroutine Definitions</a></li><li ><a href="http://rperl.org/learning_rperl.html#Section_4.2%3A_Subroutine_Calls" >Section 4.2: Subroutine Calls</a><ul ><li ><a href="http://rperl.org/learning_rperl.html#Section_4.2.1%3A_Parentheses_Suffix_%26_Ampersand_Sigil_Prefix" >Section 4.2.1: Parentheses Suffix &amp; Ampersand Sigil Prefix</a></li></ul></li><li ><a href="http://rperl.org/learning_rperl.html#Section_4.3%3A_Subroutine_Return_Values" >Section 4.3: Subroutine Return Values</a><ul ><li ><a href="http://rperl.org/learning_rperl.html#Section_4.3.1%3A_return_Operator" >Section 4.3.1: return Operator</a></li><li ><a href="http://rperl.org/learning_rperl.html#Section_4.3.2%3A_Multiple_Return_Values" >Section 4.3.2: Multiple Return Values</a></li></ul></li><li ><a href="http://rperl.org/learning_rperl.html#Section_4.4%3A_Subroutine_Arguments" >Section 4.4: Subroutine Arguments</a><ul ><li ><a href="http://rperl.org/learning_rperl.html#Section_4.4.1%3A_Variadic_Subroutines" >Section 4.4.1: Variadic Subroutines</a></li></ul></li><li ><a href="http://rperl.org/learning_rperl.html#Section_4.5%3A_Subroutine_Variables%2C_Variable_Scope_%26_Persistence" >Section 4.5: Subroutine Variables, Variable Scope &amp; Persistence</a><ul ><li ><a href="http://rperl.org/learning_rperl.html#Section_4.5.1%3A_my_Intermittent_Variables" >Section 4.5.1: my Intermittent Variables</a></li></ul></li><li ><a href="http://rperl.org/learning_rperl.html#Section_4.6%3A_use_strict%3B_use_warnings%3B_Pragmas_%26_Magic" >Section 4.6: use strict; use warnings; Pragmas &amp; Magic</a></li><li ><a href="http://rperl.org/learning_rperl.html#Section_4.7%3A_Exercises" >Section 4.7: Exercises</a><ul ><li ><a href="http://rperl.org/learning_rperl.html#1._Subroutine_To_Calculate_Total_Of_Numeric_Array_Elements_%5B_45_mins_%5D" >1. Subroutine To Calculate Total Of Numeric Array Elements [ 45 mins ]</a></li><li ><a href="http://rperl.org/learning_rperl.html#2._Subroutine_To_Calculate_Total_Of_Numbers_1_Through_1_000_%5B_15_mins_%5D" >2. Subroutine To Calculate Total Of Numbers 1 Through 1_000 [ 15 mins ]</a></li><li ><a href="http://rperl.org/learning_rperl.html#3._Subroutine_To_Find_Above-Average_Array_Elements_%5B_45_mins_%5D" >3. Subroutine To Find Above-Average Array Elements [ 45 mins ]</a></li><li ><a href="http://rperl.org/learning_rperl.html#4._Subroutine_To_Greet_User_%26_Store_Program_State_%5B_30_mins_%5D" >4. Subroutine To Greet User &amp; Store Program State [ 30 mins ]</a></li><li ><a href="http://rperl.org/learning_rperl.html#5._Subroutine_To_Greet_User_%26_Store_More_Program_State_%5B_35_mins_%5D" >5. Subroutine To Greet User &amp; Store More Program State [ 35 mins ]</a></li></ul></li></ul>
  545. What's next for RPerl?  ;What other exciting new advancements are coming down the pike?
  546. Stay tuned to <a href="http://RPerl.org">RPerl.org</a> and find out!"</p>
  547.  
  548. <p>MAJ</p>
  549. ]]>
  550.        
  551.    </content>
  552. </entry>
  553.  
  554. <entry>
  555.    <title>Grant Proposal: Standardization, Test Coverage, and Documentation of Perl 6 I/O Routines</title>
  556.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/grant-proposal-standardization.html" />
  557.    <id>tag:news.perlfoundation.org,2017://18.3843</id>
  558.  
  559.    <published>2017-01-17T15:00:00Z</published>
  560.    <updated>2017-01-30T11:53:26Z</updated>
  561.  
  562.    <summary>The Grants Committee has received one grant proposal Standardization, Test Coverage, and Documentation of Perl 6 I/O Routines for the January round. Before the Committee members vote, we would like to solicit feedback from the Perl community on the proposal. Review the proposal below and please comment here by January 23rd, 2017. The Committee members will start the voting process following that and the conclusion will be announced approximately in one week. Standardization, Test Coverage, and Documentation of Perl 6...</summary>
  563.    <author>
  564.        <name>Makoto Nozaki</name>
  565.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  566.    </author>
  567.    
  568.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  569.    
  570.    
  571.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  572.        <![CDATA[<p>The Grants Committee has received one grant proposal <strong>Standardization, Test Coverage, and Documentation of Perl 6 I/O Routines</strong> for the January round.  Before the Committee members vote, we would like to solicit feedback from the Perl community on the proposal.</p>
  573.  
  574. <p>Review the proposal below and please comment here by January 23rd, 2017.  The Committee members will start the voting process following that and the conclusion will be announced approximately in one week.</p>
  575.  
  576. <h1>Standardization, Test Coverage, and Documentation of Perl 6 I/O Routines</h1>
  577.  
  578. <ul>
  579. <li><p>Name:</p>
  580.  
  581. <p>Zoffix Znet (legal name: Pete Evstratov)</p></li>
  582. <li><p>Amount Requested:</p>
  583.  
  584. <p>USD 999</p></li>
  585. </ul>
  586.  
  587. <h2>Synopsis</h2>
  588.  
  589. <p>Many of Perl 6's I/O routines currently have inconsistencies in behaviour
  590. between method and subroutine forms along with inconsistencies in calling
  591. forms and failure modes compared to the rest of the language. Also some of
  592. them, despite being speculated in the synopses and implemented in Rakudo, have
  593. no test coverage in the Perl 6 Specification, and as such they remain
  594. undocumented and not part of the Perl 6 Language. Some of the routines that do
  595. have presence in the Specification, have sparse test coverage, leaving
  596. some of their functionality entirely untested.</p>
  597.  
  598. <p>The work funded by this grant seeks to resolve those inconsistencies, as well
  599. as provide full test coverage and documentation.</p>
  600.  
  601. <h2>Benefits to the Perl Community</h2>
  602.  
  603. <p>Inconsistent interfaces are difficult to master and are bug-prone due to
  604. programmers forgetting about varying details of individual routines. By making
  605. I/O routines take arguments and indicate failures consistent to the way it's
  606. done in the rest of the language, they will be much easier for programmers to
  607. learn and use. Along with a more pleasant interface, the Perl Community will
  608. also benefit by needing to provide less support for people trying to learn the
  609. language.</p>
  610.  
  611. <p>The largest benefit will come from the full test coverage that will no doubt
  612. reveal bugs that can be fixed before they're encountered by users in
  613. production code. The coverage will also protect from future bugs being
  614. introduced inadvertently. Also, the currently unspecced routines will be
  615. officially part of the language, and so will be documented and available for
  616. use.</p>
  617.  
  618. <h3><strong>As bonus benefits:</strong></h3>
  619.  
  620. <p>The timing of this work seeks to align with the production of "Learning Perl 6"
  621. book, in order for it to contain valid information on I/O routines and
  622. describe only routines that are actually part of the language, which will
  623. avoid confusion for its readers and folks helping those readers learn Perl 6.</p>
  624.  
  625. <p>Lastly, the bonus deliverables (described below) will benefit further
  626. development of Rakudo/Perl 6 by elucidating unspecced, unused, or unwanted
  627. routines. The data can also be used to produce a teaching/reference aid
  628. (e.g. flash cards with routine names or IRC bot for routine reference).</p>
  629. ]]>
  630.        <![CDATA[<h2>Deliverables</h2>
  631.  
  632. <p><strong>Scope:</strong> by <em>I/O routines</em> this grant proposal means subroutines and
  633. methods of the <a href="https://github.com/rakudo/rakudo/">Rakudo implementation</a>
  634. found in <code>src/core/io_operators.pm</code>,
  635. <code>src/core/IO.pm</code>, <code>src/core/IO/ArgFiles.pm</code>, <code>src/core/IO/Handle.pm</code>,
  636. <code>src/core/IO/Notification.pm</code>, <code>src/core/IO/Path.pm</code>, <code>src/core/IO/Pipe.pm</code>,
  637. <code>src/core/IO/Special.pm</code>, and <code>src/core/IO/Spec.pm</code> as well as its
  638. subclasses found in <code>src/core/IO/Spec/</code> directory. Note that <code>IO::Socket</code> and
  639. its subclasses are NOT in the scope of this grant proposal.</p>
  640.  
  641. <p>Deliverables:</p>
  642.  
  643. <ul>
  644. <li>I/O Action Plan Report</li>
  645. <li>Commits in <a href="https://github.com/rakudo/rakudo/">rakudo</a> implementing
  646. the Action Plan.</li>
  647. <li>Commits in <a href="https://github.com/perl6/roast">Perl 6 Specification</a>
  648. providing full coverage for I/O routines.</li>
  649. <li>Commits in <a href="https://github.com/perl6/doc">Perl 6 Documentation</a>
  650. providing full coverage for undocumented I/O routines, as well as any
  651. corrections for existing I/O documentation.</li>
  652. <li>Bonus deliverable: The "Map" of Rakudo Routines</li>
  653. <li>Bonus objective: whenever possible, I intend to fix any of the bugs
  654. found by the new test coverage. Should a bug prove to be hard to fix,
  655. the test exposing it will be fudged and a ticket for the bug will be filed.</li>
  656. </ul>
  657.  
  658. <h2>Project Details</h2>
  659.  
  660. <ul>
  661. <li>(Bonus deliverable): <strong>The "Map" of Rakudo Routines</strong>
  662. This will be semi-automatically generated (by introspection) list of all
  663. subroutines and publicly accessible object methods provided by Rakudo
  664. implementation, together with information on what calling convention they
  665. use and how they fail (e.g. returning some object, throwing, or returning
  666. a <code>Failure</code> object). This data will guide the decision on how the calling convetion/failure mode for I/O routines should be standardized. I intend
  667. to work on this deliverable while this grant proposal is deliberated. As
  668. such, it's a bonus deliverable and will be completed regardless of whether
  669. this grant is approved.</li>
  670. <li><strong>I/O Action Plan Report</strong>
  671. This will be a Markdown document detailing how the existing routines will
  672. change, what the new routines will do, if any are to be added, and whether
  673. any currently unspecced routines are to be removed. Parts of this document
  674. will eventually be re-used as documention for currently undocumented
  675. routines.
  676. <ul>
  677. <li>The scope of all of the changes will be limited by the <em>6.c</em> Perl 6
  678. language specification, so none of the changes would have to be deferred
  679. until <em>6.d</em> language release.</li>
  680. <li>This document will be placed into
  681. <a href="https://github.com/rakudo/rakudo/">rakudo</a> repository when ready and
  682. other core developers will be asked to reivew it and make comments on the
  683. proposed changes.</li>
  684. </ul></li>
  685. <li><strong>Commits</strong>
  686. The commits to rakudo/roast/doc repositories will implement changes in
  687. the Action Plan, and test and document any I/O routines that are still
  688. left untested/undocumented after those changes.</li>
  689. </ul>
  690.  
  691. <h2>Inch-stones</h2>
  692.  
  693. <p>These are the inch-stones I intend to follow:</p>
  694.  
  695. <h3>Routine Map</h3>
  696.  
  697. <ul>
  698. <li>Use Perl 6's introspection facilities to locate core subroutines and
  699. classes in <code>CORE::</code> lexical scope. Further introspect those classes to obtain
  700. <code>Method</code> objects. Further introspect the candidates and signatures of all of
  701. these routines to obtain the calling convention list (e.g. we pass arguments
  702. as adverbs or as positionals, etc)</li>
  703. <li>Further introspect the arguments and programmatically invoke the
  704. routines with some probably-acceptable values to obtain the output range, in
  705. particular failure modes. Some heuristics or manual massaging will be needed
  706. here.</li>
  707. <li>Part of this work already exists in <a href="https://github.com/zoffixznet/perl6-map">a repo</a>. If the grant is approved, this repository will be
  708. transfered to <a href="https://github.com/perl6/">Perl 6 GitHub organization</a></li>
  709. </ul>
  710.  
  711. <h3>I/O Action Plan Report</h3>
  712.  
  713. <ul>
  714. <li>Using the routine map, figure out a better interface for I/O routines
  715. and then see what can be changed without breaking the 6.c language spec. Even
  716. without that map, I already can see some targets for change: the routines that
  717. take <code>$test</code> named arg as a predefined string of test letters in particular
  718. order, as well as the inconsistency that most methods <code>fail()</code> while most
  719. subroutines <code>throw()</code>. Based on a brief <a href="https://irclog.perlgeek.de/perl6-dev/2016-12-28#i_13814034">conversation with
  720. Larry Wall</a>, the
  721. likely change would be to make all of them consistently <code>fail()</code>.</li>
  722. <li>Inspect the <a href="https://github.com/rakudo/rakudo/compare/6bbb56f4c598ba0fef49ba9b11671df675019366...newio">code of NewIO branch</a>
  723. for any ideas that can be salvaged for 6.c Language. The work in this branch
  724. was created by lizmat++ in 2014-2015, but due to unfortunate circumstances
  725. never got merged to master prior to 6.c release. My understanding is it offers
  726. a lot of improvements to our current IO, but based on brief perusal of the
  727. code, I suspect it would have a lot of conflict with 6.c Language
  728. Specification tests. Under this grant, I would like to see if any of the
  729. improvements that work offers can be applied to current 6.c language.</li>
  730. <li>Using the <a href="http://perl6.party/post/Perl-6-Core-Hacking-Can-Has-Moar-Cover">MoarVM coverage report
  731. tool</a> (and by
  732. grepping the <a href="https://github.com/perl6/roast/">roast repo</a>), find
  733. routines that are entirely unspecced and decide whether they
  734. should stay or be removed. For example, the currently unspecced <code>indir()</code>
  735. routine is a likely candidate for staying, while I've seen some calls on IRC
  736. to remove the unspecced <code>tmpdir()</code>.</li>
  737. <li>I forcee the largest part of this grant work to be the writing of
  738. the tests. Here are some examples of the rough current coverage state of IO
  739. routines:
  740. <a href="http://perl6.wtf/src_core_io_operators.pm.coverage.html">src/core/io_operators.pm</a>,
  741. <a href="http://perl6.wtf/src_core_IO_ArgFiles.pm.coverage.html">IO::Argfiles</a>,
  742. <a href="http://perl6.wtf/src_core_IO_Special.pm.coverage.html">IO::Special</a>,
  743. <a href="http://perl6.wtf/src_core_IO_Spec_Win32.pm.coverage.html">IO::Spec::Win32</a>,
  744. and <a href="http://perl6.wtf/src_core_IO_Handle.pm.coverage.html">IO::Handle</a>. The
  745. routines whose names are on red lines indicate they're untested in roast
  746. (this report was generated on Oct 7 and as I recall only IO::ArgFiles.lines and
  747. IO::Handle.seek received any further tests since then).</li>
  748. <li>A lot of the decisions made by the Action Plan will be able to close
  749. many of the tickets opened by <em>brian d foy</em> while gathering info on our
  750. I/O routines that is going to be included in <em>Learning Perl 6</em> book and the
  751. concerns raised in the tickets will be used as input for the Action Plan as
  752. well. (Some of them are:
  753. <a href="https://rt.perl.org/Public/Bug/Display.html?id=130460">RT#130460</a>,
  754. <a href="https://rt.perl.org/Public/Bug/Display.html?id=130456">RT#130456</a>,
  755. <a href="https://rt.perl.org/Public/Bug/Display.html?id=130454">RT#130454</a>,
  756. <a href="https://rt.perl.org/Public/Bug/Display.html?id=130455">RT#130455</a>,
  757. <a href="https://rt.perl.org/Public/Bug/Display.html?id=130489">RT#130489</a>,
  758. <a href="https://rt.perl.org/Public/Bug/Display.html?id=130490">RT#130490</a>).</li>
  759. <li>Write down the action plan in Markdown format, make it available
  760. in Rakudo repository, and invite other core members in <code>#perl6-dev</code> IRC
  761. channel to comment on it.</li>
  762. <li>After a 1 week review period, update the Action Plan to reflect
  763. any received feedback, and proceed to implement it.</li>
  764. </ul>
  765.  
  766. <h3>Commits</h3>
  767.  
  768. <p>The commits will implement the Action Plan. Roast commits will be based on
  769. the changes to routines as well as the report generated by the coverage tool.
  770. And the doc commits will be done by manually searching and reading exiting
  771. documentation and amending it as needed.</p>
  772.  
  773. <p>(N.B.: I'm aware the coverage tool is currently busted by a commit that changed
  774. filenames in <code>.file</code> method for core routines; however MasterDuke++ promised
  775. to fix it, and if they won't be able to find time to do so, the fix should be
  776. simple enough that I'd fix the tool myself).</p>
  777.  
  778. <h2>Project Schedule</h2>
  779.  
  780. <p>I already began work on the routine map generator and will complete it by
  781. the time the decision on this grant proposal is available. After that,
  782. I expect to spend 2 weeks preparing the I/O Action Plan Report, 1 week for its
  783. review by other core members, and 2 weeks for its full implementation
  784. (including tests and docs). I also allow for extra 2 weeks for any unforseen
  785. delays in any of the steps.</p>
  786.  
  787. <p>If my understanding of <a href="http://news.perlfoundation.org/2017/01/call-for-grant-proposals-jan-2.html">the date when the decision on this grant would be
  788. ready</a> is correct, I intend to finish the work before the end of March, 2017.</p>
  789.  
  790. <h2>Completeness Criteria</h2>
  791.  
  792. <ul>
  793. <li><a href="https://github.com/rakudo/rakudo/tree/nom/docs">rakudo repository</a>
  794. will contain the IO Action Plan document and it will be fully implemented.</li>
  795. <li>All of the I/O routines will have tests in
  796. <a href="https://github.com/perl6/roast/">roast</a> and documented on
  797. <a href="https://docs.perl6.org">docs.perl6.org</a>. If any of the currently implemented
  798. but unspecced routines are decided against being included in Perl 6 Language,
  799. their implementation will no longer be available in Rakudo.</li>
  800. <li>The test coverage tool will report all I/O routines as covered and
  801. the information will be visible on <a href="http://perl6.wtf">perl6.wtf</a> (<em>Perl 6's
  802. Wonderful Test Files</em>) website. Note: due to current experimental status of the
  803. coverage tool, its report may still show some lines or conditionals untested
  804. despite them actually being tested; however, it <em>will</em> show the lines where
  805. routines' names are specified as covered.</li>
  806. </ul>
  807.  
  808. <h2>Sidenote Comments</h2>
  809.  
  810. <p>The grant amount requested may be low compared to the described amount of work
  811. because I'd like to still view part of my time on this work as donated to
  812. Perl 6. Those who see me on IRC may notice I bounced around the ideas in this
  813. proposal before.</p>
  814.  
  815. <p>The grant will let me finish this work much sooner and in a more complete
  816. state than I would be able to otherwise.</p>
  817.  
  818. <h2>Bio</h2>
  819.  
  820. <p>I'm a 30-year old Canadian who lived near Toronto for the past 14 years.
  821. I also spent some years of my life living in USA (New Jersey) and, before that,
  822. in Russia (Siberia), where I was born.</p>
  823.  
  824. <p>I started with Perl 5 about 12 years ago and have since released over
  825. 200 Perl 5 modules on CPAN and for the last 10 years held a single job,
  826. large part of which is web development with Perl 5.</p>
  827.  
  828. <p>In the fall of 2015, I switched my focus to Perl 6 and to date released 34
  829. Perl 6 modules and delivered a couple of Perl 6 presentations at the Toronto
  830. Perl Mongers meetings.</p>
  831.  
  832. <p>Around July, 2016 I joined the Rakudo Perl 6 Core Development Team. I also have
  833. been Rakudo's release manager every month since the 2016.06 release.</p>
  834.  
  835. <p>My notable deliverables to the Perl 6 Community involve the creation of the
  836. web app driving <a href="https://modules.perl6.org">modules.perl6.org</a>; nearly total
  837. automation of the Rakudo's release process, including the development of
  838. <a href="http://perl6.fail">perl6.fail</a> web app for RT interfacing and release status
  839. tracking; and writing all of the tutorials on
  840. <a href="http://perl6.party">perl6.party</a> website.</p>
  841.  
  842. <p>To date, I have authored <strong>461 commits</strong> to
  843. <a href="https://github.com/rakudo/rakudo/">Rakudo</a> and <strong>1,823 commits</strong> to
  844. repositories in <a href="https://github.com/perl6/">Perl 6 GitHub organization</a>
  845. (<strong>523</strong> of which have been to the
  846. <a href="https://github.com/perl6/roast/">Perl 6 Specification</a> repository).</p>
  847. ]]>
  848.    </content>
  849. </entry>
  850.  
  851. <entry>
  852.    <title>Maintaining the Perl 5 Core: December 2016 report</title>
  853.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/maintaining-the-perl-5-core-de.html" />
  854.    <id>tag:news.perlfoundation.org,2017://18.3842</id>
  855.  
  856.    <published>2017-01-17T14:00:00Z</published>
  857.    <updated>2017-01-20T07:19:29Z</updated>
  858.  
  859.    <summary><![CDATA[Dave Mitchell writes: I spent December: 1) looking for quick some wins on speeding up perl compile-time, using 'perl -MCPAN -e1' as a typical example of loading and compiling several .pm files. I tweaked Perl_yyparse() and shaved ~2% off the compile time; then tweaked Perl_sv_gets() and shaved another ~2% off, and also got a pleasing run-time boost for line reading, with reading a big list of words now ~8% faster on my system: perl -e'$i++ while (&lt;>)' /usr/share/dict/words 2) investigating...]]></summary>
  860.    <author>
  861.        <name>Makoto Nozaki</name>
  862.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  863.    </author>
  864.    
  865.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  866.    
  867.        <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category" />
  868.    
  869.    
  870.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  871.        <![CDATA[<p><em>Dave Mitchell writes:</em></p>
  872.  
  873. <pre>
  874. I spent December:
  875.  
  876. 1) looking for quick some wins on speeding up perl compile-time, using
  877. 'perl -MCPAN -e1' as a typical example of loading and compiling several
  878. .pm files.  I tweaked Perl_yyparse() and shaved ~2% off the compile time;
  879. then tweaked Perl_sv_gets() and shaved another ~2% off, and also got a
  880. pleasing run-time boost for line reading, with reading a big list of words
  881. now ~8% faster on my system:
  882.  
  883.    perl -e'$i++ while (<>)' /usr/share/dict/words
  884.  
  885. 2) investigating possible ways of making the regex engine faster by (in
  886. some cases) processing 8 bytes at a time on 64-bit platforms. This
  887. culminated in an this email thread:
  888.  
  889.    http://nntp.perl.org/group/perl.perl5.porters/241891
  890.  
  891. 3) as usual, working on a few miscellaneous tickets.
  892.  
  893. SUMMARY:
  894.      1:30 RT #130385 Bleadperl breaks DNS-LDNS
  895.      1:00 RT #130385 Bleadperl breaks List-Pairwise
  896.      1:00 RT #130398 Bleadperl breaks Method-Signatures
  897.      4:26 [perl #129199] Difficult-to-trigger panic
  898.      1:01 [perl #130247] Perl_rpeep(OP *): Assertion `oldop' failed
  899.      0:55 [perl #130307] Bug: Regex matches when it shouldn't
  900.      0:33 [perl #130311] heap-buffer-overflow Perl_yyparse
  901.      0:55 fix build warnings and smoke failures
  902.      1:40 fix some CPAN modules under PERL_OP_PARENT
  903.     19:00 investigate making find_by_class faster()
  904.      2:37 optimise Perl_sv_gets()
  905.      4:45 optimise Perl_yyparse()
  906.     12:20 process p5p mailbox
  907.      3:22 review RT tickets
  908.      3:04 review security tickets
  909.    ------
  910.     58:08 TOTAL (HH::MM)
  911.  
  912. 170.1 weeks
  913. 2338.8 total hours
  914.  13.7 average hours per week
  915.  
  916. There are 61 hours left on the grant
  917.  
  918. </pre>
  919. ]]>
  920.        
  921.    </content>
  922. </entry>
  923.  
  924. <entry>
  925.    <title>Grant Extension Request: Maintaining the Perl 5 Core</title>
  926.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/grant-extension-request-mainta-2.html" />
  927.    <id>tag:news.perlfoundation.org,2017://18.3841</id>
  928.  
  929.    <published>2017-01-10T22:00:01Z</published>
  930.    <updated>2017-01-12T15:20:39Z</updated>
  931.  
  932.    <summary>Dave Mitchell has requested an extension of $20,000 for his Maintaining the Perl 5 Core grant. This will allow him to dedicate another 400 hours to this work. During this grant he sent regular reports to the p5p mailing list as well as providing monthly summary reports that have been published on this site, the most recent of which are linked below: Month 35 Month 36 Oct/Nov Before we make a decision on this extension, we would like to have...</summary>
  933.    <author>
  934.        <name>Makoto Nozaki</name>
  935.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  936.    </author>
  937.    
  938.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  939.    
  940.    
  941.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  942.        <![CDATA[<p><strong>Dave Mitchell</strong> has requested an extension of $20,000 for his <strong>Maintaining the Perl 5 Core</strong> grant. This will allow him to dedicate another 400 hours to this work. During this grant he sent regular reports to the p5p mailing list as well as providing monthly summary reports that have been published on this site, the most recent of which are linked below:</p>
  943.  
  944. <ul>
  945. <li><a href="http://news.perlfoundation.org/2016/09/maintaining-the-perl-5-core-re-31.html">Month 35</a></li>
  946. <li><a href="http://news.perlfoundation.org/2016/10/maintaining-the-perl-5-core-re-32.html">Month 36</a></li>
  947. <li><a href="http://news.perlfoundation.org/2017/01/maintaining-the-perl-5-core-oc.html">Oct/Nov</a></li>
  948. </ul>
  949.  
  950. <p>Before we make a decision on this extension, we would like to have a period of community consultation. Please leave feedback in the comments field below or if you prefer, send email with your comments to makoto at perlfoundation.org. We request that all the feedback should be sent by January 15th.</p>
  951.  
  952. <p>If successful this extension will be funded from the <a href="http://www.perlfoundation.org/perl_5_core_maintenance_fund">Perl 5 Core Maintenance Fund</a>.</p>
  953. ]]>
  954.        
  955.    </content>
  956. </entry>
  957.  
  958. <entry>
  959.    <title>Maintaining the Perl 5 Core: October / November 2016 report</title>
  960.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/maintaining-the-perl-5-core-oc.html" />
  961.    <id>tag:news.perlfoundation.org,2017://18.3840</id>
  962.  
  963.    <published>2017-01-09T22:00:00Z</published>
  964.    <updated>2017-01-10T03:32:21Z</updated>
  965.  
  966.    <summary>Dave Mitchell writes: I spent last the last two months: * reworking list assignment (especially with an aggregate on the LHS) to be much faster in many cases. For example, this code is 33% faster in 5.25.7 compared with 5.24.0: my @a; for my $i (1..10_000_000) { @a = (1,2,3); @a = (); } * trying to reduce the overhead of compile time a bit; * freeing up some uses of SV flags; * fixing various assorted bugs as listed...</summary>
  967.    <author>
  968.        <name>Makoto Nozaki</name>
  969.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  970.    </author>
  971.    
  972.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  973.    
  974.    
  975.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  976.        <![CDATA[<p><em>Dave Mitchell writes:</em></p>
  977.  
  978. <pre>
  979. I spent last the last two months:
  980.  
  981. * reworking list assignment (especially with an aggregate on the LHS) to
  982.  be much faster in many cases. For example, this code is 33% faster in
  983.  5.25.7 compared with 5.24.0:
  984.  
  985.    my @a;
  986.    for my $i (1..10_000_000) {
  987.        @a = (1,2,3);
  988.        @a = ();
  989.    }
  990.  
  991. * trying to reduce the overhead of compile time a bit;
  992.  
  993. * freeing up some uses of SV flags;
  994.  
  995. * fixing various assorted bugs as listed below;
  996.  
  997. SUMMARY:
  998.     59:16 [perl #127999] Slowdown in split + list assign
  999.      8:28 [perl #129140] attempting double-free Perl_safesysfree util.c:388
  1000.      0:23 [perl #129771] %+ not scoped properly
  1001.      0:16 [perl #129802] Regexp performance problem with swiped strings (?)
  1002.      1:13 [perl #129821] Bleadperl v5.25.5-65-g5012eeb breaks JJORE/Devel-OptreeDiff-2.3.tar.gz
  1003.      3:01 [perl #129825] Overloaded integer constants are prematurely deallocated
  1004.      0:34 [perl #129950] Some UTF-8 regular expression matches fail when read from file
  1005.      0:10 [perl #129954] dist/Carp/t/arg_string.t: Test fails in blead
  1006.      3:51 [perl #129991] Assertion failure in S_aassign_copy_common
  1007.      7:23 [perl #129996] BBC Devel-SearchINC
  1008.      4:01 [perl #129997] heap-use-after-free sv_catpvn_flags() within Perl_do_vop
  1009.      8:44 [perl #130132] Bleadperl breaks Date-Manip
  1010.      1:27 [perl #130188] crash on return from substitution in subroutine
  1011.      8:00 eliminate some ugly SV flag usages
  1012.      1:00 fix build warnings and smoke failures
  1013.      2:30 miscellaneous fixups
  1014.      2:09 optimise undef assignment
  1015.     13:36 performance of keywords.c
  1016.      7:33 process p5p mailbox
  1017.      1:00 review security tickets
  1018.      1:40 split to an array creating RO elements
  1019.    ------
  1020.    136:15 TOTAL (HH::MM)
  1021.  
  1022. 163.4 weeks
  1023. 2243.6 total hours
  1024.  13.7 average hours per week
  1025.  
  1026. There are 156 hours left on the grant
  1027. </pre>
  1028.  
  1029. <p><em>Note: This report was sent in December and signed off by Marcus Holland-Moritz on Jan 6th.</em></p>
  1030. ]]>
  1031.        
  1032.    </content>
  1033. </entry>
  1034.  
  1035. <entry>
  1036.    <title>TPF Grant Nov/Dec 2016 Round Results</title>
  1037.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/tpf-grant-novemberdecember-rou.html" />
  1038.    <id>tag:news.perlfoundation.org,2017://18.3839</id>
  1039.  
  1040.    <published>2017-01-09T21:00:00Z</published>
  1041.    <updated>2017-01-10T03:33:39Z</updated>
  1042.  
  1043.    <summary>Grant Proposal: Learning Perl 6, a book from O&apos;Reilly Media At the invitation of the TPF board, brian has withdrawn the grant proposal for the Learning Perl 6 book, and will submit a proposal to TPF on other ways for TPF to participate in enhancing the visibility of Perl 6. The Grants Committee had a general discussion on funding activities whose output is not free of charge. TPF has documentation that states grant results must be &quot;released under a publically...</summary>
  1044.    <author>
  1045.        <name>Makoto Nozaki</name>
  1046.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  1047.    </author>
  1048.    
  1049.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  1050.    
  1051.    
  1052.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  1053.        <![CDATA[<p><a href="http://news.perlfoundation.org/2016/12/grant-proposal-learning-perl-6.html">Grant Proposal: Learning Perl 6, a book from O'Reilly Media</a></p>
  1054.  
  1055. <p>At the invitation of the TPF board, brian has withdrawn the grant
  1056. proposal for the Learning Perl 6 book, and will submit a proposal to
  1057. TPF on other ways for TPF to participate in enhancing the visibility
  1058. of Perl 6.</p>
  1059.  
  1060. <p>The Grants Committee had a general discussion on funding activities
  1061. whose output is not free of charge. TPF has documentation that states
  1062. grant results must be "released under a publically available license
  1063. that is free for redistribution and use without discrimination against
  1064. field of endeavour" (from the "Grant Benefits" page), but the process of
  1065. reviewing this proposal revealed that the documentation was easy to miss
  1066. and not clearly stated as policy in the Grants Committee rules of
  1067. operation. The committee unanimously agreed to update the rules to make
  1068. it clear that all grant results should be available free of charge. We
  1069. are in the process of adding such a clause to the rules of operation soon
  1070. (wording may be slightly changed):</p>
  1071.  
  1072. <p>1.3. Grant proposals should mention how the grant results will be made
  1073. available to the public. The grant results must be must be accessible
  1074. free of charge.</p>
  1075. ]]>
  1076.        
  1077.    </content>
  1078. </entry>
  1079.  
  1080. <entry>
  1081.    <title>Grant Report: Test2 Manual</title>
  1082.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/grant-report-test2-manual-2.html" />
  1083.    <id>tag:news.perlfoundation.org,2017://18.3838</id>
  1084.  
  1085.    <published>2017-01-08T14:58:17Z</published>
  1086.    <updated>2017-01-08T15:03:45Z</updated>
  1087.  
  1088.    <summary>Chad Granun reports on his work on the Test2 Manual grant. The last month was devoted to: How to list the test tools in the modules dependencies; Tutorial for TODO tests; Tutorial for advanced test planning....</summary>
  1089.    <author>
  1090.        <name>Alberto Simões</name>
  1091.        <uri>http://blogs.perl.org/users/alberto_simoes/</uri>
  1092.    </author>
  1093.    
  1094.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  1095.    
  1096.    <category term="grants" label="grants" scheme="http://www.sixapart.com/ns/types#tag" />
  1097.    
  1098.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  1099.        <![CDATA[<p>Chad Granun reports on his work on the Test2 Manual grant. The last month was devoted to:</p>
  1100.  
  1101. <ul>
  1102. <li>How to list the test tools in the modules dependencies;</li>
  1103. <li>Tutorial for TODO tests;</li>
  1104. <li>Tutorial for advanced test planning.</li>
  1105. </ul>
  1106. ]]>
  1107.        
  1108.    </content>
  1109. </entry>
  1110.  
  1111. <entry>
  1112.    <title>Call For Grant Proposals (Jan 2017 Round)</title>
  1113.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/call-for-grant-proposals-jan-2.html" />
  1114.    <id>tag:news.perlfoundation.org,2017://18.3837</id>
  1115.  
  1116.    <published>2017-01-05T22:00:00Z</published>
  1117.    <updated>2017-01-06T03:00:32Z</updated>
  1118.  
  1119.    <summary>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 January 15th UTC. We will publish the received applications, get community feedback and conclude acceptance by January 25th. To apply, please read How to Write a Proposal. Rules of...</summary>
  1120.    <author>
  1121.        <name>Makoto Nozaki</name>
  1122.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  1123.    </author>
  1124.    
  1125.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  1126.    
  1127.    
  1128.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  1129.        <![CDATA[<p>The Grants Committee is accepting grant proposals all the time.  We evaluate them every two months and another evaluation period has come.</p>
  1130.  
  1131. <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 January 15th UTC.</strong> We will publish the received applications, get community feedback and conclude acceptance by January 25th.</p>
  1132.  
  1133. <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> and <a href="http://www.perlfoundation.org/running_grants">Running Grants List</a> will also help you understand how the grant process works. We also got some <a href="http://www.perlfoundation.org/grant_ideas">grant ideas</a> from the community. The format is the same as the previous rounds in 2014-2016.</p>
  1134.  
  1135. <p>We will confirm the receipt of application within 24 hours.</p>
  1136.  
  1137. <p>If you have further questions, please contact me at tpf-grants-secretary at perl-foundation.org.</p>
  1138. ]]>
  1139.        
  1140.    </content>
  1141. </entry>
  1142.  
  1143. <entry>
  1144.    <title>TPF 2016Q4 Activity Report</title>
  1145.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/12/tpf-2016q4-activity-report.html" />
  1146.    <id>tag:news.perlfoundation.org,2016://18.3836</id>
  1147.  
  1148.    <published>2016-12-27T23:00:00Z</published>
  1149.    <updated>2016-12-28T04:44:58Z</updated>
  1150.  
  1151.    <summary>General White Camels Awards winners have been annouonced. TPF will take part in Outreachy. Conferences Perl Conference NA 2017 will be held June 18th through June 23rd in Alexandria, Virginia. Grants Updates Maintaining Perl 5: November | August Maintaining Perl 5 Core: October | September JavaScript Backend For Rakudo: October RPerl User Documentation: December | October blogs.perl.org Rewrite: November Test2 Manual: November | October Start Act - Voyager: No update Proposal Learning Perl 6 book: Pending Grant Extension Maintaining Perl...</summary>
  1152.    <author>
  1153.        <name>Makoto Nozaki</name>
  1154.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  1155.    </author>
  1156.    
  1157.        <category term="Perl Foundation" scheme="http://www.sixapart.com/ns/types#category" />
  1158.    
  1159.    
  1160.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  1161.        <![CDATA[<h3>General</h3>
  1162.  
  1163. <ul>
  1164. <li><a href="http://blogs.perl.org/users/brian_d_foy/2016/12/white-camels-2016.html">White Camels Awards</a> winners have been annouonced.</li>
  1165. <li>TPF will <a href="http://news.perlfoundation.org/2016/09/taking-part-in-outreachy-1.html">take part in</a> <a href="https://www.gnome.org/outreachy/">Outreachy</a>.</li>
  1166. </ul>
  1167.  
  1168. <h3>Conferences</h3>
  1169.  
  1170. <ul>
  1171. <li><a href="http://news.perlfoundation.org/2016/11/the-perl-conference-save-date-2017.html">Perl Conference NA 2017</a> will be held June 18th through June 23rd in Alexandria, Virginia.</li>
  1172. </ul>
  1173.  
  1174. <h3>Grants</h3>
  1175.  
  1176. <ul>
  1177. <li>Updates
  1178. <ul>
  1179. <li>Maintaining Perl 5: <a href="http://news.perlfoundation.org/2016/12/maintaining-perl-5-grant-repor-35.html">November</a> | <a href="http://news.perlfoundation.org/2016/10/maintaining-perl-5-grant-repor-33.html">August</a></li>
  1180. <li>Maintaining Perl 5 Core: <a href="http://news.perlfoundation.org/2016/10/maintaining-the-perl-5-core-re-32.html">October</a> | <a href="http://news.perlfoundation.org/2016/09/maintaining-the-perl-5-core-re-31.html">September</a></li>
  1181. <li>JavaScript Backend For Rakudo: <a href="http://news.perlfoundation.org/2016/10/update-on-javascript-backend-f.html">October</a></li>
  1182. <li>RPerl User Documentation: <a href="http://news.perlfoundation.org/2016/12/grant-report-rperl-user-docume-11.html">December</a> | <a href="http://news.perlfoundation.org/2016/10/grant-report-rperl-user-docume-10.html">October</a></li>
  1183. <li>blogs.perl.org Rewrite: <a href="http://news.perlfoundation.org/2016/11/public-beta-of-blogsperlorg-re.html">November</a></li>
  1184. <li>Test2 Manual: <a href="http://news.perlfoundation.org/2016/11/grant-report-test2-manual-1.html">November</a> | <a href="http://news.perlfoundation.org/2016/10/grant-report-test2-manual.html">October</a></li>
  1185. <li>Start Act - Voyager: No update</li>
  1186. </ul></li>
  1187. <li>Proposal
  1188. <ul>
  1189. <li><a href="http://news.perlfoundation.org/2016/12/grant-proposal-learning-perl-6.html">Learning Perl 6 book</a>: Pending</li>
  1190. </ul></li>
  1191. <li>Grant Extension
  1192. <ul>
  1193. <li><a href="http://news.perlfoundation.org/2016/10/tony-cooks-grant-extended-1.html">Maintaining Perl 5 Extension</a>: Approved</li>
  1194. </ul></li>
  1195. </ul>
  1196.  
  1197. <h3>People On The Move</h3>
  1198.  
  1199. <ul>
  1200. <li>Karen Pauley has stepped down as TPF President and Jim Brandt has assumed the the new President role (<a href="http://news.perlfoundation.org/2016/11/tpf-president-change.html">details</a>).</li>
  1201. </ul>
  1202.  
  1203. <p><em>Is this report useful? We welcome your feedback. Contact: makoto at perlfoundation.org</em></p>
  1204. ]]>
  1205.        
  1206.    </content>
  1207. </entry>
  1208.  
  1209. </feed>
  1210.  

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://www.feedvalidator.org/check.cgi?url=http%3A//news.perlfoundation.org/atom.xml

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