Please don't change the naming. There is absolutely no reason for it apart from rambling of a delusional, political-correctness maniac.
What happened to all the "inside jokes" and humour of the IT world - why are we letting the bacteria of political-correctness into IT? Apart from the confusion, it will create an unnecessary architecture/provisioning changes in many, many places. Possible benefits are *none*. Literally - *none*. Please focus on the PRs that really matter and make apache-mesos a better product, this name-change is only a (pretty good) troll attempt. ( also the logic that led You to changing the "slave" part is somewhat flawed - after all, we all are equal right? so there shouldn't be any "master" either. Rename master to "democratically-elected-member-of-equal-rights-community - to match the insanity after all, its only fair if we take into account all areas. ) PS. First of April was 2 months ago. Maciej Strzelecki Operations Engineer Tel: +49 30 6098381-50 Fax: +49 851-213728-88 E-mail: [email protected] www.crealytics.com<http://www.crealytics.com> blog.crealytics.com crealytics GmbH - Semantic PPC Advertising Technology Brunngasse 1 - 94032 Passau - Germany Oranienstraße 185 - 10999 Berlin - Germany Managing directors: Andreas Reiffen, Christof König, Dr. Markus Kurch Register court: Amtsgericht Passau, HRB 7466 Geschäftsführer: Andreas Reiffen, Christof König, Daniel Trost Reg.-Gericht: Amtsgericht Passau, HRB 7466 ________________________________ From: Alexander Rojas <[email protected]> Sent: Wednesday, June 3, 2015 9:58 AM To: [email protected] Subject: Re: [DISCUSS] Renaming Mesos Slave +1 to Isabel's plan. Times change, language change so lets not be anachronistic. On 02 Jun 2015, at 22:19, Isabel Jimenez <[email protected]<mailto:[email protected]>> wrote: Hi Adam, 1. Mesos Agent 2. Mesos Agent 3. No but is master-agent a logical coupling? 4. +1 Dave, documentation, then API, then rest of the code base. We should also make sure that we only have to change once and that we cover all the connotations that might offend. On Tue, Jun 2, 2015 at 11:50 AM, Dave Lester <[email protected]<mailto:[email protected]>> wrote: Hi Adam, I've been using Master/Worker in presentations for the past 9 months and it hasn't led to any confusion. 1. Mesos worker 2. Mesos worker 3. No 4. Documentation, then API with a full deprecation cycle Dave On Mon, Jun 1, 2015, at 02:18 PM, Adam Bordelon wrote: There has been much discussion about finding a less offensive name than "Slave", and many of these thoughts have been captured in https://issues.apache.org/jira/browse/MESOS-1478 I would like to open up the discussion on this topic for one week, and if we cannot arrive at a lazy consensus, I will draft a proposal from the discussion and call for a VOTE. Here are the questions I would like us to answer: 1. What should we call the "Mesos Slave" node/host/machine? 2. What should we call the "mesos-slave" process (could be the same)? 3. Do we need to rename Mesos Master too? Another topic worth discussing is the deprecation process, but we don't necessarily need to decide on that at the same time as deciding the new name(s). 4. How will we phase in the new name and phase out the old name? Please voice your thoughts and opinions below. Thanks! -Adam- P.S. My personal thoughts: 1. Mesos Worker [Node] 2. Mesos Worker or Agent 3. No 4. Carefully
