PSC #086: 2022-11-11

Porters,

Philippe and Paul and I met on Zoom today.  Here's what we talked about.

*What can we do to make things easier for new contributors?*  Philippe was wondering about improving perlguts, perlinterp, perlhack, and perlapi.  Paul was not sure this would pay off, because there are so many areas that someone might show up and want to work on.

Another question that came up was, "Is the existing state of things worse than nothing?"  Paul ended with, "I'm the wrong person to ask, because this document wouldn't be targeting me."  Rik had a similar take.

"It's easier to answer specific questions.  Write me the first page and I'll write you the rest of the book."  Anyway, this is a conundrum we've discussed many times.

*Smartmatch!*  Philippe has been sending patches to people whose CPAN libraries will be affected.  We discussed autodie at some length, which is core and generates code that uses ~~.  We believe this can be fixed, but it needs some more work than we could give it on the call.

*Announcements?*  When we have things to announce like "smartmatch is being formally deprecated", where should we post these things?  "Well," said Paul, "until last week I was thinking Twitter…"

But what place can people best get the simple updates?  p5p is more than many want it.  blogs.perl.org and RSS aggregators are not, we think, really well read.  Probably the current answer remains "Every week we post the PSC updates to blogs.perl.org and tweet a link to that."  Extra announcements get an extra post.

*Other news:*  "use feature 'module_true'" is now in core and in the v5.38 feature bundle!  RFC 13, for overloading in concatenation and join, is looking good and now only waiting on substr?

-- 
rjbs, LeoNerd, and BooK

• PSC #086: 2022-11-11 by Ricardo Signes
• Re: PSC #086: 2022-11-11 by Oodler 577 via perl5-porters