We maybe don't need to litigate this one again. I do think this point of view is legitimate, as is the point of view that 'master' is inextricably linked to 'master/slave' as an unfortunate term of art; it did not originate in reference to mastery of a skill but of another entity. Even if one viewed this as a symbolic gesture at best, that has value. Nobody believes this is going to end racism or anything, but has at least value as a signal of community values.
This of course does have to balance against practical concerns. We don't want to break APIs and code over this, I believe. On Fri, Jul 9, 2021 at 9:55 AM Mich Talebzadeh <mich.talebza...@gmail.com> wrote: > > Hi, > > I am afraid I have to differ on this if I may. This is the gist of it. > > The term master has been a part of English and English speaking culture > for a very long time. Unlike " slave" this term "master" has no > connotation to anything related to race, creed and so forth. It is widely > used in the literature > > I believe this has been discussed in Spark forums before. Otherwise we may > end up replacing master tournaments with leader tournaments, master class > with leader class, master craftsman with leader craftsman and so forth. > Personally I don't believe it will make any significant contribution. We > should bear in mind these terminologies are interpreted as they are used > and within the context they are used. > > HTH > > > view my Linkedin profile > <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/> > > > > *Disclaimer:* Use it at your own risk. Any and all responsibility for any > loss, damage or destruction of data or any other property which may arise > from relying on this email's technical content is explicitly disclaimed. > The author will in no case be liable for any monetary damages arising from > such loss, damage or destruction. > > > > > On Fri, 9 Jul 2021 at 15:24, Thomas Graves <tgraves...@gmail.com> wrote: > >> Hey everyone, >> >> Looking at this again since we cut spark 3.2 branch thinking this >> might be something to target for Spark 3.3. >> >> Based on the feedback, I'd like to propose using "Leader" to replace >> "Master". If there are objections to this please let me know in the >> next few days. >> >> Thanks, >> Tom >> >> On Tue, Jan 19, 2021 at 10:13 AM Tom Graves >> <tgraves...@yahoo.com.invalid> wrote: >> > >> > thanks for the interest, I haven't had time to work on replacing >> Master, hopefully for the next release but time dependent, if you follow >> the lira - https://issues.apache.org/jira/browse/SPARK-32333 - I will >> post there when I start or if someone else picks it up should see activity >> there. >> > >> > Tom >> > >> > On Saturday, January 16, 2021, 07:56:14 AM CST, João Paulo Leonidas >> Fernandes Dias da Silva <jplfdsi...@gmail.com> wrote: >> > >> > >> > So, it looks like slave was already replaced in the docs. Waiting for a >> definition on the replacement(s) for master so I can create a PR for the >> docs only. >> > >> > On Sat, Jan 16, 2021 at 8:30 AM jpaulorio <jplfdsi...@gmail.com> wrote: >> > >> > What about updating the documentation as well? Does it depend on the >> codebase >> > changes or can we treat it as a separate issue? I volunteer to update >> both >> > Master and Slave terms when there's an agreement on what should be used >> as >> > replacement. Since [SPARK-32004] >> > <https://issues.apache.org/jira/browse/SPARK-32004> was already >> resolved, >> > can I start replacing slave with worker? >> > >> > >> > >> > -- >> > Sent from: http://apache-spark-developers-list.1001551.n3.nabble.com/ >> > >> > --------------------------------------------------------------------- >> > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org >> > >> >> --------------------------------------------------------------------- >> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org >> >>
