I wrote a language-agnostic article and posted it on Medium. Cross posting here for anyone following my Perl posts as well. I hope you enjoy it.
MetaCPAN is the community developed and maintained website and api for finding and learning about Perl modules. This year, we dedicated a long weekend to improving it and oh what a weekend it was!
While I have hung out on the fringes of the p5p and toolchain communities for a few years now, my largest “qualifying” contribution has been Alien::Base, which has largely been handed off to Graham Ollis (plicease). Therefore I was a little surprised but very honored to be invited to the 2016 Perl QA Hackathon held in Rugby, England.
Overall it was an incredible experience. Day after day the energy in the room was palpable. Everyone was creating and improving the code that we would all get to use one way or the other. People hacking on PAUSE and MetaCPAN and CPANTesters, on ExtUtils::MakeMaker, on Test2 and Test::More.
In a future post I will recount the details of my delightful experience at the 2016 Perl QA Hackathon (N.B. now published here). Since this is my first post since that time I do want to tip my hat to the great sponsors of the event and to my own employer ServerCentral without whom I would not have been able to attend. I will thank them in more detail in that post.
Before I get to that however, I want to post a reflection on one discussion that is and has been weighing on my mind since then. That topic is the upcoming release of Test2, which I consider to be a very important step forward for Perl’s testing architecture.
There has been some discussion this week about forks of pieces of Mojolicious. Frustrating discussions over what is proper and how to discourage forking. It has been a long week to be honest (and thankfully the recent incident has been peacefully resolved, see postscript).
But then finally, just today, I’ve chosen to see things a different way. I’m really happy to see what lengths people are willing to go to in order to use Mojolicious. This includes addressing a perceived need for streamlining by taking a maintenance burden onto themselves and forking that code that which they need. They see the value in Mojolicious’ code, if not the value in the toolkit as a whole.
Search this blog
- Cross-post: On the Danger of Software Magicians
- meta::hack 2016
- My Perl QA Hackathon 2016
- Reflections on Test2
- On The Mojolicious Codebase
- Super Easy SSL Certs for Mojolicious Apps
- Get an in-browser remote desktop with Mojolicious and noVNC
- On the Semantic Naming of Things
- Response to The Perl Jam 2
- I'm Thankful for Perl