[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-frameworks-devel
Subject:    Re: let's get ready for Google Summer of Code 2014
From:       Myriam Schweingruber <myriam () kde ! org>
Date:       2014-02-11 16:47:48
Message-ID: CAGzoOB_xH5QES2qu2a7fLY9AGEoDeuSJ_K5n595tuaqu6HQhzg () mail ! gmail ! com
[Download RAW message or body]

On Tue, Feb 11, 2014 at 12:36 PM, Sebastian Kügler <sebas@kde.org> wrote:
> On Tuesday, February 11, 2014 11:03:39 Myriam Schweingruber wrote:
...
>> And no, it is not enough to be able to guide, you also need people
>> available who can review code. I was able to mentor twice in the past
>> because I was around to help the student find solutions and nag them
>> to give the requested regular feedback and to make sure they respected
>> the deadlines and had somebody to talk to when there are problems, and
>> I had several people at hand who could do the code reviewing part,
>> something I definitely can't do myself. So if nobody is around to
>> review the code, then don't suggest a project, as it is a necessary
>> step in the process.
>
> I agree, though in practice, the work can often be spread out. What works is
> having one person to do most of the mentoring tasks, and someone else (or more
> people) who can help with reviewing code. Not everything has to be done by a
> single person.

That is exactly what I meant: one for the bureaucracy side of the GSoC
(what I did), and a group of people to review the code (as done in
Amarok) is the ideal setup IMHO


Regards, Myriam
-- 
Proud member of the Amarok and KDE Community
Protect your freedom and join the Fellowship of FSFE:
http://www.fsfe.org
Please don't send me proprietary file formats,
use ISO standard ODF instead (ISO/IEC 26300)
_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

[prev in list] [next in list] [prev in thread] [next in thread]