Hey Daniel, thanks for clarifying. I'm on vacation this week but keen to see us come to some consensus on this. I agree with Gus too ... I think the main thing we need to get agreement on here is on the question of if we unbundle plugins and provide a wizard to make sure new users are not confronted with an unusable Jenkins. I think we can figure out the details of how that should happen (the implementation) in a PR and in conversations, so wouldn't get too hung up on that.
Sent from my iPhone > On 27 Aug 2015, at 19:23, Daniel Beck <[email protected]> wrote: > > After discussion with Tom and Gus I changed parts of the chapter "The Jenkins > Distribution (jenkins.war)" that were referring to essential plugins, as none > of the plugins are required for Jenkins to properly work -- they just extend > its functionality. > > Jesse (and everyone who read the first revision), could you please take > another look? > >> On 27.08.2015, at 20:01, Gus Reiber <[email protected]> wrote: >> >> Fair enough. >> Daniel is offering the same concerns and it seems the doc isn't clear enough >> on exactly how we intend to do away with the notion of essential plugins and >> completely unwind the current notion of bundled plugins. Fixing exactly what >> we don't like about bundled plugins will be the primary goal of our PR. >> Daniel is going to help add some clarity to the doc. >> >> My hope is still that, in general, the consensus here is that we are doing >> the right thing removing or at least diminishing bundled plugins, and adding >> a GUI selector so that users can choose which plugins they start using. >> >> On Thu, Aug 27, 2015 at 9:53 AM, Jesse Glick <[email protected]> wrote: >>> On Thu, Aug 27, 2015 at 11:37 AM, Gus Reiber <[email protected]> wrote: >>> "detached" plugins >>> that are essential to Jenkins but have been implemented as plugins for >>> quicker updates and ease of implementation. >> >> Split plugins are just plugins, which by definition are not >> “essential” to Jenkins. They may be very useful and commonly desired, >> or they may be obscure, but you can always disable them. (Even bundled >> plugins, though these cannot be _uninstalled_.) >> >>> Of the optional, feature style plugins >> >> I.e., just “plugins”. >> >> I am not trying to split hairs here, but to emphasize again that split >> plugins deserve no special status when deciding which plugins ought to >> recommended to new users. Each plugin should be evaluated on its >> intrinsic merits, not historical inclusion in core sources. Some >> examples to illustrate my point: >> >> * `ssh-slaves` (split, currently bundled): used in most larger >> installations, probably good to recommend. >> * `windows-slaves` (split, currently bundled): useful in some >> Windows-based installations but often hard to troubleshoot compared to >> JNLP slaves; debatable. >> * `external-monitor-job` (split, currently bundled): somewhat exotic >> use case, probably best omitted. >> * `credentials` (dependency of splits, currently bundled): should be >> recommended to all users. >> * `git` (not currently bundled): good to recommend to new users, at >> least until we have an SCM selection wizard. >> * `chromedriver` (not currently bundled): useful for a small number of >> users, but too obscure to be recommended. >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Jenkins Developers" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/jenkinsci-dev/kRobm-cxFw8/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1gp9VGUkpw0P%2BKVd3iq7JNaY1%2BrWcZzesaGefTXJUCkA%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]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAOcHHXx7%2Bti3ojyqvcTZW4K5pwtHDgR%2BBjTGSZtUsnP2dDeiow%40mail.gmail.com. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/kRobm-cxFw8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/F397B8F7-7195-4F4A-B3FA-E9E933E0CAAF%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/C13958A8-9D73-454D-A464-48B6B9001C34%40gmail.com. For more options, visit https://groups.google.com/d/optout.
