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-11-24T03:26:49Z</updated>
  8.    
  9.    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 4.38</generator>
  10.  
  11. <entry>
  12.    <title>Grant Report: Inline::C(PP) - November 2014</title>
  13.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/11/grant-report-inlinecpp---novem.html" />
  14.    <id>tag:news.perlfoundation.org,2014://18.3528</id>
  15.  
  16.    <published>2014-11-24T03:08:11Z</published>
  17.    <updated>2014-11-24T03:26:49Z</updated>
  18.  
  19.    <summary>Ingy and David have made great strides this month on Inline::Module. Weekly updates can be found at the Ouistreet Inline blog. Highlights &quot;We now have real, usable, open source software on GitHub, so the roadmap and problems will start being expressed as Issues.&quot; Support for ExtUtils::MakeMaker, Dist::Zilla, Zilla::Dist, and Module::Install based distributions for Inline. Well filled out Inline::Module::Tutorial According to David: &quot;In brief, our primary objective now works for four out of the five toolchains we intend to support, and...</summary>
  20.    <author>
  21.        <name>Mark A Jensen</name>
  22.        
  23.    </author>
  24.    
  25.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  26.    
  27.    <category term="grant2014inlinecpp" label="grant-2014-inlinecpp" 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>Ingy and David have made great strides this month on <a href="https://metacpan.org/pod/distribution/Inline-Module/lib/Inline/Module.pod">Inline::Module</a>. Weekly updates can be found at <a href="http://inline.ouistreet.com/">the Ouistreet Inline blog</a>.</p>
  31.  
  32. <p>Highlights</p>
  33.  
  34. <ul>
  35. <li><p>"We now have real, usable, open source software on <a href="https://github.com/ingydotnet/inline-module-pm/issues">GitHub</a>, so the roadmap and problems will start being expressed as Issues."</p></li>
  36. <li><p>Support for <a href="https://metacpan.org/pod/ExtUtils::MakeMaker">ExtUtils::MakeMaker</a>, <a href="https://metacpan.org/pod/Dist::Zilla">Dist::Zilla</a>, <a href="https://metacpan.org/pod/distribution/Zilla-Dist/lib/Zilla/Dist.pod">Zilla::Dist</a>, and <a href="https://metacpan.org/pod/distribution/Module-Install/lib/Module/Install.pod">Module::Install</a> based distributions for Inline.</p></li>
  37. <li><p>Well filled out <a href="https://metacpan.org/pod/distribution/Inline-Module/lib/Inline/Module/Tutorial.pod">Inline::Module::Tutorial</a></p></li>
  38. </ul>
  39.  
  40. <p>According to David: "In brief, our primary objective now works for four out of the five toolchains we intend to support, and we will get the last one done probably this week. After that some polish and a few demonstration releases, and we will be ready to wrap it up."</p>
  41.  
  42. <p>MAJ</p>
  43. ]]>
  44.        
  45.  
  46.    </content>
  47. </entry>
  48.  
  49. <entry>
  50.    <title>Inside look at TPF&apos;s budget process</title>
  51.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/11/inside-look-at-tpfs-budget-pro.html" />
  52.    <id>tag:news.perlfoundation.org,2014://18.3526</id>
  53.  
  54.    <published>2014-11-22T16:42:25Z</published>
  55.    <updated>2014-11-22T16:59:39Z</updated>
  56.  
  57.    <summary>It hasn&apos;t always been the case that The Perl Foundation has much of a budget to speak of. There were many early years that we flew by the seat of our pants. &quot;Is it in the budget&quot; was more or less the same as asking &quot;what&apos;s left in the bank account?&quot; But, as the foundation has grown up, so have our business and accounting practices. First, it is helpful to know that The Perl Foundation has an accountant and bookkeeper...</summary>
  58.    <author>
  59.        <name>Dan Wright</name>
  60.        <uri>http://www.dwright.org</uri>
  61.    </author>
  62.    
  63.    
  64.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  65.        <![CDATA[<p>It hasn't always been the case that The Perl Foundation has much of a budget to speak of.    There were many early years that we flew by the seat of our pants.    "Is it in the budget" was more or less the same as asking "what's left in the bank account?"    But, as the foundation has grown up, so have our business and accounting practices.    </p>
  66.  
  67. <p>First, it is helpful to know that The Perl Foundation has an accountant and bookkeeper that we work with in order to prepare our taxes, keep our records straight, and to help out with the interesting accounting questions that come along with running a charitable foundation.   Everything that we do is tracked using commonly accepted standard accounting practices by an independent, licensed accountant.</p>]]>
  68.        <![CDATA[<p>So, what's up with this mysterious <span class="caps">TPF </span>budget anyway?   How does it all work?   As with everything else, it starts with the Perl community.    The leaders of <span class="caps">TPF </span>do their best to listen to the community.    We try to feel out what the needs are.    We also solicit feedback to determine the attitude on existing programs:  do the members of the community favor what we are doing?   Have the programs been successful?    What needs adjusted?</p>
  69.  
  70. <p>Next, the Treasurer reaches out to the Chairpeople of <span class="caps">TPF'</span>s committees:  Community Advocacy, Conferences, Marketing, Grants, and Steering.  They needs to write up their plans for the coming year.    They need to explain what they want to do, and how much it will cost. </p>
  71.  
  72. <p>Once all of that is done, the Treasurer meets with the President to get feedback on her visions for the upcoming year.    The feedback that has been received and various committee requests are discussed.    There are also program that operate outside of a specific committee (for example, the Outreach Program for Women.)   All of this must be considered in detail in order to formulate both a reasonable set of objectives for the upcoming year and a matching budget.    The outcome is a draft plan for the following year.</p>
  73.  
  74. <p>Finally, the draft plan is sent along to The Perl Foundation's Board of Directors.    The Board reviews the recommendations, makes adjustments as they deem necessary, and ultimately approves the final budget.</p>
  75.  
  76. <p>Once the budget has been approved, each chairperson has the discretion to spend their budget on the items they had initially requested (within a few limitations and guidelines.)</p>
  77.  
  78. <p>The budgets can get a little complicated due to the way we handle fund accounting:   We have a general fund that handle a majority of our operations.   We also operate separate funds for the Ian Hague grants and the Perl 5 Core grants.     So, each of those need to be budgeted separately.</p>
  79.  
  80. <p>We also operate separate custodial funds for the various Perl workshops that associate with us.   But since <span class="caps">TPF'</span>s money typically does not flow in or out of the Perl workshops, we do not budget those.</p>
  81.  
  82. <p>The entire process takes about three months to complete.  Requests from Chairpeople were due today.    We expect to have the 2015 budget final by early January.</p>]]>
  83.    </content>
  84. </entry>
  85.  
  86. <entry>
  87.    <title>Perl::Lint Released</title>
  88.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/11/perllint-released.html" />
  89.    <id>tag:news.perlfoundation.org,2014://18.3524</id>
  90.  
  91.    <published>2014-11-17T19:28:41Z</published>
  92.    <updated>2014-11-17T19:54:01Z</updated>
  93.  
  94.    <summary>Since our last report, Taiki has made even more progress on Perl::Lint, a static analyser for Perl 5. Taiki has now released a usable version of this code to CPAN that improves on the development version mentioned in our previous report. So, now would be a great time to install Perl::Lint using your favourite CPAN client, run your code through Perl::Lint and let us know what you think. If you already use Perl::Critic to check your code, how do the...</summary>
  95.    <author>
  96.        <name>Tom Hukins</name>
  97.        
  98.    </author>
  99.    
  100.    
  101.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  102.        <![CDATA[<p>Since <a href="http://news.perlfoundation.org/2014/09/more-perllint-progress-2.html">our last report</a>, Taiki has made even more progress on Perl::Lint, a static analyser for Perl 5.  Taiki has now <a href="https://metacpan.org/release/Perl-Lint">released a usable version of this code to <span class="caps">CPAN</span></a> that improves on the development version mentioned in our previous report.</p>
  103.  
  104. <p>So, now would be a great time to install Perl::Lint using your favourite <span class="caps">CPAN </span>client, run your code through Perl::Lint and let us know what you think. If you already use Perl::Critic to check your code, how do the two compare?</p>
  105.  
  106. <p>Although Perl::Lint is ready for production use, Taiki still has a few remaining tasks before work on this grant completes:</p>
  107.  
  108.  
  109. <ul>
  110. <li><a href="https://github.com/moznion/Perl-Lint/issues/69">Implement remaining policies</a></li>
  111. <li><a href="https://github.com/moznion/Perl-Lint/issues/56">Stop using Regexp::Parser</a></li>
  112. <li><a href="https://github.com/moznion/Perl-Lint/issues/2">Support a <em>## no lint</em> option</a></li>
  113. </ul>
  114.  
  115.  
  116.  
  117. <p>As before, you can track development in the <a href="https://github.com/moznion/Perl-Lint">project's public Github repository</a>.</p>]]>
  118.        
  119.    </content>
  120. </entry>
  121.  
  122. <entry>
  123.    <title>YAPC::NA 2015 to be hosted at Little America</title>
  124.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/11/yapcna-2015-to-be-hosted-at-li.html" />
  125.    <id>tag:news.perlfoundation.org,2014://18.3522</id>
  126.  
  127.    <published>2014-11-17T15:42:48Z</published>
  128.    <updated>2014-11-17T15:46:50Z</updated>
  129.  
  130.    <summary>The Perl Foundation, along with the Salt Lake Perl Mongers is pleased to announce that the official venue for YAPC::NA 2015 will be the Little America Hotel, in Salt Lake City, Utah.</summary>
  131.    <author>
  132.        <name>TPF Conferences Staff</name>
  133.        
  134.    </author>
  135.    
  136.        <category term="Conferences" scheme="http://www.sixapart.com/ns/types#category" />
  137.    
  138.        <category term="Marketing" scheme="http://www.sixapart.com/ns/types#category" />
  139.    
  140.        <category term="Meetings" scheme="http://www.sixapart.com/ns/types#category" />
  141.    
  142.    <category term="yapc" label="yapc" scheme="http://www.sixapart.com/ns/types#tag" />
  143.    <category term="yapc2015" label="YAPC 2015" scheme="http://www.sixapart.com/ns/types#tag" />
  144.    <category term="yapcconferences" label="yapc conferences" scheme="http://www.sixapart.com/ns/types#tag" />
  145.    <category term="yapcna" label="YAPC::NA" scheme="http://www.sixapart.com/ns/types#tag" />
  146.    
  147.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  148.        <![CDATA[<p>Walnut, CA - The Perl Foundation, along with the Salt Lake Perl Mongers is pleased to announce that the official venue for <span class="caps">YAPC</span>::NA 2015 will be the Little America Hotel, in Salt Lake City, Utah.</p>
  149.  
  150. <p>Little America, a four-diamond hotel located on South Main Street has been working with this year's organizer team to meet all of the needs necessary to host a <span class="caps">YAPC.</span> The facility, which boasts 14 meeting rooms and 25,000 square feet, will provide a high tech and inviting environment for next year's conference. </p>
  151.  
  152. <p>The Perl Foundation has negotiated special room rates with Little America, which are available through March 1, 2015. These rates start at $129 per night, and reservations can be made directly with Little America.</p>
  153.  
  154. <p>The conference website is now live, and registrations are being accepted online at <a href="http://www.yapcna.org">www.yapcna.org</a>. The official Call for Talks is also open on the event website. The conference fee for 2015 has been set at $250. Discounts for students and military (active and retired) will be released in the upcoming weeks. </p>
  155.  
  156. <p>This year's conference theme, "Perl Elevated," will offer four different tracks, including a beginner-style track for those new to the Perl Community. </p>
  157.  
  158. <p>For more information, and to register for <span class="caps">YAPC</span>::NA, please visit www.yapcna.org. Conference updates, including schedules, add-on classes, and speakers, will be pushed regularly via the conference blog at blog.yapcna.org. </p>]]>
  159.        
  160.    </content>
  161. </entry>
  162.  
  163. <entry>
  164.    <title>November 2014 Grant Proposal</title>
  165.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/11/november-2014-grant-proposal.html" />
  166.    <id>tag:news.perlfoundation.org,2014://18.3520</id>
  167.  
  168.    <published>2014-11-15T21:00:01Z</published>
  169.    <updated>2014-11-16T02:48:54Z</updated>
  170.  
  171.    <summary>The Grants Committee has received one grant proposal for the November 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 there. The Committee members will start the voting process on November 26th and the conclusion will be announced by November 30th. IO::All Redux, Ingy döt Net and David Oswald, USD 4,000 Note that this proposal was reviewed in the September round (previous proposal...</summary>
  172.    <author>
  173.        <name>Makoto Nozaki</name>
  174.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  175.    </author>
  176.    
  177.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  178.    
  179.    
  180.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  181.        <![CDATA[<p>The Grants Committee has received one grant proposal for the November round.  Before the Committee members vote, we would like to solicit feedback from the Perl community on the proposal.</p>
  182.  
  183. <p>Review the proposal below and please comment there.  The Committee members will start the voting process on November 26th and the conclusion will be announced by November 30th.</p>
  184.  
  185. <ul>
  186. <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 4,000</li>
  187. </ul>
  188.  
  189. <p>Note that this proposal was reviewed in the September round (<a href="http://news.perlfoundation.org/2014/09/grant-proposal-ioall-redux.html">previous proposal and comments</a>).  While the proposal got more yes voters than nos, the committee decided not to fund it for the September round and review this again (<a href="http://news.perlfoundation.org/2014/09/september-2014-grant-votes.html">details</a>). Ingy and David revised the proposal and we have posted the updated version.</p>
  190. ]]>
  191.        
  192.  
  193.    </content>
  194. </entry>
  195.  
  196. <entry>
  197.    <title>Grant Proposal: IO::All Redux</title>
  198.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/11/grant-proposal-ioall-redux-1.html" />
  199.    <id>tag:news.perlfoundation.org,2014://18.3518</id>
  200.  
  201.    <published>2014-11-15T21:00:00Z</published>
  202.    <updated>2014-11-16T02:44:00Z</updated>
  203.  
  204.    <summary>We have received the following grant application &quot;IO::All Redux&quot;. Please leave feedback in the comments field by November 25th, 2014. IO::All Redux Name Ingy döt Net David Oswald Amount Requested USD $4,000 Synopsis Rewrite IO::All to match the needs of 10 years experience. Benefits to the Perl Community IO::All is a Perl module that attempts to make all Input/Output operations in Perl, as simple, normal, and uniform as possible. IO::All has been in existence since 2004. It is popular, useful...</summary>
  205.    <author>
  206.        <name>Makoto Nozaki</name>
  207.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  208.    </author>
  209.    
  210.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  211.    
  212.    
  213.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  214.        <![CDATA[<p><em>We have received the following grant application "IO::All Redux".  Please leave feedback in the comments field by November 25th, 2014.</em></p>
  215.  
  216. <h1>IO::All Redux</h1>
  217.  
  218. <ul>
  219. <li>Name
  220. <ul>
  221. <li>Ingy döt Net</li>
  222. <li>David Oswald</li>
  223. </ul></li>
  224. <li><p>Amount Requested</p>
  225.  
  226. <p>USD $4,000</p></li>
  227. </ul>
  228.  
  229. <h2>Synopsis</h2>
  230.  
  231. <p>Rewrite IO::All to match the needs of 10 years experience.</p>
  232.  
  233. <h2>Benefits to the Perl Community</h2>
  234.  
  235. <p>IO::All is a Perl module that attempts to make all Input/Output operations in
  236. Perl, as simple, normal, and uniform as possible. IO::All has been in
  237. existence since 2004. It is popular, useful and somewhat extensible, but has a
  238. number of inconsistencies, flaws and misgivings.</p>
  239.  
  240. <p>The proposal is to refactor and<em>or rewrite the IO::All code to become the
  241. perfect way to encode almost all of Perl I</em>O needs and file system needs. In
  242. other words:</p>
  243.  
  244. <ul>
  245. <li>All things are done safely</li>
  246. <li>Unicode issues are all handled correctly</li>
  247. <li>Options have the proper scope (lexical<em>package</em>object)</li>
  248. <li>Can be used safely in production</li>
  249. <li>Consistent method names (match prior art when possible)</li>
  250. <li>Stays simple for 1-liners (small needs)</li>
  251. <li>Internals are all plugin based rather than semi-hardcoded</li>
  252. <li>All operations are checked for errors</li>
  253. <li>Defaults are sane</li>
  254. <li>Mo(o(se)) compatible OO</li>
  255. <li>Weirder stuff like <em>operator overloads</em> will be off by default</li>
  256. </ul>
  257.  
  258. <p>IO::All has a community of maintainers on irc.perl.org/#io-all. These
  259. ideas are the result of working with them and talking about a rewrite for
  260. many years.</p>
  261.  
  262. <h2>Deliverables</h2>
  263.  
  264. <p>Using the <a href="https://metacpan.org/pod/Alt">Alt</a> module strategy, we deliver an <a href="https://metacpan.org/pod/Alt-IO-All-Redux">Alt-IO-All-Redux</a> dist that
  265. installs a new IO::All. This is tested in beta until deemed safe to release
  266. properly as the new IO-All dist.</p>
  267.  
  268. <p>Current IO::All plugins are revised to the new strategy.</p>
  269.  
  270. <h2>Project Details</h2>
  271.  
  272. <p>See:</p>
  273.  
  274. <ul>
  275. <li><a href="https://github.com/ingydotnet/io-all-pm#readme">https://github.com/ingydotnet/io-all-pm#readme</a></li>
  276. <li><a href="https://raw.githubusercontent.com/ingydotnet/io-all-pm/master/note/Design.swim">https://raw.githubusercontent.com/ingydotnet/io-all-pm/master/note/Design.swim</a></li>
  277. </ul>
  278.  
  279. <p>The style of the <a href="http://inline.ouistreet.com/">Inline Grant</a> will be
  280. continued:</p>
  281.  
  282. <ul>
  283. <li>Regular Blogging/Tweeting</li>
  284. <li>Public Pair Programming</li>
  285. </ul>
  286.  
  287. <h2>Inch-stones</h2>
  288.  
  289. <ul>
  290. <li>Create Alt-IO-All-Redux dist so that new code can be used and tested by the community immediately</li>
  291. <li>Write tests for new behaviors</li>
  292. <li>Refactor the code to match the new design</li>
  293. <li>Port current IO::All extension modules to new design</li>
  294. <li>Get people on #io-all IRC channel and beyond to test the rewrite</li>
  295. <li>Release as IO-All when deemed ready</li>
  296. </ul>
  297.  
  298. <h2>Project Schedule</h2>
  299.  
  300. <p>This project will take 3 months and can be started immediately upon
  301. acceptance.</p>
  302.  
  303. <h2>Completeness Criteria</h2>
  304.  
  305. <p>Alt-IO-All-Redux passes all tests, is vetted by the community and is released
  306. to CPAN as the new IO-All dist.</p>
  307.  
  308. <h2>Bio</h2>
  309.  
  310. <p>Ingy döt Net wrote IO::All in 2004. Of his many CPAN modules, it is probably
  311. one of the 3 most popular.</p>
  312.  
  313. <p>David Oswald has been a Perl user for over a decade, is an author of several
  314. CPAN modules, and maintainer of more. David also runs Salt Lake Perl Mongers.</p>
  315.  
  316. <p>Ingy and David work well together and have decided to collaborate on a number
  317. of projects that will benefit Perl and Software Development.</p>
  318. ]]>
  319.        
  320.  
  321.    </content>
  322. </entry>
  323.  
  324. <entry>
  325.    <title>Grant Reports for October</title>
  326.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/11/grant-reports-for-october-cfp.html" />
  327.    <id>tag:news.perlfoundation.org,2014://18.3516</id>
  328.  
  329.    <published>2014-11-13T12:00:00Z</published>
  330.    <updated>2014-11-16T02:25:38Z</updated>
  331.  
  332.    <summary>Grant recipients are required to publish a grant report every month. We got the following updates in October: Grant Report: Modern OO Programming in Perl (Book) Grant Report: Inline::C(PP) - October 2014 ACT - Voyager - logbook 2014-10-01 ACT - Voyager - logbook 2014-09-01 We appreciate those who made great progress and kept the community updated during the autumn conference season. Just a reminder, CFP for the November round will be closed tomorrow....</summary>
  333.    <author>
  334.        <name>Makoto Nozaki</name>
  335.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  336.    </author>
  337.    
  338.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  339.    
  340.    
  341.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  342.        <![CDATA[<p>Grant recipients are required to publish a grant report every month.  We got the following updates in October:</p>
  343.  
  344. <ul>
  345. <li><a href="http://news.perlfoundation.org/2014/10/grant-report-modern-oo-program-1.html">Grant Report: Modern OO Programming in Perl (Book)</a></li>
  346. <li><a href="http://news.perlfoundation.org/2014/10/grant-report-inlinecpp---octob.html">Grant Report: Inline::C(PP) - October 2014</a></li>
  347. <li><a href="http://news.perlfoundation.org/2014/10/act---voyager---logbook-2014-1.html">ACT - Voyager - logbook 2014-10-01</a></li>
  348. <li><a href="http://news.perlfoundation.org/2014/10/act---voyager---logbook-2014-0.html">ACT - Voyager - logbook 2014-09-01</a></li>
  349. </ul>
  350.  
  351. <p>We appreciate those who made great progress and kept the community updated during the autumn conference season.</p>
  352.  
  353. <p>Just a reminder, <a href="http://news.perlfoundation.org/2014/11/november-2014-grant-votes.html">CFP for the November round</a> will be closed tomorrow.</p>
  354. ]]>
  355.        
  356.  
  357.    </content>
  358. </entry>
  359.  
  360. <entry>
  361.    <title>Maintaining the Perl 5 Core: Report for Month 13</title>
  362.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/11/maintaining-the-perl-5-core-re-11.html" />
  363.    <id>tag:news.perlfoundation.org,2014://18.3514</id>
  364.  
  365.    <published>2014-11-09T22:01:37Z</published>
  366.    <updated>2014-11-09T22:05:09Z</updated>
  367.  
  368.    <summary>Dave Mitchell writes: The main things I worked on this month were: set up the beginnings of a basic performance/optimisation testing infrastructure under t/perf/ investigated the performance of perl&apos;s string allocation and growing implementation, and came up with some suggested improvements (which I haven&apos;t yet done). fixed some issues with $#shared with threads::shared arrays 5:26 [perl #122950] Off-by-one when truncating shared array 0:20 fix compiler warnings 2:48 investigate floating-point performance regression 6:32 investigate sv_grow() algorithm 15:07 process p5p mailbox 0:26...</summary>
  369.    <author>
  370.        <name>Karen Pauley</name>
  371.        <uri>http://martian.org/karen</uri>
  372.    </author>
  373.    
  374.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  375.    
  376.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  377.    
  378.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  379.        <![CDATA[<p><em>Dave Mitchell writes:</em></p>
  380.  
  381. <p>The main things I worked on this month were:</p>
  382.  
  383.  
  384. <ul>
  385. <li>set up the beginnings of a basic performance/optimisation testing infrastructure under t/perf/</li>
  386. </ul>
  387.  
  388.  
  389.  
  390.  
  391. <ul>
  392. <li>investigated the performance of perl's string allocation and growing implementation, and came up with some suggested improvements (which I haven't yet done).</li>
  393. </ul>
  394.  
  395.  
  396.  
  397.  
  398. <ul>
  399. <li>fixed some issues with $#shared with threads::shared arrays</li>
  400. </ul>
  401.  
  402.  
  403.  
  404. <blockquote><p>5:26 [perl #122950] Off-by-one when truncating <strong>shared</strong> array<br />
  405. 0:20 fix compiler warnings<br />
  406. 2:48 investigate floating-point performance regression<br />
  407. 6:32 investigate sv_grow() algorithm<br />
  408. 15:07 process p5p mailbox<br />
  409. 0:26 review "Speeding up perl's <span class="caps">OOP</span>" patch<br />
  410. 3:58 set up t/perf/</p></blockquote>
  411.  
  412. <p><b>34:37 Total (HH::MM)</b></p>
  413.  
  414. <p>As of 2014/10/31: since the beginning of the grant:</p>
  415.  
  416. <blockquote><p>54.7 weeks<br />
  417. 747.8 total hours<br />
  418. 13.7 average hours per week</p></blockquote>
  419.  
  420. <p>There are 452 hours left on the grant</p>]]>
  421.        
  422.    </content>
  423. </entry>
  424.  
  425. <entry>
  426.    <title>Call For Grant Proposals (November Round)</title>
  427.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/11/november-2014-grant-votes.html" />
  428.    <id>tag:news.perlfoundation.org,2014://18.3510</id>
  429.  
  430.    <published>2014-11-02T20:00:00Z</published>
  431.    <updated>2014-11-13T16:56:48Z</updated>
  432.  
  433.    <summary>This is a bi-monthly reminder. The Grants Committee is accepting grant proposals all the time. We evaluate them every two months and another evaluation period has come. If you have an idea for doing some Perl work that will benefit the Perl community, consider sending a grant application. The application deadline for this round is 23:59 November 14th UTC. We will publish the received applications, get community feedback and conclude the acceptance by November 30th. The format will be the...</summary>
  434.    <author>
  435.        <name>Makoto Nozaki</name>
  436.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  437.    </author>
  438.    
  439.        <category term="Grants" 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><em>This is a bi-monthly reminder.</em></p>
  444.  
  445. <p>The Grants Committee is accepting grant proposals all the time.  We evaluate them every two months and another evaluation period has come.</p>
  446.  
  447. <p>If you have an idea for doing some Perl work that will benefit the Perl community, consider sending a grant application. <strong>The application deadline for this round is 23:59 November 14th UTC.</strong> We will publish the received applications, get community feedback and conclude the acceptance by November 30th.</p>
  448.  
  449. <p>The format will be the same as the September round (<a href="http://news.perlfoundation.org/2014/09/september-2014-grant-proposals.html">Proposals</a>, <a href="http://news.perlfoundation.org/2014/09/september-2014-grant-votes.html">Results</a>).</p>
  450.  
  451. <p>To apply, please read <a href="http://www.perlfoundation.org/how_to_write_a_proposal">How to Write a
  452. Proposal</a>.
  453. <a href="http://www.perlfoundation.org/rules_of_operation">Rules of Operation</a>
  454. will also help you understand how the grant process works.</p>
  455.  
  456. <p>We will confirm the receipt of application within 24 hours.</p>
  457.  
  458. <p>If you have further questions, please comment here.  If your comment
  459. does not show up here within 24 hours, the chances are that the spam
  460. filter did something bad. Get in touch with me at tpf-grants-secretary
  461. at perl-foundation.org.</p>
  462. ]]>
  463.        
  464.  
  465.    </content>
  466. </entry>
  467.  
  468. <entry>
  469.    <title>Grant Report: Modern OO Programming in Perl (Book) - Oct 2014</title>
  470.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/10/grant-report-modern-oo-program-1.html" />
  471.    <id>tag:news.perlfoundation.org,2014://18.3509</id>
  472.  
  473.    <published>2014-10-30T02:12:39Z</published>
  474.    <updated>2014-10-30T02:31:33Z</updated>
  475.  
  476.    <summary><![CDATA[Toby Inkster reports in his blog that the book took a back seat to other duties this month. He is continuing to develop the basic ideas, most recently in the form of a talk that he will present at the London Perl Workshop. Toby has shared this &lt;SPOILER_ALERT&gt; material &lt;/SPOILER_ALERT&gt;. MAJ...]]></summary>
  477.    <author>
  478.        <name>Mark A Jensen</name>
  479.        
  480.    </author>
  481.    
  482.    <category term="grant2014moopbook" label="grant-2014-moopbook" scheme="http://www.sixapart.com/ns/types#tag" />
  483.    
  484.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  485.        <![CDATA[<p>Toby Inkster reports in his <a href="http://blogs.perl.org/users/toby_inkster/2014/10/book-report---october-2014.html">blog</a> that the <a href="https://github.com/tobyink/docs-modern-oop">book</a> took a back seat to other duties this month. He is continuing to develop the basic ideas, most recently in the form of a talk that he will present at the <a href="http://act.yapc.eu/lpw2014/">London Perl Workshop</a>. Toby has shared this &lt;SPOILER_ALERT&gt; <a href="https://github.com/tobyink/docs-modern-oop/tree/master/talks/three-weird-tricks">material</a> &lt;/SPOILER_ALERT&gt;.</p>
  486.  
  487. <p>MAJ</p>
  488. ]]>
  489.        
  490.  
  491.    </content>
  492. </entry>
  493.  
  494. <entry>
  495.    <title>Maintaining the Perl 5 Core: Report for Month 12</title>
  496.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/10/maintaining-the-perl-5-core-re-10.html" />
  497.    <id>tag:news.perlfoundation.org,2014://18.3507</id>
  498.  
  499.    <published>2014-10-28T06:28:00Z</published>
  500.    <updated>2014-10-28T06:45:25Z</updated>
  501.  
  502.    <summary>Dave Mitchell writes: The main things I worked on this month were: finished off making the op_private OP flags and data be auto-generated from a single consistent source. I started to investigate how the allocation and growing of strings (in Perl_sv_grow()) interacts (sometimes badly) with COW and the underlying malloc() library implementation reviewing, discussing, fixing up and applying Syber&apos;s method call optimisation work 3:52 [perl #122666] Bleadperl v5.21.1-120-g34dadc6 breaks SYOHEX/Text-Xslate-3.3.3.tar.gz 1:14 [perl #122791] Memory leak oddities with various versions of...</summary>
  503.    <author>
  504.        <name>Karen Pauley</name>
  505.        <uri>http://martian.org/karen</uri>
  506.    </author>
  507.    
  508.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  509.    
  510.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  511.    
  512.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  513.        <![CDATA[<p><em>Dave Mitchell writes:</em></p>
  514.  
  515. <p>The main things I worked on this month were:</p>
  516.  
  517.  
  518. <ul>
  519. <li>finished off making the op_private OP flags and data be auto-generated from a single consistent source.</li>
  520. </ul>
  521.  
  522.  
  523.  
  524.  
  525. <ul>
  526. <li>I started to investigate how the allocation and growing of strings (in Perl_sv_grow()) interacts (sometimes badly) with <span class="caps">COW </span>and the underlying malloc() library implementation</li>
  527. </ul>
  528.  
  529.  
  530.  
  531.  
  532. <ul>
  533. <li>reviewing, discussing, fixing up and applying Syber's method call optimisation work</li>
  534. </ul>
  535.  
  536.  
  537.  
  538. <blockquote><p>3:52 [perl #122666] Bleadperl v5.21.1-120-g34dadc6 breaks <span class="caps">SYOHEX</span>/Text-Xslate-3.3.3.tar.gz<br />
  539. 1:14 [perl #122791] Memory leak oddities with various versions of Perl<br />
  540. 0:36 create t/re/speed.t<br />
  541. 14:21 investigate sv_grow() algorithm<br />
  542. 19:07 make op_private flag definitions be auto-generated<br />
  543. 0:57 misc tidying up<br />
  544. 24:19 process p5p mailbox<br />
  545. 9:14 review "Speeding up perl's <span class="caps">OOP</span>" patch<br />
  546. 2:20 sort out B.xs op_padix issue<br />
  547. 1:53 sort out globals.c make dependencies</p></blockquote>
  548.  
  549. <p><b>77:53 Total (HH::MM)</b></p>
  550.  
  551. <p>As of 2014/09/30: since the beginning of the grant:</p>
  552.  
  553. <blockquote><p>50.3 weeks<br />
  554. 712.0 total hours<br />
  555. 14.2 average hours per week</p></blockquote>
  556.  
  557. <p>There are 88 hours left on the grant</p>]]>
  558.        
  559.    </content>
  560. </entry>
  561.  
  562. <entry>
  563.    <title>Grant Report: Inline::C(PP) - October 2014</title>
  564.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/10/grant-report-inlinecpp---octob.html" />
  565.    <id>tag:news.perlfoundation.org,2014://18.3505</id>
  566.  
  567.    <published>2014-10-27T10:53:15Z</published>
  568.    <updated>2014-10-30T02:09:00Z</updated>
  569.  
  570.    <summary>Ingy and David report on their Inline:C(PP) grant progress in their joint blog. Some exciting highlights: All work being done publicly: David and Ingy code in remote PairUp™ session (tmux) All realtime communication in IRC (irc.perl.org#inline) Tmux to be termcasted soon (live terminal in a browser) Fork &apos;em on GitHub Figured out a decent Inline Module API strategy Authors do 3 simple new things to ship Inline code to CPAN No end-user dependency on Inline for these modules End result...</summary>
  571.    <author>
  572.        <name>Mark A Jensen</name>
  573.        
  574.    </author>
  575.    
  576.    <category term="grant2014inlinecpp" label="grant-2014-inlinecpp" scheme="http://www.sixapart.com/ns/types#tag" />
  577.    
  578.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  579.        <![CDATA[<p>Ingy and David report on their Inline:C(PP) grant progress in their <a href="http://inline.ouistreet.com/page/inline-grant-weekly-report-1.html">joint blog</a>. Some exciting highlights:</p>
  580.  
  581.  
  582. <ul>
  583. <li>    All work being done publicly:
  584. <ul>
  585. <li>        David and Ingy code in remote PairUp™ session (tmux)</li>
  586. <li>        All realtime communication in <span class="caps">IRC </span>(irc.perl.org#inline)</li>
  587. <li>        Tmux to be termcasted soon (live terminal in a browser)</li>
  588. <li>        Fork 'em on <a href="https://github.com/ingydotnet/inline-module-pm">GitHub</a></li>
  589. </ul>
  590. </li>
  591. <li>    Figured out a decent Inline Module <span class="caps">API </span>strategy
  592. <ul>
  593. <li>        Authors do 3 simple new things to ship Inline code to <span class="caps">CPAN</span></li>
  594. <li>        No end-user dependency on Inline for these modules</li>
  595. <li>        End result is essentially same as hand written XS</li>
  596. </ul>
  597. </li>
  598. <li>    Created specification document: http://inline.ouistreet.com/node/v3e7.html</li>
  599. <li>    Released two new <span class="caps">CPAN </span>modules:
  600. <ul>
  601. <li>       <a href="https://metacpan.org/pod/Inline::Module"> Inline::Module</a> (The majority of the grant coding)</li>
  602. <li>        <a href="https://metacpan.org/release/Acme-Math-XS">Acme::Math::XS</a> (first test module using Inline::C)</li>
  603. </ul>
  604. </li>
  605. <li>    Created a <a href="http://inline.ouistreet.com/">new blog site</a> to document the Inline Grant Project<br />
  606.     ("A new site using some of our other loved technologies: Cog, Coffee, make, Swim, Jemplate, gh-pages, BootStrap")</li>
  607. </ul>
  608.  
  609.  
  610.  
  611. <p>Looks pretty cool. Here is Acme::Math::XS in its totality:</p>
  612.  
  613. <blockquote><p>use strict; use warnings;<br />
  614. package Acme::Math::XS;<br />
  615. our $VERSION = '0.0.2';<br />
  616. <br />
  617. use Exporter 'import';<br />
  618. our @EXPORT = qw(<br />
  619.    add<br />
  620.    subtract<br />
  621. );<br />
  622. <br />
  623. use Acme::Math::XS::Inline C =&gt; &lt;&lt;'...';<br />
  624. long add(long a, long b) {<br />
  625.    return a + b;<br />
  626. }<br />
  627. <br />
  628. long subtract(long a, long b) {<br />
  629.    return a - b;<br />
  630. } <br />
  631. 1;</p></blockquote>
  632.  
  633.  
  634. <p><span class="caps">MAJ</span></p>]]>
  635.        
  636.    </content>
  637. </entry>
  638.  
  639. <entry>
  640.    <title>ACT - Voyager - logbook 2014-10-01</title>
  641.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/10/act---voyager---logbook-2014-1.html" />
  642.    <id>tag:news.perlfoundation.org,2014://18.3503</id>
  643.  
  644.    <published>2014-10-17T14:40:21Z</published>
  645.    <updated>2014-10-17T14:50:53Z</updated>
  646.  
  647.    <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>
  648.    <author>
  649.        <name>Elizabeth Mattijsen</name>
  650.        
  651.    </author>
  652.    
  653.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  654.    
  655.    <category term="act" label="act" scheme="http://www.sixapart.com/ns/types#tag" />
  656.    
  657.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  658.        <![CDATA[<p><i>As time moves on the Voyage gradually moves forward.</i></p>
  659.  
  660. <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>
  661.  
  662. <h1>The Apache &amp; mod_perl nightmare</h1>
  663.  
  664. <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>
  665.  
  666. <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>
  667.  
  668. <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>
  669.  
  670. <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>
  671.  
  672. <ul>
  673. <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>
  674. <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>
  675. </ul>
  676.  
  677. <h1>The green pastures of 'Act-out-of-the-box'</h1>
  678.  
  679. So, I took all that info and started to work on a super easy way for any Act developer to start hacking:<br />
  680. <ol>
  681. <li>Download Vagrant</li>
  682. <li>Download the <i>'Act-out-of-the-box'</i> vagrant image</li>
  683. <li>vagrant up</li>
  684. <li>Choose your install type</li>
  685. <li>Welcome to Act</li>
  686. </ol>
  687. So, what is happening there, what install types...?
  688.  
  689. <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>
  690.  
  691. <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>
  692.  
  693. <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>
  694.  
  695. <ul>
  696. <li>Apache 1.2.42</li>
  697. <li>mod_perl 1.31</li>
  698. <li>postfix</li>
  699. <li>PostgreSQL</li>
  700. <li>sample databases</li>
  701. <li>Act dependencies</li>
  702. </ul>
  703. 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.
  704.  
  705. <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>
  706.  
  707. <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>
  708.  
  709. <h1>Patch -p2 hackathon in Lyon</h1>
  710.  
  711. <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>
  712.  
  713. <p><i>Your Captain</i> Theo van Hoesel</p>]]>
  714.        
  715.    </content>
  716. </entry>
  717.  
  718. <entry>
  719.    <title>ACT - Voyager - logbook 2014-09-01</title>
  720.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/10/act---voyager---logbook-2014-0.html" />
  721.    <id>tag:news.perlfoundation.org,2014://18.3501</id>
  722.  
  723.    <published>2014-10-17T14:08:43Z</published>
  724.    <updated>2014-10-17T14:18:35Z</updated>
  725.  
  726.    <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>
  727.    <author>
  728.        <name>Elizabeth Mattijsen</name>
  729.        
  730.    </author>
  731.    
  732.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  733.    
  734.    <category term="act" label="ACT" scheme="http://www.sixapart.com/ns/types#tag" />
  735.    
  736.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  737.        <![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>
  738.  
  739. <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>
  740.  
  741. <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>
  742.  
  743. <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>
  744.  
  745. <p>The next day there was a BoF with a dozen people showing up that had different kinds off interests:</p>
  746.  
  747. <ul>
  748. <li>people that want a complete rewrite</li>
  749. <li>people that want a quick fix and new features on top of the current <span class="caps">ACT</span></li>
  750. <li>people that want to change the internals first</li>
  751. </ul>
  752. 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.
  753.  
  754. <p>We are looking forward to see what Sawyer is doing for some kind of wizardry.</p>
  755.  
  756. <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>
  757.  
  758. <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>
  759.  
  760. <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>
  761.  
  762. <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>
  763.  
  764. <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>
  765.  
  766. <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>
  767.  
  768. <p>Theo van Hoesel</p>]]>
  769.        
  770.    </content>
  771. </entry>
  772.  
  773. <entry>
  774.    <title>Grant Extension Request: Dave Mitchell</title>
  775.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2014/10/grant-extension-request-dave-m.html" />
  776.    <id>tag:news.perlfoundation.org,2014://18.3497</id>
  777.  
  778.    <published>2014-10-09T21:40:13Z</published>
  779.    <updated>2014-10-09T21:44:59Z</updated>
  780.  
  781.    <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>
  782.    <author>
  783.        <name>Karen Pauley</name>
  784.        <uri>http://martian.org/karen</uri>
  785.    </author>
  786.    
  787.    
  788.    <content type="html" xml:lang="en" xml:base="http://news.perlfoundation.org/">
  789.        <![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>
  790.  
  791. <p><a href="http://news.perlfoundation.org/2014/10/maintaining-the-perl-5-core-re-9.html">Report for Month 11</a><br />
  792. <a href="http://news.perlfoundation.org/2014/08/maintaining-the-perl-5-core-re-8.html">Report for Month 10</a><br />
  793. <a href="http://news.perlfoundation.org/2014/07/maintaining-the-perl-5-core-re-7.html">Report for Month 9</a></p>
  794.  
  795. <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>
  796.  
  797. <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>]]>
  798.        
  799.    </content>
  800. </entry>
  801.  
  802. </feed>
  803.  

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