Congratulations!

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

Recommendations

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

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

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <feed xmlns="http://www.w3.org/2005/Atom">
  3.    <title>The Perl Foundation</title>
  4.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/" />
  5.    <link rel="self" type="application/atom+xml" href="http://news.perlfoundation.org/atom.xml" />
  6.    <id>tag:news.perlfoundation.org,2010-03-22://18</id>
  7.    <updated>2017-11-14T03:42:12Z</updated>
  8.    
  9.    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 6.2.2</generator>
  10.  
  11. <entry>
  12.    <title>Grant Extension Approved: Tony Cook&apos;s maintaining Perl 5 Grant</title>
  13.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/11/grant-extension-approved-tony-.html" />
  14.    <id>tag:news.perlfoundation.org,2017://18.3926</id>
  15.  
  16.    <published>2017-11-13T22:00:00Z</published>
  17.    <updated>2017-11-14T03:42:12Z</updated>
  18.  
  19.    <summary>Tony Cook recently requested an extension of his Maintaining the Perl 5 Grant. I&apos;m pleased to announce that the Board of Directors approved extension of another $20,000. It&apos;ll allow him to dedicate another 400 hours to this work. I would like to thank the community members who took time to comment on this grant extension request and our sponsors who made funding the grant possible through our Perl 5 Core Maintenance Fund. For the fund status, please also see P5CMF...</summary>
  20.    <author>
  21.        <name>Makoto Nozaki</name>
  22.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  23.    </author>
  24.    
  25.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  26.    
  27.        <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category" />
  28.    
  29.    
  30.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  31.        <![CDATA[<p><strong>Tony Cook</strong> recently <a href="http://news.perlfoundation.org/2017/10/grant-extension-request-mainta-5.html">requested an extension of his Maintaining the Perl 5 Grant</a>.</p>
  32.  
  33. <p>I'm pleased to announce that the Board of Directors approved extension of another $20,000. It'll allow him to dedicate another 400 hours to this work.</p>
  34.  
  35. <p>I would like to thank the community members who took time to comment on this grant extension request and our sponsors who made funding the grant possible through our Perl 5 Core Maintenance Fund. For the fund status, please also see <a href="http://news.perlfoundation.org/2017/10/p5cmf-running-out-of-funds.html">P5CMF running out of funds</a>.</p>
  36.  
  37. <p>I also appreciate Tony Cook, who publishes regular progress report on his work.</p>
  38. ]]>
  39.        
  40.    </content>
  41. </entry>
  42.  
  43. <entry>
  44.    <title>Maintaining Perl 5 (Tony Cook): October 2017 Report</title>
  45.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/11/maintaining-perl-5-tony-cook-o.html" />
  46.    <id>tag:news.perlfoundation.org,2017://18.3925</id>
  47.  
  48.    <published>2017-11-12T23:00:00Z</published>
  49.    <updated>2017-11-13T04:21:35Z</updated>
  50.  
  51.    <summary>This is a monthly report by Tony Cook on his grant under Perl 5 Core Maintenance Fund. We thank the TPF sponsors to make this grant possible....</summary>
  52.    <author>
  53.        <name>Makoto Nozaki</name>
  54.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  55.    </author>
  56.    
  57.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  58.    
  59.        <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category" />
  60.    
  61.    
  62.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  63.        <![CDATA[<p>This is a monthly report by Tony Cook on his grant under <a href="http://www.perlfoundation.org/perl_5_core_maintenance_fund">Perl 5 Core Maintenance Fund</a>. We thank the TPF sponsors to make this grant possible.</p>
  64. ]]>
  65.        <![CDATA[<pre>Approximately 23 tickets were reviewed, and 7 patches were
  66. applied
  67.  
  68. [Hours]         [Activity]
  69.  0.33          #122807 review discussion
  70.  0.45          #124349 review discussion and apply patch
  71.  0.40          #125619 review discussion, research, briefly comment
  72.  0.25          #125760 review discussion, add to 5.30 blockers for make
  73.                them croak instead
  74.  0.18          #126707 review discussion and code, comment
  75.  0.17          #126849 check upstream report and close
  76.  0.83          #127063 re-check patch, testing, apply to blead
  77. 39.85          #127743 work on cherry-picking from cperl
  78.                #127743 more cherry-picking
  79.                #127743 more cherry-picking
  80.                #127743 more cherry-picking
  81.                #127743 more cherry-picking
  82.                #127743 more cherry-picking
  83.                #127743 more cherry-picking
  84.                #127743 more cherry-picking
  85.                #127743 work on cherry-picking from cperl
  86.                #127743 work on cherry-picking from cperl
  87.                #127743 code review
  88.                #127743 code review
  89.                #127743 more code review
  90.                #127743 more code review, consider fixes
  91.                #127743 status email
  92.                #127743 email discussion
  93.                #127743 work on fixes
  94.                #127743 work on possible way to test large numbers of Svs
  95.                #127743 manage to produce buggy behaviour, work on fix
  96.                #127743 large object tag implementation, testing
  97.                #127743 test 2G+ object tag handling, testing
  98.                #127743 audit 2G+ tag handling for hooks, work on
  99.                regression tests for 2G+ object tag handling
  100.                #127743 more work on tests
  101.  3.21          #128765 work on fix
  102.                #128765 more work on fix
  103.                #128765 more work on fix, fail to figure out efficient
  104.                masking
  105.  0.33          #130080 research, add to maint-votes
  106.  0.92          #131065 (sec) comment
  107.  0.92          #131878 (sec) work up a patch and comment with patch
  108.  1.88          #131982 testing (including some strange results) minor
  109.                portability change, apply to blead
  110.  8.98          #132013 work on an implementation
  111.                #132013 work on an implementation
  112.                #132013 testing, debugging
  113.                #132013 debugging, add groups, - prefix
  114.                #132013 more tests, docs, polish, comment with patch
  115.  0.25          #132159 testing, apply to blead
  116.  0.40          #132160 review patch, testing, apply to blead
  117.  0.73          #132171 review, testing, apply to blead
  118.  0.42          #132234 try to reproduce, comment
  119.  5.50          #132245 debugging, find a memory leak, work on a fix,
  120.                testing
  121.                #132245 re-work fix, testing, comment with patches
  122.                #132245 restesting, apply to blead
  123.  0.28          comment on Zefram’s character encoding comment
  124.  0.52          default_inc_excludes_dot query
  125.  0.28          fix io/tell.t
  126.  0.52          script runs discussion: comment
  127. ======
  128. 67.60 hours total</pre>
  129. ]]>
  130.    </content>
  131. </entry>
  132.  
  133. <entry>
  134.    <title>Call For Proposals: November 2017 Round</title>
  135.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/11/call-for-proposals-november-20.html" />
  136.    <id>tag:news.perlfoundation.org,2017://18.3924</id>
  137.  
  138.    <published>2017-11-12T18:56:28Z</published>
  139.    <updated>2017-11-12T19:07:25Z</updated>
  140.  
  141.    <summary>The Grants Committee has expended its budget for the period ending with 2017. In accordance with the TPF rules of operation (http://www.perlfoundation.org/rulesofoperation), grants evaluations are stalled until further notice. I&apos;m expecting that we&apos;ll be able to re-open evaluations starting in the January 2018 period. Thanks to all the TPF sponsors that make the grants process possible. Please consider becoming one and donating at http://donate.perlfoundation.org/ If you have further questions, please contact me at tpf-grants-secretary at perl-foundation.org....</summary>
  142.    <author>
  143.        <name>Coke</name>
  144.        
  145.    </author>
  146.    
  147.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  148.    
  149.    
  150.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  151.        <![CDATA[<p>The Grants Committee has expended its budget for the period ending with 2017.</p>
  152.  
  153. <p>In accordance with the TPF rules of operation (http://www.perlfoundation.org/rules<em>of</em>operation),
  154. grants evaluations are stalled until further notice. I'm expecting that we'll be able to re-open
  155. evaluations starting in the January 2018 period.</p>
  156.  
  157. <p>Thanks to all the TPF sponsors that make the grants process possible. Please consider becoming one and
  158. donating at http://donate.perlfoundation.org/</p>
  159.  
  160. <p>If you have further questions, please contact me at tpf-grants-secretary at perl-foundation.org.</p>
  161. ]]>
  162.        
  163.    </content>
  164. </entry>
  165.  
  166. <entry>
  167.    <title>Grant Report - Complete YAML::PP - October 2017</title>
  168.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/11/grant-report---complete-yamlpp.html" />
  169.    <id>tag:news.perlfoundation.org,2017://18.3923</id>
  170.  
  171.    <published>2017-11-05T00:20:13Z</published>
  172.    <updated>2017-11-05T00:23:04Z</updated>
  173.  
  174.    <summary>Tina has put &gt;50hrs in on YAML::PP, as she describes in her blog post. Some highlights: 23 tests added to the standard test suite Updates to the YAML Test Matrix (which is a nice overview of YAML compliance across implementations in several languages) Under-hood work on YAML::XS boolean handling and YAML flow-style. MAJ...</summary>
  175.    <author>
  176.        <name>Mark A Jensen</name>
  177.        
  178.    </author>
  179.    
  180.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  181.    
  182.    <category term="grants" label="grants" scheme="http://www.sixapart.com/ns/types#tag" />
  183.    <category term="yaml" label="yaml" scheme="http://www.sixapart.com/ns/types#tag" />
  184.    
  185.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  186.        <![CDATA[<p>Tina has put >50hrs in on YAML::PP, as she describes in her <a href="http://blogs.perl.org/users/tinita/2017/11/yamlpp-grant-report-october-2017.html">blog post</a>. Some highlights:</p>
  187.  
  188. <ul>
  189. <li>23 tests added to the standard test suite</li>
  190. <li>Updates to the <a href="http://matrix.yaml.io/">YAML Test Matrix</a> (which is a nice overview of YAML compliance across implementations in several languages)</li>
  191. <li>Under-hood work on YAML::XS boolean handling and YAML flow-style.</li>
  192. </ul>
  193.  
  194. <p>MAJ</p>
  195. ]]>
  196.        
  197.    </content>
  198. </entry>
  199.  
  200. <entry>
  201.    <title>P5CMF running out of funds.</title>
  202.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/10/p5cmf-running-out-of-funds.html" />
  203.    <id>tag:news.perlfoundation.org,2017://18.3922</id>
  204.  
  205.    <published>2017-10-31T15:02:51Z</published>
  206.    <updated>2017-11-02T02:36:46Z</updated>
  207.  
  208.    <summary>The Perl 5 Core Maintenance Fund was established at YAPC::NA 2011 by Jesse Vincent and Karen Pauley as a continuation of the previous Booking.com grant. It is intended to be &quot;used for the maintenance and improvement of the Perl 5 core.&quot; Since its inception, the P5CMF has received over half of a million dollars in donations, and has provided funding for eight different individuals to contribute over 9,000 service hours towards improving performance, stability, and features for Perl 5. (Full...</summary>
  209.    <author>
  210.        <name>Dan Wright</name>
  211.        <uri>http://www.dwright.org</uri>
  212.    </author>
  213.    
  214.    
  215.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  216.        <![CDATA[<p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">The </span><a href="http://www.perlfoundation.org/perl_5_core_maintenance_fund" style="text-decoration: none;"><span style="font-size: 11pt; font-family: Arial; color: #1155cc; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: underline; vertical-align: baseline;">Perl 5 Core Maintenance Fund</span></a><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;"> was established at YAPC::NA 2011 by Jesse Vincent and Karen Pauley as a continuation of the previous Booking.com grant. It is intended to be "used for the maintenance and improvement of the Perl 5 core."</span></p>
  217. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"></p>
  218. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Since its inception, the P5CMF has received over half of a million dollars in donations, and has provided funding for eight different individuals to contribute over 9,000 service hours towards improving performance, stability, and features for Perl 5. (Full history </span><a href="https://docs.google.com/spreadsheet/pub?key=0AkU6pBm3WGeedGlqV1d0OXFVaG8yVTVDRFI5c0hLOHc&amp;output=html" style="text-decoration: none;"><span style="font-size: 11pt; font-family: Arial; color: #1155cc; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: underline; vertical-align: baseline;">here</span></a><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">)</span></p>
  219. <p dir="ltr" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"></p>
  220. <p></p>]]>
  221.        <![CDATA[<p><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Two of the current recipients of the P5CMF grants are nearing the end of their allocations: Tony Cook will have depleted his allocation by the end of October and <a href="http://news.perlfoundation.org/2017/10/grant-extension-request-mainta-5.html">has already requested an extension</a>. David Mitchell will likely need an extension to his fund in February 2018. Typically these grants are extended in $20,000 increments.</span></p>
  222. <p><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">Presently, the P5CMF has $8,426 remaining in unallocated funds. The Perl Foundation board has already moved $20,000 from its general fund to the P5CMF (as well as a matching $20,000 to the sister Perl 6 fund) in July of this year and is currently considering moving an additional $20,000 to the fund to cover Tony Cook's current grant extension request. These extensions were made possible through the generous support of our annual sponsors: craigslist, cPanel, bluehost, Grant Street Group, and Assurant.</span></p>
  223. <p><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">For targeted funds like the Perl 5 core maintenance fund, the goal is to allow donors to show their support for the work the fund enables through new donations. We believe this fund is important and valuable for everyone who relies on the health and continued development of Perl 5, but without additional donations we may need to consider closing the fund. We need your support to make sure that doesn't happen.</span></p>
  224. <p><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">If you would like to make a tax-deductible contribution to The Perl Foundation's Perl 5 Core Maintenace Fund, you may do so </span><a href="https://www.z2systems.com/np/clients/perlfoundation/donation.jsp?campaign=2&amp;" style="text-decoration: none;"><span style="font-size: 11pt; font-family: Arial; color: #1155cc; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: underline; vertical-align: baseline;">here</span></a><span style="font-size: 11pt; font-family: Arial; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline;">. As a thank-you gift, we will send you an "I patched Perl\x9d" adhesive patch for every $50 contributed to the fund (maximum 5 patches). </span></p>]]>
  225.    </content>
  226. </entry>
  227.  
  228. <entry>
  229.    <title>Maintaining Perl 5 (Tony Cook): Grant Report for September 2017</title>
  230.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/10/maintaining-perl-5-tony-cook-g-3.html" />
  231.    <id>tag:news.perlfoundation.org,2017://18.3920</id>
  232.  
  233.    <published>2017-10-25T22:00:00Z</published>
  234.    <updated>2017-10-25T02:03:18Z</updated>
  235.  
  236.    <summary>This is a monthly report by Tony Cook on his grant under Perl 5 Core Maintenance Fund. We thank the TPF sponsors to make this grant possible....</summary>
  237.    <author>
  238.        <name>Makoto Nozaki</name>
  239.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  240.    </author>
  241.    
  242.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  243.    
  244.        <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category" />
  245.    
  246.    
  247.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  248.        <![CDATA[<p>This is a monthly report by Tony Cook on his grant under <a href="http://www.perlfoundation.org/perl_5_core_maintenance_fund">Perl 5 Core Maintenance Fund</a>. We thank the TPF sponsors to make this grant possible.</p>
  249. ]]>
  250.        <![CDATA[<pre>Approximately 47 tickets were reviewed, and 7 patches were applied.
  251.  
  252. [Hours]         [Activity]
  253.  7.13          #122112 work on a fix (and reentr discussion with khw)
  254.                #122112 more work on a fix
  255.                #122112 debugging
  256.                #122112 debugging
  257.                #122112 debugging, look for a different approach
  258.  2.31          #124256 re-work patch
  259.                #124256 more re-work patch, testing
  260.  3.94          #125351 try to understand the parser
  261.                #125351 try restoring stack, debug crashes
  262.                #125351 experiments, testing, debugging
  263.  1.82          #126706 re-work patch a bit, testing, debugging
  264.                #126706 debugging, fix taint issue
  265.  7.01          #127663 re-check, minor commit message changes, comment
  266.                with new patch
  267.                #127663 testing
  268.                #127663 more testing, apply to blead
  269.                #127663 reproduce, work on a fix, testing
  270.                #127663 more testing
  271.                #127663 comment on freebsd renameat() ticket
  272.  1.98          #129990 review, testing, coverage checks, benchmarking,
  273.                apply to blead
  274.  2.36          #131582 (sec) work on CVE details, comment
  275.                #131582, #131598 (sec) work with downstream
  276.                #131582, #131598 (sec) work with downstream
  277.  0.57          #131598 (sec) work on CVE details, comment
  278.  3.32          #131648 (sec) debugging
  279.                #131648 (sec) more debugging, briefly comment
  280.  0.77          #131665 (sec) work on CVE details, comment
  281.                #131665 (sec) comment
  282.  1.58          #131683 comment
  283.                #131683 comment
  284.                #131683 review patch, discussion in #p5p
  285.  0.70          #131685 research
  286.  1.15          #131746 retesting, apply to blead
  287.  1.45          #131777 re-base, re-check, re-test and apply to blead
  288.  2.21          #131894 research how to fix non-hex digit handling for
  289.                hex^Wbinaryfp numbers
  290.                #131894 work on a fix, testing
  291.                #131894 add more tests, testing, comment with patch
  292.  1.18          #131954 (sec) research and comment
  293.  1.51          #131982 research, comment
  294.                #131982 work on a patch and comment with patch
  295.  0.95          #131984 comment
  296.                #131984 re-review, testing, apply to blead
  297.  0.67          #132001 debugging, reject with comment
  298.  3.24          #132008 testing, minor fixes, apply to blead
  299.                #132008 look into regression, start setup of test VM
  300.                #132008 discussion with Tux, finish VM setup, also discuss
  301.                spam when smokes run in PERL_UNICODE= LC_ALL=some-utf8-
  302.                locale mode, work on a fix and apply to blead
  303.  0.17          #132017 (sec) comment
  304.  1.74          #132055 (sec) reproduce, debugging
  305.                #132055 (sec) debugging, ask khw to look at it
  306.  0.20          #132063 (sec) debugging, ask khw again
  307.  0.75          #132077 review patches and comment
  308.  3.02          #132087 testing, research, comment with patch, comment
  309.                with fixed patch
  310.                #132087, #127663 re-test various portability fixes and
  311.                apply to blead
  312.  0.28          #132094 research and comment
  313.  1.53          #132105 research and comment
  314.                #132105 look at making SIG_SIZE a variable, check CPAN for
  315.                usage and comment
  316.  0.05          #132134 review and comment
  317.  0.33          #132137 research and comment
  318.  1.03          #132138 work to understand failure, fix and apply to blead
  319.  0.20          #132139 track down when minitest was introduced and
  320.                comment
  321.  1.23          #132147 (sec) research, comment
  322.  0.95          #132158 (sec) debugging, comment
  323.  0.42          #132159 review patch and comment
  324.  0.60          #132163 debugging, comment, more debugging
  325.  0.62          #132171 review patch and comment
  326.  0.10          Configure changes from 5.24.1 to 5.26.1 thread: comment
  327.  0.38          Configure changes from 5.24.1 to 5.26.1 thread: research
  328.                and comment
  329.  0.15          nigel’s arm builds: review build error, research and
  330.                comment
  331.  0.52          pin down CVE issues versions manually
  332.  0.07          security ticket follow-up
  333.  0.12          tes::readline fixe to backport list
  334.  0.58          test openbsd fix for khw
  335.  0.42          Try to pin down CVE issue versions with bisect
  336.  0.70          update CVE entries at Mitre
  337.  2.03          work on cleaning up build noise under PERL_UNICODE= ,
  338.                testing, apply to blead
  339.  2.92          Work on cleaning up test noise under PERL_UNICODE=
  340. ======
  341. 66.96 hours total</pre>
  342. ]]>
  343.    </content>
  344. </entry>
  345.  
  346. <entry>
  347.    <title>Grant Update: Test2 Manual by Chad Granum</title>
  348.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/10/grant-update-test2-manual-by-c.html" />
  349.    <id>tag:news.perlfoundation.org,2017://18.3921</id>
  350.  
  351.    <published>2017-10-25T11:08:56Z</published>
  352.    <updated>2017-10-25T11:12:24Z</updated>
  353.  
  354.    <summary>Chad has been working on his Test2 manual. The fact that he is, also, maintaining Test2 modules, and implementing or refactoring some portions of these modules make the documentation process harder, as it need the changes done before documenting them. Nevertheless, in the last month, Chad has been updating the documentation given outdated information, and added some new sections. He also added a lot of new section titles referring subjects he intends to write about....</summary>
  355.    <author>
  356.        <name>Alberto Simões</name>
  357.        <uri>http://blogs.perl.org/users/alberto_simoes/</uri>
  358.    </author>
  359.    
  360.    
  361.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  362.        <![CDATA[<p>Chad has been working on his Test2 manual. The fact that he is, also, maintaining Test2 modules, and implementing or refactoring some portions of these modules make the documentation
  363. process harder, as it need the changes done before documenting them.</p>
  364.  
  365. <p>Nevertheless, in the last month, Chad has been updating the <a href="https://github.com/Test-More/Test2-Manual/commit/eb5c04aee1d7a64246670030da9ba57d273b3e3f">documentation</a>
  366. given outdated information, and added some new sections. He also added a lot of new section titles referring subjects he intends to write about. </p>
  367. ]]>
  368.        
  369.    </content>
  370. </entry>
  371.  
  372. <entry>
  373.    <title>Call for Organizers - TPCNA::2018</title>
  374.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/10/call-for-organizers-tpcna2018.html" />
  375.    <id>tag:news.perlfoundation.org,2017://18.3919</id>
  376.  
  377.    <published>2017-10-23T15:00:00Z</published>
  378.    <updated>2017-10-23T21:28:37Z</updated>
  379.  
  380.    <summary> Have you ever felt like you&apos;d love to do more for the Perl community? Have you ever been at a YAPC or TPC and thought &quot;I know JUST the way to improve this aspect of the conference!&quot;? Have you been wanting to donate hours and hours of your time and just not been able to find the perfect place to do so? If you answered &quot;Yes!&quot; to any of these questions, have I got the perfect opportunity for you!...</summary>
  381.    <author>
  382.        <name>Lena Hand</name>
  383.        
  384.    </author>
  385.    
  386.        <category term="Conferences" scheme="http://www.sixapart.com/ns/types#category" />
  387.    
  388.    <category term="tpc" label="TPC" scheme="http://www.sixapart.com/ns/types#tag" />
  389.    <category term="tpcna" label="TPC::NA" scheme="http://www.sixapart.com/ns/types#tag" />
  390.    <category term="tpcna" label="TPCNA" scheme="http://www.sixapart.com/ns/types#tag" />
  391.    <category term="yapc" label="YAPC" scheme="http://www.sixapart.com/ns/types#tag" />
  392.    <category term="yapcna" label="YAPC::NA" scheme="http://www.sixapart.com/ns/types#tag" />
  393.    <category term="yapcna" label="YAPCNA" scheme="http://www.sixapart.com/ns/types#tag" />
  394.    
  395.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  396.        <![CDATA[<ul>
  397. <li><p>Have you ever felt like you'd love to do more for the Perl community?</p></li>
  398. <li><p>Have you ever been at a YAPC or TPC and thought "I know JUST the way to improve this aspect of the conference!"?</p></li>
  399. <li><p>Have you been wanting to donate hours and hours of your time and just not been able to find the perfect place to do so? </p></li>
  400. </ul>
  401.  
  402. <p>If you answered "Yes!" to any of these questions, have I got the perfect opportunity for you! </p>
  403.  
  404. <p>The Perl Conference Organizing Committee for the 2018 NEEDS <strong>your</strong> help! </p>
  405.  
  406. <p>Please fill out the application at the following link to show your interest:
  407. <a href="https://goo.gl/qEogwS">https://goo.gl/qEogwS</a></p>
  408. ]]>
  409.        
  410.    </content>
  411. </entry>
  412.  
  413. <entry>
  414.    <title>Grant Extension Request: Maintaining the Perl 5 (Tony Cook)</title>
  415.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/10/grant-extension-request-mainta-5.html" />
  416.    <id>tag:news.perlfoundation.org,2017://18.3918</id>
  417.  
  418.    <published>2017-10-21T21:30:00Z</published>
  419.    <updated>2017-10-22T03:35:58Z</updated>
  420.  
  421.    <summary>Tony Cook has requested an extension of $20,000 for his Maintaining the Perl 5 grant. This will allow him to dedicate another 400 hours to this work. During this grant he sent regular reports to the p5p mailing list as well as providing monthly summary reports that have been published on this site, the most recent of which are linked below: August 2017 July 2017 May/June 2017 Before we make a decision on this extension, we would like to have...</summary>
  422.    <author>
  423.        <name>Makoto Nozaki</name>
  424.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  425.    </author>
  426.    
  427.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  428.    
  429.        <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category" />
  430.    
  431.    
  432.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  433.        <![CDATA[<p><strong>Tony Cook</strong> has requested an extension of $20,000 for his <strong>Maintaining the Perl 5</strong> grant. This will allow him to dedicate another 400 hours to this work. During this grant he sent regular reports to the p5p mailing list as well as providing monthly summary reports that have been published on this site, the most recent of which are linked below:</p>
  434.  
  435. <ul>
  436. <li><a href="http://news.perlfoundation.org/2017/09/maintaining-perl-5-tony-cook-g-2.html">August 2017</a></li>
  437. <li><a href="http://news.perlfoundation.org/2017/09/maintaining-perl-5-tony-cook-g-1.html">July 2017</a></li>
  438. <li><a href="http://news.perlfoundation.org/2017/08/maintaining-perl-5-tony-cook-g.html">May/June 2017</a></li>
  439. </ul>
  440.  
  441. <p>Before we make a decision on this extension, we would like to have a period of community consultation. Please leave feedback in the comments field below or if you prefer, send email with your comments to makoto at perlfoundation.org. We request that all the feedback should be sent by Oct 29th.</p>
  442.  
  443. <p>If successful this extension will be funded from the <a href="http://www.perlfoundation.org/perl_5_core_maintenance_fund">Perl 5 Core Maintenance Fund</a>.</p>
  444. ]]>
  445.        
  446.    </content>
  447. </entry>
  448.  
  449. <entry>
  450.    <title>September 2017 Grant Votes</title>
  451.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/10/september-2017-grant-votes.html" />
  452.    <id>tag:news.perlfoundation.org,2017://18.3917</id>
  453.  
  454.    <published>2017-10-07T20:17:16Z</published>
  455.    <updated>2017-11-12T18:53:44Z</updated>
  456.  
  457.    <summary>The Grants Committee has concluded the voting of the September 2017 round. There were two proposals in this round....</summary>
  458.    <author>
  459.        <name>Coke</name>
  460.        
  461.    </author>
  462.    
  463.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  464.    
  465.    
  466.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  467.        <![CDATA[<p>The Grants Committee has concluded the voting of the September 2017 round.</p>
  468.  
  469. <p>There were two proposals in this round.</p>
  470. ]]>
  471.        <![CDATA[<h1>Rakudo Perl 6 performance analysis tooling  </h1>
  472.  
  473. <p><a href="http://news.perlfoundation.org/2017/09/grant-proposal-rakudo-perl-6-p.html">Performance Analysis (7,500 USD)</a></p>
  474.  
  475. <p>Voting results: 7 Yes votes, and 2 abstentions with a score of 33 (5 votes of 5, 2 votes of 4)</p>
  476.  
  477. <p>This grant is approved, and will be funded.</p>
  478.  
  479. <h1>Start Act Voyager</h1>
  480.  
  481. <p><a href="http://news.perlfoundation.org/2017/09/grant-proposal-act-voyager.html">Voyager (7,500 USD)</a></p>
  482.  
  483. <p>Voting results: 2 Yes votes, 1 abstention, and 6 No votes</p>
  484.  
  485. <p>This grant is not approved. Concerns were raised about the previous related grant by the same submitter that was not successful.</p>
  486.  
  487. <h1>Next Round </h1>
  488.  
  489. <p>We accept proposals throughout the year; our next round of voting would be in November, but since we have allocated all the
  490. funding from our budget for the calendar year, there will be no explicit call for grants in November/December. The next call
  491. will be in January of 2018. </p>
  492.  
  493. <p>You can <a href="http://www.perlfoundation.org/how_to_write_a_proposal" title="submit proposals">submit proposals</a> now.
  494. If you want to help funding and increase our budget, please visit <a href="https://donate.perlfoundation.org/" title="our donations page">our donations page</a>
  495. We sincerely appreciate all the donors which made the grant
  496. program possible. Also see the <a href="http://www.perlfoundation.org/press_releases" title="press releases">press releases</a> for
  497. the recent major donations.</p>
  498. ]]>
  499.    </content>
  500. </entry>
  501.  
  502. <entry>
  503.    <title>Grant: Improving the Robustness of Unicode Support - Completed</title>
  504.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/10/completed.html" />
  505.    <id>tag:news.perlfoundation.org,2017://18.3916</id>
  506.  
  507.    <published>2017-10-07T19:51:35Z</published>
  508.    <updated>2017-10-07T20:15:07Z</updated>
  509.  
  510.    <summary>I&apos;m happy to announce that the GC has voted to accept the completion of the grant http://news.perlfoundation.org/2017/04/grant-proposal.html by Samantha McVey (samcv)...</summary>
  511.    <author>
  512.        <name>Coke</name>
  513.        
  514.    </author>
  515.    
  516.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  517.    
  518.    
  519.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  520.        <![CDATA[<p>I'm happy to announce that the GC has voted to accept the completion of the grant
  521. <a href="http://news.perlfoundation.org/2017/04/grant-proposal.html" title="Improving the Robustness of Unicode Support in Rakudo">http://news.perlfoundation.org/2017/04/grant-proposal.html</a>
  522. by Samantha McVey (samcv)</p>
  523. ]]>
  524.        
  525.    </content>
  526. </entry>
  527.  
  528. <entry>
  529.    <title>Final Report: Start ACT - Voyager </title>
  530.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/10/final-report-start-act---voyag.html" />
  531.    <id>tag:news.perlfoundation.org,2017://18.3915</id>
  532.  
  533.    <published>2017-10-07T19:23:30Z</published>
  534.    <updated>2017-10-07T20:14:57Z</updated>
  535.  
  536.    <summary>This is a bookkeeping post regarding the 2014 Grant &quot;Start ACT - Voyager&quot;. Due to the Grant Committee&apos;s rules of operations, this grant was cancelled due to lack of progress in August of 2017....</summary>
  537.    <author>
  538.        <name>Coke</name>
  539.        
  540.    </author>
  541.    
  542.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  543.    
  544.    
  545.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  546.        <![CDATA[<p>This is a bookkeeping post regarding the 2014 Grant "Start ACT - Voyager".</p>
  547.  
  548. <p>Due to the Grant Committee's rules of operations, this grant was cancelled due to lack
  549. of progress in August of 2017.</p>
  550. ]]>
  551.        
  552.    </content>
  553. </entry>
  554.  
  555. <entry>
  556.    <title>Grant Report : Complete YAML::PP - September 2017</title>
  557.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/09/grant-report-complete-yamlpp--.html" />
  558.    <id>tag:news.perlfoundation.org,2017://18.3914</id>
  559.  
  560.    <published>2017-09-30T15:25:46Z</published>
  561.    <updated>2017-09-30T15:34:16Z</updated>
  562.  
  563.    <summary>Tinita has already achieved much in a short time on her grant to Complete YAML::PP. She has provided full details at blogs.perl.org. Some highlights: Produced YAML::PP::Lexer, ::Parser, ::Dumper, ::Emitter, ::Reader, ::Highlight Continued work towards full YAML 1.2 compliance Allows Unicode chars Bugfixes, refactors and miscellaneous doodads Code is on github. You&apos;re wondering &quot;What&apos;s so cool about this?&quot; Check out Tinita&apos;s talk where you can learn all about the secret features of YAML that few parsers get right. You&apos;re asking &quot;How...</summary>
  564.    <author>
  565.        <name>Mark A Jensen</name>
  566.        
  567.    </author>
  568.    
  569.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  570.    
  571.        <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category" />
  572.    
  573.    <category term="grants" label="grants" scheme="http://www.sixapart.com/ns/types#tag" />
  574.    <category term="yaml" label="yaml" scheme="http://www.sixapart.com/ns/types#tag" />
  575.    
  576.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  577.        <![CDATA[<p>Tinita has already achieved much in a short time on her grant to <a href="http://news.perlfoundation.org/2017/08/grant-proposal-complete-yamlpp.html">Complete YAML::PP</a>. She has provided full details at <a href="http://blogs.perl.org/users/tinita/2017/09/yamlpp-grant-report-augustseptember-2017.html">blogs.perl.org</a>. Some highlights:</p>
  578.  
  579. <ul>
  580. <li>Produced YAML::PP::Lexer, ::Parser, ::Dumper, ::Emitter, ::Reader, ::Highlight</li>
  581. <li>Continued work towards full YAML 1.2 compliance</li>
  582. <li>Allows Unicode chars</li>
  583. <li>Bugfixes, refactors and miscellaneous doodads</li>
  584. </ul>
  585.  
  586. <p>Code is on <a href="https://github.com/perlpunk/YAML-PP-p5">github</a>.</p>
  587.  
  588. <p>You're wondering "What's so cool about this?" Check out <a href="https://perlpunk.github.io/slides.tpcia2017/the-state-of-the-yaml">Tinita's talk</a> where you can learn all about the secret features of YAML that few parsers get right.</p>
  589.  
  590. <p>You're asking "How can I help?". Tina sez:</p>
  591.  
  592. <p>"If you have YAML data that you think should be valid, but YAML::PP can't parse it (or the other way around), please create an issue or send it to me (of course, you have to take into account the features not implemented yet).</p>
  593.  
  594. <p>You can simply do:</p>
  595.  
  596. <p>```</p>
  597.  
  598. <pre><code>% yamlpp5-highlight &lt; file.yaml
  599. # ANSI colored YAML
  600. % yamlpp5-load &lt; file.yaml
  601. # Data::Dumper output
  602. % yamlpp5-load-dump &lt; file.yaml
  603. # Load and Dump back into YAML
  604. % yamlpp5-events &lt; file.yaml
  605. # Show parsing events in yaml-test-suite format
  606. </code></pre>
  607.  
  608. <p>```</p>
  609.  
  610. <p>I'm happy to receive suggestions and comments on the API."</p>
  611.  
  612. <p>MAJ</p>
  613. ]]>
  614.        
  615.    </content>
  616. </entry>
  617.  
  618. <entry>
  619.    <title>Final Report : Grant &quot;Robust Perl 6 Unicode Support&quot;</title>
  620.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/09/final-report-grant-robust-perl.html" />
  621.    <id>tag:news.perlfoundation.org,2017://18.3913</id>
  622.  
  623.    <published>2017-09-28T01:52:40Z</published>
  624.    <updated>2017-09-28T01:56:23Z</updated>
  625.  
  626.    <summary>Samantha has submitted her last grant update and her final review of her work for the consideration of the community and the Grants Committee. Highlights for the latest month of work include: Her Unicode Collation Algorithm is fully merged into MoarVM She has released full UCA documentation Prepends are handled with more generality, so that edge cases in certain ops now work properly Bugs in encoding into and handling UTF8-C8 have been squashed In the Final Report section, Samantha reviews...</summary>
  627.    <author>
  628.        <name>Mark A Jensen</name>
  629.        
  630.    </author>
  631.    
  632.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  633.    
  634.        <category term="Perl 6 Development" scheme="http://www.sixapart.com/ns/types#category" />
  635.    
  636.    <category term="grants" label="grants" scheme="http://www.sixapart.com/ns/types#tag" />
  637.    <category term="unicode" label="unicode" scheme="http://www.sixapart.com/ns/types#tag" />
  638.    
  639.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  640.        <![CDATA[<p>Samantha has submitted <a href="https://cry.nu/perl6/grant-report/">her last grant update and her final review of her work</a> for the consideration of the community and the Grants Committee.</p>
  641.  
  642. <p>Highlights for the latest month of work include:</p>
  643.  
  644. <ul>
  645. <li>Her Unicode Collation Algorithm is fully merged into MoarVM</li>
  646. <li>She has released full <a href="https://github.com/MoarVM/MoarVM/blob/master/docs/collation.asciidoc">UCA documentation</a></li>
  647. <li>Prepends are handled with more generality, so that edge cases in certain ops now work properly</li>
  648. <li>Bugs in encoding into and handling UTF8-C8 have been squashed</li>
  649. </ul>
  650.  
  651. <p>In the Final Report section, Samantha reviews her many achievements and deliverables. These can be compared to the inchstones and goals of <a href="http://news.perlfoundation.org/2017/04/grant-proposal.html">her original proposal</a>.</p>
  652.  
  653. <p>The Grants Committee would appreciate comments regarding this grant and its state of completion before it votes on whether to approve the work and proceed to payment. Please make any such comments to this post.</p>
  654.  
  655. <p>MAJ</p>
  656. ]]>
  657.        
  658.    </content>
  659. </entry>
  660.  
  661. <entry>
  662.    <title>Grant Proposal: Act Voyager</title>
  663.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/09/grant-proposal-act-voyager.html" />
  664.    <id>tag:news.perlfoundation.org,2017://18.3912</id>
  665.  
  666.    <published>2017-09-20T01:10:38Z</published>
  667.    <updated>2017-10-07T19:17:19Z</updated>
  668.  
  669.    <summary>The Grants Committee has received the following grant proposal for the September/October 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 September 26th, 2017. The Committee members will start the voting process following that and the conclusion will be announced the first week of October. Act Voyager Name: Theo van Hoesel Amount Requested: USD 7,500 Synopsis A Modern rebuild of the...</summary>
  670.    <author>
  671.        <name>Coke</name>
  672.        
  673.    </author>
  674.    
  675.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  676.    
  677.    
  678.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  679.        <![CDATA[<p>The Grants Committee has received the following grant proposal for the September/October round.
  680. Before the Committee members vote, we would like to solicit feedback from the Perl community on the proposal.</p>
  681.  
  682. <p>Review the proposal below and please comment here by September 26th, 2017.
  683. The Committee members will start the voting process following that and the conclusion
  684. will be announced the first week of October.</p>
  685.  
  686. <h1>Act Voyager</h1>
  687.  
  688. <ul>
  689. <li><p>Name:</p>
  690.  
  691. <p>Theo van Hoesel</p></li>
  692. <li><p>Amount Requested:</p>
  693.  
  694. <p>USD 7,500</p></li>
  695. </ul>
  696.  
  697. <h2>Synopsis</h2>
  698.  
  699. <p>A Modern rebuild of the Conference Tool Kit.</p>
  700. ]]>
  701.        <![CDATA[<p>Act, as we know it, has been build more than a decade ago for Apache 1 and
  702. mod-perl 1.3 architecture. And it has served the Perl Community very well over
  703. all those years and hundreds of events.</p>
  704.  
  705. <p>But over the last year we have suffered from major outages. And since the
  706. operating sytem it self being used to run on, has passed it LTS, more recent
  707. compilers being packed, it has become extremely difficult (if not impossible) to
  708. rebuild Act from scratch.</p>
  709.  
  710. <p>Also, Act as it is now, is no longer maintained in a pro-active manner, due to
  711. it's archaic design - and people having other priorities.</p>
  712.  
  713. <p>Lastly, due to the flexibility off how it has been designed it comes with such a
  714. complexity, that it is hard and difficult for current organisers to deliver new
  715. websites for each and every conference or workshop they want to promote. Of
  716. course, this also relates to the fact that most of the Perl developers are not
  717. the best frontend designers.</p>
  718.  
  719. <p>Reasons enough to stop using Act, as a toolkit, it has become rusty and unfit
  720. for the job. It has come to the point that Act should be to REST.</p>
  721.  
  722. <h2>Benefits to the Perl Community</h2>
  723.  
  724. <p>The future is quite clear. Act requires a giant leap forward to keep up with the
  725. demands of today users.</p>
  726.  
  727. <p>Visitors that come to the website should experience that Perl, although a
  728. language with a longstanding history, is still keeping up and pushing the bar to
  729. a higher level for competing alternatives. The user experience should be up to
  730. modern expectations. Therefor Act Voyager will include a revamped frontend. And
  731. hopefully will make it more likely to attract new people to the Community,
  732. rather then putting people off on their first impression (as we know from Perl
  733. Monks).</p>
  734.  
  735. <p>Organisers should be enabled to quickly and easaly set up a new event. That
  736. should be as easy as setting a date, selecting a frontend theme and additional
  737. styling. The admin part of Act would be decoupled from the public website. This
  738. makes it much easier to implement, without messing with the public website
  739. interface. This admin part would also need new tools that connect with Social
  740. Media and allow simple things as sending emails. Previous organisers will
  741. recognise all the hassle to get it up and running and most would wish it was
  742. more easy to communicate with attendees and prospective Community members.</p>
  743.  
  744. <h2>Deliverables</h2>
  745.  
  746. <h3>Act-out-of-the-Box</h3>
  747.  
  748. <p>A 'must have' for working on anything related to Act, more specific, anything
  749. related to the Legacy code base.</p>
  750.  
  751. <h3>Open API spec (aka Swagger)</h3>
  752.  
  753. <p>This YAML specification of an API will describe the interface.</p>
  754.  
  755. <p>Rather than just writing code and deliver something that would look okay, it's
  756. important to have a good definition of what the API looks like - much like Test
  757. Driven Development.</p>
  758.  
  759. <h3>API server</h3>
  760.  
  761. <p>Based on the above Specification, there will an API server that talks to the
  762. Legacy Act databases.</p>
  763.  
  764. <h3>Act CLI</h3>
  765.  
  766. <p>As a side product, mostly for testing purposes, there will be a simple command
  767. line interface. Extremely useful for admins and people that dislike modern web.</p>
  768.  
  769. <h3>Theme based web-server</h3>
  770.  
  771. <p>A Dancer2 application that will provide the HTML, JavaScript, and CSS needed to
  772. access a Perl Event web page.</p>
  773.  
  774. <h3>Improve Modules</h3>
  775.  
  776. <ul>
  777. <li>Dancer2::Plugin::HTTP::Auth::Extensible</li>
  778. <li>Dancer2::Plugin::HTTP::Caching</li>
  779. <li>Dancer2::Plugin::HTTP::ConditionalRequest</li>
  780. <li>Dancer2::Plugin::HTTP::ContentNegotiation</li>
  781. <li>LPW::UserAgent::Caching</li>
  782. <li>HTTP::Caching</li>
  783. </ul>
  784.  
  785. <h2>Project Details</h2>
  786.  
  787. <h3>Act-out-of-the-Box</h3>
  788.  
  789. <p>Since it's a nightmare to build Act from scratch - DO NOT TRY THIS AT HOME - it
  790. comes with Apache 1.3.x and mod-perl 1.31. It also includes a recent checkout
  791. of the Git repository and it's dependancies.</p>
  792.  
  793. <p>This will benefit organisers to work on their website and test locally before
  794. committing and merging with the 'Act-Conferences' repository.</p>
  795.  
  796. <p>It will also help developers that desire to fix bugs in the legacy codebase of
  797. Act... or add new features.</p>
  798.  
  799. <p>This part has almost finished. I have gone through dozens and dozens off
  800. iterations to get it working. Luckily I had a back up from a previous attempt
  801. from some years ago. It only needs some nice script to make it easy for an
  802. organiser to add a conference, linked to GitHub.</p>
  803.  
  804. <h3>Open API specification</h3>
  805.  
  806. <p>There are many tools available around the Oen API specification that will help
  807. backend developers to test their implementations. There are also tools available
  808. to run a API simulation. And many more...</p>
  809.  
  810. <p>The Specification will be a living document and contributions are welcome. But
  811. whatever the specification will be, that will be what client and server will
  812. to agree on. This will open up the way developers can work on separate products.
  813. With a proper Specification, it is possible to built different clients (like iOS
  814. applications) and servers.</p>
  815.  
  816. <p>The specification can be just one big file and will soon become messy. This year
  817. I started out writing the specification, split over several files. This will
  818. make it much more easy to maintain. The current setup passes the OAS validation.</p>
  819.  
  820. <p>More endpoints and objects will need to be added. But I also hope that people
  821. interested in the project will comment on the repo and make pull-requests.</p>
  822.  
  823. <h3>API server</h3>
  824.  
  825. <p>Most likely, this will be build on top of Dancer2, using a few plugins that deal
  826. with the correct handling of HTTP request headers in requests and responses.</p>
  827.  
  828. <h3>Web Server</h3>
  829.  
  830. <p>This will be a minimal viable product.</p>
  831.  
  832. <p>Themes used for this server should obtain their data through the REST api. And
  833. since it has a strict separation between data and presentation, actually anyone
  834. could build their own server that talks to the API ... when following the
  835. Specification.</p>
  836.  
  837. <p>The server will also include a 'page' that enable a user to manage their own
  838. settings and make payments.</p>
  839.  
  840. <h3>Improve Modules</h3>
  841.  
  842. <p>There are some modules I already published on CPAN, but need a little more after
  843. care. Some lack proper tests, some actually fail after changes in Dancer2.</p>
  844.  
  845. <p>I've written those modules, because I felt they were needed to make this entire
  846. project succeed. But the Perl Dancer developers have a good level of minimum
  847. requirements before being acknowledged and accepted as real Dancer2 plugins.</p>
  848.  
  849. <p>LWP::UserAgent::Caching, and it's dependancy HTTP::Caching, require a bit more
  850. development. So far, it's the only RFC compliant library.</p>
  851.  
  852. <p>The module will be needed in the CLI client. The REST api will only serve
  853. 'simple' (JSON) objects. And because off that, they are cacheable. But there was
  854. no UserAgent that was capable of handling HTTP requests or responses as it was
  855. defined by the RFC's.</p>
  856.  
  857. <h2>Inch-stones</h2>
  858.  
  859. <h3>Act-out-of-the-Box</h3>
  860.  
  861. <ul>
  862. <li>create script to add a conference and checkout wit GitHub</li>
  863. <li>save as a Vagrant Box</li>
  864. <li>write documentation for organisers and developers</li>
  865. </ul>
  866.  
  867. <h3>Open API Specification</h3>
  868.  
  869. <ul>
  870. <li>add specification for <code>user</code></li>
  871. <li>add specification for <code>talk</code></li>
  872. <li>add specification for <code>confernce</code></li>
  873. <li>add specification for <code>attendee</code></li>
  874. <li>add specification for <code>...</code></li>
  875. </ul>
  876.  
  877. <h3>Improving Modules</h3>
  878.  
  879. <ul>
  880. <li><p>Dancer2::Plugin::HTTP::AuthExtensible</p>
  881.  
  882. <p>probably quite some rewrite, but there is quite some willingness to support that
  883. work from the Dancer Core developers</p></li>
  884. <li><p>Dancer2::Plugin::HTTP::Caching</p>
  885.  
  886. <ul>
  887. <li>add tests and anything else that would enhance the kwalitee</li>
  888. </ul></li>
  889. <li>Dancer2::Plugin::HTTP::ConditionalRequest
  890. <ul>
  891. <li>add tests and anything else that would enhance the kwalitee</li>
  892. </ul></li>
  893. <li>Dancer2::Plugin::HTTP::ContentNegotiation
  894. <ul>
  895. <li>add tests and anything else that would enhance the kwalitee</li>
  896. </ul></li>
  897. <li>HTTP::Caching
  898. <ul>
  899. <li>Responses should have <code>Age</code> header</li>
  900. <li>successful <code>Delete</code> request should delete the cached data</li>
  901. </ul></li>
  902. </ul>
  903.  
  904. <h3>Moo Classes for business and transport objects and data access objects.</h3>
  905.  
  906. <p>This requires a little chat with some respectable Perl developers. But basically
  907. I want a true separation of the business object and how it has been retrieved or
  908. stored or updated.</p>
  909.  
  910. <p>This makes it possible to use the same object on the CLI and on the server, with
  911. the only difference that the former talks to the REST api and the latter to the
  912. database.</p>
  913.  
  914. <h3>API Server</h3>
  915.  
  916. <ul>
  917. <li>create simple route</li>
  918. <li>add authentication and authorization</li>
  919. <li>add more routes as described in the Open API specification</li>
  920. </ul>
  921.  
  922. <h3>CLI</h3>
  923.  
  924. <ul>
  925. <li><p>figure out how to easy build a CLI from a Swagger file</p>
  926.  
  927. <p>Tina Muller has done some tremendous work on that</p></li>
  928. <li><p>get it working for a <code>user</code> object</p></li>
  929. <li><p>add more command options</p>
  930.  
  931. <p>as the Specification is becoming more complete, and the API get more endpoints,
  932. the CLI will grow with it.</p></li>
  933. </ul>
  934.  
  935. <h3>Theme Based WEB Server</h3>
  936.  
  937. <p>This requires some more investigation, but I have very strong connection with
  938. some very reputable front end developer that knows how to build a front end.</p>
  939.  
  940. <p>But it basically comes down - when using Angular2 with Bootstrap 4 to just go
  941. along with the growth of the API.</p>
  942.  
  943. <h2>Project Schedule</h2>
  944.  
  945. <p>The project is quite big, but within the first few weeks, it will at least have
  946. made good progress on the first two deliverables.</p>
  947.  
  948. <p>The hard part will be to get an initial 'prototype' of the REST api working. I
  949. expect that to have finished within two months after having the Vagrant Box up
  950. and running.</p>
  951.  
  952. <p>The CLI will follow probably another month later.</p>
  953.  
  954. <p>From there on, it's a matter of adding more endpoints and command options as the
  955. Swagger files gets updated.</p>
  956.  
  957. <p>A first release of the web-server will probably follow four to six months after
  958. the CLI.</p>
  959.  
  960. <p>Since the size of the project, it would be about a year before the MVP will be
  961. ready.</p>
  962.  
  963. <h2>Completeness Criteria</h2>
  964.  
  965. <p>Well, a minimal viable product, a working theme-based website. It should at
  966. least cover 80% of the common user stories for a general conference attendee.
  967. This includes a personal web-page to edit and manage settings.</p>
  968.  
  969. <p>For the other admin tasks, I would stick to a proper CLI for now.</p>
  970.  
  971. <h2>Bio</h2>
  972.  
  973. <p>I have initially started work on this project some years ago and am very eager
  974. to continue work on this.</p>
  975.  
  976. <p>I've done a lot of research on REST api's and given some presentations on that.</p>
  977.  
  978. <p>In the last three years I've also organised three Perl Workshops in the
  979. Netherlands - and was the main organiser of The Perl Conference in Amsterdam.</p>
  980.  
  981. <p>This has given me a lot of insight in how Act has been designed and what the
  982. difficulties are with the current legacy version.</p>
  983.  
  984. <p>A year ago I did give a presentation during the Perl Dancer conference. This
  985. was a summary of my work done so far and how all the puzzle pieces would fit
  986. together to build Act-Voyager.</p>
  987.  
  988. <p>Compared to three years ago, I've grown much more in experience as a Perl
  989. Developer. This new application is much better than the previous and based on
  990. personal experience working on on the project intermittently.</p>
  991.  
  992. <p>While organising TPCiA, I was facing quite some difficulties that caused delay
  993. in further development of Act Voyager. Now that has finished, time has come
  994. available.</p>
  995. ]]>
  996.    </content>
  997. </entry>
  998.  
  999. </feed>
  1000.  

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

  1. Download the "valid Atom 1.0" banner.

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

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

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

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

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