If the abstract for your module is up to snuff, then have a look at the SYNOPSIS to see whether you could improve that in a CPAN Day release. The SYNOPSIS should briefly show typical usage of the headline features of your module.
Here are some guidelines for a good SYNOPSIS:
Most Perl programmers using named captures in regex probably pick the
(?<NAME>...) syntax, as that's what's displayed more prominently in the Perl documentation and tutorials.
However, Python does not support this syntax and uses
(?P<NAME>...) instead (notice the extra P character). Incidentally, visual regex tool like kiki is built with Python and only support this syntax.
(?P<NAME>...) is also supported by Perl. So if you work with Python or use kiki, you might, like me, want to accustom yourself to using the P syntax.
PCRE (and thus PHP and other PCRE-using languages) supports both syntax. Komodo IDE's Rx toolkit support both. However, Ruby and .NET only support the non-P syntax. Well, that's how the real world works.
So, very recently the excellent Vastyn (Henry Van Styn) pointed out that we should be at the top of git.io:
" I came across our very own Kent Fredric’s GitHub profile today and did a double-take when I read his contrib stats:
# "Year of contributions: 21,996 total
Without even speculating by what kind of dedication/witchcraft this number is even possible, it made me curious about stats in general for GitHub, and some googling turned up this page:
This is a report of the “Most Active” 256 GitHub users. Well, not quite… The current number 1 on the list has HALF the contribs (kevinsawicki at “11,430”).
kentfredric doesn’t show up because of this second caveat: "Only first 1000 GitHub users according to the count of followers are taken. This is because of limitations of GitHub search.
I have app which do some stuff via HTTP/HTTPS. Here it is, already posted about it on blogs.perl.org
There is simple logic:
1) Use http. If user wants https, use https but check that LWP version >= 6 AND LWP::UserAgent->is_protocol_supported("https")
2) Retry HTTP 500 server errors. There can be a lot (coming from server, it's normal)
3) Retry HTTP 500 errors with Client-Warning=Internal response (LWP could raise this in case of conenction problem and socket timeout) with warning "connection problem"
So now I got two reports at once that everything completely broken and HTTPS does not work.
After some investigation I found that:
LWP 6.00 and 6.01:
1) ship LWP::Protocol::https as part of LWP::UserAgent distr, not a separate dist.
2) Do not ship and depend on Mozilla::CA. Instead there is note in docs:
If you're looking for something to release on CPAN day, check the abstract for your modules, and make sure they have a good abstract. The abstract should not only be compliant pod, but should succinctly describe what your module does. The name and abstract are often the first thing that potential users see, so make them count.
We are very proud and delighted to announce the conference schedule!
We've tried our hardest to balance the wealth of topics that our lovely speakers have proposed. But please let us know if you notice any issues with scheduling, as we will be fine-tuning this over the next weeks.
How many releases were done on previous CPAN Days? I know you've been dying to find out, so here are a few graphs, and I'll also compare with the top days in CPAN history. If 100 people each do one release on this coming CPAN Day (16th August, UTC), then it'd be the best CPAN Day yet. If between us we manager 151 releases, that would be the highest day ever.
CPAN and PAUSE record their timestamps in UTC, as all sane systems do. So if you're planning to release on CPAN, please take that into consideration.
The final dependency for Dezi has been released as Dezi::App on CPAN. In addition Search::OpenSearch::Engine::Lucy 0.400 has been released which supports Dezi::App.
Read more about it on the Dezi site.