> 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?
If that is a question to me personally I'm flexible and everything is good as I
believe that the process is for people, not the vice versa. However, I believe
that I'm the wrong person to ask about this. I would stick to your original
proposition about the social aspect, how to make sure that the PR will get
attention of the people with the commit flag, will not get ignored, and the
discussion of a new feature won't result an a yet another stonewalling. And
also how to make sure that if there is an agreement that the feature, the PR
merging _will_ follow and will not be "forgotten".
As for the technicalities, part of my PR was a separate Image.pod dedicated
just for this aspect, so that perlpod.pod could just refer to that file, if
anything.
--
Sincerely,
Dmitry Karasik
