Re: POD formatter version comments

[Karen Etheridge]

On Wed, Mar 20, 2024 at 2:28 AM Graham Knop  wrote:

> On Fri, Mar 15, 2024 at 7:55 PM Shawn H Corey  wro
> I guess I wasn't clear. I was talking about making the requirement an
> option for the formatters. When the user runs a formatter, they can specify
> an option to include the info in their output. In other words, move it from
> a requirement to an optional implementation for a formatter.
>
> Formatters can implement whatever options they want, and can output
> however they want. What is the purpose of stating this specific option
> as something they can do? It can't be standardized, because it will
> inherently be dependent on the output format.
>

 I believe the paragraph in the docs should stay, but change the MUST to a
SHOULD, with a proviso that there should be a way to disable it (for the
purposes of repeatable builds etc). If the paragraph is removed entirely,
no one will implement it (the fact that it is not well-implemented now is
sad, but beside the point). I have no strong feelings as to whether the
option should default to on or off, but the option should exist for those
that wish this extra content.

Re: Increasing podlators Perl dependency to 5.12

[Karen Etheridge]

On Sat, Mar 16, 2024 at 6:22 PM Russ Allbery  wrote:

> I wanted to provide some advance notice that I plan to increase the
> minimum Perl dependency for podlators (Pod::Man and Pod::Text) to 5.12
> from 5.10 in the next release.
>

Sounds good to me; I appreciate the heads up!

It's worth noting that at last year's Perl Toolchain Summit (PTS) there was
a consensus agreement to raise the maximum-minimum required Perl version to
5.16 (that is, critical toolchain modules MAY raise their minimum version
requirements to as high as 5.16, but will not do so arbitrarily), and this
value will be raised to 5.20 after the release of Perl 5.40 a few months
from now. (ref: https://rjbs.cloud/blog/2023/05/pts-2023-lyon-amendment-2-5/
)

...My goal is to eventually get to at least Perl 5.24 so that I can use
> postfix dereferencing.
>

For the 'postderef' feature (and for sub signatures too, my other favourite
and oft-used feature), 5.20 should be sufficient for most things; you may
want to consider stopping there for a bit.

Re: podlators 5.00 released

[Karen Etheridge]

On Fri, Dec 30, 2022 at 5:10 PM Leon Timmermans  wrote:

> I guess p5p would have been the most obvious place to have this discussion
> in this particular case. Toolchain doesn't really do email for some reason.
>

We do, somewhat... cpan-workers and module-authors are reasonable lists to
use. However, lately some email lists have been getting deleted without
warning so it's hard to know whether we can trust that these will remain
alive.

Re: Which Pod module should be used / subclassed?

[Karen Etheridge]

Have you looked at Pod::Weaver? It's usually used as part of
Dist::Zilla, but it absolutely can be used on its own, and it's great
for parsing pod documents into separate pieces. I'm also a big fan of
Pod::Simple.

On Sun, May 5, 2019 at 3:59 PM Harald Jörg  wrote:
>
> Hello Pod-People,
>
> I hope that I don't start a religious war with this question.
> I found this mailing list advertised in the Pod::Simple docs, so I would
> accept a bias towards Pod::Simple based solutions :)
>
> So here's what I want to do: Extract Pod from a bunch of (ca 100) Perl
> modules and Pod files and convert it to HTML.  Or XHTML.  Anything good
> for today's browsers is fine.  Sounds pretty TIMTOWTDI, but every way
> I've tried so far has minor issues, and I've some requirements for which
> I haven't found an existing solution yet.
>
> The issues are rather harmless:
>
>  - Pod::POM is what's used today in the software to create the HTML
>docs.  It fails to process Lhttps://www.perl.org>
>links correctly.
>
>  - Pod::Simple::HTML produces invalid HTML (nested 'a' elements) when a
>heading or item contains a Link like this:
>
>  =head1 Start at L
>
>  - Pod::Simple::XHTML apparently makes no effort to find content for the
> element (nor does core pod2html, BTW).
>
> And there are a few things I miss.  They could be implemented in a
> subclass of either of these, or even provided as an enhancement via Pull
> Request:
>
>  - A custom link resolver: I want links to documents within the project
>to be relative, but link to other CPAN modules to be
>absolute. Preferably to metacpan.org instead of search.cpan.org.
>
>  - A custom table of contents
>
>  - Custom (or just different) backlinks to top of page
>
>  - Decent heuristics for page titles (Pod::Simple::PullParser does that
>marvelously)
>
>  - ...and some more, but not enough to roll out my own converter.
>
> So, which if the modules is considered "state of the art" by the Pod
> People?  Which one of them is least likely to be deprecated?
>
> Do others have similar requirements?
> --
> Cheers,
> haj

Test::Pod and friends are up for adoption

[Karen Etheridge]

https://justatheory.com/2018/05/adopt-my-modules/

Test::Pod and Text::Markup::Pod are on this list.

(I'm happy to be a comaint, but I lack the bandwidth to become primary
maintainer.)

-et...@cpan.org

can Pod::Readme join the pod-people collective?

[Karen Etheridge]

Hi pod-people,

I've recently acquired PAUSE comaintainership of Pod::Readme and am
interested in doing a few small maint releases to fix some low-hanging
fruit such as prerequisites and installation tooling, but it needs more
love than I have time (or knowledge of Pod::* architecture) for.  I've been
in contact with the authors of Pod::Readme, David Precious and Robert
Rothenberg, about the future of this module -- would it be possible to move
it under pod-people's umbrella?

The repository currently lives at https://github.com/bigpresh/Pod-Readme --
in order for it to be transferred to
https://github.com/pod-people/Pod-Readme, David Precious would need to be
added as an admin of pod-people. Is this possible to do (either temporarily
or permanently)?  I'm a regular member of the pod-people organization but
do not have admin rights so I cannot take the repo and then add it myself,
nor add David to the admin list.

I've cc'd both David and Robert on this message in case there are more
details to hammer out.  I'm also on irc, pingable during (western
hemisphere) waking hours.

thanks!

Karen Etheridge (ether)
et...@cpan.org