Based on the current feedback, the following terminology is suggested:

   - Master node => "Built-in Node"
   - "master" label => "builtin" // We will need to keep master for 
   compatibility reasons, but it can be deprecated and maybe even hidden from 
   UI
   - “Master branch” in documentation and help => "default branch"
   - Agent-to-Master security => " Agent-to-Controller security "
   - "Jenkins master container " => "Jenkins controller container"
   - "Jenkins master pod" => "Jenkins controller pod" // That still sounds 
   a bit fishy since "controller" is a term in K8s
   - "Serialization whetelist" for JEP-200 => "serialization permit list"

Any objections regarding these terms?

On Monday, April 26, 2021 at 6:22:20 PM UTC+2 Oleg Nenashev wrote:

> Dear all,
>
> Thanks to everyone who contributed their ideas in the sub-term 
> definitions list 
> <https://docs.google.com/document/d/1-8myIWOZZktR0HNtbFIiNA0RfDCvkfKKuNI0C3wcvbo/edit#heading=h.tznacb7eadfy>.
>  
> We've got a number of ideas and identified the missing terms where we need 
> decisions. Most notable ones which require discussion:
>
>    - Jenkins as node
>    - Jenkins “main node” label - Aligned with “Jenkins as node”
>    - Jenkins master pod - for K8s components
>    - “Master branch” in documentation, not the repository layout
>    
> I suggest we continue the discussion and finalize the term decisions at 
> the next governance meeting on May 05. I encourage all contributors to 
> review the doc, vote for terms and let us know if you see any term missing. 
> Hopefully we could build a consensus before th governance meeting happens.
>
> Thanks for your time,
> Oleg Nenashev
>
>
> On Tuesday, April 20, 2021 at 12:42:14 PM UTC+2 Oleg Nenashev wrote:
>
>> Dear all,
>>
>> As discussed in the Jenkins chats, we would like to continue the 
>> terminology definitions we agreed on in 2020. Just to summarize the status 
>> from this thread 
>> <https://groups.google.com/u/1/g/jenkinsci-dev/c/CLR55wMZwZ8/m/AdMfXV-wAgAJ> 
>> and the related announcements:
>>
>>    - We adopted "controller" as a term to define the main Jenkins 
>>    instance which acts as a web interface and the Jenkins system controller 
>>    (context, agent controller, endpoint for CLI and REST API, etc.). 
>> Formerly 
>>    known as "master", yes
>>    - We agreed that localizations for the term are to be reviewed on a 
>>    case-by-case basis by maintainers and localization leaders. 
>> Recommendations 
>>    for German, French, Spanish, Chinese, Italian and Russian are defined 
>>    here 
>>    
>> <https://docs.google.com/document/d/1-8myIWOZZktR0HNtbFIiNA0RfDCvkfKKuNI0C3wcvbo/edit#heading=h.pjrd2d5qm09j>
>>    .
>>    - We agreed to follow-up on the naming for sub-entities of the 
>>    controller instance: e.g. Web interface, Jenkins as a "main" node, 
>> labels, 
>>    etc. This follow-up has not happened yet...
>>
>> In this thread I suggest to finally agree on terms for the third item so 
>> that we could ensure that all patches use the same terminology. It is 
>> *VERY* important, because such sub-entity terms are widespread in the 
>> Jenkins Web UI. For example, a screenshot from Danioel Beck:
>>
>> [image: image.png]
>>
>> I have started a table for sub-entity terms here 
>> <https://docs.google.com/document/d/1-8myIWOZZktR0HNtbFIiNA0RfDCvkfKKuNI0C3wcvbo/edit#heading=h.tznacb7eadfy>,
>>  
>> this document is open for any suggestions. We kindly invite all interested 
>> contributors to:
>>
>>    - Help us identify areas where "controller"/"master" terms need to be 
>>    amended. These terms might be used inside the Jenkins core or in any 
>> other 
>>    Jenkins components: docs, plugins, etc. Whatever you see, let's fix that
>>    - Come up with term proposals or comment on already proposed ones
>>
>> Thanks in advance to all contributors!
>>
>> Best regards,
>> Oleg Nenashev
>> Jenkins Governance Board
>>
>>
>>

-- 
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/81506cb1-ce85-4ebe-9990-45bc9ae53f7an%40googlegroups.com.

Reply via email to