@Stephen +1 for PR as this shows which plugins have no maintainers and plugins in the attic space can possibly be hidden in the available plugins (yes, 1000+ plugins is too much to find which plugins can be useful).
@Kanstantsin Fortunately, the numbers of current installations by plugins are already available and up to date at [1]. These numbers of installations are just waiting for someone to get them and can probably be added to update-center.json [2] by [3] and then displayed in the list of available plugins. [1] http://stats.jenkins-ci.org/plugin-installation-trend/latestNumbers.json [2] https://updates.jenkins-ci.org/current/update-center.json [3] https://github.com/jenkinsci/backend-update-center2 Le mardi 9 juin 2015 16:04:31 UTC+2, Kanstantsin Shautsou a écrit : > > > On Jun 9, 2015, at 16:05, Baptiste Mathus <[email protected] <javascript:>> > wrote: > > > 2015-06-09 14:53 GMT+02:00 Kanstantsin Shautsou <[email protected] > <javascript:>>: > >> >> > On Jun 9, 2015, at 15:47, Baptiste Mathus <[email protected] >> <javascript:>> wrote: >> > >> > +1 Good idea. At first before opening your full message, I thought 3 >> months for last commit would be far too limiting. But the PR idea is very >> cool: simple and to the point. The maintainer can just answer something >> standard or something at all to prevent his plugin going to the attic state. >> > >> > There could even be something like the process posting a second warning >> as a comment after a grace period like "It's been one month, please add a >> comment before blablabla so that that plugins isn't tagged as attic". >> > >> > Btw, there should also be a documented way to move a plugin out of the >> attic (either because you missed the PR, or because a plugin got new >> maintainers). >> >> Why end-user in update center should care about when last commit was >> done? If plugin works and solves user issues - nobody cares and this label >> will just confuse. Some plugins are jut libraries (like github-api plugin) >> and they can be stable for long time, such PRs will look like WTF. >> > > End users are (typically) Jenkins admins. > > Wrong, i know more examples where jenkins is used by developers (just > because not every projects wants stuff jenkins admins because of using > jenkins). And the main problem why jenkins require “admins” (imho of > course) - it complexity, bugs, problems, bad UI. (In comparison to TeamCity > for example). > > I am one of those people. > I totally care about if a plugin is actually abandonned when I install it. > > I always look at the number of installations, and I would definitely > consider that information and find it absolutely valuable. > > Create filters in UC. And filter as you want “> 1k installations, not > abandoned, not assigned, 5 stars rating, etc”. > -- 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/f2acd971-b699-4a59-bab0-c1bf54a436d0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
