Congratulations!

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

Recommendations

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

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

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <feed xmlns="http://www.w3.org/2005/Atom">
  3.    <title>The Perl Foundation</title>
  4.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/" />
  5.    <link rel="self" type="application/atom+xml" href="http://news.perlfoundation.org/atom.xml" />
  6.    <id>tag:news.perlfoundation.org,2010-03-22://18</id>
  7.    <updated>2017-01-23T00:22:37Z</updated>
  8.    
  9.    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 6.2.2</generator>
  10.  
  11. <entry>
  12.    <title>Grant Report : RPerl User Documentation #2 - Dec 2016</title>
  13.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/grant-report-rperl-user-docume-12.html" />
  14.    <id>tag:news.perlfoundation.org,2017://18.3844</id>
  15.  
  16.    <published>2017-01-23T00:06:46Z</published>
  17.    <updated>2017-01-23T00:22:37Z</updated>
  18.  
  19.    <summary>Will Braswell reports that he has completed the deliverables for RPerl Docs #2: &quot;Lots of big news for RPerl! First, Christmas saw the release of the new Perl-powered platform CloudForFree.org ;v1.0, codename Nimbostratus. Secondly, on New Years Day we released RPerl v2.4, codename Aurora. And last but not least, we are proud to announce the publication of Learning RPerl chapter 4, thereby completing part 2 of the TPF grant! Over 160 pages of brand new material has been written under...</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="grants" label="grants" scheme="http://www.sixapart.com/ns/types#tag" />
  28.    <category term="rperl" label="RPerl" scheme="http://www.sixapart.com/ns/types#tag" />
  29.    
  30.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  31.        <![CDATA[<p>Will Braswell reports that he has completed the deliverables for
  32. <a href="http://news.perlfoundation.org/2016/02/grant-proposal-rperl-user-docu-1.html">RPerl Docs #2</a>:</p>
  33.  
  34. <p>"Lots of big news for RPerl!
  35. First, Christmas saw the release of the new Perl-powered platform <a href="http://CloudForFree.org">CloudForFree.org</a> ;v1.0, codename Nimbostratus.
  36. Secondly, on New Years Day we released <a href="https://metacpan.org/release/WBRASWELL/RPerl-2.410000">RPerl v2.4</a>, codename Aurora.
  37. And last but not least, we are proud to announce the publication of Learning RPerl chapter 4, thereby completing part 2 of the TPF grant!
  38. Over 160 pages of brand new material has been written under this grant for chapters 2, 3, and 4 of Learning RPerl.</p>
  39.  
  40. <p><a href="http://rperl.org/learning_rperl.html#CHAPTER_4%3A_ORGANIZING_BY_SUBROUTINES" >CHAPTER 4: ORGANIZING BY SUBROUTINES</a><span ></span><ul ><li ><a href="http://rperl.org/learning_rperl.html#Section_4.1%3A_Subroutine_Definitions" >Section 4.1: Subroutine Definitions</a></li><li ><a href="http://rperl.org/learning_rperl.html#Section_4.2%3A_Subroutine_Calls" >Section 4.2: Subroutine Calls</a><ul ><li ><a href="http://rperl.org/learning_rperl.html#Section_4.2.1%3A_Parentheses_Suffix_%26_Ampersand_Sigil_Prefix" >Section 4.2.1: Parentheses Suffix &amp; Ampersand Sigil Prefix</a></li></ul></li><li ><a href="http://rperl.org/learning_rperl.html#Section_4.3%3A_Subroutine_Return_Values" >Section 4.3: Subroutine Return Values</a><ul ><li ><a href="http://rperl.org/learning_rperl.html#Section_4.3.1%3A_return_Operator" >Section 4.3.1: return Operator</a></li><li ><a href="http://rperl.org/learning_rperl.html#Section_4.3.2%3A_Multiple_Return_Values" >Section 4.3.2: Multiple Return Values</a></li></ul></li><li ><a href="http://rperl.org/learning_rperl.html#Section_4.4%3A_Subroutine_Arguments" >Section 4.4: Subroutine Arguments</a><ul ><li ><a href="http://rperl.org/learning_rperl.html#Section_4.4.1%3A_Variadic_Subroutines" >Section 4.4.1: Variadic Subroutines</a></li></ul></li><li ><a href="http://rperl.org/learning_rperl.html#Section_4.5%3A_Subroutine_Variables%2C_Variable_Scope_%26_Persistence" >Section 4.5: Subroutine Variables, Variable Scope &amp; Persistence</a><ul ><li ><a href="http://rperl.org/learning_rperl.html#Section_4.5.1%3A_my_Intermittent_Variables" >Section 4.5.1: my Intermittent Variables</a></li></ul></li><li ><a href="http://rperl.org/learning_rperl.html#Section_4.6%3A_use_strict%3B_use_warnings%3B_Pragmas_%26_Magic" >Section 4.6: use strict; use warnings; Pragmas &amp; Magic</a></li><li ><a href="http://rperl.org/learning_rperl.html#Section_4.7%3A_Exercises" >Section 4.7: Exercises</a><ul ><li ><a href="http://rperl.org/learning_rperl.html#1._Subroutine_To_Calculate_Total_Of_Numeric_Array_Elements_%5B_45_mins_%5D" >1. Subroutine To Calculate Total Of Numeric Array Elements [ 45 mins ]</a></li><li ><a href="http://rperl.org/learning_rperl.html#2._Subroutine_To_Calculate_Total_Of_Numbers_1_Through_1_000_%5B_15_mins_%5D" >2. Subroutine To Calculate Total Of Numbers 1 Through 1_000 [ 15 mins ]</a></li><li ><a href="http://rperl.org/learning_rperl.html#3._Subroutine_To_Find_Above-Average_Array_Elements_%5B_45_mins_%5D" >3. Subroutine To Find Above-Average Array Elements [ 45 mins ]</a></li><li ><a href="http://rperl.org/learning_rperl.html#4._Subroutine_To_Greet_User_%26_Store_Program_State_%5B_30_mins_%5D" >4. Subroutine To Greet User &amp; Store Program State [ 30 mins ]</a></li><li ><a href="http://rperl.org/learning_rperl.html#5._Subroutine_To_Greet_User_%26_Store_More_Program_State_%5B_35_mins_%5D" >5. Subroutine To Greet User &amp; Store More Program State [ 35 mins ]</a></li></ul></li></ul>
  41. What's next for RPerl?  ;What other exciting new advancements are coming down the pike?
  42. Stay tuned to <a href="http://RPerl.org">RPerl.org</a> and find out!"</p>
  43.  
  44. <p>MAJ</p>
  45. ]]>
  46.        
  47.    </content>
  48. </entry>
  49.  
  50. <entry>
  51.    <title>Grant Proposal: Standardization, Test Coverage, and Documentation of Perl 6 I/O Routines</title>
  52.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/grant-proposal-standardization.html" />
  53.    <id>tag:news.perlfoundation.org,2017://18.3843</id>
  54.  
  55.    <published>2017-01-17T15:00:00Z</published>
  56.    <updated>2017-01-17T19:30:37Z</updated>
  57.  
  58.    <summary>The Grants Committee has received one grant proposal Standardization, Test Coverage, and Documentation of Perl 6 I/O Routines for the January 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 January 23rd, 2017. The Committee members will start the voting process following that and the conclusion will be announced approximately in one week. Standardization, Test Coverage, and Documentation of Perl 6...</summary>
  59.    <author>
  60.        <name>Makoto Nozaki</name>
  61.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  62.    </author>
  63.    
  64.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  65.    
  66.    
  67.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  68.        <![CDATA[<p>The Grants Committee has received one grant proposal <strong>Standardization, Test Coverage, and Documentation of Perl 6 I/O Routines</strong> for the January round.  Before the Committee members vote, we would like to solicit feedback from the Perl community on the proposal.</p>
  69.  
  70. <p>Review the proposal below and please comment here by January 23rd, 2017.  The Committee members will start the voting process following that and the conclusion will be announced approximately in one week.</p>
  71.  
  72. <h1>Standardization, Test Coverage, and Documentation of Perl 6 I/O Routines</h1>
  73.  
  74. <ul>
  75. <li><p>Name:</p>
  76.  
  77. <p>Zoffix Znet (legal name: Pete Evstratov)</p></li>
  78. <li><p>Amount Requested:</p>
  79.  
  80. <p>USD 999</p></li>
  81. </ul>
  82.  
  83. <h2>Synopsis</h2>
  84.  
  85. <p>Many of Perl 6's I/O routines currently have inconsistencies in behaviour
  86. between method and subroutine forms along with inconsistencies in calling
  87. forms and failure modes compared to the rest of the language. Also some of
  88. them, despite being speculated in the synopses and implemented in Rakudo, have
  89. no test coverage in the Perl 6 Specification, and as such they remain
  90. undocumented and not part of the Perl 6 Language. Some of the routines that do
  91. have presence in the Specification, have sparse test coverage, leaving
  92. some of their functionality entirely untested.</p>
  93.  
  94. <p>The work funded by this grant seeks to resolve those inconsistencies, as well
  95. as provide full test coverage and documentation.</p>
  96.  
  97. <h2>Benefits to the Perl Community</h2>
  98.  
  99. <p>Inconsistent interfaces are difficult to master and are bug-prone due to
  100. programmers forgetting about varying details of individual routines. By making
  101. I/O routines take arguments and indicate failures consistent to the way it's
  102. done in the rest of the language, they will be much easier for programmers to
  103. learn and use. Along with a more pleasant interface, the Perl Community will
  104. also benefit by needing to provide less support for people trying to learn the
  105. language.</p>
  106.  
  107. <p>The largest benefit will come from the full test coverage that will no doubt
  108. reveal bugs that can be fixed before they're encountered by users in
  109. production code. The coverage will also protect from future bugs being
  110. introduced inadvertently. Also, the currently unspecced routines will be
  111. officially part of the language, and so will be documented and available for
  112. use.</p>
  113.  
  114. <h3><strong>As bonus benefits:</strong></h3>
  115.  
  116. <p>The timing of this work seeks to align with the production of "Learning Perl 6"
  117. book, in order for it to contain valid information on I/O routines and
  118. describe only routines that are actually part of the language, which will
  119. avoid confusion for its readers and folks helping those readers learn Perl 6.</p>
  120.  
  121. <p>Lastly, the bonus deliverables (described below) will benefit further
  122. development of Rakudo/Perl 6 by elucidating unspecced, unused, or unwanted
  123. routines. The data can also be used to produce a teaching/reference aid
  124. (e.g. flash cards with routine names or IRC bot for routine reference).</p>
  125. ]]>
  126.        <![CDATA[<h2>Deliverables</h2>
  127.  
  128. <p><strong>Scope:</strong> by <em>I/O routines</em> this grant proposal means subroutines and
  129. methods of the <a href="https://github.com/rakudo/rakudo/">Rakudo implementation</a>
  130. found in <code>src/core/io_operators.pm</code>,
  131. <code>src/core/IO.pm</code>, <code>src/core/IO/ArgFiles.pm</code>, <code>src/core/IO/Handle.pm</code>,
  132. <code>src/core/IO/Notification.pm</code>, <code>src/core/IO/Path.pm</code>, <code>src/core/IO/Pipe.pm</code>,
  133. <code>src/core/IO/Special.pm</code>, and <code>src/core/IO/Spec.pm</code> as well as its
  134. subclasses found in <code>src/core/IO/Spec/</code> directory. Note that <code>IO::Socket</code> and
  135. its subclasses are NOT in the scope of this grant proposal.</p>
  136.  
  137. <p>Deliverables:</p>
  138.  
  139. <ul>
  140. <li>I/O Action Plan Report</li>
  141. <li>Commits in <a href="https://github.com/rakudo/rakudo/">rakudo</a> implementing
  142. the Action Plan.</li>
  143. <li>Commits in <a href="https://github.com/perl6/roast">Perl 6 Specification</a>
  144. providing full coverage for I/O routines.</li>
  145. <li>Commits in <a href="https://github.com/perl6/doc">Perl 6 Documentation</a>
  146. providing full coverage for undocumented I/O routines, as well as any
  147. corrections for existing I/O documentation.</li>
  148. <li>Bonus deliverable: The "Map" of Rakudo Routines</li>
  149. <li>Bonus objective: whenever possible, I intend to fix any of the bugs
  150. found by the new test coverage. Should a bug prove to be hard to fix,
  151. the test exposing it will be fudged and a ticket for the bug will be filed.</li>
  152. </ul>
  153.  
  154. <h2>Project Details</h2>
  155.  
  156. <ul>
  157. <li>(Bonus deliverable): <strong>The "Map" of Rakudo Routines</strong>
  158. This will be semi-automatically generated (by introspection) list of all
  159. subroutines and publicly accessible object methods provided by Rakudo
  160. implementation, together with information on what calling convention they
  161. use and how they fail (e.g. returning some object, throwing, or returning
  162. a <code>Failure</code> object). This data will guide the decision on how the calling convetion/failure mode for I/O routines should be standardized. I intend
  163. to work on this deliverable while this grant proposal is deliberated. As
  164. such, it's a bonus deliverable and will be completed regardless of whether
  165. this grant is approved.</li>
  166. <li><strong>I/O Action Plan Report</strong>
  167. This will be a Markdown document detailing how the existing routines will
  168. change, what the new routines will do, if any are to be added, and whether
  169. any currently unspecced routines are to be removed. Parts of this document
  170. will eventually be re-used as documention for currently undocumented
  171. routines.
  172. <ul>
  173. <li>The scope of all of the changes will be limited by the <em>6.c</em> Perl 6
  174. language specification, so none of the changes would have to be deferred
  175. until <em>6.d</em> language release.</li>
  176. <li>This document will be placed into
  177. <a href="https://github.com/rakudo/rakudo/">rakudo</a> repository when ready and
  178. other core developers will be asked to reivew it and make comments on the
  179. proposed changes.</li>
  180. </ul></li>
  181. <li><strong>Commits</strong>
  182. The commits to rakudo/roast/doc repositories will implement changes in
  183. the Action Plan, and test and document any I/O routines that are still
  184. left untested/undocumented after those changes.</li>
  185. </ul>
  186.  
  187. <h2>Inch-stones</h2>
  188.  
  189. <p>These are the inch-stones I intend to follow:</p>
  190.  
  191. <h3>Routine Map</h3>
  192.  
  193. <ul>
  194. <li>Use Perl 6's introspection facilities to locate core subroutines and
  195. classes in <code>CORE::</code> lexical scope. Further introspect those classes to obtain
  196. <code>Method</code> objects. Further introspect the candidates and signatures of all of
  197. these routines to obtain the calling convention list (e.g. we pass arguments
  198. as adverbs or as positionals, etc)</li>
  199. <li>Further introspect the arguments and programmatically invoke the
  200. routines with some probably-acceptable values to obtain the output range, in
  201. particular failure modes. Some heuristics or manual massaging will be needed
  202. here.</li>
  203. <li>Part of this work already exists in <a href="https://github.com/zoffixznet/perl6-map">a repo</a>. If the grant is approved, this repository will be
  204. transfered to <a href="https://github.com/perl6/">Perl 6 GitHub organization</a></li>
  205. </ul>
  206.  
  207. <h3>I/O Action Plan Report</h3>
  208.  
  209. <ul>
  210. <li>Using the routine map, figure out a better interface for I/O routines
  211. and then see what can be changed without breaking the 6.c language spec. Even
  212. without that map, I already can see some targets for change: the routines that
  213. take <code>$test</code> named arg as a predefined string of test letters in particular
  214. order, as well as the inconsistency that most methods <code>fail()</code> while most
  215. subroutines <code>throw()</code>. Based on a brief <a href="https://irclog.perlgeek.de/perl6-dev/2016-12-28#i_13814034">conversation with
  216. Larry Wall</a>, the
  217. likely change would be to make all of them consistently <code>fail()</code>.</li>
  218. <li>Inspect the <a href="https://github.com/rakudo/rakudo/compare/6bbb56f4c598ba0fef49ba9b11671df675019366...newio">code of NewIO branch</a>
  219. for any ideas that can be salvaged for 6.c Language. The work in this branch
  220. was created by lizmat++ in 2014-2015, but due to unfortunate circumstances
  221. never got merged to master prior to 6.c release. My understanding is it offers
  222. a lot of improvements to our current IO, but based on brief perusal of the
  223. code, I suspect it would have a lot of conflict with 6.c Language
  224. Specification tests. Under this grant, I would like to see if any of the
  225. improvements that work offers can be applied to current 6.c language.</li>
  226. <li>Using the <a href="http://perl6.party/post/Perl-6-Core-Hacking-Can-Has-Moar-Cover">MoarVM coverage report
  227. tool</a> (and by
  228. grepping the <a href="https://github.com/perl6/roast/">roast repo</a>), find
  229. routines that are entirely unspecced and decide whether they
  230. should stay or be removed. For example, the currently unspecced <code>indir()</code>
  231. routine is a likely candidate for staying, while I've seen some calls on IRC
  232. to remove the unspecced <code>tmpdir()</code>.</li>
  233. <li>I forcee the largest part of this grant work to be the writing of
  234. the tests. Here are some examples of the rough current coverage state of IO
  235. routines:
  236. <a href="http://perl6.wtf/src_core_io_operators.pm.coverage.html">src/core/io_operators.pm</a>,
  237. <a href="http://perl6.wtf/src_core_IO_ArgFiles.pm.coverage.html">IO::Argfiles</a>,
  238. <a href="http://perl6.wtf/src_core_IO_Special.pm.coverage.html">IO::Special</a>,
  239. <a href="http://perl6.wtf/src_core_IO_Spec_Win32.pm.coverage.html">IO::Spec::Win32</a>,
  240. and <a href="http://perl6.wtf/src_core_IO_Handle.pm.coverage.html">IO::Handle</a>. The
  241. routines whose names are on red lines indicate they're untested in roast
  242. (this report was generated on Oct 7 and as I recall only IO::ArgFiles.lines and
  243. IO::Handle.seek received any further tests since then).</li>
  244. <li>A lot of the decisions made by the Action Plan will be able to close
  245. many of the tickets opened by <em>brian d foy</em> while gathering info on our
  246. I/O routines that is going to be included in <em>Learning Perl 6</em> book and the
  247. concerns raised in the tickets will be used as input for the Action Plan as
  248. well. (Some of them are:
  249. <a href="https://rt.perl.org/Public/Bug/Display.html?id=130460">RT#130460</a>,
  250. <a href="https://rt.perl.org/Public/Bug/Display.html?id=130456">RT#130456</a>,
  251. <a href="https://rt.perl.org/Public/Bug/Display.html?id=130454">RT#130454</a>,
  252. <a href="https://rt.perl.org/Public/Bug/Display.html?id=130455">RT#130455</a>,
  253. <a href="https://rt.perl.org/Public/Bug/Display.html?id=130489">RT#130489</a>,
  254. <a href="https://rt.perl.org/Public/Bug/Display.html?id=130490">RT#130490</a>).</li>
  255. <li>Write down the action plan in Markdown format, make it available
  256. in Rakudo repository, and invite other core members in <code>#perl6-dev</code> IRC
  257. channel to comment on it.</li>
  258. <li>After a 1 week review period, update the Action Plan to reflect
  259. any received feedback, and proceed to implement it.</li>
  260. </ul>
  261.  
  262. <h3>Commits</h3>
  263.  
  264. <p>The commits will implement the Action Plan. Roast commits will be based on
  265. the changes to routines as well as the report generated by the coverage tool.
  266. And the doc commits will be done by manually searching and reading exiting
  267. documentation and amending it as needed.</p>
  268.  
  269. <p>(N.B.: I'm aware the coverage tool is currently busted by a commit that changed
  270. filenames in <code>.file</code> method for core routines; however MasterDuke++ promised
  271. to fix it, and if they won't be able to find time to do so, the fix should be
  272. simple enough that I'd fix the tool myself).</p>
  273.  
  274. <h2>Project Schedule</h2>
  275.  
  276. <p>I already began work on the routine map generator and will complete it by
  277. the time the decision on this grant proposal is available. After that,
  278. I expect to spend 2 weeks preparing the I/O Action Plan Report, 1 week for its
  279. review by other core members, and 2 weeks for its full implementation
  280. (including tests and docs). I also allow for extra 2 weeks for any unforseen
  281. delays in any of the steps.</p>
  282.  
  283. <p>If my understanding of <a href="http://news.perlfoundation.org/2017/01/call-for-grant-proposals-jan-2.html">the date when the decision on this grant would be
  284. ready</a> is correct, I intend to finish the work before the end of March, 2017.</p>
  285.  
  286. <h2>Completeness Criteria</h2>
  287.  
  288. <ul>
  289. <li><a href="https://github.com/rakudo/rakudo/tree/nom/docs">rakudo repository</a>
  290. will contain the IO Action Plan document and it will be fully implemented.</li>
  291. <li>All of the I/O routines will have tests in
  292. <a href="https://github.com/perl6/roast/">roast</a> and documented on
  293. <a href="https://docs.perl6.org">docs.perl6.org</a>. If any of the currently implemented
  294. but unspecced routines are decided against being included in Perl 6 Language,
  295. their implementation will no longer be available in Rakudo.</li>
  296. <li>The test coverage tool will report all I/O routines as covered and
  297. the information will be visible on <a href="http://perl6.wtf">perl6.wtf</a> (<em>Perl 6's
  298. Wonderful Test Files</em>) website. Note: due to current experimental status of the
  299. coverage tool, its report may still show some lines or conditionals untested
  300. despite them actually being tested; however, it <em>will</em> show the lines where
  301. routines' names are specified as covered.</li>
  302. </ul>
  303.  
  304. <h2>Sidenote Comments</h2>
  305.  
  306. <p>The grant amount requested may be low compared to the described amount of work
  307. because I'd like to still view part of my time on this work as donated to
  308. Perl 6. Those who see me on IRC may notice I bounced around the ideas in this
  309. proposal before.</p>
  310.  
  311. <p>The grant will let me finish this work much sooner and in a more complete
  312. state than I would be able to otherwise.</p>
  313.  
  314. <h2>Bio</h2>
  315.  
  316. <p>I'm a 30-year old Canadian who lived near Toronto for the past 14 years.
  317. I also spent some years of my life living in USA (New Jersey) and, before that,
  318. in Russia (Siberia), where I was born.</p>
  319.  
  320. <p>I started with Perl 5 about 12 years ago and have since released over
  321. 200 Perl 5 modules on CPAN and for the last 10 years held a single job,
  322. large part of which is web development with Perl 5.</p>
  323.  
  324. <p>In the fall of 2015, I switched my focus to Perl 6 and to date released 34
  325. Perl 6 modules and delivered a couple of Perl 6 presentations at the Toronto
  326. Perl Mongers meetings.</p>
  327.  
  328. <p>Around July, 2016 I joined the Rakudo Perl 6 Core Development Team. I also have
  329. been Rakudo's release manager every month since the 2016.06 release.</p>
  330.  
  331. <p>My notable deliverables to the Perl 6 Community involve the creation of the
  332. web app driving <a href="https://modules.perl6.org">modules.perl6.org</a>; nearly total
  333. automation of the Rakudo's release process, including the development of
  334. <a href="http://perl6.fail">perl6.fail</a> web app for RT interfacing and release status
  335. tracking; and writing all of the tutorials on
  336. <a href="http://perl6.party">perl6.party</a> website.</p>
  337.  
  338. <p>To date, I have authored <strong>461 commits</strong> to
  339. <a href="https://github.com/rakudo/rakudo/">Rakudo</a> and <strong>1,823 commits</strong> to
  340. repositories in <a href="https://github.com/perl6/">Perl 6 GitHub organization</a>
  341. (<strong>523</strong> of which have been to the
  342. <a href="https://github.com/perl6/roast/">Perl 6 Specification</a> repository).</p>
  343. ]]>
  344.    </content>
  345. </entry>
  346.  
  347. <entry>
  348.    <title>Maintaining the Perl 5 Core: December 2016 report</title>
  349.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/maintaining-the-perl-5-core-de.html" />
  350.    <id>tag:news.perlfoundation.org,2017://18.3842</id>
  351.  
  352.    <published>2017-01-17T14:00:00Z</published>
  353.    <updated>2017-01-20T07:19:29Z</updated>
  354.  
  355.    <summary><![CDATA[Dave Mitchell writes: I spent December: 1) looking for quick some wins on speeding up perl compile-time, using 'perl -MCPAN -e1' as a typical example of loading and compiling several .pm files. I tweaked Perl_yyparse() and shaved ~2% off the compile time; then tweaked Perl_sv_gets() and shaved another ~2% off, and also got a pleasing run-time boost for line reading, with reading a big list of words now ~8% faster on my system: perl -e'$i++ while (&lt;>)' /usr/share/dict/words 2) investigating...]]></summary>
  356.    <author>
  357.        <name>Makoto Nozaki</name>
  358.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  359.    </author>
  360.    
  361.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  362.    
  363.        <category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category" />
  364.    
  365.    
  366.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  367.        <![CDATA[<p><em>Dave Mitchell writes:</em></p>
  368.  
  369. <pre>
  370. I spent December:
  371.  
  372. 1) looking for quick some wins on speeding up perl compile-time, using
  373. 'perl -MCPAN -e1' as a typical example of loading and compiling several
  374. .pm files.  I tweaked Perl_yyparse() and shaved ~2% off the compile time;
  375. then tweaked Perl_sv_gets() and shaved another ~2% off, and also got a
  376. pleasing run-time boost for line reading, with reading a big list of words
  377. now ~8% faster on my system:
  378.  
  379.    perl -e'$i++ while (<>)' /usr/share/dict/words
  380.  
  381. 2) investigating possible ways of making the regex engine faster by (in
  382. some cases) processing 8 bytes at a time on 64-bit platforms. This
  383. culminated in an this email thread:
  384.  
  385.    http://nntp.perl.org/group/perl.perl5.porters/241891
  386.  
  387. 3) as usual, working on a few miscellaneous tickets.
  388.  
  389. SUMMARY:
  390.      1:30 RT #130385 Bleadperl breaks DNS-LDNS
  391.      1:00 RT #130385 Bleadperl breaks List-Pairwise
  392.      1:00 RT #130398 Bleadperl breaks Method-Signatures
  393.      4:26 [perl #129199] Difficult-to-trigger panic
  394.      1:01 [perl #130247] Perl_rpeep(OP *): Assertion `oldop' failed
  395.      0:55 [perl #130307] Bug: Regex matches when it shouldn't
  396.      0:33 [perl #130311] heap-buffer-overflow Perl_yyparse
  397.      0:55 fix build warnings and smoke failures
  398.      1:40 fix some CPAN modules under PERL_OP_PARENT
  399.     19:00 investigate making find_by_class faster()
  400.      2:37 optimise Perl_sv_gets()
  401.      4:45 optimise Perl_yyparse()
  402.     12:20 process p5p mailbox
  403.      3:22 review RT tickets
  404.      3:04 review security tickets
  405.    ------
  406.     58:08 TOTAL (HH::MM)
  407.  
  408. 170.1 weeks
  409. 2338.8 total hours
  410.  13.7 average hours per week
  411.  
  412. There are 61 hours left on the grant
  413.  
  414. </pre>
  415. ]]>
  416.        
  417.    </content>
  418. </entry>
  419.  
  420. <entry>
  421.    <title>Grant Extension Request: Maintaining the Perl 5 Core</title>
  422.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/grant-extension-request-mainta-2.html" />
  423.    <id>tag:news.perlfoundation.org,2017://18.3841</id>
  424.  
  425.    <published>2017-01-10T22:00:01Z</published>
  426.    <updated>2017-01-12T15:20:39Z</updated>
  427.  
  428.    <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 regular reports to the p5p mailing list as well as providing monthly summary reports that have been published on this site, the most recent of which are linked below: Month 35 Month 36 Oct/Nov Before we make a decision on this extension, we would like to have...</summary>
  429.    <author>
  430.        <name>Makoto Nozaki</name>
  431.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  432.    </author>
  433.    
  434.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  435.    
  436.    
  437.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  438.        <![CDATA[<p><strong>Dave Mitchell</strong> has requested an extension of $20,000 for his <strong>Maintaining the Perl 5 Core</strong> grant. This will allow him to dedicate another 400 hours to this work. During this grant he sent regular reports to the p5p mailing list as well as providing monthly summary reports that have been published on this site, the most recent of which are linked below:</p>
  439.  
  440. <ul>
  441. <li><a href="http://news.perlfoundation.org/2016/09/maintaining-the-perl-5-core-re-31.html">Month 35</a></li>
  442. <li><a href="http://news.perlfoundation.org/2016/10/maintaining-the-perl-5-core-re-32.html">Month 36</a></li>
  443. <li><a href="http://news.perlfoundation.org/2017/01/maintaining-the-perl-5-core-oc.html">Oct/Nov</a></li>
  444. </ul>
  445.  
  446. <p>Before we make a decision on this extension, we would like to have a period of community consultation. Please leave feedback in the comments field below or if you prefer, send email with your comments to makoto at perlfoundation.org. We request that all the feedback should be sent by January 15th.</p>
  447.  
  448. <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>
  449. ]]>
  450.        
  451.    </content>
  452. </entry>
  453.  
  454. <entry>
  455.    <title>Maintaining the Perl 5 Core: October / November 2016 report</title>
  456.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/maintaining-the-perl-5-core-oc.html" />
  457.    <id>tag:news.perlfoundation.org,2017://18.3840</id>
  458.  
  459.    <published>2017-01-09T22:00:00Z</published>
  460.    <updated>2017-01-10T03:32:21Z</updated>
  461.  
  462.    <summary>Dave Mitchell writes: I spent last the last two months: * reworking list assignment (especially with an aggregate on the LHS) to be much faster in many cases. For example, this code is 33% faster in 5.25.7 compared with 5.24.0: my @a; for my $i (1..10_000_000) { @a = (1,2,3); @a = (); } * trying to reduce the overhead of compile time a bit; * freeing up some uses of SV flags; * fixing various assorted bugs as listed...</summary>
  463.    <author>
  464.        <name>Makoto Nozaki</name>
  465.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  466.    </author>
  467.    
  468.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  469.    
  470.    
  471.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  472.        <![CDATA[<p><em>Dave Mitchell writes:</em></p>
  473.  
  474. <pre>
  475. I spent last the last two months:
  476.  
  477. * reworking list assignment (especially with an aggregate on the LHS) to
  478.  be much faster in many cases. For example, this code is 33% faster in
  479.  5.25.7 compared with 5.24.0:
  480.  
  481.    my @a;
  482.    for my $i (1..10_000_000) {
  483.        @a = (1,2,3);
  484.        @a = ();
  485.    }
  486.  
  487. * trying to reduce the overhead of compile time a bit;
  488.  
  489. * freeing up some uses of SV flags;
  490.  
  491. * fixing various assorted bugs as listed below;
  492.  
  493. SUMMARY:
  494.     59:16 [perl #127999] Slowdown in split + list assign
  495.      8:28 [perl #129140] attempting double-free Perl_safesysfree util.c:388
  496.      0:23 [perl #129771] %+ not scoped properly
  497.      0:16 [perl #129802] Regexp performance problem with swiped strings (?)
  498.      1:13 [perl #129821] Bleadperl v5.25.5-65-g5012eeb breaks JJORE/Devel-OptreeDiff-2.3.tar.gz
  499.      3:01 [perl #129825] Overloaded integer constants are prematurely deallocated
  500.      0:34 [perl #129950] Some UTF-8 regular expression matches fail when read from file
  501.      0:10 [perl #129954] dist/Carp/t/arg_string.t: Test fails in blead
  502.      3:51 [perl #129991] Assertion failure in S_aassign_copy_common
  503.      7:23 [perl #129996] BBC Devel-SearchINC
  504.      4:01 [perl #129997] heap-use-after-free sv_catpvn_flags() within Perl_do_vop
  505.      8:44 [perl #130132] Bleadperl breaks Date-Manip
  506.      1:27 [perl #130188] crash on return from substitution in subroutine
  507.      8:00 eliminate some ugly SV flag usages
  508.      1:00 fix build warnings and smoke failures
  509.      2:30 miscellaneous fixups
  510.      2:09 optimise undef assignment
  511.     13:36 performance of keywords.c
  512.      7:33 process p5p mailbox
  513.      1:00 review security tickets
  514.      1:40 split to an array creating RO elements
  515.    ------
  516.    136:15 TOTAL (HH::MM)
  517.  
  518. 163.4 weeks
  519. 2243.6 total hours
  520.  13.7 average hours per week
  521.  
  522. There are 156 hours left on the grant
  523. </pre>
  524.  
  525. <p><em>Note: This report was sent in December and signed off by Marcus Holland-Moritz on Jan 6th.</em></p>
  526. ]]>
  527.        
  528.    </content>
  529. </entry>
  530.  
  531. <entry>
  532.    <title>TPF Grant Nov/Dec 2016 Round Results</title>
  533.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/tpf-grant-novemberdecember-rou.html" />
  534.    <id>tag:news.perlfoundation.org,2017://18.3839</id>
  535.  
  536.    <published>2017-01-09T21:00:00Z</published>
  537.    <updated>2017-01-10T03:33:39Z</updated>
  538.  
  539.    <summary>Grant Proposal: Learning Perl 6, a book from O&apos;Reilly Media At the invitation of the TPF board, brian has withdrawn the grant proposal for the Learning Perl 6 book, and will submit a proposal to TPF on other ways for TPF to participate in enhancing the visibility of Perl 6. The Grants Committee had a general discussion on funding activities whose output is not free of charge. TPF has documentation that states grant results must be &quot;released under a publically...</summary>
  540.    <author>
  541.        <name>Makoto Nozaki</name>
  542.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  543.    </author>
  544.    
  545.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  546.    
  547.    
  548.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  549.        <![CDATA[<p><a href="http://news.perlfoundation.org/2016/12/grant-proposal-learning-perl-6.html">Grant Proposal: Learning Perl 6, a book from O'Reilly Media</a></p>
  550.  
  551. <p>At the invitation of the TPF board, brian has withdrawn the grant
  552. proposal for the Learning Perl 6 book, and will submit a proposal to
  553. TPF on other ways for TPF to participate in enhancing the visibility
  554. of Perl 6.</p>
  555.  
  556. <p>The Grants Committee had a general discussion on funding activities
  557. whose output is not free of charge. TPF has documentation that states
  558. grant results must be "released under a publically available license
  559. that is free for redistribution and use without discrimination against
  560. field of endeavour" (from the "Grant Benefits" page), but the process of
  561. reviewing this proposal revealed that the documentation was easy to miss
  562. and not clearly stated as policy in the Grants Committee rules of
  563. operation. The committee unanimously agreed to update the rules to make
  564. it clear that all grant results should be available free of charge. We
  565. are in the process of adding such a clause to the rules of operation soon
  566. (wording may be slightly changed):</p>
  567.  
  568. <p>1.3. Grant proposals should mention how the grant results will be made
  569. available to the public. The grant results must be must be accessible
  570. free of charge.</p>
  571. ]]>
  572.        
  573.    </content>
  574. </entry>
  575.  
  576. <entry>
  577.    <title>Grant Report: Test2 Manual</title>
  578.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/grant-report-test2-manual-2.html" />
  579.    <id>tag:news.perlfoundation.org,2017://18.3838</id>
  580.  
  581.    <published>2017-01-08T14:58:17Z</published>
  582.    <updated>2017-01-08T15:03:45Z</updated>
  583.  
  584.    <summary>Chad Granun reports on his work on the Test2 Manual grant. The last month was devoted to: How to list the test tools in the modules dependencies; Tutorial for TODO tests; Tutorial for advanced test planning....</summary>
  585.    <author>
  586.        <name>Alberto Simões</name>
  587.        <uri>http://blogs.perl.org/users/alberto_simoes/</uri>
  588.    </author>
  589.    
  590.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  591.    
  592.    <category term="grants" label="grants" scheme="http://www.sixapart.com/ns/types#tag" />
  593.    
  594.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  595.        <![CDATA[<p>Chad Granun reports on his work on the Test2 Manual grant. The last month was devoted to:</p>
  596.  
  597. <ul>
  598. <li>How to list the test tools in the modules dependencies;</li>
  599. <li>Tutorial for TODO tests;</li>
  600. <li>Tutorial for advanced test planning.</li>
  601. </ul>
  602. ]]>
  603.        
  604.    </content>
  605. </entry>
  606.  
  607. <entry>
  608.    <title>Call For Grant Proposals (Jan 2017 Round)</title>
  609.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2017/01/call-for-grant-proposals-jan-2.html" />
  610.    <id>tag:news.perlfoundation.org,2017://18.3837</id>
  611.  
  612.    <published>2017-01-05T22:00:00Z</published>
  613.    <updated>2017-01-06T03:00:32Z</updated>
  614.  
  615.    <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 January 15th UTC. We will publish the received applications, get community feedback and conclude acceptance by January 25th. To apply, please read How to Write a Proposal. Rules of...</summary>
  616.    <author>
  617.        <name>Makoto Nozaki</name>
  618.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  619.    </author>
  620.    
  621.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  622.    
  623.    
  624.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  625.        <![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>
  626.  
  627. <p>If you have an idea for doing some Perl work that will benefit the Perl community, consider sending a grant application. <strong>The application deadline for this round is 23:59 January 15th UTC.</strong> We will publish the received applications, get community feedback and conclude acceptance by January 25th.</p>
  628.  
  629. <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>
  630.  
  631. <p>We will confirm the receipt of application within 24 hours.</p>
  632.  
  633. <p>If you have further questions, please contact me at tpf-grants-secretary at perl-foundation.org.</p>
  634. ]]>
  635.        
  636.    </content>
  637. </entry>
  638.  
  639. <entry>
  640.    <title>TPF 2016Q4 Activity Report</title>
  641.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/12/tpf-2016q4-activity-report.html" />
  642.    <id>tag:news.perlfoundation.org,2016://18.3836</id>
  643.  
  644.    <published>2016-12-27T23:00:00Z</published>
  645.    <updated>2016-12-28T04:44:58Z</updated>
  646.  
  647.    <summary>General White Camels Awards winners have been annouonced. TPF will take part in Outreachy. Conferences Perl Conference NA 2017 will be held June 18th through June 23rd in Alexandria, Virginia. Grants Updates Maintaining Perl 5: November | August Maintaining Perl 5 Core: October | September JavaScript Backend For Rakudo: October RPerl User Documentation: December | October blogs.perl.org Rewrite: November Test2 Manual: November | October Start Act - Voyager: No update Proposal Learning Perl 6 book: Pending Grant Extension Maintaining Perl...</summary>
  648.    <author>
  649.        <name>Makoto Nozaki</name>
  650.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  651.    </author>
  652.    
  653.        <category term="Perl Foundation" scheme="http://www.sixapart.com/ns/types#category" />
  654.    
  655.    
  656.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  657.        <![CDATA[<h3>General</h3>
  658.  
  659. <ul>
  660. <li><a href="http://blogs.perl.org/users/brian_d_foy/2016/12/white-camels-2016.html">White Camels Awards</a> winners have been annouonced.</li>
  661. <li>TPF will <a href="http://news.perlfoundation.org/2016/09/taking-part-in-outreachy-1.html">take part in</a> <a href="https://www.gnome.org/outreachy/">Outreachy</a>.</li>
  662. </ul>
  663.  
  664. <h3>Conferences</h3>
  665.  
  666. <ul>
  667. <li><a href="http://news.perlfoundation.org/2016/11/the-perl-conference-save-date-2017.html">Perl Conference NA 2017</a> will be held June 18th through June 23rd in Alexandria, Virginia.</li>
  668. </ul>
  669.  
  670. <h3>Grants</h3>
  671.  
  672. <ul>
  673. <li>Updates
  674. <ul>
  675. <li>Maintaining Perl 5: <a href="http://news.perlfoundation.org/2016/12/maintaining-perl-5-grant-repor-35.html">November</a> | <a href="http://news.perlfoundation.org/2016/10/maintaining-perl-5-grant-repor-33.html">August</a></li>
  676. <li>Maintaining Perl 5 Core: <a href="http://news.perlfoundation.org/2016/10/maintaining-the-perl-5-core-re-32.html">October</a> | <a href="http://news.perlfoundation.org/2016/09/maintaining-the-perl-5-core-re-31.html">September</a></li>
  677. <li>JavaScript Backend For Rakudo: <a href="http://news.perlfoundation.org/2016/10/update-on-javascript-backend-f.html">October</a></li>
  678. <li>RPerl User Documentation: <a href="http://news.perlfoundation.org/2016/12/grant-report-rperl-user-docume-11.html">December</a> | <a href="http://news.perlfoundation.org/2016/10/grant-report-rperl-user-docume-10.html">October</a></li>
  679. <li>blogs.perl.org Rewrite: <a href="http://news.perlfoundation.org/2016/11/public-beta-of-blogsperlorg-re.html">November</a></li>
  680. <li>Test2 Manual: <a href="http://news.perlfoundation.org/2016/11/grant-report-test2-manual-1.html">November</a> | <a href="http://news.perlfoundation.org/2016/10/grant-report-test2-manual.html">October</a></li>
  681. <li>Start Act - Voyager: No update</li>
  682. </ul></li>
  683. <li>Proposal
  684. <ul>
  685. <li><a href="http://news.perlfoundation.org/2016/12/grant-proposal-learning-perl-6.html">Learning Perl 6 book</a>: Pending</li>
  686. </ul></li>
  687. <li>Grant Extension
  688. <ul>
  689. <li><a href="http://news.perlfoundation.org/2016/10/tony-cooks-grant-extended-1.html">Maintaining Perl 5 Extension</a>: Approved</li>
  690. </ul></li>
  691. </ul>
  692.  
  693. <h3>People On The Move</h3>
  694.  
  695. <ul>
  696. <li>Karen Pauley has stepped down as TPF President and Jim Brandt has assumed the the new President role (<a href="http://news.perlfoundation.org/2016/11/tpf-president-change.html">details</a>).</li>
  697. </ul>
  698.  
  699. <p><em>Is this report useful? We welcome your feedback. Contact: makoto at perlfoundation.org</em></p>
  700. ]]>
  701.        
  702.    </content>
  703. </entry>
  704.  
  705. <entry>
  706.    <title>White Camel Awards for 2016</title>
  707.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/12/white-camel-awards-for-2016.html" />
  708.    <id>tag:news.perlfoundation.org,2016://18.3835</id>
  709.  
  710.    <published>2016-12-20T08:14:54Z</published>
  711.    <updated>2016-12-23T01:08:24Z</updated>
  712.  
  713.    <summary>brian d foy has announced the White Camel Awards for 2016 and we&apos;d like to congratulate the winners. I&apos;d like to add a special congratulations to Karen Pauley for all her work with Perl, both officially as TPF president and unofficially as a community member. Thanks to all of the winners for your constant efforts toward keeping the Perl community a vibrant and fun place to be....</summary>
  714.    <author>
  715.        <name>Jim Brandt</name>
  716.        <uri>http://breakingpositive.com</uri>
  717.    </author>
  718.    
  719.        <category term="Awards" scheme="http://www.sixapart.com/ns/types#category" />
  720.    
  721.    
  722.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  723.        <![CDATA[<p>brian d foy has <a href="http://blogs.perl.org/users/brian_d_foy/2016/12/white-camels-2016.html">announced the White Camel Awards for 2016</a> and we'd like to congratulate the winners. I'd like to add a special congratulations to Karen Pauley for all her work with Perl, both officially as TPF president and unofficially as a community member. Thanks to all of the winners for your constant efforts toward keeping the Perl community a vibrant and fun place to be.</p>
  724. ]]>
  725.        
  726.    </content>
  727. </entry>
  728.  
  729. <entry>
  730.    <title>Maintaining Perl 5: Grant Report for November 2016</title>
  731.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/12/maintaining-perl-5-grant-repor-35.html" />
  732.    <id>tag:news.perlfoundation.org,2016://18.3834</id>
  733.  
  734.    <published>2016-12-14T23:00:00Z</published>
  735.    <updated>2017-01-20T07:56:46Z</updated>
  736.  
  737.    <summary>The Perl Foundation received the following report from Tony Cook. Approximately 31 tickets were reviewed or worked on, and 8 patches were applied. [Hours] [Activity] 0.37 #116945 review and comment #116945 try to review branch, comment 2.05 #122112 research, review code 3.66 #123638 (sec) work on patch, testing #123638 (sec) perldiag wording, work on regression test #123638 (sec) final tests, comment with patch 3.58 #126706 testing, research #126706 try an alternate approach (and fail) 0.65 #128967 research, testing, revert a...</summary>
  738.    <author>
  739.        <name>Makoto Nozaki</name>
  740.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  741.    </author>
  742.    
  743.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  744.    
  745.    <category term="perl5core" label="perl5 core" scheme="http://www.sixapart.com/ns/types#tag" />
  746.    
  747.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  748.        <![CDATA[<p><em>The Perl Foundation received the following report from Tony Cook.</em></p>
  749.  
  750. <p>Approximately 31 tickets were reviewed or worked on, and 8 patches
  751. were applied.</p>
  752.  
  753. <pre>
  754. [Hours]         [Activity]
  755.  0.37          #116945 review and comment
  756.                #116945 try to review branch, comment
  757.  2.05          #122112 research, review code
  758.  3.66          #123638 (sec) work on patch, testing
  759.                #123638 (sec) perldiag wording, work on regression test
  760.                #123638 (sec) final tests, comment with patch
  761.  3.58          #126706 testing, research
  762.                #126706 try an alternate approach (and fail)
  763.  0.65          #128967 research, testing, revert a test changed only to
  764.                satisfy the commit reverted to fix this ticket
  765.  1.42          #129000 testing, apply to blead with minor commit message
  766.                changes
  767. </pre>
  768. ]]>
  769.        <![CDATA[<pre>
  770.  5.10          #129238 debugging
  771.                #129238 finish new API, work on using it
  772.                #129238 more work on using it
  773.  0.83          #129272 (sec) testing, dup of #129000
  774.  4.83          #129274 (sec) debugging
  775.                #129274 (sec) debugging
  776.                #129274 make public, comment with minor patch
  777.  0.88          #129292 (sec) minimize
  778.                #129292 (sec) more minimize, comment
  779.  0.42          #129826 testing, apply to blead and close
  780.  1.18          #129881 (sec) minimize, comment
  781.  1.27          #129963 (sec) minimize, debugging, comment
  782.  1.32          #129975 (sec) minimize, testing, comment
  783.  5.46          #129990 ask for patch as attachment, briefly review
  784.                without testing
  785.                #129990 review, try a sanitize build, track down other
  786.                sanitize failures
  787.                #129990 testing
  788.                #129990 review code and try to break it, benchmarking,
  789.                comment
  790.                #129990 testing, comment
  791.  0.97          #129991 minimize, comment
  792.  6.28          more debugging, open ticket #129997
  793.                #129997 testing, work on some alternate approaches,
  794.                comment with patch
  795.                #129997 work on a regression test, apply to blead, merge
  796.                into (sec) #129995 and close
  797.                #129997 comments
  798.  3.39          #130080 testing, comment
  799.                #130080 testing, reproduce, email Steve Hay
  800.                #130080 comment
  801.  0.95          #130082 review and comment
  802.                #130082 review new patch, testing, apply to blead
  803.  0.80          #130100 (sec) research, comment
  804.  2.00          #130101 review and comment
  805.                #130101 comment
  806.                #130101 review, testing, extra patches for bumping version
  807.                and updating changes list, apply to blead
  808. 24.08          #130108 test setup, debugging
  809.                #130108 work on a fix, testing, comment with patch
  810.                #130108 testing on 10.3, comment with patch for build
  811.                issue
  812.                #130108 debugging, comment
  813.                #130108 testing on Solaris, testing on freebsd 11, trying
  814.                to build older perl with dtrace on freebsd
  815.                #130108 check reference supplied by swills in irc, irc
  816.                discussion
  817.                #130108 work on a Makefile.SH patch
  818.                #130108 more dtrace build re-work
  819.                #130108 more dtrace build re-work, cross-platform testing
  820.                #130108 work out darwin failure, work on getting it to
  821.                probe correctly in a FreeBSD jail
  822.                #130108 move -xnolibs check earlier, testing
  823.                #130108 cross-platform test setup
  824.                #130108 test built binaries, polish, post patch to ticket
  825.  0.90          #130128 review, testing, apply to blead
  826.  0.73          #130133 review discussion, testing, apply to blead
  827.  0.73          #130143 research, comment
  828.  1.00          #130193 review, testing (faster without sanitize), apply
  829.                to blead
  830.  0.85          fix diag.t failure (make :utf8 deprecated warnings default
  831.                on)
  832.  2.30          fix Time-HiRes El Capitan build failure, testing
  833.  1.38          HP-UX issues, revert hek_flags change, it was causing
  834.                unaligned accesses
  835.  0.58          more sanitize debugging
  836.  0.57          OS X build testing, get build failure for blead on El
  837.                Capitan
  838. ======
  839. 80.53 hours total
  840. </pre>
  841. ]]>
  842.    </content>
  843. </entry>
  844.  
  845. <entry>
  846.    <title>Grant Report : RPerl User Documentation #2 - Nov 2016</title>
  847.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/12/grant-report-rperl-user-docume-11.html" />
  848.    <id>tag:news.perlfoundation.org,2016://18.3833</id>
  849.  
  850.    <published>2016-12-14T03:35:13Z</published>
  851.    <updated>2016-12-21T17:50:00Z</updated>
  852.  
  853.    <summary><![CDATA[Here is Will's report for November: " Chapter 3 is now complete! The following new sections of Learning RPerl have been published: Section 3.10: Range .. Operator Section 3.11: Converting From Array To String Section 3.12: Program Control Using The for &amp; foreach Loops Section 3.12.1: The Range for Loop Section 3.12.2: The C-Style for Loop Section 3.12.3: The foreach Loop Section 3.13: Punctuation Variables &amp; Magic Section 3.14: reverse Operator Section 3.15: sort Operator Section 3.16: Scalar &amp; Array...]]></summary>
  854.    <author>
  855.        <name>Mark A Jensen</name>
  856.        
  857.    </author>
  858.    
  859.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  860.    
  861.    <category term="grants" label="grants" scheme="http://www.sixapart.com/ns/types#tag" />
  862.    <category term="rperl" label="RPerl" scheme="http://www.sixapart.com/ns/types#tag" />
  863.    
  864.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  865.        <![CDATA[<p>Here is Will's report for November:</p>
  866.  
  867. <p>" Chapter 3 is now complete!</p>
  868.  
  869. <p>The following new sections of Learning RPerl have been published:</p>
  870.  
  871. <ul>
  872. <li><a href="http://rperl.org/learning_rperl.html#Section_3.10%3A_Range_.._Operator">Section 3.10: Range .. Operator</a></li>
  873. <li><a href="http://rperl.org/learning_rperl.html#Section_3.11%3A_Converting_From_Array_To_String">Section 3.11: Converting From Array To String</a></li>
  874. <li><a href="http://rperl.org/learning_rperl.html#Section_3.12%3A_Program_Control_Using_The_for_%26_foreach_Loops">Section 3.12: Program Control Using The for &amp; foreach Loops</a>
  875. <ul>
  876.  <li><a href="http://rperl.org/learning_rperl.html#Section_3.12.1%3A_The_Range_for_Loop">Section 3.12.1: The Range for Loop</a></li>
  877.  <li><a href="http://rperl.org/learning_rperl.html#Section_3.12.2%3A_The_C-Style_for_Loop">Section 3.12.2: The C-Style for Loop</a></li>
  878.  <li><a href="http://rperl.org/learning_rperl.html#Section_3.12.3%3A_The_foreach_Loop">Section 3.12.3: The foreach Loop</a></li>
  879.  </ul></li>
  880. <li><a href="http://rperl.org/learning_rperl.html#Section_3.13%3A_Punctuation_Variables_%26_Magic">Section 3.13: Punctuation Variables &amp; Magic</a></li>
  881. <li><a href="http://rperl.org/learning_rperl.html#Section_3.14%3A_reverse_Operator">Section 3.14: reverse Operator</a></li>
  882. <li><a href="http://rperl.org/learning_rperl.html#Section_3.15%3A_sort_Operator">Section 3.15: sort Operator</a></li>
  883. <li><a href="http://rperl.org/learning_rperl.html#Section_3.16%3A_Scalar_%26_Array_Contexts">Section 3.16: Scalar &amp; Array Contexts</a></li>
  884. <li><a href="http://rperl.org/learning_rperl.html#Section_3.17%3A_STDIN_%26_Arrays">Section 3.17: STDIN &amp; Arrays</a></li>
  885. <li><a href="http://rperl.org/learning_rperl.html#Section_3.18%3A_Exercises">Section 3.18: Exercises</a>
  886. <ul>
  887.  <li><a href="http://rperl.org/learning_rperl.html#1._Reverse_Collected_Array_Of_Strings_%5B_30_mins_%5D">1. Reverse Collected Array Of Strings [ 30 mins ]</a></li>
  888.  <li><a href="http://rperl.org/learning_rperl.html#2._Collect_Array_Indices_%5B_45_mins_%5D">2. Collect Array Indices [ 45 mins ]</a></li>
  889.  <li><a href="http://rperl.org/learning_rperl.html#3._Sort_%26_Display_Collected_Array_Of_Strings_%5B_45_mins_%5D">3. Sort &amp; Display Collected Array Of Strings [ 45 mins ]</a></li>
  890.  </ul></li>
  891.  </ul>
  892.  
  893.  
  894. Also, updates and modifications have been made to the following sections (among others):
  895.  
  896. <ul>
  897. <li><a href="http://rperl.org/learning_rperl.html#Section_3.3%3A_How_To_Access_Array_Elements">Section 3.3: How To Access Array Elements</a></li>
  898. <li><a href="http://rperl.org/learning_rperl.html#Section_3.6%3A_Quote_Word_qw()_Operator">Section 3.6: Quote Word qw() Operator</a></li>
  899. <li><a href="http://rperl.org/learning_rperl.html#Section_3.8%3A_push_%26_pop_Operators">Section 3.8: push &amp; pop Operators</a></li>
  900. <li><a href="http://rperl.org/learning_rperl.html#Section_3.9%3A_shift_%26_unshift_Operators">Section 3.9: shift &amp; unshift Operators</a></li>
  901. </ul>
  902.  
  903. <p>Happy Holidays from the RPerl Team to your family!  :-) "</p>
  904.  
  905. <p>MAJ</p>
  906. ]]>
  907.        
  908.    </content>
  909. </entry>
  910.  
  911. <entry>
  912.    <title>Maintaining Perl 5: Grant Report for October 2016</title>
  913.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/12/maintaining-perl-5-grant-repor-34.html" />
  914.    <id>tag:news.perlfoundation.org,2016://18.3832</id>
  915.  
  916.    <published>2016-12-10T22:00:00Z</published>
  917.    <updated>2016-12-18T13:53:12Z</updated>
  918.  
  919.    <summary>The Perl Foundation received the following report from Tony Cook in November. Note: This post was delayed due to the role changes within TPF. Apologies. Approximately 29 tickets were reviewed or worked on, and 8 patches were applied. [Hours] [Activity] 1.52 #128996 (sec) testing vs 129879, seems to be the same, make public, apply patch 4.11 #128997 (sec) reproduce again, debugging #128997 move to public, comment, debug other issue, work on patch #128997 write test, testing, comment with patch #128997...</summary>
  920.    <author>
  921.        <name>Makoto Nozaki</name>
  922.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  923.    </author>
  924.    
  925.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  926.    
  927.    <category term="perl5core" label="perl5 core" scheme="http://www.sixapart.com/ns/types#tag" />
  928.    
  929.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  930.        <![CDATA[<p><em>The Perl Foundation received the following report from Tony Cook in November. Note: This post was delayed due to the role changes within TPF. Apologies.</em></p>
  931.  
  932. <p>Approximately 29 tickets were reviewed or worked on, and 8 patches
  933. were applied. </p>
  934.  
  935. <pre>
  936. [Hours] [Activity]
  937. 1.52   #128996 (sec) testing vs 129879, seems to be the same,
  938.        make public, apply patch
  939. 4.11   #128997 (sec) reproduce again, debugging
  940.        #128997 move to public, comment, debug other issue, work
  941.        on patch
  942.        #128997 write test, testing, comment with patch
  943.        #128997 re-check, testing, apply to blead
  944. </pre>
  945. ]]>
  946.        <![CDATA[<pre>
  947. 6.45   #129000 (sec) debugging, work on a fix, tests for new api
  948.        needed for fix
  949.        #129000 make public, more new api test cases, debugging
  950.        #129000 more new api test cases, write a test case for the
  951.        bug itself, comment with patch
  952.        #129000 alternative patch
  953. 0.42   #129085 make ticket public, re-check, testing, apply to
  954.        blead
  955. 4.12   #129125 (sec) work on alternate patch, testing
  956.        #129125 (sec) testing, debugging new tests
  957.        #129125 (sec) debugging, post new patch
  958. 0.79   #129130 (sec) double-check patch, testing
  959.        #129130 make public and push to blead
  960. 0.80   #129183 review discussion, produce a simple patch
  961. 2.70   #129229 work on a better dep patch, read over discussion
  962.        #129229 testing, comment
  963.        #129229 review new patch and comment
  964. 5.81   #129238 review discussion
  965.        #129238 read discussion, work on a patch
  966.        #129238 work on alt patch
  967.        #129238 alt patch: test code, debugging
  968. 0.22   #129277 review discussion
  969. 2.07   #129281 (sec) review, work up test, research and comment
  970. 1.63   #129292 (sec) debugging
  971. 0.67   #129298 review patches and comment
  972. 0.65   #129300 debugging
  973. 1.52   #129336 review, review existing switch handling, testing,
  974.        apply to blead
  975. 0.12   #129766 review
  976. 0.77   #129788 review patch and produce alternate (move test to a
  977.        better place)
  978. 2.25   #129826 try to reproduce in blead, try against 5.24.0
  979.        #129826 try to reproduce some more, check poster's “--”
  980.        theory, comment
  981.        #129826 review Inline::Perl5 code and comment
  982. 0.25   #129840 (sec) testing, debugging
  983. 3.55   #129861 (sec) debugging
  984.        #129861 (sec) more debugging, comment with simple
  985.        reproducer
  986. 2.19   #129864 (sec) review code
  987.        #129864 (sec) more review code, comment
  988.        #129864 (sec) review response
  989. 2.03   #129879 (sec) diagnose, simplify, produce patch and
  990.        comment
  991. 2.13   #129895 review change, test prep
  992.        #129895 testing, apply to blead
  993. 0.37   #129908 review, porting tests, make a commit and apply to
  994.        blead
  995. 1.15   #129928 review, testing, apply to blead
  996. 0.82   #129950 testing, debugging and comment
  997. 0.80   #129961 review, testing, apply to blead
  998. 0.18   #129967 review, research and comment
  999. 0.90   review list
  1000. ======
  1001. 50.99 hours total
  1002.  
  1003. </pre>
  1004. ]]>
  1005.    </content>
  1006. </entry>
  1007.  
  1008. <entry>
  1009.    <title>Grant Proposal: Learning Perl 6, a book from O&apos;Reilly Media</title>
  1010.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/12/grant-proposal-learning-perl-6.html" />
  1011.    <id>tag:news.perlfoundation.org,2016://18.3831</id>
  1012.  
  1013.    <published>2016-12-06T23:00:00Z</published>
  1014.    <updated>2017-01-11T12:19:23Z</updated>
  1015.  
  1016.    <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>
  1017.    <author>
  1018.        <name>Makoto Nozaki</name>
  1019.        <uri>http://blogs.perl.org/users/makoto_nozaki/</uri>
  1020.    </author>
  1021.    
  1022.        <category term="Grants" scheme="http://www.sixapart.com/ns/types#category" />
  1023.    
  1024.    
  1025.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  1026.        <![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>
  1027.  
  1028. <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>
  1029.  
  1030. <h1>Learning Perl 6, a book from O'Reilly Media</h1>
  1031.  
  1032. <ul>
  1033. <li><p>Name:</p>
  1034.  
  1035. <p>brian d foy</p></li>
  1036. <li><p>Amount Requested:</p>
  1037.  
  1038. <p>USD 10,000</p></li>
  1039. </ul>
  1040.  
  1041. <h2>Synopsis</h2>
  1042.  
  1043. <p>Partially fund the writing process for Learning Perl 6, a book from O'Reilly Media</p>
  1044.  
  1045. <h2>Benefits to the Perl Community</h2>
  1046.  
  1047. <p>Note: I am also running a Kickstarter campaign
  1048. (<a href="https://www.kickstarter.com/projects/1422827986/learning-perl-6">https://www.kickstarter.com/projects/1422827986/learning-perl-6</a>). I
  1049. have not given much thought to the mechanism of The Perl Foundation
  1050. funding, but I think I'd want it to be through your normal mechanism
  1051. rather than Kickstarter. I understand that payment on completion in
  1052. part of that process. That works for me. I would appreciate TPF's help
  1053. in spreading the word and finding backers.</p>
  1054.  
  1055. <p>Perl 6 does not have a tutorial book. To reach further out into the general
  1056. programming world, people need a gentle introduction to the language. This
  1057. book is about bringing people into the community more than serving the
  1058. ones already here.</p>
  1059.  
  1060. <p>Some people have written survey books that have covered ancient
  1061. versions of the language (Perl 6 and Parrot Essentials, Perl 6 Now).
  1062. Other people are working on cookbook-style example books (Moritz Lenz
  1063. most notably). Several other efforts have stalled or stopped. A book
  1064. can be a big chunk of a person's life, and financial stability along with
  1065. the removal of the distractions of normal commerce are key to success.</p>
  1066.  
  1067. <p>The big question is my need for the money, especially when I have a
  1068. major publisher committed to publishing the book. In short, I've
  1069. shifted O'Reilly risk tolerance by taking on some of it myself.</p>
  1070.  
  1071. <p>First, book sales aren't what they used to be. I'm taking a big gamble
  1072. here and I have a lot of personal risk, mostly in lost time. Many
  1073. comments on the kickstarter have centered around "Why doesn't O'Reilly
  1074. pay for the book?" Publishers don't "pay" so much as give you advanced
  1075. royalties. That robs the future to pay for the present. I've never
  1076. taken an advance on a book, and even if I did, a sane publisher
  1077. wouldn't provide me enough money to allow me to do this. I fully
  1078. expect Learning Perl 6 to be my least-popular book.</p>
  1079.  
  1080. <p>The entire technology book market shrinking and has been for years.
  1081. Perl 6 as a usable language is a new technology in an already crowded
  1082. market. There's a big chance that this is a "front list" book that
  1083. makes all of its sales in the first months of its release and is never
  1084. bought again. This situation happens with a dedicated fan base or a
  1085. highly promoted book that doesn't catch on. I already know the sales
  1086. numbers for Learning Perl. If I had to guess at a sales target for
  1087. Learning Perl 6, I'd take one-tenth that number. It's not a motivating
  1088. amount for me. As the author of several existing books, I don't have
  1089. the same secondary rewards of new fame and recognition as a first-time
  1090. author.</p>
  1091.  
  1092. <p>Second, book sales aren't primarily important to the marketing
  1093. goals of the Perl 6 community. To be taken seriously as a technology
  1094. (even if the community is small), someone needs to be able to point to
  1095. something in the marketplace. A technology manager might take a
  1096. signalling cue from the existence of a dead-tree book because the
  1097. publisher has already judged risk and committed to the book. Even if
  1098. we think this is a poor way to make judgements (and granted, we'd
  1099. often be right), there's the dirty mess of reality versus how we think
  1100. the world should be. This is important to many people in the Perl 6
  1101. community. The lack of a book is a big hurdle for our "force
  1102. multipliers"—the teachers and trainers who don't have the time to
  1103. construct a full curriculum themselves but could use a tutorial book
  1104. that's ready to teach in a segmented, classroom enviromented.</p>
  1105.  
  1106. <p>Third, the Kickstarter amount sounds impressive, but I'm also
  1107. responsible for all expenses and taxes. Every e-book and print book I
  1108. give out as a reward is actually a pre-sale. Most of that money flows
  1109. to the publisher as a sale (of which I still get a royalty). The
  1110. Kickstarter money is also subject to taxes. I've run a small business
  1111. for a couple decades; that number doesn't seem that large for the
  1112. effort. I'm looking for any support out there. When you consider the
  1113. amount, I think it's much more productive to think about getting what
  1114. you want at a price that makes sense to you. Considering the levels
  1115. that TPF has funded similar grants delivering less, I think this is
  1116. more than reasonable value.</p>
  1117.  
  1118. <p>If you could get this book without this grant and without the
  1119. Kickstarter, I'd support that. Indeed, I've waited for that book just
  1120. like you. But, no one has stepped up to write it and that book doesn't
  1121. exist. TPF's role could underpin the community support I'm already
  1122. receiving. This grant further ensures the end result.</p>
  1123. ]]>
  1124.        <![CDATA[<h2>Deliverables</h2>
  1125.  
  1126. <p>The deliverable is a printed O'Reilly Media book. O'Reilly publishes
  1127. and promotes the book. I am already under contract with O'Reilly.
  1128. Brian Jepson is my editor, and we've developed mock cover art for the
  1129. book (meaning, O'Reilly has assigned us an animal).</p>
  1130.  
  1131. <p>I am running a campaign through Kickstarter to fund this book. Several
  1132. of the rewards involve delivery of the book. The folks at O'Reilly
  1133. tell me this means I can't have my working sources open as I normally
  1134. do because it would violate the Robinson-Patman Act (some customers
  1135. get the same product at a lower price). I can, however, allow access
  1136. for selected technical reviewers and grant managers.</p>
  1137.  
  1138. <h2>Project Details</h2>
  1139.  
  1140. <p>I'm writing a tutorial-style book for beginners. I expect the book to
  1141. be about the size and scope of the existing Learning Perl book. I'm
  1142. aiming for 300 pages.</p>
  1143.  
  1144. <p>This is not be definitive or a reference (others are working on
  1145. that). This is not the documentation. A tutorial's task is to introduce
  1146. the language in steps and uses the least number of concepts along the
  1147. way. My goal is to build a solid foundation for understanding the
  1148. language both in syntax and philosophy. Documentation explains a tool
  1149. but doesn't put it into the context of a task.</p>
  1150.  
  1151. <p>This book progresses by slowly introducing concepts and giving
  1152. readers a chance to practice those. Typically, I explain the fully
  1153. expanded form of syntax and work my way to the idiomatic
  1154. representation. This technique helps readers understand the implied
  1155. parts of the idiomatic form, but also helps them become better readers
  1156. of other people's code.</p>
  1157.  
  1158. <p>Each chapter of the book includes exercises along with explicated
  1159. answers. Practice is the key to learning.</p>
  1160.  
  1161. <h2>Inch-stones</h2>
  1162.  
  1163. <p>A book project isn't straightforward. There's not a single
  1164. path to the result. Often the work is a big soup until it seemingly
  1165. miraculously comes together close to the end. The progress in a new
  1166. book is more experimental and philosophical than concrete. The initial
  1167. effort is usually a big mess, but that's part of the process.</p>
  1168.  
  1169. <h2>Project Schedule</h2>
  1170.  
  1171. <p>I have these major milestones specified in the contract for the book:</p>
  1172.  
  1173. <ul>
  1174. <li>Two completed chapters by January</li>
  1175. <li>Half the book by May</li>
  1176. <li>The whole book by August</li>
  1177. </ul>
  1178.  
  1179. <p>It takes approximately three months for a book to make it through the
  1180. O'Reilly publishing process. This includes one round of technical
  1181. review, two rounds of copy-editing, an indexer (a live person who
  1182. indexes the book), and finally injection into the distribution channels.</p>
  1183.  
  1184. <p>Additionally, there is a set of people (official technical reviewers
  1185. or self-selected backers through a Kickstarter reward) who will
  1186. receive monthly drafts of the book. They will be able to provide feedback
  1187. and comments, and should be an effective commitment device. They get a PDF
  1188. that looks just like an O'Reilly book since it comes out of the continuous
  1189. publishing system.</p>
  1190.  
  1191. <p>As for a more detailed schedule, it's been my experience in publishing
  1192. that they are never honest and no one expects them to be true. I could
  1193. say that I'd deliver a particular chapter in a particular month, but
  1194. later discover that it's more important to work on a different
  1195. chapter. Halfway through I typically have a moment of clarity that
  1196. makes me go back through everything I've already done to take it in a
  1197. different direction.</p>
  1198.  
  1199. <p>I typically view the schedules as a bit squishy, but I've always been
  1200. close.</p>
  1201.  
  1202. <h2>Completeness Criteria</h2>
  1203.  
  1204. <p>To be judged complete, my O'Reilly editor, Brian Jepson, certifies
  1205. that I've met the conditions imposed by O'Reilly. Once I've done that,
  1206. O'Reilly mostly takes over and it's a sure thing.</p>
  1207.  
  1208. <p>Under the standard author contract, O'Reilly judges the book complete
  1209. when they think the content and form of the book are at or above the
  1210. level of their usual quality. If it is not (and this have never been a
  1211. problem for me), they have the right to ask another author to make
  1212. changes to bring it up to their standards.</p>
  1213.  
  1214. <h2>Bio</h2>
  1215.  
  1216. <p>I'm brian d foy, the author or co-author of many of the existing
  1217. Perl 5 books from O'Reilly Media, including Learning Perl, (Editions 4 to 7),
  1218. Intermediate Perl (Editions 1 and 2), Mastering Perl (Editions 1 and 2), and
  1219. Programming Perl (4th Edition). I am a U.S. citizen living in the U.S.</p>
  1220.  
  1221. <p>I've worked extensively in the publishing process, have great tools that
  1222. I've already used for my previous books, and have already set up everything
  1223. with O'Reilly Media.</p>
  1224. ]]>
  1225.    </content>
  1226. </entry>
  1227.  
  1228. <entry>
  1229.    <title>Metacpan Upgraded</title>
  1230.    <link rel="alternate" type="text/html" href="http://news.perlfoundation.org/2016/11/metacpan-upgraded.html" />
  1231.    <id>tag:news.perlfoundation.org,2016://18.3830</id>
  1232.  
  1233.    <published>2016-11-29T13:08:36Z</published>
  1234.    <updated>2016-12-18T14:35:47Z</updated>
  1235.  
  1236.    <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>
  1237.    <author>
  1238.        <name>Jim Brandt</name>
  1239.        <uri>http://breakingpositive.com</uri>
  1240.    </author>
  1241.    
  1242.        <category term="CPAN" scheme="http://www.sixapart.com/ns/types#category" />
  1243.    
  1244.    
  1245.    <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
  1246.        <![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>
  1247. ]]>
  1248.        
  1249.    </content>
  1250. </entry>
  1251.  
  1252. </feed>
  1253.  

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