You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Ele Mooney (JIRA)" <ji...@apache.org> on 2015/01/20 05:28:34 UTC

[jira] [Commented] (MESOS-1478) Replace Master/Slave terminology

    [ https://issues.apache.org/jira/browse/MESOS-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283391#comment-14283391 ] 

Ele Mooney commented on MESOS-1478:
-----------------------------------

I'd very much like to work on this ticket, but I don't know where to start. 

One developer I work with mentioned it might be a good start to change the UI and documentation so that Mesos users aren't looking at this terminology even if it's still running backend. Personally, I'd also appreciate that approach. At my company, we only use master/slave if it's part of the documentation of the software we're using but it's actually very awkward since it's against our own standards. Since Mesos itself is deployed and managed by Ops, the Dev teams only really view the UI to monitor Docker containers deploying with Marathon.

 



> Replace Master/Slave terminology
> --------------------------------
>
>                 Key: MESOS-1478
>                 URL: https://issues.apache.org/jira/browse/MESOS-1478
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Clark Breyman
>            Priority: Minor
>
> Inspired by the comments on this PR:
> https://github.com/django/django/pull/2692
> TL;DR - Computers sharing work should be a good thing. Using the language of human bondage and suffering is inappropriate in this context. It also has the potential to alienate users and community members. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)