+1 to just make those plugins without wiki page invisible in the update centre, because their origin and history are unknown.
+1 to minimize plugins categories displayed in the update centre, because several plugins use too many categories (labels in the wiki) including one category for their own plugin (this could be edited directly in the wiki just I have just done for a few plugins). After this, the update centre needs more cleanup. Some plugins are displayed in double because of id changed after release, for example: - Wall display - MobileCloud - PaasLane - SMS Notifications And I suggest that some old and unmaintained plugins may need deprecation or at least a warning sign in the wiki: https://wiki.jenkins-ci.org/display/JENKINS/Proposed+Plugin+Deprecation - Emeric Le mardi 28 avril 2015 20:46:39 UTC+2, Baptiste Mathus a écrit : > > +1 to just make those plugins invisible until they fix those things. > From my experience, the "soft" behaviour just does not work. Plugins > developers will only fix their plugin if it prevents them from being > publicly visible/usable. > > And users will still /suffer/ from this. The requirement we're talking is > not much IMO. > > Or, maybe we could just require having some file inside the repository > itself? > > 2015-04-28 20:36 GMT+02:00 Oleg Nenashev <[email protected] > <javascript:>>: > >> I would alter the UC's behavior in order to consider plugins as >> deprecated if there's no Wiki pages for them (probably with an extra >> whitelist based in jenkins-infra) with a minimal standardised set of >> sections (extra macros to poll poms?). >> >> BR, Oleg >> >> понедельник, 27 апреля 2015 г., 23:51:56 UTC+3 пользователь Daniel Beck >> написал: >>> >>> >>> On 27.04.2015, at 13:36, Christopher Orr <[email protected]> wrote: >>> >>> > It is possible to edit the ignores file in the update centre code [2], >>> but that requires a pull request and getting somebody to merge it etc. >>> >>> They can easily be created within a minute or two on the Github UI, and >>> I'd be happy to review and merge any such PR. (My open PR was mainly to >>> allow community review, I could have committed it directly.) >>> >>> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/9eb9c587-e0b3-472c-a651-6d3d7ce1db64%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/9eb9c587-e0b3-472c-a651-6d3d7ce1db64%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! > -- 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/d2b682ad-fc0c-4ef4-9d23-ed58e4f4d1a1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
