At Openmeetings we spent some time looking for mentors, and every mentor really helped at some point.
Upayavira's letter reminds me to say thanks to @Andrus, @Egor and @Ross. 24.03.2013 21:21 пользователь "Upayavira" <u...@odoko.co.uk> написал: > I have mentored at least two podlings where I am the only active mentor. > One had six mentors on the list, but I was the only one actually paying > any attention. We're not talking about occasional absenteeism, we're > talking not having participated since the beginning of the podling. One > podling I note two of the mentors don't even appear to be subscribed to > the dev list. > > I didn't sign up to being the *only* mentor. I'm not convinced that > having only me as a mentor is best for the project. Fortunately, there's > another ASF member who watches and chimes in, which I really appreciate. > > So sure, let's not force out people who are having a bad month or > something, but surely we should only be listing as mentors those that > are actually paying some attention to the podling? > > Upayavira > > On Sat, Mar 23, 2013, at 11:59 PM, Ross Gardler wrote: > > I'd suggest a different approach, the motivation for this suggestion is > > that I don't believe having inactive mentors is a problem if there is an > > active one available. Everyone gets busy occasionally, should we really > > be > > kicking them off a podling when they have already expressed interest? At > > next months report they might be the one who is active. They may have > > been > > active in the two months between reports. Etc. > > > > In my opinion there is only a problem if nobody is looking or if the > > podling community feels they are not getting the support they need. > > > > I therefore suggest reaching out to the podling rather than passing > > judgement on the mentors. > > > > Ross > > > > > > > > On 23 March 2013 10:23, Christian Grobmeier <grobme...@gmail.com> wrote: > > > > > Hello, > > > > > > I know at least one podling where 75% of the mentors is awol. We don't > > > have an oversight on the "awol"-state, just the shepherds do know for > > > the projects they shepherd. > > > > > > We have status reports, which should be signed by all mentors. I > > > believe reading, verifying and signing a podling report is not so much > > > work and it is the least a mentor should do. > > > > > > My proposal: > > > > > > We should contact all Mentors who have not signed a report 2 times in > > > a row if they are still committed to their role. If we get no response > > > within a week, we should remove them as a mentor from podlings.xml (or > > > give them an inactive flag). With this information clutch can report > > > projects which do not have sufficient mentors. > > > > > > Thoughts? > > > > > > Christian > > > > > > -- > > > http://www.grobmeier.de > > > https://www.timeandbill.de > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > -- > > Ross Gardler (@rgardler) > > Programme Leader (Open Development) > > OpenDirective http://opendirective.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
