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 <[email protected]> wrote: > On Wed, Mar 16, 2016 at 12:18 PM, Jie Yu <[email protected]> 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. >
