I proposed this a year or so ago. It was fairly soundly rejected for a number of reasons, the two I recall (because I felt they had significant merit) were:
a) adds additional hierarchy b) impossible to decide where a project best fits These two things together give the potential for silos. I don't think we discussed models for solving the silo problem. Ross On 14 June 2013 23:58, Shane Curcuru <a...@shanecurcuru.org> wrote: > Apologies if this horse has been beaten already, but... have we discussed > the concept of splitting incubator operations into a handful of separate > groups, based on technology areas? > > I.e. while the IPMC or ComDev or whoever would still set policy and provide > community best practice guidance. But then separate mailing lists/groups > would provide actual oversight of podlings (incoming, mentoring, > graduating). These would be based on rough technology areas: java, hadoop, > servers, UI, whatever. > > That way, people could participate in governance oversight and mentoring in > focus areas that they care about, and not have to immediately deal with the > many other podlings that are not related in terms of technology/interest > areas. > > Obviously there's a lot about coordinating suggested feedback on policies, > best practices, etc. between the groups and the core IPMC/ComDev., but it > would (hopefully) result in most of the groups being much quieter, and more > focused. > > - Shane, off to make a G&T > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
