I always thought the term "master" as it relates to version control systems was similar to audio mastering where you produce the "final mix" or "gold master" as the source from which all subsequent copies would be made...hence the "master branch" in version control.
But to me, "trunk" makes more sense than "main". After all, how could you have branches without a trunk?
In any case, I'm in no way trying to diminish the importance of changing the "norms" to be more inclusive.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I always thought the term "master" as it relates to version control systems was similar to audio mastering where you produce the "final mix" or "gold master" as the source from which all subsequent copies would be made...hence the "master branch" in version control.
But to me, "trunk" makes more sense than "main". After all, how could you have branches without a trunk?
In any case, I'm in no way trying to diminish the importance of changing the "norms" to be more inclusive.