Re: Introduction - Aditi

Hi Aditi, Please feel free to add me as a reviewer for these patches. I contributed part of Phase 1, and ended up looking ahead as to what would be required for the further phases. I'd be happy to review your patches! Joris On Thu, Jun 4, 2015 at 11:00 AM, Aditi Dixit wrote: > Hi all, > > I'm

Re: Build failed in Jenkins: mesos-reviewbot #6201

JPeach: That's correct. You had it right in the top level project, but the comparison was wrong in the libprocess check. Probably just a copy paste error, all fixed now! :-) Thanks for helping us move to more general macros! Joris On Thu, Jun 4, 2015 at 10:51 PM, James Peach wrote: > > > On Jun

Re: Build failed in Jenkins: mesos-reviewbot #6201

> On Jun 4, 2015, at 12:50 PM, Vinod Kone wrote: > > On Thu, Jun 4, 2015 at 7:48 AM, Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > >> checking for C++ compiler version... 4.8.2 >> checking for C++ compiler vendor... (cached) gnu >> configure: error: GCC 4.8 or higher required (f

Re: Build failed in Jenkins: mesos-reviewbot #6201

Looks like ben pushed a fix ~ 5 hours ago. On Thu, Jun 4, 2015 at 12:50 PM, Vinod Kone wrote: > On Thu, Jun 4, 2015 at 7:48 AM, Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > > > checking for C++ compiler version... 4.8.2 > > checking for C++ compiler vendor... (cached) gnu > > co

Re: Build failed in Jenkins: mesos-reviewbot #6201

On Thu, Jun 4, 2015 at 7:48 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > checking for C++ compiler version... 4.8.2 > checking for C++ compiler vendor... (cached) gnu > configure: error: GCC 4.8 or higher required (found 4.8.2) > hmm. this looks weird.

Re: soliciting shepherds for auto tools changes

> On Jun 4, 2015, at 9:33 AM, James Peach wrote: > > >> On Jun 4, 2015, at 8:31 AM, Benjamin Hindman wrote: >> >> Took care of MESOS-2666 as well James. There was a bug I had to fix. ;-) >> Please take a look at the reviews where I left some comments. > > Thanks Ben! > >> >> It looks like

Re: soliciting shepherds for auto tools changes

> On Jun 4, 2015, at 8:31 AM, Benjamin Hindman wrote: > > Took care of MESOS-2666 as well James. There was a bug I had to fix. ;-) > Please take a look at the reviews where I left some comments. Thanks Ben! > > It looks like Cody still has some questions around semantics for > https://reviews

Re: soliciting shepherds for auto tools changes

Took care of MESOS-2666 as well James. There was a bug I had to fix. ;-) Please take a look at the reviews where I left some comments. It looks like Cody still has some questions around semantics for https://reviews.apache.org/r/33752, please address that and then we can get it committed. Thank y

Re: [DISCUSS] Renaming Mesos Slave

-1 master/worker -1 master/agent -1 leader/follower +1 master/slave; no change needed There's no technical benefit **at all** to a terminology change at this point. If people want to change the names in their client presentations that's fine. Master/slave conveys specific meaning that is lost oth

Re: soliciting shepherds for auto tools changes

I just took a look and shipped the reviews associated with MESOS-2659. I'll take a look at MESOS-2666 next. Thanks for the contributions James! On Thu, Jun 4, 2015 at 5:54 AM Jake Farrell wrote: > I can only help review, not a Mesos committer > > -Jake > > > > On Wed, Jun 3, 2015 at 11:47 PM, J

Re: [DISCUSS] Renaming Mesos Slave

> 1. Mesos Worker [node/host/machine] > 2. Mesos Worker [process] > 3. No, master/worker seems to address the issue with less changes. > 4. Begin using the new name ASAP, add a disambiguation to the docs, and > change old references over time. Fixing the "official" name, even before > changes ar

Re: soliciting shepherds for auto tools changes

I can only help review, not a Mesos committer -Jake On Wed, Jun 3, 2015 at 11:47 PM, James Peach wrote: > > > 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 r

Re: Introduction - Aditi

Thanks for the information Adam. This really helps! Yes, Vinod is my mentor for the duration of my internship. My JIRA id is aditidixit Thanks, Aditi On Thu, Jun 4, 2015 at 2:56 PM, Adam Bordelon wrote: > Welcome to the Mesos community Aditi! > > I'm very excited to see you moving forward with

Mesos 0.23 Release Planning Guidelines (Proposal)

In the spirit of transparency in our release planning, I’d like to propose some guidelines for our JIRA use that will help us all track the release progress together and discover where we can help out others. The Mesos 0.23 release will be gated by a few major features (SSL, Persistent Volumes, Dyn

Re: Introduction - Aditi

Welcome to the Mesos community Aditi! I'm very excited to see you moving forward with Updating FrameworkInfo. Have you reached out to Vinod to Shepherd/mentor you through the process? There's a bit more history in the Epic JIRA MESOS-703 . Also note

Introduction - Aditi

Hi all, I'm Aditi and I'm currently interning at Outreachy. Apache Mesos is an amazing piece of software and I'm really excited to work on it. This is my first time contributing to an open source software, so any advice you may have for me is welcome! The project that I would be working on is Upda

RE: [DISCUSS] Renaming Mesos Slave

+1 to Itamar. I'd be interested to hear any case studies of how this has been handled in other OS projects with master/slave namings if anyone can give examples? From: Itamar Ostricher [ita...@yowza3d.com] Sent: 04 June 2015 05:38 To: u...@mesos.apache.org Cc: de