Rename master branch to match our Level of Enterprise to fight all the *isms

[antonioJASR]

As a Mexican Professional have concern to have a master branch, I propose to change master to enterprise_branch_which_is_stable_edition.

With that we can ends Racisms, Classisms, Polymorphisms in the World.

[dusnm]

I for one as a Serbian engineer fully endorse this concept as it could bring about peace and equality in an otherwise unequal software engineering world. Thenceforth it is of great importance to find a more suitable naming convetion for the master branch and finally put an end to the classist, imperialist, and racist dogma of modern times.

[adm1nx]

As a fellow identitarian of color I also believe in the appropriate corporate position of renaming the highly offensive master branch to one that aligns with our aggressively neutral stance on equality. Such a change will remove all barriers to entry for underprivileged developers and create an inclusive branch that anybody can create a pull request to.

[Tylersuard]

@antonioJASR I feel like renaming it to "branch which is stable" gives users unrealistic hopes for the repo.

[emiln]

There can be no doubt that master is deeply problematic and is making contributors feel unwelcome due to the oppressive terminology used. We've put our trusted Swedish Inclusivity Consultant on the case, and ze've made a number of observations and a recommendation for our new default branch name.

Most importantly:

• The default branch name must not exclude anyone regardless of how they identify in terms of gender, color, religion, species, or physical form. Ze stresses that the previous list is not exhaustive.
• The new branch name should not suggest a rigid hierarchy, where it is somehow more privileged than other branches. Rather, it should encompass them, and have ample space for all other branches to be who and what they truly are.
• It would be a good opportunity to fight the industry-pervasive meritocratic values that entrench those with talent and ability in a position of dominance.

Ze came up with the amazing suggestion:

uinverse

Our consultant is strong, dyslexic, and proud, and we as a company fully support zir in zir efforts, just like we support anyone regardless of gender identity, ability, height, and race. The previous list is not exhaustive.

So as of right now our default branch is uinverse and master has been removed.

[Itheme]

While uinverse is a good step towards a more inclusive future of the project, we need to take a look at the whole picture. After all, some users can still checkout previous versions of the code base. To ensure that the proposed changes aren't just a window dressing, after these long awaited changes will get implemented, someone ought to purge the entirety of the repo's history. So that none of those questionable commits could resurface.

Insensitive commits from the past might damage project's reputation. We, as a community, must keep history in check and erase it if possible. Otherwise, some might even try to fork previous problematic version of the project for the sole purpose of glorification of their appalling beliefs