Re: MESOS-2516: Shepherd wanted

Alex, Very well said.:-) On সোমবার 16 মে 2016 10:47 অপরাহ্ণ, Alex Rukletsov wrote: Cong, it's strange that you project your frustrations—which are understandable and may have good reasons—on the project as a whole. There are reasons why things are done in the way they are done; our primary

Re: MESOS-2516: Shepherd wanted

Hi guys, Thanks for bringing up the issues regarding getting patches/reviews committed. Instead of answering specific questions or points raised in this thread, I wanted to highlight some of the things we've done or doing (and plan to do) to improve the process further. *Re: Roadmap*: Perhaps

Re: MESOS-2516: Shepherd wanted

Hello, Alex On Mon, May 16, 2016 at 10:17 AM, Alex Rukletsov wrote: > Cong, > > it's strange that you project your frustrations—which are understandable > and may have good reasons—on the project as a whole. There are reasons why > things are done in the way they are done;

Re: MESOS-2516: Shepherd wanted

Cong, it's strange that you project your frustrations—which are understandable and may have good reasons—on the project as a whole. There are reasons why things are done in the way they are done; our primary goal is quality, we'd rather have a few well implemented features rather than a bunch of

Re: MESOS-2516: Shepherd wanted

On Sat, May 14, 2016 at 12:22 PM, José Guilherme Vanz wrote: > If is always difficult to find I shepherd, change the approach can be a > good ideia. Maybe remove this burocracy of a shepherd and keep just the > review board and reviews. Once a new patch is uploaded the >

Re: MESOS-2516: Shepherd wanted

On Sat, May 14, 2016 at 12:22 PM, José Guilherme Vanz < guilherme@gmail.com> wrote: > I'm very new in the community and I do not know all the issues the > community already faced. My advance apologies if I'm saying bullshit... > > If is always difficult to find I shepherd, change the approach

Re: MESOS-2516: Shepherd wanted

I'm very new in the community and I do not know all the issues the community already faced. My advance apologies if I'm saying bullshit... If is always difficult to find I shepherd, change the approach can be a good ideia. Maybe remove this burocracy of a shepherd and keep just the review board

Re: MESOS-2516: Shepherd wanted

It looks fine for me except for some minor style issues I left on it. Please add me as reviewers to trigger it pass jenkins build. In addition, I think need inform this to modu...@mesos.apache.org and dev@mesos.apache.org in another thread. Because it change `mesos::master::allocator::Allocator`

Re: MESOS-2516: Shepherd wanted

José— Thanks a lot for taking this and doing the cleanup! I have filed this ticket some time ago, but currently I don't have cycles to shepherd. It looks like other shepherds have different priorities right now and can't help out here either. Right now most of shepherds are focusing on 0.29,

Re: MESOS-2516: Shepherd wanted

On Thu, May 12, 2016 at 8:54 PM, José Guilherme Vanz wrote: > Even I did not find a shepherd, I've uploaded a first version of the patch > in the review board. You are not alone. This is the biggest problem of this community which people here refuse to see, especially

Re: MESOS-2516: Shepherd wanted

Hi folks Even I did not find a shepherd, I've uploaded a first version of the patch in the review board. Issue: https://issues.apache.org/jira/browse/MESOS-2516 Patch: https://reviews.apache.org/r/47281/ Thanks! On Mon, 9 May 2016 at 22:39 José Guilherme Vanz wrote:

MESOS-2516: Shepherd wanted

Hi everyone! I'm looking for a shepherd to the issue MESOS-2516. I've already have the preliminary patch in my github mirror to send to review. However, I would like to find the shepherd before send the code. Someone volunteer? =] Best Vanz