Re: [DISCUSS] Renaming Mesos Slave

1. Mesos Worker (or just Mesos node) 2. Mesos Worker 3. No, but if we do then Leader or Director or Controller 4. Deprecation cycle, documentation, etc. Provide aliases for a release or two. Thanks for raising this topic; it's been on my mind for a while. As for why I think this matters: http://e

Re: [DISCUSS] Renaming Mesos Slave

Strong -1 for changing the name (either master or slave). >From a community stand point, if dev resources are diverted to renaming efforts, then the community and the user base both lose meaningful functionality that isn't being worked on. >From a using organization stand point, as well as framew

Re: soliciting shepherds for auto tools changes

> On Jun 3, 2015, at 10:25 AM, Jake Farrell wrote: > > Happy to help review and provide feedback on these patches Thanks Jake, does that mean you are shepherding too, or just reviewing? > > -Jake > > On Wed, Jun 3, 2015 at 12:21 PM, James Peach wrote: > >> >>> On May 18, 2015, at 10:52 AM

Re: Let mesos to run on arm64 servers

Hi all, Is there someone want to be the Shepherd for me and review my patches? That will be greatly appreciated. 2015-06-01 17:05 GMT+08:00 Adam Bordelon : > Robin, thanks for your interest in compiling and running Mesos on arm64. > I have added you as a JIRA contributor and assigned the JIRA to

Re: [DISCUSS] Renaming Mesos Slave

+1 I’d like to voice my support for removing the master/slave nomenclature. It’s our policy at aster.is that we don’t use that terminology in our projects or presentations. Currently we use ‘leader/follower’, but we are open to using whatever terms the community comes up wi

Re: [DISCUSS] Renaming Mesos Slave

+1 I’d like to voice my support for removing the master/slave nomenclature. It’s our policy at aster.is that we don’t use that terminology in our projects or presentations. Currently we use ‘leader/follower’, but we are open to using whatever terms the community comes up with. We’re also will

Re: [DISCUSS] Renaming Mesos Slave

+1 for Brian Hicks' leader/follower name and a huge +1 for the explanation he gave On Wed, Jun 3, 2015 at 10:27 AM, Brian Hicks wrote: > 1. We’ve been aliasing everything to “leader/follower” in the projects I’m > a part of. I think it gets rid of the problematic language while still > being des

Re: Native code error

Hi Alberto, Can you share the full crash report with us? Niklas On 2 June 2015 at 02:37, Alberto Rodriguez wrote: > Hi all, > > I've got a bunch of tests that are checking whether my spark process is > able to connect to a mesos cluster. The "happy path" (mesos up & running) > is working fine

Re: soliciting shepherds for auto tools changes

Happy to help review and provide feedback on these patches -Jake On Wed, Jun 3, 2015 at 12:21 PM, James Peach wrote: > > > On May 18, 2015, at 10:52 AM, Vinod Kone wrote: > > > > Tim and Cody. Do any of you have cycles to shepherd these? > > If there's no takers, should I just close the ticket

Re: [DISCUSS] Renaming Mesos Slave

Dave, I am not saying that we should make the decision solely based on organization votes. This is just an extra input we can use while making the decision. By looking at the threads, looks like we don't have a community consensus here. Then the question is: how do we make a *better* decision wit

Re: soliciting shepherds for auto tools changes

> On May 18, 2015, at 10:52 AM, Vinod Kone wrote: > > Tim and Cody. Do any of you have cycles to shepherd these? If there's no takers, should I just close the tickets? > > On Fri, May 15, 2015 at 3:19 PM, Vinod Kone wrote: > >> >> >> -- Vinod >> >> -- Forwarded message --

Re: [DISCUSS] Renaming Mesos Slave

Hi Jie, I understand your concern here, but within Apache projects, "organizations" do not have a voice/vote -- people do. I think should take into strong consideration the overhead any change may have on any adopter/organization and discuss those risks and problems openly, but ideally this decis

Re: [DISCUSS] Renaming Mesos Slave

Adam, If a vote is called out, how do we decide if it passes or not. Will that be the same of voting for a release (i.e., PMC member can veto it)? I would imagine that some PMC members might want to express some negative feedbacks on this, but certainly do not want to veto it. How do we deal with

Re: [DISCUSS] Renaming Mesos Slave

1. Mesos worker 2. Mesos worker 3. No 4. Documentation should first be changed Thanks, Elizabeth On Monday, June 1, 2015, 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.a