Skip to content

Update master/slave to primary/secondary #136

@ParetoOptimalDev

Description

@ParetoOptimalDev

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions