On Thu, Jun 20, 2019 at 12:03 AM 'Gavin Mogan' via Jenkins Developers <[email protected]> wrote: > we got to talking about adding github releases info to the wiki, but was > mentioned its probably better to add it to plugins.jenkins.io instead
I think this needs a somewhat broader discussion of what the landing page for a plugin (hosted in @jenkinsci) ought to be. There are two basic kinds of visitors, I would think: · People who want to know general stuff about the plugin—what it does, how to configure it, etc. · Admins already running the plugin who see an update notification inside Jenkins and want to check release notes before accepting. And we have a number of places where content is either defined, displayed, or linked to: · wiki.jenkins.io/display/JENKINS/*+Plugin · `jenkinsci/*-plugin/README.md` · https://jenkins.io/doc/ for certain fundamental plugins. · jenkinsci/*-plugin/releases · plugins.jenkins.io · `jenkinsci/*-plugin/pom.xml#/project/url` · `$jenkins/pluginManager/` Using Confluence is awful in my experience: clumsy to edit, no code review, mediocre speed & reliability, hard to keep in synch with code changes. My inclination is to say that the best practice would be for the `url` ought to point to plugins.jenkins.io, which ought to be (somehow) aggregating `README.md` + `releases`, but that the plugin manager ought to link directly to `releases`. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0U0JAHv%3DqoVz3uT3GxktBvFAtyDn8ka%3DBsqijtjsst0g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
