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.
* Salve J. Nilsen (sjn)Â - Update to the CPAN Meta Spec, in light of new legal requirements from different legislators (including the Cyber Resilience Act): https://github.com/Perl-Toolchain-Gang/CPAN-Meta/issues/137
* Salve J. Nilsen (sjn) - Sustainability-related metadata. What metadata can be added to help CPAN projects find new maintainers?
* ...
* Salve J. Nilsen (sjn) - CPANSec as an Open Source Steward, and what it can mean for CPAN and the toolchain
* Salve J. Nilsen (sjn) - Metadata and SBOM requirements from different legislations
* ...
Current CPAN clients have limitations that I believe can not be fixed without fundamentally changing the core of how they resolve dependencies, therefor I think we need a new CPAN client.
* Thorough support for recommended and suggested dependencies (including when they get circular)
* Strong support for parallel installation (and especially parallel downloading versus installing)
* Pluggable support for installing external dependencies
* Policy based decision making (e.g. licensing or security related).
cpantesters has been operating in a degraded state for quite a while. I look forward to working with preaction and others to stabilize the existing systems where possible.
I am particularly interested in bridging the gap between MetaCPAN and other essential toolchain projects such as CPAN Testers and CPANSec, making them more visible and useful to developers.
* Discuss an update to the CPAN Meta Spec, in light of new legal requirements from different legislators (including the Cyber Resilience Act): https://github.com/Perl-Toolchain-Gang/CPAN-Meta/issues/137
* Discuss the role of CPANSec as an Open Source Steward (a new organization envisioned in the Cyber Resilience Act)
* CPANSec tooling, using the DBI project to test them on
* Configure results into SBOM (with @sjn)
* Discuss new possible threat-detections by new gcc behavior
* Discuss having Test::CVE resulst be paprt of CpanTesters results
* Make Devel::Cover work with 5.42
* Get cpancover working fully inside docker and ensure it works across different environments
* Work with MetaCPAN folk on redundancy, backups, running in their infrastructure etc.
* Try to make a dent on github tickets