Hi Andre,
Sorry i didn't have much time, is there still time for us? So far I got only few categories of easy tasks, which on other hand are really easy, so maybe not even suitable (they don't really require much thinking). These are:
Localization in source code - find elements which have hardcoded english and implement localization macros on them, so that they are retrieved by key from xml files (basically replacing hardcoded strings with some C++ code) this can be more complicated for gui elements, where new functions may need to be created, but it's still very trivial task, that requires beginner c++ knowledge.
Update of deprecated code - we have some nice functions, that could be used on many places, so basically rewriting some parts of code utilizing them.
Update of deprecated API calls - some MW api's were deprecated in recent days, queries used in huggle need to be updated.
I believe all these categories are suitable for newbie programmers, but I don't really know if it's kind of tasks you would like to have at code in. What do you think? Should I create bugs for these?
If someone has an idea for other easy tasks, let me know.
P.S. I have a number of harder tasks as well, but these may require deep knowledge of C and C++.
On Fri, Nov 7, 2014 at 2:25 PM, Andre Klapper aklapper@wikimedia.org wrote:
On Fri, 2014-11-07 at 13:22 +0100, Petr Bena wrote:
This is a good idea, I will try to get some easy tasks and will list myself there. Thanks
That's awesome, thank you, Petr! Plus we'll have another interesting programming language in the mix!
Feel free to drop your rough ideas on https://www.mediawiki.org/wiki/Google_Code-in_2014#Proposed_tasks (as Google will take a look at that list on Monday). We can still polish them until Dec 01st when Code-In starts. Also, it probably makes sense to have a Huggle section under https://www.mediawiki.org/wiki/Google_Code-in_2014#Common_instructions_for_t... with general information and links (where to find the code, how to compile, etc).
Cheers & thanks! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/
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:
Sorry i didn't have much time, is there still time for us?
Sure. You can add tasks at any time until the contest ends in January.
So far I got only few categories of easy tasks, which on other hand are really easy, so maybe not even suitable (they don't really require much thinking). These are:
[...]
I believe all these categories are suitable for newbie programmers, but I don't really know if it's kind of tasks you would like to have at code in. What do you think? Should I create bugs for these?
These sound like good cases for me, so yes, feel free to create tickets.
P.S. I have a number of harder tasks as well, but these may require deep knowledge of C and C++.
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
Ok, I am just wondering why both tasks are now marked as not a beginner tasks. At least the localization task is rather trivial, so I believe that everyone with basic programming knowledge should be able to do that.
Thanks
On Tue, Nov 11, 2014 at 5:25 PM, Andre Klapper aklapper@wikimedia.org wrote:
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:
Sorry i didn't have much time, is there still time for us?
Sure. You can add tasks at any time until the contest ends in January.
So far I got only few categories of easy tasks, which on other hand are really easy, so maybe not even suitable (they don't really require much thinking). These are:
[...]
I believe all these categories are suitable for newbie programmers, but I don't really know if it's kind of tasks you would like to have at code in. What do you think? Should I create bugs for these?
These sound like good cases for me, so yes, feel free to create tickets.
P.S. I have a number of harder tasks as well, but these may require deep knowledge of C and C++.
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/
On Wed, 2014-11-12 at 09:33 +0100, Petr Bena wrote:
Ok, I am just wondering why both tasks are now marked as not a beginner tasks. At least the localization task is rather trivial, so I believe that everyone with basic programming knowledge should be able to do that.
Beginner tasks are supposed to take less than 30 minutes to an experienced contributor. They are supposed to be "less technical in nature".
If you are sure that the tasks fit into that category (time constraints and not too technical), feel free to set them as beginner tasks again.
Thanks, andre