[
https://issues.apache.org/jira/browse/HBASE-13852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell resolved HBASE-13852.
-----------------------------------------
Resolution: Later
Easy to advocate for such things, harder to show up and do the work, that is my
take. That said the PMC, including myself are still willing to support such an
effort by way of timely review of PRs and release voting, should someone show
up to do the work.
This is open source. You don't tell people what to do, you show up and do it.
Be the change you want to see! (Or not...)
Resolving as Later. Reopen whenever desired.
> Replace master-slave terminology in book, site, and javadoc with a more
> modern vocabulary
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-13852
> URL: https://issues.apache.org/jira/browse/HBASE-13852
> Project: HBase
> Issue Type: Task
> Components: documentation, website
> Reporter: Andrew Kyle Purtell
> Priority: Minor
>
> We should reconsider our use of historical master-slave terminology
> everywhere - book, site, and javadoc - and replace it with a more modern
> vocabulary. There was a conversation in the background at HBaseCon about this
> (I was involved in one on Twitter). Out of some of the suggestions, I like
> "coordinator" as replacement for "master", and "worker" as one replacement
> for "slave", with the other the more descriptive "regionserver" or "region
> server".
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
