search

haskell / pvp

Haskell Package Version Policy (PVP)
http://pvp.haskell.org/
38 stars 25 forks source link

remove misleading "suggest changes" link #62

Open mauke opened 2 months ago

mauke commented 2 months ago

At the bottom of https://pvp.haskell.org/#related it says:

If you'd like suggest changes, please open an issue on GitHub.

But that doesn't do anything in practice because changes suggested on github are only made on Github; they don't make it to the website. For example, PR #20 from 2018 contained a bugfix that corrects a nonsensical suggestion in the flowchart diagram, but the website still hasn't been updated.

In practical terms, there is no way to get changes into the published PVP, so the Github issue suggestion should be removed.

tomjaguarpaw commented 2 months ago

Isn't this proposal self-defeating? If your suggested change ever makes it to the website then that can only be because we've found a way of making changes to the GitHub repo make it to the website!

I suggest we just work out how to deploy changes to the website.

gbaz commented 1 month ago

The clc has day-to-day responsibility over the PVP. Whenever it wants to publish a new version, it should request the admin team help. Also we'd be happy to set up a more consistent sync if preferred.

Bodigrim commented 4 days ago

@gbaz I think the easiest way to sync would be to set up GitHub Pages for this repository and point pvp.haskell.org to them. Does it sit well with you?