Terminology Updates

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
64 messages Options
1234
Reply | Threaded
Open this post in threaded view
|

Re: Terminology Updates

Oleg Nenashev
Thanks to everyone who voted for the options! We will review of the voting results to the Governance meeting agenda: https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.cgd8zbewht8o

The meeting will start in 20 minutes, everyone is welcome to join: https://zoom.us/j/99217163913?pwd=TldwZWZTQzNNc3ZGaThFOThlckFGQT09

Best regards,
Oleg

On Thursday, July 23, 2020 at 8:35:15 PM UTC+2, Mark Waite wrote:
Unfortunately, new terms can't be included in the the votiing.  The voting is already in progress at  <a href="https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_1bd92a17371a1ca5&amp;akey=f82b79a50f54ad87" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fcivs.cs.cornell.edu%2Fcgi-bin%2Fvote.pl%3Fid%3DE_1bd92a17371a1ca5%26akey%3Df82b79a50f54ad87\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHZm1B09ejprD-EpJLu5HG-mqj6Ng&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fcivs.cs.cornell.edu%2Fcgi-bin%2Fvote.pl%3Fid%3DE_1bd92a17371a1ca5%26akey%3Df82b79a50f54ad87\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHZm1B09ejprD-EpJLu5HG-mqj6Ng&#39;;return true;">https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_1bd92a17371a1ca5&akey=f82b79a50f54ad87 .  The governance board is using the voting as input for the final decision on the term to be used.

On Thu, Jul 23, 2020 at 7:15 AM Steve Carter <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="6ipTSiirCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">swe...@...> wrote:
Hi all,

I showed up late to the party, so I'll accept a snub gracefully, but I was intrigued by the problem of replacing the term "master" and have one further term I would like to put in the poll if at all possible.

Dispatcher.

This would most correctly apply to the function of taking jobs off the queue and handing them to nodes. What we today know as master would therefore consist of dispatcher and zero-or-one agents.

What I think distinguishes this suggestion is that it connotes a service provided to agents in collaboration rather than a hierarchical power relationship.

--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="6ipTSiirCAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/b8487054-6383-4dec-be3e-29103215cc09o%40googlegroups.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/b8487054-6383-4dec-be3e-29103215cc09o%40googlegroups.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/b8487054-6383-4dec-be3e-29103215cc09o%40googlegroups.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/b8487054-6383-4dec-be3e-29103215cc09o%40googlegroups.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/83c6c952-2acb-40c3-82bc-9ddb024d4d29o%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Terminology Updates

slide
Hi Everyone,

Just wanted to update on the current status of this effort. We discussed this in the Governance Meeting yesterday. The poll closed yesterday, you can see the results at: https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_1bd92a17371a1ca5. They are also shown below:

Result
1. Controller  (Condorcet winner: wins contests with all other choices)
2. Manager  loses to Controller by 95–35
3. Coordinator  loses to Controller by 98–37, loses to Manager by 69–59
4. Primary  loses to Controller by 90–44, loses to Coordinator by 66–63
5. Main  loses to Controller by 97–36, loses to Primary by 68–47
6. Director  loses to Controller by 110–21, loses to Main by 70–56
7. Leader  loses to Controller by 106–24, loses to Director by 71–46
8. Executive  loses to Controller by 116–15, loses to Leader by 65–34

Our plan now is to take the terms from the poll and run them through some checks with native speakers and Google Translate to check the internationalization aspects of the options. We will make a final decision in the next Governance Meeting and make announcements here on the Developers Mailing List as well as providing context and information via blog posts.

Just as a reminder, this effort is to replace the "Jenkins application" term, for what used to be termed the "Jenkins Master." In addition to this usage of "master" we also have the concept of the "master" node that can exist in the Jenkins Application. We will determine next steps on replacing that term (for that node) in the future (because the terms in the list below do not necessarily match the requirements in the context of nodes). 

We want to thank everyone who participated in the poll. We are working hard to get these changes going on this important effort.

Regards,

Alex Earl

On Wednesday, July 29, 2020 at 10:38:24 AM UTC-7 Oleg Nenashev wrote:
Thanks to everyone who voted for the options! We will review of the voting results to the Governance meeting agenda: https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.cgd8zbewht8o

The meeting will start in 20 minutes, everyone is welcome to join: https://zoom.us/j/99217163913?pwd=TldwZWZTQzNNc3ZGaThFOThlckFGQT09

Best regards,
Oleg


On Thursday, July 23, 2020 at 8:35:15 PM UTC+2, Mark Waite wrote:
Unfortunately, new terms can't be included in the the votiing.  The voting is already in progress at  https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_1bd92a17371a1ca5&akey=f82b79a50f54ad87 .  The governance board is using the voting as input for the final decision on the term to be used.

On Thu, Jul 23, 2020 at 7:15 AM Steve Carter <[hidden email]> wrote:
Hi all,

I showed up late to the party, so I'll accept a snub gracefully, but I was intrigued by the problem of replacing the term "master" and have one further term I would like to put in the poll if at all possible.

Dispatcher.

This would most correctly apply to the function of taking jobs off the queue and handing them to nodes. What we today know as master would therefore consist of dispatcher and zero-or-one agents.

What I think distinguishes this suggestion is that it connotes a service provided to agents in collaboration rather than a hierarchical power relationship.

--
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 [hidden email].

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/16dd80db-6686-451a-9e77-9f009833bafen%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Terminology Updates

Oleg Nenashev
Hi all,

Just a reminder, we will be selecting a final term at the governance meeting in 5 minutes.
Everybody is welcome to participate: https://zoom.us/j/91564716663?pwd=R3A2RDFGcU1wTVdoVTErYm1jNzVWdz09

Best regards,
Oleg


On Thursday, July 30, 2020 at 7:21:19 PM UTC+2, slide wrote:
Hi Everyone,

Just wanted to update on the current status of this effort. We discussed this in the Governance Meeting yesterday. The poll closed yesterday, you can see the results at: <a href="https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_1bd92a17371a1ca5" style="font-weight:bold" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fcivs.cs.cornell.edu%2Fcgi-bin%2Fresults.pl%3Fid%3DE_1bd92a17371a1ca5\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFYRzkObxpdALycLVkLxhRQVvdebQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fcivs.cs.cornell.edu%2Fcgi-bin%2Fresults.pl%3Fid%3DE_1bd92a17371a1ca5\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFYRzkObxpdALycLVkLxhRQVvdebQ&#39;;return true;">https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_1bd92a17371a1ca5. They are also shown below:

Result
1. Controller  (Condorcet winner: wins contests with all other choices)
2. Manager  loses to Controller by 95–35
3. Coordinator  loses to Controller by 98–37, loses to Manager by 69–59
4. Primary  loses to Controller by 90–44, loses to Coordinator by 66–63
5. Main  loses to Controller by 97–36, loses to Primary by 68–47
6. Director  loses to Controller by 110–21, loses to Main by 70–56
7. Leader  loses to Controller by 106–24, loses to Director by 71–46
8. Executive  loses to Controller by 116–15, loses to Leader by 65–34

Our plan now is to take the terms from the poll and run them through some checks with native speakers and Google Translate to check the internationalization aspects of the options. We will make a final decision in the next Governance Meeting and make announcements here on the Developers Mailing List as well as providing context and information via blog posts.

Just as a reminder, this effort is to replace the "Jenkins application" term, for what used to be termed the "Jenkins Master." In addition to this usage of "master" we also have the concept of the "master" node that can exist in the Jenkins Application. We will determine next steps on replacing that term (for that node) in the future (because the terms in the list below do not necessarily match the requirements in the context of nodes). 

We want to thank everyone who participated in the poll. We are working hard to get these changes going on this important effort.

Regards,

Alex Earl

On Wednesday, July 29, 2020 at 10:38:24 AM UTC-7 Oleg Nenashev wrote:
Thanks to everyone who voted for the options! We will review of the voting results to the Governance meeting agenda: <a href="https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.cgd8zbewht8o" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading\x3dh.cgd8zbewht8o&#39;;return true;" onclick="this.href=&#39;https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading\x3dh.cgd8zbewht8o&#39;;return true;">https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.cgd8zbewht8o

The meeting will start in 20 minutes, everyone is welcome to join: <a href="https://zoom.us/j/99217163913?pwd=TldwZWZTQzNNc3ZGaThFOThlckFGQT09" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fzoom.us%2Fj%2F99217163913%3Fpwd%3DTldwZWZTQzNNc3ZGaThFOThlckFGQT09\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGyc8vXdvWfp2XEmYCjm2_1rmyaqg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fzoom.us%2Fj%2F99217163913%3Fpwd%3DTldwZWZTQzNNc3ZGaThFOThlckFGQT09\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGyc8vXdvWfp2XEmYCjm2_1rmyaqg&#39;;return true;">https://zoom.us/j/99217163913?pwd=TldwZWZTQzNNc3ZGaThFOThlckFGQT09

Best regards,
Oleg


On Thursday, July 23, 2020 at 8:35:15 PM UTC+2, Mark Waite wrote:
Unfortunately, new terms can't be included in the the votiing.  The voting is already in progress at  <a href="https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_1bd92a17371a1ca5&amp;akey=f82b79a50f54ad87" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fcivs.cs.cornell.edu%2Fcgi-bin%2Fvote.pl%3Fid%3DE_1bd92a17371a1ca5%26akey%3Df82b79a50f54ad87\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHZm1B09ejprD-EpJLu5HG-mqj6Ng&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fcivs.cs.cornell.edu%2Fcgi-bin%2Fvote.pl%3Fid%3DE_1bd92a17371a1ca5%26akey%3Df82b79a50f54ad87\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHZm1B09ejprD-EpJLu5HG-mqj6Ng&#39;;return true;">https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_1bd92a17371a1ca5&akey=f82b79a50f54ad87 .  The governance board is using the voting as input for the final decision on the term to be used.

