sureshanaparti opened a new issue #4887:
URL: https://github.com/apache/cloudstack/issues/4887


   ## Background
   
   The default git branch name 'master' was replaced with 'main' on GitHub 
[2][3] and in the wider Git community [4]. For those that have missed the 
broader discussion in society, the term 'master' is offensive to some people 
[1]. This is widely considered insensitive if not illegal, hence the proposed 
change.
   
   [1] 
https://www.theserverside.com/feature/Why-GitHub-renamed-its-master-branch-to-main
   [2] 
https://www.techrepublic.com/article/github-to-replace-master-with-main-starting-in-october-what-developers-need-to-know
   [3] https://github.com/github/renaming
   [4] https://about.gitlab.com/blog/2021/03/10/new-git-default-branch-name/
   
   ## Proposal
   
   It seems fitting the CloudStack would follow this example of inclusiveness. 
For this, the project would rename its default branch name of all the 
repositories to 'main'. In addition, all the applicable integration points (Eg: 
Travis-CI, etc) using these repositories have to replace the branch name 
'master' with 'main'.
   
   The sample steps to rename and replace the default branch to 'main' are 
here: 
https://faun.pub/git-step-by-step-renaming-a-master-branch-to-main-16390ca7577b
   
   #### Systems/Scripts integrated with Apache CloudStack repo
   
   - Jenkins
   - Travis CI
   - Trillian
   - cwiki
   - Git mirrors
   - Internal Documentation (internal readme/install docs/etc)
   - External Documentation
   - External CI systems ?
   - Any third party tools ?
   
   #### Impacted Systems/Scripts [Update ( 'master' to 'main') status]
   
   - Jenkins          [NO]
   - Travis CI        [NO]
   - Trillian            [NO]
   - cwiki              [NO]
   - Git mirrors     [NO]
   
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Infra / Other
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to