I would go one further and aswell as the metadata, create an "attic" update center akin to the "experimental" UC.
It's sometimes daunting for a new admin to find that one plugin that may do what he needs from the 1000+ listed... On Tuesday, 9 June 2015 11:57:47 UTC+1, Stephen Connolly wrote: > > On 9 June 2015 at 11:11, Daniel Beck <[email protected] <javascript:>> > wrote: > >> We should definitely find out which plugins are unmaintained, and try to >> find maintainers for them, so +1 on that. >> >> I'm not sure about some of the details of your proposal (like the 1 month >> period between opening the PR and declaring the plugin unmaintained, or the >> aggressive updating of Jenkins parent versions), but overall it looks >> sensible. >> >> What exactly is the 'attic' status? Does it change anything for the >> plugin, or users of the plugin, other than showing up on the list of >> plugins in the attic? >> > > Maybe we just inject the attic status into the description text e.g. > > > Note I am not picking on the CAS protocol version 1 plugin, just hacking > up a screenshot where I altered the "excerpt" to > > <strong class="warning">This plugin has no active maintainers and has been >> put into the plugin <a href="blah">attic</a></strong><br><br>This plugin >> lets Hudson authenticate users via your organization's Central >> Authentication Service (<a href="http://www.jasig.org/cas";>CAS</a>), for >> single-sign-on. > > > Which works as the excerpt is treated as HTML > > >> >> >> On 09.06.2015, at 10:24, Stephen Connolly <[email protected] >> <javascript:>> wrote: >> >> > In pseudocode: >> > >> > FOR repo IN (SELECT repo FROM github WHERE last_commit < now - 3 months) >> > CREATE PULL REQUEST update base jenkins version to LTS-1 >> > END >> > WAIT 1 month >> > >> > I suggest that any repo that has not commented / merged / rejected >> those pull requests is a dead plugin >> > >> > I suggest that we would subsequently start a campaign to either find >> maintainers or move those into an attic/deprecated status. >> > >> > We can lather rinse and repeat the above process every couple of months. >> > >> > With 1000+ plugins we need to start culling/tidying up the unmaintained >> cruft. >> > >> > I think an "attic" status is a better name for such a cull. It's >> different from deprecated, it's more saying nobody was playing with these >> toys, so we'll put them in the attic until somebody decides to play with >> them again. >> > >> > Thoughts? >> > >> > -Stephen >> > >> > -- >> > 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/CA%2BnPnMwPAD4zLsabwaWTP5t5h1e79KoFu-1XMpkizbn7o66QZA%40mail.gmail.com >> . >> > For more options, visit https://groups.google.com/d/optout. >> >> -- >> 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/C21AFC36-CCD7-4619-9B0D-62B66D674AFB%40beckweb.net >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/be63dd88-7d82-4269-b9fe-5725160d6954%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
