Hi Petr, thanks for the tasks you've added to https://www.mediawiki.org/wiki/Google_Code-in_2014 ! I've edited them a little bit. I will transfer them to Google Melange once Google announces which organizations are accepted for this round of Google Code-in. For general info and expectations towards mentors, please read https://www.mediawiki.org/wiki/Google_Code-in_2014#Mentors.27_corner and ask if something is unclear. :) On Tue, 2014-11-11 at 14:20 +0100, Petr Bena wrote: Sure. You can add tasks at any time until the contest ends in January. [...] These sound like good cases for me, so yes, feel free to create tickets. If those harder tasks are self-contained, non-controversial tasks that would take an experienced developer 2-3 hours that would be suitable. You can always clearly state in the task description that a student applying for the task MUST be an experienced C/C++ developer already. In the end it all depends on how clear the task description is when it comes to expectations - that avoids bad surprises, disappointment or even wasted time on both sides. For example if you wrote "Expected time depends on number of strings that would be fixed" a student would not know how much s/he is supposed to fix. You could add a rough number to communicate expectations. Imagine you are a student who has never heard of Huggle before - will they be able to follow the task description and fully know what they are supposed to do? If that is not the case, you might have to ask more questions of those students on IRC. ;) Could you also edit the general Huggle information (to be included in each GCI task for Huggle) under https://www.mediawiki.org/wiki/Google_Code-in_2014#Huggle ? Currently as a "clueless student" I'd have no good idea where to find its code, how to compile it, how to test my changes, etc. Pointers welcome (could be just a link to a wikipage explaining that already)! Thanks! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/