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>2016-02-10T11:20:54Z</updated>
  8.    
  9.    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 6.2.2</generator>
  10.  
  11. <entry>
  12.    <title>YAPC::NA::2016 Call for Master Classes</title>
  13.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/02/yapcna2016-call-for-master-cla.html" />
  14.    <id>tag:news.perlfoundation.org,2016://18.3767</id>
  15.  
  16.    <published>2016-02-10T11:18:46Z</published>
  17.    <updated>2016-02-10T11:20:54Z</updated>
  18.  
  19.    <summary>Are you an experienced Perl instructor who would like to offer a course at YAPC:NA this year in Orlando? We want to offer the Perl community a selection of courses and tutorials before and after the conference. Master Classes can be a half day (3 hours), full day (6 hours) or 2 days in length and will run on Sunday 19th, Thursday 23rd, or Friday 24th of June. To submit your proposal please send the following information to talks@yapcna.org:...</summary>
  20.    <author>
  21.        <name>Dan Wright</name>
  22.        <uri>http://www.dwright.org</uri>
  23.    </author>
  24.    
  25.    
  26.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  27.        <![CDATA[<p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" id="docs-internal-guid-df0aaaaf-cae8-44b6-06b6-b7401f2147e1"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Are you an experienced Perl instructor who would like to offer a course at YAPC:NA this year in Orlando? We want to offer the Perl community a selection of courses and tutorials before and after the conference.  Master Classes can be a half day (3 hours), full day (6 hours) or 2 days in length and will run on Sunday 19th, Thursday 23rd, or Friday 24th of June.</span></p>
  28. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; 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>
  29. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">To submit your proposal please send the following information to </span><a href="mailto:talks@yapcna.org" style="text-decoration: none;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #1155cc; background-color: transparent; font-weight: bold; font-style: normal; font-variant: normal; text-decoration: underline; vertical-align: baseline;">talks@yapcna.org:</span></a></p>
  30. <p></p>]]>
  31.        <![CDATA[<ul style="margin-top: 0pt; margin-bottom: 0pt;">
  32. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  33. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Class Title</span></p>
  34. </li>
  35. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  36. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Names of Speakers</span></p>
  37. </li>
  38. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  39. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Speaker Biography</span></p>
  40. </li>
  41. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  42. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Abstract</span></p>
  43. </li>
  44. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  45. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Class Description, including:</span></p>
  46. </li>
  47. <ul style="margin-top: 0pt; margin-bottom: 0pt;">
  48. <li dir="ltr" style="list-style-type: circle; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  49. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">the course's length</span></p>
  50. </li>
  51. <li dir="ltr" style="list-style-type: circle; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  52. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">the intended audience</span></p>
  53. </li>
  54. <li dir="ltr" style="list-style-type: circle; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  55. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">any prerequisites or expected level of knowledge</span></p>
  56. </li>
  57. <li dir="ltr" style="list-style-type: circle; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  58. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">any supplies you will be providing to students</span></p>
  59. </li>
  60. <li dir="ltr" style="list-style-type: circle; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  61. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">any supplies you expect students to bring</span></p>
  62. </li>
  63. <li dir="ltr" style="list-style-type: circle; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  64. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">a short course outline</span></p>
  65. </li>
  66. <li dir="ltr" style="list-style-type: circle; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  67. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">maximum class size</span></p>
  68. </li>
  69. </ul>
  70. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  71. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">The dates on which you would be willing to give your course (June 19th, 23rd, or 24th)</span></p>
  72. </li>
  73. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  74. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">A list of requirements for the venue (A/V, Internet, etc.)</span></p>
  75. </li>
  76. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  77. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Cost of the Class, per student (please keep in mind YAPC will also need to add an administrative fee to this initial cost)</span><span style="font-size: 14.666666666666666px; 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>
  78. </li>
  79. </ul>
  80. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; 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>
  81. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Please bear in mind that it is our goal to keep the cost of these classes down for students as this is a low cost conference.</span></p>]]>
  82.    </content>
  83. </entry>
  84.  
  85. <entry>
  86.    <title>YAPC::NA::2016 Call for Speakers</title>
  87.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/02/yapcna2016-call-for-speakers.html" />
  88.    <id>tag:news.perlfoundation.org,2016://18.3765</id>
  89.  
  90.    <published>2016-02-09T03:24:22Z</published>
  91.    <updated>2016-02-09T03:28:24Z</updated>
  92.  
  93.    <summary>The YAPC::NA::2016 call for speakers is now open! The Yet Another Perl Conference is a high-quality, inexpensive technical conference that celebrates the Perl programming language. The conference is accessible to everyone, regardless of experience, yet it remains valuable to the most skilled programmers. Each year the conference attracts hundreds of programmers from around the world, including luminaries such as Larry Wall, Ricardo Signes, and Damian Conway. We hope you will consider applying to present at this exciting event! YAPC::NA::2016 will...</summary>
  94.    <author>
  95.        <name>Dan Wright</name>
  96.        <uri>http://www.dwright.org</uri>
  97.    </author>
  98.    
  99.        <category term="Conferences" scheme="http://www.sixapart.com/ns/types#category" />
  100.    
  101.    
  102.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  103.        <![CDATA[<p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 8pt;" id="docs-internal-guid-5859ebc7-c410-3a47-cc18-d4014b2d4d79"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">The YAPC::NA::2016 call for speakers is now open! The Yet Another Perl Conference is a high-quality, inexpensive technical conference that celebrates the Perl programming language. The conference is accessible to everyone, regardless of experience, yet it remains valuable to the most skilled programmers. Each year the conference attracts hundreds of programmers from around the world, including luminaries such as Larry Wall, Ricardo Signes, and Damian Conway. We hope you will consider applying to present at this exciting event!</span></p>
  104. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 8pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">YAPC::NA::2016 will be held in Orlando, Florida June 20th-22nd, 2016.</span></p>
  105. <p></p>]]>
  106.        <![CDATA[<p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">We expect to have approximately one hundred (100) sessions across four (4) tracks with over four hundred (400) attendees. In addition, there will be professional tutorials and hackathons in the days prior to, and following, the main conference.  </span></p>
  107. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; 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>
  108. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">We are interested in hearing talks on a wide variety of subjects. This includes both Perl 5 and Perl 6, as well as other topics that may be of general interest to Perl programmers. Please review the talk schedules from previous years (e.g., </span><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: bold; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">2015</span><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">: </span><a href="http://www.yapcna.org/yn2015/schedule" style="text-decoration: none;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #1155cc; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: underline; vertical-align: baseline;">http://www.yapcna.org/yn2015/schedule</span></a><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;"> or </span><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: bold; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">2014</span><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">: </span><a href="http://www.yapcna.org/yn2014/schedule" style="text-decoration: none;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #1155cc; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: underline; vertical-align: baseline;">http://www.yapcna.org/yn2014/schedule</span></a><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">) to get an idea of the type and breadth of talks we accept. </span></p>
  109. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 8pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;"></span></p>
  110. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 8pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">We will be accepting proposals for the following session types:</span></p>
  111. <ul style="margin-top: 0pt; margin-bottom: 0pt;">
  112. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  113. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Short Talks (20 minutes) </span></p>
  114. </li>
  115. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  116. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Standard Talks (50 minutes) </span></p>
  117. </li>
  118. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  119. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 8pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Tutorial Session (80 or 110 minutes)</span></p>
  120. </li>
  121. </ul>
  122. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 8pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">To submit a proposal for a talk/presentation, please register your proposed title and an abstract to the YAPC::NA site at </span><a href="http://www.yapcna.org/yn2016/newtalk" style="text-decoration: none;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #1155cc; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: underline; vertical-align: baseline;">http://www.yapcna.org/yn2016/newtalk</span></a><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">.  </span></p>
  123. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 8pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Submissions are due before midnight (23:59 EST) on March 1st 2016. Speakers will be notified by the 16th of March. If your proposal is accepted you will be expected to confirm within 48 hours of  your notification that you, in fact, will give the talk. If you do not confirm in the given time frame we may, at our discretion, assign your slot to another proposal.</span></p>
  124. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 8pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Please include the following with your abstract(s):</span></p>
  125. <ul style="margin-top: 0pt; margin-bottom: 0pt;">
  126. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  127. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">A little information about yourself (and possibly a link to an image of your choosing - preferably of yourself - that we may use to promote your talk).</span></p>
  128. </li>
  129. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  130. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">The expected minimum level of knowledge of your target audience (Beginner (2 years or less experience), Intermediate (3 to 5 years experience), Advanced (5+ years experience))</span></p>
  131. </li>
  132. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  133. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">An indication of the length of the presentation.</span></p>
  134. </li>
  135. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  136. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 8pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Details of any requirements you might have for doing your presentation. We will try to accommodate your request. Projectors and internet connection will be available for all talks.</span></p>
  137. </li>
  138. </ul>
  139. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 8pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">We will be recording presentations. If you do not want your presentation recorded please let us </span><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">know in advance.</span></p>
  140. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">We cannot offer much for your talk*, except:</span></p>
  141. <ul style="margin-top: 0pt; margin-bottom: 0pt;">
  142. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  143. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Free admittance</span></p>
  144. </li>
  145. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  146. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">A chance to meet a lot of smart, fun Perl people</span></p>
  147. </li>
  148. <li dir="ltr" style="list-style-type: disc; font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">
  149. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">The great love that being a speaker receives from said smart, fun Perl people</span></p>
  150. </li>
  151. </ul>
  152. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 13.333333333333332px; 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>
  153. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 13.333333333333332px; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">*Free admittance reserved for Short Talk, Standard Talk, and Tutorial Session speakers only.</span></p>
  154. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 13.333333333333332px; 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>
  155. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 14.666666666666666px; 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 have any special requests which have to do with fee and payment please contact us at </span><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: transparent; font-weight: bold; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">talks@yapcna.org</span><span style="font-size: 14.666666666666666px; 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>
  156. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"></p>
  157. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 8pt;"><span style="font-size: 18.666666666666664px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: bold; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Lightning Talks</span></p>
  158. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 8pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Due to their impromptu nature, the call for Lightning Talks will open at a later time. You may submit Lightning Talks at this time, but there is no guarantee of notification on their acceptance.</span></p>
  159. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 8pt;"><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Thank you!  We hope you will participate either as a speaker or as an attendee. If you have any questions at all, please do not hesitate to contact us at </span><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: bold; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">talks@yapcna.org</span><span style="font-size: 14.666666666666666px; font-family: Arial; color: #000000; background-color: #fafafa; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">.</span></p>]]>
  160.    </content>
  161. </entry>
  162.  
  163. <entry>
  164.    <title>Grant Proposal: RPerl User Documentation, Part 2</title>
  165.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/02/grant-proposal-rperl-user-docu-1.html" />
  166.    <id>tag:news.perlfoundation.org,2016://18.3766</id>
  167.  
  168.    <published>2016-02-08T22:00:00Z</published>
  169.    <updated>2016-02-09T03:50:12Z</updated>
  170.  
  171.    <summary>The Grants Committee has received one grant proposal for the January/February round. Before the Committee members vote, we would like to solicit feedback from the Perl community on the proposal. Review the proposal below and please comment here by February 17th, 2016. The Committee members will start the voting process following that and the conclusion will be announced by February 27th. RPerl User Documentation, Part 2 Name: Will Braswell Amount Requested: USD 1,600 Synopsis RPerl v1.5 has been released with...</summary>
  172.    <author>
  173.        <name>Makoto Nozaki</name>
  174.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  175.    </author>
  176.    
  177.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  178.    
  179.    
  180.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  181.        <![CDATA[<p>The Grants Committee has received one grant proposal for the January/February round.  Before the Committee members vote, we would like to solicit feedback from the Perl community on the proposal.</p>
  182.  
  183. <p>Review the proposal below and please comment here by February 17th, 2016.  The Committee members will start the voting process following that and the conclusion will be announced by February 27th.</p>
  184.  
  185. <h1>RPerl User Documentation, Part 2</h1>
  186.  
  187. <ul>
  188. <li><p>Name:</p>
  189.  
  190. <p>Will Braswell</p></li>
  191. <li><p>Amount Requested:</p>
  192.  
  193. <p>USD 1,600</p></li>
  194. </ul>
  195.  
  196. <h2>Synopsis</h2>
  197.  
  198. <p>RPerl v1.5 has been released with numerous new features, as promised.
  199. The RPerl User Docs grant work has been completed, but much documentation
  200. remains to be written immediately.
  201. This grant proposal is to continue work on the Learning RPerl user tutorial.</p>
  202.  
  203. <h2>Benefits to the Perl Community</h2>
  204.  
  205. <p>The number one request and obvious need at this time is still quality RPerl
  206. user documentation, to help new RPerl users learn how to write fast software.
  207. Learning RPerl is the canonical guide to RPerl and must be completed to enjoy
  208. the maximum benefit to the Perl programming community.</p>
  209.  
  210. <h2>Deliverables</h2>
  211.  
  212. <p>Deliverables for this grant proposal are:</p>
  213.  
  214. <p>1.  Complete Learning RPerl Chapter 2</p>
  215.  
  216. <p>2.  Write Learning RPerl Chapter 3</p>
  217.  
  218. <p>3.  Write Learning RPerl Chapter 4</p>
  219. ]]>
  220.        <![CDATA[<h2>Project Details</h2>
  221.  
  222. <p>I've already written all of the code for the solutions to exercises from
  223. chapters 1 through 6 of Learning Perl:
  224. https://github.com/wbraswell/rperl/tree/master/lib/RPerl/Learning</p>
  225.  
  226. <p>Exercises in Learning Perl which are not supported by RPerl are omitted.</p>
  227.  
  228. <p>I've already got a partial copy of Learning RPerl on the website:
  229. http://rperl.org/learning_rperl.html</p>
  230.  
  231. <h2>Inch-stones</h2>
  232.  
  233. <p>Chapter 2 Scalar Data
  234. 1a.  Numbers; Strings; Perl’s Built-in Warnings; Scalar Variables</p>
  235.  
  236. <p>1b.  Output with print; The if Control Structure; Getting User Input; The chomp Operator</p>
  237.  
  238. <p>1c.  The while Control Structure; The undef Value; The defined Function</p>
  239.  
  240. <p>Chapter 3 Lists and Arrays</p>
  241.  
  242. <p>2a.  Accessing Elements of an Array; Special Array Indices; List Literals; List Assignment</p>
  243.  
  244. <p>2b.  Interpolating Arrays into Strings; The foreach Control Structure</p>
  245.  
  246. <p>2c.  Scalar and List Context; <STDIN> in List Context</p>
  247.  
  248. <p>Chapter 4 Subroutines</p>
  249.  
  250. <p>3a.  Defining a Subroutine; Invoking a Subroutine; Return Values; Arguments</p>
  251.  
  252. <p>3b.  Private Variables in Subroutines; Variable-Length Parameter Lists; Notes on Lexical (my) Variables</p>
  253.  
  254. <p>3c.  The use strict Pragma; The return Operator;</p>
  255.  
  256. <p>3d.  Non-Scalar Return Values; Persistent, Private Variables</p>
  257.  
  258. <h2>Project Schedule</h2>
  259.  
  260. <p>I will begin work immediately upon granting.</p>
  261.  
  262. <p>I expect work to take approximately 30 to 60 days.</p>
  263.  
  264. <h2>Completeness Criteria</h2>
  265.  
  266. <p>I will release a new version of RPerl to CPAN with the new documentation.</p>
  267.  
  268. <p>I will release a new version of the RPerl website with the new documentation.</p>
  269.  
  270. <h2>Bio</h2>
  271.  
  272. <p>I am the creator and lead developer of RPerl.</p>
  273.  
  274. <p>I've been working on RPerl for over 36 months.</p>
  275.  
  276. <p>I've successfully completed work on 1 TPF grant.</p>
  277.  
  278. <p>I would like to start work on the 2nd grant now.</p>
  279. ]]>
  280.    </content>
  281. </entry>
  282.  
  283. <entry>
  284.    <title>Perl 6 Release Goals: Final Grant Report</title>
  285.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/02/perl-6-release-goals-final-gra.html" />
  286.    <id>tag:news.perlfoundation.org,2016://18.3764</id>
  287.  
  288.    <published>2016-02-04T07:05:35Z</published>
  289.    <updated>2016-02-04T07:13:41Z</updated>
  290.  
  291.    <summary>Jonathan Worthington writes: I applied for a third and final extension of my Perl 6 Release Goals grant, which was published for comments in December and subsequently approved. The final extension granted a further 110 hours of work, which I completed prior to the Christmas release of Perl 6. This report covers the work that was done under this extension, and concludes with some final comments on the grant as a whole. I&apos;d like to start with a small note...</summary>
  292.    <author>
  293.        <name>Karen Pauley</name>
  294.        <uri>http://martian.org/karen</uri>
  295.    </author>
  296.    
  297.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  298.    
  299.    <category term="perl6grants" label="perl 6 grants" scheme="http://www.sixapart.com/ns/types#tag" />
  300.    
  301.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  302.        <![CDATA[<p><em>Jonathan Worthington writes:</em></p>
  303.  
  304. <p>I applied for a third and final extension of my Perl 6 Release Goals grant, which was published for <a href="http://news.perlfoundation.org/2015/12/perl-6-release-goals-first-gra.html">comments in December</a> and subsequently approved. The final extension granted a further 110 hours of work, which I completed prior to the Christmas release of Perl 6. This report covers the work that was done under this extension, and concludes with some final comments on the grant as a whole.</p>
  305.  
  306. <p>I'd like to start with a small note on timing. In November, I worked almost exclusively on Perl 6. Around the middle of the month, I had exhausted all of the hours that had been assigned in the previous grant extension. The general understanding on Perl 6 Core Development Fund grants is that I may - at my own risk - go ahead and continue with work that needs doing, in hope that a grant extension application will be approved. I did this, concurrent with writing up a report on what was achieved and requesting the extension. Thus, I didn't actually endure a sleepless week or two in December completing the hours in the final grant extension - as was speculated in one comment! Rather, the extension covered all of my December work, as well work in the later parts of November.</p>
  307.  
  308. <p>Numerous issues were resolved during the hours provided by this final grant extension:</p>
  309.  
  310. <ul>
  311. <li>Supplies, the Perl 6 API for asynchronous streams of data, got a design cleanup. The API was good overall, but several corners of it were suboptimal both from a language design and safety point of view, as well as from an optimizability perspective.</li>
  312. <li>Some API design issues around async sockets and processes, as well as with Promise combinators, were resolved. The CLOSE phaser was added to supply blocks to facilitate resource management, and the whenever syntax came to support channels as well as promises and supplies. This meant that the earliest block syntax, which I've never been entirely happy with, could go away. Finally, a couple of other concurrency bugs were resolved.</li>
  313. <li>A number of important I/O issues were dealt with, the most notable of which involved dealing with various complaints about Windows newline handling. The native file descriptor behind a handle was also exposed, for use in conjunction with native calling, and UDP support was added to IO::Socket::Async.</li>
  314. <li>The semantics of multi methods stubbed in roles, as well as composition of multi methods in roles, were reviewed and modified to be more useful.</li>
  315. <li>Sized native lexical variables got a good looking over, as well as unsigned native integers. Numerous issues around them were addressed.</li>
  316. <li>A few control flow related semantic issues were ironed out, generally involving the interaction of phasers and control flow operations (such as next and last).</li>
  317. <li>Nearly 20 other smaller semantic bugs were resolved in a range of areas: list flattening edge cases, role punning, .?/.+/.* behavior with multis, multi-dispatch with optional parameters, shadowing of built-in types, return constraints on blocks, and sigilless variables in list assignments.</li>
  318. <li>A couple of nasty bugs were fixed (a GC hang, a pre-compilation bug, and a meta-object mixins problem).</li>
  319. </ul>
  320.  
  321. <p>I also contributed in various ways to preparing for the release itself. Of note, I added the experimental pragma and moved a number of things we were not happy with including in Perl 6 Christmas behind it. I also clarified version reporting to reflect the language/compiler version distinction more cleanly. Finally, I was there on Christmas day itself to lend a hand with the release.</p>
  322.  
  323. <p>With the Perl 6 Christmas release now made, this Perl 6 Release Goals grant has reached its natural conclusion. I would like to thank all those who have contributed funds to make the initial grant and its two extensions possible. For me, 2015 was a year with various happy distractions, but also in the latter parts of the year suboptimal health. Together, these notably reduced my usual levels of "free time" for participating in Perl 6. So, rather than simply enabling me to do a bit more, this grant was critical to my continued substantial involvement in the Perl 6 project during this important year. I would also like to thank TPF for administering this grant, my grant manager, and last - but certainly not least - the Perl 6 community, who I count among the best folks I've worked with on anything, ever.</p>
  324. ]]>
  325.        
  326.    </content>
  327. </entry>
  328.  
  329. <entry>
  330.    <title>Perl 5 Grant Application: QA Hackathon Travel</title>
  331.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/02/perl-5-grant-application-qa-ha.html" />
  332.    <id>tag:news.perlfoundation.org,2016://18.3763</id>
  333.  
  334.    <published>2016-02-03T05:18:05Z</published>
  335.    <updated>2016-02-03T23:25:18Z</updated>
  336.  
  337.    <summary>We have received the following 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 2016 Amount Requested: $1200 Synopsis: This grant will be used to pay for travel for Ricardo Signes to and from the Perl...</summary>
  338.    <author>
  339.        <name>Karen Pauley</name>
  340.        <uri>http://martian.org/karen</uri>
  341.    </author>
  342.    
  343.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  344.    
  345.    <category term="perl5grants" label="Perl 5 grants" scheme="http://www.sixapart.com/ns/types#tag" />
  346.    
  347.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  348.        <![CDATA[<p>We have received the following 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.</p>
  349.  
  350. <p><strong>Name:</strong> Ricardo Signes</p>
  351.  
  352. <p><strong>Project Title:</strong>  Perl QA Hackathon 2016</p>
  353.  
  354. <p><strong>Amount Requested:</strong> $1200</p>
  355.  
  356. <p><strong>Synopsis:</strong></p>
  357.  
  358. <p>This grant will be used to pay for travel for Ricardo Signes to and from the Perl QA Hackathon held in Rugby, UK in Q1 2016.</p>
  359.  
  360. <p><strong>Benefits to Perl 5:</strong></p>
  361.  
  362. <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 CPAN and related tools.  Specifically, I was one of the chief implementors of the new CPAN Testers platform (Metabase) and built the Fake CPAN system for testing CPAN tools, and several reusable software libraries that are used to power both Metabase and Fake CPAN.  In 2012, I worked on refactoring PAUSE, adding tests and improving maintainability. PAUSE, the system which processes contributor uploads to the CPAN, manages CPAN contributor identity, and builds the CPAN indexes used by CPAN clients to locate libraries for installation.</p>
  363.  
  364. <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>
  365.  
  366. <p><strong>Deliverable Elements:</strong></p>
  367.  
  368. <p>The QA Hackathon does not have a set agenda, so promising specific work product 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>
  369.  
  370. <p>I hope, in particular, to work on the web code of PAUSE and to discuss mechanisms for improving collaborative code review within the community of toolchain maintainers.</p>
  371.  
  372. <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>
  373.  
  374. <p>Any software that I produce will be released under the Perl 5 standard license terms, or possibly even less restrictive terms.</p>
  375.  
  376. <p><strong>Applicant Biography:</strong></p>
  377.  
  378. <p>I have been building software in Perl professionally for about fifteen years. I am a frequent contributor of original software to the CPAN and a frequent contributor to, or maintainer of, other popular CPAN libraries. I am also a contributor to the core Perl 5 project, and its current project lead.</p>
  379.  
  380. <p>I have been the recipient of TPF grants five times before, all of which were successful.</p>
  381. ]]>
  382.        
  383.    </content>
  384. </entry>
  385.  
  386. <entry>
  387.    <title>Ian Hague Perl 6 Grant Application: JavaScript backend for Rakudo</title>
  388.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/02/ian-hague-perl-6-grant-applica.html" />
  389.    <id>tag:news.perlfoundation.org,2016://18.3762</id>
  390.  
  391.    <published>2016-02-01T05:27:53Z</published>
  392.    <updated>2016-02-09T14:12:45Z</updated>
  393.  
  394.    <summary>We have received the following Perl 6 Ian Hague Grant Application. Before we vote on this proposal we would like to have a period of community consultation for 10 days. Please leave feedback in the comments or if you prefer send email with your comments to karen at perlfoundation.org. Name: Paweł Murias Project Title: JavaScript backend for Rakudo Synopsis: Improve the JavaScript backend from handling NQP (Not Quite Perl) to full Perl 6. Benefits to to Perl 6 Development: A...</summary>
  395.    <author>
  396.        <name>Karen Pauley</name>
  397.        <uri>http://martian.org/karen</uri>
  398.    </author>
  399.    
  400.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  401.    
  402.    <category term="perl6haguegrant" label="perl6 hague grant" scheme="http://www.sixapart.com/ns/types#tag" />
  403.    
  404.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  405.        <![CDATA[<p>We have received the following Perl 6 Ian Hague Grant Application. Before we vote on this proposal we would like to have a period of community consultation for 10 days. Please leave feedback in the comments or if you prefer send email with your comments to karen at perlfoundation.org.</p>
  406.  
  407. <p><strong>Name:</strong> Paweł Murias</p>
  408.  
  409. <p><strong>Project Title:</strong> JavaScript backend for Rakudo</p>
  410.  
  411. <p><strong>Synopsis:</strong></p>
  412.  
  413. <p>Improve the JavaScript backend from handling NQP (Not Quite Perl) to full Perl 6.</p>
  414.  
  415. <p><strong>Benefits to to Perl 6 Development:</strong></p>
  416.  
  417. <p>A JavaScript backend for Rakudo will allow the use of Perl 6 in many new niches. The main focus of the grant is to allow Perl 6 to be used for writing the frontend part of single page applications (for the backend part we can use MoarVM).</p>
  418.  
  419. <p>A side benefit of the grant is that I intend to create a web-based REPL that should allow users to play around with Perl 6 without installing it. The goal of the grant is provide a JavaScript backend with enough features that the community can start experimenting with what running inside the browser will allow us to accomplish.</p>
  420.  
  421. <p>While working on the JavaScript backend I write test for the things I'm implementing. Expanding the test suite will directly help future backend authors. It also helps anyone doing non trivial changes to the existing backends. I have found MoarVM and JVM bugs in the past doing that.</p>
  422.  
  423. <p><strong>Deliverables:</strong></p>
  424.  
  425. <ul>
  426. <li>Upload rakudo-js to npm and CPAN.</li>
  427. <li>Have this rakudo-js be able compile our chosen subset of the 6.c roast (official Perl 6 test suit) to JavaScript and pass them in a modern browser.</li>
  428. <li>Write a simple REPL in Perl 6 that will run in a modern browser.</li>
  429. <li>Write a tutorial showing how to use the JavaScript backend.</li>
  430. </ul>
  431.  
  432. <p><strong>Project Details:</strong></p>
  433.  
  434. <p>Rakudo compiles Perl 6 and NQP (a subset of Perl 6 that Rakudo itself is written in) to an abstract syntax tree form called QAST. QAST is then passed to either the MoarVM, JVM or JavaScript backends. Currently the JavaScript backend can only handle AST that is produced from NQP. The goal of this project is to improve the JavaScript backend to handle the QAST produced from full Perl 6.</p>
  435.  
  436. <p>I started the original work on the JavaScript backend while Rakudo was transitioning from being a Parrot targeting compiler to a multi-platform one. Parts of the work on the backend was done as parts of a GSoC project. After the GSoC projects I undertook a rewrite of the backend. The rewrite allowed me to add source maps support and use more type information to generate better code. The JavaScript backend is now merged in the the master branch of the NQP repo.</p>
  437.  
  438. <p>After reviewing the initial draft of this grant proposal Jonathan Worthington pointed out that implementing gather/take proved to be tricky on other backends. To reduce this risk I added basic continuations support to the backend. This was enough to run a basic form of gather/take: <a href="https://github.com/perl6/nqp/blob/master/t/js/continuations.t#L76">https://github.com/perl6/nqp/blob/master/t/js/continuations.t#L76</a> . I implemented this using a CPS transform with a trampoline (to work around the lack of tail call optimization).</p>
  439.  
  440. <p>Most of Perl 6 is built from smaller building blocks. This will mean that a large part of the effort will be needed before I get to the point where the test module compiles and the first test passes. On the other hand when the needed building blocks are implemented correctly I will be able to reuse the quality work that went into Rakudo and the setting.</p>
  441. ]]>
  442.        <![CDATA[<p><strong>Inch-stones:</strong></p>
  443.  
  444. <ul>
  445. <li>Cleanup the array handling in nqp-js.</li>
  446. <li>Finish up serialization of closures in the nqp-js-running-on-js.</li>
  447. <li>Go through the MoarVM opcode list and where it's possible write tests for untested opcode and implement them in nqp-js</li>
  448. <li>Do the obvious speedups for the code generated by nqp-js.</li>
  449. <li>Compile the meta-model and bootstrap support with nqp-js.</li>
  450. <li>Implement a bunch of p6 specific ops.</li>
  451. <li>Get rakudo to compile on nqp-js.</li>
  452. <li>Get rakudo compiled to js to correctly compile nqp::say("Hello World").</li>
  453. <li>Get the rakudo setting to compile.</li>
  454. <li>Get rakudo compiled to js to correctly compile say("Hello World").</li>
  455. <li>Get Test.pm to correctly compile.</li>
  456. <li>Pass a first test.</li>
  457. <li>Go through roast test fixing bugs and implementing missing things to make them pass.</li>
  458. <li>Get continuations support fully functional. Get nqp-js to pass test all test in full CPS mode.</li>
  459. <li>Pass the part of roast we focus on node.js.</li>
  460. <li>Be able to webpack the generated javascript code.</li>
  461. <li>Be able to run tests in the browser.</li>
  462. <li>Pass the part of roast we focus on in a browser.</li>
  463. <li>Polish up source maps support.</li>
  464. <li>Implement (and test) interoperability with javascript code</li>
  465. <li>Upload rakudo-js on npm.</li>
  466. <li>Write a simple Perl6 REPL that should run in modern browser.</li>
  467. <li>Put the REPL on try.perl6.org when the community views it as good enough.</li>
  468. <li>Write a tutorial that describes how to use the backend.</li>
  469. <li>Make sure our source map support works correctly and integrates well with browsers.</li>
  470. <li>Fix issues that early adopters will encounter.</li>
  471. <li>Fix the most obvious performance issues.</li>
  472. </ul>
  473.  
  474. <p><strong>Completeness Criteria:</strong></p>
  475.  
  476. <ul>
  477. <li>Rakudo-js released on npm</li>
  478. <li>Rakudo-js passes our chosen subset of roast</li>
  479. <li>A simple Perl 6 REPL running in a modern browser (for evaluation purposes a modern version of Google Chrome)</li>
  480. </ul>
  481.  
  482. <p><strong>List of tests we want to pass:</strong></p>
  483.  
  484. <p>We want to pass tests from the official Perl 6 Test Suit "Roast". It can be found on github.com/perl6/roast.</p>
  485.  
  486. <p>For the purpose of the grant we focus on a subset of those (mainly excluding IO and OS interaction). Some tests might be broken for reasons outside of the JavaScript backend so that for grant completeness purposes we are only concerned with the tests that pass on the Rakudo MoarVM backend.</p>
  487.  
  488. <p>We want to pass the tests in the following subdirectories of roast:</p>
  489.  
  490. <ul>
  491. <li>S02-lexical-conventions</li>
  492. <li>S02-lists</li>
  493. <li>S02-literals</li>
  494. <li>S02-magicals</li>
  495. <li>S02-names</li>
  496. <li>S02-names-vars</li>
  497. <li>S02-one-pass-parsing</li>
  498. <li>S02-packages</li>
  499. <li>S02-types</li>
  500. <li>S03-binding</li>
  501. <li>S03-feeds</li>
  502. <li>S03-junctions</li>
  503. <li>S03-metaops</li>
  504. <li>S03-operators</li>
  505. <li>S03-sequence</li>
  506. <li>S03-smartmatch</li>
  507. <li>S04-blocks-and-statements</li>
  508. <li>S04-declarations</li>
  509. <li>S04-exception-handlers</li>
  510. <li>S04-exceptions</li>
  511. <li>S04-phasers</li>
  512. <li>S04-statement-modifiers</li>
  513. <li>S04-statement-parsing</li>
  514. <li>S04-statements</li>
  515. <li>S05-capture</li>
  516. <li>S05-grammar</li>
  517. <li>S05-interpolation</li>
  518. <li>S05-mass</li>
  519. <li>S05-match</li>
  520. <li>S05-metachars</li>
  521. <li>S05-metasyntax</li>
  522. <li>S05-modifier</li>
  523. <li>S05-nonstrings</li>
  524. <li>S05-substitution</li>
  525. <li>S05-syntactic-categories</li>
  526. <li>S05-transliteration</li>
  527. <li>S06-advanced</li>
  528. <li>S06-currying</li>
  529. <li>S06-macros</li>
  530. <li>S06-multi</li>
  531. <li>S06-operator-overloading</li>
  532. <li>S06-other</li>
  533. <li>S06-routine-modifiers</li>
  534. <li>S06-signature</li>
  535. <li>S06-traits</li>
  536. <li>S07-iterators</li>
  537. <li>S09-autovivification</li>
  538. <li>S09-hashes</li>
  539. <li>S09-subscript</li>
  540. <li>S09-typed-arrays</li>
  541. <li>S10-packages</li>
  542. <li>S11-modules</li>
  543. <li>S12-attributes</li>
  544. <li>S12-class</li>
  545. <li>S12-construction</li>
  546. <li>S12-enums</li>
  547. <li>S12-introspection</li>
  548. <li>S12-meta</li>
  549. <li>S12-methods</li>
  550. <li>S12-subset</li>
  551. <li>S12-traits</li>
  552. <li>S13-overloading</li>
  553. <li>S13-syntax</li>
  554. <li>S13-type-casting</li>
  555. <li>S14-roles</li>
  556. <li>S14-traits</li>
  557. <li>S32-array</li>
  558. <li>S32-basics</li>
  559. <li>S32-container</li>
  560. <li>S32-exceptions</li>
  561. <li>S32-hash</li>
  562. <li>S32-list</li>
  563. <li>S32-num</li>
  564. <li>S32-scalar</li>
  565. <li>S32-str</li>
  566. <li>S32-temporal</li>
  567. <li>S32-trig</li>
  568. </ul>
  569.  
  570. <p><strong>Project Schedule:</strong></p>
  571.  
  572. <p>The project is expected to take 4 months of full time effort. I will begin work as soon as the grant gets accepted. Based on the progress of previous backends most of the effort will be needed to get to the point where all the basic building blocks are working and we start passing tests.</p>
  573.  
  574. <p>The plan for the months of the grant is:</p>
  575.  
  576. <ul>
  577. <li>Getting to the point where can begin compiling the CORE setting.</li>
  578. <li>Correctly compile and load the setting.</li>
  579. <li>Fixing inevitable bugs that cause failing tests and implementing missing bits of functionality. After this steps we should be passing the roast test suit.</li>
  580. <li>Working on making the backend easy to install and use. This will include writing a tutorial, fixing issues that early users find, tweaking source maps, improving obvious performance problems.</li>
  581. </ul>
  582.  
  583. <p><strong>Report Schedule:</strong></p>
  584.  
  585. <p>I will report on the progress of the grant on a blog at least every two weeks, preferably more often. I will also keep the #perl6 channel updated on my progress.</p>
  586.  
  587. <p><strong>Public Repository:</strong></p>
  588.  
  589. <p>The backend code will be hosted at github.com/perl6/nqp. Any required modifications to rakudo will be hosted at github.com/perl6/rakudo. (Work on rakudo itself will intially be done in either a branch or a github fork).</p>
  590.  
  591. <p><strong>Grant Deliverables ownership/copyright and License Information:</strong></p>
  592.  
  593. <p>All the work produced as a result of this grant will be licensed under the Artistic License Version 2.0. I will send in the CLA and if required transfer the copyright to The Perl Foundation.</p>
  594.  
  595. <p><strong>Things not addressed by the scope of the grant:</strong></p>
  596.  
  597. <p>Performance and size of the generated JavaScript code will likely be an important concern before using the backend for serious production use. While I'll to keep it in mind and attempt to solve the most obvious problems as it's a very open ended issue it's not the main focus of the grant. As the feedback from the #perl6 channel seemed to imply webapps are the thing the community is the most interested in, I'm moving IO support while running on node.js outside of the scope of grant.</p>
  598.  
  599. <p><strong>Amount Requested:</strong> $10000.</p>
  600.  
  601. <p><strong>Bio:</strong></p>
  602.  
  603. <p>Worked on the mildew/smop/kp6 Perl 6 implementations. Once the Perl 6 implementations converged on Rakudo I started working on the JavaScript backend for it, starting first with one for NQP. I worked on the JavaScript backend for NQP outside of and as part of a Google Summer of Code project. I have tweaked both the MoarVM and JVM backends so if changes to the whole of NQP are required I will be capable of that.</p>
  604. ]]>
  605.    </content>
  606. </entry>
  607.  
  608. <entry>
  609.    <title>Grant Report: Test::Simple/Stream Stabilization</title>
  610.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/01/grant-report-testsimplestream-.html" />
  611.    <id>tag:news.perlfoundation.org,2016://18.3761</id>
  612.  
  613.    <published>2016-01-29T17:28:07Z</published>
  614.    <updated>2016-01-31T01:25:53Z</updated>
  615.  
  616.    <summary>In the last month, Chad has been working with Ricardo Signes (rjbs) doing final tweaking of Test2. For that, some new versions of Test2 and related modules have been published for testing and review purposes. For those who are lazy, some pointers here for Test2, Test2::Suite, Test2::Workflow and dev release of Test::Builder....</summary>
  617.    <author>
  618.        <name>Alberto Simões</name>
  619.        <uri>http://blogs.perl.org/users/alberto_simoes/</uri>
  620.    </author>
  621.    
  622.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  623.    
  624.    <category term="grants" label="grants" scheme="http://www.sixapart.com/ns/types#tag" />
  625.    
  626.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  627.        <![CDATA[<p>In the last month, Chad has been working with Ricardo Signes (<em>rjbs</em>) doing final tweaking of Test2. For that, some new versions of Test2 and related modules have been published for testing and review purposes.</p>
  628. <p>For those who are lazy, some pointers here for <a href="https://metacpan.org/pod/Test2">Test2</a>, <a href="https://metacpan.org/pod/Test2::Suite">Test2::Suite,</a> <a href="https://metacpan.org/pod/Test2::Workflow">Test2::Workflow</a> and dev release of <a href="https://metacpan.org/pod/release/EXODIST/Test-Simple-1.302013_012/lib/Test/Builder.pm">Test::Builder</a>.</p>]]>
  629.        
  630.    </content>
  631. </entry>
  632.  
  633. <entry>
  634.    <title>Maintaining Perl 5: Grant Report for November 2015</title>
  635.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/01/maintaining-perl-5-grant-repor-24.html" />
  636.    <id>tag:news.perlfoundation.org,2016://18.3760</id>
  637.  
  638.    <published>2016-01-27T04:57:32Z</published>
  639.    <updated>2016-01-30T10:52:39Z</updated>
  640.  
  641.    <summary>Tony Cook writes: Approximately 54 tickets were reviewed, and 12 patches were applied. [perl #126593] illustrates how some of perl&apos;s internal tools need to be careful of which parts of the language they use. The tr/// operator can do its job in one of two ways, if all the code points are between 0 and 255 with a 256 entry table of shorts, otherwise using a swash, which is created by SWASHNEW in lib/utf8_heavy.pl. tr/// uses the UTF-8 flag on...</summary>
  642.    <author>
  643.        <name>Karen Pauley</name>
  644.        <uri>http://martian.org/karen</uri>
  645.    </author>
  646.    
  647.    
  648.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  649.        <![CDATA[<p><em>Tony Cook writes:</em></p>
  650.  
  651. <p>Approximately 54 tickets were reviewed, and 12 patches were applied.</p>
  652.  
  653. <p>[perl #126593] illustrates how some of perl's internal tools need to be careful of which parts of the language they use.</p>
  654.  
  655. <p>The tr/// operator can do its job in one of two ways, if all the code points are between 0 and 255 with a 256 entry table of shorts, otherwise using a swash, which is created by <span class="caps">SWASHNEW </span>in lib/utf8_heavy.pl.</p>
  656.  
  657. <p>tr/// uses the <span class="caps">UTF</span>-8 flag on the search and replacement strings to decide whether to use the look-up table or the swash, so it's possible for the swash to be used even when the search and replacement strings are representable as bytes.</p>
  658.  
  659. <p>aa8f6cef changed a s/// operator in lib/utf8_heavy.pl to a tr/// operator.  All of the characters in the search and replacement strings can be represented as bytes - they're all <span class="caps">ASCII </span>range, so at first sight the implementation should be using the lookup table rather than the swash.</p>
  660.  
  661. <p>The problem is code that uses the deprecated ${^ENCODING} variable, in this case the encoding::warnings module.  encoding::warnings sets ${^ENCODING} to a filter that warns (or croaks) when a non-UTF-8 marked PV with non-ASCII is used with <span class="caps">UTF</span>-8 marked PVs.<sup class="footnote"><a href="http://news.perlfoundation.org/2016/01/maintaining-perl-5-grant-repor-24.html#fn1">1</a></sup></p>
  662.  
  663. <p>When parsing string literals, including tr/// operators, S_scan_str() in toke.c always returns <span class="caps">UTF</span>-8 marked strings when ${^ENCODING} is true</p>
  664.  
  665. <p>The module that started [perl #125693] loads encoding::warnings, so ${^ENCODING} is now set, then Fatal, which loads Carp which includes the line:</p>
  666.  
  667. <pre><code>$VERSION =~ tr/_//d;</code></pre>
  668.  
  669. <p>so both the search and replacement strings are passed to S_pmtrans() (op.c) as <span class="caps">UTF</span>-8 marked strings.</p>
  670.  
  671. <p>S_pmtrans() attempts to create a swash, which starts to load utf8_heavy.pl, until we get to the line:</p>
  672.  
  673. <pre><code>(my $loose = $_[0]) =~ tr/-_ \t//d;</code></pre>
  674.  
  675. <p>where things break.</p>
  676.  
  677. <p>[1] the current recommended practice is that the <span class="caps">UTF</span>-8 flag controls internal representation only and combining two such strings isn't an issue.  Don't use encoding::warnings.</p>]]>
  678.        <![CDATA[<table><tr><td>Hours</td><td>Activity</td></tr><tr><td>0.17</td><td>#122251 review upstream tickets and resolve</td></tr><tr><td>0.45</td><td>#123710 testing, close</td></tr><tr><td>2.55</td><td>#123737 review discussion, testing</td></tr><tr><td></td><td>#123737 debugging, produce a patch and comment</td></tr><tr><td>1.62</td><td>#123991 produce a patch and comment</td></tr><tr><td>2.51</td><td>#124068 testing, fix issues, more testing</td></tr><tr><td></td><td>#124068 another fix, testing, push to blead</td></tr><tr><td>1.15</td><td>#124080 review, testing</td></tr><tr><td></td><td>#124080 review test results, push to blead</td></tr><tr><td>2.32</td><td>#124097 review code, try a fix</td></tr><tr><td></td><td>#124097 review more code, comment with patch</td></tr><tr><td></td><td>#124097 testing, comment</td></tr><tr><td>0.83</td><td>#124349 produce a patch</td></tr><tr><td>0.75</td><td>#125619 review discussion and comment</td></tr><tr><td>0.40</td><td>#125830 review cflags.SH changes, testing, apply to blead</td></tr><tr><td>2.14</td><td>#126042 research</td></tr><tr><td></td><td>#126042 more research, comment with a simple patch</td></tr><tr><td>2.86</td><td>#126045 review discussion, research, work on test patch</td></tr><tr><td></td><td>#126045 more work on patch, comment with patch (and some</td></tr><tr><td></td><td>smartmatch irc discussion)</td></tr><tr><td>1.94</td><td>#126193 review code, work on a patch, testing, comment with patch</td></tr><tr><td></td><td>#126193 re-check patch, testing, apply to blead</td></tr><tr><td>1.27</td><td>#126240 (camel issues), testing and comment</td></tr><tr><td>0.52</td><td>#126325 review patch, testing and apply to blead</td></tr><tr><td>0.50</td><td>#126368 review, test all three modules with blead and close</td></tr><tr><td>0.53</td><td>#126403 review and comment</td></tr><tr><td>0.23</td><td>#126437 research, comment</td></tr><tr><td>2.32</td><td>#126443 (sec) comment</td></tr><tr><td></td><td>#126443 create a test, testing, comment with new patch</td></tr><tr><td></td><td>#126443 testing, apply to blead</td></tr><tr><td>0.57</td><td>#126469 review, re-test and apply to blead</td></tr><tr><td>1.37</td><td>#126474 comment</td></tr><tr><td></td><td>#126474 research, comment</td></tr><tr><td>1.55</td><td>#126480 produce a patch and comment</td></tr><tr><td></td><td>#126480 minor corrections to patch, push a smoke-me</td></tr><tr><td></td><td>#126480 testing, apply to blead</td></tr><tr><td>0.88</td><td>#126502 testing</td></tr><tr><td></td><td>#126502 more testing, start bisect</td></tr><tr><td></td><td>#126502 comment</td></tr><tr><td>1.08</td><td>#126533 review and comment</td></tr><tr><td></td><td>#126533 test and apply to blead</td></tr><tr><td>0.60</td><td>#126534 review, test and apply</td></tr><tr><td>1.03</td><td>#126544 research, comment</td></tr><tr><td>0.40</td><td>#126546 fuzzer tickets meta-ticket</td></tr><tr><td>0.60</td><td>#126552 testing, debugging</td></tr><tr><td>5.59</td><td>#126593 debugging, research, longer comment</td></tr><tr><td></td><td>#126593 review discussion, try some fixes</td></tr><tr><td></td><td>#126593 comment with patch</td></tr><tr><td>2.03</td><td>#126602 review, produce a patch and comment</td></tr><tr><td></td><td>#126602 re-check patch, testing, apply to blead</td></tr><tr><td>0.50</td><td>#126608 review and comment</td></tr><tr><td>0.43</td><td>#126609 review, test and apply to blead</td></tr><tr><td>0.76</td><td>#126611 review and comment</td></tr><tr><td></td><td>#126611 review latest patch, testing, apply to blead</td></tr><tr><td>3.13</td><td>#126621 review, code, prep for testing, reproduce, review</td></tr><tr><td></td><td>failing tests, work on simple reproducer</td></tr><tr><td></td><td>#126621 comment, try to work out a fix</td></tr><tr><td>0.15</td><td>#126632 review, requires <span class="caps">CPAN </span>updates, so leave</td></tr><tr><td>2.17</td><td>#126633 review failing code, review patch, make a simple reproducer</td></tr><tr><td></td><td>#126633 try to make a simpler reproducer, try a simple</td></tr><tr><td></td><td>patch and comment</td></tr><tr><td>1.93</td><td>#126635 reproduce, review code, produce a patch and comment</td></tr><tr><td></td><td>#126635 produce alternate patch and comment</td></tr><tr><td></td><td>#126635 testing, apply to blead</td></tr><tr><td>0.98</td><td>#126707 review change, research, comment</td></tr><tr><td>1.25</td><td>make_ext.pl silent handling, notice unneeded rebuilds and</td></tr><tr><td></td><td>open #126710</td></tr><tr><td>1.67</td><td>#126719 debugging, open Encode ticket, comments</td></tr><tr><td>0.32</td><td>#126731 review code, testing, find dup and comment, merge tickets</td></tr><tr><td>3.64</td><td>#126755 (sec) try to map MapPathW crash, working up test code</td></tr><tr><td></td><td>#126755 (sec) more test code, testing, re-working supplied fix</td></tr><tr><td>0.35</td><td>5.24.0 blocker updates</td></tr><tr><td>7.01</td><td>#57512 review discussion, look over code</td></tr><tr><td></td><td>#57512 more look over code, testing</td></tr><tr><td></td><td>#57512 research, code on in-place edit close failures</td></tr><tr><td></td><td>#57512 more code, testing, comment with patches</td></tr><tr><td>2.78</td><td>cygwin build warnings - testing, seem to be 32-bit</td></tr><tr><td></td><td>generic, testing, fixes</td></tr><tr><td>0.32</td><td>cygwin failures – re-test original fix and apply to blead</td></tr><tr><td>0.48</td><td>jhi's scandir thread – research and comment</td></tr><tr><td>0.63</td><td>khw's cygwin issues</td></tr><tr><td>0.28</td><td>os390 dynaloader issue: fix an else nesting bug</td></tr><tr><td>0.65</td><td>rjbs's redefinition warning strangeness: irc and reply to list</td></tr><tr><td>0.93</td><td>smartmatch review overloading code</td></tr><tr><td>2.47</td><td>smartmatch testing, work on overload.t failures</td></tr><tr><td>2.08</td><td>smartmatch: fix overload.t tests, more testing, push to branch</td></tr><tr><td>2.72</td><td>smartmatch: rebase, work on overloading</td></tr></table>
  679.  
  680. <p><b>78.39 Hours Total</b></p>]]>
  681.    </content>
  682. </entry>
  683.  
  684. <entry>
  685.    <title>Migrating blogs.perl.org: Second Progress Report</title>
  686.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/01/migrating-blogsperlorg-second-.html" />
  687.    <id>tag:news.perlfoundation.org,2016://18.3759</id>
  688.  
  689.    <published>2016-01-26T21:35:48Z</published>
  690.    <updated>2016-01-31T13:55:52Z</updated>
  691.  
  692.    <summary>Evozon have been busy working on their grant to improve blogs.perl.org. Since our first progress report they have worked hard analysing the project&apos;s requirements and implementing them in Jeff&apos;s public GitHub repository. The project runs PearlBee using Docker and Carton. So far, the new system supports the following: RSS export Markdown editing Data migration from the old site ElasticSearch An inproved user interface Home page posts Per-user posts User profile page Permissions Associating assets with blog posts Comments The project...</summary>
  693.    <author>
  694.        <name>Tom Hukins</name>
  695.        <uri>http://www.exceptone.co.uk/</uri>
  696.    </author>
  697.    
  698.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  699.    
  700.    
  701.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  702.        <![CDATA[<p>Evozon have been busy working on their <a href="http://news.perlfoundation.org/2015/07/grant-proposal-revitalize-blog.html">grant to improve blogs.perl.org</a>.</p>
  703.  
  704. <p>Since <a href="http://news.perlfoundation.org/2015/10/migrating-blogsperlorg-first-p.html">our first progress report</a> they have worked hard analysing the project's requirements and implementing them in <a href="https://github.com/drforr/blogs-perl-org">Jeff's public GitHub repository</a>.</p>
  705.  
  706. <p>The project runs <a href="http://pearlbee.org/">PearlBee</a> using Docker and Carton.</p>
  707.  
  708. <p>So far, the new system supports the following:</p>
  709. <ul>
  710. <li>RSS export</li>
  711. <li>Markdown editing</li>
  712. <li>Data migration from the old site</li>
  713. <li>ElasticSearch</li>
  714. <li>An inproved user interface</li>
  715. <li>Home page posts</li>
  716. <li>Per-user posts</li>
  717. <li>User profile page</li>
  718. <li>Permissions</li>
  719. <li>Associating assets with blog posts</li>
  720. <li>Comments</li>
  721. </ul>
  722.  
  723. <p>The project has a private staging server to demonstrate the new system:  soon we will open it up to the wider community for testing.</p>]]>
  724.        
  725.    </content>
  726. </entry>
  727.  
  728. <entry>
  729.    <title>YAPC::NA::2016 Update #2 -- It&apos;s Orlando!​</title>
  730.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/01/yapcna2016-update-2----its-orl.html" />
  731.    <id>tag:news.perlfoundation.org,2016://18.3758</id>
  732.  
  733.    <published>2016-01-23T23:51:03Z</published>
  734.    <updated>2016-01-30T20:14:20Z</updated>
  735.  
  736.    <summary>I am pleased to be able to bring you the news we have all been waiting for! We know the wait hasn&apos;t been easy, and so the YAPC::NA 2016 organizing committee would like to take this opportunity to thank you for your patience. It&apos;s been a long road getting to this point, but thankfully we have finally secured a location that best fits all of our needs. Throughout our search we considered and visited venues in Maryland, Pennsylvania, Michigan, Kansas,...</summary>
  737.    <author>
  738.        <name>Dan Wright</name>
  739.        <uri>http://www.dwright.org</uri>
  740.    </author>
  741.    
  742.    
  743.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  744.        <![CDATA[<p>I am pleased to be able to bring you the news we have all been waiting
  745. for!  We know the wait hasn't been easy, and so the YAPC::NA
  746. 2016 organizing committee would like to take this opportunity to thank
  747. you for your patience.  It's been a long road getting to this
  748. point, but thankfully we have finally secured a location that best fits
  749. all of our needs.    </p>
  750.  
  751. <p>Throughout our search we considered and visited venues in Maryland,
  752. Pennsylvania, Michigan, Kansas, Florida, and Washington D.C..  Many
  753. people spent countless hours putting out feelers and soliciting bids.
  754. In particular, we would like to give a huge thanks to the DC/Baltimore
  755. Perl Mongers and the Detroit Perl Mongers:  their efforts were
  756. invaluable in this process, and we hope that we can eventually bring
  757. YAPC::NA to their fantastic cities.</p>
  758.  
  759. <p><strong>It is with great enthusiasm that we happily announce YAPC::NA 2016 will
  760. be held Sunday, June 19th through Friday, June 24th at the Downtown
  761. Doubletree Hotel in Orlando, Florida!</strong></p>
  762.  
  763. <p>The main event will run from Monday, June 20th through Wednesday, June
  764. 22nd.  Master Classes, training, and other activities will be held on
  765. the 19th, 23rd, and 24th.  We highly encourage you to attend all days,
  766. but especially look forward to seeing you at the Main Event.</p>
  767.  
  768. <p>We'll be opening up the new website, registration, call for
  769. talks, etc over the next month or so.    Please continue to watch your
  770. email for future updates.</p>
  771. ]]>
  772.        
  773.    </content>
  774. </entry>
  775.  
  776. <entry>
  777.    <title>Grant Report : RPerl User Documentation - Final (Jan 2016)</title>
  778.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/01/grant-report-rperl-user-docume-3.html" />
  779.    <id>tag:news.perlfoundation.org,2016://18.3757</id>
  780.  
  781.    <published>2016-01-23T21:59:48Z</published>
  782.    <updated>2016-01-31T08:44:24Z</updated>
  783.  
  784.    <summary>Will Braswell has completed his RPerl Docs grant, submitting the following report: &quot;I have released RPerl v1.51 with all grant work items now completed! 1a. Describe Eyapp EBNF grammar format and Grammar.eyp file sections http://rperl.org/learningrperl.html#B.1%3AEyappGrammarFormat%26Sections 1b. Describe lexical token types http://rperl.org/learningrperl.html#B.2%3ALexiconTokenTypes 1c. Describe operator precedence and associativity http://rperl.org/learningrperl.html#B.3%3ASyntaxPrecedence%26_Associativity 1d. Describe all grammar rules and productions 1e. Provide examples of valid code http://rperl.org/learningrperl.html#B.4%3ASyntaxProductionRules 2a. Complete source code of solutions to chapters 1 - 6 2b. Describe how to arrive at each...</summary>
  785.    <author>
  786.        <name>Mark A Jensen</name>
  787.        
  788.    </author>
  789.    
  790.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  791.    
  792.    
  793.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  794.        <![CDATA[<p>Will Braswell has completed his <a href="http://news.perlfoundation.org/2015/09/grant-proposal-rperl-user-docu.html">RPerl Docs grant</a>,
  795. submitting the following report:</p>
  796.  
  797. <p>"I have released RPerl v1.51 with all grant work items now completed!</p>
  798.  
  799. <p>1a. Describe Eyapp EBNF grammar format and Grammar.eyp file sections</p>
  800.  
  801. <p><a href="http://rperl.org/learning_rperl.html#B.1%3A_Eyapp_Grammar_Format_%26_Sections">http://rperl.org/learning<em>rperl.html#B.1%3A</em>Eyapp<em>Grammar</em>Format<em>%26</em>Sections</a></p>
  802.  
  803. <p>1b. Describe lexical token types</p>
  804.  
  805. <p><a href="http://rperl.org/learning_rperl.html#B.2%3A_Lexicon_Token_Types">http://rperl.org/learning<em>rperl.html#B.2%3A</em>Lexicon<em>Token</em>Types</a></p>
  806.  
  807. <p>1c. Describe operator precedence and associativity</p>
  808.  
  809. <p><a href="http://rperl.org/learning_rperl.html#B.3%3A_Syntax_Precedence_%26_Associativity">http://rperl.org/learning<em>rperl.html#B.3%3A</em>Syntax<em>Precedence</em>%26_Associativity</a></p>
  810.  
  811. <p>1d. Describe all grammar rules and productions
  812. 1e. Provide examples of valid code</p>
  813.  
  814. <p><a href="http://rperl.org/learning_rperl.html#B.4%3A_Syntax_Production_Rules">http://rperl.org/learning<em>rperl.html#B.4%3A</em>Syntax<em>Production</em>Rules</a></p>
  815.  
  816. <p>2a. Complete source code of solutions to chapters 1 - 6
  817. 2b. Describe how to arrive at each solution</p>
  818.  
  819. <p><a href="http://rperl.org/learning_rperl.html#APPENDIX_A%3A_EXERCISE_ANSWERS">http://rperl.org/learning<em>rperl.html#APPENDIX</em>A%3A<em>EXERCISE</em>ANSWERS</a></p>
  820.  
  821. <p>3a. Create POD versions of deliverables 1 and 2</p>
  822.  
  823. <p><a href="https://github.com/wbraswell/rperl/blob/master/lib/RPerl/Learning.pm">https://github.com/wbraswell/rperl/blob/master/lib/RPerl/Learning.pm</a></p>
  824.  
  825. <p>3b. Use POD::Tree::HTML or similar to generate HTML</p>
  826.  
  827. <p><a href="https://github.com/wbraswell/rperl/blob/master/script/development/pod2rperlhtml.pl">https://github.com/wbraswell/rperl/blob/master/script/development/pod2rperlhtml.pl</a></p>
  828.  
  829. <p>3c. Integrate HTML into rperl.org web framework</p>
  830.  
  831. <p><a href="http://rperl.org/learning_rperl.html">http://rperl.org/learning_rperl.html</a>
  832. "</p>
  833.  
  834. <p>Owing to issues with TPF blog, this report could not be published in a timely fashion.
  835. The Grants Committee elected to vote on completion without public comments. The committee
  836. accepted the work as successfully completed.</p>
  837.  
  838. <p>MAJ</p>
  839. ]]>
  840.        
  841.    </content>
  842. </entry>
  843.  
  844. <entry>
  845.    <title>New site, same URL</title>
  846.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/01/new-site-same-url.html" />
  847.    <id>tag:news.perlfoundation.org,2016://18.3756</id>
  848.  
  849.    <published>2016-01-23T17:21:13Z</published>
  850.    <updated>2016-02-01T07:38:23Z</updated>
  851.  
  852.    <summary>This site, The Perl Foundation News, got a technical issue and it had to be changed to read-only mode last week. I&apos;m pleased to announce that this site is back up with the latest version of Movable Type. Apologies for those who tried to leave a comment in the past week and ended up with an error. Grants Committee&apos;s January round is rescheduled as follows: Proposal deadline: February 3rd Public comments deadline: February 10th Thanks to the volunteers who recovered...</summary>
  853.    <author>
  854.        <name>Makoto Nozaki</name>
  855.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  856.    </author>
  857.    
  858.    
  859.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  860.        <![CDATA[<p>This site, The Perl Foundation News, got a technical issue and it had to be changed to read-only mode last week. I'm pleased to announce that this site is back up with the latest version of Movable Type.</p>
  861.  
  862. <p>Apologies for those who tried to leave a comment in the past week and ended up with an error.</p>
  863.  
  864. <p>Grants Committee's January round is rescheduled as follows:</p>
  865.  
  866. <ul>
  867. <li>Proposal deadline: February 3rd</li>
  868. <li>Public comments deadline: February 10th</li>
  869. </ul>
  870.  
  871. <p>Thanks to the volunteers who recovered the site. And I appreciate Six Apart, Ltd. who helped the migration.</p>]]>
  872.        
  873.    </content>
  874. </entry>
  875.  
  876. <entry>
  877.    <title>Maintaining Perl 5: Grant Report for October 2015</title>
  878.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/01/maintaining-perl-5-grant-repor-23.html" />
  879.    <id>tag:news.perlfoundation.org,2016://18.3750</id>
  880.  
  881.    <published>2016-01-07T18:01:14Z</published>
  882.    <updated>2016-01-30T11:04:43Z</updated>
  883.  
  884.    <summary>Tony Cook writes: Approximately 46 tickets were reviewed, and 13 patches were applied. HoursActivity1.98#123658 review, testing, apply to blead0.42#123985, #123831 review, research, ask kid51 for a test build2.93#123994 review code, testing#123994 more testing, comment with some possible fixes0.63#124063 apply to blead with some fiddling2.29#124068 review, research (symbian is dead, dead, dead)#124068 more research, comment0.85#124080 review, testing, comment0.35#125569 research, comment0.22#125830 comments0.28#126045 review latest response0.67#126051 apply to blead, dealing with conflicts, testing0.23#126082 review0.50#126152 review, research and comment0.28#126196 review, test, apply to blead0.38#126228...</summary>
  885.    <author>
  886.        <name>Karen Pauley</name>
  887.        <uri>http://martian.org/karen</uri>
  888.    </author>
  889.    
  890.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  891.    
  892.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  893.    
  894.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  895.        <![CDATA[<p><em>Tony Cook writes:</em></p>
  896.  
  897. <p>Approximately 46 tickets were reviewed, and 13 patches were applied.</p>
  898.  
  899. <table><tr><td>Hours</td><td>Activity</td></tr><tr><td>1.98</td><td>#123658 review, testing, apply to blead</td></tr><tr><td>0.42</td><td>#123985, #123831 review, research, ask kid51 for a test build</td></tr><tr><td>2.93</td><td>#123994 review code, testing</td></tr><tr><td></td><td>#123994 more testing, comment with some possible fixes</td></tr><tr><td>0.63</td><td>#124063 apply to blead with some fiddling</td></tr><tr><td>2.29</td><td>#124068 review, research (symbian is dead, dead, dead)</td></tr><tr><td></td><td>#124068 more research, comment</td></tr><tr><td>0.85</td><td>#124080 review, testing, comment</td></tr><tr><td>0.35</td><td>#125569 research, comment</td></tr><tr><td>0.22</td><td>#125830 comments</td></tr><tr><td>0.28</td><td>#126045 review latest response</td></tr><tr><td>0.67</td><td>#126051 apply to blead, dealing with conflicts, testing</td></tr><tr><td>0.23</td><td>#126082 review</td></tr><tr><td>0.50</td><td>#126152 review, research and comment</td></tr><tr><td>0.28</td><td>#126196 review, test, apply to blead</td></tr><tr><td>0.38</td><td>#126228 review, research, comment</td></tr></table>]]>
  900.        <![CDATA[<table><tr><td></td><td>#126228 reject</td></tr><tr><td></td><td>#126228 reopen and comment</td></tr><tr><td>2.82</td><td>#126242 review, testing, comment</td></tr><tr><td></td><td>#126242 fixes, testing, debug test failures, research</td></tr><tr><td></td><td>#126242 more testing, apply to blead, note for backporting fix</td></tr><tr><td>0.63</td><td>#126281 review, test, apply to blead, perldelta</td></tr><tr><td>1.17</td><td>#126319 debugging, comment, more debugging</td></tr><tr><td>3.28</td><td>#126325 debugging, produce patch with tests, comment</td></tr><tr><td>0.08</td><td>#126337 review and reject - EU::CB already updated</td></tr><tr><td>1.93</td><td>#126373 research, testing, apply to blead</td></tr><tr><td>0.93</td><td>#126374 research, testing</td></tr><tr><td></td><td>#126374 testing, apply to blead</td></tr><tr><td>0.88</td><td>#126376 research, testing and comment</td></tr><tr><td>0.67</td><td>#126377 review, testing, apply to blead</td></tr><tr><td>1.36</td><td>#126402 review, research, testing</td></tr><tr><td></td><td>#126402 review test results, apply to blead</td></tr><tr><td>5.13</td><td>#126403 review perlio code</td></tr><tr><td></td><td>#126403 testing, comment</td></tr><tr><td></td><td>#126403 research, produce a different patch</td></tr><tr><td></td><td>#126403 comment with patch</td></tr><tr><td></td><td>#126403 comment</td></tr><tr><td></td><td>#126403 benchmarking</td></tr><tr><td>1.87</td><td>#126405 debugging</td></tr><tr><td></td><td>#126405 debugging</td></tr><tr><td>0.62</td><td>#126407 review, check perldeltas, start bisect</td></tr><tr><td>1.15</td><td>#126410 review discussion, review and test patch, comment</td></tr><tr><td>0.63</td><td>#126412 review, test and apply to blead</td></tr><tr><td>1.78</td><td>#126414 research</td></tr><tr><td></td><td>#126414 more research and comment</td></tr><tr><td>2.27</td><td>#126431 review, comment</td></tr><tr><td></td><td>#126431 review and test new patch and apply to blead</td></tr><tr><td></td><td>#126431 partly revert for C++ builds</td></tr><tr><td></td><td>#126431 research, comment</td></tr><tr><td>0.52</td><td>#126440 review, testing, open cpan #107970, reject</td></tr><tr><td>2.37</td><td>#126443 debugging, produce patch and comment</td></tr><tr><td>2.34</td><td>#126452 review</td></tr><tr><td></td><td>#126452, #126453 review, testing, apply to blead</td></tr><tr><td>0.83</td><td>#126453 review</td></tr><tr><td></td><td>#126453 fix non-Win32 build issue introduced by this patch</td></tr><tr><td>0.52</td><td>#126469 review</td></tr><tr><td></td><td>#126469 produce patch and comment</td></tr><tr><td>0.20</td><td>#126474 comment</td></tr><tr><td>0.60</td><td>#126480 research and comment</td></tr><tr><td>0.88</td><td>#126482 debugging</td></tr><tr><td>1.15</td><td>cygwin build issue, test failure</td></tr><tr><td>0.57</td><td>dmake build issue, fix and testing</td></tr><tr><td>0.18</td><td>dmake build issues</td></tr><tr><td>0.55</td><td>more cygwin</td></tr><tr><td>0.88</td><td><span class="caps">POSIX</span>/Coverity noise - produce a patch</td></tr><tr><td>0.23</td><td>reproduce and fix podcheck error</td></tr><tr><td>0.33</td><td>Unicode::Normalize testing</td></tr></table>
  901.  
  902. <p><b>51.36 Hours Total</b></p>]]>
  903.    </content>
  904. </entry>
  905.  
  906. <entry>
  907.    <title>Grant Report : RPerl User Documentation - December 2015</title>
  908.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/01/grant-report-rperl-user-docume-2.html" />
  909.    <id>tag:news.perlfoundation.org,2016://18.3748</id>
  910.  
  911.    <published>2016-01-05T00:53:12Z</published>
  912.    <updated>2016-01-05T01:18:30Z</updated>
  913.  
  914.    <summary>Will Braswell provides the following update on his RPerl doc grant. By my assessment of the inchstones, Will is well past the 60% mark and is doggedly making constant headway. &quot;I&apos;ve released RPerl v1.4 and v1.5 with updated Learning RPerl content: https://metacpan.org/release/RPerl For work item 2b, I am about halfway through writing the explanations of how to arrive at each code solution for the exercises in chapters 1 - 6: http://rperl.org/learning_rperl.html#APPENDIX_A%3A_EXERCISE_ANSWERS For work item 3b, I have updated the pod2rperlhtml.pl...</summary>
  915.    <author>
  916.        <name>Mark A Jensen</name>
  917.        
  918.    </author>
  919.    
  920.    
  921.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  922.        <![CDATA[<p>Will Braswell provides the following update on his <a href="http://news.perlfoundation.org/2015/09/grant-proposal-rperl-user-docu.html">RPerl doc grant</a>. By my assessment of the inchstones, Will is well past the 60% mark and is doggedly making constant headway.</p>
  923.  
  924. <p>"I've released RPerl v1.4 and v1.5 with updated Learning RPerl content:
  925. <a href="https://metacpan.org/release/RPerl">https://metacpan.org/release/RPerl</a></p>
  926.  
  927. <p>For work item 2b, I am about halfway through writing the explanations of how to arrive at each code solution for the exercises in chapters 1 - 6:</p>
  928.  
  929. <p><a href="http://rperl.org/learning_rperl.html#APPENDIX_A%3A_EXERCISE_ANSWERS">http://rperl.org/learning_rperl.html#APPENDIX_A%3A_EXERCISE_ANSWERS</a></p>
  930.  
  931. <p>For work item 3b, I have updated the pod2rperlhtml.pl script to support MetaCPAN-style formatting and the new <noncode>...</noncode> tags:</p>
  932.  
  933. <p><a href="https://github.com/wbraswell/rperl/blob/master/script/development/pod2rperlhtml.pl">https://github.com/wbraswell/rperl/blob/master/script/development/pod2rperlhtml.pl</a></p>
  934.  
  935. <p>As before, you can access the latest major release of Learning RPerl via MetaCPAN:</p>
  936.  
  937. <p><a href="https://metacpan.org/pod/RPerl::Learning">https://metacpan.org/pod/RPerl::Learning</a></p>
  938.  
  939. <p>I have completed work item 3c by integrating the HTML content of Learning RPerl into the RPerl.org website, with slightly nicer formatting than MetaCPAN itself:</p>
  940.  
  941. <p><a href="http://rperl.org/use_rperl.html">http://rperl.org/use_rperl.html</a></p>
  942.  
  943. <p>... which leads to ...</p>
  944.  
  945. <p><a href="http://rperl.org/learning_rperl.html">http://rperl.org/learning_rperl.html</a> "</p>
  946.  
  947. <p>MAJ</p>
  948. ]]>
  949.        
  950.    </content>
  951. </entry>
  952.  
  953. <entry>
  954.    <title>Call For Grant Proposals (January 2016 Round)</title>
  955.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/01/call-for-grant-proposals-janua-1.html" />
  956.    <id>tag:news.perlfoundation.org,2016://18.3746</id>
  957.  
  958.    <published>2016-01-02T23:00:00Z</published>
  959.    <updated>2016-02-03T05:59:53Z</updated>
  960.  
  961.    <summary>Happy new year! The Grants Committee is accepting grant proposals all the time. We evaluate them every two months and another evaluation period has come. If you have an idea for doing some Perl work that will benefit the Perl community, consider sending a grant application. The application deadline for this round is 23:59 January 16th UTC. We will publish the received applications, get community feedback and conclude acceptance by February 3rd. The format will be the same as the...</summary>
  962.    <author>
  963.        <name>Makoto Nozaki</name>
  964.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  965.    </author>
  966.    
  967.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  968.    
  969.    
  970.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  971.        <![CDATA[<p>Happy new year!</p>
  972.  
  973. <p>The Grants Committee is accepting grant proposals all the time.  We evaluate them every two months and another evaluation period has come.</p>
  974.  
  975. <p>If you have an idea for doing some Perl work that will benefit the Perl community, consider sending a grant application. <strong>The application deadline for this round is 23:59 January 16th UTC.</strong> We will publish the received applications, get community feedback and conclude acceptance by February 3rd.</p>
  976.  
  977. <p>The format will be the same as the previous rounds in 2014-2015.</p>
  978.  
  979. <p>To apply, please read <a href="http://www.perlfoundation.org/how_to_write_a_proposal">How to Write a Proposal</a>.  <a href="http://www.perlfoundation.org/rules_of_operation">Rules of Operation</a> and <a href="http://www.perlfoundation.org/running_grants">Running Grants List</a> will also help you understand how the grant process works. We also got some <a href="http://www.perlfoundation.org/grant_ideas">grant ideas</a> from the community.</p>
  980.  
  981. <p>We will confirm the receipt of application within 24 hours.</p>
  982.  
  983. <p>If you have further questions, please comment here or contact me at tpf-grants-secretary at perl-foundation.org.</p>
  984. ]]>
  985.        
  986.    </content>
  987. </entry>
  988.  
  989. </feed>
  990.  

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