Control plane works but is a mouthfull. Controller works, but as others pointed out, could easily be confused in the k8s world.
the other two (Host and Server) are way too generic to convey meaning if you don't know the system. You could go silly like POTUJ (President of the United Jenkins) or JOTUJ (Jenkins of the United Jenkins). Jenkins Brain Jenkins President Jenkins CEO Jenkins Manager Jenkins Foreman Jenkins Governor Jenkins Super / Super Jenkins Jenkins Taskmaster Jenkins Boss Jenkins Leader Jenkins Overlord A lot came from https://www.wordhippo.com/what-is/another-word-for/controller.html I personally think without the slave context, master is pretty accurate. To be absolutely honest, if it has more syllables than the current, people are super likely to stick with the existing wording (Slave-1 vs Agent-2) cause its easier to say/remember. Gavin On Fri, Jun 12, 2020 at 9:13 AM Jeff Thompson <jthomp...@cloudbees.com> wrote: > My favorite is "Jenkins server" or something like that. There are already > existing usages and it's reasonably explanatory. Something with "manager" > could also work, but I don't find the term as clean and clear. > > Outside of bias issues, one of the problems with whitelist and blacklist > is that the terms don't really say what they do. Sometimes the > interpretation depends on which way you're looking at it. Somewhat similar > to whether a class hierarchy goes up or down. > > "AllowList" and "DenyList" are good matching pairs that convey more > semantics about what they do. > > In other discussions we have noted that not all usages of > whitelist/blacklist fall into the same behavioral meaning. Sometimes we > will need to use different terminology to better convey the meaning. > > Jeff > On 6/12/20 3:20 AM, Oleg Nenashev wrote: > > I am +1 for changing the terminology, and I encourage Jenkins contributors > to participate in this effort. It is not something we could change in a > minute, but we could do a gradual cleanup and improve the overall > documentation while doing so. > > I am -1 w.r.t "host" due to the following reasons: > > - Host term is very generic, it has thousands of usages in Jenkins > https://github.com/search?q=org%3Ajenkinsci+host&type=Code. Choosing > this term will require a careful cleanup to avoid confusion in user > documentation and the codebase > - "agent host" is often used to describe target hosts for outbound > agents > > My suggestion would be to consider a *"Jenkins server"* term. You can see > that such a term is already used in our codebase > <https://github.com/search?q=org%3Ajenkinsci+%22Jenkins+server%22&type=Code>, > website > <https://github.com/jenkins-infra/jenkins.io/search?q=%22jenkins+server%22&unscoped_q=%22jenkins+server%22>and > on 3rd party resources > <https://www.google.com/search?q=%22Jenkins+server%22&rlz=1C1CHBF_enCH837CH837&oq=%22Jenkins+server%22&aqs=chrome..69i57j0l7.2969j0j4&sourceid=chrome&ie=UTF-8> > . > > Best regards, > Oleg > > On Friday, June 12, 2020 at 6:42:34 AM UTC+2, Marky Jackson wrote: >> >> It is a suggestion for consideration if you would like. >> >> On Jun 11, 2020, at 9:35 PM, Richard Bywater <ric...@bywater.nz> wrote: >> >> >> Good point. I actually wonder if Manager is a reasonable replacement? >> >> On Fri, 12 Jun 2020 at 16:04, Marky Jackson <marky....@gmail.com> wrote: >> >>> The concern with controller may be a conflict with Kubernetes on Jenkins >>> given the same name. This was originally my suggestion but than I >>> remembered I was also part of renaming in that community. >>> >>> > On Jun 11, 2020, at 9:02 PM, Richard Bywater <ric...@bywater.nz> >>> wrote: >>> > >>> >> -- >> 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 jenkin...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcrbnGua2b3sHamE2AG1r3z8cXBxA02%2B4NrQHMWqQjzyg%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcrbnGua2b3sHamE2AG1r3z8cXBxA02%2B4NrQHMWqQjzyg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> -- > 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/4ffdf650-4bb4-4878-a629-4e49c3ac06b5o%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/4ffdf650-4bb4-4878-a629-4e49c3ac06b5o%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > 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/e024d4a9-09e1-ff95-3bbc-a35d486e21ed%40cloudbees.com > <https://groups.google.com/d/msgid/jenkinsci-dev/e024d4a9-09e1-ff95-3bbc-a35d486e21ed%40cloudbees.com?utm_medium=email&utm_source=footer> > . > -- 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/CAG%3D_DuuE1g6-xW0DtSjYsv9F%2B-WNmv-WUrtM68nbZPWK%3DdfJ5w%40mail.gmail.com.
