Hi Gus, I really like the idea. As a Jenkins user I really would like to have such "marketplace" where we can easily find in a unified way all data about our plugins. This is really an important stuff to have from my POV for our users and I would love to have a similar stuff in Jenkins itself in the plugins manager.
I don't know how I could help but for sure I'm supporting this Arnaud On Tue, Jun 14, 2016 at 9:57 PM, Gus Reiber <[email protected]> wrote: > Hey all, > So I have on and off pushed the idea that the Jenkins community could > benefit greatly from an overhaul of the wiki based plugins site. As an > ultimate goal, I don't see any reason we couldn't build something that > approach a modern app store, like https://play.google.com/store, but for > the short run, it seems like we should be able to improove upon the > browsing experience of the existing list page and detail view. > > Existing: > > - list: https://wiki.jenkins-ci.org/display/JENKINS/Plugins > - detail: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin > > I think as a minimum, we ought to be able to provide a reasonable search > interface and means of filtering plugins by maintainer, Jenkins core > requirement, plugins labels, and installation count. Plugins should also be > assigned to categories that map to Jenkins user expectations a bit better > than the current list of ~30ish maintainer assigned labels do today. > Ideally the user ought to be able to manage the list of all plugins by > specific features of the plugin and by some suggestion of quality or > currentness of the plugin. > > At various points, my interest in bringing this value to the community has > been great enough to assemble a couple of different prototypes and > wireframes, attempting to generate interest. I have also had a chance to > play with some prototypes from others all with what seems to me to be > reasonable implementation paths. Attached are a few more recent sketches > showing the gist of how we might handle searching and filtering as well as > the plugin details. > > Anyway, at the moment, the plugin site is maintained by our > representatives here in the community. So it is really the will of the > community that should be reflected in any efforts that are actually > deployed and later maintained by our community. Thus again, I am looking > for grass roots support for the effort, support that potentially includes > some avenue for long term hosting and support. > > So my questions are these: Is enhancing the plugin site really worth that > degree of effort to the community? If you think it is, would you be willing > to join the effort, both for the immediate development needs, but also for > longer term support? Do you have any experience with other communities who > manage to accomplish this sort of ends? > > ...and finally, could you help articulate a set of minimum requirements > that would make overhauling the plugin site worth while? > > Thanks in advance, > Gus > > > > -- > 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/11a2687d-254a-4fa8-b9e5-50e5c40ff8d3%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/11a2687d-254a-4fa8-b9e5-50e5c40ff8d3%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- ----- Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier -- 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/CAFNCU-98iBObDf-Gzp6RW7vegAs9L8QdL_QiAP8ssr_Xyk3B5A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
