Skip to content
This repository has been archived by the owner on Jul 26, 2020. It is now read-only.

Get away from master/slave vocabulary #67

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bopopescu
Copy link

For diversity reasons, it would be nice to try to avoid 'master' and 'slave' terminology in this repository which can be associated to slavery. The master-slave terminology could be problematic for people in several countries which has the history of slavery like Romania, USA and many others. Thank you for considering the proposal. Let me know if any changes in the PR are needed, I would be happy to implement them.

Copy link
Contributor

@kayousterhout kayousterhout left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for doing this; this is a great change to make. There's a bit more work necessary to make this work:

(1) The scripts like start_mesos_slave are present on the EC2 instance, so the path to the script can't be renamed without also renaming the underlying script.

(2) Similarly, the git branches that refer to "master" can't be renamed to "main" unless those branches already exist on Github.

(3) The slaves should be renamed to "worker" to match the Spark terminology.

(4) The boto files are an external dependency so should be updated in Boto rather than here (and then this repo could be updated to use the latest version of Boto).

This repo was last updated 7 years ago and is no longer maintained so I'm not sure this effort is worthwhile; I'm going to mark the repo as deprecated and add a note about the bad terminology used.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants