The incubator is a very large committee with a lot of moving parts. To pick an example off the top of my head, let's look at the mentoring situation. What we generally do with new mentors is say hey so and so I trust you will do a good job of watching over this podling for us. What we don't have right now are any general agreements of what "doing a good job" entails. Sure there are probably some docs about the subject, but different people will interpret the relative merits of every bullet point in different ways. The things we ask them to do, like sign off on reports etc, are just ways of taking their pulse. What we need is some place where they can talk to other mentors about what they're supposed to be doing, what is actually important versus what isn't, etc etc. If issues pop up they can shoot off an informal email to the mentoring working group before having things escalated to incubator-private the way they do now. You might say they could contact other, more senior mentors on the project but then again it's a crap shoot about the type of response you receive.
There are other examples, like on boarding and off boarding, where more focused collaboration would serve the org well. Docs are great, but they don't replace the personal touch. On Thu, Oct 15, 2015 at 3:48 AM, Joe Schaefer < joe_schae...@yahoo.com.invalid> wrote: > That's certainly a reasonable approach, but it doesn't quite capture what > I'm talking about when I mention the concept of having individual working > groups to do more focused collaboration on specific areas of work > activity. Where these conversations take place isn't really all that > important, what is important is that we have them. > > > > On Thursday, October 15, 2015 3:38 AM, Bertrand Delacretaz < > bdelacre...@apache.org> wrote: > > > On Thu, Oct 15, 2015 at 5:05 AM, Joe Schaefer > <joe_schae...@yahoo.com.invalid> wrote: > > ...Formally, that's all a working group needs to be- yet another mailing > list.... > > I'm not in favor of more mailing lists, I think [tags] in subject > lines can pretty much do the same thing without splitting the > community (as per Stefano Mazzocchi's busy lists pattern [1]). > > So maybe just define a set of such tags like [graduation], [proposal] > [release] etc. but stay here. > > -Bertrand > > [1] > http://grep.codeconsult.ch/2011/12/06/stefanos-mazzocchis-busy-list-pattern/ > > > >
