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

Update master/slave to primary/secondary #136

Open
ParetoOptimalDev opened this issue Sep 28, 2022 · 0 comments
Open

Update master/slave to primary/secondary #136

ParetoOptimalDev opened this issue Sep 28, 2022 · 0 comments

Comments

@ParetoOptimalDev
Copy link

As many projects begin to update their api's to remove slave/master and many github repos are named main it feels a bit odd using api's that still use it for me. At the very least it's a reminder of the discussions about the terminology.

Additionally, mongodb has tickets like this one to modernize terminology and update these terms.

I can see an argument in waiting for mongodb to update those things first, but created this issue anyway because:

  • It's uncomfortable
  • I've had students and coworkers I was teaching that were either uncomfortable with it or at least distracted enough to ask why the API still had slave/master

What are your thoughts?

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

No branches or pull requests

1 participant