Slave / master terms

[Thiago Carvalho D Avila]

Hi,

Master/slave concept has been on Jenkins since the start, despite the cultural reinforcement of slavery-related terms. 

Maybe a JEP could follow the trend to more harmonious terms:

https://www.breitbart.com/tech/2018/09/12/programming-language-python-to-change-master-and-slave-terminology-to-appease-sjws/

Best regards,

Thiago C. D'Ávila

-


"Esta mensagem do SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO), empresa pública federal regida pelo disposto na Lei Federal nº 5.615, é enviada exclusivamente a seu destinatário e pode conter informações confidenciais, protegidas por sigilo profissional. Sua utilização desautorizada é ilegal e sujeita o infrator às penas da lei. Se você a recebeu indevidamente, queira, por gentileza, reenviá-la ao emitente, esclarecendo o equívoco."

"This message from SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO) -- a government company established under Brazilian law (5.615/70) -- is directed exclusively to its addressee and may contain confidential data, protected under professional secrecy rules. Its unauthorized use is illegal and may subject the transgressor to the law's penalties. If you're not the addressee, please send it back, elucidating the failure."

[Matthew...@diamond.ac.uk]

> Master/slave concept has been on Jenkins since the start, despite the cultural reinforcement of slavery-related terms. 
> Maybe a JEP could follow the trend to more harmonious terms:

In Jenkins 2, slaves (also sometimes known as nodes), were renamed to agents.

--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

[Baptiste Mathus]

Yes, +1. We all have been committed to do that to change and it was done in early Jenkins 2.x a few years ago. 

Normally the core UI has fully been fixed. Most classes could unfortunately not be renamed for binary compatibility reasons.

So about the JEP, good question. Because it's been fixed already, I'm leaning towards saying JEPing might not be strictly necessary. (?)

There could be a few leftovers here and there, mainly in some less maintained plugins, so don't hesitate to file JIRAs and possibly PRs if you find some of these. We're happy to fix together the last remainders of this.

Cheers

-- Baptiste

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/12021635ce4d46998d66b74c0735ad3e%40Diamond.ac.uk.
For more options, visit https://groups.google.com/d/optout.

[Oleg Nenashev]

FTR https://issues.jenkins-ci.org/browse/JENKINS-42816

It lists some known issues, but it is not complete of course.

We have tentatively added some issues from the list to Google Code-In task list. Many of required patches are pretty small, so they are newbie-friendly.

BR, Oleg