On 24.02.2016, at 13:05, Victor Martinez <victormartinezru...@gmail.com> wrote:
> What about docker plugin? It might be a good candidate as part of the plugin > selection as it's widely used and might alienate the concept of > reproducibility and configuration, which are nowadays quite trendy, with > Jenkins. This is an interesting question, and one I wanted to explore once the initial plugins selection is defined: Could we actually manage to curate a more opinionated list? Given how the initial discussion last year went, I had my doubts -- hence this reboot that started out with a set of rules/guidelines, rather than a proposed list of plugins. I think the result could be much better, if we were to actually build a list based on our collective experience with Jenkins. The risk of course is that we're not getting anywhere, as our varying experiences using Jenkins color our opinion what plugins are a "must have". I'm not excluding myself here -- I noticed this with a few plugins I included in the original list, that, when viewed critically, weren't nearly as universally useful as I first considered them to be. ---- That said, I suggest we continue with the current approach of a mostly popularity based list, excluding unmaintained and unsuitable plugins, for now. So please, provide some more feedback on it, and maybe think about ways to make the above work. -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1C2691DD-F00D-43B7-867C-FC8E230985E9%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
