Skip to content

Terminology: Conclusions should set the bar low, not high #1

@mallory

Description

@mallory

A comment, "While I link the level of examination demonstrated in this document for the terms "master" and "slave" (especially in close proximity), I wonder if it may also represent a too high bar of formalism to start the process for each new term that may need replacement? I mean, is such a doc going to be required for each new term the community decides to replace with better language?"
We can take this feedback into the conclusions, recognising the history of this document (in 2018 no one cared) but acknowledge ground broken such that new discussions can be brought more easily than this one about these few terms.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions