public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: Douglas Anderson <dja@gendja.com>
Cc: Gentoo project list <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] Improving our people
Date: Wed, 21 Jan 2009 08:55:19 -0800	[thread overview]
Message-ID: <20090121165519.GA12642@comet> (raw)
In-Reply-To: <efeb8d230901202304r788e0289r885e63c81847f2f6@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]

On 16:04 Wed 21 Jan     , Douglas Anderson wrote:
> On Wed, Jan 21, 2009 at 1:32 PM, Donnie Berkholz <dberkholz@gentoo.org> wrote:
> > On 20:30 Tue 20 Jan     , Donnie Berkholz wrote:
> >> It isn't necessarily obvious from a recruiter's interaction with a
> >> mentor whether he is good at the actual task of mentoring.
> >
> > We could take a tip from the Summer of Code and have both mentor and
> > mentee fill out a quick eval at the end of probation. This would perhaps
> > be more valuable over a longer probation.
> >
> 
> The evaluation is a good idea, but it would have to be something maybe
> only devrel had access to.

How would mentors know what they need to improve upon?

One way to answer this is to have 2 sections -- 1 optional section that 
only recruiters see, and 1 that the mentor sees.

> With the Summer of Code, many students leave the project after they're 
> finished,

The best ones stay. And they fill out evals too, so it's clearly a 
solvable problem.

> but with a new dev they're just starting a (hopefully) long 
> relationship with their mentor. I personally would hesitate to point 
> out the weak points of an experienced developer if I were just 
> starting out here. Something to think about...

I would love to improve my mentoring, and suggestions to help me are 
welcome. Pointing out unfixable weak points is also welcome because 
those are areas I should avoid, instead focusing on what I'm good at.

-- 
Thanks,
Donnie

Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2009-01-21 16:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-17 18:53 [gentoo-project] Improving our people Donnie Berkholz
2009-01-18  1:10 ` Wulf C. Krueger
2009-01-18 20:55 ` Petteri Räty
2009-01-20 23:47 ` Denis Dupeyron
2009-01-21  4:30   ` Donnie Berkholz
2009-01-21  4:32     ` Donnie Berkholz
2009-01-21  7:04       ` Douglas Anderson
2009-01-21 16:55         ` Donnie Berkholz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090121165519.GA12642@comet \
    --to=dberkholz@gentoo.org \
    --cc=dja@gendja.com \
    --cc=gentoo-project@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox