Google Code-in is in some ways the pre-university counterpart of Google Summer of Code, and KDE has has been a very successful mentoring organization since its first edition in 2010. Needless to say, we are applying to be a mentoring organization again this year.
If you are a prospective Code-in student, stay tuned – mentoring organizations have not been selected so we have no news for you yet. If we get accepted, we’ll be delighted to mentor you.
If you are a prospective Code-in mentor, please read on
The KDE student programs team has already applied on behalf of KDE, but to be successful we now need to add as many tasks as we can think of to the Google Code-in 2012 Ideas page in the KDE community wiki.
Most importantly, please only add tasks you are willing and available to mentor. Mentoring Google Code-in students is a very rewarding activity, but it takes a fair bit of patience and dedication.
A few things to keep in mind.
- Google Code-in is not just about code. We also need other tasks (likely even more than coding tasks).
- We need at least 5 tasks in each category to qualify.
- A task should take a normal KDE contributor about 2 hours. This is a guideline for you, to give you some idea of how much work a task should be. The actual time needed for students to complete a task can vary greatly. If you have doubts/questions feel free to ask the student programs team (teo- or Nightrose on #kde-soc).
- Unlike the previous years, there are no translation tasks.
- There is no distinction between easy/normal/hard tasks – while difficulty will of course vary between tasks, all tasks are treated the same.
- The mentoring organization gets to choose 2 grand-prize winners among our best students. This means students are much more likely to stick with one org throughout the Code-in season than in previous editions.
- The students don’t get money for each task. They get a Code-in t-shirt after clearing at least three tasks, and they compete for the grand prizes.
- Google expects a turnaround time on tasks of less than 36 hours, but we should try to get to less than 24 hours if at all possible.
- Check the timeline. If you are not available to approve and review tasks for some of that time please add that to the task description.
Our tasks list must be finished by November 5th, but please submit your tasks as early as possible.
Leave a comment
- RT @tomahawk: Tomahawk 0.7 is now live and auto-update is coming (Windows, OS X & Arch Linux). Other Linux packages coming soon. http:… 2 weeks ago
- KDE accepted for Google Summer of Code 2013 wp.me/p2uxRL-dA 1 month ago
- RT @tomahawk: Tomahawk 0.6.1 just released. Pushed updates to Windows and OSX. Linux updates coming soon. blog.tomahawk-player.org/post/462643637… 1 month ago
- RT @sup3rmark: Two weeks of no pope: baby cured of HIV, breath test for cancer, salt water found on moon of Jupiter. Day one with pope: ... 2 months ago
- RT @lfranchi: Repubblica headline says it all: "Ungovernable Italy". Just what we needed... 2 months ago