Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove racially insensitive language #164

Closed
nmerket opened this issue Jun 15, 2020 · 2 comments · Fixed by #205
Closed

Remove racially insensitive language #164

nmerket opened this issue Jun 15, 2020 · 2 comments · Fixed by #205
Assignees

Comments

@nmerket
Copy link
Member

nmerket commented Jun 15, 2020

The big one is the fact that we're mirroring the AWS EMR API by using the terms "master" and "slave" in our input file. I'm open to suggestions on what the updated terms should be. Maybe we should look at other projects that have a similar paradigm to see what terminology they use so we can be consistent.

Next, we should change the name of the master branch to something else. Github as a whole is moving this direction. This should be pretty easy, but could be disruptive to developers so will need to be coordinated. We have several repos, so maybe this change should be done in conjunction with others.

@nmerket nmerket self-assigned this Jun 15, 2020
@rHorsey
Copy link
Contributor

rHorsey commented Jun 29, 2020

@nmerket I'm going to roll this into the new public ComStock repo as well. From what I can tell on twitter main has become the new recommended default (although I do love production not least of all because I can then ask why people aren't using production in production...) Are you seeing the trend towards main as well? Do you have significant thoughts one way or the other on this? I'm thinking standardized branches of main release/* hotfix/* develop feature/* and bug/* or main release-* hotfix-* develop feature-* and bug-*would set us up for success...

@nmerket
Copy link
Member Author

nmerket commented Aug 26, 2020

I changed the main branch name to develop (easy). Still need to change the yaml keys.

@aspeake aspeake self-assigned this Jan 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants