<?xml version="1.0" encoding="us-ascii"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>NEILB</title><id>http://neilb.org/atom.xml</id><author><name>Neil Bowers</name><email>neil@bowers.com</email></author><updated>2026-01-14T06:51:40Z</updated><generator uri="https://metacpan.org/pod/XML::Atom::SimpleFeed" version="0.905">XML::Atom::SimpleFeed</generator><entry><title>CPAN Report 2026</title><link href="http://neilb.org/2026/01/13/cpan-report-2026.html"/><id>http://neilb.org/2026/01/13/cpan-report-2026.html</id><summary type="html">&lt;p&gt;This is a look at CPAN activity through the end of 2025,
to see whether CPAN authoring is decreasing, increasing, or holding level.
I&#39;ve done this a few times before, and the general trend has been a steady decline.&lt;/p&gt;
</summary><published>2026-01-13T20:14:28Z</published><updated>2026-01-14T06:51:40Z</updated></entry><entry><title>When asking to adopt a CPAN module please tell me your PAUSE id</title><link href="http://neilb.org/2024/10/28/what-is-your-pause-id.html"/><id>http://neilb.org/2024/10/28/what-is-your-pause-id.html</id><summary type="html">&lt;p&gt;If you&#39;re emailing the PAUSE admin alias (&lt;code&gt;modules@perl.org&lt;/code&gt;),
saying that you want to adopt a module / distribution,
please Please PLEASE include your PAUSE id in your email.&lt;/p&gt;
</summary><published>2024-10-28T10:08:59Z</published><updated>2026-01-14T06:51:40Z</updated></entry><entry><title>CPAN Report 2022</title><link href="http://neilb.org/2023/07/13/cpan-report-2023.html"/><id>http://neilb.org/2023/07/13/cpan-report-2023.html</id><summary type="html">&lt;p&gt;This is a follow-up to
&lt;a href=&#34;https://neilb.org/2022/02/07/cpan-report-2022.html&#34;&gt;last year&#39;s blog post&lt;/a&gt;,
where I posted some charts to show how new CPAN users and distributions
have changed over time.
I meant to post this in January, but was repeatedly ambushed by yaks,
and eventually decided it was too late.
Then Olaf asked if I could show him updated charts with 2022 data,
and I figured I might as well publish a belated report.&lt;/p&gt;
</summary><published>2023-07-13T21:49:43Z</published><updated>2026-01-14T06:51:40Z</updated></entry><entry><title type="html">Creating a CPAN Author&#39;s Guide</title><link href="http://neilb.org/2022/10/07/cpan-authors-guide.html"/><id>http://neilb.org/2022/10/07/cpan-authors-guide.html</id><summary type="html">&lt;p&gt;In the
&lt;a href=&#34;https://neilb.org/2022/02/07/cpan-report-2022.html&#34;&gt;CPAN Report on 2021&lt;/a&gt;
I noted that there has been a steady decline in the number of
new authors, releasing authors, and releases, year-on-year,
for the last 8 years.
In the conclusion, I noted one of the things that I thought would help
is a &#34;manual on how to become a good CPAN author&#34;.
I wonder if we can use Hacktoberfest to get this started?&lt;/p&gt;
</summary><published>2022-10-07T21:29:58Z</published><updated>2026-01-14T06:51:40Z</updated></entry><entry><title>CPAN Report 2021</title><link href="http://neilb.org/2022/02/07/cpan-report-2022.html"/><id>http://neilb.org/2022/02/07/cpan-report-2022.html</id><summary type="html">&lt;p&gt;This is a follow-up to
&lt;a href=&#34;http://neilb.org/2021/03/03/cpan-report-2021.html&#34;&gt;last year&#39;s blog post&lt;/a&gt;,
where I posted some charts to show how new CPAN users and distributions
have changed over time.
I&#39;ve updated the charts to include data for 2021,
and added a new chart to see if it adds anything else to the picture
(spoiler: not really).
The executive summary is that CPAN creation is continuing to decline.&lt;/p&gt;
</summary><published>2022-02-07T22:07:36Z</published><updated>2026-01-14T06:51:40Z</updated></entry><entry><title>Please delete your old releases from CPAN!</title><link href="http://neilb.org/2021/05/10/delete-your-old-releases.html"/><id>http://neilb.org/2021/05/10/delete-your-old-releases.html</id><summary type="html">&lt;p&gt;PAUSE ran out of diskspace this weekend,
so we&#39;re asking everyone to delete old releases
from their author directory.
Every release you do to CPAN stays in your author directory
until you choose to delete it.
Sometimes you might want your old releases to stay available,
but most of the time you could happily delete them (they&#39;re always
available on &lt;a href=&#34;http://backpan.cpantesters.org&#34;&gt;BackPAN&lt;/a&gt;).
Below I&#39;ll explain how you can do this.&lt;/p&gt;
</summary><published>2021-05-10T19:03:12Z</published><updated>2026-01-14T06:51:40Z</updated></entry><entry><title type="html">There&#39;s no such thing as &#34;The Perl Community&#34;</title><link href="http://neilb.org/2021/04/27/perl-communities.html"/><id>http://neilb.org/2021/04/27/perl-communities.html</id><summary type="html">&lt;p&gt;We often talk about &#34;The Perl Community&#34;, but I don&#39;t think it exists.
Instead what we have is a loose,
and at times fraught,
federation of communities.
Over the last few weeks I&#39;ve been thinking and talking about this a lot,
so I wanted to share some of those thoughts, and hear what others think.
This is not me trying to tell you how things are, but how I see things,
and also to outline some things that I think might help us be less fraught.&lt;/p&gt;
</summary><published>2021-04-27T23:02:46Z</published><updated>2026-01-14T06:51:40Z</updated></entry><entry><title>Optional use of modules</title><link href="http://neilb.org/2021/04/04/optional-use-of-modules.html"/><id>http://neilb.org/2021/04/04/optional-use-of-modules.html</id><summary type="html">&lt;p&gt;Sometimes you want to optionally &lt;code&gt;use&lt;/code&gt; a module in your code:
if it&#39;s available, then load it,
but if not, you can still proceed.
I had to do this recently, and used one of the common approaches,
but have been thinking it would be nice if this were easier to do.&lt;/p&gt;
</summary><published>2021-04-04T11:39:24Z</published><updated>2026-01-14T06:51:40Z</updated></entry><entry><title>CPAN River position vs time since last release</title><link href="http://neilb.org/2021/03/23/river-position-vs-age.html"/><id>http://neilb.org/2021/03/23/river-position-vs-age.html</id><summary type="html">&lt;p&gt;As part of the &lt;a href=&#34;http://neilb.org/2021/03/03/cpan-report-2021.html&#34;&gt;CPAN Report&lt;/a&gt;
post I did recently,
I looked at how recently distributions had their last release,
and how that varied with the river position
(number of dependent distributions).
I&#39;ve been playing with some other ideas related to this,
to see if they&#39;ll help identify distributions that could do with some TLC.&lt;/p&gt;
</summary><published>2021-03-23T20:54:46Z</published><updated>2026-01-14T06:51:40Z</updated></entry><entry><title>CPAN Report 2020</title><link href="http://neilb.org/2021/03/03/cpan-report-2021.html"/><id>http://neilb.org/2021/03/03/cpan-report-2021.html</id><summary type="html">&lt;p&gt;CPAN was launched in 1995, so Perl developers have been sharing their
code with each other for more than 25 years.
In this post I&#39;ll share various charts that show how releases
to CPAN have waxed and waned.
I previously did a &lt;a href=&#34;http://neilb.org/cpan-report/&#34;&gt;CPAN Report 2013&lt;/a&gt;,
which as you&#39;ll see below, was when many measures were at or near their peak.&lt;/p&gt;
</summary><published>2021-03-03T09:01:44Z</published><updated>2026-01-14T06:51:40Z</updated></entry></feed>