I started a Google Doc to capture proposals and votes https://docs.google.com/document/d/1-8myIWOZZktR0HNtbFIiNA0RfDCvkfKKuNI0C3wcvbo/edit?usp=sharing
On Wednesday, June 17, 2020 at 12:30:47 AM UTC+2, Tammy Fox wrote: > > +1 for allowlist/denylist to be consistent with what other communities are > using. > > I have 3 suggestions to replace Master: > > 1. Director > 2. Expeditor > 3. Coordinator > > Thoughts? I was thinking about what a Master does, and it seems similar to > the Expeditor in a restaurant kitchen. The Master getting build requests > and sending it to the individual build agents is similar to an Expeditor > sending different items to the different food stations in a restaurant. > > On Tuesday, June 16, 2020 at 4:05:58 PM UTC-4 Tracy Miranda wrote: > >> Good discussion on 'master' replacement - listening and learning >> >> On the other terminology I vote allowlist/denylist. >> This is also consistent with other projects communities e.g. >> Rails/Kubernetes >> https://github.com/rails/rails/issues/33677 >> https://github.com/kubernetes/website/pull/21591 >> >> Tracy >> >> >> On Tue, Jun 16, 2020 at 1:30 PM Justin Harringa <[email protected]> >> wrote: >> >>> Conductor is a cool suggestion! >>> >>> On Mon, Jun 15, 2020, 2:49 PM Adrien Lecharpentier < >>> [email protected]> wrote: >>> >>>> I have to say that the music parallel from Angelique seems nice and has >>>> a lot of sense in my opinion. >>>> And the Jenkins butler is not that far from a music orchestrator as >>>> well. >>>> >>>> Le lun. 15 juin 2020 à 22:47, Daniel Beck <[email protected]> a écrit : >>>> >>>>> >>>>> >>>>> > On 15. Jun 2020, at 22:39, Markus Winter <[email protected]> wrote: >>>>> > >>>>> > Second the server is also just plain agent (more or less). For this >>>>> we >>>>> > could use the term "main" as the default label. >>>>> >>>>> That's what I proposed earlier in the thread as well. >>>>> >>>>> 'main' seems reasonable, but still has the connotation that it's >>>>> actually a good idea to use this node, when it rarely is. >>>>> >>>>> -- >>>>> 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/300611FD-062F-40B8-9292-8E16170ABDE6%40beckweb.net >>>>> . >>>>> >>>> -- >>>> 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/CLR55wMZwZ8/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/CAKwJSvwus_DLMT%3Dn2vxwpHya-Cn24qNRU%2B2bDbrKQBOyYL25yw%40mail.gmail.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAKwJSvwus_DLMT%3Dn2vxwpHya-Cn24qNRU%2B2bDbrKQBOyYL25yw%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 [email protected]. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/CAOa798WubmTKAqcV_bKtN0jSVUKNV%3DaSxfhybqPcSP%3D8tqHynA%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAOa798WubmTKAqcV_bKtN0jSVUKNV%3DaSxfhybqPcSP%3D8tqHynA%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a12075ca-48e0-4c55-bc8b-0eee84a210d3o%40googlegroups.com.
