<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Mehdi,<div class=""><br class=""></div><div class="">I completely agree and this has been raised in other forums as well. GitHub is planning to change the default name of the ‘master’ branch for new repos - I think we should wait to see what they move to, so we can decide whether its makes sense to align with that.</div><div class=""><br class=""></div><div class="">-Chris<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jun 19, 2020, at 2:48 AM, Mehdi AMINI via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class="">Hi,<br class=""><div class=""><br class=""></div><div class="">When we moved to GitHub a few months ago, we used without more consideration the "master" convention to name our development branch. On SVN it used to be just "trunk".</div><div class="">This naming is <a href="https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1" class="">unfortunate</a> as it can <a href="https://dev.to/afrodevgirl/replacing-master-with-main-in-github-2fjf" class="">hurt some contributors</a>, and there is really no technical advantage that I know of to favor this convention over another.</div><div class=""><br class=""></div><div class="">I am perfectly aware that `master` has other significations than the master/slave meaning, and I personally never made this association in the past. However I'm also able to recognize that I'm privileged here, and that not everyone is in the same position.</div><div class=""><br class=""></div><div class="">As we intend to be an inclusive community, I propose that we change the name of our development branch and that we adopt instead a more neutral terminology for the LLVM monorepo. Possible names are "dev", "trunk", "main", "default", ...</div><div class=""><br class=""></div><div class="">We need to plan a transition as all the bots will need to be updated to track this new branch instead, but these are minor technical details, nothing compared to the SVN->Git migration we went through.</div><div class=""><br class=""></div><div class="">Since I'm on this topic, we should also likely look into the pervasive use of whitelist/blacklist in the project.</div><div class=""><br class=""></div><div class="">Thoughts?</div><div class=""><br class=""></div><div class="">-- </div><div class="">Mehdi</div><div class=""><br class=""></div><div class=""><br class=""></div></div></div></div>
_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br class=""></div></blockquote></div><br class=""></div></body></html>