PTS 2018 Projects
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.
Discussions
Are there things we should discuss this year?
MetaCPAN
- Joel Berger (jberger) floater
- Graham Knop (haarg)
CPAN Testers
- Joel Berger (jberger) floater
PAUSE
CPAN Clients
cpanm 2 (Menlo)
- Tatsuhiko Miyagawa (miyagawa)
Carmel
- Tatsuhiko Miyagawa (miyagawa)
Module installation and testing
Static CPAN installation
Our current installation mechanism is very flexible (in a Turing complete way), but most of the time that isn't necessary. It could be useful if this dependency on shelling out to Makefile.PL/Build.PL could be eliminated where possible.
- Leon Timmermans (leont)
- Tatsuhiko Miyagawa (miyagawa)?
Test::Needs
Extensions for environment, program, internet, threads, etc checks.
- Graham Knop (haarg)
Distribution metadata
ExtUtils::VersionParser
Version extraction from modules. Static parsing or options for evals. To be used by ExtUtils::MakeMaker, Module::Metadata, PAUSE.
- Graham Knop (haarg)
CPAN::Changes
Changelog parser upgrade. Needs downstream testing.
- Graham Knop (haarg)
Authoring Tools
App::ModuleBuildTiny
This the minimalist authoring counterpart to Module::Build::Tiny. It's slowly gaining features and becoming a more complete authoring tool.
- Leon Timmermans (leont)
Perl 6
Perl5 core Configuration
cpancover
- Joel Berger (jberger) 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. This might or might not be organized under the auspices of metacpan
Individual Projects/Goals
Joel Berger
I'm happy to float project to project as needed and available
Nicolas R. (atoomic)
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.
H.Merijn Brand (tux)
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.
abeltje
- Investigate cpantesters reports of failing test suite and fix.
- Normalize the distribution to install in the regular library dirs
- Talk to SawyerX about an old idea to get better info from the smoke-reports, make a start with that
David Golden (xdg)
- Add reCAPTCHA to PAUSE ID request page
- Explore getting MetaCPAN usage data for authors via Google Analytics or web logs
- Address my issue backlog for toolchain modules I maintain
version 19 saved on 03/04/18 20:14 by Leon Timmermans (leont)
Home | Tags | Recent changes | History