On Thu, Jul 23, 2020 at 7:15 AM Steve Carter <[hidden email]> wrote:
Hi all,

I showed up late to the party, so I'll accept a snub gracefully, but I was intrigued by the problem of replacing the term "master" and have one further term I would like to put in the poll if at all possible.

Dispatcher.

This would most correctly apply to the function of taking jobs off the queue and handing them to nodes. What we today know as master would therefore consist of dispatcher and zero-or-one agents.

What I think distinguishes this suggestion is that it connotes a service provided to agents in collaboration rather than a hierarchical power relationship.

--
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 [hidden email].

To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/b8487054-6383-4dec-be3e-29103215cc09o%40googlegroups.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/b8487054-6383-4dec-be3e-29103215cc09o%40googlegroups.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/b8487054-6383-4dec-be3e-29103215cc09o%40googlegroups.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/b8487054-6383-4dec-be3e-29103215cc09o%40googlegroups.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/bb36caa6-715e-46e1-84be-3d14bfc9c1fao%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Terminology Updates

slide
Hi everyone,

To follow up on the Governance Meeting (https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.10x94wjx4rlj). We took the input from the community poll and discussed the options. We voted to change from the term "master' to the term "controller" in referring to the "Jenkins Application". We will be doing some additional work to understand the internationalization aspects as people start to make PR's to change terms in non-english languages. I will be creating a page that will contain recommendations for each language for various terms as the various language discussions occur during PR's. 

Thanks for all those who participated in the poll and the discussion.

Regards,

Alex

On Wednesday, August 12, 2020 at 10:55:07 AM UTC-7 Oleg Nenashev wrote:
Hi all,

Just a reminder, we will be selecting a final term at the governance meeting in 5 minutes.

Best regards,
Oleg


On Thursday, July 30, 2020 at 7:21:19 PM UTC+2, slide wrote:
Hi Everyone,

Just wanted to update on the current status of this effort. We discussed this in the Governance Meeting yesterday. The poll closed yesterday, you can see the results at: https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_1bd92a17371a1ca5. They are also shown below:

Result
1. Controller  (Condorcet winner: wins contests with all other choices)
2. Manager  loses to Controller by 95–35
3. Coordinator  loses to Controller by 98–37, loses to Manager by 69–59
4. Primary  loses to Controller by 90–44, loses to Coordinator by 66–63
5. Main  loses to Controller by 97–36, loses to Primary by 68–47
6. Director  loses to Controller by 110–21, loses to Main by 70–56
7. Leader  loses to Controller by 106–24, loses to Director by 71–46
8. Executive  loses to Controller by 116–15, loses to Leader by 65–34

Our plan now is to take the terms from the poll and run them through some checks with native speakers and Google Translate to check the internationalization aspects of the options. We will make a final decision in the next Governance Meeting and make announcements here on the Developers Mailing List as well as providing context and information via blog posts.

Just as a reminder, this effort is to replace the "Jenkins application" term, for what used to be termed the "Jenkins Master." In addition to this usage of "master" we also have the concept of the "master" node that can exist in the Jenkins Application. We will determine next steps on replacing that term (for that node) in the future (because the terms in the list below do not necessarily match the requirements in the context of nodes). 

We want to thank everyone who participated in the poll. We are working hard to get these changes going on this important effort.

Regards,

Alex Earl

On Wednesday, July 29, 2020 at 10:38:24 AM UTC-7 Oleg Nenashev wrote:
Thanks to everyone who voted for the options! We will review of the voting results to the Governance meeting agenda: https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.cgd8zbewht8o

The meeting will start in 20 minutes, everyone is welcome to join: https://zoom.us/j/99217163913?pwd=TldwZWZTQzNNc3ZGaThFOThlckFGQT09

Best regards,
Oleg


On Thursday, July 23, 2020 at 8:35:15 PM UTC+2, Mark Waite wrote:
Unfortunately, new terms can't be included in the the votiing.  The voting is already in progress at  https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_1bd92a17371a1ca5&akey=f82b79a50f54ad87 .  The governance board is using the voting as input for the final decision on the term to be used.

On Thu, Jul 23, 2020 at 7:15 AM Steve Carter <[hidden email]> wrote:
Hi all,

I showed up late to the party, so I'll accept a snub gracefully, but I was intrigued by the problem of replacing the term "master" and have one further term I would like to put in the poll if at all possible.

Dispatcher.

This would most correctly apply to the function of taking jobs off the queue and handing them to nodes. What we today know as master would therefore consist of dispatcher and zero-or-one agents.

What I think distinguishes this suggestion is that it connotes a service provided to agents in collaboration rather than a hierarchical power relationship.

--
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 [hidden email].

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4e5ee65b-da96-4692-b8ec-e2aa296a0b30n%40googlegroups.com.
1234