Congratulations!

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

Recommendations

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

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

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <feed xmlns="http://www.w3.org/2005/Atom">
  3.    <title>The Perl Foundation</title>
  4.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/" />
  5.    <link rel="self" type="application/atom+xml" href="http://news.perlfoundation.org/atom.xml" />
  6.    <id>tag:news.perlfoundation.org,2010-03-22://18</id>
  7.    <updated>2015-03-17T10:52:07Z</updated>
  8.    
  9.    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 4.38</generator>
  10.  
  11. <entry>
  12.    <title>Extended: Calling for grant proposals </title>
  13.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/03/extended-calling-for-grant-pro.html" />
  14.    <id>tag:news.perlfoundation.org,2015://18.3596</id>
  15.  
  16.    <published>2015-03-16T23:00:00Z</published>
  17.    <updated>2015-03-17T10:52:07Z</updated>
  18.  
  19.    <summary>I had flu with a high fever (104°F == 40°C) for a week. Unfortunately this happened in the final week of the March grant acceptance period. Apologies I couldn&apos;t respond to inquiries in timely fashion. As we haven&apos;t received grant applications in this period, we will extend the deadline to March 22nd. To apply for a grant of up to $10,000, please refer to my previous post to understand how....</summary>
  20.    <author>
  21.        <name>Makoto Nozaki</name>
  22.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  23.    </author>
  24.    
  25.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  26.    
  27.    
  28.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  29.        <![CDATA[<p>I had flu with a high fever (104°F == 40°C) for a week. Unfortunately this happened in the final week of the March grant acceptance period. Apologies I couldn't respond to inquiries in timely fashion.</p>
  30.  
  31. <p>As we haven't received grant applications in this period, we will extend the deadline to March 22nd.</p>
  32.  
  33. <p>To apply for a grant of up to $10,000, please refer to <a href="http://news.perlfoundation.org/2015/03/call-for-grant-proposals-march.html">my previous post</a> to understand how. </p>
  34. ]]>
  35.        
  36.  
  37.    </content>
  38. </entry>
  39.  
  40. <entry>
  41.    <title>Maintaining Perl 5: Grant Report for February 2015</title>
  42.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/03/maintaining-perl-5-grant-repor-15.html" />
  43.    <id>tag:news.perlfoundation.org,2015://18.3594</id>
  44.  
  45.    <published>2015-03-15T04:19:31Z</published>
  46.    <updated>2015-03-15T04:30:58Z</updated>
  47.  
  48.    <summary><![CDATA[Tony Cook writes: Approximately 55 tickets were reviewed or worked on, and 10 patches were applied. [perl #123784] shows perl's dependency on other system tools, in this case there were two issues when using GCC 5.0. First, with GCC 5.0, by default the pre-processor with generate #line entries showing the origin of the definition of a macro that's been replaced, so the pre-processor was producing output from: &quot;EDOM&quot; [[ EDOM ]] something like: #line &quot;errno.c&quot;, 1 &quot;EDOM&quot; [[ #line &quot;somesystemheader&quot;,...]]></summary>
  49.    <author>
  50.        <name>Karen Pauley</name>
  51.        <uri>http://martian.org/karen</uri>
  52.    </author>
  53.    
  54.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  55.    
  56.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  57.    
  58.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  59.        <![CDATA[<p><em>Tony Cook writes:</em></p>
  60.  
  61. <p>Approximately 55 tickets were reviewed or worked on, and 10 patches were applied.</p>
  62.  
  63. <p>[perl #123784] shows perl's dependency on other system tools, in this case there were two issues when using <span class="caps">GCC</span> 5.0.</p>
  64.  
  65. <p>First, with <span class="caps">GCC</span> 5.0, by default the pre-processor with generate #line entries showing the origin of the definition of a macro that's been replaced, so the pre-processor was producing output from:</p>
  66.  
  67. <pre><code>  &quot;EDOM&quot; [[ EDOM ]]</code></pre>
  68.  
  69. <p>something like:</p>
  70.  
  71. <pre><code>  #line &quot;errno.c&quot;, 1
  72.  &quot;EDOM&quot; [[
  73.  #line &quot;somesystemheader&quot;, 100
  74.            33
  75.  #line &quot;errno.c&quot;, 1
  76.                ]]</code></pre>
  77.  
  78. <p>instead of the expected:</p>
  79.  
  80. <pre><code>  &quot;EDOM&quot; [[ 33 ]]</code></pre>
  81.  
  82. <p>which ext/Errno/ 's parser couldn't handle.</p>
  83.  
  84. <p>The other change was expressing compiler defined macros in hex instead of decimal.</p>]]>
  85.        <![CDATA[<p>Older versions of <span class="caps">GCC </span>define integer constants in decimal:</p>
  86.  
  87. <pre><code>  # 4.7.2
  88.  $ echo __LONG_MAX__| gcc -E -P -
  89.  9223372036854775807L</code></pre>
  90.  
  91. <p>while <span class="caps">GCC</span> 5.0 defines them in hex:</p>
  92.  
  93. <pre><code>  # 5.0
  94.  $ echo __LONG_MAX__| gcc -E -P -
  95.  0x7fffffffffffffffL</code></pre>
  96.  
  97. <p>which the h2ph parser converted to code like:</p>
  98.  
  99. <pre><code>  unless (defined &amp;__LONG_MAX__) { sub __LONG_MAX__() { &amp;0x7fffffffffffffffL } }</code></pre>
  100.  
  101. <p>because the preamble code generator didn't handle hex numbers.  The naive solution is to output:</p>
  102.  
  103. <pre><code>  unless (defined &amp;__LONG_MAX__) { sub __LONG_MAX__() { 0x7fffffffffffffff } }</code></pre>
  104.  
  105. <p>but this produces compile-time warnings when the pre-defined macros include hex constants that don't fit in a <span class="caps">UV. </span> Since the end-developer might not even be using these particular constants I changed them into run-time warnings, so the code generated for large constants becomes:</p>
  106.  
  107. <pre><code>  unless (defined &amp;__LONG_MAX__) { sub __LONG_MAX__() { hex('0x7fffffffffffffff') } }</code></pre>
  108.  
  109. <table><tr><td>Hours</td><td>Activity</td></tr><tr><td>2.08</td><td>#123011 test strange platforms to update patch</td></tr><tr><td>0.85</td><td>#123145 review</td></tr><tr><td></td><td>#123145 try to understand behaviour</td></tr><tr><td>4.96</td><td>Review 5.22 blockers, #123202</td></tr><tr><td></td><td>#123202 callgrind, review code and sprout's patch, produce</td></tr><tr><td></td><td>and test a patch, comment</td></tr><tr><td></td><td>#123202 add a test to the patch</td></tr><tr><td></td><td>#123202 review, testing</td></tr><tr><td></td><td>#123202 apply to blead</td></tr><tr><td>0.58</td><td>#123218 re-test, apply to blead and comment</td></tr><tr><td>4.60</td><td>#123554 <span class="caps">IRIX</span> 64 test issue - review mail from jhi, review code and reply</td></tr><tr><td></td><td>#123554 <span class="caps">IRIX </span>issue- review config.sh, debugging, produce a patch, mail jhi</td></tr><tr><td></td><td>#123554 more follow-up, minor patch fix, push to blead</td></tr><tr><td>0.73</td><td>#123558 fail to reproduce in blead, reproduce on reporrted</td></tr><tr><td></td><td>commit, start bisect</td></tr><tr><td>0.40</td><td>#123580 review discussion, testing, close ticket</td></tr><tr><td>0.67</td><td>#123620 review and comment</td></tr><tr><td>7.24</td><td>#123638 (security)</td></tr><tr><td></td><td>#123638 (security) updates, testing</td></tr><tr><td></td><td>#123638 (security) testing</td></tr><tr><td></td><td>#123638 comment</td></tr><tr><td></td><td>#123638 (security)</td></tr><tr><td>0.48</td><td>#123647 (security) review, testing, comment</td></tr><tr><td>0.15</td><td>#123685 review discussion</td></tr><tr><td>0.40</td><td>#123704 test and push to blead</td></tr><tr><td>0.07</td><td>#123714 review and comment</td></tr><tr><td>1.13</td><td>#123717 try to reproduce</td></tr><tr><td>1.80</td><td>#123721 review and comment</td></tr><tr><td>0.47</td><td>#123738 review, testing</td></tr><tr><td>1.37</td><td>#123739 review Tux's test code</td></tr><tr><td></td><td>#123739 debug [Tux]'s eol.t, comment and close</td></tr><tr><td>0.22</td><td>#123743 review</td></tr><tr><td>0.23</td><td>#123751 review and comment</td></tr><tr><td>0.75</td><td>#123752 comment</td></tr><tr><td></td><td>#123752 research and comment</td></tr><tr><td>1.17</td><td>#123754 (security) review, debugging</td></tr><tr><td>0.43</td><td>#123775 review discussion and comment</td></tr><tr><td>7.18</td><td>#123784 review, start gcc svn up</td></tr><tr><td></td><td>#123784 start gcc 5.0 build</td></tr><tr><td></td><td>#123784 install gcc and test, debug and produce a patch, comment</td></tr><tr><td></td><td>#123784 review discussion and patch</td></tr><tr><td></td><td>#123784 test Errno_pm.PL patch, try to resolve h2ph issue</td></tr><tr><td></td><td>#123784 testing, comment with patch</td></tr><tr><td></td><td>#123784 review discussion, adjust patch and comment</td></tr><tr><td></td><td>#123784 retest and apply to blead, perldelta, comment</td></tr><tr><td></td><td>#123784 review and test ppisar's patch, and apply to</td></tr><tr><td></td><td>blead.  Also review Gisles unticketed hp-ux hints patch and comment</td></tr><tr><td>2.72</td><td>#123786 review and comment</td></tr><tr><td></td><td>#123786 review discussion, testing, produce a fix, comment</td></tr><tr><td></td><td>with patch, create 123921</td></tr><tr><td></td><td>#123786 start bisect for blead leaks</td></tr><tr><td></td><td>#123786 review and comment</td></tr><tr><td>0.77</td><td>#123790 reproduce, try to debug</td></tr><tr><td>0.27</td><td>#123791 (security) comment with rejection</td></tr><tr><td>0.17</td><td>#123792 (security) comment with rejection</td></tr><tr><td>0.17</td><td>#123795 review and fix subject</td></tr><tr><td>1.60</td><td>#123831 review, download icc network installer and start install</td></tr><tr><td></td><td>#123831 testing with icc 15, comment</td></tr><tr><td>1.84</td><td>#123836 review, research and comment</td></tr><tr><td></td><td>#123836 make a patch</td></tr><tr><td></td><td>#123836 retest and apply to blead, comment</td></tr><tr><td>0.88</td><td>#123837 review patch, test and apply to blead, review</td></tr><tr><td></td><td>makefile.mk deps</td></tr><tr><td>0.65</td><td>#123844 review, test and apply to blead</td></tr><tr><td>0.92</td><td>#123851 review discussion and comment</td></tr><tr><td></td><td>#123851 close ticket per OP request</td></tr><tr><td>0.65</td><td>#123853 testing, research and comment</td></tr><tr><td>3.03</td><td>#123860 (security) debug, produce a patch and comment</td></tr><tr><td></td><td>#123860 write a test, update old patch and comment</td></tr><tr><td>0.90</td><td>#123865 reproduce, try to debug</td></tr><tr><td>0.32</td><td>#123866 apply to blead</td></tr><tr><td>9.20</td><td>#123879 review, review commits, prep for testing/debugging</td></tr><tr><td></td><td>#123879 fail to reproduce at various commits/build options</td></tr><tr><td></td><td>#123879 reproduce and comment</td></tr><tr><td></td><td>#123879 debugging</td></tr><tr><td></td><td>#123879 prep</td></tr><tr><td></td><td>#123879 debugging and comment</td></tr><tr><td>0.53</td><td>#123904 review and try to work out a solution</td></tr><tr><td>0.10</td><td>#123905 comment</td></tr><tr><td>0.27</td><td>#123907 research and comment</td></tr><tr><td>0.13</td><td>#123918 review dicsussion</td></tr><tr><td>0.37</td><td>#123922 finish bisect, further tests and report issue</td></tr><tr><td>0.93</td><td>#123945 encoding.pm meta ticket setup</td></tr><tr><td>0.37</td><td>#36248 review discussion, research</td></tr><tr><td>3.02</td><td>debugging path search for no-fallback popenlist</td></tr><tr><td>0.62</td><td>khw's op/pack.t failures</td></tr><tr><td>2.50</td><td>look at khw's pack.t issues</td></tr><tr><td>0.28</td><td>more <span class="caps">IPC</span>-Cmd debugging</td></tr><tr><td>0.38</td><td>open ticket on icc 15 build issues</td></tr><tr><td>2.12</td><td>remove shell fallback from multi-arg win32 popen,</td></tr><tr><td></td><td>debugging</td></tr><tr><td>0.88</td><td>review bulk88's ppport email, check for a dep issue in</td></tr><tr><td></td><td>Makefile.SH, reply</td></tr><tr><td>0.18</td><td>review OP_SIGNATURE discussion</td></tr><tr><td>0.62</td><td>review signature branch</td></tr><tr><td>0.78</td><td>try to reproduce Win32 <span class="caps">IPC</span>-Cmd failures</td></tr></table>
  110.  
  111. <p><b>76.13 hours total</b></p>]]>
  112.    </content>
  113. </entry>
  114.  
  115. <entry>
  116.    <title>Taking Part in Outreachy</title>
  117.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/03/taking-part-in-outreachy.html" />
  118.    <id>tag:news.perlfoundation.org,2015://18.3592</id>
  119.  
  120.    <published>2015-03-09T12:04:49Z</published>
  121.    <updated>2015-03-09T12:09:23Z</updated>
  122.  
  123.    <summary>I am pleased to announced that The Perl Foundation will be taking part in Outreachy, the successor of the Outreach Program for Women. The Outreach Program for Women was started by the GNOME Foundation in 2006 to encourage women to participate in the GNOME project. Since inception the project has grown to include many Free and Open Source organisations, including The Perl Foundation, and now the program has been rebranded and extended to encourage the participation of all underrepresented groups....</summary>
  124.    <author>
  125.        <name>Karen Pauley</name>
  126.        <uri>http://martian.org/karen</uri>
  127.    </author>
  128.    
  129.        <category term="OPW" scheme="http://www.sixapart.com/ns/types#category" />
  130.    
  131.    <category term="internship" label="internship" scheme="http://www.sixapart.com/ns/types#tag" />
  132.    <category term="outreachy" label="outreachy" scheme="http://www.sixapart.com/ns/types#tag" />
  133.    
  134.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  135.        <![CDATA[<p>I am pleased to announced that The Perl Foundation will be taking part in <a href="https://www.gnome.org/outreachy/">Outreachy</a>, the successor of the Outreach Program for Women.  </p>
  136.  
  137. <p>The Outreach Program for Women was started by the <span class="caps">GNOME</span> Foundation in 2006 to encourage women to participate in the <span class="caps">GNOME </span>project.  Since inception the project has grown to include many Free and Open Source organisations, including The Perl Foundation,  and now the program has been rebranded and extended to encourage the participation of all underrepresented groups.</p>
  138.  
  139. <p>We are offering one full-time internship in the summer program which will run from May 25th to August 25th.  The application process is <a href="https://outreachy.gnome.org/?q=program_home&amp;prg=4">now open</a> and applications need to be submitted by March 24th.</p>
  140.  
  141. <p>We have mentors from Dancer signed up to provide projects ideas and you can read about the possible projects on our <a href="http://www.perlfoundation.org/outreachy">information page</a>.</p>]]>
  142.        
  143.    </content>
  144. </entry>
  145.  
  146. <entry>
  147.    <title>Grant Extension Request: Maintaining Perl 5</title>
  148.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/03/grant-extension-request-mainta-1.html" />
  149.    <id>tag:news.perlfoundation.org,2015://18.3590</id>
  150.  
  151.    <published>2015-03-05T11:51:32Z</published>
  152.    <updated>2015-03-05T11:58:42Z</updated>
  153.  
  154.    <summary>Tony Cook has requested an extension of $20,000 for his Maintaining Perl 5 grant. This grant has been running successfully since July 2013. The requested extension would allow Tony to devote another 400 hours to the project. The funds for this extension would come from the Perl 5 Core Maintenance Fund. As well as posting reports on the p5p mailing list Tony provides detailed monthly reports, the most recent of which can be found in the following blog posts: January...</summary>
  155.    <author>
  156.        <name>Karen Pauley</name>
  157.        <uri>http://martian.org/karen</uri>
  158.    </author>
  159.    
  160.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  161.    
  162.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  163.    
  164.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  165.        <![CDATA[<p>Tony Cook has requested an extension of $20,000 for his <a href="http://news.perlfoundation.org/2013/05/grant-application-maintaining.html">Maintaining Perl 5</a> grant. This grant has been running successfully since July 2013. The requested extension would allow Tony to devote another 400 hours to the project. The funds for this extension would come from the <a href="http://www.perlfoundation.org/perl_5_core_maintenance_fund">Perl 5 Core Maintenance Fund</a>.</p>
  166.  
  167. <p>As well as posting reports on the p5p mailing list Tony provides detailed monthly reports, the most recent of which can be found in the following blog posts:</p>
  168.  
  169. <p><a href="http://news.perlfoundation.org/2015/03/maintaining-perl-5-grant-repor-14.html">January 2015</a><br />
  170. <a href="http://news.perlfoundation.org/2015/02/maintaing-perl-5-grant-report-1.html">December 2014</a><br />
  171. <a href="http://news.perlfoundation.org/2015/01/maintaing-perl-5-grant-report.html">November 2014</a></p>
  172.  
  173. <p>Before we make a decision on this extension we would like to have a period of community consultation that will last for seven days. Please leave feedback in the comments or, if you prefer, email your comments to karen at perlfoundation.org.</p>]]>
  174.        
  175.    </content>
  176. </entry>
  177.  
  178. <entry>
  179.    <title>Maintaining Perl 5: Grant Report for January 2015</title>
  180.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/03/maintaining-perl-5-grant-repor-14.html" />
  181.    <id>tag:news.perlfoundation.org,2015://18.3588</id>
  182.  
  183.    <published>2015-03-04T09:40:40Z</published>
  184.    <updated>2015-03-04T09:53:03Z</updated>
  185.  
  186.    <summary>Tony Cook writes: Approximately 61 tickets were reviewed or worked on, and 11 patches were applied. There were no especially interesting tickets this month. HoursActivity1.60cpan #101078 create/test bisect script and start bisectcpan #101078 review bisect results, comment0.27#120357 (security) research and comment0.52#122432 review status#122432 summarize status of cpan dists2.25#122443 testing, polish1.48#122730 bang head against dzil, try some simple fixes,create github issue0.20#123065 apply to blead...</summary>
  187.    <author>
  188.        <name>Karen Pauley</name>
  189.        <uri>http://martian.org/karen</uri>
  190.    </author>
  191.    
  192.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  193.    
  194.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  195.    
  196.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  197.        <![CDATA[<p><em>Tony Cook writes:</em></p>
  198.  
  199. <p>Approximately 61 tickets were reviewed or worked on, and 11 patches were applied.</p>
  200.  
  201. <p>There were no especially interesting tickets this month.</p>
  202.  
  203. <table><tr><td>Hours</td><td>Activity</td></tr><tr><td>1.60</td><td>cpan #101078 create/test bisect script and start bisect</td></tr><tr><td></td><td>cpan #101078 review bisect results, comment</td></tr><tr><td>0.27</td><td>#120357 (security) research and comment</td></tr><tr><td>0.52</td><td>#122432 review status</td></tr><tr><td></td><td>#122432 summarize status of cpan dists</td></tr><tr><td>2.25</td><td>#122443 testing, polish</td></tr><tr><td>1.48</td><td>#122730 bang head against dzil, try some simple fixes,</td></tr><tr><td></td><td>create github issue</td></tr><tr><td>0.20</td><td>#123065 apply to blead</td></tr></table>]]>
  204.        <![CDATA[<table><tr><td>0.83</td><td>#123218 produce a patch</td></tr><tr><td>0.15</td><td>#123315 comment</td></tr><tr><td>2.13</td><td>#123341 testing, review code and comment</td></tr><tr><td>2.78</td><td>#123394 review, cleanup, testing, push to blead</td></tr><tr><td></td><td>#123394 review discussion and comment</td></tr><tr><td>2.52</td><td>#123413 review latest patch, look into sdbm history,</td></tr><tr><td></td><td>comment</td></tr><tr><td></td><td>#123413 review, testing, fixes, push to blead, comment</td></tr><tr><td>0.23</td><td>#123437 review and comment</td></tr><tr><td>0.58</td><td>#123443 look for similar write() bug and work on fix</td></tr><tr><td>0.18</td><td>#123512 review and comment</td></tr><tr><td>1.17</td><td>#123528 review patch, discussion of win32 GetVersionEx()</td></tr><tr><td></td><td>behaviour</td></tr><tr><td>1.03</td><td>#123532 testing, review code, comment</td></tr><tr><td>3.03</td><td>#123538 diagnose, produce a patch, comment</td></tr><tr><td></td><td>#123538 test, apply to blead, check 123622 and lots of</td></tr><tr><td></td><td>win32 test failure code in between</td></tr><tr><td>3.34</td><td>#123542 reproduce, debugging, try to reduce test case</td></tr><tr><td></td><td>#123542 reduce test case size, try to understand the parser</td></tr><tr><td>0.67</td><td>#123549 review, research, testing, comment</td></tr><tr><td>1.60</td><td>#123551 try to work out afl-gcc/blead build issues</td></tr><tr><td>4.00</td><td>#123554 diagnose, debugging and comment</td></tr><tr><td></td><td>#123554 produce a better patch, checking code, comment</td></tr><tr><td></td><td>#123554 review, re-test and apply to blead</td></tr><tr><td>0.57</td><td>#123555 review, research and comment</td></tr><tr><td></td><td>#123555 review discussion and mark as rejected</td></tr><tr><td>0.33</td><td>#123562 try to understand code</td></tr><tr><td>1.52</td><td>#123566 review, testing, apply to blead and comment</td></tr><tr><td>0.45</td><td>#123575 review, testing</td></tr><tr><td>0.50</td><td>#123580 review discussion</td></tr><tr><td>0.22</td><td>#123585 review ticket and code</td></tr><tr><td>0.97</td><td>#123591, 123538, test, add tests to 123538 patch</td></tr><tr><td>1.84</td><td>#123599 research and comment</td></tr><tr><td></td><td>#123599 follow-up comment</td></tr><tr><td>0.45</td><td>#123600 review smoke results, re-test and push to blead</td></tr><tr><td>0.25</td><td>#123605 review, test and apply to blead</td></tr><tr><td>0.83</td><td>#123606 review, test, apply to blead and comment</td></tr><tr><td>0.53</td><td>#123620 review and briefly comment</td></tr><tr><td></td><td>#123620 review</td></tr><tr><td>1.13</td><td>#123632 review, check history/usage of Opcode, comment</td></tr><tr><td></td><td>#123632 test and apply to blead</td></tr><tr><td>0.52</td><td>#123634 review, test and apply to blead</td></tr><tr><td>0.20</td><td>#123635 review discussion and patch and reject</td></tr><tr><td>6.96</td><td>#123638 (security) review, discussion, attempt to fix</td></tr><tr><td></td><td>#123638 debugging</td></tr><tr><td></td><td>#123638 code review</td></tr><tr><td></td><td>#123638 testing</td></tr><tr><td>0.40</td><td>#123658 review discussion and patch, comment</td></tr><tr><td>1.79</td><td>#123672 review, find problem not in v5.14, start bisect</td></tr><tr><td></td><td>#123672 fix bisect</td></tr><tr><td>0.40</td><td>#123675 review discussion, research, comment</td></tr><tr><td>1.05</td><td>#123677 try to debug</td></tr><tr><td>0.35</td><td>#123682 review and briefly comment</td></tr><tr><td>1.30</td><td>#123683 try to visually track down commit, leont beats me</td></tr><tr><td></td><td>to commenting, start bisect</td></tr><tr><td>0.35</td><td>#123689 comment</td></tr><tr><td>0.40</td><td>#123693 review patch and comment</td></tr><tr><td>0.47</td><td>#36248 try to understand cause and boggle at encoding.pm</td></tr><tr><td>0.97</td><td>64-bit gcc/win32 build issue</td></tr><tr><td>3.18</td><td>check out recent gcc Win32 build issues</td></tr><tr><td>1.30</td><td>cygwin op/repeat.t issue</td></tr><tr><td>1.28</td><td>fix <span class="caps">SDBM</span>_File build on gcc/win32</td></tr><tr><td>1.35</td><td>look into Win32 test failures, reproduce, start bisect</td></tr><tr><td>0.83</td><td>More 5.20.2</td></tr><tr><td>0.95</td><td>more gcc Win32</td></tr><tr><td>0.52</td><td>Plack-App-PHPCGI setup</td></tr><tr><td>2.68</td><td>Review 5.20.2 votes list</td></tr><tr><td>0.55</td><td>review and comment on character/bin data thread</td></tr><tr><td>1.40</td><td>review bisect result and fix bisect code</td></tr><tr><td>0.40</td><td>review maint-5.20 votes</td></tr><tr><td>0.45</td><td>win32 sdbm issues</td></tr><tr><td>0.32</td><td>win32 test failure</td></tr><tr><td>2.83</td><td>win32 unthreaded sdbm_file build issues, discussion,</td></tr><tr><td></td><td>diagnosis, fix, testing</td></tr></table>
  205.  
  206. <p><b>73.35 Hours Total</b></p>]]>
  207.    </content>
  208. </entry>
  209.  
  210. <entry>
  211.    <title>Call For Grant Proposals (March 2015 Round)</title>
  212.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/03/call-for-grant-proposals-march.html" />
  213.    <id>tag:news.perlfoundation.org,2015://18.3586</id>
  214.  
  215.    <published>2015-03-02T23:00:00Z</published>
  216.    <updated>2015-03-03T04:41:36Z</updated>
  217.  
  218.    <summary>The Grants Committee is accepting grant proposals all the time. We evaluate them every two months and another evaluation period has come. If you have an idea for doing some Perl work that will benefit the Perl community, consider sending a grant application. The application deadline for this round is 23:59 March 15th UTC. We will publish the received applications, get community feedback and conclude the acceptance by March 30th. To apply, please read How to Write a Proposal. Rules...</summary>
  219.    <author>
  220.        <name>Makoto Nozaki</name>
  221.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  222.    </author>
  223.    
  224.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  225.    
  226.    
  227.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  228.        <![CDATA[<p>The Grants Committee is accepting grant proposals all the time.  We evaluate them every two months and another evaluation period has come.</p>
  229.  
  230. <p>If you have an idea for doing some Perl work that will benefit the Perl community, consider sending a grant application. <strong>The application deadline for this round is 23:59 March 15th UTC.</strong> We will publish the received applications, get community feedback and conclude the acceptance by March 30th.</p>
  231.  
  232. <p>To apply, please read <a href="http://www.perlfoundation.org/how_to_write_a_proposal">How to Write a Proposal</a>.  <a href="http://www.perlfoundation.org/rules_of_operation">Rules of Operation</a>
  233. will also help you understand how the grant process works. For those who are familiar with the process, the format will be the same as the previous rounds in 2014-2015.</p>
  234.  
  235. <p>We will confirm the receipt of application within 24 hours.</p>
  236.  
  237. <p>If you have further questions, please comment here.  If your comment
  238. does not show up here within 24 hours, the chances are that the spam
  239. filter did something bad. Get in touch with me at tpf-grants-secretary
  240. at perl-foundation.org.</p>
  241. ]]>
  242.        
  243.  
  244.    </content>
  245. </entry>
  246.  
  247. <entry>
  248.    <title>YAPC::NA::2015 Hackathons Announced</title>
  249.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/02/yapcna2015-hackathons-announce.html" />
  250.    <id>tag:news.perlfoundation.org,2015://18.3584</id>
  251.  
  252.    <published>2015-02-26T13:51:34Z</published>
  253.    <updated>2015-02-26T14:26:49Z</updated>
  254.  
  255.    <summary>The Perl Foundation is excited to announce three hackathons that will be running sequentially with YAPC::NA 2015 in Salt Lake City this June. These events include a Perl 6 hackathon with Perl creator Larry Wall to be held on June 11th.
  256. </summary>
  257.    <author>
  258.        <name>TPF Conferences Staff</name>
  259.        
  260.    </author>
  261.    
  262.        <category term="Conferences" scheme="http://www.sixapart.com/ns/types#category" />
  263.    
  264.        <category term="Hackathons" scheme="http://www.sixapart.com/ns/types#category" />
  265.    
  266.        <category term="Marketing" scheme="http://www.sixapart.com/ns/types#category" />
  267.    
  268.        <category term="Perl 6 Development" scheme="http://www.sixapart.com/ns/types#category" />
  269.    
  270.    
  271.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  272.        <![CDATA[<p>The Perl Foundation is excited to announce three hackathons that will be running sequentially with <span class="caps">YAPC</span>::NA 2015 in Salt Lake City this June. These events include a Perl 6 hackathon with Perl creator Larry Wall to be held on June 11th. </p>
  273.  
  274. <p>The cost to attend these three hackathons is included in all <span class="caps">YAPC</span>::NA 2015 passes, but we do encourage you to <span class="caps">RSVP </span>online so we know how many to expect. Putting on these events is not cheap! Along with being able to attend each hackathon, we will also be providing rooms, wi-fi, and snacks throughout the day. So we would appreciate your help! To help cover these costs, we have a suggested donation of $50 per day, which you can make during your online registration. </p>
  275.  
  276. <p>Each hackathon listed will run from 9:00 am until 6:00 pm. We will provide snacks and drinks, but you will be on your own for lunch.</p>
  277.  
  278. <p>This year's hackathons will be:</p>
  279.  
  280. <h3>Sunday, June 7th 2015:  Pull request hackathon</h3>
  281.  
  282. <p>Come join your fellow Perl developers for a day of bug squashing and developing as you participate in the 2015 <span class="caps">CPAN</span> Pull Request Challenge. Or, bring your own pet project and just enjoy a day of hacking amongst your like-minded peers.</p>
  283.  
  284. <h3>Thursday, June 11th 2015:  Perl 6 hackathon with Larry Wall</h3>
  285.  
  286. <p>Come spend an entire day working on the next generation of Perl. There's no better way to learn it than to do it! Perl creator, Larry Wall will be on hand throughout the day.</p>
  287.  
  288. <h3>Friday, June 12th 2015: Hardware hackathon</h3>
  289.  
  290. <p>Get up to your armpits in Arduino!  Bring your own toys or come check out some of ours. It's time to get creative and see what you can make.</p>
  291.  
  292. <p>We look forward to seeing you! Please take a moment to register on the <span class="caps">YAPC </span>site: <a href="http://www.yapcna.org/yn2015/purchase">http://www.yapcna.org/yn2015/purchase</a>   </p>]]>
  293.        
  294.    </content>
  295. </entry>
  296.  
  297. <entry>
  298.    <title>Ricardo Signes Grant Application Successful </title>
  299.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/02/ricardo-signes-grant-applicati.html" />
  300.    <id>tag:news.perlfoundation.org,2015://18.3582</id>
  301.  
  302.    <published>2015-02-26T08:33:06Z</published>
  303.    <updated>2015-02-26T09:06:45Z</updated>
  304.  
  305.    <summary>I am pleased to announce that Ricardo Signes&apos; recent grant application to cover the costs of his travel to the QA Hackathon has been successful. I would like to thank everyone who provided feedback on this grant. The grant was awarded from our Perl 5 Core Maintenance Fund. If you wish to contribute to this fund please go to our donation system or contact karen [a] perlfoundation.org The QA Hackathon is a free of charge coding workshop for people involved...</summary>
  306.    <author>
  307.        <name>Karen Pauley</name>
  308.        <uri>http://martian.org/karen</uri>
  309.    </author>
  310.    
  311.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  312.    
  313.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  314.    
  315.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  316.        <![CDATA[<p>I am pleased to announce that Ricardo Signes' recent grant application to cover the costs of his travel to the <a href="http://act.qa-hackathon.org/qa2015/">QA Hackathon</a> has been successful. I would like to thank everyone who provided feedback on this grant.</p>
  317.  
  318. <p>The grant was awarded from our <a href="http://www.perlfoundation.org/perl_5_core_maintenance_fund">Perl 5 Core Maintenance Fund</a>. If you wish to contribute to this fund please go to our donation system or contact karen [a] perlfoundation.org</p>
  319.  
  320. <p>The <a href="http://act.qa-hackathon.org/qa2015/">QA Hackathon</a> is a free of charge coding workshop for people involved in Quality Assurance, testing, packaging, <span class="caps">CPAN, </span>and other quality assurance projects. It is taking place in Berlin, Germany, from the 16th to the 19th April.</p>]]>
  321.        
  322.    </content>
  323. </entry>
  324.  
  325. <entry>
  326.    <title>Maintaining the Perl 5 Core: Report, Month 16</title>
  327.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/02/maintaining-the-perl-5-core-re-14.html" />
  328.    <id>tag:news.perlfoundation.org,2015://18.3580</id>
  329.  
  330.    <published>2015-02-17T05:24:21Z</published>
  331.    <updated>2015-02-17T05:29:26Z</updated>
  332.  
  333.    <summary>Dave Mitchell writes: At the start of the month I continued work on making the stderr of builds less noisy, and for blead to build, test, and be stderr-clean under ASan -fsanitize=undefined. At the end of this work I raised around 26 RT and github tickets with fixes for cpan/ distributions; currently around 9 of these have been merged back into blead and a further 4 have been merged upstream but not yet released. For the rest of the month...</summary>
  334.    <author>
  335.        <name>Karen Pauley</name>
  336.        <uri>http://martian.org/karen</uri>
  337.    </author>
  338.    
  339.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  340.    
  341.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  342.    
  343.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  344.        <![CDATA[<p><em>Dave Mitchell writes:</em></p>
  345.  
  346. <p>At the start of the month I continued work on making the stderr of builds less noisy, and for blead to build, test, and be stderr-clean under ASan -fsanitize=undefined.</p>
  347.  
  348. <p>At the end of this work I raised around 26 RT and github tickets with fixes for cpan/ distributions; currently around 9 of these have been merged back into blead and a further 4 have been merged upstream but not yet released.</p>
  349.  
  350. <p>For the rest of the month I spent a bit of time on a few RT tickets and tried to keep with my p5p mailbox.</p>
  351.  
  352. <p><b>Summary</b></p>
  353.  
  354. <blockquote><p>2:52 [Win32] Unable to build 64-bit 5.21.7<br />
  355. 1:50 [perl #123469] Bug in split function, with utf8 strings<br />
  356. 3:30 [perl #123609] Unexpected warning compiling array subscript<br />
  357. 2:00 [perl #123685] Question regarding the '#!' argument passing.<br />
  358. 13:30 process p5p mailbox<br />
  359. 6:08 reduce amount of stderr stuff in build/test<br />
  360. ------<br />
  361. <b>29:50 Total (HH::MM)</b></p></blockquote>
  362.  
  363. <p>As of 2015/01/31: since the beginning of the grant:</p>
  364.  
  365. <blockquote><p>68.0 weeks<br />
  366. 913.1 total hours<br />
  367. 13.4 average hours per week</p></blockquote>
  368.  
  369. <p>There are 287 hours left on the grant</p>]]>
  370.        
  371.    </content>
  372. </entry>
  373.  
  374. <entry>
  375.    <title>Call for Master Classes</title>
  376.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/02/call-for-master-classes.html" />
  377.    <id>tag:news.perlfoundation.org,2015://18.3578</id>
  378.  
  379.    <published>2015-02-09T11:25:45Z</published>
  380.    <updated>2015-02-13T02:02:25Z</updated>
  381.  
  382.    <summary>Are you an experienced Perl instructor who would like to offer a
  383. course at YAPC:NA this year in Salt Lake City?  We want to offer the
  384. Perl community a selection of courses and tutorials before and after
  385. the conference.</summary>
  386.    <author>
  387.        <name>TPF Conferences Staff</name>
  388.        
  389.    </author>
  390.    
  391.        <category term="Conferences" scheme="http://www.sixapart.com/ns/types#category" />
  392.    
  393.    
  394.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  395.        <![CDATA[<p>Are you an experienced Perl instructor who would like to offer a<br />
  396. course at <span class="caps">YAPC</span>:NA this year in Salt Lake City?  We want to offer the<br />
  397. Perl community a selection of courses and tutorials before and after<br />
  398. the conference.</p>
  399.  
  400. <p>Master Classes can be a half day (3 hours), full day (6 hours) or 2<br />
  401. days in length and will run on Sunday 7th, Thursday 11th, and Friday<br />
  402. 12th of June.</p>
  403.  
  404. <p>To submit your proposal please send the following information to<br />
  405. <a href="mailto:%74%61%6C%6B%73%40%79%61%70%63%6E%61%2E%6F%72%67">talks@yapcna.org</a></p>
  406.  
  407.  
  408.  
  409. <ul>
  410. <li>Class Title</li>
  411. <li>Names of Speakers</li>
  412. <li>Speaker Biography</li>
  413. <li>Abstract</li>
  414. <li>Class Description, including<br />
  415.          the course's length<br />
  416.          the intended audience<br />
  417.          any prerequisites or expected level of knowledge<br />
  418.          any supplies you will be providing to students<br />
  419.          any supplies you expect students to bring<br />
  420.          a short course outline<br />
  421.          maximum class size</li>
  422. <li>The dates on which you would be willing to give your course (June 7th, 11th, 12th)</li>
  423. <li>A list of requirements for the venue (A/V, Internet, etc.)</li>
  424. <li>Cost of the Class</li>
  425. </ul>
  426.  
  427.  
  428.  
  429. <p>Please bear in mind that it is our goal to keep the cost of these<br />
  430. classes down for students as this is a low cost conference.</p>]]>
  431.        
  432.    </content>
  433. </entry>
  434.  
  435. <entry>
  436.    <title>Perl 5 Grant Application: Travel to QA Hackathon</title>
  437.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/02/we-have-received-the-following.html" />
  438.    <id>tag:news.perlfoundation.org,2015://18.3576</id>
  439.  
  440.    <published>2015-02-08T07:42:48Z</published>
  441.    <updated>2015-02-08T07:57:27Z</updated>
  442.  
  443.    <summary>We have received the following Perl 5 grant application from Ricardo Signes. Before we vote on this proposal we would like to have a period of community consultation that will last seven days. Please leave feedback in the comments or if you prefer send email with your comments to karen at perlfoundation.org. Name: Ricardo Signes Project Title: Perl QA Hackathon 2015 Amount Requested: $1200 Synopsis This grant will be used to pay for travel for Ricardo Signes to and from...</summary>
  444.    <author>
  445.        <name>Karen Pauley</name>
  446.        <uri>http://martian.org/karen</uri>
  447.    </author>
  448.    
  449.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  450.    
  451.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  452.    
  453.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  454.        <![CDATA[<p>We have received the following Perl 5 grant application from Ricardo Signes.</p>
  455.  
  456. <p>Before we vote on this proposal we would like to have a period of community consultation that will last seven days. Please leave feedback in the comments or if you prefer send email with your comments to karen at perlfoundation.org.</p>
  457.  
  458. <p><b>Name:</b> Ricardo Signes</p>
  459.  
  460. <p><b>Project Title:</b> Perl QA Hackathon 2015</p>
  461.  
  462. <p><b>Amount Requested</b>: $1200</p>
  463.  
  464. <p><b>Synopsis</b></p>
  465.  
  466. <p>This grant will be used to pay for travel for Ricardo Signes to and from the Perl QA Hackathon held in Berlin in Q1 2015.</p>
  467.  
  468. <p><b>Benefits to Perl 5</b></p>
  469.  
  470. <p>I have attended six of the seven Perl QA Hackathons (Oslo, Birmingham, Amsterdam, Paris, Lancaster, and Lyon) and have, at each of them, been able to contribute several solid work days of very productive work to the infrastructure behind the <span class="caps">CPAN </span>and related tools.  Specifically, I was one of the chief implementors of the new <span class="caps">CPAN</span> Testers platform (Metabase) and built the Fake <span class="caps">CPAN </span>system for testing <span class="caps">CPAN </span>tools, and several reusable software libraries that are used to power both Metabase and Fake <span class="caps">CPAN. </span> In 2012, I worked on refactoring <span class="caps">PAUSE, </span>adding tests and improving maintainability. <span class="caps">PAUSE, </span>the system which processes contributor uploads to the <span class="caps">CPAN, </span>manages <span class="caps">CPAN </span>contributor identity, and builds the <span class="caps">CPAN </span>indexes used by <span class="caps">CPAN </span>clients to locate libraries for installation.</p>
  471.  
  472. <p>In previous years, I also spent a significant amount of time working with other attendees on their contributions, and plan to do the same this year. This is one of the several reasons that attendance in person is incomparably superior to "virtual attendance."</p>
  473.  
  474. <p><b>Deliverable Elements</b></p>
  475.  
  476. <p>The QA Hackathon does not have a set agenda, so promising specific work product<br />
  477. from it up front seems unwise. I have detailed, above, the sort of work that I am almost certain to do, however. Further, I will provide a public, written report of my activities at the Hackathon.</p>
  478.  
  479. <p>I hope, in particular, to work on the web code of <span class="caps">PAUSE </span>and to discuss mechanisms for improving collaborative code review within the community of toolchain maintainers.</p>
  480.  
  481. <p>The hackathon takes place over the course of four days, with eight to ten hour workdays.  I'll  probably also be working on the travel and in the evenings.</p>
  482.  
  483. <p>Any software that I produce will be released under the Perl 5 standard license terms, or possibly even less restrictive terms.</p>
  484.  
  485. <p><b>Applicant Biography</b></p>
  486.  
  487. <p>I have been building software in Perl professionally for about fifteen years. I am a frequent contributor of original software to the <span class="caps">CPAN </span>and a frequent contributor to, or maintainer of, other popular <span class="caps">CPAN </span>libraries. I am also a contributor to the core Perl 5 project, and its current project lead.</p>
  488.  
  489. <p>I have been the recipient of <span class="caps">TPF </span>grants five times before, all of which were successful.</p>]]>
  490.        
  491.    </content>
  492. </entry>
  493.  
  494. <entry>
  495.    <title>Maintaining Perl 5: Grant Report for December 2014</title>
  496.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/02/maintaing-perl-5-grant-report-1.html" />
  497.    <id>tag:news.perlfoundation.org,2015://18.3574</id>
  498.  
  499.    <published>2015-02-03T06:25:34Z</published>
  500.    <updated>2015-02-09T11:22:44Z</updated>
  501.  
  502.    <summary>Tony Cook writes: Approximately 36 tickets were reviewed, and 5 patches were applied. I spent some time this month working on getting minitest working on Win32. In 2004 the Win32 makefiles were changed to use harness instead of TEST for minitest, presumably at some time after that Test::Harness was changed to load IO unconditionally, breaking minitest on Win32. So I switched minitest back to using TEST and then worked through the failing tests to resolve their failures. See [perl #123394]...</summary>
  503.    <author>
  504.        <name>Karen Pauley</name>
  505.        <uri>http://martian.org/karen</uri>
  506.    </author>
  507.    
  508.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  509.    
  510.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  511.    
  512.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  513.        <![CDATA[<p><em>Tony Cook writes:</em></p>
  514.  
  515. <p>Approximately 36 tickets were reviewed, and 5 patches were applied.</p>
  516.  
  517. <p>I spent some time this month working on getting minitest working on Win32.</p>
  518.  
  519. <p>In 2004 the Win32 makefiles were changed to use harness instead of <span class="caps">TEST </span>for minitest, presumably at some time after that Test::Harness was changed to load IO unconditionally, breaking minitest on Win32.</p>
  520.  
  521. <p>So I switched minitest back to using <span class="caps">TEST </span>and then worked through the failing tests to resolve their failures.  See [perl #123394] for details.</p>]]>
  522.        <![CDATA[<table><tr><td>Hours</td><td>Activity</td></tr><tr><td>1.75</td><td>#108276 debugging, try some extra assertions</td></tr><tr><td>2.82</td><td>#122287 setup to build on omnios, reproduce failure, try</td></tr><tr><td></td><td>patch, test patch on other dtrace platforms, fails on OS X</td></tr><tr><td>0.50</td><td>#122635 apply to blead fixing merge, re-test, bump all modules</td></tr><tr><td>0.32</td><td>#123063 re-test patch and apply to blead</td></tr><tr><td>2.28</td><td>#123065 review, testing, start documentation, start 32-bit iv build</td></tr><tr><td></td><td>#123065 copy/adapt to other big*, testing</td></tr><tr><td></td><td>#123065 polish, comment with patch</td></tr><tr><td>0.48</td><td>#123105 review</td></tr><tr><td>5.03</td><td>#123245 review, try to understand code, start bisect</td></tr><tr><td></td><td>#123245 debugging</td></tr><tr><td></td><td>#123245 produce fix and comment</td></tr><tr><td></td><td>#123245 have trouble reproducing, put test together</td></tr><tr><td></td><td>#123245 review test results, push to blead, close</td></tr><tr><td>0.63</td><td>#123266 review, test on non glibc and glibc, push to blead</td></tr><tr><td>0.78</td><td>#123312 review -V output, research local::lib and comment</td></tr><tr><td></td><td>#123312 review latest response and close</td></tr><tr><td>0.40</td><td>#123333 reproduce, review, test and apply to blead</td></tr><tr><td>0.25</td><td>#123345 review tie documentation and implementation</td></tr><tr><td>0.25</td><td>#123353 review, test, apply to blead</td></tr><tr><td>1.22</td><td>#123359 review patch, unrelated #p5p file locking discussion, comment</td></tr><tr><td>2.82</td><td>#123364 reproduce, debugging</td></tr><tr><td></td><td>#123364 code review, debugging, comment</td></tr><tr><td>1.99</td><td>#123394 comment</td></tr><tr><td></td><td>#123394 testing, adjusting patches based on comments</td></tr><tr><td>0.97</td><td>#123398 merge duplicate ticket, test, think about a fix, comment</td></tr><tr><td></td><td>#123398 comment</td></tr><tr><td>0.70</td><td>#123402 review, testing, comment</td></tr><tr><td>0.33</td><td>#123413 review discussion and comment</td></tr><tr><td>1.08</td><td>#123415 review, research and comment</td></tr><tr><td></td><td>#123415 review and comment</td></tr><tr><td>1.15</td><td>#123418 review, testing, push to blead, perldelta</td></tr><tr><td>7.62</td><td>#123443 review, produce a patch, see a possible issue in seek code too</td></tr><tr><td></td><td>#123443 re-review size patch, comment with patches</td></tr><tr><td></td><td>#123443 re-test and apply to blead</td></tr><tr><td></td><td>#123443 try to reproduce jenkins win32 failure, reproduce,</td></tr><tr><td></td><td>learn too much about PerlIO and fix</td></tr><tr><td>2.10</td><td>#81074 review latest discussion, code, consider new solution</td></tr><tr><td>0.50</td><td>#9319 review discussion</td></tr><tr><td>0.15</td><td>fix g++ builds</td></tr><tr><td>0.17</td><td>investigate jenkins failure, sprout fixes before I can push</td></tr><tr><td>2.67</td><td>more minitest, consistent build options, test failure diagnosis</td></tr><tr><td>0.53</td><td>research and comment on khw's uudecode thread</td></tr><tr><td>1.05</td><td>research, reply bulk88's malloc email</td></tr><tr><td>0.65</td><td>try to fix minitest on Win32</td></tr><tr><td>0.33</td><td>try to reproduce rjbs's OS X test failures</td></tr><tr><td>2.33</td><td>try to reproduce rjbs's OS X test failures some more,</td></tr><tr><td></td><td>track down deparse noise</td></tr><tr><td>0.55</td><td>update Data::Dumper documentation as useqq no longer</td></tr><tr><td></td><td>forces pure-perl</td></tr><tr><td>2.57</td><td>win32 minitest - clean up commits, op/coreamp.t</td></tr><tr><td>3.70</td><td>win32 minitest - finish coreamp.t, fork.t, filetest.t,</td></tr><tr><td></td><td>op/glob.t, op/magic.t, more op/glob.t</td></tr><tr><td>1.25</td><td>win32 minitest - fix minitest rules to match</td></tr><tr><td></td><td>Makefile.SH, run/switches.t, cross-platform testing,</td></tr><tr><td></td><td>create ticket 123394</td></tr><tr><td>2.67</td><td>win32 minitest - more op/glob.t, fail, clean up commits</td></tr></table>
  523.  
  524. <p><b>54.59 Hours Total</b></p>]]>
  525.    </content>
  526. </entry>
  527.  
  528. <entry>
  529.    <title>Perl::Lint Bug Fixes and New Policies</title>
  530.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/02/perllint-bug-fixes-and-new-pol.html" />
  531.    <id>tag:news.perlfoundation.org,2015://18.3572</id>
  532.  
  533.    <published>2015-02-01T09:54:36Z</published>
  534.    <updated>2015-02-01T10:13:28Z</updated>
  535.  
  536.    <summary>Last week Taiki released version 0.11 of Perl::Lint to CPAN. This new version fixes several bugs reported after Perl::Lint&apos;s release in November. Taiki has not achieved everything outlined in his grant proposal: implementing some of Perl::Lint&apos;s policies has been much harder than expected. However, Perl::Lint provides a useful tool for analysing Perl source code. So, The Perl Foundation&apos;s grants committee would like to treat this grant as successfully completed soon. As usual, we welcome comments on this grant from the...</summary>
  537.    <author>
  538.        <name>Tom Hukins</name>
  539.        
  540.    </author>
  541.    
  542.    
  543.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  544.        <![CDATA[<p>Last week Taiki released <a href="https://metacpan.org/release/MOZNION/Perl-Lint-0.11">version 0.11 of Perl::Lint</a> to <span class="caps">CPAN.</span></p>
  545.  
  546. <p>This new version fixes several bugs reported after <a href="http://news.perlfoundation.org/2014/11/perllint-released.html">Perl::Lint's release</a> in November.</p>
  547.  
  548. <p>Taiki has not achieved everything outlined in his <a href="http://news.perlfoundation.org/2014/03/grant-proposal-perllint---yet.html">grant proposal</a>: implementing some of Perl::Lint's policies has been much harder than expected.  However, Perl::Lint provides a useful tool for analysing Perl source code.  So, The Perl Foundation's grants committee would like to treat this grant as successfully completed soon.</p>
  549.  
  550. <p>As usual, we welcome comments on this grant from the Perl community.</p>]]>
  551.        
  552.    </content>
  553. </entry>
  554.  
  555. <entry>
  556.    <title>January 2015 Grant Votes</title>
  557.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/01/january-2015-grant-votes.html" />
  558.    <id>tag:news.perlfoundation.org,2015://18.3570</id>
  559.  
  560.    <published>2015-01-31T17:00:00Z</published>
  561.    <updated>2015-01-31T22:20:40Z</updated>
  562.  
  563.    <summary>The Grants Committee has concluded the voting of the January round. Proposal in this round Ado - a rapid active commotion (framework for web-projects on Mojolicious), Krasimir Berov, USD 4,500 Voting Results TitleYesNoScore Ado14 Definition of the score is found in 3.2 of the rules. Details While it is always difficult to make decision on grant proposals, this was a particularly tough one. We understand this is a serious project with good amount of interest from the community including multiple...</summary>
  564.    <author>
  565.        <name>Makoto Nozaki</name>
  566.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  567.    </author>
  568.    
  569.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  570.    
  571.    
  572.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  573.        <![CDATA[<p>The Grants Committee has concluded the voting of the January round.</p>
  574.  
  575. <h3>Proposal in this round</h3>
  576.  
  577. <ul>
  578. <li><a href="http://news.perlfoundation.org/2015/01/grant-proposal-ado---a-rapid-a.html">Ado - a rapid active commotion (framework for web-projects on Mojolicious)</a>, Krasimir Berov, USD 4,500</li>
  579. </ul>
  580.  
  581. <h3>Voting Results</h3>
  582.  
  583. <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>
  584. <tr><td>Ado<td style="text-align:right">1<td style="text-align:right">4<td><br>
  585. </table></p>
  586.  
  587. <p>Definition of the score is found in 3.2 of the <a href="http://www.perlfoundation.org/rules_of_operation">rules</a>.</p>
  588.  
  589. <h3>Details</h3>
  590.  
  591. <p>While it is always difficult to make decision on grant proposals, this was a particularly tough one. We understand this is a serious project with good amount of interest from the community including multiple code committers. </p>
  592.  
  593. <p>The main reason that led us to the negative conclusion is as follows: there are already plenty of web frameworks and CMSes. It is not a bad thing to have another one but we will not be able to fund this "another one" which may or may not attract new users given there are just too many choices.
  594. For this specific area with high competition, we tend to spend money on marketing, promotion or tutorial of software which is completed, established and/or adopted. Otherwise on initiative to solve a specific problem.</p>
  595.  
  596. <p>We hope the success of Ado.</p>
  597.  
  598. <h3>Next round</h3>
  599.  
  600. <p>The next round is in March.  You can <a href="http://www.perlfoundation.org/how_to_write_a_proposal">submit proposals now</a>.</p>
  601. ]]>
  602.        
  603.  
  604.    </content>
  605. </entry>
  606.  
  607. <entry>
  608.    <title>Deadlines Approaching!</title>
  609.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2015/01/deadlines-approaching.html" />
  610.    <id>tag:news.perlfoundation.org,2015://18.3568</id>
  611.  
  612.    <published>2015-01-29T20:35:56Z</published>
  613.    <updated>2015-02-26T14:28:08Z</updated>
  614.  
  615.    <summary>As you prepare for this year&apos;s YAPC::NA be sure to take advantage of the early bird rates being offered by Little America Hotel in Salt Lake City! Reserve your room(s) prior to March 1st 2015 and receive a nightly discount. </summary>
  616.    <author>
  617.        <name>TPF Conferences Staff</name>
  618.        
  619.    </author>
  620.    
  621.        <category term="Conferences" scheme="http://www.sixapart.com/ns/types#category" />
  622.    
  623.        <category term="Marketing" scheme="http://www.sixapart.com/ns/types#category" />
  624.    
  625.        <category term="Perl Foundation" scheme="http://www.sixapart.com/ns/types#category" />
  626.    
  627.    
  628.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  629.        <![CDATA[<p>As you prepare for this year's <span class="caps">YAPC</span>::NA be sure to take advantage of the early bird rates being offered by Little America Hotel in Salt Lake City! Reserve your room(s) prior to March 1st 2015 and receive a nightly discount. </p>
  630.  
  631. <p>After March 1st, rates will go up $20/room/night. So be sure to book today. The reservation link can be found at <a href="http://yapcna.org/yn2015/location.html">yapcna.org/yn2015/location.html</a>. </p>
  632.  
  633. <p><span class="caps">CALLING ALL SPEAKERS</span>!</p>
  634.  
  635. <p>Don't forget that submissions for your <span class="caps">YAPC</span>::NA::2015 talks are due before midnight (23:59 <span class="caps">EST</span>) on March 1st 2015. Please submit your proposal by visiting <a href="http://yapcna.org/yn2015/newtalk">yapcna.org/yn2015/newtalk</a>. </p>]]>
  636.        
  637.    </content>
  638. </entry>
  639.  
  640. </feed>
  641.  

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

  1. Download the "valid Atom 1.0" banner.

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

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

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

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

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