Congratulations!

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

Recommendations

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

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

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <feed xmlns="http://www.w3.org/2005/Atom">
  3.    <title>The Perl Foundation</title>
  4.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/" />
  5.    <link rel="self" type="application/atom+xml" href="http://news.perlfoundation.org/atom.xml" />
  6.    <id>tag:news.perlfoundation.org,2010-03-22://18</id>
  7.    <updated>2016-12-07T22:48:27Z</updated>
  8.    
  9.    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 6.2.2</generator>
  10.  
  11. <entry>
  12.    <title>Grant Proposal: Learning Perl 6, a book from O&apos;Reilly Media</title>
  13.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/12/grant-proposal-learning-perl-6.html" />
  14.    <id>tag:news.perlfoundation.org,2016://18.3831</id>
  15.  
  16.    <published>2016-12-06T23:00:00Z</published>
  17.    <updated>2016-12-07T22:48:27Z</updated>
  18.  
  19.    <summary>The Grants Committee has received one grant proposal for the November/December round. Before the Committee members vote, we would like to solicit feedback from the Perl community on the proposal. Review the proposal below and please comment here by December 12th, 2016. The Committee members will start the voting process following that and the conclusion will be announced approximately in one week. Learning Perl 6, a book from O&apos;Reilly Media Name: brian d foy Amount Requested: USD 10,000 Synopsis Partially...</summary>
  20.    <author>
  21.        <name>Makoto Nozaki</name>
  22.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  23.    </author>
  24.    
  25.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  26.    
  27.    
  28.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  29.        <![CDATA[<p>The Grants Committee has received one grant proposal for the November/December round.  Before the Committee members vote, we would like to solicit feedback from the Perl community on the proposal.</p>
  30.  
  31. <p>Review the proposal below and please comment here by December 12th, 2016.  The Committee members will start the voting process following that and the conclusion will be announced approximately in one week.</p>
  32.  
  33. <h1>Learning Perl 6, a book from O'Reilly Media</h1>
  34.  
  35. <ul>
  36. <li><p>Name:</p>
  37.  
  38. <p>brian d foy</p></li>
  39. <li><p>Amount Requested:</p>
  40.  
  41. <p>USD 10,000</p></li>
  42. </ul>
  43.  
  44. <h2>Synopsis</h2>
  45.  
  46. <p>Partially fund the writing process for Learning Perl 6, a book from O'Reilly Media</p>
  47.  
  48. <h2>Benefits to the Perl Community</h2>
  49.  
  50. <p>Note: I am also running a Kickstarter campaign
  51. (<a href="https://www.kickstarter.com/projects/1422827986/learning-perl-6">https://www.kickstarter.com/projects/1422827986/learning-perl-6</a>). I
  52. have not given much thought to the mechanism of The Perl Foundation
  53. funding, but I think I'd want it to be through your normal mechanism
  54. rather than Kickstarter. I understand that payment on completion in
  55. part of that process. That works for me. I would appreciate TPF's help
  56. in spreading the word and finding backers.</p>
  57.  
  58. <p>Perl 6 does not have a tutorial book. To reach further out into the general
  59. programming world, people need a gentle introduction to the language. This
  60. book is about bringing people into the community more than serving the
  61. ones already here.</p>
  62.  
  63. <p>Some people have written survey books that have covered ancient
  64. versions of the language (Perl 6 and Parrot Essentials, Perl 6 Now).
  65. Other people are working on cookbook-style example books (Moritz Lenz
  66. most notably). Several other efforts have stalled or stopped. A book
  67. can be a big chunk of a person's life, and financial stability along with
  68. the removal of the distractions of normal commerce are key to success.</p>
  69.  
  70. <p>The big question is my need for the money, especially when I have a
  71. major publisher committed to publishing the book. In short, I've
  72. shifted O'Reilly risk tolerance by taking on some of it myself.</p>
  73.  
  74. <p>First, book sales aren't what they used to be. I'm taking a big gamble
  75. here and I have a lot of personal risk, mostly in lost time. Many
  76. comments on the kickstarter have centered around "Why doesn't O'Reilly
  77. pay for the book?" Publishers don't "pay" so much as give you advanced
  78. royalties. That robs the future to pay for the present. I've never
  79. taken an advance on a book, and even if I did, a sane publisher
  80. wouldn't provide me enough money to allow me to do this. I fully
  81. expect Learning Perl 6 to be my least-popular book.</p>
  82.  
  83. <p>The entire technology book market shrinking and has been for years.
  84. Perl 6 as a usable language is a new technology in an already crowded
  85. market. There's a big chance that this is a "front list" book that
  86. makes all of its sales in the first months of its release and is never
  87. bought again. This situation happens with a dedicated fan base or a
  88. highly promoted book that doesn't catch on. I already know the sales
  89. numbers for Learning Perl. If I had to guess at a sales target for
  90. Learning Perl 6, I'd take one-tenth that number. It's not a motivating
  91. amount for me. As the author of several existing books, I don't have
  92. the same secondary rewards of new fame and recognition as a first-time
  93. author.</p>
  94.  
  95. <p>Second, book sales aren't primarily important to the marketing
  96. goals of the Perl 6 community. To be taken seriously as a technology
  97. (even if the community is small), someone needs to be able to point to
  98. something in the marketplace. A technology manager might take a
  99. signalling cue from the existence of a dead-tree book because the
  100. publisher has already judged risk and committed to the book. Even if
  101. we think this is a poor way to make judgements (and granted, we'd
  102. often be right), there's the dirty mess of reality versus how we think
  103. the world should be. This is important to many people in the Perl 6
  104. community. The lack of a book is a big hurdle for our "force
  105. multipliers"—the teachers and trainers who don't have the time to
  106. construct a full curriculum themselves but could use a tutorial book
  107. that's ready to teach in a segmented, classroom enviromented.</p>
  108.  
  109. <p>Third, the Kickstarter amount sounds impressive, but I'm also
  110. responsible for all expenses and taxes. Every e-book and print book I
  111. give out as a reward is actually a pre-sale. Most of that money flows
  112. to the publisher as a sale (of which I still get a royalty). The
  113. Kickstarter money is also subject to taxes. I've run a small business
  114. for a couple decades; that number doesn't seem that large for the
  115. effort. I'm looking for any support out there. When you consider the
  116. amount, I think it's much more productive to think about getting what
  117. you want at a price that makes sense to you. Considering the levels
  118. that TPF has funded similar grants delivering less, I think this is
  119. more than reasonable value.</p>
  120.  
  121. <p>If you could get this book without this grant and without the
  122. Kickstarter, I'd support that. Indeed, I've waited for that book just
  123. like you. But, no one has stepped up to write it and that book doesn't
  124. exist. TPF's role could underpin the community support I'm already
  125. receiving. This grant further ensures the end result.</p>
  126. ]]>
  127.        <![CDATA[<h2>Deliverables</h2>
  128.  
  129. <p>The deliverable is a printed O'Reilly Media book. O'Reilly publishes
  130. and promotes the book. I am already under contract with O'Reilly.
  131. Brian Jepson is my editor, and we've developed mock cover art for the
  132. book (meaning, O'Reilly has assigned us an animal).</p>
  133.  
  134. <p>I am running a campaign through Kickstarter to fund this book. Several
  135. of the rewards involve delivery of the book. The folks at O'Reilly
  136. tell me this means I can't have my working sources open as I normally
  137. do because it would violate the Robinson-Patman Act (some customers
  138. get the same product at a lower price). I can, however, allow access
  139. for selected technical reviewers and grant managers.</p>
  140.  
  141. <h2>Project Details</h2>
  142.  
  143. <p>I'm writing a tutorial-style book for beginners. I expect the book to
  144. be about the size and scope of the existing Learning Perl book. I'm
  145. aiming for 300 pages.</p>
  146.  
  147. <p>This is not be definitive or a reference (others are working on
  148. that). This is not the documentation. A tutorial's task is to introduce
  149. the language in steps and uses the least number of concepts along the
  150. way. My goal is to build a solid foundation for understanding the
  151. language both in syntax and philosophy. Documentation explains a tool
  152. but doesn't put it into the context of a task.</p>
  153.  
  154. <p>This book progresses by slowly introducing concepts and giving
  155. readers a chance to practice those. Typically, I explain the fully
  156. expanded form of syntax and work my way to the idiomatic
  157. representation. This technique helps readers understand the implied
  158. parts of the idiomatic form, but also helps them become better readers
  159. of other people's code.</p>
  160.  
  161. <p>Each chapter of the book includes exercises along with explicated
  162. answers. Practice is the key to learning.</p>
  163.  
  164. <h2>Inch-stones</h2>
  165.  
  166. <p>A book project isn't straightforward. There's not a single
  167. path to the result. Often the work is a big soup until it seemingly
  168. miraculously comes together close to the end. The progress in a new
  169. book is more experimental and philosophical than concrete. The initial
  170. effort is usually a big mess, but that's part of the process.</p>
  171.  
  172. <h2>Project Schedule</h2>
  173.  
  174. <p>I have these major milestones specified in the contract for the book:</p>
  175.  
  176. <ul>
  177. <li>Two completed chapters by January</li>
  178. <li>Half the book by May</li>
  179. <li>The whole book by August</li>
  180. </ul>
  181.  
  182. <p>It takes approximately three months for a book to make it through the
  183. O'Reilly publishing process. This includes one round of technical
  184. review, two rounds of copy-editing, an indexer (a live person who
  185. indexes the book), and finally injection into the distribution channels.</p>
  186.  
  187. <p>Additionally, there is a set of people (official technical reviewers
  188. or self-selected backers through a Kickstarter reward) who will
  189. receive monthly drafts of the book. They will be able to provide feedback
  190. and comments, and should be an effective commitment device. They get a PDF
  191. that looks just like an O'Reilly book since it comes out of the continuous
  192. publishing system.</p>
  193.  
  194. <p>As for a more detailed schedule, it's been my experience in publishing
  195. that they are never honest and no one expects them to be true. I could
  196. say that I'd deliver a particular chapter in a particular month, but
  197. later discover that it's more important to work on a different
  198. chapter. Halfway through I typically have a moment of clarity that
  199. makes me go back through everything I've already done to take it in a
  200. different direction.</p>
  201.  
  202. <p>I typically view the schedules as a bit squishy, but I've always been
  203. close.</p>
  204.  
  205. <h2>Completeness Criteria</h2>
  206.  
  207. <p>To be judged complete, my O'Reilly editor, Brian Jepson, certifies
  208. that I've met the conditions imposed by O'Reilly. Once I've done that,
  209. O'Reilly mostly takes over and it's a sure thing.</p>
  210.  
  211. <p>Under the standard author contract, O'Reilly judges the book complete
  212. when they think the content and form of the book are at or above the
  213. level of their usual quality. If it is not (and this have never been a
  214. problem for me), they have the right to ask another author to make
  215. changes to bring it up to their standards.</p>
  216.  
  217. <h2>Bio</h2>
  218.  
  219. <p>I'm brian d foy, the author or co-author of many of the existing
  220. Perl 5 books from O'Reilly Media, including Learning Perl, (Editions 4 to 7),
  221. Intermediate Perl (Editions 1 and 2), Mastering Perl (Editions 1 and 2), and
  222. Programming Perl (4th Edition). I am a U.S. citizen living in the U.S.</p>
  223.  
  224. <p>I've worked extensively in the publishing process, have great tools that
  225. I've already used for my previous books, and have already set up everything
  226. with O'Reilly Media.</p>
  227. ]]>
  228.    </content>
  229. </entry>
  230.  
  231. <entry>
  232.    <title>Metacpan Upgraded</title>
  233.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/11/metacpan-upgraded.html" />
  234.    <id>tag:news.perlfoundation.org,2016://18.3830</id>
  235.  
  236.    <published>2016-11-29T13:08:36Z</published>
  237.    <updated>2016-11-29T13:13:34Z</updated>
  238.  
  239.    <summary>The team that supports meta::cpan had a busy weekend as they completed their long project to upgrade all of the metacpan infrastructure. Thanks to the team for all of their work and to the sponsors who made meta::hack possible. The site looks and performs great!...</summary>
  240.    <author>
  241.        <name>Jim Brandt</name>
  242.        <uri>http://breakingpositive.com</uri>
  243.    </author>
  244.    
  245.        <category term="CPAN" scheme="http://www.sixapart.com/ns/types#category" />
  246.    
  247.    
  248.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  249.        <![CDATA[<p>The team that supports <a href="https://metacpan.org/">meta::cpan</a> had a <a href="http://blogs.perl.org/users/leo_lapworth/2016/11/metahack---metacpan-upgrade.html">busy weekend</a> as they completed their long project to upgrade all of the metacpan infrastructure. Thanks to the team for all of their work and to the sponsors who made <a href="https://metacpan.org/about/meta_hack">meta::hack</a> possible. The site looks and performs great! </p>
  250. ]]>
  251.        
  252.    </content>
  253. </entry>
  254.  
  255. <entry>
  256.    <title>Kickstarter to Support Learning Perl 6 Book</title>
  257.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/11/kickstarter-to-support-learnin.html" />
  258.    <id>tag:news.perlfoundation.org,2016://18.3829</id>
  259.  
  260.    <published>2016-11-25T21:35:12Z</published>
  261.    <updated>2016-11-25T21:46:54Z</updated>
  262.  
  263.    <summary>A huge number of Perl users can trace their initial coding efforts back to O&apos;Reilly&apos;s Learning Perl, now available in its 7th edition. The easy introduction and smooth tour of basic features through more powerful ones made it easy to get started, all with a focus on getting things done. brian d foy, well known in the Perl community and one of the authors of Learning Perl, has launched a Kickstarter campaign to help fund the work to create an...</summary>
  264.    <author>
  265.        <name>Jim Brandt</name>
  266.        <uri>http://breakingpositive.com</uri>
  267.    </author>
  268.    
  269.    
  270.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  271.        <![CDATA[<p>A huge number of Perl users can trace their initial coding efforts back to O'Reilly's <a href="http://shop.oreilly.com/product/0636920049517.do">Learning Perl</a>, now available in its 7th edition. The easy introduction and smooth tour of basic features through more powerful ones made it easy to get started, all with a focus on getting things done.</p>
  272.  
  273. <p>brian d foy, well known in the Perl community and one of the authors of Learning Perl, has launched <a href="https://www.kickstarter.com/projects/1422827986/learning-perl-6?ref=nav_search">a Kickstarter campaign</a> to help fund the work to create an O'Reilly-published Learning Perl 6. Just as Learning Perl made Perl 5 accessible to a wide array of programmers, both professional and casual, Learning Perl 6 will introduce this new language in a fun and accessible way. brian provides some additional detail on <a href="http://blogs.perl.org/users/brian_d_foy/2016/11/kickstart-learning-perl-6.html">his perl blog</a> as well. If you're interested in getting started with Perl 6, help brian fund the book that could get you rolling.</p>
  274. ]]>
  275.        
  276.    </content>
  277. </entry>
  278.  
  279. <entry>
  280.    <title>TPF President Change</title>
  281.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/11/tpf-president-change.html" />
  282.    <id>tag:news.perlfoundation.org,2016://18.3828</id>
  283.  
  284.    <published>2016-11-25T21:11:58Z</published>
  285.    <updated>2016-12-01T15:00:02Z</updated>
  286.  
  287.    <summary>As Mark Keating reported earlier this month, Karen Pauley has stepped down as TPF president after a very successful tenure. Karen served for an amazing 6+ years and did a fantastic job. I&apos;d like to join Mark and many other people in the Perl Community in thanking Karen for all of her work. She has truly set a high bar for the president role. As some might recall, Karen took over from me way back in 2010 and I&apos;m happy...</summary>
  288.    <author>
  289.        <name>Jim Brandt</name>
  290.        <uri>http://breakingpositive.com</uri>
  291.    </author>
  292.    
  293.    
  294.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  295.        <![CDATA[<p>As Mark Keating <a href="http://blogs.perl.org/users/shadowcat_mdk/2016/11/the-times-they-are-a-changin.html">reported</a> earlier this month, Karen Pauley has stepped down as TPF president after a very successful tenure. Karen served for an amazing 6+ years and did a fantastic job. I'd like to join Mark and many other people in the Perl Community in thanking Karen for all of her work. She has truly set a high bar for the president role.</p>
  296.  
  297. <p>As some might recall, Karen took over from me <a href="http://news.perlfoundation.org/2010/03/appointment-of-new-president.html">way back in 2010</a> and I'm happy to swap roles with her again. In addition to continuing all of TPF's major initiatives my primary goal for this year is to get more people involved in The Perl Foundation. Over the last several years, Karen and Dan Wright have done a great job educating the community about what TPF does. I'd like to continue this momentum and take it a step further by letting people know how they can help and getting new people to participate at all levels. Stay tuned to learn about different ways you can help the Perl community.</p>
  298. ]]>
  299.        
  300.    </content>
  301. </entry>
  302.  
  303. <entry>
  304.    <title>Public Beta of blogs.perl.org Rewrite</title>
  305.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/11/public-beta-of-blogsperlorg-re.html" />
  306.    <id>tag:news.perlfoundation.org,2016://18.3827</id>
  307.  
  308.    <published>2016-11-25T07:59:53Z</published>
  309.    <updated>2016-11-25T08:14:12Z</updated>
  310.  
  311.    <summary><![CDATA[Since their third report on migrating blogs.perl.org, Evozon have been working hard to produce a public beta site. This beta site lets you, the community, test and evaluate the platform. If you are a regular user of blogs.perl.org, here's a great opportunity to help us make the release candidate the best version possible. As outlined in the original grant proposal, the site provides the following: features from the exisiting site: register new account, log-in, write &amp; manage blog posts, create...]]></summary>
  312.    <author>
  313.        <name>Tom Hukins</name>
  314.        <uri>http://www.exceptone.co.uk/</uri>
  315.    </author>
  316.    
  317.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  318.    
  319.    
  320.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  321.        <![CDATA[<p>Since their <a href="http://news.perlfoundation.org/2016/03/migrating-blogsperlorg-third-p.html">third report on migrating blogs.perl.org</a>, Evozon have been working hard to produce a <a href="http://blogsperlorg.pearlbee.org/">public beta site</a>.</p>
  322.  
  323. <p>This beta site lets you, the community, test and evaluate the platform.  If you are a
  324. regular user of blogs.perl.org, here's a great opportunity to help us make the release
  325. candidate the best version possible.</p>
  326.  
  327. <p>As outlined in the <a href="http://news.perlfoundation.org/2015/07/grant-proposal-revitalize-blog.html">original grant proposal</a>, the site provides the following:</p>
  328.  
  329. <ul>
  330. <li>features from the exisiting site: register new account, log-in, write &amp; manage blog posts, create &amp; manage blogs, manage user profile, add comments, add &amp; manage users</li>
  331. <li>data imported from the existing site</li>
  332. <li>blog text, code snippets, quoting and comments display in clean UTF-8</li>
  333. <li>admin and test users can log in to their account through direct access</li>
  334. <li>beta users can sign up through Oauth (Facebook login)</li>
  335. <li>existing users can view posts, log in with their existing ID, create and comment on posts</li>
  336. </ul>
  337.  
  338. <p>At this point, the only deficiency known on the platform is its dependency on
  339. JavaScript. Users must have JavaScript enabled in their browsers.</p>
  340.  
  341. <p>This beta system can undergo small updates, due to bug fixing activities performed by the team, and data may be reset from time to time.</p>
  342.  
  343. <p>Please join the beta at <a href="http://blogsperlorg.pearlbee.org">http://blogsperlorg.pearlbee.org</a>.
  344. Once you’ve logged in or signed up, feel free to explore the platform and test all the features.
  345. We strongly encourage all beta users to <a href="https://pearlbee.uservoice.com/">report any bugs, issues, errors or suggestions</a>.
  346. If you are nervous about reporting bugs through the formal bug reporting system, you can simply email details to the support mailing list
  347. <a href="mailto:[email protected]">[email protected]</a>.</p>
  348.  
  349. <p>Enjoy testing the platform and thank you in advance for your feedback.</p>
  350. ]]>
  351.        
  352.    </content>
  353. </entry>
  354.  
  355. <entry>
  356.    <title>Save the Date! The Perl Conference NA 2017</title>
  357.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/11/the-perl-conference-save-date-2017.html" />
  358.    <id>tag:news.perlfoundation.org,2016://18.3826</id>
  359.  
  360.    <published>2016-11-21T14:59:14Z</published>
  361.    <updated>2016-11-21T16:35:38Z</updated>
  362.  
  363.    <summary>Throughout our search we considered and visited venues in Wisconsin, Michigan, Nevada, Florida, Washington D.C., and Virginia. Many people spent countless hours putting out feelers and soliciting bids. In particular, we would like to give a huge thanks to the Brew City Perl Mongers and the Detroit Perl Mongers: their efforts were invaluable in this process, and we hope that we can soon bring The Perl Conference to their fantastic cities. It is with great enthusiasm that we happily announce...</summary>
  364.    <author>
  365.        <name>Todd Rinaldo</name>
  366.        
  367.    </author>
  368.    
  369.    <category term="theperlconference" label="The Perl Conference" scheme="http://www.sixapart.com/ns/types#tag" />
  370.    
  371.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  372.        <![CDATA[<p dir="ltr"><span>Throughout our search we considered and visited venues in Wisconsin, Michigan, Nevada, Florida, Washington D.C., and Virginia. Many people spent countless hours putting out feelers and soliciting bids. In particular, we would like to give a huge thanks to the Brew City Perl Mongers and the Detroit Perl Mongers: their efforts were invaluable in this process, and we hope that we can soon bring The Perl Conference to their fantastic cities.</span></p>
  373. <div dir="ltr"></div>
  374. <p dir="ltr"><span style="text-decoration: underline;"><strong>It is with great enthusiasm that we happily announce The Perl Conference 2017 will be held Sunday, June 18th through Friday, June 23rd at the United States Patent and Trademark Office in Alexandria, Virginia!</strong></span></p>
  375. <div dir="ltr"></div>
  376. <p dir="ltr"><strong>This places us <span style="text-decoration: underline;">immediately</span> outside of Washington, DC, allowing for plenty of sightseeing opportunities!</strong></p>
  377. <div dir="ltr"></div>
  378. <p dir="ltr"><span>The main event will run from Monday, June 19th through Wednesday, June 21st. Master Classes, training, and other activities will be held on the 18th, 22nd, and 23rd. We highly encourage you to attend all days, but especially look forward to seeing you at the main event.</span></p>
  379. <div dir="ltr"></div>
  380. <p dir="ltr"><span>This amazing and unique venue is afforded to us through the tireless efforts of the DC and Baltimore Perl Mongers. Many members of the excellent organizing committee for the annual DC-Baltimore Perl Workshop has joined The Perl Conference organizing committee to make this year’s Perl Conference one of the best.</span></p>
  381. <div dir="ltr"></div>
  382. <p dir="ltr"><span>We’ll be opening the new website, registration, call for talks, etc over the next few months. Please continue to watch your email for future updates.</span></p>
  383. <div dir="ltr"></div>
  384. <div dir="ltr"></div>]]>
  385.        
  386.    </content>
  387. </entry>
  388.  
  389. <entry>
  390.    <title>Grant Report: Test2 Manual</title>
  391.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/11/grant-report-test2-manual-1.html" />
  392.    <id>tag:news.perlfoundation.org,2016://18.3825</id>
  393.  
  394.    <published>2016-11-13T15:34:58Z</published>
  395.    <updated>2016-12-08T14:49:08Z</updated>
  396.  
  397.    <summary>Chad continues working on the Test 2 Manual, with the following news: Introduction to testing with Test2 tutorial: https://github.com/Test-More/Test2-Manual/blob/master/lib/Test2/Manual/Testing/Introduction.pm Tutorial for converting from Test::More to Test2: https://github.com/Test-More/Test2-Manual/blob/master/lib/Test2/Manual/Testing/Migrating.pm...</summary>
  398.    <author>
  399.        <name>Alberto Simões</name>
  400.        <uri>http://blogs.perl.org/users/alberto_simoes/</uri>
  401.    </author>
  402.    
  403.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  404.    
  405.    
  406.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  407.        <![CDATA[<p>Chad continues working on the Test 2 Manual, with the following news:</p>
  408.  
  409. <ul>
  410. <li><p>Introduction to testing with Test2 tutorial: <a href="https://github.com/Test-More/Test2-Manual/blob/master/lib/Test2/Manual/Testing/Introduction.pm">https://github.com/Test-More/Test2-Manual/blob/master/lib/Test2/Manual/Testing/Introduction.pm</a></p></li>
  411. <li><p>Tutorial for converting from Test::More to Test2: <a href="https://github.com/Test-More/Test2-Manual/blob/master/lib/Test2/Manual/Testing/Migrating.pm">https://github.com/Test-More/Test2-Manual/blob/master/lib/Test2/Manual/Testing/Migrating.pm</a></p></li>
  412. </ul>
  413. ]]>
  414.        
  415.    </content>
  416. </entry>
  417.  
  418. <entry>
  419.    <title>Call For Grant Proposals (Nov 2016 Round)</title>
  420.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/11/call-for-grant-proposals-nov-2.html" />
  421.    <id>tag:news.perlfoundation.org,2016://18.3824</id>
  422.  
  423.    <published>2016-11-07T23:00:00Z</published>
  424.    <updated>2016-11-16T07:29:24Z</updated>
  425.  
  426.    <summary>The Grants Committee is accepting grant proposals all the time. We evaluate them every two months and another evaluation period has come. If you have an idea for doing some Perl work that will benefit the Perl community, consider sending a grant application. The application deadline for this round is 23:59 November 25th UTC. We will publish the received applications, get community feedback and conclude acceptance by December 5th. To apply, please read How to Write a Proposal. Rules of...</summary>
  427.    <author>
  428.        <name>Makoto Nozaki</name>
  429.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  430.    </author>
  431.    
  432.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  433.    
  434.    
  435.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  436.        <![CDATA[<p>The Grants Committee is accepting grant proposals all the time.  We evaluate them every two months and another evaluation period has come.</p>
  437.  
  438. <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 25th UTC.</strong> We will publish the received applications, get community feedback and conclude acceptance by December 5th.</p>
  439.  
  440. <p>To apply, please read <a href="http://www.perlfoundation.org/how_to_write_a_proposal">How to Write a Proposal</a>.  <a href="http://www.perlfoundation.org/rules_of_operation">Rules of Operation</a> and <a href="http://www.perlfoundation.org/running_grants">Running Grants List</a> will also help you understand how the grant process works. We also got some <a href="http://www.perlfoundation.org/grant_ideas">grant ideas</a> from the community. The format is the same as the previous rounds in 2014-2016.</p>
  441.  
  442. <p>We will confirm the receipt of application within 24 hours.</p>
  443.  
  444. <p>If you have further questions, please contact me at tpf-grants-secretary at perl-foundation.org.</p>
  445. ]]>
  446.        
  447.    </content>
  448. </entry>
  449.  
  450. <entry>
  451.    <title>Tony Cook&apos;s Grant Extended</title>
  452.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/10/tony-cooks-grant-extended-1.html" />
  453.    <id>tag:news.perlfoundation.org,2016://18.3823</id>
  454.  
  455.    <published>2016-10-28T06:22:29Z</published>
  456.    <updated>2016-11-21T13:55:08Z</updated>
  457.  
  458.    <summary>Tony Cook recently requested an extension of his Maintaining Perl 5 grant. This request was successful and Tony was awarded another $20,000. I would like to thank the community members who took time to comment on this grant extension request and our sponsors who made funding the grant possible through our Perl 5 Core Maintenance Fund....</summary>
  459.    <author>
  460.        <name>Karen Pauley</name>
  461.        <uri>http://martian.org/karen</uri>
  462.    </author>
  463.    
  464.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  465.    
  466.    
  467.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  468.        <![CDATA[<p>Tony Cook recently requested an extension of his <a href="http://news.perlfoundation.org/2013/05/grant-application-maintaining.html">Maintaining Perl 5</a> grant.  This <a href="http://news.perlfoundation.org/2016/09/maintaining-perl-5-grant-exten.html">request</a> was successful and Tony was awarded another $20,000.</p>
  469.  
  470. <p>I would like to thank the community members who took time to comment on this grant extension request and our sponsors who made funding the grant possible through our <a href="http://www.perlfoundation.org/perl_5_core_maintenance_fund">Perl 5 Core Maintenance Fund</a>.</p>
  471. ]]>
  472.        
  473.    </content>
  474. </entry>
  475.  
  476. <entry>
  477.    <title>Update on JavaScript Backend For Rakudo Grant</title>
  478.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/10/update-on-javascript-backend-f.html" />
  479.    <id>tag:news.perlfoundation.org,2016://18.3822</id>
  480.  
  481.    <published>2016-10-28T02:45:16Z</published>
  482.    <updated>2016-11-18T02:54:34Z</updated>
  483.  
  484.    <summary>Paweł Murias continues to work on his JavaScript backend for Rakudo grant. Paweł Murias writes: Current State rakudo.js (Rakudo compiled to JavaScript) compiles 70% of the core setting. I&apos;m working on getting it to compile the whole setting. The setting executes a bunch of code at compile time (it has BEGIN blocks, constant declarators etc.) so the code the compiler is generated is validated to some degree (the test suit will exercise it much more). I&apos;m mostly fixing bugs, and...</summary>
  485.    <author>
  486.        <name>Karen Pauley</name>
  487.        <uri>http://martian.org/karen</uri>
  488.    </author>
  489.    
  490.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  491.    
  492.    <category term="perl6grant" label="perl 6 grant" scheme="http://www.sixapart.com/ns/types#tag" />
  493.    
  494.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  495.        <![CDATA[<p>Paweł Murias continues to work on his <a href="http://news.perlfoundation.org/2016/02/ian-hague-perl-6-grant-applica.html">JavaScript backend for Rakudo</a> grant.</p>
  496.  
  497. <p><em>Paweł Murias writes:</em></p>
  498.  
  499. <p><b>Current State</b></p>
  500.  
  501. <p>rakudo.js (Rakudo compiled to JavaScript) compiles 70% of the core setting. I'm working on getting it to compile the whole setting. The setting executes a bunch of code at compile time (it has <span class="caps">BEGIN </span>blocks, constant declarators etc.) so the code the compiler is generated is validated to some degree (the test suit will exercise it much more). I'm mostly fixing bugs, and implementing missing features in the backend (most are small some required bigger changes to the way we handle things, like nqp::attrinited). While doing that I'm also expanding the nqp test suite so that new backend implementers have an easier job.</p>
  502.  
  503. <p><b>What Is Left?</b></p>
  504.  
  505. <ul>
  506. <li>Fixing bugs and missing features found while running the test suit.</li>
  507. <li>Writing a tutorial and making rakudo.js more usable (making sure the source maps are correct, it installs easily, the error messages it produces are usable etc.).</li>
  508. </ul>
  509.  
  510. <p><b>When it will be done?</b></p>
  511.  
  512. <p>A large part of the work remaining is bug fixing so I find it hard to provide a reliable estimate.  I hope to wrap things up by the end of the year.</p>]]>
  513.        
  514.    </content>
  515. </entry>
  516.  
  517. <entry>
  518.    <title>Grant Report : RPerl User Documentation #2 - Sept/Oct 2016</title>
  519.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/10/grant-report-rperl-user-docume-10.html" />
  520.    <id>tag:news.perlfoundation.org,2016://18.3821</id>
  521.  
  522.    <published>2016-10-23T21:54:22Z</published>
  523.    <updated>2016-11-16T18:39:55Z</updated>
  524.  
  525.    <summary><![CDATA[Will reports on RPerl documentation for September and most of October: "Chapter 3 is coming along nicely! The following new sections of Learning RPerl have been published: Section 3.5: 2-D Array Data Types &amp; Nested Arrays Section 3.6: qw() Operator Section 3.7: Array Assignment Section 3.8: push &amp; pop Operators Section 3.9: shift &amp; unshift Operators Also, more extensive example code has been added to the following sections: CHAPTER 3: ARRAY VALUES &amp; VARIABLES Section 3.1: Lists vs Arrays Section...]]></summary>
  526.    <author>
  527.        <name>Mark A Jensen</name>
  528.        
  529.    </author>
  530.    
  531.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  532.    
  533.    <category term="grantsrperl" label="Grants RPerl" scheme="http://www.sixapart.com/ns/types#tag" />
  534.    
  535.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  536.        <![CDATA[<p>Will reports on RPerl documentation for September and most of October:</p>
  537.  
  538. <p>"Chapter 3 is coming along nicely!</p>
  539.  
  540. <p>The following new sections of Learning RPerl have been published:</p>
  541.  
  542. <ul>
  543.    <li ><a href="http://rperl.org/learning_rperl.html#Section_3.5%3A_2-D_Array_Data_Types_%26_Nested_Arrays"  target="_blank">Section 3.5: 2-D Array Data Types &amp; Nested Arrays</a></li>
  544.    <li ><a href="http://rperl.org/learning_rperl.html#Section_3.6%3A_qw()_Operator"  target="_blank">Section 3.6: qw() Operator</a></li>
  545.    <li ><a href="http://rperl.org/learning_rperl.html#Section_3.7%3A_Array_Assignment"  target="_blank">Section 3.7: Array Assignment</a></li>
  546.    <li ><a href="http://rperl.org/learning_rperl.html#Section_3.8%3A_push_%26_pop_Operators"  target="_blank">Section 3.8: push &amp; pop Operators</a></li>
  547.    <li ><a href="http://rperl.org/learning_rperl.html#Section_3.9%3A_shift_%26_unshift_Operators"  target="_blank">Section 3.9: shift &amp; unshift Operators</a></li>
  548. </ul>
  549.  
  550. <p>Also, more extensive example code has been added to the following sections:</p>
  551.  
  552. <p><a href="http://rperl.org/learning_rperl.html#CHAPTER_3%3A_ARRAY_VALUES_%26_VARIABLES"  target="_blank">CHAPTER 3: ARRAY VALUES &amp; VARIABLES</a>
  553.  <ul >
  554.    <li ><a href="http://rperl.org/learning_rperl.html#Section_3.1%3A_Lists_vs_Arrays"  target="_blank">Section 3.1: Lists vs Arrays</a></li>
  555.    <li ><a href="http://rperl.org/learning_rperl.html#Section_3.2%3A_1-D_Array_Data_Types_%26_Constants"  target="_blank">Section 3.2: 1-D Array Data Types &amp; Constants</a></li>
  556.    <li ><a href="http://rperl.org/learning_rperl.html#Section_3.3%3A_How_To_Access_Array_Elements"  target="_blank">Section 3.3: How To Access Array Elements</a></li>
  557.    <li ><a href="http://rperl.org/learning_rperl.html#Section_3.4%3A_Array_Length_%26_Negative_Indices"  target="_blank">Section 3.4: Array Length &amp; Negative Indices</a></li>
  558. </ul>"</p>
  559.  
  560. <p>MAJ</p>
  561. ]]>
  562.        
  563.    </content>
  564. </entry>
  565.  
  566. <entry>
  567.    <title>Maintaining the Perl 5 Core: Report for Month 36</title>
  568.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/10/maintaining-the-perl-5-core-re-32.html" />
  569.    <id>tag:news.perlfoundation.org,2016://18.3820</id>
  570.  
  571.    <published>2016-10-17T11:35:42Z</published>
  572.    <updated>2016-11-21T13:53:32Z</updated>
  573.  
  574.    <summary>Dave Mitchell writes: I spent last month: eliminating the OP_PUSHRE op, converting OP_SPLIT from being a LISTOP to a PMOP, and making split faster - see v5.25.5-71-gdbdb57e; working on various fuzzer tickets; trying to work out when one should use pad_free(), pad_swipe(), S_op_clear_gv() or just plain SvREFCNT_dec(). I gave up on this for now; picking some quick and low-hanging fruit off my TODO list;...</summary>
  575.    <author>
  576.        <name>Karen Pauley</name>
  577.        <uri>http://martian.org/karen</uri>
  578.    </author>
  579.    
  580.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  581.    
  582.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  583.    
  584.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  585.        <![CDATA[<p><em>Dave Mitchell writes:</em></p>
  586.  
  587. <p>I spent last month:</p>
  588.  
  589. <ul>
  590. <li>eliminating the OP_PUSHRE op, converting OP_SPLIT from being a <span class="caps">LISTOP </span>to a <span class="caps">PMOP, </span>and making split faster - see v5.25.5-71-gdbdb57e;</li>
  591. <li>working on various fuzzer tickets;</li>
  592. <li>trying to work out when one should use pad_free(), pad_swipe(), S_op_clear_gv() or just plain SvREFCNT_dec(). I gave up on this for now;</li>
  593. <li>picking some quick and low-hanging fruit off my <span class="caps">TODO </span>list;</li>
  594. </ul>]]>
  595.        <![CDATA[<p><b>Summary</b></p>
  596.  
  597. <blockquote><p>3:52 [perl #125792] [2 <span class="caps">PATCHES</span>] sassign is wrongly declared as <span class="caps">BASEOP</span><br />
  598. 1:24 [perl #128998] heap-buffer-overflow Perl_my_atof2<br />
  599. 7:47 [perl #129086] heap-use-after-free Perl_localize<br />
  600. 4:30 [perl #129099] global-buffer-overflow S_finalize_op<br />
  601. 1:45 [perl #129158] null ptr deref, segfault in Perl_pp_split ()<br />
  602. 0:56 [perl #129238] array index constant folding uses signed bitwise arithmetic<br />
  603. 0:31 [perl #129239] <span class="caps">BEGIN </span>blocks have wrong caller package<br />
  604. 0:35 [perl #129251]<br />
  605. 14:53 make OP_SPLIT a <span class="caps">PMOP </span>and eliminate OP_PUSHRE<br />
  606. 14:12 miscellaneous fixups<br />
  607. 13:03 pad_free and pad_swipe<br />
  608. 2:55 process p5p mailbox</p></blockquote>
  609.  
  610. <p><b>66:23 Total (HH::MM)</b></p>
  611.  
  612. <blockquote><p>154.7 weeks<br />
  613. 2107.4 total hours<br />
  614. 13.6 average hours per week</p></blockquote>
  615.  
  616. <p>There are 293 hours left on the grant</p>]]>
  617.    </content>
  618. </entry>
  619.  
  620. <entry>
  621.    <title>Maintaining Perl 5: Grant Report for August 2016</title>
  622.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/10/maintaining-perl-5-grant-repor-33.html" />
  623.    <id>tag:news.perlfoundation.org,2016://18.3819</id>
  624.  
  625.    <published>2016-10-11T03:21:44Z</published>
  626.    <updated>2016-11-26T12:09:21Z</updated>
  627.  
  628.    <summary>Tony Cook writes: Approximately 42 tickets were reviewed, and 6 patches were applied. HoursActivity0.93%zu on HP-UX issue3.22#123981 updates, testing, comment5.19#126482 debugging#126482 bisect, review changes#126482 more debugging, comment12.51#127663 more tests, code review#127663 re-work, testing...</summary>
  629.    <author>
  630.        <name>Karen Pauley</name>
  631.        <uri>http://martian.org/karen</uri>
  632.    </author>
  633.    
  634.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  635.    
  636.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  637.    
  638.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  639.        <![CDATA[<p><em>Tony Cook writes:</em></p>
  640.  
  641. <p>Approximately 42 tickets were reviewed, and 6 patches were applied.</p>
  642.  
  643. <table><tr><td>Hours</td><td>Activity</td></tr><tr><td>0.93</td><td>%zu on HP-UX issue</td></tr><tr><td>3.22</td><td>#123981 updates, testing, comment</td></tr><tr><td>5.19</td><td>#126482 debugging</td></tr><tr><td></td><td>#126482 bisect, review changes</td></tr><tr><td></td><td>#126482 more debugging, comment</td></tr><tr><td>12.51</td><td>#127663 more tests, code review</td></tr><tr><td></td><td>#127663 re-work, testing</td></tr></table>]]>
  644.        <![CDATA[<table><tr><td></td><td>#127663 delete on abort, testing</td></tr><tr><td></td><td>#127663 remove some later work, testing</td></tr><tr><td></td><td>#127663 polish, testing</td></tr><tr><td></td><td>#127663 review, push to smoke-me</td></tr><tr><td></td><td>#127663 code review, testing, setup for 128954 testing</td></tr><tr><td>0.60</td><td>#127810 review discussion, brief comment</td></tr><tr><td>1.35</td><td>#127834 (sec) review follow-ups to upstream patches</td></tr><tr><td>1.95</td><td>#128095 upstream ticket #116819 with patch</td></tr><tr><td></td><td>#128095 produce alternative patch</td></tr><tr><td>2.87</td><td>#128263 debugging, testing, work on fix</td></tr><tr><td></td><td>#128263 more work on fix, write tests, comment with patch</td></tr><tr><td>0.83</td><td>#128574 testing, apply to blead</td></tr><tr><td>2.49</td><td>#128598 review discussion, produce patch, testing and comment</td></tr><tr><td></td><td>#128598 review new discussion, comment</td></tr><tr><td>1.30</td><td>#128685 try aristotle's code cross platform</td></tr><tr><td></td><td>#128685 more testing, apply to blead</td></tr><tr><td>0.58</td><td>#128740 testing, research and comment</td></tr><tr><td>0.05</td><td>#128767 reject</td></tr><tr><td>0.73</td><td>#128775 testing, review changes, review cpan changes, comment</td></tr><tr><td>0.12</td><td>#128829 (sec) , #128845 review discussion</td></tr><tr><td>1.30</td><td>#128843 debugging, review S_hextract, research</td></tr><tr><td></td><td>#128843 more research, comment</td></tr><tr><td>0.30</td><td>#128856 review and comment</td></tr><tr><td>0.55</td><td>#128865 research and comment</td></tr><tr><td>0.08</td><td>#128877 (sec) reject (CPAN upstream)</td></tr><tr><td>2.58</td><td>#128930 review patch</td></tr><tr><td></td><td>#128930 testing, find it was applied and close</td></tr><tr><td></td><td>#128930 testing, apply to blead</td></tr><tr><td>1.55</td><td>#128951 debugging</td></tr><tr><td>2.07</td><td>#128953 review, attempt to apply, comment</td></tr><tr><td></td><td>#128953 manually apply rejected chunks, apply to blead</td></tr><tr><td>1.60</td><td>#128954 review, prep for testing (or try)</td></tr><tr><td></td><td>#128954 porting tests, apply to blead</td></tr><tr><td>0.23</td><td>#128972 review, research, comment</td></tr><tr><td>2.24</td><td>#128988 (sec) diagnose, work on a fix, testing</td></tr><tr><td></td><td>#128988 (sec) comment with patch</td></tr><tr><td>0.22</td><td>#128996 (sec) simplify test code, comment</td></tr><tr><td>1.35</td><td>#128997 (sec) simplify, comments</td></tr><tr><td>3.50</td><td>#128998 (sec) debugging, work up a fix and comment</td></tr><tr><td></td><td>#128998 (sec) try to work up a test some more, comment</td></tr><tr><td>0.30</td><td>#129000 (sec) minify test case and comment</td></tr><tr><td>2.60</td><td>#129012 (sec) check older versions, debugging</td></tr><tr><td></td><td>#129012 (sec) debugging, comment</td></tr><tr><td>1.52</td><td>#129021 (sec) diagnose, make a fix, try to work up a test</td></tr><tr><td></td><td>#129021 (sec) work up a test, comment with patch</td></tr><tr><td>1.10</td><td>#129024 (sec) reproduce with valgrind, reduce test case</td></tr><tr><td></td><td>and comment</td></tr><tr><td>0.63</td><td>#129029 build library, reproduce, reduce -D flags, test</td></tr><tr><td></td><td>with valgrind, comment</td></tr><tr><td>0.43</td><td>#129068 debugging</td></tr><tr><td>0.90</td><td>#129069 comment</td></tr><tr><td></td><td>#129069 review new patch, testing, apply to blead</td></tr><tr><td>3.90</td><td>#129085 (sec) reproduce, debugging</td></tr><tr><td></td><td>#129085 (sec) work on fix, testing, comment with patch</td></tr><tr><td></td><td>#129085 (sec) comment</td></tr><tr><td>0.88</td><td>#129086 (sec) debugging, work up a fix</td></tr><tr><td>0.18</td><td>#129117 (sec) comment and reject</td></tr><tr><td>0.83</td><td>#129125 (sec) minify, diagnose and comment</td></tr><tr><td>0.97</td><td>alignment query, research, comment</td></tr><tr><td>1.70</td><td>cygwin failures, seems to be more <span class="caps">BLODA </span>in win 10 anniversary</td></tr><tr><td>0.13</td><td>khw irc discussion on non-interpreter global frees</td></tr></table>
  645.  
  646. <p><b>68.36 Hours Total</b></p>]]>
  647.    </content>
  648. </entry>
  649.  
  650. <entry>
  651.    <title>Grant Report: Test2 Manual</title>
  652.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/10/grant-report-test2-manual.html" />
  653.    <id>tag:news.perlfoundation.org,2016://18.3818</id>
  654.  
  655.    <published>2016-10-09T12:36:06Z</published>
  656.    <updated>2016-11-17T07:01:48Z</updated>
  657.  
  658.    <summary>In the last two months, Chad Granum has been working on his grant. The latest news are described below: started to write about bundles, and realized there was a major shortcoming, so he has been improving Importer.pm to make writing bundles easier. wrote additional documentation for writing comparison objects for Test2::Compare, that will also present in the manual. Test2::Manual::EndToEnd was finished, in the sense that it includes everything Chad planned. It still needs some editing for grammar and errors correction,...</summary>
  659.    <author>
  660.        <name>Alberto Simões</name>
  661.        <uri>http://blogs.perl.org/users/alberto_simoes/</uri>
  662.    </author>
  663.    
  664.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  665.    
  666.    
  667.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  668.        <![CDATA[<p>In the last two months, Chad Granum has been working on his grant.
  669. The latest news are described below:</p>
  670.  
  671. <ul>
  672. <li>started to write about bundles, and realized there was a major
  673. shortcoming, so he has been improving Importer.pm to make writing
  674. bundles easier.</li>
  675. <li>wrote additional documentation for writing comparison objects for
  676. Test2::Compare, that will also present in the manual.</li>
  677. <li><a href="https://github.com/Test-More/Test2-Manual/blob/master/lib/Test2/Manual/EndToEnd.md">Test2::Manual::EndToEnd</a>
  678. was finished, in the sense that it includes
  679. everything Chad planned. It still needs some editing for grammar and errors
  680. correction, and probably some enhancements. But it is mostly complete, and
  681. comprises the most useful part for anyone who wants to work with Test2.</li>
  682. </ul>
  683. ]]>
  684.        
  685.    </content>
  686. </entry>
  687.  
  688. <entry>
  689.    <title>Maintaining the Perl 5 Core: Report for Month 35</title>
  690.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/09/maintaining-the-perl-5-core-re-31.html" />
  691.    <id>tag:news.perlfoundation.org,2016://18.3817</id>
  692.  
  693.    <published>2016-09-28T06:19:17Z</published>
  694.    <updated>2016-11-08T04:22:34Z</updated>
  695.  
  696.    <summary>Dave Mitchell writes: I spent last month mainly working on &quot;fuzzer&quot; bug reports. Nothing really stands out as deserving special mention. Summary 1:23 &quot;Confused by eval behavior&quot; thread 0:14 perl #128940 &quot;Use of uninitialized value $fh&quot; mentions wrong variable 2:48 perl #128951 heap-buffer-overflow in Perl_sv_vcatpvfn_flags 0:51 perl #128952 stack-buffer-overflow in S_missingterm 1:41 perl #128989 Bleadperl v5.25.3-266-g1d7e644 breaks VPIT/Variable-Magic-0.59.tar.gz 4:46 perl #129012 heap-buffer-overflow Perl_fbm_instr 2:04 perl #129029 SIGBUS Perl_sv_peek 0:24 perl #129038 Assertion Failure: *Perl_pp_subst *pp_hot.c:3203 3:45 perl #129064 heap-buffer-overflow S_scan_heredoc...</summary>
  697.    <author>
  698.        <name>Karen Pauley</name>
  699.        <uri>http://martian.org/karen</uri>
  700.    </author>
  701.    
  702.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  703.    
  704.    <category term="perl5coremaintenance" label="perl5 core maintenance" scheme="http://www.sixapart.com/ns/types#tag" />
  705.    
  706.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  707.        <![CDATA[<p><em>Dave Mitchell writes:</em></p>
  708.  
  709. <p>I spent last month mainly working on "fuzzer" bug reports. Nothing really stands out as deserving special mention.</p>
  710.  
  711. <p><b>Summary</b></p>
  712.  
  713. <blockquote><p>1:23 "Confused by eval behavior" thread<br />
  714. 0:14 <a href="https://rt.perl.org/Public/Bug/Display.html?id=128940">perl #128940</a> "Use of uninitialized value $fh" mentions wrong variable<br />
  715. 2:48 <a href="https://rt.perl.org/Public/Bug/Display.html?id=128951">perl #128951</a> heap-buffer-overflow in Perl_sv_vcatpvfn_flags<br />
  716. 0:51 <a href="https://rt.perl.org/Public/Bug/Display.html?id=128952">perl #128952</a> stack-buffer-overflow in S_missingterm<br />
  717. 1:41 <a href="https://rt.perl.org/Public/Bug/Display.html?id=128989">perl #128989</a> Bleadperl v5.25.3-266-g1d7e644 breaks <span class="caps">VPIT</span>/Variable-Magic-0.59.tar.gz<br />
  718. 4:46 perl #129012 heap-buffer-overflow Perl_fbm_instr<br />
  719. 2:04 <a href="https://rt.perl.org/Public/Bug/Display.html?id=129029">perl #129029</a> <span class="caps">SIGBUS</span> Perl_sv_peek<br />
  720. 0:24 <a href="https://rt.perl.org/Public/Bug/Display.html?id=129038">perl #129038</a> Assertion Failure: *Perl_pp_subst *pp_hot.c:3203<br />
  721. 3:45 <a href="https://rt.perl.org/Public/Bug/Display.html?id=129064">perl #129064</a> heap-buffer-overflow S_scan_heredoc<br />
  722. 5:01 <a href="https://rt.perl.org/Public/Bug/Display.html?id=129099">perl #129099</a> global-buffer-overflow S_finalize_op<br />
  723. 4:02 <a href="https://rt.perl.org/Public/Bug/Display.html?id=27555">perl #27555</a> <span class="caps">TIED </span>$x = \$y{z}; delete $y{z} -- behaves badly<br />
  724. 4:10 <a href="https://rt.perl.org/Public/Bug/Display.html?id=39358">perl #39358</a> sort segfaults<br />
  725. 1:28 fix Concise hints high bits display<br />
  726. 0:48 fix build warnings and smoke failures<br />
  727. 4:42 optimise av_fetch()<br />
  728. 4:30 optimise leave_scope()<br />
  729. 9:44 process p5p mailbox</p></blockquote>
  730.  
  731. <p><b>52:21 Total (HH::MM)</b></p>
  732.  
  733. <p>As of 2016/08/31: since the beginning of the grant:</p>
  734.  
  735. <blockquote><p>150.4 weeks<br />
  736. 2041.0 total hours<br />
  737. 13.6 average hours per week</p></blockquote>
  738.  
  739. <p>There are 359 hours left on the grant</p>]]>
  740.        
  741.    </content>
  742. </entry>
  743.  
  744. </feed>
  745.  

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

  1. Download the "valid Atom 1.0" banner.

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

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

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

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

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