I agree with you. It’s probably derived from “master” as in the “gold master” [1] which is the mix from which a sound engineer would cut a record or CD. And who knows where that term came from?
But in the end, the origin of the term is irrelevant. The current name is, or may be, unwelcoming to some people, so let’s just move on. Julian [1] https://en.wikipedia.org/wiki/Mastering_(audio) <https://en.wikipedia.org/wiki/Mastering_(audio)> > On Jul 28, 2020, at 1:56 PM, Viliam Durina <vil...@hazelcast.com> wrote: > > It's not a term related to slavery, it has much broader meaning than "slave > owner", but any argument is probably vain. > > On Tue, 28 Jul 2020 at 19:43, Julian Hyde <jhyde.apa...@gmail.com> wrote: > >> I am in favor of renaming ‘master’ to ‘main’. To most people it doesn’t >> make any difference. To some, such as potential members currently outside >> the community, it makes the project more welcoming. >> >> Very little effort or disruption is required. We’ve identified a potential >> source of friction, so let’s fix it and move on. >> >> Julian >> >>> On Jul 28, 2020, at 10:31 AM, Michael Mior <mm...@apache.org> wrote: >>> >>> Hi all, >>> >>> You can find some background on this discussion at the link below [0]. >>> This is a topic that has come up regularly among D&I folks at the ASF. >>> The short summary is that the term "master" when referring to a git >>> branch is a reference to terminology related to slavery. I'm >>> suggesting main because this seems to be what the developer community >>> as a whole is gravitating towards. See for example, GitHub's public >>> roadmap [1] where there are plans to make this change. >>> >>> I'm hoping that this discussion can be focused not on whether anyone >>> has been impacted by such terminology, but how we can move forward. I >>> personally believe that if a single person feels more welcome to >>> contribute because of the change, it's a win. I also don't think >>> making this change needs to be painful. (There are less than 20 >>> relevant references to "master" in the Calcite code.) Apache Mahout >>> and I believe others have already made this change. >>> >>> I think this is a relatively low impact change that can potentially >>> make us even more welcoming to new contributors, which is a benefit to >>> us all :) >>> >>> [0] >> http://www.kapwing.com/blog/how-to-rename-your-master-branch-to-main-in-git/ >>> [1] https://github.com/github/roadmap/issues/63 >>> >>> -- >>> Michael Mior >>> mm...@apache.org >> >> > > -- > Viliam Durina > Jet Developer > hazelcast® > > <https://www.hazelcast.com> 2 W 5th Ave, Ste 300 | San Mateo, CA 94402 | > USA > +1 (650) 521-5453 | hazelcast.com <https://www.hazelcast.com> > > -- > This message contains confidential information and is intended only for the > individuals named. If you are not the named addressee you should not > disseminate, distribute or copy this e-mail. Please notify the sender > immediately by e-mail if you have received this e-mail by mistake and > delete this e-mail from your system. E-mail transmission cannot be > guaranteed to be secure or error-free as information could be intercepted, > corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. > The sender therefore does not accept liability for any errors or omissions > in the contents of this message, which arise as a result of e-mail > transmission. If verification is required, please request a hard-copy > version. -Hazelcast
