That would be the better solution indeed… but historically the rate at which committers are added is rather low and this is a pressing issue in my opinion.
> On 27 Jan 2016, at 13:17, Christopher Hicks <chi...@uber.com> wrote: > > Would it be easier to invite some of those seasoned contributors to be > committers rather than creating a new tier of contributors? Creating > additional organization complexity seems unnecessary and potentially > distracting unless there is some reason not to increase the core committer > team count. > > On Wed, Jan 27, 2016 at 2:56 AM, Alexander Rojas <alexan...@mesosphere.io> > wrote: > >> My grain of sand here. It is true that committers are a scare resource and >> it might be hard to get shepherds nowadays. However we do have a bunch of >> seasoned contributors, which while not being committers are active and know >> some of the innards of Mesos very well. How about having these guys as >> shepherds? >> >> At the end a committer may be required to sign off a project, but all the >> work of communicating with the contributor, come up with a design could be >> lifter off from committers? >> >> What do you guys thing about the idea? >> >> >>> On 27 Jan 2016, at 00:29, Vaibhav Khanduja <vaibhavkhand...@gmail.com> >> wrote: >>> >>> The community is growing with more individuals getting interested in >>> contributing to the project. This definitely brings an extra bit of >>> workload for committers “Shepherds” but at the same time more developers >>> eventually leads more adoptability across organization and enterprises. >>> >>> >>> >>> I am not sure if this is easy to find an immediate solution but would >>> really like some sort of resolution on this. If shepherd is busy, what >> else >>> can be done for a low priority but a genuine issue. >>> >>> On Sun, Jan 24, 2016 at 4:12 PM, Joris Van Remoortere < >>> joris.van.remoort...@gmail.com> wrote: >>> >>>> Hello Mesos developers, >>>> >>>> You may have noticed some churn in Jira recently around the shepherd >>>> assignment. Specifically, we have unassigned the shepherds for a bunch >> of >>>> projects. We did this in order to get a better sense of which projects >> are >>>> being actively shepherded versus having gone stale, and to identify for >>>> which projects we need to find a new shepherd who has sufficient time to >>>> dedicate to it. >>>> >>>> This is not a statement that the un-assigned tickets are not important, >>>> rather, we want to ensure that the people working on them have a >> shepherd >>>> with sufficient resources. >>>> >>>> We ask that you communicate (and agree!) with your shepherd before >>>> assigning them in Jira, so that they are not surprised when you reviews >>>> start getting posted. >>>> >>>> The benefit for the developer community should be that it will be more >>>> clear when working on a ticket whether there are sufficient resources in >>>> the community to iterate on it in a timely manner. >>>> >>>> Joris >>>> >> >> > > > -- > Christopher Hicks > Uber SRE > +1.757.598.2032
