I don't really ever weigh in on things but this time I'd like to.
I think its safe to say no one wants anything with a space or special
chars, due to obvious technical issues.
In that vein, 'Jenkins Server' could have such technical implications plus
it is very broad.
So we're left with one word alternatives, so here's a short list of me just
brain storming a little:
- controller (this is my favorite but I think someone objected a while
back)
- commander
- coordinator
- leader (a bit of a stretch)
- primary (sounds ok to me - 'primary node', 'agent node', etc.)
- first
- main
Most of these (with the exception maybe of 'commander' and 'leader')
already appear in the vernacular & are well known.
My vote is 'controller' or 'primary'.
Thanks,
Ben
On Sat, Jun 13, 2020, 5:47 PM Slide <[email protected]> wrote:
> Yes, the whole point of this thread is for discussion of all aspects,
> including all the technical issues that we will have.
>
> On Sat, Jun 13, 2020 at 2:18 PM Mark Waite <[email protected]>
> wrote:
>
>>
>>
>> On Sat, Jun 13, 2020 at 3:04 PM James Nord <[email protected]> wrote:
>>
>>>
>>> but you can not talk about the Jenkins server and know what the other is
>>> talking about without saying, you mean Linux or the java process thing it's
>>> a recepie for disaster or turning 2 words into 6 every time you want to use
>>> it.
>>>
>>> today sure we say login to jenkins using my example. but asking say
>>> what's the memory of the Jenkins server..
>>>
>>> when you want to be OS agnostic (not all Jenkins run in Linux) refering
>>> to the server is highly advantageous.
>>>
>>>
>> I see. So you would reserve the word "server" for a higher level than
>> the Jenkins java process. That is reasonable, though it means we need a
>> different word or phrase than "server"
>>
>>
>>> I just see this as something that would bite us in the future,
>>> irrespective of any technical issues (raised by Daniel)
>>>
>>>
>> I like Daniel's idea of more precisely describing the scope of the
>> changes related to this renaming and how they would be implemented. I'll
>> reply there with some ideas for discussion.
>>
>>
>> --
>> 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/CAO49JtEDr7b6sMVVFBBxd4J8FfFLCFGzhVpFDDHpXQxuvOxGxA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEDr7b6sMVVFBBxd4J8FfFLCFGzhVpFDDHpXQxuvOxGxA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> --
> Website: http://earl-of-code.com
>
> --
> 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/CAPiUgVfc0kdVi_RDiKp4RATipbwPBAMYo%3Df20PoNhaMSw%2B5Y5w%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVfc0kdVi_RDiKp4RATipbwPBAMYo%3Df20PoNhaMSw%2B5Y5w%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/CAD34T66sc09UKknN%2B881LR1ktyU5q7F_O%3DPOh9zzsG6Z-fho%3Dg%40mail.gmail.com.
