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‎)

MetaCPAN grep

- Todd Rinaldo (‎toddr‎) - Automate the git grep update process
- atoomic - features & bugs

CPAN Testers

- Doug Bell (‎preaction‎) Migrate remaining backend data processing tasks (CPAN uploads data and per-release rollup data) to Minion for reliability.

- Doug Bell (‎preaction‎) Start writing backwards-compatible replacement APIs for the Matrix that use live data (not cached data) to improve data turnaround time.

- Doug Bell (‎preaction‎) Show new automated test runner project to current testers for feedback.

- Breno Oliveira (‎garu‎) Finish migration of frontend code (CPAN::Reporter, CPAN::Testers::Common::Client, App::cpanminus::reporter) to use the shiny new backend API.

- Breno Oliveira (‎garu‎) Investigate interesting/practical/useful ways to integrate CPAN Testers' data to MetaCPAN.

- Breno Oliveira (‎garu‎) Discuss with Miyagawa the new opportunities of cpantester's integration with cpanm and menlo.

- Joel Berger (‎jberger‎) floater

Blead Breaks CPAN

Provide a way to automate detection of CPAN module failures against blead and report these up to p5p

- Todd Rinaldo (‎toddr‎)
- atoomic

PAUSE

Admin indexing permission

Cf. https://github.com/andk/pause/issues/253 -- this has not moved since the publication of the POM. I want to discuss the issue raised by Kenichi Ishigaki (‎charsbar‎) to maybe iterate the requirements analysis, and if the concept will proceed as specified then I want to get this at least as far as a breakdown of concrete steps to implement. If it gets as far as any code written to take a stab at this, I'll be delirious.

- Aristotle

Dist-oriented permission viewer

Currently we have no really good way to understand the permissions/uploader situation of a CPAN distribution. The MetaCPAN permission viewer is as good as it gets, but if a dist has an even moderately complex history, it's hard to divine exactly what the group of current maintainers actually is. A package/user matrix would make such situations a lot easier to understand at a glance. I want to cobble together a standalone proof of concept and then talk the MetaCPAN people into copying it.

- Aristotle

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‎)

Dist::Build

This is an extensible Build.PL implementation intended as a replacement for Module::Build, release is planned for this PTS.

- Leon Timmermans (‎leont‎)

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

Declarative build system

Last year we created a declarative build system for Perl 6 modules to replace Build.pm. The goal is to avoid turing complete build steps as much as possible which seems to align very well with "Static CPAN installation". This year we should get this into production, i.e. integrate it into zef, write user facing documentation and send out pull requests.

• NINE

meta2rpm

Improve meta2rpm to the point where it reliably creates usable SPEC files for Perl 6 modules and use it to push those to the Open Build Service.

• NINE

make.nqp

Improve make.nqp (a make written in NQP) to the point where it can be seriously recommended to users and shipped as part of rakudo.

• NINE

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

- Paul Johnson (‎pjcj‎) cpancover itself is in need of a little care:

• it has grown such that there is too much data of little value being stored for old CPAN releases
• the filesystem layout needs to reworked to reduce the number of files in directories so that metacpan can backup cpancover
• we need a development environment to safely develop new cpancover features
• and then we still need to properly integrate with metacpan
• Devel::Cover itself has various pull requests and bugs which need to be looked at

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.

I also want to start the "blead breaks CPAN" meta project

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.

I want to sit with Andreas to (re)discuss a patch to App::Cpan that caused the loss of an enourmous amount of time in my update process to 5.26.2: https://tux.nl/Files/App-Cpan-pm.diff

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

Shoichi Kaji (skaji)

• (experimental) Add hook to cpm
• (experimental) Add git support to cpanfile.snapshot
• Make cpm's log cpantester friendly

Tina

• Look at a bug in Test::YAML/Test::Base regarding CPAN::Reporter https://github.com/ingydotnet/test-yaml-pm/issues/3
• Look at some YAML.pm issues, one regarding testing with debugging flags on
• Talk to Joel and Kenishi about Booleans/JSON::PP
• Possibly other YAML stuff

---

version 36 saved on 19/04/18 00:43 by Breno Oliveira (‎garu‎)

Home | Tags | Recent changes | History