Do you need help with pvp.haskell.org?

[andreasabel]

Is the deployment process to pvp.haskell.org still functional or do you need help with that?

There is a PR that got merged in Jan 2018 that is not on pvp.haskell.org as of today (Nov 2022). So it seems pvp.haskell.org has not been updated for almost 5 years.

• Change diagram to suggest more common numbering progression #20

[Bodigrim]

The PVP 1.0 is supposed to remain immutable. All changes are supposed to land into PVP 1.1 folder to be published in future.

If someone has time and energy to triage and resolve open issues in this repository, I'd be personally very happy to release revised PVP 1.1.

Making a change to PVP requires a vote of CLC and (for breaking changes) of Hackage admins.

[andreasabel]

Thanks for explaining the process, @Bodigrim.

While I agree that such a formal process would be sensible for changing the PVP specification, there certainly could be a more lightweight approach to changing the vulgarization of the PVP, i.e., explaining its workings and implications.
PR #20 fixes a plainly wrong explanation of the PVP, and since it does not get published, folks keep stumbling over it, as witnessed by:

• new version number suggestions seem wrong? #31

TL;DR : For fixing such issues, I do not think that a committee needs to be involved. If the committee thinks otherwise, well, then they should get to work...