develooper Front page | perl.perl5.porters | Postings from July 2020

CPAN and the perl plan

Thread Next
From:
Matt S Trout
Date:
July 4, 2020 12:58
Subject:
CPAN and the perl plan
Message ID:
20200704125832.GF20268@vps-6c71e929.vps.ovh.net
Quoth sawyer:
> We also need to talk about CPAN and see what mitigations we need and 
> how. I know there's progress on this front, and I think the right people 
> should report on it.

There is, so far, no progress on this - sawyer and I have agreed that we
need a working group split between perl5 porters, XS specialists, and the
people maintaining the perl toolchain, but we've not got started yet.

While I'm very appreciative that Todd's been spiking some prototype ideas
as an enthusiastic amateur, nothing is at all set in stone at this point.

My default approach here would be to have the primary conversation for the
toolchain/cpan side happen on irc.perl.org #toolchain but I'm aware that
not everybody is as comfortable with IRC as the toolchain maintainers, so
for maximum inclusivity we'll probably want to have things discussed
elsewhere as well.

What do people think of the idea of starting a new IRC channel on freenode
that can take advantage of matrix.org bridging so people who want a client
from this century can join in as well?

If that doesn't work, what other discussion system would?

I'm assuming here that we'd back this up with an issues+wiki only github
repository to create a more durable record of the decision making process
- would we then need a mailing list as well or would people find the github
email interface to issues sufficient for threads?

Also, staffing wise:

My starting point is

CPAN/toolchain:

- ether
- Grinnz (Dan Book)
- haarg (Graham Knop)
- Leon Timmermans
- mst (for my sins)

We'll probably also want input from BinGOs (Chris Williams) and mohawk
on EUMM, and rjbs to keep an eye on anything Dist::Zilla related.

XS insanity:

- LeoNerd (Paul Evans)
- Leon Timmermans again
- ilmari

I'm not sure which perl core committers would want to be involved,
presumably khw since I believe he's already been working in this direction,
but probably other people as well.

Can p5p-ers who want to be included in this please stand up and be counted?

I am, obviously, entirely open to having other people pitch in too, but I
want to make sure we have a solid core of stakeholders and/or people who've
already done plenty of work in this direction since I imagine a lot of the
work is going to be "knowing what won't work and why due to bitter
experience".

Thoughts on process and communications also very much welcome, though I'd
suggest that "accessible via IRC *somehow*" is probably a necessity for any
real time chat approach since that's how things already run.

-- 
Matt S Trout - Shadowcat Systems - Perl consulting with a commit bit and a clue

http://shadowcat.co.uk/blog/matt-s-trout/   http://twitter.com/shadowcat_mst/

Email me now on mst (at) shadowcat.co.uk and let's chat about how our CPAN
commercial support, training and consultancy packages could help your team.

Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About