Add projects below that you're thinking of working on. If you see someone else's project that you'd like to help on, add your name, but email them as well please.
I'm happy to float project to project, usually MetaCPAN and CPANTesters, however I'd like to pursue a project that Paul Johnson (pjcj) suggested right at the end of last year's PTS, to get cpancover to do (near) real-time coverage reports after uploads.
I'm going to focus on grep.MetaCPAN to tackle bugs from the GitHub tracked issues and features list.
Help is always welcome if you are interested.
I want to get the three categories for what we expect from authors regarding the QA of their modules based on the river-position more clear, and integrate that into clear documentation in Release::Checklist
I also want to iron out some problems left in CORE:Configure after commits to that file directly not backported to meta/dist. I'd also like to make progress in bringing down the maintenance burden by discussing the differences with dist/meta and merge what we agree on (needs discussion with Rafael Manfredi)
I want to sit with Abe to check how we can iron out issues with Test::Smoke. My concern here being what to do about *huge* log files.
I'd like to discuss best practices regarding testing ones release against multiple versions of supported modules. e.g. Foo::Bar fixed an issue using Hoo::Blo-0.43's new shiny feature, added tests for it, but does not want to fail for still supported Hoo::Blo-0.42 and older.
version 10 saved on 02/04/18 15:08 by David Golden (xdg)
Home | Tags | Recent changes | History