ubuntu-bugcontrol team mailing list archive

[markus korn <thekorn@xxxxxx>]

On Thu, Nov 19, 2009 at 8:44 AM, Micah Gersten
<launchpad@xxxxxxxxxxxxxxxxxxx> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> markus korn wrote:
>> I don't know if this has already been discussed, but can't we use
>> launchpad to organize this mentorship program?
>> My idea is to have a restricted group called similar to
>> "~ubuntu-bugs-mentorship". All mentors are administrators of this
>> group (directly or via a separate team). People requesting mentorship
>> which do not have a mentor yet are in the "Pending approval" queue.
>> All mentees are approved members of this team.
>> This team should also be subscribed to all bugs a mentee is working
>> while participating in this program, this way it is easy to keep track
>> of what's going on.
>>
>> Markus
>>
>
> I think this would create a lot of excess bug mail.  If people have
> already adopted the packages they are mentoring, they should be getting
> the bugmail of the mentees.  This also would not match up mentees to
> mentors.
>
> Micah
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAksE92cACgkQTniv4aqX/Vm4LQCZAfUTJeLCEiyb9Xxbd/OVYFsk
> +psAn0aA369QnOV/vnnr/biYMueZKSQC
> =J8uu
> -----END PGP SIGNATURE-----
>

I'm personally not a big fan of this "this will create a lot of
(duplicate) mails"-argument, as your mail client should be able to
help you handling them. And we can always configure launchpad to send
all mails to the team ML instead of each team member.
My point is: I think it is mandatory to find a way to track bug
triaging activities related to the mentorship initiative to
 1.) find out how this program is going on for an individual mentee.
 2.) get an overall overview how successful this program is, how many
mentees are active at a certain point, are there some common mistakes
(maybe because of bad documentation), etc.

I agree, the mentee/mentor mapping can be solved easily by using launchpad