> > Empower the Mentors to run the podlings, teach the newcomers and bring it > to TLP. >
As a mentor of podlings, I dislike the above idea. Mentors get busy, they miss things, sometimes big things. Sometimes things that are obvious to an outsider are missed by mentors who don't catch it. I've certainly been guilty of missing things, and having an 'outside IPMC member' call attention to that has caused me to go find not just that problem, but other problems with a podling. Even on smaller issues, Justin and Sebb run circles around me in validating that releases comply with policy. I've voted affirmatively on releases that Justin or Sebb has found issues; occasionally glaring issues. I do not think that just because I am a mentor on $project and they aren't invalidates concerns they may raise. I may have additional insight, and be able to explain things. Similarly, a vote was brought to the IPMC as to whether or not to recommend graduation. We asked people to inspect the podling and vote, and for some reason seem displeased when everyone doesn't unanimously agree with the mentors. I am not sure whether to interpret that as 'non-mentor IPMC votes are discouraged', or whether 'dissenting opinions are discouraged'. But telling the body responsible (the IPMC) to leave podlings in its charge alone, particularly when prompted by a vote called by the podling itself hardly seems appropriate. --David --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
