I'm with Alan on our penchant to solve people problems with reorganization. We lack tangible means of measuring and recognizing that actual oversight is happening in these podlings. And by that I mean that somebody is actually following along as the project develops and providing them with requisite guidance.
This whole idea of technology subgroups harkens back to the original organizational structure at Apache, which we abandoned a long time ago because it wound up despoiling our real goal of self- governance. Why it's being reintroduced again just means to me that we don't ever learn from our past mistakes. >________________________________ > From: Upayavira <u...@odoko.co.uk> >To: general@incubator.apache.org >Sent: Saturday, June 15, 2013 10:16 AM >Subject: Re: Incubator reorg ideas: sub-groups per technology? > > >I think there's merit in the idea of multiple, smaller incubators, so >long as it is set up in a way that doesn't involve prospective podlings >playing the incubators against each other. > >Smaller groups, with smaller membership, gives the chance of a greater >sense of ownership and identification, which are important to community >building. > >Upayavira > >On Fri, Jun 14, 2013, at 11:58 PM, Shane Curcuru 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 > > > >
