[
https://issues.apache.org/jira/browse/FLINK-18209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-18209:
-----------------------------------
Labels: auto-deprioritized-minor pull-request-available (was:
pull-request-available stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Replace "charged" words in the Flink codebase.
> ----------------------------------------------
>
> Key: FLINK-18209
> URL: https://issues.apache.org/jira/browse/FLINK-18209
> Project: Flink
> Issue Type: Improvement
> Reporter: Marta Paes Moreira
> Priority: Not a Priority
> Labels: auto-deprioritized-minor, pull-request-available
>
> The Flink codebase still makes use of "charged" words that are considered
> outdated and have a negative connotation. In particular, this is the number
> of occurrences of such words:
> "Master": 1366
> "Slave": 229
>
> "Whitelist": 23
>
> "Blacklist": 28
>
> I'd like to propose that we rethink the use of these words [1] and consider
> existing alternatives that other open source projects are also adopting.
> Replacing all occurrences is non-trivial in many cases and may involve
> breaking-changes, though, so one idea would be to break this effort down into
> different phases that can be tackled over time, depending on the impact of
> the required changes.
> [1] [https://lethargy.org/~jesus/writes/a-guide-to-nomenclature-selection/]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
