In the past, it took two years to merge my first PAUSE on Plack branch into the master and three years to merge the next PAUSE on Mojolicious (actually, two years to deploy and another year to merge). Now the question was: how long would it take to merge the next big thing, multifactor authentication for PAUSE? Two years, three years, or maybe four years this time? I already had a two-year-old draft branch and initially wished to merge it this year. However, things went differently.| blogs.perl.org
Release blocker triage continued, across two days. First we caught up with a dozen of new issues and pull requests, of which we identified one more PR as a small release blocker. The majority of our time was then spent considering each release blocker in depth and updating tickets with decisions and/or requests as we went along. A number of small blockers got resolved even during the course of our extended meeting.| blogs.perl.org
A week ago I attended the 2025 PTS. For me it was a different PTS than the previous ones.| blogs.perl.org
Four years have passed since the last Perl Toolchain Summit (PTS) in Marlow. I planned to continue working on PAUSE's web UI, but I didn't exactly remember what to do. So the first thing I did at home before the...| Kenichi Ishigaki
At the Perl Toolchain Summit 2019 in Marlow/Bisham, I added a feature to manage PAUSE permissions per distribution, which I hope makes it easier for you to grant permissions to other contributors. This was the fifth year of my PAUSE...| Kenichi Ishigaki
At the last two Perl QA Hackathons, I worked on porting PAUSE on Plack, to drop old mod_perl and Apache dependencies and make it easier to set up PAUSE on your local environment. It was successful, but more could be...| Kenichi Ishigaki
Last year at the Perl Toolchain Summit (PTS) in Lyon, I left three draft pull requests: one about the class declaration introduced in Perl 5.37, one about the PAUSE on docker, and one about multifactor authentication. I wanted to brush them up and ask Andreas König to merge some, but which should I prioritize this year?| blogs.perl.org
The 2018 edition of the Perl Toolchain Summit is over! I’ve posted my report from it on my own blog....| Salve J. Nilsen
Every year we bring together the lead developers of the Perl and CPAN toolchain! This event was previously known as the QA Hackathon, but in 2016 it became the Perl Toolchain Summit (PTS) to more accurately reflect the scope and...| Salve J. Nilsen
Maintainers and authors are found everywhere throughout our dependency trees. This includes the authors of the tooling others use for maintaining, building, testing, writing and running the infrastructure they depend on. Even maintainers depend on other maintainers.| Code = Conversation
2023 has been a very Perl-centric year for me so far! | blogs.perl.org