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-03-24T01:15:34Z</updated>
  8.    
  9.    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 6.2.2</generator>
  10.  
  11. <entry>
  12.    <title>Call for Grant Proposals (March 2017 Round)</title>
  13.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/03/call-for-grant-proposals-march-2.html" />
  14.    <id>tag:news.perlfoundation.org,2017://18.3858</id>
  15.  
  16.    <published>2017-03-24T01:10:02Z</published>
  17.    <updated>2017-03-24T01:15:34Z</updated>
  18.  
  19.    <summary></summary>
  20.    <author>
  21.        <name>Coke</name>
  22.        
  23.    </author>
  24.    
  25.    
  26.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  27.        
  28.        <![CDATA[<p>The Grants Committee is accepting grant proposals all the time.
  29. We evaluate them every two months and another evaluation period has come. This month's round is a little later than usual, due to the selection of
  30. a new GC Secretary (myself). This round will be slightly compressed, and we'll strive to get back on track for the next round.</p>
  31.  
  32. <p>If you have an idea for doing some Perl work that will benefit the Perl
  33. community, consider sending a grant application. <strong>The application deadline
  34. for this round is 23:59 April 2nd UTC.</strong> We will publish the received applications, get community
  35. feedback and conclude acceptance by April 12th.</p>
  36.  
  37. <p>To apply, please read <a href="http://www.perlfoundation.org/how_to_write_a_proposal">How
  38. to Write a Proposal</a>. <a href="http://www.perlfoundation.org/rules_of_operation">Rules of
  39. 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>
  40.  
  41. <p>We will confirm the receipt of application within 24 hours.</p>
  42.  
  43. <p>If you have further questions, please contact me at tpf-grants-secretary at perl-foundation.org.</p>
  44. ]]>
  45.    </content>
  46. </entry>
  47.  
  48. <entry>
  49.    <title>New Grant Committee Member &amp; Secretary</title>
  50.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/03/new-grant-committee-member-sec.html" />
  51.    <id>tag:news.perlfoundation.org,2017://18.3857</id>
  52.  
  53.    <published>2017-03-24T00:51:07Z</published>
  54.    <updated>2017-03-24T01:00:05Z</updated>
  55.  
  56.    <summary>Please join me in welcoming John SJ Anderson (genehack) as the newest voting member of The Perl Foundation&apos;s Grants Committee. John has helped organize several recent YAPCs, given talks and training at YAPCs, and maintains several modules on CPAN. Additionally, as Makoto Nozaki is transitioning to the secretary of the TPF Board, he is vacating the position of GC Secretary, and I have been selected to to fill the role. My apologies for the delays in the transition. Look for...</summary>
  57.    <author>
  58.        <name>Coke</name>
  59.        
  60.    </author>
  61.    
  62.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  63.    
  64.    
  65.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  66.        <![CDATA[<p>Please join me in welcoming John SJ Anderson (genehack) as the newest voting member
  67. of The Perl Foundation's Grants Committee. John has helped organize several recent YAPCs,
  68. given talks and training at YAPCs, and maintains several modules on CPAN.</p>
  69.  
  70. <p>Additionally, as Makoto Nozaki is transitioning to the secretary of the TPF Board,
  71. he is vacating the position of GC Secretary, and I have been selected to
  72. to fill the role.</p>
  73.  
  74. <p>My apologies for the delays in the transition. Look for a posting shortly about
  75. the March call for proposals.</p>
  76. ]]>
  77.        
  78.    </content>
  79. </entry>
  80.  
  81. <entry>
  82.    <title>Perl 6 IO Grant: February 2017 Report</title>
  83.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/03/perl-6-io-grant-february-2017-.html" />
  84.    <id>tag:news.perlfoundation.org,2017://18.3856</id>
  85.  
  86.    <published>2017-03-24T00:20:35Z</published>
  87.    <updated>2017-03-24T00:39:56Z</updated>
  88.  
  89.    <summary></summary>
  90.    <author>
  91.        <name>Coke</name>
  92.        
  93.    </author>
  94.    
  95.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  96.    
  97.        <category term="Perl 6 Development" scheme="http://www.sixapart.com/ns/types#category" />
  98.    
  99.    
  100.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  101.        
  102.        <![CDATA[<p><i>Zoffix Znet provided this report on February 26, 2016</i></p>
  103.  
  104. <hr>
  105.                            <p>This document is the February, 2017 progress report for <a href="http://news.perlfoundation.org/2017/01/grant-proposal-standardization.html">TPF Standardization,
  106. Test Coverage, and Documentation of Perl 6 I/O Routines
  107. grant</a></p>
  108.  
  109. <h2>Timing</h2>
  110.  
  111. <p>I'm currently running slightly behind the schedule outlined in the grant. I expect to complete the Action Plan and have it ratified by other core members by March 18th, which is the date of the 2017.03 compiler release. Then, I'll implement all of the Action Plan (and complete the grant) by the 2017.04 compiler release on April 15th. This is also the release the next Rakudo Star distribution will be based on, and so the regular end users will receive better IO there and then.</p>
  112.  
  113. <p>Some members of the Core Team voiced concerns over implementing any changes that can break users' code, even if the changes do not break 6.c-errata specification
  114. tests. Once the full set of changes is known, they will be reviewed on a
  115. case-by-case basis, and some of them may be implemented under 6.d.PREVIEW
  116. pragma, to be included in 6.d language version, leaving 6.c language versions
  117. untouched. Note that changes that are decided to be 6.d material may delay
  118. the completion of this grant due to not fully-fleshed out infrastructure for
  119. supporting multiple language versions. The April 15th deadline stated above
  120. applies only to changes to 6.c language and new deadline will be ascertained
  121. for completion of the 6.d changes.</p>
  122.  
  123. <h2>User Communications</h2>
  124.  
  125. <p>I wrote and disseminated advanced notice of the changes to be made due to this grant, to prepare the users to expect some code to break (some routines were found to be documented, despite being absent entirely from the <a href="https://github.com/perl6/roast/tree/6.c-errata">Specification</a> and not officially part of the language).</p>
  126.  
  127. <p>The notice can be seen at: <a href="http://rakudo.org/2017/02/26/advance-notice-of-significant-changes/">http://rakudo.org/2017/02/26/advance-notice-of-significant-changes/
  128.    </a></p>
  129.  
  130. <p>It is possible the Core Team will decide to defer all breaking changes to
  131. 6.d language version, to be currently implemented under <code class="prettyprint">v6.d.PREVIEW</code> pragma.</p>
  132.  
  133. <h2>Bonus Deliverable</h2>
  134.  
  135. <p>The bonus deliverable—The Map of Perl 6 Routines—is now usable. The code is available in <a href="https://github.com/perl6/routine-map">perl6/routine-map</a> repository, and the rendered version is available on <a href="https://map.perl6.party">map.perl6.party</a>. Its current state is sufficient
  136. to serve the intended purpose for this grant, but I'll certainly add improvements to it sometime in the future, such as linking to docs, linking to routines' source code, having an IRC bot looking stuff up in it, etc.</p>
  137.  
  138. <p>It'll also be fairy easy to use the Map to detect undocumented routines or ones that are documented under the incorrect type.</p>
  139.  
  140. <h2>Identified Issues/Deficiencies with IO Routines</h2>
  141.  
  142. <p>These points, issues, and ideas were identified this month and will be included for consideration in the Action Plan.</p>
  143.  
  144. <ul>
  145. <li>Calling practically any method on a closed IO::Handle results in an LTA (Less Than Awesome)
  146. error message that reads <code class="prettyprint">&lt;something&gt; requires an object with REPR MVMOSHandle</code> where <code class="prettyprint">&lt;something&gt;</code> is
  147. sometimes the name of the method called by the user and others is some internal method
  148. invoked indirectly. We need better errors for closed file handles; and not something that would require a
  149. <code class="prettyprint">is-fh-closed()</code> type of conditional called in all the methods, which would be a hefty
  150. performance hit.</li>
  151. <li>Several routines have been identified which in other languages return useful information:
  152. number of bytes actually written or current file position, whereas in Perl 6 they just
  153. return a Bool (<code class="prettyprint">.print</code>, <code class="prettyprint">.say</code>, <code class="prettyprint">.write</code>) or a Mu type object (<code class="prettyprint">.seek</code>). Inconsistently,
  154. <code class="prettyprint">.printf</code> does appear to return the number of bytes written. It should be possible
  155. to make other routines similarly useful, although I suspect some of it may have to
  156. wait until 6.d language release.</li>
  157. <li>The <code class="prettyprint">.seek</code> routine takes the seek location as one of three Enum values. Not only are they
  158. quite lengthy to type, they're globally available for no good reason and <code class="prettyprint">.seek</code> is virtually
  159. unique in using this calling convention. I will seek to standardize this routine to take
  160. mutually-exclusive named arguments instead, preferably with much shorter names, but those
  161. are yet to be bikeshed.</li>
  162. <li><code class="prettyprint">IO.umask</code> routine simply shells out to <code class="prettyprint">umask</code>. This fails terribly on OSes that don't have
  163. that command, especially since the code still tries to decode the received input as
  164. an octal string, even after the failure. Needs improvement.</li>
  165. <li><code class="prettyprint">link</code>'s implementation and documentation confuses what a "target" is. Luckily (or sadly?)
  166. there are exactly zero tests for this routine in the Perl 6 Specification, so we can
  167. change it to match the behaviour of <code class="prettyprint">ln</code> Linux command and the <code class="prettyprint">foo $existing-thing, $new-thing</code>
  168. argument order of <code class="prettyprint">move</code>, <code class="prettyprint">rename</code>, and other similar routines.</li>
  169. <li>When using <code class="prettyprint">run(:out, 'some-non-existant-command').out.slurp-rest</code>
  170. it will silently succeed and return an empty string. If possible, this
  171. should be changed to return the failure or throw at some point.</li>
  172. <li><code class="prettyprint">chdir</code>'s <code class="prettyprint">:test</code> parameter for directory permissions test is taken as a
  173. single string parameter. This makes it extremely easy to mistakenly write
  174. broken code: for example, <code class="prettyprint">"/".IO.chdir: "tmp", :test&lt;r w&gt;</code> succeeds, while
  175. <code class="prettyprint">"/".IO.chdir: "tmp", :test&lt;w r&gt;</code> fails with a misleading error message
  176. saying the directory is not readable/writable. I will propose for <code class="prettyprint">:test</code>
  177. parameter to be deprecated in favour of using multiple named arguments to
  178. indicate desired tests. By extension, similar change will be applied to
  179. <code class="prettyprint">indir</code>, <code class="prettyprint">tmpdir</code>, and <code class="prettyprint">homedir</code> routines (if they remain in the language).</li>
  180. <li><em>Documentation:</em> several inaccuracies in the documentation were found. I won't be identifying these in my reports/Action Plan, but will simply ensure the documentation matches the implementation once the Action Plan is fully implemented.</li>
  181. </ul>
  182.  
  183. <h2>Discovered Bugs</h2>
  184.  
  185. <p>The hunt for 6-legged friends has these finds so far:</p>
  186.  
  187. <h4>Will (attempt to) fix as part of the grant</h4>
  188.  
  189. <ul>
  190. <li>indir() has a race condition where the actual dir it runs in ends up being wrong.
  191. Using <code class="prettyprint">indir '/tmp/useless', { qx/rm -fr */ }</code> in one thread and backing
  192. up your precious data in another has the potential to result in some spectacular failurage.</li>
  193. <li><code class="prettyprint">perl6 -ne '@ = lines'</code> crashes after first iteration, crying about <code class="prettyprint">MVMOSHandle REPR</code>. I suspect
  194. the code is failing to follow iterator protocol somewhere and is attempting to read
  195. on an already closed handle. I expect to be able to resolve this and the related
  196. <a href="https://rt.perl.org/Ticket/Display.html?id=128047">RT#128047</a> as part of the grant.</li>
  197. <li><code class="prettyprint">.tell</code> incorrectly always returns <code class="prettyprint">0</code> on files opened in append mode</li>
  198. <li><code class="prettyprint">link</code> mixes up target and link name in its error message</li>
  199. </ul>
  200.  
  201. <h4>Don't think I will be able to fix these as part of the grant</h4>
  202.  
  203. <ul>
  204. <li><code class="prettyprint">seek()</code> with <code class="prettyprint">SeekFromCurrent</code> as location fails to seek correctly if called
  205. after <code class="prettyprint">.readchars</code>, but only on MoarVM. This appears to occur due to some sort of buffering.
  206. I filed this as <a href="https://rt.perl.org/Ticket/Display.html?id=130843">RT#130843</a>.</li>
  207. <li>On JVM, <code class="prettyprint">.readchars</code> incorrectly assumes all chars are 2 bytes long. This appears to be
  208. just a naive substitute for nqp::readcharsfh op. I filed this as
  209. <a href="https://rt.perl.org/Ticket/Display.html?id=130840">RT#130840</a>.</li>
  210. </ul>
  211.  
  212. <h4>Already Fixed</h4>
  213.  
  214. <ul>
  215. <li>While making the Routine Map, I discovered <code class="prettyprint">.WHICH</code> and <code class="prettyprint">.Str</code> methods on <code class="prettyprint">IO::Special</code> were <code class="prettyprint">only</code>
  216. methods defined only for the <code class="prettyprint">:D</code> subtype, resulting in a crash when using, say, <code class="prettyprint">infix:&lt;eqv&gt;</code>
  217. operator on the type object, instead <code class="prettyprint">Mu.WHICH</code>/<code class="prettyprint">.Str</code> candidates getting invoked.
  218. This bug was easy and I already commited fix in
  219. <a href="https://github.com/rakudo/rakudo/commit/dd4dfb14d3ccfe50dbd4b425778a005d3303edb9">radudo/dd4dfb14d3</a>
  220. and tests to cover it in
  221. <a href="https://github.com/perl6/roast/commit/63370fe0546eded34cbaa695f6d928aa3db42395">roast/63370fe054</a></li>
  222. </ul>
  223.  
  224. <h4>Auxiliary Bugs</h4>
  225.  
  226. <p>While doing the work for this grant, I also discovered some non-IO related bugs (some of which I fixed):</p>
  227.  
  228. <ul>
  229. <li><code class="prettyprint">.Bool</code>, <code class="prettyprint">.so</code>, <code class="prettyprint">.not</code>, <code class="prettyprint">.has</code>h, and <code class="prettyprint">.elems</code> on <code class="prettyprint">Baggy:U</code> crash
  230. (<a href="https://github.com/rakudo/rakudo/commit/e8af8553eae9abfe4f5cd02dcf4114c5c4877c51">fixed in e8af8553</a>)</li>
  231. <li><code class="prettyprint">.sort</code> on reified empty arrays crashes (<a href="https://rt.perl.org/Ticket/Display.html?id=130866">reported as RT#130866</a>)</li>
  232. <li>SEGV with Scalar type object in unique() (<a href="https://rt.perl.org/Ticket/Display.html?id=130852">reported as RT#130852</a>)</li>
  233. <li><code class="prettyprint">.Bool</code>, <code class="prettyprint">.so</code>, <code class="prettyprint">.not</code> and possibly others crash on <code class="prettyprint">Seq:U</code>; need to evaluate entire codebase to see where <code class="prettyprint">only</code>
  234. methods are used instead of <code class="prettyprint">multi</code>, preventing dispatch to <code class="prettyprint">Mu.*</code> candidates. (<a href="https://rt.perl.org/Ticket/Display.html?id=130867">reported as RT#130867
  235. </a>)</li>
  236. <li>Incorrect line number reported for wrong routine call when unpacking/heredocs are used (<a href="https://rt.perl.org/Ticket/Display.html?id=130862#ticket-history">reported
  237. as RT#130862</a>)</li>
  238. <li>Warnings produced by core code marked as "shouldn't happen" (<a href="https://rt.perl.org/Ticket/Display.html?id=130857#ticket-history">reported as
  239. RT#130857</a>)</li>
  240. </ul>
  241. ]]>
  242.    </content>
  243. </entry>
  244.  
  245. <entry>
  246.    <title>TPF Committee Updates</title>
  247.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/03/tpf-committee-updates.html" />
  248.    <id>tag:news.perlfoundation.org,2017://18.3855</id>
  249.  
  250.    <published>2017-03-22T09:00:00Z</published>
  251.    <updated>2017-03-27T11:06:44Z</updated>
  252.  
  253.    <summary>We&apos;ve been reviewing Perl Foundation committees over the last few months and I&apos;m happy to report some new people have stepped into committee leadership roles. David Oswald is the new conferences committee chair. This position had gone vacant for a period as TPF Treasurer Dan Wright along with others took a more active role in planning for The Perl Conference. The board is happy to once again have someone in this role to help spread the work and responsibilities. David...</summary>
  254.    <author>
  255.        <name>Jim Brandt</name>
  256.        <uri>http://breakingpositive.com</uri>
  257.    </author>
  258.    
  259.        <category term="Perl Foundation" scheme="http://www.sixapart.com/ns/types#category" />
  260.    
  261.    
  262.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  263.        <![CDATA[<p>We've been reviewing Perl Foundation committees over the last few months and I'm happy to report some new people have stepped into committee leadership roles.</p>
  264.  
  265. <p>David Oswald is the new conferences committee chair. This position had gone vacant for a period as TPF Treasurer Dan Wright along with others took a more active role in planning for The Perl Conference. The board is happy to once again have someone in this role to help spread the work and responsibilities.</p>
  266.  
  267. <p>David was one of the lead organizers of YAPC::NA 2015 in Salt Lake City. He is also on the organizing team for the <a href="https://www.openwest.org/">OpenWest</a> open source conference. We're confident David's experience will help with this year's <a href="http://www.perlconference.us/tpc-2017-dc/">Perl Conference</a> and with planning going forward.</p>
  268.  
  269. <p>Will Coleda is the new Secretary of the Grants Committee. Will has been a member of the Grants Committee since 2008, and involved with the Perl 6 community and development for over a decade. Will's selection is a great example of the cycle of involvement for a TPF member, starting as a committee member and then taking on a bigger role over time.</p>
  270.  
  271. <p>The outgoing secretary, Makoto Nozaki, has held this position since February 2014 and he will continue his work as Perl Foundation board Secretary.</p>
  272.  
  273. <p>As part of our committee review, I have also been looking into other committees that have recently been less active or inactive. As a result, the Steering Committee is being sunsetted.</p>
  274.  
  275. <p>The Steering Committee was originally created as a forum to pull in more active community members to carry out TPF business in the earlier years of the foundation when the board was much less active. When Karen Pauley, who was Steering Committee Chair, took over as president, this activity moved to the board. New committees also were created to handle specific areas of activity like conferences, grants, and marketing. With TPF activity moving to these other groups, the Steering Committee has been largely dormant so we're dissolving it. Thanks to all of the members who contributed their time to TPF through this committee.</p>
  276.  
  277. <p>Another committee we are evaluating is the Community Advocacy Committee. This committee was driven for many years by Ya'akov Sloman and we thank him for all of this efforts. He stepped down last year and the committee has been mostly inactive, so we are considering dissolving it as well. However, the board is open to proposals to revive the committee if community members are available to come forward. The <a href="http://www.perlfoundation.org/community_advocacy_committee_charter">committee charter is available</a> for review and could be revised by new members if desired.</p>
  278.  
  279. <p>Please join us in congratulating and thanking David and Will as they take on their new roles. You can expect to hear more from them in the near future.</p>
  280. ]]>
  281.        
  282.    </content>
  283. </entry>
  284.  
  285. <entry>
  286.    <title>Maintaining the Perl 5 Core: February 2017 report</title>
  287.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/03/maintaining-the-perl-5-core-fe.html" />
  288.    <id>tag:news.perlfoundation.org,2017://18.3854</id>
  289.  
  290.    <published>2017-03-13T23:00:00Z</published>
  291.    <updated>2017-03-14T03:58:13Z</updated>
  292.  
  293.    <summary>This is a monthly report by Dave Mitchell on his grant under Perl 5 Core Maintenance Fund. We thank the TPF sponsors to make this grant possible. The main things I did last month were: Firstly, fixing various issues with scopes in regexes. In particular, (RT #126697), code blocks sometimes failed to undo localisations when backtracking. For example the $s below wasn&apos;t always being restored when the B part of the match failed and it backtracked to try another A...</summary>
  294.    <author>
  295.        <name>Makoto Nozaki</name>
  296.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  297.    </author>
  298.    
  299.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  300.    
  301.        <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category" />
  302.    
  303.    
  304.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  305.        <![CDATA[<p>This is a monthly report by Dave Mitchell on his grant under <a href="http://www.perlfoundation.org/perl_5_core_maintenance_fund">Perl 5 Core Maintenance Fund</a>. We thank the TPF sponsors to make this grant possible.</p>
  306.  
  307. <pre>
  308. The main things I did last month were:
  309.  
  310. Firstly, fixing various issues with scopes in regexes. In particular,
  311. (RT #126697), code blocks sometimes failed to undo localisations when
  312. backtracking. For example the $s below wasn't always being restored when
  313. the B part of the match failed and it backtracked to try another A - where
  314. A represents something complex like (\w+\s+)* which can match in multiple
  315. ways:
  316.  
  317.    /A(?{ local $s = ...})B/
  318.  
  319. As part of that work, non-greedy matching of complex sub-expressions with
  320. captures and repeated backtracking was made more efficient under some
  321. circumstances; for example the following now runs about 25% faster:
  322.  
  323.    $s = ("a" x 1000);
  324.    $s =~ /^(?:(.)(.))*?[XY]/ for 1..10_000;
  325.  
  326. Secondly, improving 't/TEST -deparse'.
  327.  
  328. The -deparse option to t/TEST causes it to run all the core's test
  329. scripts, but after running them through the deparser first. Many of these
  330. modified scripts are currently known to fail, and there is an exclusion
  331. file, Porting/deparse-skips.txt, which is supposed to list the known
  332. failures. However, over time, new failures have appeared which are not in
  333. the exclusion list. Last August I did some work on Deparse.pm and managed
  334. to reduce some of the expected and unexpected failures, but since then
  335. more failures have crept in.
  336.  
  337. My recent work includes: modifying t/TEST so that it distinguishes
  338. between expected failures and unexpected passes, and warning of unknown
  339. files in Porting/deparse-skips.txt; purging Porting/deparse-skips.txt to
  340. account for files that have been renamed or are no longer in the core, and
  341. to reflect the current state of things; and fixing Deparse.pm to:
  342.    * better handle 'BEGIN { use_ok() }';
  343.    * better handle 'BEGIN { require expr }' (as opposed to require Bareword);
  344.    * deparse lexical var attributes, e.g. 'my $foo :bar(baz)';
  345.    * avoid a 'deep recursion' warning;
  346.    * handle an escaped literal tab char in a pattern, e.g
  347.        /.....\ ..../x where the whitespace char following the backslash is
  348.        actually a tab; previously the deparse failed to emit the backslash;
  349.    * handle declarations with multiple lexical vars within a pattern code
  350.      block, e.g. /(?{ my ($x, $y) = @a; })/
  351.  
  352. Because we're currently in code freeze, this as been pushed as
  353. smoke-me/davem/deparse and will be merged in 5.27.x.
  354.  
  355. Thirdly, reviewing and fixing tickets in the security queue. There's quite
  356. a lot of tickets in the security queue due to fuzzing, where if the fuzzer
  357. detects a use-after-free or buffer overrun for example, the reporter
  358. submits it to the security queue rather than the normal queue. Once
  359. examined, 95% of the time it will be found to be harmless or
  360. non-exploitable, but until someone has assessed and fixed it, it lingers
  361. as an open security ticket.
  362.  
  363. </pre>
  364. ]]>
  365.        <![CDATA[<pre>
  366. SUMMARY:
  367.     10:52 RT #126697 local() in embedded code in regex not working as expected
  368.      0:09 RT #128528 XSLoader may load relative paths
  369.      7:39 RT #129861 heap-use-after-free S_mro_gather_and_rename
  370.      6:05 RT #129881 heap-buffer-overflow Perl_pad_sv
  371.      2:11 RT #130321 heap-buffer-overflow Perl_vivify_ref (pp_hot.c:4362)
  372.      0:04 RT #130332 double-free affecting multiple Perl versions
  373.      0:36 RT #130336 attempting free on address which was not malloc()-ed
  374.      0:10 RT #130344 heap-use-after-free S_gv_fetchmeth_internal
  375.      1:46 RT #130569 heap-use-after-free in S_regmatch
  376.      0:43 RT #130624 heap-use-after-free in Perl_sv_setpvn
  377.      1:56 RT #130650 heap-use-after-free in S_free_codeblocks
  378.      6:04 RT #130703 heap-buffer-overflow in Perl_pp_formline
  379.      4:22 RT #130727 S_maybe_multideref: Assertion failed
  380.      2:22 RT #130766 Substr in encode leaks memory
  381.      1:12 RT #130841 AddressSanitizer: heap-buffer-overflow
  382.      0:39 fixup Module::CoreList
  383.     13:17 fixup failing TEST -deparse issues
  384.      9:30 process p5p mailbox
  385.     10:30 review security tickets
  386.    ------
  387.     80:07 TOTAL (HH::MM)
  388.  
  389. 176.3 weeks
  390. 2456.8 total hours
  391.  13.9 average hours per week
  392.  
  393. There are 343 hours left on the grant
  394. </pre>
  395. ]]>
  396.    </content>
  397. </entry>
  398.  
  399. <entry>
  400.    <title>Makoto Nozaki Appointed Secretary</title>
  401.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/03/makoto-nozaki-appointed-secret.html" />
  402.    <id>tag:news.perlfoundation.org,2017://18.3853</id>
  403.  
  404.    <published>2017-03-02T08:29:29Z</published>
  405.    <updated>2017-03-02T13:37:24Z</updated>
  406.  
  407.    <summary>The Perl Foundation is excited to announce that Makoto Nozaki, grants chair, has joined TPF board as secretary. He has served as grants chair since 2014 and has done a great job overseeing grants and providing funding for perl projects. In addition to supporting Makoto&apos;s TPF work, Two Sigma Investments, LP, Makoto&apos;s employer, has also provided donations to TPF for which we are very grateful. A focus for us this year is bringing new people into TPF at all levels,...</summary>
  408.    <author>
  409.        <name>Jim Brandt</name>
  410.        <uri>http://breakingpositive.com</uri>
  411.    </author>
  412.    
  413.        <category term="Perl Foundation" scheme="http://www.sixapart.com/ns/types#category" />
  414.    
  415.    
  416.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  417.        <![CDATA[<p>The Perl Foundation is excited to announce that Makoto Nozaki, grants chair, has joined TPF board as secretary. He has served as grants chair since 2014 and has done a great job overseeing grants and providing funding for perl projects. In addition to supporting Makoto's TPF work, <a href="https://www.twosigma.com/">Two Sigma Investments, LP</a>, Makoto's employer, has also provided donations to TPF for which we are very grateful.</p>
  418.  
  419. <p>A focus for us this year is bringing new people into TPF at all levels, and adding a new member to the board as a replacement for Karen Pauley is part of that effort. Thank you to Karen for all of her years of service on the board. As part of his role, Makoto will be taking on some projects to help us get the community more involved.</p>
  420.  
  421. <p>One important project scheduled for this year is to launch an updated and more public process for nominating and appointing new board members. TPF isn't a membership organization, so this doesn't mean we'll have elections. However, we would like to get the community involved in nominations and to have an opportunity to ask questions and interact with prospective board members as part of the evaluation process.</p>
  422.  
  423. <p>Once we have a new process in place for bringing in new board members, we plan to add more structure around the 2 year terms defined in the TPF bylaws. Currently board members have held their seats until they step down, typically because of time constraints. We would like to revise this process such that at the end of a 2 year term, existing board members will actively seek out another 2 year term if they would like to continue to serve.</p>
  424.  
  425. <p>These initiatives are at the idea phase right now and there are many details to work out to define the actual processes for both. We look forward to working these out with Makoto's active work over the next year.</p>
  426. ]]>
  427.        
  428.    </content>
  429. </entry>
  430.  
  431. <entry>
  432.    <title>Maintaining Perl 5: Grant Report for January 2017</title>
  433.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/02/maintaining-perl-5-grant-repor-37.html" />
  434.    <id>tag:news.perlfoundation.org,2017://18.3852</id>
  435.  
  436.    <published>2017-02-22T21:00:00Z</published>
  437.    <updated>2017-02-23T02:43:25Z</updated>
  438.  
  439.    <summary>This is a monthly report by Tony Cook on his grant under Perl 5 Core Maintenance Fund. We thank the TPF sponsors to make this grant possible. Approximately 38 tickets were reviewed, and 8 patches were applied [Hours] [Activity] 13.82 #122490 (sec) more merge conflicts #122490 (sec) more merge conflicts, track down warning sources #122490 (sec) track down warning sources, start merging test changes #122490 (sec) more test merging, testing, debugging #122490 (sec) debugging #122490 (sec) debugging 0.97 #126228 build...</summary>
  440.    <author>
  441.        <name>Makoto Nozaki</name>
  442.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  443.    </author>
  444.    
  445.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  446.    
  447.    
  448.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  449.        <![CDATA[<p>This is a monthly report by Tony Cook on his grant under <a href="http://www.perlfoundation.org/perl_5_core_maintenance_fund">Perl 5 Core Maintenance Fund</a>. We thank the TPF sponsors to make this grant possible.</p>
  450.  
  451. <pre>
  452. Approximately 38 tickets were reviewed, and 8 patches were
  453. applied
  454.  
  455. [Hours]         [Activity]
  456. 13.82          #122490 (sec) more merge conflicts
  457.                #122490 (sec) more merge conflicts, track down warning
  458.                sources
  459.                #122490 (sec) track down warning sources, start merging
  460.                test changes
  461.                #122490 (sec) more test merging, testing, debugging
  462.                #122490 (sec) debugging
  463.                #122490 (sec) debugging
  464.  0.97          #126228 build testing, apply to blead
  465. 16.08          #127663 testing, apply hash seed env suppression patch,
  466.                back to in-place changes
  467.                #127663 work on chdir test, testing, debugging, make
  468.                mg_freeext() API and fix docs
  469.                #127663 cleanup, threads handling, threads test
  470.                #127663 more threads testing, try to make it fail with
  471.                fork
  472.                #127663 more try to make it fail with fork and succeed,
  473.                work on fix, code polish
  474.                #127663 hoist some work back up, testing
  475.                #127663 uncombine thread/fork child handling which I
  476.                combined by accident, work on more tests and find a couple
  477.                of cleanup issues
  478.                #127663 more tests
  479.                #127663 post patch to ticket
  480.  0.22          #128528 (sec) review and comment
  481.  0.88          #128998 track down when it was fixed, ticket management
  482.  0.30          #129012 make public, comment and close
  483.  1.88          #129024 review, make public, check fix backports to 5.24,
  484.                non-trivial backport to 5.22, comment
  485.  1.30          #129125 check, testing, apply to blead
  486.  1.65          #129149 apply patch, test #130557 case, testing, make
  487.                public apply to blead, comment on #130557
  488.  0.08          #129187 check and merge into #129149
  489.  0.95          #129190 rebase with some conflicts, testing, make public,
  490.                apply to blead
  491.  0.17          #129199 make public, comment and close
  492.  2.62          #129274 (sec) try to find an alternative attack
  493.                #129274 more trying to break it, write regression test,
  494.                testing, make public, apply to blead
  495.  2.12          #129292 review code, debugging, make public and comment
  496.  1.77          #129298 review patches, research, consider whether changes
  497.                improve perl
  498.                #129298 more consideration, ask khw
  499.  4.32          #129340 (sec) review code, think about solutions
  500.                #129340 (sec) work on a solution, testing
  501.                #129340 (sec) write a regression test, testing
  502.                #129340 (sec) suggested changes, testing
  503.                #129340 (sec) research, comment with updated patch
  504.  0.50          #129342 (sec) test provided patch, create a test case and
  505.                comment
  506.  0.45          #129377 (sec) review patch, look for similar issues,
  507.                comment
  508.  1.32          #129840 (sec) review, testing
  509.                #129840 get it to test, merge into 129377
  510.  0.40          #129848 review and make public
  511.  1.53          #129861 (sec) debugging
  512.  0.42          #129887 (sec) review and comment
  513.  0.82          #129963 research, make public and link to stack-not-
  514.                refcounted meta ticket
  515.  0.92          #129975 debugging, make public and link to stack-not-
  516.                refcounted meta ticket
  517.  0.28          #130100 make public and point at list discussion on
  518.                removal
  519.  0.73          #130256 debugging, make public and link to stack-not-
  520.                refcounted meta ticket
  521.  1.67          #130262 apply patch with noise, test #130558 case,
  522.                testing, make public, push to blead, comment on #130558
  523.  0.18          #130321 (sec) debugging
  524.  0.68          #130504 review, testing, apply to blead
  525.  0.43          #130560 comment
  526.  0.90          #130567 reproduce, suspect 94749a5ed was bad, ask khw on
  527.                #p5p
  528.                #130567 irc discussion
  529.  1.35          #130569 (sec) comment
  530.  2.85          #130578 debugging
  531.                #130578 debugging, comment
  532.  0.58          #130591 review discussion and comment
  533.  0.33          #130614 research and comment
  534.  1.57          #130635 review changes, check memory use, testing, comment
  535.                #130635 comment
  536.  1.55          #130675 debugging, #p5p discussion
  537.                #130675 debugging, #p5p comment, ticket comment on #130679
  538.  0.42          comment on deprecations thread
  539. ======
  540. 69.01 hours total
  541. </pre>
  542. ]]>
  543.        
  544.    </content>
  545. </entry>
  546.  
  547. <entry>
  548.    <title>Perl 5 Core Hackathon (p5hack) Report</title>
  549.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/02/2016-p5h-report.html" />
  550.    <id>tag:news.perlfoundation.org,2017://18.3851</id>
  551.  
  552.    <published>2017-02-21T04:52:06Z</published>
  553.    <updated>2017-02-21T06:07:42Z</updated>
  554.  
  555.    <summary> (Graphics credit to Leonardo Maia.) Thanks to The Perl Foundation and our beloved sponsors, a large portion of the critical contributors to the Perl 5 Porters (p5p), the core group of Perl 5 developers, were able to get together on November 11th, 2016 at the Booking.com headquarters in Amsterdam, The Netherlands, for our very first Perl 5 Core hackathon, nicknamed Perl 5 Hack. This is our report. It was a four-day event, composed of discussions (centralized and specialized) on...</summary>
  556.    <author>
  557.        <name>Todd Rinaldo</name>
  558.        
  559.    </author>
  560.    
  561.        <category term="Conferences" scheme="http://www.sixapart.com/ns/types#category" />
  562.    
  563.        <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category" />
  564.    
  565.    
  566.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  567.        <![CDATA[<p><img alt="perl5-hack-logo-04.jpg" src="http://news.perlfoundation.org/perl5-hack-logo-04.jpg" width="600" height="103" class="mt-image-none" style="" /></p>
  568.  
  569. <p>(Graphics credit to Leonardo Maia.)</p>
  570.  
  571. <p>Thanks to The Perl Foundation and our beloved sponsors, a large portion of the critical contributors to the Perl 5 Porters (p5p), the core group of Perl 5 developers, were able to get together on November 11th, 2016 at the Booking.com headquarters in Amsterdam, The Netherlands, for our very first Perl 5 Core hackathon, nicknamed <strong>Perl 5 Hack</strong>.</p>
  572.  
  573. <p>This is our report.</p>
  574.  
  575. <hr />
  576.  
  577. <p>It was a four-day event, composed of discussions (centralized and specialized) on a myriad of important topics, knowledge sharing, and cooperative hacking. It provided us with the ability to cut down several months worth of discussions and loss of time due to timezone differences.</p>
  578.  
  579. <p>We worked on several topics, such as the <code>Configure</code> phase, core modules, security updates to Perl library loading order ("dot in <code>@INC</code>\x80\x9d), improving compilation under C++11, Core API and internals, replacements for the buggy <code>utf8</code> IO layer, conditional lexical variable warnings, and deparsing some internal warnings information (<code>${^WARNING_BITS}</code>).</p>
  580.  
  581. <p>This alone would have been quite the fit, but we also achieved a few things along with those discussions. Some of our achievements include:</p>
  582.  
  583. <ul>
  584. <li>Cleaning up dead hints code (pre-ELF)</li>
  585. <li>Improved our release guide</li>
  586. <li>Improved our Configure process
  587. <ul>
  588. <li>Removing hundreds of complicated C conditionals</li>
  589. <li>Faster Configure script</li>
  590. </ul></li>
  591. <li>Cleaned up our install output</li>
  592. <li>Improved our API documentation</li>
  593. <li>Massive speed improvements to core modules</li>
  594. <li>Explored the new Test2 testing framework for Perl</li>
  595. <li>Reviewed and listed all current deprecations</li>
  596. <li>Tied all deprecations to an exact version, to improve transparency and communicate better our intentions regarding deprecated features and syntax</li>
  597. <li>Cleaned up core code:
  598. <ul>
  599. <li>Removed obscure and unused SVs</li>
  600. <li>Removed dead code</li>
  601. <li>Moved <code>Unicode::Normalize</code> to upstream blead</li>
  602. </ul></li>
  603. <li>Had done optimizations, such as when assigning to references.</li>
  604. <li>Reduced memory usage in core modules: <code>Data::Dumper</code> and <code>Time::Local</code>.</li>
  605. <li>Fuzzed core modules</li>
  606. <li>Have rewritten much of our readline implementation</li>
  607. <li>Introduced the indented <code>HEREDOC</code> feature, being released in the upcoming 5.26</li>
  608. </ul>
  609.  
  610. <p>We raised a lot of topics and we made numerous important and valuable changes to the core code and core utilities, but we have also held in-depth discussions on the following topics:</p>
  611.  
  612. <ul>
  613. <li>Our COW implementation and where to take it in the future</li>
  614. <li>Efficiency of our hash bucket sizing</li>
  615. <li>Overloading indication</li>
  616. <li>Our policy on editing dual-life modules</li>
  617. <li>OP tree cloning</li>
  618. <li>Subroutine Signatures and their introspection</li>
  619. <li>The internals of the Perl to C compiler and what may be gleaned from it on improving perl</li>
  620. <li>The contribution hurdles when working with RT</li>
  621. <li>Vulnerability triage, classification, and handling - covering our security handling policies</li>
  622. <li>EBCDIC-portability</li>
  623. <li>Unicode (and specifically grapheme delimiters)</li>
  624. <li>Regular Expression internals</li>
  625. <li>Vtable-based hashes</li>
  626. </ul>
  627.  
  628. <p>Most of these have led to changes in policy, improvements or cleanups in core, and a "leg-up" on additional research into those topics.</p>
  629.  
  630. <p>All in all, despite it only being the first hackathon, it had already proved successful and beneficial. For this reason we intend to holding future hackathons, while both preparing better for them, as well as communicating better our work on them onward to the community.</p>
  631.  
  632. <p>Thank you to all attendees: Aaron Crane, Abigail, Brian Fraser, Dagfinn Mannsåker, Dave Mitchell, Dennis Kaarsemaker, Gonzalo Diethelm, H. Merijn Brand, John Lightsey, J. Nick Koston.  Karl Williamson, Leon Timmermans, Lukas Mai, Matthew Horsfall, Mattia Barbon, Nicholas Clark, Nicolas Rochelemagne, Sawyer X, Steffen Mueller, Stevan Little, Todd Rinaldo, Viekntiy Fusenov, and Yves Orton,</p>
  633.  
  634. <p>And thank you to The Perl Foundation for helping in organizing this event, and to all of our sponsors for contributing and assisting in this event: Our Diamond Sponsors, Booking.com; our Platinum Sponsors of cPanel and Craigslist; Silver Sponsors, Bluehost; and Bronze Sponsors of Assurant, Grant Street Group and Signature Information Solutions, and to FastMail, for their support of this, and future Perl Foundation activities.</p>
  635.  
  636. <p>A special thank you to the Perl community for the support it has given us and to the Perl 5 Porters group.</p>
  637.  
  638. <p>Sawyer X and Todd Rinaldo,
  639. Perl 5 Hackathon organizers.</p>
  640. ]]>
  641.        
  642.    </content>
  643. </entry>
  644.  
  645. <entry>
  646.    <title>Maintaining the Perl 5 Core: January 2017 report</title>
  647.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/02/maintaining-the-perl-5-core-ja.html" />
  648.    <id>tag:news.perlfoundation.org,2017://18.3850</id>
  649.  
  650.    <published>2017-02-07T23:00:00Z</published>
  651.    <updated>2017-02-08T04:43:36Z</updated>
  652.  
  653.    <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>
  654.    <author>
  655.        <name>Makoto Nozaki</name>
  656.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  657.    </author>
  658.    
  659.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  660.    
  661.    
  662.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  663.        <![CDATA[<p><em>Dave Mitchell writes:</em></p>
  664.  
  665. <pre>
  666. There are two main things I did in December (along with the usual
  667. day-to-day stuff).
  668.  
  669. First I sorted out infrastructure for ops which are called in boolean
  670. context.
  671.  
  672. Currently PADHV and RV2HV ops are flagged specially if they are not only
  673. used in scalar context, but where the result they return will only
  674. ever be used as a boolean value; for example 'if (%h) {...}'
  675.  
  676. This was originally done since a hash in scalar context returned a bucket
  677. usage ratio, which became expensive to calculate when we no longer
  678. stored the bucket occupancy count with each hash.
  679.  
  680. In 5.25.x we've changed it so that in scalar context it now only returns a
  681. key count, which is always known and doesn't need to be calculated on the
  682. fly. But it can still be quicker to return just a boolean value in
  683. these cases rather than an integer.
  684.  
  685. My work took this special-case boolean context detection code in the
  686. peephole optimiser, and improved it so that:
  687.  
  688. * it fixes a bunch of bugs - e.g. if (!%h) {...} wasn't recognised as
  689.   boolean;
  690. * it expands the number of situations that are recognised as boolean
  691.   context, such as grep:  e.g. grep %$_, @AoH;
  692. * it adds a reasonably comprehensive set of tests for checking that ops
  693.   have been flagged as boolean under various boolean scenarios;
  694. * it allows other ops to be easily added to the boolean detection in the
  695.   optimiser; and to the test suite.
  696.  
  697. I've also tweaked RV2HV so that in the negative case it just returns
  698. &PL_sv_no rather than sv_2mortal(newSViv(0)))
  699.  
  700. I've also pushed a branch davem/boolref2 that allows the ref() function to
  701. be optimised in boolean context; so 'if (ref $r) {...}' doesn't have to
  702. generate a temporary string like "Foo=ARRAY(0xc8afd8)". I intend to merge
  703. this after 5.26, and maybe booleanise a few more ops too (like length()).
  704.  
  705. The other notable thing I did last month was to change the output format
  706. produced by the op_dump() function (and perl -Dx). It now displays an
  707. ASCII-art tree structure, and more low-level information is displayed,
  708. such as each op's address and class.
  709.  
  710.  
  711. SUMMARY:
  712.      3:21 RT #129285 Perl_gv_fullname4 assertion
  713.      0:36 RT #130617 Perl_rpeep: Assertion ....
  714.      0:55 RT #130621 Segfault in Perl_vwarner (util.c:2051)
  715.      0:49 RT #130648 S_pat_upgrade_to_utf8 Assertion ...
  716.      1:17 RT #130651] regcomp.c:6881 Assertion `expr' failed
  717.      1:19 RT #130661 perly.c:341: Perl_yyparse: Assertion failed
  718.      1:03 RT #130667 Perl_sv_clear Assertion `SvTYPE(sv) != ...
  719.      0:52 RT #130669 Perl_sv_2nv_flags: Assertion `SvTYPE(sv) != ...
  720.      5:18 [perl #130198] chop(@x =~ tr///)
  721.      3:00 [perl #130584] Slow pos function in taint mode with \G
  722.     22:53 [perl #78288] ref and other ops are inefficient in boolean context
  723.     12:08 change output format of op_dump()
  724.      3:20 factor out common optree finalisation code
  725.      4:30 general housekeeping
  726.     10:41 process p5p mailbox
  727.      2:51 review security tickets
  728.    ------
  729.     74:53 TOTAL (HH::MM)
  730.  
  731. 172.3 weeks
  732. 2376.7 total hours
  733.  13.8 average hours per week
  734.  
  735. There are 423 hours left on the grant
  736. </pre>
  737. ]]>
  738.        
  739.    </content>
  740. </entry>
  741.  
  742. <entry>
  743.    <title>January 2017 Grant Votes</title>
  744.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/january-2017-grant-votes.html" />
  745.    <id>tag:news.perlfoundation.org,2017://18.3849</id>
  746.  
  747.    <published>2017-01-31T23:00:00Z</published>
  748.    <updated>2017-02-07T05:24:27Z</updated>
  749.  
  750.    <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>
  751.    <author>
  752.        <name>Makoto Nozaki</name>
  753.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  754.    </author>
  755.    
  756.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  757.    
  758.    
  759.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  760.        <![CDATA[<p>The Grants Committee has concluded the voting of the January round.</p>
  761.  
  762. <h3>Proposal in this round</h3>
  763.  
  764. <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>
  765. <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>
  766. </table></p>
  767.  
  768. <h3>Voting Results</h3>
  769.  
  770. <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>
  771. <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>
  772. </table></p>
  773.  
  774. <p>Definition of the score is found in 3.2 of the <a href="http://www.perlfoundation.org/rules_of_operation">rules</a>.</p>
  775.  
  776. <h3>Details</h3>
  777.  
  778. <p>We approve this grant.</p>
  779.  
  780. <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>
  781.  
  782. <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>
  783. ]]>
  784.        
  785.    </content>
  786. </entry>
  787.  
  788. <entry>
  789.    <title>Dave Mitchell&apos;s Grant Extended</title>
  790.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/dave-mitchells-grant-extended-2.html" />
  791.    <id>tag:news.perlfoundation.org,2017://18.3848</id>
  792.  
  793.    <published>2017-01-29T14:00:00Z</published>
  794.    <updated>2017-01-29T19:32:21Z</updated>
  795.  
  796.    <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>
  797.    <author>
  798.        <name>Makoto Nozaki</name>
  799.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  800.    </author>
  801.    
  802.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  803.    
  804.    
  805.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  806.        <![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>
  807.  
  808. <p>I'm pleased to announce that the Board of Directors approved extension of another $20,000.</p>
  809.  
  810. <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>
  811. ]]>
  812.        
  813.    </content>
  814. </entry>
  815.  
  816. <entry>
  817.    <title>Grants Committee needs a new member</title>
  818.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/grants-committee-needs-a-new-m.html" />
  819.    <id>tag:news.perlfoundation.org,2017://18.3847</id>
  820.  
  821.    <published>2017-01-25T22:00:00Z</published>
  822.    <updated>2017-01-26T05:08:38Z</updated>
  823.  
  824.    <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>
  825.    <author>
  826.        <name>Makoto Nozaki</name>
  827.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  828.    </author>
  829.    
  830.        <category term="Perl Foundation" scheme="http://www.sixapart.com/ns/types#category" />
  831.    
  832.    
  833.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  834.        <![CDATA[<p>The Perl Foundation's Grants Committee is looking for a new member.</p>
  835.  
  836. <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>
  837.  
  838. <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>
  839.  
  840. <p><p></p>
  841.  
  842. <h2>Nomination procedure</h2>
  843.  
  844. <p>Candidates must be nominated by a member (voting/non-voting) of the Grants Committee.</p>
  845.  
  846. <p>If you would like to be nominated, please get in touch with one of the members below or the Secretary ([email protected]).</p>
  847.  
  848. <p>The nomination process will be closed on Feb 1st.</p>
  849.  
  850. <p><p></p>
  851.  
  852. <h2>Position Details</h2>
  853.  
  854. <p><strong>Committee Secretary</strong></p>
  855.  
  856. <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>
  857.  
  858. <p>Note that the Secretary doesn't vote except for the casting vote and usually doesn't express opinion on each grant.</p>
  859.  
  860. <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>
  861.  
  862. <p><strong>Committee Member</strong></p>
  863.  
  864. <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>
  865.  
  866. <p><p></p>
  867.  
  868. <h2>Frequently Asked Questions</h2>
  869.  
  870. <p>Q1: Will the nomination and selection be made in public?</p>
  871.  
  872. <p>A1: No. Only the selected individual will be announced.</p>
  873.  
  874. <p>Q2: What if I have further questions?</p>
  875.  
  876. <p>A2: Feel free to contact me at [email protected] or comment here.</p>
  877.  
  878. <p><p></p>
  879.  
  880. <h2>Current Members List</h2>
  881.  
  882. <ul>
  883. <li>Makoto Nozaki (Secretary)</li>
  884. <li>Will "Coke" Coleda</li>
  885. <li>Rafael Garcia-Suarez</li>
  886. <li>Perrin Harkins</li>
  887. <li>Thomas Klausner</li>
  888. <li>Daisuke Maki</li>
  889. <li>Elizabeth Mattijsen</li>
  890. <li>Ricardo Signes</li>
  891. <li>Alberto Simões</li>
  892. <li>Sawyer X</li>
  893. <li>Alan Alavi (non-voting)</li>
  894. <li>Tom Hukins (non-voting)</li>
  895. <li>Mark A. Jensen (non-voting)</li>
  896. </ul>
  897. ]]>
  898.        
  899.    </content>
  900. </entry>
  901.  
  902. <entry>
  903.    <title>Maintaining Perl 5: Grant Report for December 2016</title>
  904.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/maintaining-perl-5-grant-repor-36.html" />
  905.    <id>tag:news.perlfoundation.org,2017://18.3846</id>
  906.  
  907.    <published>2017-01-25T21:00:00Z</published>
  908.    <updated>2017-01-26T05:10:06Z</updated>
  909.  
  910.    <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>
  911.    <author>
  912.        <name>Makoto Nozaki</name>
  913.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  914.    </author>
  915.    
  916.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  917.    
  918.    
  919.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  920.        <![CDATA[<p><em>Tony Cook writes:</em></p>
  921.  
  922. <pre>
  923. Approximately 21 tickets were reviewed or worked on, and 2 patches
  924. were applied.
  925.  
  926. [Hours]         [Activity]
  927.  4.33          #127149 re-work patch to fix a related issue, debugging
  928.                #127149 debugging, comment on Encode #59
  929. 14.98          #127663 testing, minor polish, re-check, comment with
  930.                patch
  931.                #127663 reply to comment, work on additional patch for env
  932.                control of the internal seed
  933.                #127663 more internal seed env, comment with patch
  934.                #127663 work on patch updates, testing
  935.                #127663 more patch updates, work on patch to optionally
  936.                disable hash randomization env vars
  937.                #127663 *at probes, bang head against metaconfig a bit,
  938.                directly modify Configure instead
  939.                #127663 more Configure, re-work in-place editing code to
  940.                use the new functions, testing
  941.                #127663 work on chdir test
  942.                #127663 config fixes
  943.  1.23          #128093 testing an comment
  944.  0.65          #129788 testing, apply patch to blead
  945.  0.27          #130056 review discussion, comment
  946.  2.35          #130122 partly review patch
  947.                #130122 review the rest, testing
  948.  1.53          #130169 review, testing, apply to blead
  949.  1.22          #130195 review discussion, patch
  950.                #130195 testing (and it turns out Dave applied it)
  951.  0.25          #130242 research and comment
  952.  0.27          #130256 (sec) testing, comment
  953.  0.67          #130262 (sec) testing, produce a fix, comment with patch
  954.  1.80          #130270 testing, debugging
  955.  0.50          #130321 (sec) review, debug, comment
  956.  0.27          #130328 comment
  957.  0.27          #130332 (sec) testing, minify, comment
  958.  1.98          #130335 review issue, write a test, work on a patch
  959.                #130335 debugging, fixes, comment with patch
  960.  0.47          #130336 (sec) testing, minify, comment
  961.  1.55          #130344 (sec) testing, minify, debugging, comment
  962.  1.72          #130367 work on a patch, testing, comment
  963.  0.37          perldelta update
  964.  0.32          security list discussion
  965. ======
  966. 37.00 hours total
  967. </pre>
  968. ]]>
  969.        
  970.    </content>
  971. </entry>
  972.  
  973. <entry>
  974.    <title>Final Grant Report : RPerl User Documentation #2 </title>
  975.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/final-grant-report-rperl-user-.html" />
  976.    <id>tag:news.perlfoundation.org,2017://18.3845</id>
  977.  
  978.    <published>2017-01-25T02:38:34Z</published>
  979.    <updated>2017-01-25T02:53:45Z</updated>
  980.  
  981.    <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>
  982.    <author>
  983.        <name>Mark A Jensen</name>
  984.        
  985.    </author>
  986.    
  987.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  988.    
  989.    <category term="grants" label="grants" scheme="http://www.sixapart.com/ns/types#tag" />
  990.    <category term="rperl" label="RPerl" scheme="http://www.sixapart.com/ns/types#tag" />
  991.    
  992.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  993.        <![CDATA[<p>Will Braswell has submitted his final report (below) on his grant
  994. <a href="http://news.perlfoundation.org/2016/02/grant-proposal-rperl-user-docu-1.html">RPerl User Documentation, Part 2</a>.</p>
  995.  
  996. <p>The Grants Committee welcomes comments from the community before it
  997. votes on completion of the grant.</p>
  998.  
  999. <p>MAJ</p>
  1000.  
  1001. <hr>
  1002.  
  1003. <ul id="index">
  1004.  <li><a href="#RPerl-User-Documentation-Part-2-Final-Report">RPerl User Documentation, Part 2, Final Report</a>
  1005.    <ul>
  1006.      <li><a href="#Deliverables">Deliverables</a></li>
  1007.      <li><a href="#Inch-stones">Inch-stones</a></li>
  1008.      <li><a href="#Completeness-Criteria">Completeness Criteria</a></li>
  1009.    </ul>
  1010.  </li>
  1011. </ul>
  1012.  
  1013. <h1 id="RPerl-User-Documentation-Part-2-Final-Report">RPerl User Documentation, Part 2, Final Report</h1>
  1014.  
  1015. <dl>
  1016.  
  1017. <dt id="Name">Name:</dt>
  1018. <dd>
  1019.  
  1020. <p>Will Braswell</p>
  1021.  
  1022. </dd>
  1023. <dt id="Amount-Requested">Amount Requested:</dt>
  1024. <dd>
  1025.  
  1026. <p>USD 1,600</p>
  1027.  
  1028. </dd>
  1029. </dl>
  1030.  
  1031. <h2 id="Deliverables">Deliverables</h2>
  1032.  
  1033. <p>Deliverables for this grant proposal are:</p>
  1034.  
  1035. <p>1. Complete Learning RPerl Chapter 2</p>
  1036.  
  1037. <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>
  1038.  
  1039. <p>2. Write Learning RPerl Chapter 3</p>
  1040.  
  1041. <p><a href="http://rperl.org/learning_rperl.html#CHAPTER_3%3A_ARRAY_VALUES_%26_VARIABLES">CHAPTER 3: ARRAY VALUES &amp; VARIABLES</a></p>
  1042.  
  1043. <p>3. Write Learning RPerl Chapter 4</p>
  1044.  
  1045. <p><a href="http://rperl.org/learning_rperl.html#CHAPTER_4%3A_ORGANIZING_BY_SUBROUTINES">CHAPTER 4: ORGANIZING BY SUBROUTINES</a></p>
  1046.  
  1047. <h2 id="Inch-stones">Inch-stones</h2>
  1048.  
  1049. <p>Chapter 2 Scalar Data</p>
  1050.  
  1051. <p>1a. Numbers; Strings; RPerl&rsquo;s Built-in Warnings; Scalar Variables</p>
  1052.  
  1053. <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>
  1054.  
  1055. <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>
  1056.  
  1057. <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>
  1058.  
  1059. <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>
  1060.  
  1061. <p>1b. Output with print; The if Control Structure; Getting User Input; The chomp Operator</p>
  1062.  
  1063. <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>
  1064.  
  1065. <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>
  1066.  
  1067. <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>
  1068.  
  1069. <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>
  1070.  
  1071. <p>1c. The while Control Structure; The undef Value; The defined Function</p>
  1072.  
  1073. <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>
  1074.  
  1075. <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>
  1076.  
  1077. <p>Chapter 3 Lists and Arrays</p>
  1078.  
  1079. <p>2a. Accessing Elements of an Array; Special Array Indices; List Literals; List Assignment</p>
  1080.  
  1081. <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>
  1082.  
  1083. <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>
  1084.  
  1085. <p><a href="http://rperl.org/learning_rperl.html#Section_3.1%3A_Lists_vs_Arrays">Section 3.1: Lists vs Arrays</a></p>
  1086.  
  1087. <p><a href="http://rperl.org/learning_rperl.html#Section_3.7%3A_Array_Assignment">Section 3.7: Array Assignment</a></p>
  1088.  
  1089. <p>2b. Interpolating Arrays into Strings; The foreach Control Structure</p>
  1090.  
  1091. <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>
  1092.  
  1093. <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>
  1094.  
  1095. <p>2c. Scalar and List Context; &lt;STDIN&gt; in List Context</p>
  1096.  
  1097. <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>
  1098.  
  1099. <p><a href="http://rperl.org/learning_rperl.html#Section_3.17%3A_STDIN_%26_Arrays">Section 3.17: STDIN &amp; Arrays</a></p>
  1100.  
  1101. <p>Chapter 4 Subroutines</p>
  1102.  
  1103. <p>3a. Defining a Subroutine; Invoking a Subroutine; Return Values; Arguments</p>
  1104.  
  1105. <p><a href="http://rperl.org/learning_rperl.html#Section_4.1%3A_Subroutine_Definitions">Section 4.1: Subroutine Definitions</a></p>
  1106.  
  1107. <p><a href="http://rperl.org/learning_rperl.html#Section_4.2%3A_Subroutine_Calls">Section 4.2: Subroutine Calls</a></p>
  1108.  
  1109. <p><a href="http://rperl.org/learning_rperl.html#Section_4.3%3A_Subroutine_Return_Values">Section 4.3: Subroutine Return Values</a></p>
  1110.  
  1111. <p><a href="http://rperl.org/learning_rperl.html#Section_4.4%3A_Subroutine_Arguments">Section 4.4: Subroutine Arguments</a></p>
  1112.  
  1113. <p>3b. Private Variables in Subroutines; Variable-Length Parameter Lists; Notes on Lexical (my) Variables</p>
  1114.  
  1115. <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>
  1116.  
  1117. <p><a href="http://rperl.org/learning_rperl.html#Section_4.4.1%3A_Variadic_Subroutines">Section 4.4.1: Variadic Subroutines</a></p>
  1118.  
  1119. <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>
  1120.  
  1121. <p>3c. The use strict Pragma; The return Operator</p>
  1122.  
  1123. <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>
  1124.  
  1125. <p><a href="http://rperl.org/learning_rperl.html#Section_4.3.1%3A_return_Operator">Section 4.3.1: return Operator</a></p>
  1126.  
  1127. <p>3d. Non-Scalar Return Values; Persistent, Private Variables</p>
  1128.  
  1129. <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>
  1130.  
  1131. <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>
  1132.  
  1133. <h2 id="Completeness-Criteria">Completeness Criteria</h2>
  1134.  
  1135. <p>I will release a new version of RPerl to CPAN with the new documentation.</p>
  1136.  
  1137. <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>
  1138.  
  1139. <p><a href="https://metacpan.org/pod/release/WBRASWELL/RPerl-2.410000/lib/RPerl/Learning.pm">Learning RPerl</a> (CPAN)</p>
  1140.  
  1141. <p>I will release a new version of the RPerl website with the new documentation.</p>
  1142.  
  1143. <p><a href="http://rperl.org/learning_rperl.html">Learning RPerl</a> (RPerl site)</p>
  1144. ]]>
  1145.        
  1146.    </content>
  1147. </entry>
  1148.  
  1149. <entry>
  1150.    <title>Grant Report : RPerl User Documentation #2 - Dec 2016</title>
  1151.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/grant-report-rperl-user-docume-12.html" />
  1152.    <id>tag:news.perlfoundation.org,2017://18.3844</id>
  1153.  
  1154.    <published>2017-01-23T00:06:46Z</published>
  1155.    <updated>2017-01-23T00:22:37Z</updated>
  1156.  
  1157.    <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>
  1158.    <author>
  1159.        <name>Mark A Jensen</name>
  1160.        
  1161.    </author>
  1162.    
  1163.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  1164.    
  1165.    <category term="grants" label="grants" scheme="http://www.sixapart.com/ns/types#tag" />
  1166.    <category term="rperl" label="RPerl" scheme="http://www.sixapart.com/ns/types#tag" />
  1167.    
  1168.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  1169.        <![CDATA[<p>Will Braswell reports that he has completed the deliverables for
  1170. <a href="http://news.perlfoundation.org/2016/02/grant-proposal-rperl-user-docu-1.html">RPerl Docs #2</a>:</p>
  1171.  
  1172. <p>"Lots of big news for RPerl!
  1173. First, Christmas saw the release of the new Perl-powered platform <a href="http://CloudForFree.org">CloudForFree.org</a> ;v1.0, codename Nimbostratus.
  1174. Secondly, on New Years Day we released <a href="https://metacpan.org/release/WBRASWELL/RPerl-2.410000">RPerl v2.4</a>, codename Aurora.
  1175. 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!
  1176. Over 160 pages of brand new material has been written under this grant for chapters 2, 3, and 4 of Learning RPerl.</p>
  1177.  
  1178. <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>
  1179. What's next for RPerl?  ;What other exciting new advancements are coming down the pike?
  1180. Stay tuned to <a href="http://RPerl.org">RPerl.org</a> and find out!"</p>
  1181.  
  1182. <p>MAJ</p>
  1183. ]]>
  1184.        
  1185.    </content>
  1186. </entry>
  1187.  
  1188. </feed>
  1189.  

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