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>2014-10-17T14:50:53Z</updated>
  8.    
  9.    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 4.38</generator>
  10.  
  11. <entry>
  12.    <title>ACT - Voyager - logbook 2014-10-01</title>
  13.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/10/act---voyager---logbook-2014-1.html" />
  14.    <id>tag:news.perlfoundation.org,2014://18.3503</id>
  15.  
  16.    <published>2014-10-17T14:40:21Z</published>
  17.    <updated>2014-10-17T14:50:53Z</updated>
  18.  
  19.    <summary><![CDATA[As time moves on the Voyage gradually moves forward. In the proposal I sent, I already knew that I would not be able to dedicate any time until the last week of September. So, what did happen until now: The Apache &amp; mod_perl nightmare ACTually, let me take you back december 2013. After I visited the London Perl Workshop, I went to the French hackathon Patch -p1 in Paris to see if I could do some useful things on ACT....]]></summary>
  20.    <author>
  21.        <name>Elizabeth Mattijsen</name>
  22.        
  23.    </author>
  24.    
  25.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  26.    
  27.    <category term="act" label="act" scheme="http://www.sixapart.com/ns/types#tag" />
  28.    
  29.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  30.        <![CDATA[<p><i>As time moves on the Voyage gradually moves forward.</i></p>
  31.  
  32. <p>In the proposal I sent, I already knew that I would not be able to dedicate any time until the last week of September. So, what did happen until now:</p>
  33.  
  34. <h1>The Apache &amp; mod_perl nightmare</h1>
  35.  
  36. <p><span class="caps">ACT</span>ually, let me take you back december 2013. After I visited the London Perl Workshop, I went to the French hackathon Patch -p1 in Paris to see if I could do some useful things on <span class="caps">ACT.</span> I wanted a good looking web-site for the Dutch Perl Workshop! The only thing I had at time was a jurassic Apple PowerBook G3 500Mhz <span class="caps">FW.</span> I still love that baby. During that specific hackathon my slow machine was not performing well and I had to go back home without having much achieved, technically.</p>
  37.  
  38. <p>Back home I bought a book that most would start screaming about "Practical mod_perl". In there is a recipe to get it all up and running... If only. As family we went to a resort in Belgium between Christmas and New-Year and I tried to be a nice family man. Most of the time I was trying to set-up my machine so it would run Apache 1.x with mod_perl. And it still didn't work out.</p>
  39.  
  40. <p>The best solution was actually the most simple one, a dead clean install of the original MacOS 10.4! Which includes a running Apache 1.x and mod_perl pre installed... Had I only known before.</p>
  41.  
  42. <p>Why this long story? For it is one of the many stories you will hear from anybody that wanted to install Act on their own system. It is a nightmare. Luckily there were some people that had succeeded before:</p>
  43.  
  44. <ul>
  45. <li>Detlev sent his notes on how tried to set up his development virtual machine for the <span class="caps">NLPW </span>and I never got the chance to work those out for one simple reason: I did not had a laptop robust enough to run virtualisation. But that has changed.</li>
  46. <li>Alex Mundata had worked out a way to install a working setup inside a Vagrant box. I looked at it and tried it - but failed a few times, as there were some unclear things in his setup</li>
  47. </ul>
  48.  
  49. <h1>The green pastures of 'Act-out-of-the-box'</h1>
  50.  
  51. So, I took all that info and started to work on a super easy way for any Act developer to start hacking:<br />
  52. <ol>
  53. <li>Download Vagrant</li>
  54. <li>Download the <i>'Act-out-of-the-box'</i> vagrant image</li>
  55. <li>vagrant up</li>
  56. <li>Choose your install type</li>
  57. <li>Welcome to Act</li>
  58. </ol>
  59. So, what is happening there, what install types...?
  60.  
  61. <p>As it seems there are different ways people like to work on Act. Some of them just want a test machine so they can play locally with the design and interaction. For them there will be a pre-setup environment that will give them only what they need. Others want to do some stuff in the core of Act, those will get another environment.</p>
  62.  
  63. <p>During that last install step, it does one other important thing, it does clone a repository from GitHub: the <b>stable</b> production version, the <span class="caps">HOT </span><b>Act Voyager</b> version or a <b><span class="caps">PSGI</span></b> version.</p>
  64.  
  65. <p>The <a href="https://github.com/THEMA-MEDIA/Act-out-of-the-box">'Act-out-of-the-box'</a> comes pre-installed with:</p>
  66.  
  67. <ul>
  68. <li>Apache 1.2.42</li>
  69. <li>mod_perl 1.31</li>
  70. <li>postfix</li>
  71. <li>PostgreSQL</li>
  72. <li>sample databases</li>
  73. <li>Act dependencies</li>
  74. </ul>
  75. This is going to save all Act developers, including myself a lot of work and time. I think this is a huge step forward to make Act hackable for anybody.
  76.  
  77. <p>I'm about to finish the last step in the installation procedure, so that will work nicely as it is supposed to work, not like some idiot me has smashed it together.</p>
  78.  
  79. <p>Then... it gets time for me to get the databases a bit more fancy and give Act a nice shiny <span class="caps">DBI</span>x::Class interface.</p>
  80.  
  81. <h1>Patch -p2 hackathon in Lyon</h1>
  82.  
  83. <p>I'm looking forward to the end of november, when Patch -p2 will be held in Lyon. I hope a lot of fundamental things have changed before then so we can all work on some fresh hackable environment</p>
  84.  
  85. <p><i>Your Captain</i> Theo van Hoesel</p>]]>
  86.        
  87.    </content>
  88. </entry>
  89.  
  90. <entry>
  91.    <title>ACT - Voyager - logbook 2014-09-01</title>
  92.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/10/act---voyager---logbook-2014-0.html" />
  93.    <id>tag:news.perlfoundation.org,2014://18.3501</id>
  94.  
  95.    <published>2014-10-17T14:08:43Z</published>
  96.    <updated>2014-10-17T14:18:35Z</updated>
  97.  
  98.    <summary>Grant Manager&apos;s note: please excuse the delay in posting these progress reports. Future progress reports will be more in time. This is the progress report about August 2014. As in the original proposal for the Grant, it was stated I would not start before the second half of september because of a project that is very tight on the deadline. However that does not mean that nothing happens. On the contrary, not without reason at the last evening of YAPC::EU::2014...</summary>
  99.    <author>
  100.        <name>Elizabeth Mattijsen</name>
  101.        
  102.    </author>
  103.    
  104.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  105.    
  106.    <category term="act" label="ACT" scheme="http://www.sixapart.com/ns/types#tag" />
  107.    
  108.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  109.        <![CDATA[<p><i>Grant Manager's note: please excuse the delay in posting these progress reports.  Future progress reports will be more in time.  This is the progress report about August 2014.</i></p>
  110.  
  111. <p>As in the original proposal for the Grant, it was stated I would not start before the second half of september because of a project that is very tight on the deadline.</p>
  112.  
  113. <p>However that does not mean that nothing happens. On the contrary, not without reason at the last evening of <span class="caps">YAPC</span>::EU::2014 I briefly showed the official Startrek Voyager opening video: this project already has gotten into 'Warp Speed'.</p>
  114.  
  115. <p>I held a brief introduction LightningTalk at the first day, called 'the Long Journey' see <a href="http://www.slideshare.net/theovanhoesel/the-long-journey-part-2">my SlideShare upload</a></p>
  116.  
  117. <p>The next day there was a BoF with a dozen people showing up that had different kinds off interests:</p>
  118.  
  119. <ul>
  120. <li>people that want a complete rewrite</li>
  121. <li>people that want a quick fix and new features on top of the current <span class="caps">ACT</span></li>
  122. <li>people that want to change the internals first</li>
  123. </ul>
  124. Doing a total rewrite, as usually, was being advised against, but has some challenging aspects. Making it possible to start hacking on the current version of <span class="caps">ACT </span>has the advantage that things can start immediately... although there has been proposed to make the current Apache1/ModPerl version of <span class="caps">ACT </span>run inside a <span class="caps">PSGI </span>environment. Haarg has previously made a <span class="caps">PSGI </span>port (3 years ago), which has not yet been merged back, due to deployment changes required for current live setup. SawyerX is working on a revised approach which may not need this. Once one of these solutions is merged in, it will be possible to hack on the current version at two different fronts: add features and hack the core in the meantime.
  125.  
  126. <p>We are looking forward to see what Sawyer is doing for some kind of wizardry.</p>
  127.  
  128. <p>Thank you Todd Rinaldo for setting up a new <span class="caps">ACT </span>repository at GitHub and creating the teams and send out the invitations.</p>
  129.  
  130. <p>During Lunch with BooK I was very happy to hear how he sees how this <span class="caps">ACT</span> Voyager project will work in conjunction with the current <span class="caps">ACT </span>repository at GitHub and the servers.</p>
  131.  
  132. <p>BooK suggested that whenever the Voyager team does a pull request on the original BooK/ACT repository, it will be checked out at the <span class="caps">ACT </span>test server to see how the changes will effect in real life situations. From there, it will go to the real <span class="caps">ACT </span>server. This cycle should be done as quick and frequent as possible after the pull-request. This way, the effort people take to work on the new repository will show up in production soon and it will not slow down the project.</p>
  133.  
  134. <p>One thing that BooK suggested will certainly help in moving forward more quickly: some discipline for all those that want to hack on the old code! Once the <span class="caps">DBI</span>x::Class schema is functional and working, there is still code in the <span class="caps">ACT</span>::Core that needs to be updated. All developers that want to add or edit features in the old version that rely on modules in the core, should first fix all the methods in core before adding on top off it... and test, test test. Once that stage has passed and committed (and merged) hacking on the features itself can start. This way, we make developers more responsible and involved in the whole project.</p>
  135.  
  136. <p>Later this year, BooK will organise a hackathon in Lyon. Salve J. Nilsen has already scheduled the hackathon in Oslo in May next year.</p>
  137.  
  138. <p>I am very grateful for all the support I get from people more intelligent than I am and specialised in important technologies that <span class="caps">ACT </span>will be build on.</p>
  139.  
  140. <p>Theo van Hoesel</p>]]>
  141.        
  142.    </content>
  143. </entry>
  144.  
  145. <entry>
  146.    <title>Grant Extension Request: Dave Mitchell</title>
  147.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/10/grant-extension-request-dave-m.html" />
  148.    <id>tag:news.perlfoundation.org,2014://18.3497</id>
  149.  
  150.    <published>2014-10-09T21:40:13Z</published>
  151.    <updated>2014-10-09T21:44:59Z</updated>
  152.  
  153.    <summary>Dave Mitchell has requested an extension of $20,000 for his Maintaining the Perl 5 Core grant. This will allow him to dedicate another 400 hours to this work. During this grant he sent weekly reports to the p5p mailing list as well as providing monthly summary reports that have been published on this blog, the most recent of which are linked below: Report for Month 11 Report for Month 10 Report for Month 9 Before we make a decision on...</summary>
  154.    <author>
  155.        <name>Karen Pauley</name>
  156.        <uri>http://martian.org/karen</uri>
  157.    </author>
  158.    
  159.    
  160.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  161.        <![CDATA[<p>Dave Mitchell has requested an extension of $20,000 for his <a href="http://news.perlfoundation.org/2013/09/grant-application-maintaining-1.html">Maintaining the Perl 5 Core grant</a>.  This will allow him to dedicate another 400 hours to this work.  During this grant he sent weekly reports to the p5p mailing list as well as providing monthly summary reports that have been published on this blog, the most recent of which are linked below:</p>
  162.  
  163. <p><a href="http://news.perlfoundation.org/2014/10/maintaining-the-perl-5-core-re-9.html">Report for Month 11</a><br />
  164. <a href="http://news.perlfoundation.org/2014/08/maintaining-the-perl-5-core-re-8.html">Report for Month 10</a><br />
  165. <a href="http://news.perlfoundation.org/2014/07/maintaining-the-perl-5-core-re-7.html">Report for Month 9</a></p>
  166.  
  167. <p>Before we make a decision on this extension we would like to have a period of community consultation that will last for one week. Please leave feedback in the comments or if you prefer send email with your comments to karen at perlfoundation.org.</p>
  168.  
  169. <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>]]>
  170.        
  171.    </content>
  172. </entry>
  173.  
  174. <entry>
  175.    <title>Tony Cook&apos;s Grant Extended</title>
  176.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/10/tony-cooks-grant-extended.html" />
  177.    <id>tag:news.perlfoundation.org,2014://18.3495</id>
  178.  
  179.    <published>2014-10-07T17:04:29Z</published>
  180.    <updated>2014-10-08T17:21:04Z</updated>
  181.  
  182.    <summary>I am pleased to announce that Tony Cook&apos;s Maintaining Perl 5 grant has been extended by another 400 hours. I would like to thank everyone who responded to the call for comments and who provided feedback on this grant extension. I would also like to thank all those who continue to provide financial support to the Perl 5 Core Maintenance Fund....</summary>
  183.    <author>
  184.        <name>Karen Pauley</name>
  185.        <uri>http://martian.org/karen</uri>
  186.    </author>
  187.    
  188.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  189.    
  190.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  191.    
  192.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  193.        <![CDATA[<p>I am pleased to announce that Tony Cook's <a href="http://news.perlfoundation.org/2014/03/grant-extension-request-from-t.html">Maintaining Perl 5</a> grant has been extended by another 400 hours.  </p>
  194.  
  195. <p>I would like to thank everyone who responded to the call for comments and who provided feedback on this grant extension. I would also like to thank all those who continue to provide financial support to the <a href="http://www.perlfoundation.org/perl_5_core_maintenance_fund">Perl 5 Core Maintenance Fund</a>.  </p>]]>
  196.        
  197.    </content>
  198. </entry>
  199.  
  200. <entry>
  201.    <title>Maintaining the Perl 5 Core: Report for Month 11</title>
  202.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/10/maintaining-the-perl-5-core-re-9.html" />
  203.    <id>tag:news.perlfoundation.org,2014://18.3493</id>
  204.  
  205.    <published>2014-10-05T21:23:14Z</published>
  206.    <updated>2014-10-05T21:28:15Z</updated>
  207.  
  208.    <summary>Dave Mitchell writes: The main things I worked on this month were: making the op_private OP flags and data be auto-generated from a single consistent source. Its actually complete now, although wasn&apos;t at the end of last month, which is the period this report covers. some more work on my OP_MULTIDEREF optimisation. The basic optimisation works, but it still needs work on being handled by B::* and by the use of uninitialised value&quot; warning code, and tests need adding. reviewing,...</summary>
  209.    <author>
  210.        <name>Karen Pauley</name>
  211.        <uri>http://martian.org/karen</uri>
  212.    </author>
  213.    
  214.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  215.    
  216.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  217.    
  218.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  219.        <![CDATA[<p><em>Dave Mitchell writes:</em></p>
  220.  
  221. <p>The main things I worked on this month were:</p>
  222.  
  223.  
  224. <ul>
  225. <li>making the op_private OP flags and data be auto-generated from a single consistent source. Its actually complete now, although wasn't at the end of last month, which is the period this report covers.</li>
  226. </ul>
  227.  
  228.  
  229.  
  230.  
  231. <ul>
  232. <li>some more work on my OP_MULTIDEREF optimisation. The basic optimisation works, but it still needs work on being handled by B::* and by the use of uninitialised value" warning code, and tests need adding.</li>
  233. </ul>
  234.  
  235.  
  236.  
  237.  
  238. <ul>
  239. <li>reviewing, discussing and applying Syber's method call optimisation work</li>
  240. </ul>
  241.  
  242.  
  243.  
  244. <p><b>Summary</b> </p>
  245.  
  246. <blockquote><p>0:33 [perl #122526] Potential vulnerabilities in <span class="caps">PERL</span> 5.21.2<br />
  247. 13:53 add OP_MULTIDEREF<br />
  248. 1:42 fix op/stat.t smoke issue<br />
  249. 34:26 make op_private flag definitions be auto-generated<br />
  250. 12:42 process p5p mailbox<br />
  251. 9:35 review "Speeding up perl's <span class="caps">OOP</span>" patch</p></blockquote>
  252.  
  253. <p><b>72:51 Total (HH::MM)</b></p>
  254.  
  255. <p>As of 2014/08/31: since the beginning of the grant:</p>
  256.  
  257. <blockquote><p>46.0 weeks<br />
  258. 634.1 total hours<br />
  259. 13.8 average hours per week</p></blockquote>
  260.  
  261. <p>There are 166 hours left on the grant</p>]]>
  262.        
  263.    </content>
  264. </entry>
  265.  
  266. <entry>
  267.    <title>Grant Reports for September</title>
  268.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/10/grant-reports-for-september.html" />
  269.    <id>tag:news.perlfoundation.org,2014://18.3491</id>
  270.  
  271.    <published>2014-10-04T03:00:00Z</published>
  272.    <updated>2014-10-04T03:42:49Z</updated>
  273.  
  274.    <summary>Grant recipients are required to publish a grant report every month. Here are what we got in September: Modern Object Oriented Programming in Perl Perl::Lint TPF also got a grant report on &quot;Start ACT - Voyager&quot; (proposal) so I expect it to be published shortly. If you have any comments/suggestions for each grant, please get in touch with them. We appreciate their hard work and we look forward to seeing the next update....</summary>
  275.    <author>
  276.        <name>Makoto Nozaki</name>
  277.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  278.    </author>
  279.    
  280.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  281.    
  282.    
  283.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  284.        <![CDATA[<p>Grant recipients are required to publish a grant report every month.  Here are what we got in September:</p>
  285.  
  286. <ul>
  287. <li><a href="http://news.perlfoundation.org/2014/09/grant-report-modern-oo-program.html">Modern Object Oriented Programming in Perl</a></li>
  288. <li><a href="http://news.perlfoundation.org/2014/09/more-perllint-progress-2.html">Perl::Lint</a></li>
  289. </ul>
  290.  
  291. <p>TPF also got a grant report on "Start ACT - Voyager" (<a href="http://news.perlfoundation.org/2014/07/grant-proposal-start-act---voy.html">proposal</a>) so I expect it to be published shortly.</p>
  292.  
  293. <p>If you have any comments/suggestions for each grant, please get in touch with them.</p>
  294.  
  295. <p>We appreciate their hard work and we look forward to seeing the next update.</p>
  296. ]]>
  297.        
  298.  
  299.    </content>
  300. </entry>
  301.  
  302. <entry>
  303.    <title>Booking.com Donates $60,000 to Perl 5 Development</title>
  304.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/10/bookingcom-donates-60000-to-pe.html" />
  305.    <id>tag:news.perlfoundation.org,2014://18.3489</id>
  306.  
  307.    <published>2014-10-02T16:26:21Z</published>
  308.    <updated>2014-10-02T16:34:57Z</updated>
  309.  
  310.    <summary>Booking.com donates $60,000 dollars to The Perl Foundation for continued support of the Perl 5 Core Maintenance Fund.</summary>
  311.    <author>
  312.        <name>TPF Conferences Staff</name>
  313.        
  314.    </author>
  315.    
  316.        <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category" />
  317.    
  318.        <category term="Perl Foundation" scheme="http://www.sixapart.com/ns/types#category" />
  319.    
  320.    
  321.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  322.        <![CDATA[<p>It is our pleasure to announce that Booking.com has donated the sum of $60,000 to the Perl Foundation to aid with further development of the Perl 5 programming language. This donation is a further contribution to the Core Maintenance Fund (P5CMF) that Booking.com has consistently supported over several years. This donation is a another step in the support that Booking.com gives to <span class="caps">TPF </span>and the broader Perl community.</p>
  323.  
  324. <p>Darren Huston, Chief Executive Officer of Booking.com, said "Perl is central to the success of Booking.com." By continuing with grants, supporting Perl community events and hackathons: </p>
  325.  
  326. <p>"we keep up our tradition of giving back to the community. As one of the world's largest employers of Perl developers, an investment for us into a healthy and dynamic Perl community is an investment in the future of our company and innovative web development in general."</p>
  327.  
  328. <p>Booking.com has also recently entered into an arrangement to continuously fund some of David Mitchell's work on the Perl 5 Core. This has a specific focus towards performance improvements and evolution of the language in line with the vision of the project leader. This future-focus secures Perl's relevance as an enterprise grade language for large web applications.</p>
  329.  
  330. <p>"It is always a tremendous pleasure to work with Booking.com," said Karen Pauley, President of the Perl Foundation. </p>
  331.  
  332. <p>"With Booking.com it goes far deeper than a desire to promote our language or support our community, it is a genuine feeling that they wish to belong which is why they involve themselves so much. They are a part of the Perl family."</p>
  333.  
  334. <p>Since the foundation of Booking.com, in 1996, the company has built its IT infrastructure on myriad of open source projects and products. These include Linux, MySQL, Nginx, Hadoop, and Redis to complement a strong association with the Perl programming language. Because of this, Booking.com is a keen supporter of the Perl and open source communities. As Steffen Mueller, Senior Manager for Technology and Infrastructure at Booking.com, would say:</p>
  335.  
  336. <p>"Developers at Booking.com are encouraged to release code to Open Source projects. Booking.com has a culture of contributing to the Open Source community. Our staff are regular attendees and speakers at Perl events, but also find themselves at non-Perl conferences. We are happy to hire talented developers from a variety of backgrounds and varying skill sets and re-train them in the Booking.com culture and Perl language."</p>
  337.  
  338. <p><img alt="booking_logo.png" src="http://news.perlfoundation.org/booking_logo.png" width="500" height="85" class="mt-image-center" style="text-align: center; display: block; margin: 0 auto 20px;" /></p>
  339.  
  340. <p><u><b>About Booking.com</b></u><br />
  341. Booking.com <span class="caps">B.V., </span>part of the Priceline Group (Nasdaq: <span class="caps">PCLN</span>), owns and operates Booking.com™, the world leader in booking accommodation online. Each day, over 700,000 room nights are reserved on Booking.com. The Booking.com website and apps attract visitors from both the leisure and business sectors worldwide.</p>
  342.  
  343. <p>Established in 1996, Booking.com <span class="caps">B.V. </span>guarantees the best prices for every type of property, from small, family-run bed and breakfasts to executive apartments and five-star luxury suites. Self-catered properties are also specifically a focus of Villas.com, a sister site recently launched by Booking.com. Truly international, Booking.com is available in more than 40 languages, and offers over 537,980 properties in 207 countries.</p>]]>
  344.        
  345.    </content>
  346. </entry>
  347.  
  348. <entry>
  349.    <title>September 2014 Grant Votes</title>
  350.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/09/september-2014-grant-votes.html" />
  351.    <id>tag:news.perlfoundation.org,2014://18.3487</id>
  352.  
  353.    <published>2014-09-30T23:30:00Z</published>
  354.    <updated>2014-10-01T01:40:28Z</updated>
  355.  
  356.    <summary>The Grants Committee has concluded the voting of the September round. Proposals in this round Nile - Visual Web App Framework Separating Code From Design Multi Lingual And Multi Theme, Ahmed Amin Elsheshtawy, USD 10,000 IO::All Redux, Ingy döt Net and David Oswald, USD 3,000 Inline::C(PP) Module Support, Ingy döt Net and David Oswald, USD 2,000 Pegex Grammar for YAML, Ingy döt Net and David Oswald, USD 3,500 Swim Pod, Ingy döt Net and David Oswald, USD 3,000 Voting Results...</summary>
  357.    <author>
  358.        <name>Makoto Nozaki</name>
  359.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  360.    </author>
  361.    
  362.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  363.    
  364.    
  365.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  366.        <![CDATA[<p>The Grants Committee has concluded the voting of the September round.</p>
  367.  
  368. <h3>Proposals in this round</h3>
  369.  
  370. <ul>
  371. <li><a href="http://news.perlfoundation.org/2014/09/grant-proposal-nile---visual-w.html">Nile - Visual Web App Framework Separating Code From Design Multi Lingual And Multi Theme</a>, Ahmed Amin Elsheshtawy, USD 10,000</li>
  372. <li><a href="http://news.perlfoundation.org/2014/09/grant-proposal-ioall-redux.html">IO::All Redux</a>, Ingy döt Net and David Oswald, USD 3,000</li>
  373. <li><a href="http://news.perlfoundation.org/2014/09/grant-proposal-inlinecpp-modul.html">Inline::C(PP) Module Support</a>, Ingy döt Net and David Oswald, USD 2,000</li>
  374. <li><a href="http://news.perlfoundation.org/2014/09/grant-proposal-pegex-grammar-f.html">Pegex Grammar for YAML</a>, Ingy döt Net and David Oswald, USD 3,500</li>
  375. <li><a href="http://news.perlfoundation.org/2014/09/grant-proposal-swim-to-pod.html">Swim Pod</a>, Ingy döt Net and David Oswald, USD 3,000</li>
  376. </ul>
  377.  
  378. <h3>Voting Results</h3>
  379.  
  380. <p><p><table border=1 style="border:1px solid black;border-collapse:collapse;"><tr><th>Title</th><th>Yes</th><th>No</th><th>Score</th>
  381. <tr><td>Nile<td style="text-align:right">0<td style="text-align:right">7<td><br>
  382. <tr><td>IO::All Redux<td style="text-align:right">4<td style="text-align:right">3<td>9 = 5+2+1+1
  383. <tr><td>Inline::C(PP) ...<td style="text-align:right">8<td style="text-align:right">0<td>29 = 5+4+4+4+3+3+3+3
  384. <tr><td>Pegex Grammar ...<td style="text-align:right">1<td style="text-align:right">6<td><br>
  385. <tr><td>Swim Pod<td style="text-align:right">0<td style="text-align:right">9<td><br>
  386. </table></p>
  387.  
  388. <p>Definition of the score is found in 3.2 of the <a href="http://www.perlfoundation.org/rules_of_operation">rules</a>.</p>
  389. ]]>
  390.        <![CDATA[<h3>Details</h3>
  391.  
  392. <p><a href="http://news.perlfoundation.org/2014/09/grant-proposal-nile---visual-w.html">Nile - Visual Web App Framework Separating Code From Design Multi Lingual And Multi Theme</a></p>
  393.  
  394. <p>First of all, thank you for submitting this application.  It's always good to see new faces.  </p>
  395.  
  396. <p>For this grant, we are unable to find a reason to spend a large portion of the community money on this new web framework at this point.  We would like to see the author continue the development of Nile and get some more community support on it first.</p>
  397.  
  398. <p><a href="http://news.perlfoundation.org/2014/09/grant-proposal-ioall-redux.html">IO::All Redux</a></p>
  399.  
  400. <p>We approve this grant.  We will not fund this grant at this point and will re-evaluate this in the next round.  </p>
  401.  
  402. <p><a href="http://news.perlfoundation.org/2014/09/grant-proposal-inlinecpp-modul.html">Inline::C(PP) Module Support</a></p>
  403.  
  404. <p>We are pleased that the Grants Committee will approve and fund this grant.  This will be useful for the community and we already saw enough positive feedback.  It should be noted that the total score was the second highest this year after the Perl::Lint grant.</p>
  405.  
  406. <p>Mark Jensen agreed to be the grant manager.</p>
  407.  
  408. <p><a href="http://news.perlfoundation.org/2014/09/grant-proposal-pegex-grammar-f.html">Pegex Grammar for YAML</a></p>
  409.  
  410. <p>We understand YAML is used in a number of places and the grant has certain value.  However at this point we are not able to approve it.</p>
  411.  
  412. <p><a href="http://news.perlfoundation.org/2014/09/grant-proposal-swim-to-pod.html">Swim Pod</a></p>
  413.  
  414. <p>We hope we can discuss this grant after Swim gets wider adoption and community support.</p>
  415.  
  416. <h3>Next round</h3>
  417.  
  418. <p>The next round is in November.  You can <a href="http://www.perlfoundation.org/how_to_write_a_proposal">submit proposals now</a>.</p>
  419. ]]>
  420.    </content>
  421. </entry>
  422.  
  423. <entry>
  424.    <title>The Perl Foundation to increase brand, marketing, and PR</title>
  425.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/09/the-perl-foundation-to-increas.html" />
  426.    <id>tag:news.perlfoundation.org,2014://18.3485</id>
  427.  
  428.    <published>2014-09-29T17:13:19Z</published>
  429.    <updated>2014-09-29T17:19:19Z</updated>
  430.  
  431.    <summary>Walnut, CA - With the planning stages of YAPC::NA 2015 (Yet Another Perl Conference) underway, The Perl Foundation has made an increased commitment to marketing and public relations: by teaming up with Pittsburgh based firm ALTRIS Incorporated. ALTRIS Incorporated, a full-service printing, marketing, and web design firm, specializes in non-profit marketing, fundraising, branding, and event management. &quot;We originally brought in the team at ALTRIS to help with our 2012 and 2013 end-of-the-year reports and sponsorship prospectus,&quot; said Dan Wright, Perl...</summary>
  432.    <author>
  433.        <name>TPF Conferences Staff</name>
  434.        
  435.    </author>
  436.    
  437.        <category term="Marketing" scheme="http://www.sixapart.com/ns/types#category" />
  438.    
  439.        <category term="Perl Foundation" scheme="http://www.sixapart.com/ns/types#category" />
  440.    
  441.    
  442.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  443.        <![CDATA[<p>Walnut, CA - With the planning stages of <span class="caps">YAPC</span>::NA 2015 (Yet Another Perl Conference) underway, The Perl Foundation has made an increased commitment to marketing and public relations: by teaming up with Pittsburgh based firm <span class="caps">ALTRIS</span> Incorporated. </p>
  444.  
  445. <p><span class="caps">ALTRIS</span> Incorporated, a full-service printing, marketing, and web design firm, specializes in non-profit marketing, fundraising, branding, and event management. "We originally brought in the team at <span class="caps">ALTRIS </span>to help with our 2012 and 2013 end-of-the-year reports and sponsorship prospectus," said Dan Wright, Perl Foundation Treasurer, "having a professional marketing and PR team on board is the next step to growing the Foundation's brand, and events."</p>
  446.  
  447. <p>The Perl Foundation supports four yearly events, including the DC-Baltimore and Pittsburgh Perl Workshops, Perl Oasis, and <span class="caps">YAPC</span>::NA. <span class="caps">ALTRIS</span> Incorporated will be supporting local organizers and the Foundation's marketing and conferences committees promote their events internationally. The relationship will also include broadcasting news and updates regarding advancements in Perl, sponsorship opportunities, grants, and training materials. </p>
  448.  
  449. <p>Visit The Perl Foundation online at www.perlfoundation.org and on Facebook at www.fb.com/tpf.perl. Information regarding <span class="caps">YAPC</span>::NA 2015 will be available at www.yapcna.org. </p>]]>
  450.        
  451.    </content>
  452. </entry>
  453.  
  454. <entry>
  455.    <title>Grant Report: Modern OO Programming in Perl (Book) - Sept 2014</title>
  456.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/09/grant-report-modern-oo-program.html" />
  457.    <id>tag:news.perlfoundation.org,2014://18.3483</id>
  458.  
  459.    <published>2014-09-26T15:40:45Z</published>
  460.    <updated>2014-09-26T15:55:02Z</updated>
  461.  
  462.    <summary>Toby Inkster reports on his book-writing progress in his latest blog post. Highlights:The material is open and mirrored at GitHub and Bitbucket. He welcomes your comments and suggestions.Work on the namespace chapter is beginning.I and I&apos;m sure many others are looking forward to having this great resource.MAJ...</summary>
  463.    <author>
  464.        <name>Mark A Jensen</name>
  465.        
  466.    </author>
  467.    
  468.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  469.    
  470.    <category term="grant2014moopbook" label="grant-2014-moopbook" scheme="http://www.sixapart.com/ns/types#tag" />
  471.    
  472.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  473.        <![CDATA[<p>Toby Inkster reports on his book-writing progress in his latest <a href="http://blogs.perl.org/users/toby_inkster/2014/09/book-report---september-2014.html">blog post</a>. Highlights:</p><ul><li>The material is open and mirrored at <a href="https://github.com/tobyink/docs-modern-oop">GitHub</a> and <a href="https://bitbucket.org/tobyink/docs-modern-oop">Bitbucket</a>. He welcomes your comments and suggestions.</li><li>Work on the namespace chapter is beginning.</li></ul><p>I and I'm sure many others are looking forward to having this great resource.</p><p>MAJ<br /></p>]]>
  474.        
  475.    </content>
  476. </entry>
  477.  
  478. <entry>
  479.    <title>Outreach Program for Women - Winter 2014 / 2015</title>
  480.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/09/outreach-program-for-women---w.html" />
  481.    <id>tag:news.perlfoundation.org,2014://18.3481</id>
  482.  
  483.    <published>2014-09-25T07:09:14Z</published>
  484.    <updated>2014-09-25T07:42:56Z</updated>
  485.  
  486.    <summary>I am delighted to announce that the Perl Foundation will once again be taking part in the GNOME Outreach Program for Women. The Outreach Program for Women (OPW) was started by the GNOME Foundation in 2006 to encourage women to participate in the GNOME project. In the first round eight interns took part working from GNOME. This program has been expanded and in the last round, that took place this summer, forty interns were accepted and seventeen Free and Open...</summary>
  487.    <author>
  488.        <name>Karen Pauley</name>
  489.        <uri>http://martian.org/karen</uri>
  490.    </author>
  491.    
  492.        <category term="OPW" scheme="http://www.sixapart.com/ns/types#category" />
  493.    
  494.    <category term="opensourcewomen" label="open source women" scheme="http://www.sixapart.com/ns/types#tag" />
  495.    
  496.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  497.        <![CDATA[<p>I am delighted to announce that the Perl Foundation will once again be taking part in the <a href="http://gnome.org/opw/"><span class="caps">GNOME</span> Outreach Program for Women</a>.  </p>
  498.  
  499. <p>The Outreach Program for Women (OPW) was started by the <span class="caps">GNOME</span> Foundation in 2006 to encourage women to participate in the <span class="caps">GNOME </span>project.  In the first round eight interns took part working from <span class="caps">GNOME. </span> This program has been expanded and in the last round, that took place this summer, forty interns were accepted and seventeen Free and Open Source organisations took part including The Perl Foundation.</p>
  500.  
  501. <p>We are offering one internship in the winter program which runs from the 9th December 2014 to the 9th March 2015.  We have mentors from Dancer and MetaCPAN signed up to provide project ideas and you can read about possible projects on our <a href="http://www.perlfoundation.org/outreach_program_for_women">information page</a>.</p>
  502.  
  503. <p>We could not take part in this program without the support of our sponsors.  In particular I would like to thank Wendy and Liz for donating $1000 to the program. </p>]]>
  504.        
  505.    </content>
  506. </entry>
  507.  
  508. <entry>
  509.    <title>September 2014 Grant Proposals</title>
  510.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/09/september-2014-grant-proposals.html" />
  511.    <id>tag:news.perlfoundation.org,2014://18.3479</id>
  512.  
  513.    <published>2014-09-15T00:00:10Z</published>
  514.    <updated>2014-09-15T01:17:05Z</updated>
  515.  
  516.    <summary>The Grants Committee has received five grant proposals for the September round. Before the Committee members vote, we would like to solicit feedback from the Perl community on the proposal. Review the proposals below and please comment there. The Committee members will start the voting process on September 26th and the conclusion will be announced by September 30th. Nile - Visual Web App Framework Separating Code From Design Multi Lingual And Multi Theme, Ahmed Amin Elsheshtawy, USD 10,000 IO::All Redux,...</summary>
  517.    <author>
  518.        <name>Makoto Nozaki</name>
  519.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  520.    </author>
  521.    
  522.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  523.    
  524.    
  525.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  526.        <![CDATA[<p>The Grants Committee has received five grant proposals for the September round.  Before the Committee members vote, we would like to solicit feedback from the Perl community on the proposal.</p>
  527.  
  528. <p>Review the proposals below and please comment there.  The Committee members will start the voting process on September 26th and the conclusion will be announced by September 30th.</p>
  529.  
  530. <ul>
  531. <li><a href="http://news.perlfoundation.org/2014/09/grant-proposal-nile---visual-w.html">Nile - Visual Web App Framework Separating Code From Design Multi Lingual And Multi Theme</a>, Ahmed Amin Elsheshtawy, USD 10,000</li>
  532. <li><a href="http://news.perlfoundation.org/2014/09/grant-proposal-ioall-redux.html">IO::All Redux</a>, Ingy döt Net and David Oswald, USD 3,000</li>
  533. <li><a href="http://news.perlfoundation.org/2014/09/grant-proposal-inlinecpp-modul.html">Inline::C(PP) Module Support</a>, Ingy döt Net and David Oswald, USD 2,000</li>
  534. <li><a href="http://news.perlfoundation.org/2014/09/grant-proposal-pegex-grammar-f.html">Pegex Grammar for YAML</a>, Ingy döt Net and David Oswald, USD 3,500</li>
  535. <li><a href="http://news.perlfoundation.org/2014/09/grant-proposal-swim-to-pod.html">Swim Pod</a>, Ingy döt Net and David Oswald, USD 3,000</li>
  536. </ul>
  537.  
  538. <p>For the proposals from Ingy and David, we also got the following statement from them:</p>
  539.  
  540. <blockquote>
  541.  <p>Ingy döt Net and David Oswald have a number of ambitious Perl related projects that we would like to collaborate on. We think that having a pair of programmers fulfilling grants will lead to a better experience for all.</p>
  542.  
  543. <p>We have thought up about a dozen potential ideas, and we think 4 of them are ready to propose now. The others will come to fruition over time.</p>
  544.  
  545. <p>(snip)</p>
  546.  
  547. <p>Our ideal situation would be to continually propose 3-5 grants every 2 months, but only have 1 of them granted at a time. This is of course, up to you and based on your perception of the merit of our proposals, but hopefully we can get better and better at providing projects that really move Perl forward.</p>
  548. </blockquote>
  549. ]]>
  550.        
  551.  
  552.    </content>
  553. </entry>
  554.  
  555. <entry>
  556.    <title>Grant Proposal: Swim to Pod</title>
  557.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/09/grant-proposal-swim-to-pod.html" />
  558.    <id>tag:news.perlfoundation.org,2014://18.3477</id>
  559.  
  560.    <published>2014-09-15T00:00:04Z</published>
  561.    <updated>2014-09-15T01:14:32Z</updated>
  562.  
  563.    <summary>We have received the following grant application &quot;Swim to Pod&quot;. Please leave feedback in the comments field by September 25th, 2014. Swim to Pod Name: Ingy döt Net David Oswald Amount Requested USD $3000 Synopsis Provide Swim tools that allow Perl programmers to produce elaborate Pod documention, painlessly. Provide all the functionality of Pod in a syntax better than Markdown. Provide 5 plugins for extending Swim in ways useful to Perl people. Benefits to the Perl Community Pod excels in...</summary>
  564.    <author>
  565.        <name>Makoto Nozaki</name>
  566.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  567.    </author>
  568.    
  569.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  570.    
  571.    
  572.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  573.        <![CDATA[<p><em>We have received the following grant application "Swim to Pod".  Please leave feedback in the comments field by September 25th, 2014.</em></p>
  574.  
  575. <h1>Swim to Pod</h1>
  576.  
  577. <ul>
  578. <li>Name:
  579. <ul>
  580. <li>Ingy döt Net</li>
  581. <li>David Oswald</li>
  582. </ul></li>
  583. <li><p>Amount Requested</p>
  584.  
  585. <p>USD $3000</p></li>
  586. </ul>
  587.  
  588. <h2>Synopsis</h2>
  589.  
  590. <p>Provide Swim tools that allow Perl programmers to produce elaborate Pod
  591. documention, painlessly.</p>
  592.  
  593. <p>Provide all the functionality of Pod in a syntax better than Markdown.</p>
  594.  
  595. <p>Provide 5 plugins for extending Swim in ways useful to Perl people.</p>
  596.  
  597. <h2>Benefits to the Perl Community</h2>
  598.  
  599. <p>Pod excels in providing a great <strong>model</strong> for documentation. That means it
  600. supports all (most of) the semantic concepts needed to write great docs. Where
  601. Pod falls down is on syntax. The syntax is so verbose that common idioms (like
  602. creating lists of lists) are often avoided because they are to hard to write.</p>
  603.  
  604. <p>Many Perl people use Markdown which offers simpler syntax, but lacks many of
  605. the common semantic idioms in Pod. For instance, Markdown has no ability to do
  606. 'Data Definition' lists that are so common in CPAN docs (<code>dl/dt/dd</code> HTML
  607. tags). Markdown is also weak in nesting semantic blocks.</p>
  608.  
  609. <p>This summer Ingy created Swim, after thinking about it and discussing it for 8
  610. years. He has converted all the documentation in over 80 of his CPAN (and
  611. other language) distributions. The result is incredibly easy to write and
  612. maintain doc, all published to Pod for CPAN and GitHub rendering.</p>
  613.  
  614. <h2>Deliverables</h2>
  615.  
  616. <ol>
  617. <li>Tested support for full Pod semantics in Swim</li>
  618. <li>Tools to convert Swim to Pod
  619. <ul>
  620. <li>From <code>.swim</code> files</li>
  621. <li>From <code>.pm</code> files embedded</li>
  622. </ul></li>
  623. <li>Provide 5 new Swim plugin modules
  624. <ul>
  625. <li>Useful Perl/doc things</li>
  626. <li>Examples to write more</li>
  627. </ul></li>
  628. <li>Module automation plugins for turning Swim to Pod
  629. <ul>
  630. <li>Dist::Zilla</li>
  631. <li>Module::Install</li>
  632. </ul></li>
  633. <li>Pod-to-Swim conversion tool</li>
  634. </ol>
  635.  
  636. <h2>Project Details</h2>
  637.  
  638. <p>Here are the things that Swim currently does:</p>
  639.  
  640. <ul>
  641. <li>Supports all basic markup semantics</li>
  642. <li>Converts to Pod, HTML, Markdown, nroff (manpages) Text, DVI, PDF and more</li>
  643. <li>Extensible by plugins A Travis badge plugin is currently on CPAN</li>
  644. <li>Swim is Pegex based
  645. <ul>
  646. <li>Defined by a readable (human friendly) grammar</li>
  647. <li>Will have implementations in many languages (including JavaScript)</li>
  648. </ul></li>
  649. </ul>
  650.  
  651. <h2>Inch-stones</h2>
  652.  
  653. <ol>
  654. <li>Write tests for all the semantic capabilities of Pod.</li>
  655. <li>Make basic <code>swim --to=pod</code> pass those tests.</li>
  656. <li>Write a Pod parsing grammar for Pod-to-Swim tool.</li>
  657. <li>Swim plugin module candidates:
  658. <ul>
  659. <li>Unicode escapes <code>&lt;U+2603&gt;</code> <code>&lt;U SNOWMAN&gt;</code></li>
  660. <li>HTML table support</li>
  661. <li>Video embedding</li>
  662. <li>Side-by-side comarison widget</li>
  663. <li>Syntax highlighting code blocks</li>
  664. </ul></li>
  665. <li>Dist::Zilla plugin that transforms:
  666. <ul>
  667. <li>from: <code>doc/My/Module.swim</code></li>
  668. <li>or from: <code>lib/My/Module.pm</code></li>
  669. <li>to: <code>lib/My/Module.pod</code></li>
  670. </ul></li>
  671. </ol>
  672.  
  673. <h2>Project Schedule</h2>
  674.  
  675. <p>This project will take 2 months and can be started immediately upon
  676. acceptance.</p>
  677.  
  678. <h2>Completeness Criteria</h2>
  679.  
  680. <p>Above modules released to CPAN with all functionality and tests in place.
  681. Passing all tests.</p>
  682.  
  683. <h2>Bio</h2>
  684.  
  685. <p>Ingy döt Net has created markup languages in the past including the Kwiki wiki
  686. markup and the Socialtext wiki markup. He is extremely familiar with parsing,
  687. syntax and semantics issues in this space.</p>
  688.  
  689. <p>David Oswald has been a Perl user for over a decade, is an author of several
  690. CPAN modules, and maintainer of more. David also runs Salt Lake Perl Mongers.</p>
  691.  
  692. <p>Ingy and David work well together and have decided to collaborate on a number
  693. of projects that will benefit Perl and Software Development.</p>
  694.  
  695. <h2>Notes</h2>
  696.  
  697. <p>This document was written entirely in Swim and converted to Pod.</p>
  698.  
  699. <p>See these links:</p>
  700.  
  701. <ul>
  702. <li>A complex Swim/Pod pair:
  703. <ul>
  704. <li><a href="https://github.com/ingydotnet/git-hub/blob/master/doc/git-hub.swim">https://github.com/ingydotnet/git-hub/blob/master/doc/git-hub.swim</a></li>
  705. <li><a href="https://github.com/ingydotnet/git-hub/blob/master/ReadMe.pod">https://github.com/ingydotnet/git-hub/blob/master/ReadMe.pod</a></li>
  706. </ul></li>
  707. <li>Swim Grammar:
  708. <ul>
  709. <li><a href="https://github.com/ingydotnet/swim-pgx/blob/master/swim.pgx">https://github.com/ingydotnet/swim-pgx/blob/master/swim.pgx</a></li>
  710. </ul></li>
  711. <li>Swim/Pod CPAN example:
  712. <ul>
  713. <li><a href="https://github.com/ingydotnet/io-all-pm/blob/master/doc/IO/All.swim">https://github.com/ingydotnet/io-all-pm/blob/master/doc/IO/All.swim</a></li>
  714. <li><a href="https://metacpan.org/pod/IO::All">https://metacpan.org/pod/IO::All</a></li>
  715. </ul></li>
  716. </ul>
  717. ]]>
  718.        
  719.  
  720.    </content>
  721. </entry>
  722.  
  723. <entry>
  724.    <title>Grant Proposal: Pegex Grammar for YAML</title>
  725.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/09/grant-proposal-pegex-grammar-f.html" />
  726.    <id>tag:news.perlfoundation.org,2014://18.3475</id>
  727.  
  728.    <published>2014-09-15T00:00:03Z</published>
  729.    <updated>2014-09-15T01:13:14Z</updated>
  730.  
  731.    <summary>We have received the following grant application &quot;Pegex Grammar for YAML&quot;. Please leave feedback in the comments field by September 25th, 2014. Pegex Grammar for YAML Name: Ingy döt Net David Oswald Amount Requested USD $3500 Synopsis Make YAML.pm and YAML::Tiny driven by a common formal grammar. Benefits to the Perl Community Perl has four major YAML implementations: YAML YAML::Tiny YAML::XS YAML::Syck They all have major incompatabilities. In the past year the #yaml channel on irc.perl.org has gotten all the...</summary>
  732.    <author>
  733.        <name>Makoto Nozaki</name>
  734.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  735.    </author>
  736.    
  737.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  738.    
  739.    
  740.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  741.        <![CDATA[<p><em>We have received the following grant application "Pegex Grammar for YAML".  Please leave feedback in the comments field by September 25th, 2014.</em></p>
  742.  
  743. <h1>Pegex Grammar for YAML</h1>
  744.  
  745. <ul>
  746. <li>Name:
  747. <ul>
  748. <li>Ingy döt Net</li>
  749. <li>David Oswald</li>
  750. </ul></li>
  751. <li><p>Amount Requested</p>
  752.  
  753. <p>USD $3500</p></li>
  754. </ul>
  755.  
  756. <h2>Synopsis</h2>
  757.  
  758. <p>Make YAML.pm and YAML::Tiny driven by a common formal grammar.</p>
  759.  
  760. <h2>Benefits to the Perl Community</h2>
  761.  
  762. <p>Perl has four major YAML implementations:</p>
  763.  
  764. <ul>
  765. <li><a href="https://metacpan.org/pod/YAML">YAML</a></li>
  766. <li><a href="https://metacpan.org/pod/YAML::Tiny">YAML::Tiny</a></li>
  767. <li><a href="https://metacpan.org/pod/YAML::XS">YAML::XS</a></li>
  768. <li><a href="https://metacpan.org/pod/YAML::Syck">YAML::Syck</a></li>
  769. </ul>
  770.  
  771. <p>They all have major incompatabilities. In the past year the #yaml channel on
  772. irc.perl.org has gotten all the right people together to resolve this. A great
  773. next step would be to make the two pure Perl implementations <a href="https://metacpan.org/pod/YAML">YAML</a> and
  774. <a href="https://metacpan.org/pod/YAML::Tiny">YAML::Tiny</a> be grammar driven.</p>
  775.  
  776. <p><a href="https://metacpan.org/pod/Pegex">Pegex</a> is a Perl 6 Rules inspired framework that greatly lowers the barriers
  777. to writing parsers. The main goal of Pegex is to make grammars for parsing a
  778. language or syntax be as human friendly as possible. Pegex is also extremely
  779. fast for pure Perl code.</p>
  780.  
  781. <p>By having the Load functions for <a href="https://metacpan.org/pod/YAML">YAML</a> and <a href="https://metacpan.org/pod/YAML::Tiny">YAML::Tiny</a> be grammar driven,
  782. the following benefits would occur:</p>
  783.  
  784. <ol>
  785. <li>Both modules would parse the same YAML exactly the same</li>
  786. <li>Bugs could easily be fixed for both modules in the same grammar</li>
  787. <li>YAML::Tiny would be tinyer</li>
  788. <li>YAML.pm would become faster</li>
  789. </ol>
  790.  
  791. <h2>Deliverables</h2>
  792.  
  793. <p>This project will provide:</p>
  794.  
  795. <ul>
  796. <li>Pegex grammar for YAML</li>
  797. <li><a href="https://metacpan.org/pod/YAML">YAML</a> and <a href="https://metacpan.org/pod/YAML::Tiny">YAML::Tiny</a> parser/loaders based on the grammar</li>
  798. <li>Common test suite proving compatability</li>
  799. </ul>
  800.  
  801. <h2>Project Details</h2>
  802.  
  803. <p>Pegex is four years old, and has several CPAN modules based on it. It makes
  804. language defining grammars appear crystal clear. It has undergone an
  805. optimization development phase that makes it very fast.</p>
  806.  
  807. <p>Recent work was done to get YAML indentation working in Pegex. This was a
  808. major hurdle. This is now a good time to make a complete YAML grammar. Since
  809. Pegex works in many languages, eventually there will be exactly compatible
  810. YAML parsers in Perl, Python, Ruby, JS, etc.</p>
  811.  
  812. <h2>Inch-stones</h2>
  813.  
  814. <ul>
  815. <li>Write a grammar for YAML in Pegex
  816. <ul>
  817. <li>Grammar will be well documented</li>
  818. <li>Each grammar rule will be tested</li>
  819. </ul></li>
  820. <li>Convert <a href="https://metacpan.org/pod/YAML">YAML</a> to use the grammar for its loader</li>
  821. <li>Convert <a href="https://metacpan.org/pod/YAML::Tiny">YAML::Tiny</a> to use (a subset of) the grammar for its loader</li>
  822. <li>Both modules pass a common test suite</li>
  823. </ul>
  824.  
  825. <h2>Project Schedule</h2>
  826.  
  827. <p>This project will take 2-3 months and can be started immediately upon
  828. acceptance.</p>
  829.  
  830. <h2>Completeness Criteria</h2>
  831.  
  832. <p>Both modules released to CPAN, using the new Pegex grammar and passing the
  833. same tests. Pegex/YAML grammar published in its own GitHub repo.</p>
  834.  
  835. <h2>Bio</h2>
  836.  
  837. <p>Ingy döt Net invented the YAML language, is the author and maintainer of
  838. <a href="https://metacpan.org/pod/YAML">YAML</a> and <a href="https://metacpan.org/pod/YAML::XS">YAML::XS</a> and is one of he people currently actively maintaining
  839. <a href="https://metacpan.org/pod/YAML::Tiny">YAML::Tiny</a>. He also is the creator of the Pegex parsing framework.</p>
  840.  
  841. <p>David Oswald has been a Perl user for over a decade, is an author of several
  842. CPAN modules, and maintainer of more. David also runs Salt Lake Perl Mongers.</p>
  843.  
  844. <p>Ingy and David work well together and have decided to collaborate on a number
  845. of projects that will benefit Perl and Software Development.</p>
  846. ]]>
  847.        
  848.  
  849.    </content>
  850. </entry>
  851.  
  852. <entry>
  853.    <title>Grant Proposal: Inline::C(PP) Module Support</title>
  854.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/09/grant-proposal-inlinecpp-modul.html" />
  855.    <id>tag:news.perlfoundation.org,2014://18.3473</id>
  856.  
  857.    <published>2014-09-15T00:00:02Z</published>
  858.    <updated>2014-09-15T01:11:59Z</updated>
  859.  
  860.    <summary>We have received the following grant application &quot;Inline::C(PP) Module Support&quot;. Please leave feedback in the comments field by September 25th, 2014. Inline::C(PP) Module Support Name Ingy döt Net David Oswald Amount Requested USD $2,000 Synopsis Make Inline::C and Inline::CPP the best choice for writing &quot;XS&quot; modules. Benefits to the Perl Community In 2000, Inline.pm and Inline::C brought XS from &quot;hard things possible&quot; to &quot;hard things simple&quot;. People with basic knowledge of Perl and C could combine the two, without having...</summary>
  861.    <author>
  862.        <name>Makoto Nozaki</name>
  863.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  864.    </author>
  865.    
  866.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  867.    
  868.    
  869.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  870.        <![CDATA[<p><em>We have received the following grant application "Inline::C(PP) Module Support".  Please leave feedback in the comments field by September 25th, 2014.</em></p>
  871.  
  872. <h1>Inline::C(PP) Module Support</h1>
  873.  
  874. <ul>
  875. <li>Name
  876. <ul>
  877. <li>Ingy döt Net</li>
  878. <li>David Oswald</li>
  879. </ul></li>
  880. <li><p>Amount Requested</p>
  881.  
  882. <p>USD $2,000</p></li>
  883. </ul>
  884.  
  885. <h2>Synopsis</h2>
  886.  
  887. <p>Make Inline::C and Inline::CPP the best choice for writing "XS" modules.</p>
  888.  
  889. <h2>Benefits to the Perl Community</h2>
  890.  
  891. <p>In 2000, Inline.pm and Inline::C brought XS from "hard things possible" to
  892. "hard things simple". People with basic knowledge of Perl and C could combine
  893. the two, without having to learn the entirety of the black art of XS.</p>
  894.  
  895. <p>Soon after, support was added for C++, Java and ~25 other languages. Inline
  896. was consider rather successful.</p>
  897.  
  898. <p>The missing piece of all this is that Inline (C, C++) was never really
  899. polished to write CPAN modules; CPAN dists that would handle the compilation
  900. parts at install/build time, and then become nearly indistinguishable from
  901. plain XS modules after installation.</p>
  902.  
  903. <p>A common pattern has been for module programmers to start with Inline::C and
  904. then use it to learn XS, so that they can release the modules to CPAN. Often
  905. Inline::C has been used to generate the XS which is then pasted into a module
  906. distribution with a few adaptations to fit the distribution's framework.
  907. Though very successful, Inline should go further to simplify and remove the
  908. need for authors to manually work through tedious and error-prone steps.</p>
  909.  
  910. <p>In the summer of 2014, a number of core Inline developers came together to get
  911. Inline up to modern standards. We've decided the next big move is to polish up
  912. Inline so that it is ModuleReady™; so that it supports module authorship and
  913. distribution.</p>
  914.  
  915. <p>This will allow many more people to use C and C++ to make Perl modules,
  916. without ever needing to learn XS boilerplate, which is a significant barrier
  917. to entry. Those who already know XS will still be pleased to rediscover that
  918. Inline is an easy way to create XS, and that these enhancements make it a good
  919. choice as a basis for XS module distributions.</p>
  920.  
  921. <h2>Deliverables</h2>
  922.  
  923. <ul>
  924. <li>Allow compilation of inlined C code to happen during a module's build time, and then allow Inline to get out of the way to a greater degree than currently happens.</li>
  925. <li>Make <code>use Inline</code> not trigger a C compile or a C source check when running installed.</li>
  926. <li>Provide support integration for:
  927. <ul>
  928. <li>Dist::Zilla</li>
  929. <li>Module::Install</li>
  930. <li>ExtUtils::MakeMaker</li>
  931. <li>Module::Build</li>
  932. </ul></li>
  933. <li>Make sure that the right things happen at test and build time (vs runtime).</li>
  934. <li>Test that all works properly with C++.</li>
  935. <li>Provide support for C modules where the C code is not 'inlined'
  936. <ul>
  937. <li>Like YAML::XS</li>
  938. </ul></li>
  939. <li>Release a few current XS modules using Inline.
  940. <ul>
  941. <li>YAML::XS</li>
  942. <li>String::Slice</li>
  943. </ul></li>
  944. </ul>
  945.  
  946. <h2>Project Details</h2>
  947.  
  948. <p>Inline development has resurged in #inline on irc.perl.org. The primary
  949. maintainers of Inline, Inline::C and Inline::CPP (C++) are the ones who want
  950. to make this happen.</p>
  951.  
  952. <p>These three modules above have already undergone considerable refactoring,
  953. modernization and bug fixing in the past 3 months, with many releases to
  954. show for it.</p>
  955.  
  956. <p>The goals for this grant are not conceptually hard, but require some focus.
  957. This grant will give us the time to focus. There is no reason to expect this
  958. work will take more than 2 months.</p>
  959.  
  960. <h2>Inch-stones</h2>
  961.  
  962. <ol>
  963. <li><p>Identify existing (or create new) modules that use different 'XS' strategies.  These will be the driving test cases.</p>
  964.  
  965. <p>They should include:</p>
  966.  
  967. <ul>
  968. <li>Inlined C</li>
  969. <li>External C</li>
  970. <li>Currently using XS</li>
  971. <li>Trying to ship with Inline</li>
  972. <li>C++</li>
  973. </ul></li>
  974. <li><p>Adjust Inline to know about development vs build vs installed runtimes.</p>
  975.  
  976. <p>There are a few strategies. Likely there will be a dependency on a small
  977. module, say Inline::Module, that knows how to DTRTs, at the right times.</p></li>
  978. <li><p>Facilitate making Inline and Inline::C/CPP authoring and build tools for distributions, not just runtime tools.</p></li>
  979. <li>Make sure that Inline::C and Inline::CPP work right. In particular, upgrade the grammar tests and parsing to handle many C and C++ constructs that have been found to be lacking in current parsing solutions.</li>
  980. <li><p>Release real modules to CPAN that exercise each of the new development strategies.</p>
  981.  
  982. <p>Watch for results on cpantesters.</p></li>
  983. <li><p>Write automation helpers:</p>
  984.  
  985. <ul>
  986. <li>Dist::Zilla plugin</li>
  987. <li>Module::Install plugin</li>
  988. <li>Documentation for ExtUtils::MakeMaker and Module::Build</li>
  989. </ul></li>
  990. <li><p>Write documention for how to be an "XS" author without learning XS boilerplate.</p>
  991.  
  992. <p>Likely this will include a tutorial.</p></li>
  993. </ol>
  994.  
  995. <h2>Project Schedule</h2>
  996.  
  997. <p>David and Ingy see no reason this can't be done in two months. One month for
  998. code and modules. One month for documentation and testing. We hope to work on
  999. other grants, each about 2 months, so there is good reason to get this one
  1000. done, done right, and out of the way.</p>
  1001.  
  1002. <h2>Completeness Criteria</h2>
  1003.  
  1004. <p>Release of these modules to CPAN (with above support):</p>
  1005.  
  1006. <ul>
  1007. <li><a href="https://metacpan.org/pod/Inline">Inline</a></li>
  1008. <li><a href="https://metacpan.org/pod/Inline::C">Inline::C</a></li>
  1009. <li><a href="https://metacpan.org/pod/Inline::CPP">Inline::CPP</a></li>
  1010. <li><a href="https://metacpan.org/pod/YAML::XS">YAML::XS</a></li>
  1011. <li><a href="https://metacpan.org/pod/Math::Fast::PrimeSieve">Math::Fast::PrimeSieve</a></li>
  1012. </ul>
  1013.  
  1014. <h2>Bio</h2>
  1015.  
  1016. <p>Ingy döt Net is the original creator of Inline and Inline::C. His primary
  1017. focus in Perl is to bring the "hard" things into the hands of beginners.</p>
  1018.  
  1019. <p>David Oswald has been maintaining Inline::CPP for four years, and is the only
  1020. person to have made releases on Inline::CPP since 2003.</p>
  1021.  
  1022. <p>Ingy and David work well together and have decided to collaborate on a number
  1023. of big projects that benefit Perl and Software Development. Inline was the
  1024. obvious first choice.</p>
  1025. ]]>
  1026.        
  1027.  
  1028.    </content>
  1029. </entry>
  1030.  
  1031. </feed>
  1032.  

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