ribasushi

33
68
68
64
68
68
28
319
56
57

ribasushi

#!/usr/bin/env perl

use warnings;
use strict;

use Carp 'cluck';

sub worker {
  my $ctx =
    defined wantarray.

ribasushi

*.html binary

ribasushi

<p>I can not think of anything qualifying as <i>doesn't have to be a huge Perl project</i>* However, I have an idea which unquestionably will benefit the Perl community immensely, yet has a remarkably low barrier to entry (mainly one thing - patience). I propose that someone applies for a grant in the role of <b>DBIx::Class re-documentation project lead</b>.

<p>I have had inklings of "there got to be a better way to do things", but it wasn't until I read <a href="http://www.perlmonks.org/?node_id=1133234">this meditation by BrowserUK</a> that it dawned at me: Fixing up the better-than-most-but-still-terrible documentation of DBIC is a ~200 person-hour undertaking, which on top of that requires someones fresh eye. Given that DBIx::Class is a "staple-module" in the contemporary Perl ecosystem, I believe it is reasonable to expect for the TPF to "pick up the tab" if someone with the right qualifications steps up.


<p>What is wrong with DBIC's documentation anyway?
<ul><li>Lack of entry level architectural docu

ribasushi

Yet Another Perl Podcast: Perl 7 & Pragmatic Perl & etc.

This is an English transcript of the 17th issue of a Russian podcast Yet Another Perl Podcast, recorded on the 17th of April 2013 and aired on April 28th. The original audio of the podcast is available at its official site. The recording is also available for direct mp3 download.

ribasushi

• A while ago Coro gets a bugreport about XS-level signal handlers and Perl-level signal handlers going out of sync
• Coro's author reaches deep into perl internals to patch this up for the runtime, writes extensive tests for it, fixes the Coro-level manifestation
• in 5.21.8 the hook interface is removed in order to (sic) save 4k of memory PER PROCESS: https://github.com/Perl/perl5/commit/c910fead7893
• A ticket is raised against 5.22.0-to-be, and dies after some discussion: http://www.nntp.perl.org/group/perl.perl5.porters/2015/05/msg228257.html
• The issue is however acknowledged but not much is done to fixing it https://rt.perl.org/Public/Bug/Display.html?id=125439
• As a result Coro as a toolkit can either
  • remove a part of its tests and continue being buggy under a known use scenario
  • refuse to build on 5.21.8+ until either P5#125439 is resolved or c910fead7893 is rolled back
• The author chose the second option (which is exactly what I would do myself in his situation)
• The "stableperl fork"

ribasushi

01c25aa HEAD@{Wed, 25 May 2016 14:42:16 +0200}: rebase -i (finish): returning to refs/heads/master
01c25aa HEAD@{Wed, 25 May 2016 14:42:15 +0200}: rebase -i (pick): grrrrr
a81471f HEAD@{Wed, 25 May 2016 14:19:27 +0200}: commit (amend): Move even more utils into DBIC::_Util (see next commit)
69815c3 HEAD@{Wed, 25 May 2016 14:19:13 +0200}: commit: Move even more utils into DBIC::_Util (see next commit)
890c012 HEAD@{Wed, 25 May 2016 14:13:38 +0200}: cherry-pick: fast-forward
140bcb6 HEAD@{Wed, 25 May 2016 14:13:38 +0200}: rebase -i (start): checkout HEAD^^^^
2774d1f HEAD@{Wed, 25 May 2016 13:03:02 +0200}: rebase -i (finish): returning to refs/heads/master
2774d1f HEAD@{Wed, 25 May 2016 13:03:02 +0200}: rebase -i (pick): grrrrr
890c012 HEAD@{Wed, 25 May 2016 12:54:31 +0200}: commit: Couple lines forgotten during 399b9455
140bcb6 HEAD@{Wed, 25 May 2016 12:53:48 +0200}: cherry-pick: fast-forward

ribasushi

ca62a61 HEAD@{Thu, 28 Jul 2016 15:35:52 +0200}: commit (amend): Merging the ResultSource diagnostics rework
3220bf3 HEAD@{Thu, 28 Jul 2016 15:35:19 +0200}: commit (amend): Merging the ResultSource diagnostics rework
c169503 HEAD@{Thu, 28 Jul 2016 15:06:54 +0200}: checkout: moving from sssss to master
a71b078 HEAD@{Thu, 28 Jul 2016 15:03:45 +0200}: rebase -i (finish): returning to refs/heads/sssss
a71b078 HEAD@{Thu, 28 Jul 2016 15:03:45 +0200}: rebase -i (pick): (travis) Do not retry module installation when running single thread
a115f0d HEAD@{Thu, 28 Jul 2016 15:03:45 +0200}: rebase -i (pick): (travis) cPerl 5.24.0 has shipped
a6b1a4f HEAD@{Thu, 28 Jul 2016 15:03:34 +0200}: rebase -i (continue): Enable the schema SanChecks on 5.8 as well
db18e50 HEAD@{Thu, 28 Jul 2016 15:01:02 +0200}: rebase -i (edit): Enable the schema SanChecks on 5.8 as well
28dc870 HEAD@{Thu, 28 Jul 2016 15:01:02 +0200}: rebase -i (pick): Fix inexplicable 5.8.x C3 errors - roll back e6efde04
c169503 HEAD@{Thu, 28 Jul 2016 15:00:34 +0200}:

ribasushi

From: Peter Rabbitson <ribasushi@cpan.org>
Subject: Upcoming PAUSE permissions dispute
To: modules@perl.org
Message-ID: <272835d7-1fd9-ef0a-ad0e-a62d2995c6e2@cpan.org>
Date: Thu, 15 Sep 2016 04:58:02 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Icedove/45.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

ribasushi

mst_20151207.log:[16:42:22] <mst> aight. what stuff are you going to want me to take on?
mst_20151207.log:[18:06:39] <ribasushi> um... we talked about this - I am not doing an orderly handover
mst_20151207.log:[18:06:45] <ribasushi> so.. nothing? :)
mst_20151207.log:[18:07:03] <ribasushi> am going to be @ LPW, can talk more then if you insist
mst_20151208.log:[15:54:23] <mst> you said on the blog post you'll be transferring maint bits. I'm not asking for orderly, just a heads up as to which things I'm going to wake up on boxing day owning, if anyway
mst_20151208.log:[16:39:12] <ribasushi> that bridge will be burning when I get to it
mst_20151208.log:[16:39:12] <ribasushi> don't worry - I will not land you in a Scwern-like situation
mst_20151208.log:[16:39:12] <ribasushi> but that's about it
mst_20151208.log:[16:44:55] <mst> so, basically "giving warning would stop it being the not-orderly thing you have in mind, but while you're trying to make a splash, you're going to do so without causing carnage" or so