Sure, Since there was already an agreement of having a single wizard as Tom 
already noticed, sorry about that suggestion, I joint the thread a bit 
late, I believe in the below criteria (see my red and blue comments)

- Is the plugin useful, and does it actually work? (Mostly approximated by 
install count) 
   Agree
- Does the plugin integrate well with Jenkins? Does it work well in secured and 
distributed Jenkins? 
   As I already mention "secured" shouldn't pruned any plugins as long as 
those are heavily used by the community and it is an open source version
- Are the features it provides useful to someone fairly new to Jenkins? 
   What do you mean about someone fairly new to Jenkins? Configuration as 
Code (Workflow, JobDSL or jenkins builder) will be fairly complex to 
understand by someone new to Jenkins, even using  you use Workflow, don't 
you think?Then some of those recommended plugins don't follow this criteria.
- Even if it's not popular, is it a reasonably common SCM? (SCM's are so 
fundamental to successful Jenkins use that these shouldn't be as heavily 
restricted as some of the other categories.) 
   Agree

As an example of one of my production jenkins instances, there are a bunch 
of plugins and probably some of them will not part of the recommended list, 
since the above list criteria.

PluginVersionNumber of jobshipchat 
<http://wiki.jenkins-ci.org/display/JENKINS/HipChat+Plugin>0.1.6449throttle-
concurrents 
<http://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin>
1.8.3292rebuild <http://wiki.jenkins-ci.org/display/JENKINS/Rebuild+Plugin>
1.22291timestamper <http://wiki.jenkins-ci.org/display/JENKINS/Timestamper>
1.5.13261build-failure-analyzer 
<http://wiki.jenkins-ci.org/display/JENKINS/Build+Failure+Analyzer>1.13.0254
envinject <https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin>1.90
236mercurial <http://wiki.jenkins-ci.org/display/JENKINS/Mercurial+Plugin>
1.50163build-blocker-plugin 
<https://wiki.jenkins-ci.org/display/JENKINS/Build+Blocker+Plugin>1.6157
heavy-job <https://wiki.jenkins-ci.org/display/JENKINS/Heavy+Job+Plugin>1.1
157mailer <http://wiki.jenkins-ci.org/display/JENKINS/Mailer>1.15150jira 
<http://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin>1.39114git 
<http://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin>2.3.589multiple-scms 
<http://wiki.jenkins-ci.org/display/JENKINS/Multiple+SCMs+Plugin>0.375ws-
cleanup 
<http://wiki.jenkins-ci.org/display/JENKINS/Workspace+Cleanup+Plugin>0.2156
ownership <https://wiki.jenkins-ci.org/display/JENKINS/Ownership+Plugin>0.7
47parameterized-trigger 
<http://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin>2.
2545github <http://wiki.jenkins-ci.org/display/JENKINS/Github+Plugin>1.11.3
26matrix-project 
<https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Project+Plugin>1.624
gradle <http://wiki.jenkins-ci.org/display/JENKINS/Gradle+Plugin>1.2422build
-timeout <http://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin>1.
14.120ant <http://wiki.jenkins-ci.org/display/JENKINS/Ant+Plugin>1.220groovy 
<http://wiki.jenkins-ci.org/display/JENKINS/Groovy+plugin>1.1920conditional-
buildstep 
<https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin>1.
3.316junit <http://wiki.jenkins-ci.org/display/JENKINS/JUnit+Plugin>1.915
chucknorris <http://wiki.jenkins-ci.org/display/JENKINS/ChuckNorris+Plugin>
0.510groovy-postbuild 
<http://wiki.jenkins-ci.org/display/JENKINS/Groovy+Postbuild+Plugin>1.108
copyartifact 
<http://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin>1.318build-
user-vars-plugin 
<http://wiki.jenkins-ci.org/display/JENKINS/Build+User+Vars+Plugin>1.47email
-ext <http://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin>2.38.26job
-dsl <https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin>1.385
postbuildscript 
<http://wiki.jenkins-ci.org/display/JENKINS/PostBuildScript+Plugin>0.165
jenkins-multijob-plugin 
<http://wiki.jenkins-ci.org/display/JENKINS/Multijob+Plugin>1.135ircbot 
<http://wiki.jenkins-ci.org/display/JENKINS/IRC+Plugin>2.255custom-tools-
plugin <https://wiki.jenkins-ci.org/display/JENKINS/Custom+Tools+Plugin>0.
4.44htmlpublisher 
<http://wiki.jenkins-ci.org/display/JENKINS/HTML+Publisher+Plugin>1.44sonar 
<http://docs.codehaus.org/display/SONAR/Hudson+and+Jenkins+Plugin>2.13
subversion <http://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin>2.5
.13ghprb 
<https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin>
1.28.62scriptler 
<http://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin>2.72javadoc 
<http://wiki.jenkins-ci.org/display/JENKINS/Javadoc+Plugin>1.12locks-and-
latches <http://wiki.hudson-ci.org/display/HUDSON/Locks+and+Latches+plugin>0
.62xvnc <http://wiki.jenkins-ci.org/display/JENKINS/Xvnc+Plugin>1.172
findbugs <http://wiki.jenkins-ci.org/x/GYAs>4.562cobertura 
<http://wiki.jenkins-ci.org/display/JENKINS/Cobertura+Plugin>1.9.52feature-
branch-notifier 
<http://wiki.jenkins-ci.org/display/JENKINS/Feature+Branch+Notifier+Plugin>1
.32unity3d-plugin 
<http://wiki.jenkins-ci.org/display/JENKINS/Unity3dBuilder+Plugin>0.72nunit 
<http://wiki.jenkins-ci.org/display/JENKINS/NUnit+Plugin>0.162artifactory 
<http://wiki.jenkins-ci.org/display/JENKINS/Artifactory+Plugin>2.2.41publish
-over-ssh 
<http://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+SSH+Plugin>1.111
dynamicparameter 
<https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Dynamic+Parameter+Plug-in>
0.2.01extended-choice-parameter 
<http://wiki.jenkins-ci.org/display/JENKINS/Extended+Choice+Parameter+plugin>
0.341




On Thursday, 1 October 2015 14:59:36 UTC+2, Daniel Beck wrote:
>
>
> On 01.10.2015, at 08:42, Victor Martinez <victormar...@gmail.com 
> <javascript:>> wrote: 
>
> > Therefore, IMO those categories and recommended plugin as long as they 
> are not part of any Commercial version shouldn't be blocked by those 3 
> "filters", don't you think? I mean, if I was Company who provides a Jenkins 
> enterprise version I shouldn't allow any unsecured plugins for bare things 
> even though it's also based on OSS, but as long as this is an open source 
> version it shouldn't restrict those plugins at all. 
> > 
> > Again, I strongly believe this wizard is a great idea but this approach 
> prunes too much plugins. 
>
> Please provide an alternative list of criteria, or plugins -- right now 
> it's not clear how you'd like to proceed here. Or are you rejecting the 
> concept of a curated list entirely, preferring to show all 1000+ plugins? 
>
>

-- 
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/a29c2bab-1061-4567-9629-a4f3f0b838eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to