Re: Google Code-in

[Andre Klapper <ak-47 gmx net>]

Hola,

On Mon, 2011-10-31 at 02:34 +0700, Andika Triwidada wrote:
> 2011/10/30 Коростіль Данило <ted korostiled gmail com>
> > I've added two tasks already. I'll try add more ones later.

> Ted's two entries
> https://live.gnome.org/GoogleCodeIn/Tasks#Translate_PiTiVi_documentation_into_Ukrainian
> https://live.gnome.org/GoogleCodeIn/Tasks#Translate_GAP_.28GIMP.29_into_Ukrainian
> stated more 7 and 10 days time estimation, while guideline at
> https://live.gnome.org/GoogleCodeIn/HowToWriteAGoodTask#Guidelines
> suggest 2 to 5 days.

Please keep your students in mind - tasks should be fun and an
introduction to open source, and not cheap gruntwork. ;-)

5 days for a task is the maximum, plus students might not have 8 free
hours a day either, as there's still school to do.

You can always define dependencies in task descriptions, like "This task
can NOT be claimed before task "Do foo in bar" has been marked as
completed".

Thanks,
andre
-- 
mailto:ak-47 gmx net | failed
http://blogs.gnome.org/aklapper | http://www.openismus.com