Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAHA+R7Pz3b58BS64FdOR2nEt-fDUb3YU4Xnh2=rEnD038zWWPg@mail.gmail.com>
References: 
 <CAHA+R7Pe2gz_NSunyjrXuuVk46t2rF7yh9tTNurWmzBWSCxT6g@mail.gmail.com>
	<CAMHxVRHwqvcnPgE+=pswVMmNforZdqCRQ4_itW+ArebAK=1L4g@mail.gmail.com>
	<CAHA+R7NZ+QnytCajhxeHwgGm+NB40NYir70pzGjvS_kTqx-G7w@mail.gmail.com>
	<CAMHxVRFUQQK1cFynFKSA5eYZ93zZZu1CTVkyY7q2i4uZ4wtRtQ@mail.gmail.com>
	<CAHA+R7PQosUHiYudR7sL8L0FDrZr=TEZvCjY+NqXFd02uMsWNw@mail.gmail.com>
	<CAMHxVRH1WtU_C18U3WgVnu5yu72Vgn-cnVmE6hq8iP8iRHhYrg@mail.gmail.com>
	<CAHA+R7Pz3b58BS64FdOR2nEt-fDUb3YU4Xnh2=rEnD038zWWPg@mail.gmail.com>
Date: Wed, 16 Mar 2016 14:21:37 -0700
Message-ID: 
 <CAMHxVRFDn=Sz21uqE50GtieKXL-CCkFXmNaA7Genq1p09KndoQ@mail.gmail.com>
Subject: Re: Backport r/44230 to 0.27 branch
From: Jie Yu <yujie.jay@gmail.com>
To: dev@mesos.apache.org
Cc: Michael Park <mpark@apache.org>, Vinod Kone <vinodkone@apache.org>,
	Jojy Varghese <jojy@mesosphere.io>
Content-Type: multipart/alternative; boundary=089e013d11a25fc845052e311985

--089e013d11a25fc845052e311985
Content-Type: text/plain; charset=UTF-8

I understand your frustration. I am curious what review/ticket are you
talking about, and who is the shepherd for your review/ticket?

Mesos project has a clear guide how to contribute to the project, that's
what the community has agreed on:

https://github.com/apache/mesos/blob/master/docs/submitting-a-patch.md#before-you-start-writing-code

"Find a shepherd to collaborate on your patch. A shepherd is a Mesos
committer that will work with you to give you feedback on your proposed
design, and to eventually commit your change into the Mesos source tree."

- Jie


On Wed, Mar 16, 2016 at 2:03 PM, Cong Wang <cwang@twopensource.com> wrote:

> On Wed, Mar 16, 2016 at 12:18 PM, Jie Yu <yujie.jay@gmail.com> wrote:
> >>
> >> like many other review requests are burned or take
> >
> > 6+ months to merge
> >
> >
> > Have you reached out to any shepherd for that ticket/review?
> >
>
> This is exactly where it doesn't work.
>
> You, as qualified as a committer, need to do _your_ work, you have
> to prioritize all the review requests you get, take care of all of them.
> Why? Because you have them all, you should know which of them
> are more important than others therefore should be reviewed earlier
> than later. You can't wait for others to tell you, because you are a
> committer.
>
> Priorities are based on _your_ understanding of the code, rather than
> who you know better or who pings you more than others.
>
> You have 20+ committers, you should be able to handle all of these
> review requests, but apparently some of them are not working at all
> so some of them are overloaded. This is a problem you need to fix,
> rather than being ping'ed.
>

--089e013d11a25fc845052e311985--