FEED Validator

for Atom and RSS and KML

Sorry

This feed does not validate.

line 7, column 28: updated must be an RFC-3339 date-time: 2024-05-06T19:42:01 [help]

<updated>2024-05-06T19:42:01</updated>
                            ^

line 12, column 32: published must be an RFC-3339 date-time: 2024-05-06T19:42:01 (15 occurrences) [help]

  <published>2024-05-06T19:42:01</published>
                                ^

line 13, column 30: updated must be an RFC-3339 date-time: 2024-05-06T19:42:01 (15 occurrences) [help]

  <updated>2024-05-06T19:42:01</updated>
                              ^

In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendation.

line 25, column 0: style attribute contains potentially dangerous content: max-width (28 occurrences) [help]
```
       <img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e6 ...
```

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

<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>The Perl Foundation</title>
<link rel="alternate" type="text/html" href="http://news.perlfoundation.org/"/>
<link rel="self" type="application/atom+xml" href="http://news.perlfoundation.org/atom.xml"/>
<id>tag:news.perlfoundation.org,2010-03-22://18</id>
<updated>2024-05-06T19:42:01</updated>
<generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 6.2.2</generator><entry>
<title>Maintaining Perl (Tony Cook) February 2024 </title>
<link rel="alternate" type="text/html" href="https://news.perlfoundation.org:443/post/maintaining_perl_tonyc_february_2024"/>
<id>tag:news.perlfoundation.org,2024-05-06:/post/maintaining_perl_tonyc_february_2024</id>
<published>2024-05-06T19:42:01</published>
<updated>2024-05-06T19:42:01</updated>
<summary>
<![CDATA[
Tony writes: 2024/02/01 Thursday 2.50 #21873 fix, testing on both gcc and MSVC, push for CI 2.50 2024/02/02 Friday 0.72 #21915 review, testing, comments 0.25 #21883 review recent updates, apply to blead 0.97 2024/02/05 Monday 0.25 github notifications 0.08 #21885 review updates and approve 0.57 #21920 review and comment 0.08 #21921 review and approve 0.12 #21923 review and approve
]]>
</summary>
<author>
<name>alh</name>
</author>
<category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
<![CDATA[
<img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br>
<p>Tony writes:</p>
<p>```
[Hours] [Activity]
2024/02/01 Thursday</p>
<h1> 2.50 #21873 fix, testing on both gcc and MSVC, push for CI</h1>
<p>2.50</p>
<p>2024/02/02 Friday
0.72 #21915 review, testing, comments</p>
<h1> 0.25 #21883 review recent updates, apply to blead</h1>
<p>0.97</p>
<p>2024/02/05 Monday
0.25 github notifications
0.08 #21885 review updates and approve
0.57 #21920 review and comment
0.08 #21921 review and approve
0.12 #21923 review and approve
0.08 #21924 review and approve
0.08 #21926 review and approve
0.67 #21925 review and comments</p>
<h1> 2.00 #21877 code review, testing</h1>
<p>3.93</p>
<p>2024/02/06 Tuesday
0.23 #21925 comment
0.52 review coverity scan report, reply to email from jkeenan
0.27 #21927 review and comment
0.08 #21928 review and approve</p>
<h1> 0.08 #21922 review and approve</h1>
<p>1.18</p>
<p>2024/02/07 Wednesday
0.25 github notifications
0.52 #21935 review, existing comments need addressing</p>
<h1> 2.12 #21877 work on fix, push for CI most of a fix</h1>
<p>2.89</p>
<p>2024/02/08 Thursday
0.40 #21927 review and approve
0.23 #21935 review, check each comment has been addressed,
approve
0.45 #21937 review and approve
0.15 #21938 review and comment
0.10 #21939 review and approve
0.13 #21941 review and approve
0.10 #21942 review and approve
0.08 #21943 review and approve
0.07 #21945 review and approve
0.17 #21877 look into CI failures, think I found problem, push
probable fix
0.18 #21927 make a change to improve pad_add_name_pvn() docs,
testing, push for CI
2.20 #21877 performance test on cygwin, try to work up a</p>
<h1> regression test</h1>
<p>4.26</p>
<p>2024/02/12 Monday
0.60 #18606 fix minor issue pointed out by mauke, testing
0.40 github notifications
0.08 #21872 review latest changes and approve
0.08 #21920 review latest changes and approve
1.48 #21877 debugging test
0.30 #21524 comment on downstream ticket</p>
<h1> 0.27 #21724 update title to match reality and comment</h1>
<p>3.21</p>
<p>2024/02/13 Tuesday
0.35 #21915 review, brief comment
0.25 #21983 review and approve
0.03 #21233 close
0.28 #21878 comment
0.08 #21927 check CI results and make PR 21984
0.63 #21877 debug failing CI
0.27 #21984 follow-up
0.58 #21982 review, testing, comments</p>
<h1> 0.32 #21979 review and approve</h1>
<p>2.79</p>
<p>2024/02/14 Wednesday
1.83 #21958 testing, finally reproduce, debugging and comment
0.08 #21987 review discussion and briefly comment
0.08 #21984 apply to blead
0.22 #21977 review and approve
0.12 #21988 review and approve
0.15 #21990 review and approve
0.82 #21550 probable fix, build tests
0.38 coverity scan follow-up
1.27 #21829/#21558 (related to 21550) debugging</p>
<h1> 0.65 #21829/#21558 more debugging, testing, comment</h1>
<p>5.60</p>
<p>2024/02/15 Thursday
0.15 github notifications
0.08 #21915 review updates and approve
2.17 #21958 debugging, research, long comment
0.58 #21958 testing, follow-up</p>
<h1> 0.12 #21991 review and approve</h1>
<p>3.10</p>
<p>2024/02/19 Monday
0.88 #21161 review comment and reply, minor change, testing,
force push
0.23 #22001 review and comment
0.30 #22002 review and comment
0.12 #22004 review and comment
0.28 #22005 review and approve
0.32 #21993 testing, review changes
1.95 #21661 review comments on PR and fixes, review code and</p>
<h1> history for possible refactor of vFAIL*() macros</h1>
<p>4.08</p>
<p>2024/02/20 Tuesday
0.35 github notifications
0.08 #22010 review and approve
0.08 #22007 review and approve with comment
0.60 #22006 review, research and approve with comment
0.08 #21989 review and approve
0.58 #21996 review, testing, comment
0.22 #22009 review and approve
0.50 #21925 review latest updates and approve</p>
<h1> 1.05 #18606 apply to blead, work on a perldelta, make PR 22011</h1>
<p>3.54</p>
<p>2024/02/21 Wednesday
0.18 #22011 fixes
0.80 #21683 refactoring</p>
<h1> 1.80 #21683 more refactor</h1>
<p>2.78</p>
<p>2024/02/22 Thursday
0.38 #22007 review and comment
0.70 #21161 apply to blead, perldelta as PR22017
1.75 smoke report checks: testing win32 gcc failures
0.27 #22007 review updates and approve</p>
<h1> 1.15 #21661 re-check, research and push for smoke/ci</h1>
<p>4.25</p>
<p>2024/02/26 Monday
2.10 look over smoke reports, debug PERLIO=stdio failure on mac</p>
<h1> 1.38 more debug PERLIO=stdio</h1>
<p>3.48</p>
<p>2024/02/27 Tuesday
0.08 #22029 review and apply to blead
0.27 #22024 review and approve
0.33 #22026 review and approve
0.08 #22027 review and approve
0.10 #22028 review and approve
0.08 #22030 review and comment, conditionally approve
0.25 #22033 review, comments and approve
0.08 #22034 review and approve
0.17 #22035 review and comment</p>
<h1> 0.78 #21877 debugging</h1>
<p>2.22</p>
<p>2024/02/28 Wednesday
0.38 github notifications
0.52 #22040 review discussion, research and comment
0.13 #22043 review and approve
0.12 #22044 review and approve
0.72 #22045 review, research, comment and approve
0.13 #22046 review, research and approve</p>
<h1> 1.55 #21877 more debugging (unexpected leak)</h1>
<p>3.55</p>
<p>2024/02/29 Thursday
0.15 #21966 review update and approve
1.18 #21877 debugging</p>
<h1> 0.13 fix $DynaLoader::VERSION</h1>
<p>1.46</p>
<p>Which I calculate is 55.79 hours.</p>
<p>Approximately 70 tickets were reviewed or worked on, and 5 patches
were applied.
```</p>
]]>
</content>
</entry>
<entry>
<title>TPRF sponsors Perl Toolchain Summit</title>
<link rel="alternate" type="text/html" href="https://news.perlfoundation.org:443/post/sponsor-2024-pts"/>
<id>tag:news.perlfoundation.org,2024-05-03:/post/sponsor-2024-pts</id>
<published>2024-05-03T19:49:12</published>
<updated>2024-05-03T19:49:12</updated>
<summary>
<![CDATA[
I am pleased to announce that The Perl and Raku Foundation sponsored the Perl Toolchain Summit 2024 as a Platinum Sponsor. The Perl Toolchain Summit is an annual event where they bring together the volunteers who work on the tools and modules at the heart of Perl and the CPAN ecosystem. The PTS gives them 4 days to work together on these systems, with all their fellow volunteers to hand.
]]>
</summary>
<author>
<name>Makoto Nozaki</name>
</author>
<category term="Perl 5 Development" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
<![CDATA[
<p>I am pleased to announce that The Perl and Raku Foundation sponsored the <a href="https://perltoolchainsummit.org/pts2024/">Perl Toolchain Summit 2024</a> as a Platinum Sponsor. </p>
<p>The Perl Toolchain Summit (PTS) is an annual event where they bring together the volunteers who work on the tools and modules at the heart of Perl and the CPAN ecosystem. The PTS gives them 4 days to work together on these systems, with all their fellow volunteers to hand.</p>
<p>The event successfully concluded in Lisbon, Portugal at the end of April 2024.</p>
<p>If you or your company is willing to help the future PTS events, you can get in touch with the <a href="https://perltoolchainsummit.org/pts2024/sponsors.html">PTS team</a>. Alternatively, you can <a href="https://www.perlfoundation.org/donate.html">make a donation to The Perl and Raku Foundation</a>, which is a 501(c)(3) organization.</p>
]]>
</content>
</entry>
<entry>
<title>TPRC Call for volunteers</title>
<link rel="alternate" type="text/html" href="https://news.perlfoundation.org:443/post/tprc2024vol"/>
<id>tag:news.perlfoundation.org,2024-04-27:/post/tprc2024vol</id>
<published>2024-04-27T11:36:57</published>
<updated>2024-04-27T11:36:57</updated>
<summary>
<![CDATA[
We hope you are coming to in Las Vegas June 24-28! Plans are underway for a wonderful TPRC. But a conference of this type is only possible because of volunteers who give their time and expertise to plan, promote, and execute every detail. We need volunteers! You may have already volunteered to speak at the conference; if so, wonderful! If you are not presenting there are many ways to help.
]]>
</summary>
<author>
<name>Amber Krawczyk</name>
</author> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
<![CDATA[
<img src="_ra-rel-mnt_/simplecas/fetch_content/33d4afce089e16b8dafad78c3d139938bbd71d11/Screenshot 2024-01-03 at 2.21.40â€¯PM.png" style="max-width:100%;max-height:100%;padding:20px;" /><br>
<p>We hope you are coming to [The Perl and Raku Conference[(https://tprc.us/) in Las Vegas June 24-28!
Plans are underway for a wonderful TPRC. But a conference of this type is only possible because of volunteers who give their time and expertise to plan, promote, and execute every detail.
We need volunteers!
You may have already volunteered to speak at the conference; if so, wonderful!
If you are not presenting (or even if you are), there are many ways to help. We need people to set up and take down, to run the registration desk, to serve as room monitors, to help record the talks, and to just be extra hands. If you can spare some of your time for the sake of the conference, please fill out a volunteer form at https://tprc.us/tprc-2024-las/volunteer/ .
We also welcome spouses and friends of attendees who might be coming along to Las Vegas to share the experience. We are offering <a href="https://tprc.us/tickets">TPRC "companion" tickets</a>, for access to the social parts of the conference (food, drink, parties) but not the technical. Volunteers of at least one complete day, who sign up before the conference, will have companion access "comped".
If you have questions about volunteering, please contact our TPRC Volunteer Coordinator:
Sarah Gray <a href="mailto:sarah.gray@pobox.com">sarah.gray@pobox.com</a></p>
]]>
</content>
</entry>
<entry>
<title>Grant Application: RakuAST</title>
<link rel="alternate" type="text/html" href="https://news.perlfoundation.org:443/post/sseifert-rakuas-apr2024"/>
<id>tag:news.perlfoundation.org,2024-04-26:/post/sseifert-rakuas-apr2024</id>
<published>2024-04-26T15:18:56</published>
<updated>2024-04-26T15:18:56</updated>
<summary>
<![CDATA[
Another Grant Application from a key Raku develoer, Stefan Seifert. A member of the Raku Steering Council, Stefan is also an author of several Perl 5 modules including Inline::Python and Inline::Perl6. This Grant is to help advance AST or Abstract Syntax Tree. This is integral to Raku internals and allows designing and implementation of new language components, that can be converted into bytecode for execution by the interpreteter or "virtual
]]>
</summary>
<author>
<name>Saif Ahmed</name>
</author>
<category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/>
<category term="Raku Development" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
<![CDATA[
<img src="_ra-rel-mnt_/simplecas/fetch_content/6f840394561d9857b5504b2cb1df0300d1e2f848/RakuAST.png" style="max-width:100%;max-height:100%;padding:20px;" /><br>
<p>Another Grant Application from a key Raku develoer, <a href="https://metacpan.org/author/NINE">Stefan Seifert</a>.
A member of the Raku Steering Council, Stefan is also an author of several Perl 5 modules including Inline::Python and (of course) Inline::Perl6. This Grant is to help advance AST or Abstract Syntax Tree. This is integral to Raku internals and allows designing and implementation of new language components, that can be converted into bytecode for execution by the interpreteter or "virtual machine" more easily that trying to rewrite the interpretter. Here is an <a href="https://dev.to/lizmat/rakuast-for-early-adopters-576n">excellent intro</a> by <a href="https://liz.nl/">Elizabeth Mattijsen</a></p>
<hr>
<h3>Project Title: Taking RakuAST over the finish line</h3>
<p><img src="_ra-rel-mnt_/simplecas/fetch_content/6f840394561d9857b5504b2cb1df0300d1e2f848/RakuAST.png" style="max-width:50%;" /></p>
<h4>Synopsis</h4>
<p>There is a grant called RakuAST granted to Johnathan Worthington that is still listed as running. Sadly Johnathan has moved on and is no longer actively developing the Rakudo core. However the goal of his grant is still worthy as it is one of the strategic initiatives providing numerous benefits to the language. I have in fact already taken over his work on RakuAST and over the last two years have pushed some 450+ commits which led to hundreds of spectests to pass. This work was done in my spare time which was possible because I had a good and reliable source of income and could at times sneak in some Raku work into my dayjob. I can no longer claim that Raku is in any way connected to my day job and time invested in Raku comes directly out of the pool that should ensure my financial future. In other words, there's a real cost for me and I'd like to ask for this to be offset by way of a grant.</p>
<h4>Benefits to Raku</h4>
<p>This is mostly directly taken from the RakuAST grant proposal as the goal stays the same:</p>
<p>An AST can be thought of as a document object model for a programming language. The goal of RakuAST is to provide an AST that is part of the Raku language specification, and thus can be relied upon by the language user. Such an AST is a prerequisite for a useful implementation of macros that actually solve practical problems, but also offers further powerful opportunities for the module developer. For example:</p>
<ul>
<li>Modules that use Raku as a translation target (for example, ECMA262Regex, a dependency of JSON::Schema) can produce a tree representation to EVAL rather than a string. This is more efficient, more secure, and more robust. (In the standard library, this could also be used to realize a more efficient sprintf implementation.)</li>
<li>A web framework such as Cro could obtain program elements involved in validation, and translate a typical subset of them into JavaScript (or patterns for the HTML5 pattern attribute) to provide client side validation automatically.</li>
</ul>
<p>RakuAST will also become the initial internal representation of Raku programs used by Rakudo itself. That in turn gives an opportunity to improve the compiler. The frontend compiler architecture of Rakudo has changed little in the last 10 years. Naturally, those working on it have learned a few things in that time, and implementing RakuAST provides a chance to fold those learnings into the compiler. Better static optimization, use of parallel processing in the compiler, and improvements to memory and time efficiency are all quite reasonable expectations. We have already seen that the better internal structure fixes a few long standing bugs incidentally. However, before many of those benefits can be realized, the work of designing and implementing RakuAST, such that the object model covers the entire semantic and declarational space of the language, must take place. This grant focuses on that work.</p>
<h4>Project Details</h4>
<ol>
<li>Based on previous development velocity I expect do do some 200 more commits before the RakuAST based compiler frontend passes both Rakudo's test and the Raku spectest suites.</li>
<li>Once the test suites pass, there will be some additional work needed to compile Rakudo itself with the RakuAST-frontend. This work will center around bootstrapping issues.</li>
</ol>
<p>Considering the amount of work these items already will be, I would specifically exclude work targeted at synthetic AST generation, designs for new macros based on this AST, and anything else that is not strictly necessary to reach the goal of the RakuAST compiler frontend becoming the default.</p>
<h4>Schedule</h4>
<p>For the test and spectest suites I would continue my tried and proven model of picking the next failing test file and making fixes until it passes. Based on current velocity this will take around 6 months. However there's hope that some community members will return from their side projects and chime in.</p>
<h4>Bio</h4>
<p>I have been involved in Rakudo development since 2014 when I started development of Inline::Perl5 which brings full two-way interoperability between Raku and Perl. Since then I have helped with every major effort in Rakudo core development like the Great List Refactor, the new dispatch mechanism and full support for unsigned native integers. I have fixed hundreds of bugs in MoarVM including garbage collection issues, race conditions and bugs in the specializer. I have made NativeCall several orders of magnitude faster by writing a special dispatcher and support for JIT compiling native calls. I replaced a slow and memory hungry MAST step in the compilation process by writing bytecode directly, have written most of Rakudo's module loading and repository management code and in general have done everything I could to make Rakudo production worthy. I have also been a member of the Raku Steering Council since its inception.</p>
<h4>Supporters</h4>
<p>Elizabeth Mattijsen, Geoffrey Broadwell, Nick Logan, Richard Hainsworth </p>
]]>
</content>
</entry>
<entry>
<title>Grant Application: Dancer 2 Documentation Project</title>
<link rel="alternate" type="text/html" href="https://news.perlfoundation.org:443/post/crome_dancer2"/>
<id>tag:news.perlfoundation.org,2024-04-18:/post/crome_dancer2</id>
<published>2024-04-18T16:50:55</published>
<updated>2024-04-18T16:50:55</updated>
<summary>
<![CDATA[
We have had a grant aplication from Jason Crome. He is an author and maintainer of a very popular Perl Web Framework familiar to many of us in the Perl community. Dancer 2 has continued to evolve and remains very useful for web application creation. As it besomes more modernised, more robust, and acquired more new features, it has become out of sync with available documentation. A key requirement to
]]>
</summary>
<author>
<name>Saif Ahmed</name>
</author>
<category term="CPAN" scheme="http://www.sixapart.com/ns/types#category"/>
<category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
<![CDATA[
<img src="_ra-rel-mnt_/simplecas/fetch_content/e546abe16d89083567e7862ab68d866c7cb2ad91/dancer 2.png" style="max-width:100%;max-height:100%;padding:20px;" /><br>
<p>We have had a grant aplication from Jason Crome.
He is an author and maintainer of a very popular Perl Web Framework
familiar to many of us in the Perl community. Dancer 2 has continued
to evolve and remains very useful for web application creation.
As it besomes more modernised, more robust, and acquired
more new features, it has become out of sync with available documentation.
A key requirement to realise the usefulness of any project is the availability of resources that enable its use. This includes up to date documents and representative examples.</p>
<p><img src="_ra-rel-mnt_/simplecas/fetch_content/e546abe16d89083567e7862ab68d866c7cb2ad91/dancer 2.png" style="max-width:100%;" /></p>
<hr>
<h2>Dancer2 Documentation Project</h2>
<h3>Synopsis</h3>
<p>Improve the overall quality of the <a href="https://metacpan.org/dist/Dancer2">Dancer2</a> documentation, and ensurethat documentation is up-to-date with recent developments of Dancer2. Create a sample application that follows current Dancer2 standards.</p>
<h3>Applicant Profile</h3>
<ul>
<li>Name: <a href="https://cromedome.net/">Jason Crome</a> <a href="https://metacpan.org/author/CROMEDOME">CromeDome</a></li>
<li>Country of Residence: US</li>
<li>Nationality: US</li>
</ul>
<h3>Benefits to the Perl Community</h3>
<p>The Dancer Core Team ran a survey of its community in 2017, and one of
the items that stood out most was documentation. 33% of our users like
our documentation, 33% are ambivalent, and 33% dislike it. Clearly, that
leaves a lot of room for improvement, and sadly, the state of our docs
hasn't changed much since then.</p>
<p>As reference material, the <a href="https://metacpan.org/dist/Dancer2">Dancer2</a> docs are adequate, but many core
concepts are not explained well or at all. <a href="https://metacpan.org/dist/Dancer2">Dancer2</a> is easy to get
going with, but the documentation doesn't do the best job of
illustrating this. Enhanced documentation is not only good for seasoned
users of Perl and<a href="https://metacpan.org/dist/Dancer2">Dancer2</a>, but also lowers the barrier to entry for less
experienced developers, or developers who are new to building web
applications.</p>
<p>The example application is also a bit of a mess; we've had to patch it
several times to make it correctly work, and it doesn't adhere to
current standards in places. This example should serve as a model of
what a quality <a href="https://metacpan.org/dist/Dancer2">Dancer2</a> app looks like while being a good learning tool.
We don't feel it does either of these well.</p>
<p>We leaned on a tech writer to review our docs, and they provided a list
of suggestions and enhancements to make Dancer2's documentation
friendlier and more approachable, and these suggestions form the basis
of this grant.</p>
<h3>Project Details / Proposed Schedule</h3>
<p>This grant will run for four months, and is organized into the
following segments:</p>
<h4>Months 1 and 2: <code>Dancer2::Manual</code> revamp</h4>
<p>The most intense work of this grant will happen during this first
segment. The core of the manual will be restructured, revised, and
improved. The manual will be structured such that it will first
emphasize how easy it is to build applications with Dancer2 and explain
the fundamental concepts of building Dancer2 applications:</p>
<ul>
<li>A single file ""Hello, World!"" Dancer2 app</li>
<li>Route handlers</li>
<li>HTTP methods</li>
<li>Path patterns</li>
</ul>
<p>From there, the manual will layer on additional concepts, each building
on each other. These sections will align with tasks that developers
will want to accomplish with their Dancer2 apps:</p>
<ul>
<li>Template handling</li>
<li>Error handling</li>
<li>Sessions</li>
<li>etc.</li>
</ul>
<h4>Month 3: Example application; review and edit <code>Dancer2::Manual</code></h4>
<p>The primary task in month 3 is to rebuild the example application such
that it uses all modern techniques and standards for Dancer2
applications. It should be well-written and documented to be the best
learning tool it can be.</p>
<p>Much of the review and editing of the core manual will happen during
this time.</p>
<h4>Month 4: Update and revise the cookbook, deployment, and migration guides; final edits</h4>
<p>In the last segment of this grant, we'll review the cookbook and
deployment guide to ensure they are in the best possible shape. Outdated
information will be updated or pruned; up to date examples will be added
to the deployment guide (Docker/containerization, Caddy, etc.). The
cookbook will be enhanced with new suggestions and recipes, and the
migration guide will be freshened up.</p>
<p>Any remaining time will be used for any final edits that are needed
for this grant can be considered complete.</p>
<h3>Applicant Bio</h3>
<p>I'm Jason Crome, though you may know me as CromeDome (my CPAN handle).
I've been around the Perl community for the better part of 20 years, and
was an active member of the CGI::Application community before becoming a
Dancer Core Developer in 2015. I've served on the TPRF Grants Committee,
first as a voting member and later as its secretary. I'm the organizer
of Charlotte Perl Mongers, and I like puppies and long walks in the
park.</p>
<p>I've been the release manager for Dancer2 for the last 5+ years, and the
loudest/most publicly outspoken member of our community during that
time. I'm constantly in contact with our community, and no one knows our
community quite as well as I do. My extensive knowledge of both the
framework and our community makes me the ideal candidate for this work.
And when I need help or get blocked, I know exactly who to bring in to
help things get going again.</p>
<h3>Funding Request</h3>
<p>$2,800 USD, with half paid two months in, the balance paid upon
completion.</p>
<p>There <em>may</em> be others involved in the writing and editing of the updated
docs; if so, I would coordinate the work and issue any payments to
these parties out of payments I receive from TPF. This would be my
burden to manage; the interface on this project would be between
me and the selected grant manager.</p>
]]>
</content>
</entry>
<entry>
<title>The Perl and Raku Conference: Call for Speakers Renewed</title>
<link rel="alternate" type="text/html" href="https://news.perlfoundation.org:443/post/tprc2024-call-for-speakers-renewed"/>
<id>tag:news.perlfoundation.org,2024-04-16:/post/tprc2024-call-for-speakers-renewed</id>
<published>2024-04-16T17:17:13</published>
<updated>2024-04-16T17:17:13</updated>
<summary>
<![CDATA[
TPRC in Vegas June 24-28. Sign up as a speaker for a free ticket to the conference!
]]>
</summary>
<author>
<name>Todd Rinaldo</name>
</author>
<category term="Conferences" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
<![CDATA[
<img src="_ra-rel-mnt_/simplecas/fetch_content/938a568a36e3d91c43cbbf408496a171b906719d/NeonCamel.png" style="max-width:100%;max-height:100%;padding:20px;" /><br>
<p><a href="https://tprc.us">The Perl and Raku Conference</a> is fast approaching! We will be in <a href="https://www.youtube.com/watch?v=R_ijlnDtKa4">Las Vegas</a> from June 24 to 28 (the main conference is from June 25 to 27).</p>
<p>We want more speakers, so we are reopening the full call for talks/papers/posters. The new deadline is April 20, midnight Las Vegas time (April 21 00:00 UTC). Now that the national eclipse is not a distraction, please consider <a href="https://tprc.us/talks">submitting a talk (50 minute, or 20 minute)</a> or a <a href="https://tprc.us/papers">scientific paper or poster</a> before the new deadline! Speakers will be informed of talk acceptance by April 30.</p>
<p>Talks of 20 minutes or 50 minutes, papers, and posters earn the presenter free admission. Giving a Lightning Talk does not reduce the admission fee but earns our appreciation and delight!</p>
<p>Whether speaker or attendee, we look forward to seeing you in Las Vegas!</p>
]]>
</content>
</entry>
<entry>
<title>Maintaining Perl 5 Core (Dave Mitchell): March 2024 </title>
<link rel="alternate" type="text/html" href="https://news.perlfoundation.org:443/post/maintaining_perl_dave_mitchell_march_2024"/>
<id>tag:news.perlfoundation.org,2024-04-09:/post/maintaining_perl_dave_mitchell_march_2024</id>
<published>2024-04-09T13:03:47</published>
<updated>2024-04-09T13:03:47</updated>
<summary>
<![CDATA[
Dave writes: This is my monthly report on work done during March 2024 covered by my TPF perl core maintenance grant. Less hours than normal last month due to a combination of jury service and the consequences of spending lots of time with my fellow jurors. I spent my time mainly on general small tasks to help get blead into shape for the 5.40 release, such as analysing and reducing
]]>
</summary>
<author>
<name>alh</name>
</author>
<category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
<![CDATA[
<img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br>
<p>Dave writes:</p>
<p>This is my monthly report on work done during March 2024 covered by my
TPF perl core maintenance grant.</p>
<p>Less hours than normal last month due to a combination of jury service
and the consequences of spending lots of time with my fellow jurors.</p>
<p>I spent my time mainly on general small tasks to help get blead into shape
for the 5.40 release, such as analysing and reducing smoke failures, and
fixing bugs.</p>
<p>SUMMARY:
* 1:39 "Variable is not available" warning on nested evals
* 3:44 #21784 BBC: Blead breaks MLEHMANN/Coro-6.57.tar.gz
* 4:15 make stack reference counted - XS
* 2:22 process p5p mailbox
* 1:38 reduce smoke failures
* 1:38 review Coverity reports
* 7:42 rework XS documentation</p>
<p>TOTAL:
* 22:58 (HH::MM)</p>
]]>
</content>
</entry>
<entry>
<title>PEVANS Core Perl 5: Grant Report for March 2024 </title>
<link rel="alternate" type="text/html" href="https://news.perlfoundation.org:443/post/pevans_core_dev_march_2024"/>
<id>tag:news.perlfoundation.org,2024-04-09:/post/pevans_core_dev_march_2024</id>
<published>2024-04-09T07:47:58</published>
<updated>2024-04-09T07:47:58</updated>
<summary>
<![CDATA[
Paul writes: Hours: 2 builtin::is_inf is_nan https://github.com/Perl/perl5/pull/22059 1 Tidying up PADNAMEf_TOMBSTONE https://github.com/Perl/perl5/pull/22063 1 Revert PR 21915 https://github.com/Perl/perl5/pull/22085 2 C99 named initialisers in MGVTBL structs https://github.com/Perl/perl5/pull/22086 4 perl 5.39.9 release https://metacpan.org/release/PEVANS/perl-5.39.9 Total: 10 hours
]]>
</summary>
<author>
<name>alh</name>
</author>
<category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
<![CDATA[
<img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br>
<p>Paul writes:</p>
<p>```
Hours:</p>
<p>2 = builtin::is_inf + is_nan (as yet unfinished)
https://github.com/Perl/perl5/pull/22059</p>
<p>1 = Tidying up PADNAMEf_TOMBSTONE
https://github.com/Perl/perl5/pull/22063</p>
<p>1 = Revert PR 21915
https://github.com/Perl/perl5/pull/22085</p>
<p>2 = C99 named initialisers in MGVTBL structs
https://github.com/Perl/perl5/pull/22086</p>
<p>4 = perl 5.39.9 release
https://metacpan.org/release/PEVANS/perl-5.39.9</p>
<p>Total: 10 hours
```</p>
]]>
</content>
</entry>
<entry>
<title>Maintaining Perl (Tony Cook) January 2024</title>
<link rel="alternate" type="text/html" href="https://news.perlfoundation.org:443/post/maintaining_perl_tonyc_january_2024"/>
<id>tag:news.perlfoundation.org,2024-04-09:/post/maintaining_perl_tonyc_january_2024</id>
<published>2024-04-09T07:43:41</published>
<updated>2024-04-09T07:43:41</updated>
<summary>
<![CDATA[
Tony writes: 2024/01/02 Tuesday 0.18 #21759 review and approve 0.17 #21705 review and approve 0.08 #21736 review and approve 0.33 #21757 review and approve 0.22 #21749 review and approve 0.08 #21778 review and approve 1.43 #21745 review in progress 0.67 #21745 more review and approve, comment 3.16 2024/01/03 Wednesday 0.10 #21761 review and approve 0.32 extract RC_STACK pp_backtick from
]]>
</summary>
<author>
<name>alh</name>
</author>
<category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
<![CDATA[
<img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br>
<p>Tony writes:</p>
<p>```
[Hours] [Activity]
2024/01/02 Tuesday
0.18 #21759 review and approve
0.17 #21705 review and approve
0.08 #21736 review and approve
0.33 #21757 review and approve
0.22 #21749 review and approve
0.08 #21778 review and approve
1.43 #21745 review in progress</p>
<h1> 0.67 #21745 more review and approve, comment</h1>
<p>3.16</p>
<p>2024/01/03 Wednesday
0.10 #21761 review and approve
0.32 extract RC_STACK pp_backtick from an experiment, push for
CI
0.15 #21734 review and approve
0.08 #21739 review and conditionally approve
0.70 #21740 review and comment
0.10 check CI results and make PR 21789
0.05 #21754 review and comment
0.32 #21764 review, research and approve
0.13 #21767 review and approve
0.18 #21769 review, research and comment
0.20 #21770 review, comment and approve
0.15 #21789 follow-up comment
0.10 #21772 review and approve
0.20 #21773 review
0.33 #21773 more review and approve
0.18 #21771 review and approve
0.08 #21776 review and approve
0.10 #21777 review and approve
0.08 #21786 review and approve</p>
<h1> 0.23 #21790 review and approve</h1>
<p>3.78</p>
<p>2024/01/04 Thursday
0.25 github notifications
0.95 list, native data checks, comment on the linked spec
0.30 #21754 review update and approve
0.08 #21792 review and approve
0.08 #21793 review and approve
0.07 #21794 review and approve
1.47 #21791 review, testing, comments, approve
0.18 #21737 re-check and apply to blead</p>
<h1> 0.42 #16608 debugging</h1>
<p>3.80</p>
<p>2024/01/08 Monday
0.18 github notifications
0.08 #21798 review and approve
0.93 #21796 start review, comment</p>
<h1> 2.70 #21796 follow-up, more review</h1>
<p>3.89</p>
<p>2024/01/09 Tuesday</p>
<h1> 0.50 #21796 issue fixed, re-check force pushed commits, approve</h1>
<p>0.50</p>
<p>2024/01/10 Wednesday
0.08 #21808 review and approve
0.47 #21801 review and comment
0.08 #21810 review and approve
0.38 #21805 review discussion and request some info
2.32 #21782 research, comment on CPAN ticket, work on a fix and
push for CI
0.10 #21782 check CI results, make PR 21813
1.25 #21751 research, reproduce on modern darwin, test fix on
modern darwin and push for CI</p>
<h1> 0.47 #21724 research, testing</h1>
<p>5.15</p>
<p>2024/01/11 Thursday
0.52 #21813 apply to blead, perldelta
1.77 review Dave’s XS post to ML, research and comment
0.08 #21751 review CI results and make PR 21818
0.08 #21801 review updates and approve
0.07 #21803 review discussion and ask for some info
0.15 #21815 review and approve
0.33 #21814 review, research and comment
0.25 #15108 work up a small doc update and push for CI</p>
<h1> 0.32 #21814 review updates, research and approve</h1>
<p>3.57</p>
<p>2024/01/15 Monday
1.38 #21821 investigate why bad link didn’t result in an error,
find many similar errors, testing on perldoc.perl.org and
metacpan, fixes, testing and push
0.70 #21820 review and approve
2.65 warnings on win32 gcc builds, testing, research (-Wformat
is broken), push for CI</p>
<h1> 0.18 #21832 review and comment</h1>
<p>4.91</p>
<p>2024/01/16 Tuesday
0.63 review coverity scan results, discuss one with khw,
comment on original pull request for the other
0.80 #21832 review changes, research and approve
0.08 #21837 review and approve
0.75 #21833 review, research and comment
0.25 #21834 review and approve
0.43 #21840 review and approve
0.48 #21824 review code and discussion</p>
<h1> 0.30 warnings on win32 gcc builds: open pR 21842</h1>
<p>3.72</p>
<p>2024/01/17 Wednesday
0.08 #21842 apply to blead
0.33 #21833 review modifications, research, comment and approve
0.43 #21843 review and approve
0.08 #21844 review and approve
1.08 #21091 research based on latest comment and follow-up
comment
0.62 #21550 research</p>
<h1> 0.58 #21550 more research</h1>
<p>3.20</p>
<p>2024/01/18 Thursday
0.35 #21833 research and comment
0.97 look over use VERSION -> builtin thread, review #21850 and
approve
0.08 #21845 review and approve
0.42 #21846 review, research and approve
0.38 #21847 review, consider other comments, comment and
approve
0.15 #21848 review
0.48 #21550 static build detection and testing</p>
<h1> 0.95 #21550 reading code</h1>
<p>3.78</p>
<p>2024/01/22 Monday
0.43 #21833 review updates and approve
0.08 #21853 review and approve
0.13 #21855 review and approve with comment
0.22 #21856 review and approve
0.08 #21857 review and approve
0.13 #21858 review and approve
0.12 #21859 review and approve
0.12 #21862 review and approve</p>
<h1> 0.08 #21863 review and approve</h1>
<p>1.39</p>
<p>2024/01/23 Tuesday
0.90 #21850 review updates and comment
0.13 #21868 review and approve
0.08 #21869 briefly review and approve
0.30 #21871 review, briefly research and comment, brief
discussion, research on #21850 in #p5p</p>
<h1> 0.92 #21872 review</h1>
<p>2.33</p>
<p>2024/01/25 Thursday
1.18 #21872 more review, testing, comment
0.35 #21850 review changes and approve
0.72 #21877 try to reproduce and profile (build issues with -
pg)</p>
<h1> 2.15 #21877 testing, review code, comment</h1>
<p>4.40</p>
<p>2024/01/29 Monday
0.30 github notifications
0.63 #21872 consider builtin implementation vs RC_STACK, find
why it works
0.53 #21874 review and comment
0.15 #21844 review and comment
1.25 #21885 review, research, testing and comment
0.07 #21866 review and approve
0.40 #21887 review, research and comment
0.08 #21891 review and approve</p>
<h1> 2.23 #21877 profiling, review code, comment</h1>
<p>5.64</p>
<p>2024/01/30 Tuesday
0.50 review coverity scan results, work up a fix and push for
CI
1.43 #21877 long comment
0.57 #21884 comment
0.13 coverity scan result follow-up: check CI, open PR #21910
1.55 #16607 also look into handling hwm for xsubs properly,</p>
<h1> find several broken XS, (including EU::PXS generated code)</h1>
<p>4.18</p>
<p>2024/01/31 Wednesday
0.13 #21884 review updates and approve
0.15 #21883 review and approve
0.45 #21873 testing, research and comment
0.32 #21878 research and comment
0.17 #21906 review and apply to blead
0.62 #16607 research, follow-up on related comment on #21872</p>
<h1> 0.45 #21897 review, research and comment</h1>
<p>2.29</p>
<p>Which I calculate is 59.69 hours.</p>
<p>Approximately 88 tickets were reviewed or worked on, and 4 patches
were applied.
```</p>
]]>
</content>
</entry>
<entry>
<title>Registration for The Perl and Raku Conference 2024 is open!</title>
<link rel="alternate" type="text/html" href="https://news.perlfoundation.org:443/post/registration_perl_and_raku_conference_2024"/>
<id>tag:news.perlfoundation.org,2024-03-15:/post/registration_perl_and_raku_conference_2024</id>
<published>2024-03-15T23:13:20</published>
<updated>2024-03-15T23:13:20</updated>
<summary>
<![CDATA[
The Perl and Raku Conference is coming June 24-28. Get tickets to the conference at https://tprc.us/tickets Sign up for a talk at https://tprc.us/talks Take advantage of our special room rate: https://tprc.us/hotel
]]>
</summary>
<author>
<name>Todd Rinaldo</name>
</author>
<category term="Conferences" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
<![CDATA[
<img src="_ra-rel-mnt_/simplecas/fetch_content/61bfc3abfb1d0c3a13bd4889075886d631c23898/TPRC 2024.png" style="max-width:100%;max-height:100%;padding:20px;" /><br>
<p>The Perl and Raku Conference (formerly knwn as YAPC::NA) is going strong! This year, we are celebrating 25 years, our silver anniversary, in the Silver State, Nevada! The main conference will be in Las Vegas on June 25-27, but there will be hackathons and possibly classes on the day before and the day after the conference (June 24th and 28th), so please consider joining us for the whole week!</p>
<p>The backbone of this conference has always been our tracks of "traditional" talks by community members and what we have come to call the "Hallway Track" the informal exchange of ideas and camaraderie that sparks new projects and fuels collaboration.</p>
<p>This year, we are pleased also to host the presentation of Papers and Posters accepted by the Science Perl Journal!</p>
<p>Registration is open, so your ticket can now <a href="https://tprc2024.sched.com/tickets">be purchased</a>. </p>
<p>Talk submissions are still open, and we are seeking proposals on a wide variety of subjects. This includes language features, personal projects, applications like Koha, and anything that may be of general interest to Perl and Raku programmers. (We had juggling and origami in the past. Fun!)
* Talks can be 20 minutes or 50 minutes. Please <a href="https://www.papercall.io/tprclas24">submit through PaperCall</a>.
* <a href="https://science.perlcommunity.org/spj/about/submissions">Papers and Posters</a> follow the guidelines of the Science Perl Journal.
Links to both are also on https://tprc.us.</p>
<p>Speakers who are approved for a talk, paper, or poster will receive a free ticket to the event. The submission deadline is April 5th at 8pm EST, so please send us your submissions soon!</p>
<p>We are planning some special activities during the conference to celebrate our rich 25-year history. </p>
<p>Go now to https://tprc.us/ to check out what is planned and to book a room (see link to <a href="https://tprc.us/tprc-2024-las/location/">Alexis Park Resort under "Location"</a>). Rooms start at only $75 per night, so it’s worth booking early! </p>
<p>The best way to register for the conference is at https://tprc2024.sched.com/tickets</p>
<p>Thanks,
TPRC Admins</p>
]]>
</content>
</entry>
<entry>
<title>Maintaining Perl (Tony Cook) December 2023 </title>
<link rel="alternate" type="text/html" href="https://news.perlfoundation.org:443/post/maintaining_perl_tonyc_december_2023"/>
<id>tag:news.perlfoundation.org,2024-03-11:/post/maintaining_perl_tonyc_december_2023</id>
<published>2024-03-11T08:10:00</published>
<updated>2024-03-11T08:10:00</updated>
<summary>
<![CDATA[
Tony writes: 2023/12/04 Monday 0.42 #21677 minor fix. testing 0.23 #21661 check smoke results, minor commit message edit, make PR 21683 1.90 #21680 testing, debugging 1.28 #21680 fixes, testing, push for CI 1.42 #21651 testing and reproduce, try a fix and testing, push for CI 5.25 2023/12/05 Tuesday 0.30 #21677 research 0.95 #21664 apply to blead, perldelta, comment on original
]]>
</summary>
<author>
<name>alh</name>
</author>
<category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
<![CDATA[
<img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br>
<p>Tony writes:</p>
<p>```
[Hours] [Activity]
2023/12/04 Monday
0.42 #21677 minor fix. testing
0.23 #21661 check smoke results, minor commit message edit,
make PR 21683
1.90 #21680 testing, debugging
1.28 #21680 fixes, testing, push for CI
1.42 #21651 testing and reproduce, try a fix and testing, push</p>
<h1> for CI</h1>
<p>5.25</p>
<p>2023/12/05 Tuesday
0.30 #21677 research
0.95 #21664 apply to blead, perldelta, comment on original
perlmonks post
0.82 #13814 research
0.38 #13814 try a different approach</p>
<h1> 0.62 #13814 get it working, add tests, testing, push for CI</h1>
<p>3.07</p>
<p>2023/12/06 Wednesday
1.07 #13814 review CI results, documentation, testing, make PR
21693
2.48 #21692 review, comments, try to work out getlines()
cleanup
1.52 #21692 finally figure it out, comment
0.13 #21686 testing and comment
0.57 #16535 research and close
0.12 #16529 research and close</p>
<h1> 0.08 #16522 testing</h1>
<p>5.97</p>
<p>2023/12/07 Thursday
0.38 #17457 rebase, retest, push for CI
2.03 #17435 testing, work on a fix, more testing
0.35 #21679 apply to blead, perldelta
0.75 #13814 changes per comments</p>
<h1> 0.10 #17457 check CI results, make PR 21696</h1>
<p>3.61</p>
<p>2023/12/08 Friday
0.35 #21696 apply to blead, update dist/IO/Changes</p>
<h1> 0.25 #13814 apply to blead, perldelta</h1>
<p>0.60</p>
<p>2023/12/11 Monday
0.20 #21684 follow-up
0.72 #21701 research and comment
0.63 #21705 research and comment
0.60 #21702 testing, research and approve
0.08 #21706 review and approve
0.13 #21703 review and approve
0.08 #21699 review and approve
0.08 #21698 review and approve
0.08 #21704 review and approve
0.17 #21700 review and approve
1.03 #21701 testing, research, comment
0.13 #21708 review and approve</p>
<h1> 0.15 #21709 review and approve</h1>
<p>4.08</p>
<p>2023/12/12 Tuesday
1.02 #21712 review the code, testing, comment (not a bug)
0.68 #21684 apply to blead, look at regenning the deps</p>
<h1> 0.23 #21684 more deps</h1>
<p>1.93</p>
<p>2023/12/13 Wednesday
0.27 #21705 research and comment
0.22 #21710 review and approve
2.38 #21714 review and approve, comment
0.27 #21711 review and approve
0.18 #21713 review and approve
0.40 #21676 review and approve</p>
<h1> 2.42 #21684 more deps</h1>
<p>6.14</p>
<p>2023/12/14 Thursday
0.12 #21714 follow-up
1.83 #21701 testing and research, comment</p>
<h1> 0.63 #21684 more deps</h1>
<p>2.58</p>
<p>2023/12/18 Monday
0.42 #21725 debugging, comment
1.38 #21716 debugging. research, comment, work on a fix, push</p>
<h1> for CI</h1>
<p>1.80</p>
<p>2023/12/19 Tuesday
1.08 #21716 minor fixes, testing and comments
0.62 #21725 add comment
0.85 #21719 review, research and comments</p>
<h1> 0.32 #21720 try to understand the diff</h1>
<p>2.87</p>
<p>2023/12/20 Wednesday
0.45 #21723 review, research and approve
0.18 #21726 review, research (alternate openbsd libc anywhere?,
apparently not), approve
0.23 #21728 review and approve
0.58 #21720 review, comments and approve
0.25 #21731 follow-up comment
0.70 #21636 re-work
1.03 #21636 more re-work, testing and push
0.50 #21732 testing and comment, work on fixing the most</p>
<h1> obvious build related issues and push for CI</h1>
<p>3.92</p>
<p>2023/12/21 Thursday
0.08 #21732 review discussion, check CI results and create PR
21737
0.20 #21716 review discussion and comment
0.15 #21719 review updates and approve</p>
<h1> 1.05 #21718 debugging</h1>
<p>1.48</p>
<p>Which I calculate is 43.3 hours.</p>
<p>Approximately 44 tickets were reviewed or worked on, and 5 patches
were applied.
```</p>
]]>
</content>
</entry>
<entry>
<title>PEVANS Core Perl 5: Grant Report for February 2024 </title>
<link rel="alternate" type="text/html" href="https://news.perlfoundation.org:443/post/pevans_core_dev_feb_2024"/>
<id>tag:news.perlfoundation.org,2024-03-05:/post/pevans_core_dev_feb_2024</id>
<published>2024-03-05T12:33:21</published>
<updated>2024-03-05T12:33:21</updated>
<summary>
<![CDATA[
Paul writes: Hours: 1 Allow space in `-M` option https://github.com/Perl/perl5/pull/21935 3 Tidy up remove `builtin` unimport logic https://github.com/Perl/perl5/pull/22002 https://github.com/Perl/perl5/pull/22009 5.5 `use VERSION` restrictions https://github.com/Perl/perl5/pull/21980 https://github.com/Perl/perl5/pull/21997 https://github.com/Perl/perl5/pull/22057 1 class.c bugfix https://github.com/Perl/perl5/pull/21957 2 builtin::numify https://github.com/Perl/perl5/pull/21982 1 Tests for class.c non-ASCII UTF-8 https://github.com/Perl/perl5/pull/21983 1.5 Logical xor operator https://github.com/Perl/perl5/pull/21996 Total: 15 hours.
]]>
</summary>
<author>
<name>alh</name>
</author>
<category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
<![CDATA[
<img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br>
<p>Paul writes:</p>
<p>```
Hours:</p>
<p>1 = Allow space in <code>-M</code> option
https://github.com/Perl/perl5/pull/21935</p>
<p>3 = Tidy up / remove <code>builtin</code> unimport logic
https://github.com/Perl/perl5/pull/22002
https://github.com/Perl/perl5/pull/22009</p>
<p>5.5 = <code>use VERSION</code> restrictions
https://github.com/Perl/perl5/pull/21980
https://github.com/Perl/perl5/pull/21997
https://github.com/Perl/perl5/pull/22057</p>
<p>1 = class.c bugfix
https://github.com/Perl/perl5/pull/21957</p>
<p>2 = builtin::numify
https://github.com/Perl/perl5/pull/21982</p>
<p>1 = Tests for class.c non-ASCII UTF-8
https://github.com/Perl/perl5/pull/21983</p>
<p>1.5 = Logical xor operator (^^)
https://github.com/Perl/perl5/pull/21996</p>
<p>Total: 15 hours.
```</p>
]]>
</content>
</entry>
<entry>
<title>Maintaining Perl 5 Core (Dave Mitchell): January - February 2024</title>
<link rel="alternate" type="text/html" href="https://news.perlfoundation.org:443/post/maintaining_perl_dave_mitchell_january_february_2024"/>
<id>tag:news.perlfoundation.org,2024-03-05:/post/maintaining_perl_dave_mitchell_january_february_2024</id>
<published>2024-03-05T07:44:55</published>
<updated>2024-03-05T07:44:55</updated>
<summary>
<![CDATA[
Dave writes: This is my monthly report on work done during Jan,Feb 2024 covered by my TPF perl core maintenance grant. I spent the last two months mainly on two goals. 1> Understanding XS better so that I can then decide how to update the XS ecosystem to better support a reference-counted stack; as an example, automatically removing the need to call XSUBs via a wrapper in some circumstances. Doing
]]>
</summary>
<author>
<name>alh</name>
</author>
<category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
<![CDATA[
<img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br>
<p>Dave writes:</p>
<p>(this report covers two months)</p>
<p>This is my monthly report on work done during Jan,Feb 2024 covered by my
TPF perl core maintenance grant.</p>
<p>I spent the last two months mainly on two goals.</p>
<p>1) Understanding XS better so that I can then decide how to update the XS
ecosystem to better support a reference-counted stack; as an example,
automatically removing the need to call XSUBs via a wrapper in some
circumstances.</p>
<p>Doing this led me down a rabbit hole of realising how awful our current XS
documentation is. Just about every section I read resulted in confusion,
followed by time out to experiment and/or to look at the ParseXS src code
to try to understand what the documentation was trying to tell me. It's
also very out of date: telling us of exciting "new" features introduced 25
years ago.</p>
<p>The net result of this is that I now have about 1000 lines of notes on
"things to fix in the XS docs". I intend sometime soon to completely
revamp perlxs.pod and perlxstut.pod, based on these notes. Which is a bit
of sidetrack from getting XS working better under PERL_RC_STACK builds.
And doing PERL_RC_STACK was itself initially a sidetrack from doing more
work on perl signatures. Such is often the way when working on perl.</p>
<p>2) General small tasks to help get blead into shape for the 5.40 release,
such as analysing and reducing smoke failures, fixing bugs, and fixing any
Deparse regressions that have crept in over the last year.</p>
<p>SUMMARY:
* 0:38 #21822: BBC: Blead Breaks Variable::Magic
* 1:20 #21876: BBC: 5.39.7 breaks GONZUS/Cache-utLRU-0.002000.tar.gz
* 3:21 #21969: clone-with-stack.t crash
* 2:17 fix Test -deparse failures
* 1:35 fix minitest failures
* 3:39 make <code>__LINE__</code> etc Deparse batter
* 1:57 make stack reference counted
* 30:30 make stack reference counted - XS
* 19:46 process p5p mailbox
* 1:28 reduce build stderr noise
* 8:33 reduce smoke failures</p>
<p>TOTAL:
* 75:04 (HH::MM)</p>
]]>
</content>
</entry>
<entry>
<title>Nominate heroes for the 2024 White Camel Awards</title>
<link rel="alternate" type="text/html" href="https://news.perlfoundation.org:443/post/white-camel-2024-nominations"/>
<id>tag:news.perlfoundation.org,2024-02-21:/post/white-camel-2024-nominations</id>
<published>2024-02-21T17:20:23</published>
<updated>2024-02-21T17:20:23</updated>
<summary>
<![CDATA[
We are seeking nominations for the 2024 White Camel Awards, which honor remarkable non-technical contributions in the Perl community. The Board will consider all nominations and will seek input both from the Advisory Board and the Perl Steering Council. To nominate an individual, kindly complete the form at https://forms.gle/xQczcsRkguvaBDBn8. In light of our community’s growing diversity, we kindly ask that the rationale for each nomination be articulated in a manner
]]>
</summary>
<author>
<name>Makoto Nozaki</name>
</author> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
<![CDATA[
<p>We are seeking nominations for the 2024 White Camel Awards, which honor remarkable non-technical contributions in the Perl community. The Board will consider all nominations and will seek input both from the Advisory Board and the Perl Steering Council.</p>
<p>To nominate an individual, kindly complete the form at https://forms.gle/xQczcsRkguvaBDBn8.</p>
<p>In light of our community’s growing diversity, we kindly ask that the rationale for each nomination be articulated in a manner accessible to those who may not be familiar with the nominee.</p>
<p>For reference, previous recipients of this award can be found at https://whitecamel.org/.</p>
]]>
</content>
</entry>
<entry>
<title>Maintaining Perl 5 Core (Dave Mitchell): November - December 2023 </title>
<link rel="alternate" type="text/html" href="https://news.perlfoundation.org:443/post/maintaining_perl_dave_mitchell_november_december_2023"/>
<id>tag:news.perlfoundation.org,2024-02-20:/post/maintaining_perl_dave_mitchell_november_december_2023</id>
<published>2024-02-20T08:13:54</published>
<updated>2024-02-20T08:13:54</updated>
<summary>
<![CDATA[
Dave writes: This is my monthly report on work done during November-December 2023 covered by my TPF perl core maintenance grant. I mainly continued my work on making the perl stack reference counted. As well as "unwrapping" a few more ops, I also took the opportunity to introduce some basic optimisations to get the speed of a PERL_RC_STACK perl interpreter build back closer to a vanilla build. On my most
]]>
</summary>
<author>
<name>alh</name>
</author>
<category term="Grants" scheme="http://www.sixapart.com/ns/types#category"/> <content type="html" xml:lang="en-us" xml:base="http://news.perlfoundation.org/">
<![CDATA[
<img src="_ra-rel-mnt_/simplecas/fetch_content/7f97282811f6a9f862d7e659c79e5462cc195d94/grant-funding.png" style="max-width:100%;max-height:100%;padding:20px;" /><br>
<p>Dave writes:</p>
<p>This is my monthly report on work done during November-December 2023
covered by my TPF perl core maintenance grant.</p>
<p>I mainly continued my work on making the perl stack reference counted.
As well as "unwrapping" a few more ops, I also took the opportunity
to introduce some basic optimisations to get the speed of a PERL_RC_STACK
perl interpreter build back closer to a vanilla build.</p>
<p>On my most recent branch (rc7, pushed today, 3rd Jan), the average of the
500 or so benchmarks in t/perf/benchmarks under PERL_RC_STACK has the
following instruction read, conditional branches, etc results as compared
to a vanilla perl build. 100% is unchanged, higher is better.</p>
<p><code>
Ir 93.31
Dr 94.54
Dw 93.90
COND 92.50
IND 98.12
</code></p>
<p>Note that the benchmark coverage is not yet comprehensive, and my
optimising efforts will likely have been biased to make these numbers look
better, rather than fixing the ops which aren't yet covered.</p>
<p>I've also made a start into looking at how XS code can be made (at least
sometimes) to work directly under a ref-counted stack, rather than each
XS call needing to be wrapped.</p>
<p>SUMMARY:</p>
<ul>
<li>86:42 make stack reference counted</li>
<li>12:22 make stack reference counted - XS</li>
<li><p>9:33 process p5p mailbox</p>
<p>TOTAL:</p></li>
<li><p>108:37 (HH::MM)</p></li>
</ul>
]]>
</content>
</entry>
</feed>

Home · About · News · Docs · Terms