{"thread":{"id":"53743","subject":"[ANNOUNCE] Regarding Git and Branch Naming","startedAt":"2020-06-23T16:59:14Z","lastAt":"2020-06-23T16:59:14Z","messageCount":1,"participants":["Christian Couder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"400394","messageId":"CAP8UFD1KfEps4hS8eadBK-E4e5WyWSh93XivRabZAVhiCuQimQ@mail.gmail.com","threadId":"53743","inReplyTo":null,"subject":"[ANNOUNCE] Regarding Git and Branch Naming","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2020-06-23T16:58:59Z","receivedAt":"2020-06-23T16:59:14Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"We at Git PLC [*1*] (who represents the project to our umbrella\norganization, Software Freedom Conservancy) drafted a statement on\nthe subject matter with the Conservancy and it now is posted at the\nconservancy's site at [*2*].  A copy of it is attached at the end of\nthis message.\n\nIt is important that discussions and decisions about what changes we\nare going to make to the code happen on this list, just like any\nother changes.\n\nTo that end, the patch series posted by Johannes Schindelin earlier\nthis month [*3*] to allow users to give a name of their choice to\nthe first branch \"git init\" creates and to configure the default for\nthat purpose seems like an obviously good starting point.  Hopefully\nthe series can be polished and included in the 2.28 release.\n\nBut it is just a starting point.  We need to keep the discussion\nmoving and reach a consensus on remaining issues, including\n\n - whether to change the default used as the name of the first\n   branch created in a new repository away from 'master'?\n\n - if we were to change it, what should we change it to?\n\nThere may be more things that need to be decided.  Please be\nrespectful to each other and keep the discussion constructive\nin the coming weeks.\n\nThanks.\n\n[Footnotes]\n\n*1* The current members of Git PLC are:\n\n  - Ævar Arnfjörð Bjarmason <avarab@gmail.com>\n  - Christian Couder <christian.couder@gmail.com>\n  - Jeff King <peff@peff.net>\n  - Junio C Hamano <gitster@pobox.com>\n\n*2* https://sfconservancy.org/news/2020/jun/23/gitbranchname/\n\n*3* https://lore.kernel.org/git/pull.656.git.1591823971.gitgitgadget@gmail.com/\n\n-- >8 --\n\nExisting versions of Git are capable of working with any branch name;\nthere's nothing special about ‘master’ except that it has historically\nbeen the name used for the first branch when creating a new repository\nfrom scratch (with the git init command). Thus many projects use it to\nrepresent the primary line of development. We support and encourage\nprojects to switch to branch names that are meaningful and inclusive,\nand we'll be adding features to Git to make it even easier to use a\ndifferent default for new projects.\n\nAs a first step, Git will add a mechanism to allow users to specify the\ndefault used as the name of the first branch when creating a new\nrepository. Also, consistent with its project governance, Git has\nundertaken a community process to explore changing the name of the\nfirst branch created automatically for new repositories away from\n'master'. That change is currently being discussed on our mailing list.\nAs always, changes in Git's core will minimize disruption for Git's\nusers and will include appropriate deprecation periods.\n\nMeanwhile, Git as a project remains engaged in encouraging\nparticipation of underrepresented groups in the development of Git\nitself. Git continues their participation, which began four years ago,\nin Conservancy's Outreachy initiative. Conservancy also continues to\nexplore and support other initiatives that can also assist in this\narea.\n"}]}