Re: Discussing Extending the POD Spec

[email protected] ("Paul \"LeoNerd\" Evans") Fri, 22 Sep 2023 12:36:11 +0100
Newsgroups perl.pod-people
Message-ID <[email protected]>
--Sig_/l8AfIyorf+rubBL5QeQOxAv
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Fri, 22 Sep 2023 09:32:35 +0200
Dmitry Karasik <[email protected]> wrote:

> So I agree the process is as clear as
> mud. If the community can resolve this social problem, there are old
> threads about the images in pod and I believe many have still have
> interest in this.

It sounds, therefore, like there's a lack of process at all. It isn't
clear to me whether new additions should happen first in the actual
spec, and we expect implementors to support them, or should actual
implementations just start adding behaviours and we hope to pull them
together into a coherent standard at the end?

Since there is one specification document - being pod/perlpod.pod in
perl core itself - that would feel to be a good place to begin the
process.

Maybe we should begin by raising a PR to change that file, and hope to
get some review comment and general acceptance from people on the
implementation side before proceeding.

Would that work as a process?

--=20
Paul "LeoNerd" Evans

[email protected]      |  https://metacpan.org/author/PEVANS
http://www.leonerd.org.uk/  |  https://www.tindie.com/stores/leonerd/

--Sig_/l8AfIyorf+rubBL5QeQOxAv
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQQACtfoNPkrOD+dkiu8tLZMLxwGjQUCZQ18KwAKCRC8tLZMLxwG
jQ7yAKCrQvjm+XKaLhwMiy2hoIZS9CMxQgCg8BhJeiGiRmYqaJg2j7zW2EAcCmQ=
=APZP
-----END PGP SIGNATURE-----

--Sig_/l8AfIyorf+rubBL5QeQOxAv--