So it is Dist and a little Pod day here in the Dist-Pen.
In my last post I as have a look at the [Availability] section plug-in and ran at a problem when I was trying to get the content for the 'development' info that was promised by the Plug-in.
There where a few issues with my approach. First what I wanted to see was the link up to my github site. I though that this would do it to the 'dist.ini' file;
...
[Bugtracker]
web = https://github.com/byterock/%l/issues
mailto = test@test.com
…
Last month I offered a bold proposal to my Perl Mongers group (MadMongers): Let’s create a video game from scratch as a learning exercise!
At MadMongers we give a talk every month on some area of Perl technology. However, we almost never put those lessons into a practical hands-on form. Yet, we have members who are everything from “I have never used Perl.” to “I have used Perl every day for 20 years.” So my proposal was to build something relatively simple so that we could build it in roughly 12 two-hour sessions over the course of a year, but complicated enough to have real decisions we could make about its design. That way we could put to use skills like using git, creating a CPAN distribution, writing tests, using data storage mechanisms, parsing text, creating user interfaces, making web services, etc.
At YAPC::EU 2010 in Pisa I received a business card with "Rakudo Star" and the
date July 29, 2010 which was the date of the first release -- a week earlier
with a countdown to 1200 UTC. I still have mine, although it has a tea stain
on it and I refreshed my memory over the holidays by listening again to Patrick
Michaud speaking about the launch of Rakudo Star (R*):
R* was originally intended as first of a number of distribution releases (as
opposed to a compiler release) -- useable for early adopters but not initially production
Quality. Other names had been considered at the time like Rakudo Beta (rejected as
sounding like "don't use this"!) and amusingly Rakudo Adventure Edition.
Finally it became Rakudo Whatever and Rakudo Star (since * means "whatever"!).
In my last post I wrapped up the final section [Legal] found in the [@Default] template for Pod::Weaver. Since I am on such a roll I will go on and look at a number of other 'Sections' that available on CPAN.
The first one I am going to look at is [Availability]. This will add an section to you POD that will contain an Availability blurb depending on what you have configured in your 'dist.ini' file.
This plug-in cannot be used stand alone you will have to use both the 'Dist::Zilla::Plugin::Bugtracker' and the 'Dist::Zilla::Plugin::Homepage plug-in in your 'dist.ini' file. Now I have yet to play with these two plug-ins so I will install and then add them to my '.ini' file
I just received a mail from Neil Bowers asking if I would consider having my CPAN distributions be a part of the 2017 CPAN Pull Request Challenge.
My undelayed mental response: Well of course...
I participated in the 2016 Hacktoberfest, I did not contribute much, but I participated and I would have loved to contribute more. These sort of "events" are good, IMHO they bring out the best in open source and they demonstrate the essence of the open source community.
In addition they help tie a community together, so when you are like me; a maintainer of CPAN distributions with very little time, every patch and every PR is most welcome.
A CPAN Pull Request Challenge gives you exactly that.
The CPAN Pull Request Challenge 2017 is soon to kick off, which mean YOU have a chance to benefit from this incredible initiative.
If you have received a mail from Neil respond and be take into consideration for possible PR coming your way or you can tag your issues on Github with the label:
This is the C::Blocks Advent Calendar, in which I release a new treat each day about the C::Blocks library. At the time of writing, we are actually in the season of Christmas, not Advent. I hope you'll forgive these late posts. :-)
Yesterday I used C::Blocks to play around with Perl's C API and mess with keywords. Today I will focus on a couple of neat C tricks that can help clean up the C-end of your library API.
I can see the end soon for POD here in the Dist-Pen but not quite yet.
In my last post I had a real quick look at the [Authors] section plug-in and how the trick to using it is to know that the list of authors comes from your 'dist.ini' file. Today I am going to look [Legal] the last of the sections found in the [@Default] template.
As you can guess this is where
Pod::Weaver
dumps the legal stuff we all love to add to your PODs. Like the [Authors] plug-in this one gets its info from the 'dist.ini' file. In my file I have
As part of the MetaCPAN hackathon, meta::hack, I was invited to work on the CPAN Testers integration. CPAN Testers is a community of CPAN users who send in test reports for CPAN modules as they are uploaded. MetaCPAN adds a summary of those test reports to every CPAN distribution to help you determine which module you'd most like to use. For quite a few months, this integration was broken, and the nature of the current integration (a SQLite database) means it is not as generally useful as it could be.
This was not just a bad year for musicians. Unfortunately not. And the last three months were busy, with lot of (mostly bureaucratic) work. I was expecting the Christmas day to have some extra-time and do, at least one, a decent PR, but I got sick and the will to program just passed by.
So, this semester we had:
October, Perl-Critic-StricterSubs: my patch was to define the minimum required Perl version, as requested by CPANTS.
November, Net-SFTP-Foreign: following CPANTS suggestions, set the same module version for all distribution modules, and declare minimum required Perl version.
December, WWW-Pastebin-PastebinCom-API: generate META.json when building the dist.
I know, not proud of any of these PRs. I said to Neil I want to continue, but I really hope to start being more useful to module authors, or I will just quit...
Still plunking away in the POD world today in the Dist-Pen.
In my last post I had a look a the very simple [Leftovers] section plug-in and how it dumps all unaccounted for POD in the that place on your template. Today I am going to look at another simple one from the [@default] template [Authors]
Looking at the POD for the first time is plug-in one would be quite lost at how to use it. I guess the original POD writer though that is was so simple to use it need no explanation. The trick here is this particular plug-in gets all its info from the 'dist.ini' file. In that file there will be a least one 'author' line as in mine;
Silver Gold Bull is your trusted silver and gold dealer. It provide you with competitive, up-to-minute pricing and make sure your precious metals are delivered to your door discreetly and fully insured.
SilverGoldBull::API provides with the following functionality:
- get all product/order list;
- get full information about product/order;
- or even create and sell your own product;
- and etc.
This is the C::Blocks Advent Calendar, in which I release a new treat each day about the C::Blocks library. Yesterday I compared C::Blocks to other TinyCC-based Perl libraries. Today I will focus on a fun diversion: hacking on the parser with a bit of C::Blocks code.
I must admit that some of yesterday's results have me a bit depressed. I've put a lot of work into this library, and I am really surprised and worried about the performance cliffs I illustrated yesterday. Today, though, we're going to have some fun.
In my last post I had a look at the [Collect] section plug-in and how you can use it to gather up similar parts of your POD in to one section in a document. Useful when you want to keep the POD next to the code but you have a mix of function attributes and subs in the code for other valid reasons.
Today I am looking aI would guess would be the simplest plug-in to use [Leftovers]. As the name implies it dump any Pod that has not been put into another section.
In the case of the [@Default] template it is here;
Your early holiday gift from the Dancer Core Team has arrived - Dancer2 0.204002 is on its way to your favorite CPAN mirror. This release provides the following:
A fix for public_dir: When using public_dir , Dancer2 now waits for the configuration to be read before deciding where static content should be served from
A new plugin helper method, find_plugin(), that lets you import another plugin’s DSL for use in your own custom plugin
A variety of documentation fixes and enhancements
Make sure to check out the Dancer Advent Calendar! It features a number of great articles not only from the Dancer Core Team, but a number of our community members too.
The Dancer Core Team would like to thank all of our contributors and community members for another great year. Simply put, you are the reason we keep working hard at Dancer, and we are grateful to have such a great community of users and developers around us. Here’s to a great 2017… Hope you all have a safe and happy holiday season!
This is the C::Blocks Advent Calendar, in which I release a new treat each day about the C::Blocks library. Yesterday I explained how to use C::Blocks in multithreaded Perl code. Today I will compare C::Blocks to other TinyCC-based Perl libraries.
