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-12-11T03:29:39Z</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 (Dave Mitchell): Grant Report for Nov 2017</title>
  13.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/12/maintaining-the-perl-5-core-da-3.html" />
  14.    <id>tag:news.perlfoundation.org,2017://18.3935</id>
  15.  
  16.    <published>2017-12-10T22:00:00Z</published>
  17.    <updated>2017-12-11T03:29:39Z</updated>
  18.  
  19.    <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. I spent last month mainly: * Fixing some issues thrown up by the new OP_MULTICONCAT optimisation; * Fixing some regressions in deparse testing: &apos;t/TEST -deparse&apos; feeds every test suite script through the deparser before trying to run it; about 6 scripts that formerly passed had started failing. I fixed all these, and removed...</summary>
  20.    <author>
  21.        <name>Makoto Nozaki</name>
  22.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  23.    </author>
  24.    
  25.        <category term="Perl 5 Development" 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>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>
  30.  
  31. <pre>I spent last month mainly:
  32.  
  33. * Fixing some issues thrown up by the new OP_MULTICONCAT optimisation;
  34.  
  35. * Fixing some regressions in deparse testing: 't/TEST -deparse' feeds every
  36.  test suite script through the deparser before trying to run it; about 6
  37.  scripts that formerly passed had started failing. I fixed all these, and
  38.  removed another 6 or so scripts from the 'expected to fail' exclusion
  39.  list.
  40.  
  41. SUMMARY:
  42.      1:30 RT #132152 Bleadperl breaks SARTAK/NetHack-Item-0.21.tar.gz
  43.      1:40 RT #132187 heap-buffer-overflow in Perl_fbm_instr
  44.      2:20 RT #132385 BBC: PDL-2.018 affected too
  45.      6:47 RT #132385 BBC: Whatever-0.23 affected too
  46.      2:30 RT #132385 OP_MULTICONCAT breaks Bit-Vector-7.4
  47.      2:26 Smoke FAIL's for lib/perl5db.t
  48.      1:20 [perl #132430] Multiconcat breaks AIX builds
  49.      1:51 fix OP_MULTICONCAT int type issues
  50.     16:52 fix TEST -deparse regressions
  51.      1:08 fix ext/B/t/optree_specials.t
  52.      8:28 process p5p mailbox
  53.      3:22 review security tickets
  54.    ------
  55.     50:14 TOTAL (HH::MM)
  56.  
  57. 215.6 weeks
  58. 2873.4 total hours
  59.  13.3 average hours per week
  60.  
  61. There are 260 hours left on the grant.</pre>
  62. ]]>
  63.        
  64.    </content>
  65. </entry>
  66.  
  67. <entry>
  68.    <title>Call for Volunteers</title>
  69.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/12/call-for-volunteers.html" />
  70.    <id>tag:news.perlfoundation.org,2017://18.3934</id>
  71.  
  72.    <published>2017-12-10T21:05:16Z</published>
  73.    <updated>2017-12-10T21:07:44Z</updated>
  74.  
  75.    <summary> Help needed for the 2018 TPC::NA The Perl Conference in America, formerly YAPC::NA, has put forward a formal call for volunteers to help out with next year&apos;s event. Perl has likely helped you, we could even say it has been helping you to pay your bills? This may be your chance to give back to the community that isn&apos;t writing code. TPC::NA 2018 (formerly known as YAPC::NA) is looking for volunteers to organize the conference. Can you do any...</summary>
  76.    <author>
  77.        <name>mdk</name>
  78.        <uri>http://www.shadowcat.co.uk</uri>
  79.    </author>
  80.    
  81.    <category term="conference" label="Conference" scheme="http://www.sixapart.com/ns/types#tag" />
  82.    <category term="perl" label="Perl" scheme="http://www.sixapart.com/ns/types#tag" />
  83.    <category term="volunteers" label="Volunteers" scheme="http://www.sixapart.com/ns/types#tag" />
  84.    
  85.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  86.        <![CDATA[<p> <big>Help needed for the 2018 TPC::NA<br />
  87. </big><br />
  88. The Perl Conference in America, formerly YAPC::NA, has put forward a formal call for volunteers to help out with next year's event. Perl has likely helped you, we could even say it has been helping you to pay your bills? This may be your chance to give back to the community that isn't writing code.</p>
  89.  
  90. <p>TPC::NA 2018 (formerly known as YAPC::NA) is looking for volunteers to organize the conference. Can you do any of these?<br />
  91. <ul><br />
  92. <li>Design logos & other creative things.</li><br />
  93. <li>Draft announcements & other communication.</li><br />
  94. <li>Be awesome & generally helpful.</li><br />
  95. </ul><br />
  96. <big>What will you get in return?</big><br />
  97. The main benefit is in knowing you helped bring a well loved conference to life and the grateful thanks of all the attendees, however there will be other benefits given such as a staff conference clothing, drinks and other appropriate reward.</p>
  98.  
  99. <p>If the answer is yes, then please fill in this form: https://docs.google.com/forms/d/1VLzH7cgMtX5P5q0y5pykiPW19TxEfIb_LLBXAvq8c2c/vewform?edit_requested=true</p>
  100.  
  101. <p><big>Note</big><br />
  102. In person attendance is optional (but we would love to see you in person), though it will require consistent monthly and weekly web conferences with other organizers.</p>]]>
  103.        
  104.    </content>
  105. </entry>
  106.  
  107. <entry>
  108.    <title>Grant Report : Complete YAML::PP - November 2017</title>
  109.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/12/grant-report-complete-yamlpp---1.html" />
  110.    <id>tag:news.perlfoundation.org,2017://18.3933</id>
  111.  
  112.    <published>2017-12-10T04:10:43Z</published>
  113.    <updated>2017-12-10T04:15:05Z</updated>
  114.  
  115.    <summary>Tinita, the one-woman YAML ecosystem, continues apace with her grant Complete YAML::PP. Find her latest report on her blog. She is making headway on some of the cooler features of YAML: flow style, anchors, and special tags. Legit boolean behavior is now implemented in YAML::XS. The blog post provides a nice rundown of the 4 ways to quote in YAML. Wondering what all the fuss is about? check out Tina&apos;s London talk. Code is at https://github.com/perlpunk/YAML-PP-p5. MAJ...</summary>
  116.    <author>
  117.        <name>Mark A Jensen</name>
  118.        
  119.    </author>
  120.    
  121.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  122.    
  123.    <category term="grants" label="grants" scheme="http://www.sixapart.com/ns/types#tag" />
  124.    <category term="yaml" label="yaml" scheme="http://www.sixapart.com/ns/types#tag" />
  125.    
  126.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  127.        <![CDATA[<p>Tinita, the one-woman YAML ecosystem, continues apace with her grant <a href="http://news.perlfoundation.org/2017/08/grant-proposal-complete-yamlpp.html">Complete YAML::PP</a>. Find her latest report on <a href="http://blogs.perl.org/users/tinita/2017/12/yamlpp-grant-report-november-2017.html">her blog</a>.</p>
  128.  
  129. <p>She is making headway on some of the cooler features of YAML: flow style, anchors, and special tags. Legit boolean behavior is now implemented in <a href="https://metacpan.org/pod/YAML::XS">YAML::XS</a>. The blog post provides a nice rundown of the 4 ways to quote in YAML.</p>
  130.  
  131. <p>Wondering what all the fuss is about? check out Tina's London <a href="http://act.yapc.eu/lpw2017/talk/7232">talk</a>.</p>
  132.  
  133. <p>Code is at <a href="https://github.com/perlpunk/YAML-PP-p5">https://github.com/perlpunk/YAML-PP-p5</a>.</p>
  134.  
  135. <p>MAJ</p>
  136. ]]>
  137.        
  138.    </content>
  139. </entry>
  140.  
  141. <entry>
  142.    <title>Maintaining the Perl 5 Core (Zefram): Grant Report for Nov 2017</title>
  143.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/12/maintaining-the-perl-5-core-ze.html" />
  144.    <id>tag:news.perlfoundation.org,2017://18.3932</id>
  145.  
  146.    <published>2017-12-04T03:00:00Z</published>
  147.    <updated>2017-12-04T03:12:16Z</updated>
  148.  
  149.    <summary>This is the first report from Zefram on his Perl 5 grant under Perl 5 Core Maintenance Fund. We thank the TPF sponsors to make this grant possible. The hours that I have worked in 2017-11 pursuant to my TPF core maintenance grant are as follows. 30h25m smartmatch 15h15m [perl #114932] state(@a) = 12h08m review tickets 9h54m review mail 8h26m [perl #108778] no warnings &quot;module name&quot; 3h46m [perl #132158] negative-size-param (size=-7) in S_scan_formline (toke.c:11414) 3h37m [perl #36078] Newz() used gratuitously...</summary>
  150.    <author>
  151.        <name>Makoto Nozaki</name>
  152.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  153.    </author>
  154.    
  155.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  156.    
  157.        <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category" />
  158.    
  159.    
  160.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  161.        <![CDATA[<p>This is the first report from Zefram on his <a href="http://news.perlfoundation.org/2017/06/perl-5-core-grant-proposal-zef.html">Perl 5 grant</a> 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>
  162.  
  163. <pre>The hours that I have worked in 2017-11 pursuant to my TPF core
  164. maintenance grant are as follows.
  165.  
  166. 30h25m  smartmatch
  167. 15h15m  [perl #114932] state(@a) =
  168. 12h08m  review tickets
  169.  9h54m  review mail
  170.  8h26m  [perl #108778] no warnings "module name"
  171.  3h46m  [perl #132158] negative-size-param (size=-7) in
  172.         S_scan_formline (toke.c:11414)
  173.  3h37m  [perl #36078] Newz() used gratuitously
  174.  3h28m  [perl #113716] Deparse and trailing colons
  175.  3h28m  [perl #38920] Filter::Simple error messages getting mangled
  176.         inside require
  177.  3h12m  [perl #132414] eval in package DB can't see caller's lexicals
  178.         in certain cases
  179.  2h58m  [perl #115266] s//$obj/ does not propagated taintedness of
  180.         overloaded object
  181.  2h43m  Devel::Cover BBC from deparsing change
  182.  2h09m  [perl #108288] stat and -T do not set errno consistently
  183.  2h07m  [perl #115258] 4-arg substr does not provide proper lvalue
  184.         context
  185.  2h05m  [perl #126414] perl rounds inode in PP stat
  186.  2h05m  [perl #132150] ... (yada-yada) parsing is inconsistent
  187.  2h02m  [perl #119803] $ISA[0] assignment does not work
  188.  1h47m  [perl #122368] [PATCH] improve docs about mortal in perlguts
  189.  1h37m  [perl #132492] inward goto deprecation has no removal date
  190.  1h33m  [perl #129892] sub calls show as gv(IV \)
  191.  1h19m  test temp filenames
  192.  1h17m  [perl #119635] deprecate and remove qsort?
  193.  1h14m  [perl #115262] PerlIO::encoding produces malformed utf8
  194.  1h13m  [perl #119813] Assertion failure when debugger dies
  195.  1h10m  ExtUtils-ParseXS test noise
  196.  1h07m  [perl #132413] PL_keyword_plugin needs thread-safe wrap
  197.         setter
  198.  1h06m  [perl #125827] [PATCH] PathTools, dont require() modules in
  199.         subs likely to be in loops
  200. </pre>
  201. ]]>
  202.        <![CDATA[<pre>
  203.    58m  [perl #131762] perldoc output misbehaviour
  204.    57m  [perl #119805] Errors in preamble code report line 0
  205.    48m  [perl #121904] array each iterator storage is inefficient
  206.    44m  [perl #91362] Deparse omits implicit ~~
  207.    38m  ext/XS-APItest/t/sviscow.t warning
  208.    38m  B version portability
  209.    37m  Win32 -k errors
  210.    36m  [perl #125774] do EXPR on dir fails but has no error code $!
  211.    30m  [perl #131895] stat() doesn't fail on filenames containing \0
  212.         / NUL
  213.    30m  [perl #113714] Deparse and CORE
  214.    28m  [perl #123491] Perl_debop and Perl_runops_debug and
  215.         PL_runops_dbg, are they DEBUGGING or not?
  216.    28m  [perl #132272] qw() differs from split " " with OGHAM SPACE
  217.         MARK
  218.    26m  [perl #119823] LABEL<newline>: only works in string eval
  219.    25m  [perl #125370] select on non-socket should be fatal on win32,
  220.         not an error code
  221.    25m  [perl #116286] *pvs SV functions don't take "const char*"s
  222.    23m  create tickets
  223.    20m  [perl #42603] func Class->method should resolve to func(
  224.         Class->method )
  225.    19m  [perl #127697] newPVOP documentation is misleading
  226.    18m  [perl #132403] Long @INC gets replaced with executable
  227.    18m  [perl #132395] BBC: Commit 7a831b72 breaks UNIVERAL::isa
  228.         tests
  229.    17m  [perl #122096] [PATCH] reduce # of calls to errno
  230.    13m  [perl #132460] ambiguity regarding "x" operator in perlop
  231.    13m  [perl #115880] redundant SvUPGRADE in perl_construct?
  232.    10m  [perl #115650] "Truth and Falsehood" doesn't belong in
  233.         perlsyn
  234.     7m  [perl #93102] keys is not always an lvalue
  235.     5m  [perl #122122] [PATCH] PERL_UNUSED_CONTEXT audit
  236. 135h02m  TOTAL
  237.  
  238. At the end of the month there was 264h58m of authorised working time
  239. remaining in this grant.</pre>
  240. ]]>
  241.    </content>
  242. </entry>
  243.  
  244. <entry>
  245.    <title>TPF to start public nomination/election process of board members</title>
  246.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/11/tpf-to-start-public-nomination.html" />
  247.    <id>tag:news.perlfoundation.org,2017://18.3931</id>
  248.  
  249.    <published>2017-11-28T03:00:18Z</published>
  250.    <updated>2017-11-28T03:11:46Z</updated>
  251.  
  252.    <summary>The Perl Foundation is a non-profit, 501(c)(3) organization based in the United States. Currently its board of directors has seven members and TPF plans to start annual nomination and election process of new members. Bringing new people to the board regularly, with some community input, will allow the organization to grow and increase its output. The below is proposed process of nomination and election of new board members, which will be practiced in February every year. The first call for...</summary>
  253.    <author>
  254.        <name>Makoto Nozaki</name>
  255.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  256.    </author>
  257.    
  258.    
  259.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  260.        <![CDATA[<p>The Perl Foundation is a non-profit, 501(c)(3) organization based in the United States. Currently its board of directors has seven members and TPF plans to start annual nomination and election process of new members. Bringing new people to the board regularly, with some community input, will allow the organization to grow and increase its output.</p>
  261.  
  262. <p>The below is proposed process of nomination and election of new board members, which will be practiced in February every year. The first call for board nominations will be posted in the first week of February 2018. If you have any questions, comment here or contact makoto at perlfoudation.org.</p>
  263.  
  264. <p>1. Nomination</p>
  265.  
  266. <p>A new member should be nominated by one or more Board members.</p>
  267.  
  268. <p>2. Eligibility</p>
  269.  
  270. <p>The nominee must be an active volunteer of TPF at least for 180 days.</p>
  271.  
  272. <p>3. Public hearing</p>
  273.  
  274. <p>Public post will be made to ask for input from the community. The post will have the nominee's bio and reasons for nomination.</p>
  275.  
  276. <p>4. Election</p>
  277.  
  278. <p>Election will be made by the board members after feedback is gathered from the public.</p>
  279. ]]>
  280.        
  281.    </content>
  282. </entry>
  283.  
  284. <entry>
  285.    <title>Booking.com Sponsors the P5CMF</title>
  286.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/11/booking-sponsors-the-perl-5.html" />
  287.    <id>tag:news.perlfoundation.org,2017://18.3930</id>
  288.  
  289.    <published>2017-11-27T09:47:18Z</published>
  290.    <updated>2017-11-27T10:00:46Z</updated>
  291.  
  292.    <summary>The long time supporters of the Perl community, world-class business ,and a leading employer of Perl programmers worldwide, Booking.com has added a generous sponsorship to the Core Maintenance Fund. It is a great privilege to announce that they have added one hundred thousand dollars to the initiative.
  293. </summary>
  294.    <author>
  295.        <name>mdk</name>
  296.        <uri>http://www.shadowcat.co.uk</uri>
  297.    </author>
  298.    
  299.        <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category" />
  300.    
  301.    <category term="bookingcom" label="Booking.com" scheme="http://www.sixapart.com/ns/types#tag" />
  302.    <category term="cmf" label="CMF" scheme="http://www.sixapart.com/ns/types#tag" />
  303.    <category term="coremaintenancefund" label="Core Maintenance Fund" scheme="http://www.sixapart.com/ns/types#tag" />
  304.    <category term="p5cmf" label="P5CMF" scheme="http://www.sixapart.com/ns/types#tag" />
  305.    <category term="perl5" label="Perl 5" scheme="http://www.sixapart.com/ns/types#tag" />
  306.    <category term="perl5" label="Perl5" scheme="http://www.sixapart.com/ns/types#tag" />
  307.    <category term="sponsorship" label="Sponsorship" scheme="http://www.sixapart.com/ns/types#tag" />
  308.    
  309.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  310.        <![CDATA[<h3>A Proud History</h3>
  311.  
  312. <p>The long time supporters of the Perl community, world-class business ,and a leading employer of Perl programmers worldwide, <a href="https://www.booking.com">Booking.com</a> has added a generous sponsorship to the Core Maintenance Fund. It is a great privilege to announce that they have added one hundred thousand dollars to the initiative.</p>
  313.  
  314. <p><a href="https://www.booking.com">Booking.com</a> have been supporters of the fund since its inception and have long championed the important work that this brings to the Perl community. It is well known that a number of prominent Perl community developers work for Booking.com who give time and support to the community work. Booking are also very visible at conferences and events and are hosts of a number of community projects and conferences.</p>
  315.  
  316. <p>The Perl Foundation are proud of the support that <a href="https://www.booking.com">Booking.com</a> bring to the community and to this important fund. Dan Wright (Treasurer of TPF) had this to say:</p>
  317.  
  318. <blockquote>
  319.  <p>‘I have spent many years marvelling at the support we get from many companies in the Perl world. I work for a company that is proud to be a part of the community and to sponsor and support our language and the people around it. So it is humbling when other companies approach me with such generous contributions. </p>
  320.  
  321. <p><a href="https://www.booking.com">Booking.com</a>, like so many other organisations and individuals who contribute to the Perl community, are a great part of why we all succeed with Perl.’</p>
  322. </blockquote>
  323.  
  324. <h3>About Booking.com</h3>
  325.  
  326. <p>Established in 1996 in Amsterdam, <a href="https://www.booking.com">Booking.com</a> has grown from a small Dutch start-up to one of the largest travel e-commerce companies in the world. Part of The Priceline Group (NASDAQ: PCLN), <a href="https://www.booking.com">Booking.com</a> now employs more than 15,000 employees in 198 offices in 70 countries worldwide.</p>
  327.  
  328. <p>With a mission to empower people to experience the world, <a href="https://www.booking.com">Booking.com</a> invests in digital technology that helps take the friction out of travel. At Booking.com, we connect travellers with the world’s largest selection of incredible places to stay, including everything from apartments, vacation homes, and family-run B&amp;Bs to 5-star luxury resorts, tree houses and even igloos. The Booking.com website and mobile apps are available in over 40 languages, offer 1,533,448 properties, and cover 123,250 destinations in 229 countries and territories worldwide.</p>
  329.  
  330. <p>Each day, more than 1,550,000 room nights are reserved on our platform. So whether travelling for business or leisure, customers can instantly book their ideal accommodation quickly and easily with Booking.com, without booking fees and backed up by our promise to price match. Via our customer experience team, customers can reach Booking.com 24/7 for assistance and support in over 40 languages, any time of the day or night.</p>
  331.  
  332. <h3>The Perl 5 Core Maintenance Fund</h3>
  333.  
  334. <p>As you may have read earlier this year the Perl 5 Core Maintenance Fund was coming to an end of its initial grant funding and the fund itself was almost out of capital. At that time we placed a call out to extend the vital work that has been done over the last five years. Booking.com are the first company to respond and we are very grateful to them.</p>
  335.  
  336. <p>The initial fund round raised over half a million dollars that has been used to fund several full time developers who have made significant improvements to Perl 5 and to the language. This second round of funding will see the initiative make more changes. </p>
  337.  
  338. <p>If you would like to join with <a href="https://www.booking.com">Booking.com</a> in sponsoring the fund then please do not hesitate to contact the Perl Foundation. </p>
  339. ]]>
  340.        
  341.    </content>
  342. </entry>
  343.  
  344. <entry>
  345.    <title>Maintaining the Perl 5 Core (Dave Mitchell): Grant Report for Sep/Oct 2017</title>
  346.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/11/maintaining-the-perl-5-core-da-2.html" />
  347.    <id>tag:news.perlfoundation.org,2017://18.3929</id>
  348.  
  349.    <published>2017-11-23T22:00:00Z</published>
  350.    <updated>2017-11-24T03:03:50Z</updated>
  351.  
  352.    <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. I didn&apos;t do much TPF grant work for the last two months, as I was mainly working on OP_MULTICONCAT, which was funded by Booking.com. That&apos;s also why there&apos;s been a dearth of weekly reports. The main thing I did was making a few minor enhancements to bench.pl. See http://nntp.perl.org/group/perl.perl5.porters/246816 for details. SUMMARY: 0:50...</summary>
  353.    <author>
  354.        <name>Makoto Nozaki</name>
  355.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  356.    </author>
  357.    
  358.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  359.    
  360.        <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category" />
  361.    
  362.    
  363.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  364.        <![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>
  365.  
  366. <pre>I didn't do much TPF grant work for the last two months, as I was mainly
  367. working on OP_MULTICONCAT, which was funded by Booking.com.
  368.  
  369. That's also why there's been a dearth of weekly reports.
  370.  
  371. The main thing I did was making a few minor enhancements to bench.pl.
  372. See http://nntp.perl.org/group/perl.perl5.porters/246816 for details.
  373.  
  374. SUMMARY:
  375.      0:50 discuss memchr() with Karl.
  376.     10:29 minor bench.pl enhancements
  377.      3:06 process p5p mailbox
  378.      1:28 review Karl's utf8n_to_uvchr work.
  379.    ------
  380.     15:53 TOTAL (HH::MM)
  381.  
  382. 211.3 weeks
  383. 2823.2 total hours
  384.  13.4 average hours per week</pre>
  385. ]]>
  386.        
  387.    </content>
  388. </entry>
  389.  
  390. <entry>
  391.    <title>Test2 Documentation Grant Progress Report</title>
  392.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/11/test2-documentation-grant-prog-3.html" />
  393.    <id>tag:news.perlfoundation.org,2017://18.3928</id>
  394.  
  395.    <published>2017-11-22T18:45:06Z</published>
  396.    <updated>2017-11-22T18:51:07Z</updated>
  397.  
  398.    <summary>During the last month, Chad Granum did some notable progress on the grant. As Chad points out: I got it to the point where I felt comfortable publishing it to cpan, despite being incomplete: https://metacpan.org/pod/Test2::Manual that includes: Spell check test, to correct my typos Added Anatomy section to describe Test2 guts Added Anatomy for Events and Facets Finished the Tooling/FirstTool document Added the Tooling/Nesting document Added the Tooling/Subtest document Added the Tooling/Testing document Lots of cleanup and minor tweaks. There...</summary>
  399.    <author>
  400.        <name>Alberto Simões</name>
  401.        <uri>http://blogs.perl.org/users/alberto_simoes/</uri>
  402.    </author>
  403.    
  404.    <category term="grants" label="grants" scheme="http://www.sixapart.com/ns/types#tag" />
  405.    
  406.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  407.        <![CDATA[<p>During the last month, Chad Granum did some notable progress on the grant. As Chad points out:</p>
  408.  
  409. <blockquote>
  410.  <p>I got it to the point where I felt comfortable publishing it to cpan, despite being incomplete: <a href="https://metacpan.org/pod/Test2::Manual">https://metacpan.org/pod/Test2::Manual</a></p>
  411. </blockquote>
  412.  
  413. <p>that includes:</p>
  414.  
  415. <ul>
  416. <li>Spell check test, to correct my typos</li>
  417. <li>Added Anatomy section to describe Test2 guts</li>
  418. <li>Added Anatomy for Events and Facets</li>
  419. <li>Finished the Tooling/FirstTool document</li>
  420. <li>Added the Tooling/Nesting document</li>
  421. <li>Added the Tooling/Subtest document</li>
  422. <li>Added the Tooling/Testing document</li>
  423. <li>Lots of cleanup and minor tweaks.</li>
  424. </ul>
  425.  
  426. <p>There are still several planned documents that need to be written, but they are all listed now in one of the 3 sections (Testing, Tooling, Anatomy) with a "coming soon" note.</p>
  427. ]]>
  428.        
  429.    </content>
  430. </entry>
  431.  
  432. <entry>
  433.    <title>Perl 6 Performance and Reliability Engineering: November 2017</title>
  434.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/11/perl-6-performance-and-reliabi-4.html" />
  435.    <id>tag:news.perlfoundation.org,2017://18.3927</id>
  436.  
  437.    <published>2017-11-19T15:22:14Z</published>
  438.    <updated>2017-11-19T15:31:22Z</updated>
  439.  
  440.    <summary>As part of the Perl 6 core development fund, Jonathan Worthington has completed another 200 hour block of hours, and his report of what was completed follows the break. Many thanks to the TPF sponsors of this and other grants. If you&apos;re interested in supporting work like this, please donate: http://donate.perlfoundation.org/...</summary>
  441.    <author>
  442.        <name>Coke</name>
  443.        
  444.    </author>
  445.    
  446.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  447.    
  448.    
  449.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  450.        <![CDATA[<p>As part of the Perl 6 core development fund, Jonathan Worthington has completed another 200 hour block of hours, and his report of what
  451. was completed follows the break.</p>
  452.  
  453. <p>Many thanks to the TPF sponsors of this and other grants. If you're interested in supporting work like this, please donate: http://donate.perlfoundation.org/</p>
  454.  
  455. <hr />
  456. ]]>
  457.        <![CDATA[<h1>Grant Completion Report: Perl 6 Performance and Reliability Engineering</h1>
  458.  
  459. <p>At the end of July, I was granted a <a href="http://news.perlfoundation.org/2017/07/grant-extension-approved-perl-.html">200 hour extension</a>
  460. of my Perl 6 Performance and Reliability Engineering grant. I used this time
  461. primarily to focus on MoarVM's dynamic optimizer, although did many other
  462. fixes and improvements aside from that.</p>
  463.  
  464. <h2>Background on the dynamic optimizer improvements</h2>
  465.  
  466. <p>Modern runtimes, especially for dynamic languages, rely on dynamic optimization
  467. techniques. These analyze the behavior of the program at runtime, and use that
  468. data to drive optimization. MoarVM's dynamic optimizer is typically referred to
  469. as "the specializer", or "spesh" for short, and this nicely captures its core
  470. strategy: taking code with lots of potential dynamism, and producing one or
  471. more specialized versions of the code with as much of that dynamic behavior
  472. stripped out as possible.</p>
  473.  
  474. <p>The specializer was planned as part of MoarVM from the start, although its
  475. implementation came after the initial public release of the VM. Soon after
  476. that, the focus switched to the Christmas release of Perl 6, where nailing down
  477. semantics was a much bigger focus than optimization. Since then, the
  478. specializer was improved in numerous ways, however various limitations in its
  479. design started to show up repeatedly as we analyzed Perl 6 program performance.
  480. Furthermore, stress testing showed up a range of bugs in the optimizer that had
  481. potential to cause incorrect behavior in user code.</p>
  482.  
  483. <p>Therefore, for the sake of both performance and reliability, it was desirable
  484. to invest some time improving the specializer.</p>
  485.  
  486. <h2>Specialization in the background</h2>
  487.  
  488. <p>Modern hardware is parallel, and it is desirable to find ways to take advantage
  489. of that. Originally, the specializer would do optimization work on the same
  490. thread that user code was running on. This not only paused execution in order
  491. to do optimization, but it also meant that multiple threads running the same
  492. code (say, in a data parallel program) would all race to do and install the
  493. same optimization.</p>
  494.  
  495. <p>I introduced a background thread for performing specializations. This not only
  496. meant that optimization work and JIT compilation would not interupt execution,
  497. but also resolved the issue of multiple threads scrambling to do the same
  498. optimization. Since there was now only one thread producing optimizations, some
  499. locking logic could also go away. A further upshot of this is that even a
  500. single-threaded user program can now get some advantage from multi-core
  501. hardware.</p>
  502.  
  503. <p>One downside of this is that the exact timing of specializations being installed
  504. becomes unpredictable, and this can make debugging more difficult. Therefore, I
  505. added a deterministic mode, enabled by environment variable, which makes a
  506. thread pause while the optimization thread does its work. This, for a
  507. single-threaded user program, offers deterministic behavior.</p>
  508.  
  509. <h2>Better data for better decisions</h2>
  510.  
  511. <p>The specializer's decision making about what to optimize, and how to optimize
  512. it, will only be as good as the data available to it. The data model
  513. prior to my work under this grant was rather limiting. For example, it was not
  514. possible to get a high level overview of what was monomorphic code (same types
  515. always), polymorphic code (handful of different types) and megamorphic code
  516. (loads of different types). There were also too few samples to know if a type
  517. that was seen to differ once was really rare or not. When there are only ten or
  518. so samples, and a type differs one time, then it could vary up to 10% of the
  519. time; that will tend to be too costly to leave deoptimization to handle. By
  520. contrast, if there are a hundred samples and it happens one time, then it is
  521. much safer to leave that slow path to be handled by the interpreter, for the
  522. sake of running the common case potentially a lot faster.</p>
  523.  
  524. <p>I implemented a lightweight interpreter logging mechanism. It writes compact
  525. logs about encountered types, invocation targets, and more into a sequential
  526. thread-local buffer. When the buffer is filled, it is sent to the specialization
  527. thread. Over on that thread, the recorded events are played back in a stack
  528. simulation, and a data model built up that aggregates the statistics. This is
  529. then used by a planner to decide what optimizations to produce.</p>
  530.  
  531. <p>Along the way, I introduced a new kind of specialization, which specializes
  532. only on the shape of the callsite (how many arguments and which named arguments)
  533. rather than the incoming types. This means that megamorphic code (that is,
  534. code called on many different types) can now receive some optimization, as well
  535. as compilation into machine code. Before, a few specializations were produced,
  536. and then everything else was left to run slowly under the interpreter.</p>
  537.  
  538. <h2>New optimizations</h2>
  539.  
  540. <p>Besides allowing for better decision making, I introduced some new optimizations
  541. as well as making existing ones more powerful.</p>
  542.  
  543. <ul>
  544. <li>I enabled many more calls to be inlined (a powerful optimization where a
  545. call to a small routine is replaced with the code of the routine itself).
  546. This was achieved by using the new statistics to spot when the target of a
  547. call was reliably the same, and introducing a guard clause. Prior to this,
  548. inlining was only available to methods resolved through the cache or subs
  549. in the setting or the outermost scope. I also handled the case where the
  550. passed arguments were consistently typed, but it had not been possible for
  551. the optimizer to prove that, again using guard clauses.</li>
  552. <li>I implemented inlining of closures (that is, code that refers to variables
  553. in an outer scope).</li>
  554. <li>I made dead code removal happen far more eagerly, and improved the
  555. quality of type information available in code following the eliminated
  556. conditional. This is a significant improvement for parameters with default
  557. values, as well as branches based on types or constants.</li>
  558. <li>I made frames that are reliably promoted from the call stack onto the heap be
  559. allocated right away on the heap, to save the promotion cost. (This promotion
  560. happens when a callframe needs to be referenced by a heap object.)</li>
  561. <li>I changed the way that control exception's flow is represented to be more
  562. accurate, enabling elimination of handlers that become unreachable once the
  563. code they cover also becomes unreachable. The change also resulted in more
  564. accurate type information propagation, which can aid other optimizations.</li>
  565. <li>I made the optimization that rewrites control exceptions into far cheaper
  566. <code>goto</code> instructions apply into inlines.</li>
  567. </ul>
  568.  
  569. <h2>Specializer fixes</h2>
  570.  
  571. <p>The specializer usually only operates on "hot" code, so that the time that it
  572. spends optimizing will have maximum benefit. However, it is possible to set an
  573. environment variable that lowers these thresholds, making the specializer try
  574. to optimize every bit of code that is encountered. This, combined with the
  575. deterministic mode, provides a means to stress test the optimizer, by forcing
  576. it to consider and optimize a great deal more code that it usually would do.
  577. Running the NQP and Rakudo builds , together with the Perl 6 test suite, in
  578. this way can flush out bugs that would not show up when only optimizing hot
  579. code.</p>
  580.  
  581. <p>Prior to my work under this grant, failures would show up from this stress
  582. testing as soon as the NQP build. After a good amount of bug hunting and fixing,
  583. the NQP build and tests, together with the Rakudo build and basic tests, are
  584. completely clean under this stresstest. The handful of remaining failures in
  585. the stresstest are a result of inlining distorting backtraces (at the moment,
  586. the inlined frames do not appear in the backtrace), thus causing some
  587. error-reporting tests to fail.</p>
  588.  
  589. <p>The fixes included addressing a long-standing but rarely occurring crash
  590. involving the intersection of specialization, multiple dispatch, and
  591. destructuring in signatures; a number of different crashes boiled down to this.
  592. Another important range of fixes involved eliminating poor assumptions around
  593. <code>Scalar</code>s and aliasing, which aside from fixing bugs also stands us in a better
  594. position to implement escape analysis (which requires alias analysis) in the
  595. future.</p>
  596.  
  597. <h2>Notable results from the specializer work</h2>
  598.  
  599. <p>The specialization improvements showed up in a number of benchmarks. Two that
  600. are particularly worth calling out are:</p>
  601.  
  602. <ul>
  603. <li>The daily <code>Text::CSV</code> module benchmark runs hit new lows thanks to the
  604. specializer improvements.</li>
  605. <li>The "read a million line UTF-8 file" benchmark that I've discussed before,
  606. where Rakudo on MoarVM used to be just a bit slower than Perl 5, is now won
  607. by Rakudo. This is a result of better code quality after specialization.</li>
  608. </ul>
  609.  
  610. <h2>Improved GC thread sync-up</h2>
  611.  
  612. <p>I re-worked the way that garbage collection synchronizes running threads, to
  613. eliminate busy-waiting. The idea of the original design was that running threads
  614. would quickly react to the GC interupt flag being set on them. However, this
  615. presumed that the threads were all really running, which is never a certainty
  616. given CPU cores are competed over by many processes. Furthermore, under tools
  617. like valgrind and callgrind, which serialize all threads onto a single CPU
  618. core, the busy-waiting strategy produced hugely distorted results, and greatly
  619. increased the time these useful, but already slow, tools would take. Now the
  620. synchronization is done using condition variables, meaning that both the kernel
  621. and tools like valgrind/callgrind have a much better idea of what is happening.
  622. While callgrind showed a large (10%-15%) reduction in CPU cycles in some
  623. multi-threaded programs, the improvements under normal running conditions were,
  624. as expected, much smaller, though still worthwhile.</p>
  625.  
  626. <h2>Other work</h2>
  627.  
  628. <p>Along with the improvements described above, I also:</p>
  629.  
  630. <ul>
  631. <li>Added support to <code>Proc::Async</code> to plumb the output handle of one process into
  632. the standard input of another process, with the handles being chained together
  633. at the file descriptor level.</li>
  634. <li>Hunted down and fixed a SEGV when many processes were spawned and all gave an
  635. error.</li>
  636. <li>Fixed RT #131384 (panic due to bug in error reporting path of ASCII decoder)</li>
  637. <li>Fixed RT #131611 (sigilles variable in coercion could generate internal
  638. compiler error)</li>
  639. <li>Fixed RT #131740 (wrong <code>$*THREAD</code> after <code>await</code> due to lack of
  640. invalidation of the dynamic variable lookup cache)</li>
  641. <li>Fixed RT #131365 and RT #131383 (<code>getc</code> and <code>readchars</code> read too many chars
  642. at the end of the file)</li>
  643. <li>Fixed RT #131673 (<code>is rw</code> with anonymous parameter reported error incorrectly)</li>
  644. <li>Fixed MoarVM issue 611 (memory errors arising from certain usage patterns of
  645. the decode stream)</li>
  646. <li>Fixed MoarVM issue 562 (SEGV from a particular use of the <code>calframe(...)</code>
  647. function)</li>
  648. <li>Fixed native callbacks when the callback is made on a thread other than the
  649. one that passed the callback in the first place</li>
  650. <li>Avoided a linear lookup, knocking 5% off the code-gen phase of compiling
  651. <code>CORE.setting</code></li>
  652. <li>Removed the long-unused <code>Lexotic</code> feature from MoarVM, which allowed some
  653. code cleanup (this used to be used to handle <code>return</code>, but it now uses the
  654. control exception system)</li>
  655. </ul>
  656.  
  657. <h2>Dissemination</h2>
  658.  
  659. <p>I wrote a 4-part series on my blog about the MoarVM specializer. The posts walk
  660. through the MoarVM specializer's design and functionality, and mention the many
  661. improvements done as a result of this grant - explaining why the new way of
  662. doing things represents an improvement from the previous way. The posts are:</p>
  663.  
  664. <ul>
  665. <li><a href="https://6guts.wordpress.com/2017/08/06/moarvm-specializer-improvements-part-1-gathering-data/">Part 1: Gathering Data</a></li>
  666. <li><a href="https://6guts.wordpress.com/2017/09/17/moarvm-specializer-improvements-part-2-planning/">Part 2: Planning</a></li>
  667. <li><a href="https://6guts.wordpress.com/2017/11/05/moarvm-specializer-improvements-part-3-optimizing-code/">Part 3: Optimizing Code</a></li>
  668. <li><a href="https://6guts.wordpress.com/2017/11/09/moarvm-specializer-improvements-part-4-argument-guards/">Part 4: Argument Guards</a></li>
  669. </ul>
  670.  
  671. <p>I also travelled to the Swiss Perl Workshop and delivered a talk about the
  672. MoarVM specializer, titled "How does deoptimization help us go faster?". The
  673. <a href="http://jnthn.net/papers/2017-spw-deopt.pdf">slides</a> and <a href="https://www.youtube.com/watch?v=3umNn1KnlCY">video</a>
  674. were published online.</p>
  675.  
  676. <h2>Summary</h2>
  677.  
  678. <p>This latest grant extension enabled me to spend a significant amount of time on
  679. the MoarVM dynamic optimizer, both addressing bugs as well as overhauling the
  680. way information about program execution is collected and used. The new data
  681. allows for better decision making, and its availability allowed me to implement
  682. some new optimizations. Furthermore, I moved optimization work to take place on
  683. a background thread, so as not to interupt program execution. Aside from this
  684. work, I fixed other bugs and made some performance improvements unrelated to
  685. the dynamic optimizer. Finally, I gave a presentation about dynamic optimization
  686. at the Swiss Perl Workshop, and wrote an extensive 4-part blog series explaining
  687. the MoarVM optimization process.</p>
  688. ]]>
  689.    </content>
  690. </entry>
  691.  
  692. <entry>
  693.    <title>Grant Extension Approved: Tony Cook&apos;s maintaining Perl 5 Grant</title>
  694.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/11/grant-extension-approved-tony-.html" />
  695.    <id>tag:news.perlfoundation.org,2017://18.3926</id>
  696.  
  697.    <published>2017-11-13T22:00:00Z</published>
  698.    <updated>2017-11-14T03:42:12Z</updated>
  699.  
  700.    <summary>Tony Cook recently requested an extension of his Maintaining the Perl 5 Grant. I&apos;m pleased to announce that the Board of Directors approved extension of another $20,000. It&apos;ll allow him to dedicate another 400 hours to this work. 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. For the fund status, please also see P5CMF...</summary>
  701.    <author>
  702.        <name>Makoto Nozaki</name>
  703.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  704.    </author>
  705.    
  706.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  707.    
  708.        <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category" />
  709.    
  710.    
  711.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  712.        <![CDATA[<p><strong>Tony Cook</strong> recently <a href="http://news.perlfoundation.org/2017/10/grant-extension-request-mainta-5.html">requested an extension of his Maintaining the Perl 5 Grant</a>.</p>
  713.  
  714. <p>I'm pleased to announce that the Board of Directors approved extension of another $20,000. It'll allow him to dedicate another 400 hours to this work.</p>
  715.  
  716. <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. For the fund status, please also see <a href="http://news.perlfoundation.org/2017/10/p5cmf-running-out-of-funds.html">P5CMF running out of funds</a>.</p>
  717.  
  718. <p>I also appreciate Tony Cook, who publishes regular progress report on his work.</p>
  719. ]]>
  720.        
  721.    </content>
  722. </entry>
  723.  
  724. <entry>
  725.    <title>Maintaining Perl 5 (Tony Cook): October 2017 Report</title>
  726.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/11/maintaining-perl-5-tony-cook-o.html" />
  727.    <id>tag:news.perlfoundation.org,2017://18.3925</id>
  728.  
  729.    <published>2017-11-12T23:00:00Z</published>
  730.    <updated>2017-11-13T04:21:35Z</updated>
  731.  
  732.    <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....</summary>
  733.    <author>
  734.        <name>Makoto Nozaki</name>
  735.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  736.    </author>
  737.    
  738.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  739.    
  740.        <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category" />
  741.    
  742.    
  743.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  744.        <![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>
  745. ]]>
  746.        <![CDATA[<pre>Approximately 23 tickets were reviewed, and 7 patches were
  747. applied
  748.  
  749. [Hours]         [Activity]
  750.  0.33          #122807 review discussion
  751.  0.45          #124349 review discussion and apply patch
  752.  0.40          #125619 review discussion, research, briefly comment
  753.  0.25          #125760 review discussion, add to 5.30 blockers for make
  754.                them croak instead
  755.  0.18          #126707 review discussion and code, comment
  756.  0.17          #126849 check upstream report and close
  757.  0.83          #127063 re-check patch, testing, apply to blead
  758. 39.85          #127743 work on cherry-picking from cperl
  759.                #127743 more cherry-picking
  760.                #127743 more cherry-picking
  761.                #127743 more cherry-picking
  762.                #127743 more cherry-picking
  763.                #127743 more cherry-picking
  764.                #127743 more cherry-picking
  765.                #127743 more cherry-picking
  766.                #127743 work on cherry-picking from cperl
  767.                #127743 work on cherry-picking from cperl
  768.                #127743 code review
  769.                #127743 code review
  770.                #127743 more code review
  771.                #127743 more code review, consider fixes
  772.                #127743 status email
  773.                #127743 email discussion
  774.                #127743 work on fixes
  775.                #127743 work on possible way to test large numbers of Svs
  776.                #127743 manage to produce buggy behaviour, work on fix
  777.                #127743 large object tag implementation, testing
  778.                #127743 test 2G+ object tag handling, testing
  779.                #127743 audit 2G+ tag handling for hooks, work on
  780.                regression tests for 2G+ object tag handling
  781.                #127743 more work on tests
  782.  3.21          #128765 work on fix
  783.                #128765 more work on fix
  784.                #128765 more work on fix, fail to figure out efficient
  785.                masking
  786.  0.33          #130080 research, add to maint-votes
  787.  0.92          #131065 (sec) comment
  788.  0.92          #131878 (sec) work up a patch and comment with patch
  789.  1.88          #131982 testing (including some strange results) minor
  790.                portability change, apply to blead
  791.  8.98          #132013 work on an implementation
  792.                #132013 work on an implementation
  793.                #132013 testing, debugging
  794.                #132013 debugging, add groups, - prefix
  795.                #132013 more tests, docs, polish, comment with patch
  796.  0.25          #132159 testing, apply to blead
  797.  0.40          #132160 review patch, testing, apply to blead
  798.  0.73          #132171 review, testing, apply to blead
  799.  0.42          #132234 try to reproduce, comment
  800.  5.50          #132245 debugging, find a memory leak, work on a fix,
  801.                testing
  802.                #132245 re-work fix, testing, comment with patches
  803.                #132245 restesting, apply to blead
  804.  0.28          comment on Zefram’s character encoding comment
  805.  0.52          default_inc_excludes_dot query
  806.  0.28          fix io/tell.t
  807.  0.52          script runs discussion: comment
  808. ======
  809. 67.60 hours total</pre>
  810. ]]>
  811.    </content>
  812. </entry>
  813.  
  814. <entry>
  815.    <title>Call For Proposals: November 2017 Round</title>
  816.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/11/call-for-proposals-november-20.html" />
  817.    <id>tag:news.perlfoundation.org,2017://18.3924</id>
  818.  
  819.    <published>2017-11-12T18:56:28Z</published>
  820.    <updated>2017-11-19T15:20:18Z</updated>
  821.  
  822.    <summary>The Grants Committee has expended its budget for the period ending with 2017. In accordance with the TPF rules of operation (http://www.perlfoundation.org/rulesofoperation), grants evaluations are stalled until further notice. I&apos;m expecting that we&apos;ll be able to re-open evaluations starting in the January 2018 period. Thanks to all the TPF sponsors that make the grants process possible. Please consider becoming one and donating at http://donate.perlfoundation.org/ If you have further questions, please contact me at tpf-grants-secretary at perl-foundation.org....</summary>
  823.    <author>
  824.        <name>Coke</name>
  825.        
  826.    </author>
  827.    
  828.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  829.    
  830.    
  831.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  832.        <![CDATA[<p>The Grants Committee has expended its budget for the period ending with 2017.</p>
  833.  
  834. <p>In accordance with the TPF rules of operation (http://www.perlfoundation.org/rules<em>of</em>operation),
  835. grants evaluations are stalled until further notice. I'm expecting that we'll be able to re-open
  836. evaluations starting in the January 2018 period.</p>
  837.  
  838. <p>Thanks to all the TPF sponsors that make the grants process possible. Please consider becoming one and
  839. donating at http://donate.perlfoundation.org/</p>
  840.  
  841. <p>If you have further questions, please contact me at tpf-grants-secretary at perl-foundation.org.</p>
  842. ]]>
  843.        
  844.    </content>
  845. </entry>
  846.  
  847. <entry>
  848.    <title>Grant Report - Complete YAML::PP - October 2017</title>
  849.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/11/grant-report---complete-yamlpp.html" />
  850.    <id>tag:news.perlfoundation.org,2017://18.3923</id>
  851.  
  852.    <published>2017-11-05T00:20:13Z</published>
  853.    <updated>2017-11-05T00:23:04Z</updated>
  854.  
  855.    <summary>Tina has put &gt;50hrs in on YAML::PP, as she describes in her blog post. Some highlights: 23 tests added to the standard test suite Updates to the YAML Test Matrix (which is a nice overview of YAML compliance across implementations in several languages) Under-hood work on YAML::XS boolean handling and YAML flow-style. MAJ...</summary>
  856.    <author>
  857.        <name>Mark A Jensen</name>
  858.        
  859.    </author>
  860.    
  861.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  862.    
  863.    <category term="grants" label="grants" scheme="http://www.sixapart.com/ns/types#tag" />
  864.    <category term="yaml" label="yaml" scheme="http://www.sixapart.com/ns/types#tag" />
  865.    
  866.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  867.        <![CDATA[<p>Tina has put >50hrs in on YAML::PP, as she describes in her <a href="http://blogs.perl.org/users/tinita/2017/11/yamlpp-grant-report-october-2017.html">blog post</a>. Some highlights:</p>
  868.  
  869. <ul>
  870. <li>23 tests added to the standard test suite</li>
  871. <li>Updates to the <a href="http://matrix.yaml.io/">YAML Test Matrix</a> (which is a nice overview of YAML compliance across implementations in several languages)</li>
  872. <li>Under-hood work on YAML::XS boolean handling and YAML flow-style.</li>
  873. </ul>
  874.  
  875. <p>MAJ</p>
  876. ]]>
  877.        
  878.    </content>
  879. </entry>
  880.  
  881. <entry>
  882.    <title>P5CMF running out of funds.</title>
  883.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/10/p5cmf-running-out-of-funds.html" />
  884.    <id>tag:news.perlfoundation.org,2017://18.3922</id>
  885.  
  886.    <published>2017-10-31T15:02:51Z</published>
  887.    <updated>2017-11-02T02:36:46Z</updated>
  888.  
  889.    <summary>The Perl 5 Core Maintenance Fund was established at YAPC::NA 2011 by Jesse Vincent and Karen Pauley as a continuation of the previous Booking.com grant. It is intended to be &quot;used for the maintenance and improvement of the Perl 5 core.&quot; Since its inception, the P5CMF has received over half of a million dollars in donations, and has provided funding for eight different individuals to contribute over 9,000 service hours towards improving performance, stability, and features for Perl 5. (Full...</summary>
  890.    <author>
  891.        <name>Dan Wright</name>
  892.        <uri>http://www.dwright.org</uri>
  893.    </author>
  894.    
  895.    
  896.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  897.        <![CDATA[<p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">The </span><a href="http://www.perlfoundation.org/perl_5_core_maintenance_fund" style="text-decoration: none;"><span style="font-size: 11pt; font-family: Arial; color: #1155cc; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: underline; vertical-align: baseline;">Perl 5 Core Maintenance Fund</span></a><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;"> was established at YAPC::NA 2011 by Jesse Vincent and Karen Pauley as a continuation of the previous Booking.com grant. It is intended to be "used for the maintenance and improvement of the Perl 5 core."</span></p>
  898. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"></p>
  899. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Since its inception, the P5CMF has received over half of a million dollars in donations, and has provided funding for eight different individuals to contribute over 9,000 service hours towards improving performance, stability, and features for Perl 5. (Full history </span><a href="https://docs.google.com/spreadsheet/pub?key=0AkU6pBm3WGeedGlqV1d0OXFVaG8yVTVDRFI5c0hLOHc&amp;output=html" style="text-decoration: none;"><span style="font-size: 11pt; font-family: Arial; color: #1155cc; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: underline; vertical-align: baseline;">here</span></a><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">)</span></p>
  900. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"></p>
  901. <p></p>]]>
  902.        <![CDATA[<p><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Two of the current recipients of the P5CMF grants are nearing the end of their allocations: Tony Cook will have depleted his allocation by the end of October and <a href="http://news.perlfoundation.org/2017/10/grant-extension-request-mainta-5.html">has already requested an extension</a>. David Mitchell will likely need an extension to his fund in February 2018. Typically these grants are extended in $20,000 increments.</span></p>
  903. <p><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Presently, the P5CMF has $8,426 remaining in unallocated funds. The Perl Foundation board has already moved $20,000 from its general fund to the P5CMF (as well as a matching $20,000 to the sister Perl 6 fund) in July of this year and is currently considering moving an additional $20,000 to the fund to cover Tony Cook's current grant extension request. These extensions were made possible through the generous support of our annual sponsors: craigslist, cPanel, bluehost, Grant Street Group, and Assurant.</span></p>
  904. <p><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">For targeted funds like the Perl 5 core maintenance fund, the goal is to allow donors to show their support for the work the fund enables through new donations. We believe this fund is important and valuable for everyone who relies on the health and continued development of Perl 5, but without additional donations we may need to consider closing the fund. We need your support to make sure that doesn't happen.</span></p>
  905. <p><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">If you would like to make a tax-deductible contribution to The Perl Foundation's Perl 5 Core Maintenace Fund, you may do so </span><a href="https://www.z2systems.com/np/clients/perlfoundation/donation.jsp?campaign=2&amp;" style="text-decoration: none;"><span style="font-size: 11pt; font-family: Arial; color: #1155cc; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: underline; vertical-align: baseline;">here</span></a><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">. As a thank-you gift, we will send you an "I patched Perl\x9d" adhesive patch for every $50 contributed to the fund (maximum 5 patches). </span></p>]]>
  906.    </content>
  907. </entry>
  908.  
  909. <entry>
  910.    <title>Maintaining Perl 5 (Tony Cook): Grant Report for September 2017</title>
  911.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/10/maintaining-perl-5-tony-cook-g-3.html" />
  912.    <id>tag:news.perlfoundation.org,2017://18.3920</id>
  913.  
  914.    <published>2017-10-25T22:00:00Z</published>
  915.    <updated>2017-10-25T02:03:18Z</updated>
  916.  
  917.    <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....</summary>
  918.    <author>
  919.        <name>Makoto Nozaki</name>
  920.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  921.    </author>
  922.    
  923.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  924.    
  925.        <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category" />
  926.    
  927.    
  928.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  929.        <![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>
  930. ]]>
  931.        <![CDATA[<pre>Approximately 47 tickets were reviewed, and 7 patches were applied.
  932.  
  933. [Hours]         [Activity]
  934.  7.13          #122112 work on a fix (and reentr discussion with khw)
  935.                #122112 more work on a fix
  936.                #122112 debugging
  937.                #122112 debugging
  938.                #122112 debugging, look for a different approach
  939.  2.31          #124256 re-work patch
  940.                #124256 more re-work patch, testing
  941.  3.94          #125351 try to understand the parser
  942.                #125351 try restoring stack, debug crashes
  943.                #125351 experiments, testing, debugging
  944.  1.82          #126706 re-work patch a bit, testing, debugging
  945.                #126706 debugging, fix taint issue
  946.  7.01          #127663 re-check, minor commit message changes, comment
  947.                with new patch
  948.                #127663 testing
  949.                #127663 more testing, apply to blead
  950.                #127663 reproduce, work on a fix, testing
  951.                #127663 more testing
  952.                #127663 comment on freebsd renameat() ticket
  953.  1.98          #129990 review, testing, coverage checks, benchmarking,
  954.                apply to blead
  955.  2.36          #131582 (sec) work on CVE details, comment
  956.                #131582, #131598 (sec) work with downstream
  957.                #131582, #131598 (sec) work with downstream
  958.  0.57          #131598 (sec) work on CVE details, comment
  959.  3.32          #131648 (sec) debugging
  960.                #131648 (sec) more debugging, briefly comment
  961.  0.77          #131665 (sec) work on CVE details, comment
  962.                #131665 (sec) comment
  963.  1.58          #131683 comment
  964.                #131683 comment
  965.                #131683 review patch, discussion in #p5p
  966.  0.70          #131685 research
  967.  1.15          #131746 retesting, apply to blead
  968.  1.45          #131777 re-base, re-check, re-test and apply to blead
  969.  2.21          #131894 research how to fix non-hex digit handling for
  970.                hex^Wbinaryfp numbers
  971.                #131894 work on a fix, testing
  972.                #131894 add more tests, testing, comment with patch
  973.  1.18          #131954 (sec) research and comment
  974.  1.51          #131982 research, comment
  975.                #131982 work on a patch and comment with patch
  976.  0.95          #131984 comment
  977.                #131984 re-review, testing, apply to blead
  978.  0.67          #132001 debugging, reject with comment
  979.  3.24          #132008 testing, minor fixes, apply to blead
  980.                #132008 look into regression, start setup of test VM
  981.                #132008 discussion with Tux, finish VM setup, also discuss
  982.                spam when smokes run in PERL_UNICODE= LC_ALL=some-utf8-
  983.                locale mode, work on a fix and apply to blead
  984.  0.17          #132017 (sec) comment
  985.  1.74          #132055 (sec) reproduce, debugging
  986.                #132055 (sec) debugging, ask khw to look at it
  987.  0.20          #132063 (sec) debugging, ask khw again
  988.  0.75          #132077 review patches and comment
  989.  3.02          #132087 testing, research, comment with patch, comment
  990.                with fixed patch
  991.                #132087, #127663 re-test various portability fixes and
  992.                apply to blead
  993.  0.28          #132094 research and comment
  994.  1.53          #132105 research and comment
  995.                #132105 look at making SIG_SIZE a variable, check CPAN for
  996.                usage and comment
  997.  0.05          #132134 review and comment
  998.  0.33          #132137 research and comment
  999.  1.03          #132138 work to understand failure, fix and apply to blead
  1000.  0.20          #132139 track down when minitest was introduced and
  1001.                comment
  1002.  1.23          #132147 (sec) research, comment
  1003.  0.95          #132158 (sec) debugging, comment
  1004.  0.42          #132159 review patch and comment
  1005.  0.60          #132163 debugging, comment, more debugging
  1006.  0.62          #132171 review patch and comment
  1007.  0.10          Configure changes from 5.24.1 to 5.26.1 thread: comment
  1008.  0.38          Configure changes from 5.24.1 to 5.26.1 thread: research
  1009.                and comment
  1010.  0.15          nigel’s arm builds: review build error, research and
  1011.                comment
  1012.  0.52          pin down CVE issues versions manually
  1013.  0.07          security ticket follow-up
  1014.  0.12          tes::readline fixe to backport list
  1015.  0.58          test openbsd fix for khw
  1016.  0.42          Try to pin down CVE issue versions with bisect
  1017.  0.70          update CVE entries at Mitre
  1018.  2.03          work on cleaning up build noise under PERL_UNICODE= ,
  1019.                testing, apply to blead
  1020.  2.92          Work on cleaning up test noise under PERL_UNICODE=
  1021. ======
  1022. 66.96 hours total</pre>
  1023. ]]>
  1024.    </content>
  1025. </entry>
  1026.  
  1027. </feed>
  1028.  

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