Google's Code-In in progress
The Haiku project was once again chosen as a mentor organization for this year's Google Code-In. The little brother of the Summer of Code is targeting younger students - 13 to 17 years old - and consists of many small tasks that are suitable for that age group. Under the lead of Scott McCreary, over a dozen Haiku mentors have entered roughly 400 tasks into Haiku's GCI page, mostly about creating or fixing haikuporter recipes to package applications and small C++ coding tasks.
Every student that completes at least one task gets a certificate and for at least three tasks additionally a t-shirt. The five best students per organization win a sweatshirt and two of those will be invited to visit the Google headquarters in California in June 2015.
The GCI starts on December 1st and ends on January 19th. In that time many students will probably hit the forums and IRC. Please give them a warm welcome! If you're eligible to participate (or if you know students that might be interested), the Google GCI page has all the info.

Comments
Re: Google's Code-In in progress
Keep Google out of Haiku ! My 2 cents.
Re: Google's Code-In in progress
Did you read what Google code-in is? I would warmly suggest to read about what it is, then you can give way more then 2 cents.
Re: Google's Code-In in progress
In first place, a big "Welcome" to the students that participate in this GCI.
Second, is nice to see all the tasks that already had been done.
Sincerely, thanks for your cooperation!!! (students and mentors)
Re: Google's Code-In in progress
Well, I didn't want to say any more than that, but as you have attacked me, you leave me no choice.
I do know what Google Code-In is, and it's not philanthropy. Just like gmail is not philanthropy.
Haiku is currently the world's best O/S. Should it be surprising that Google is interested in Haiku ? How long until every Haiku release includes a "Google demon", just as Apple's OSX includes a google "updater" when any google software is installed. I have a powermac that I frequently leave on. The disk drive would spontaneously begin furious disk activity. And the machine was dumping lots of data to the internet. Whenever the machine was booted, this would start immediately. By installing "Little Snitch", the cause was traced to Google "updater". Maybe it should be called google uploader. I deleted it, and the problem went away. Later I tried to run google earth, and got the message "to run google earth you must agree to allow google updater to run in the background". It's a trojan horse. If you want Haiku to remain the world's best O/S, keep Google out of Haiku !
Re: Google's Code-In in progress
I believe you don't know how Google Code-In work, even if you know what it is.
So, yes, we do get some money from Google after this, but not that much if you count the hours spent by the mentors and other people on the IRC channels helping the students making their first steps with Haiku.
You may now be asking yourself why Google is running this. Certainly not philantropy (no one would believe that even if they said so). Here is their explanation which I think is convincing:
So, what do we get: a money compensation from Google, and lot of young people knowing about Haiku and maybe joining the ranks of our developers or just hanging around (oh, and did I mention free T-Shirts?). What do we risk: not much, and if that ever changed we would just stop entering GCI or similar programs.
Google is big, so big that you can't really reject everything in block about it. We can be critical when they do things wrong, but we can also be supportive when they do great things such as GCI. You may think this is "open-source-washing" from them (like there is "greenwashing" for others), and you may be right. But it actually benefits both Google and the participating projects. Why deny that then?
Re: Google's Code-In in progress
All true, only that we don't get any money for GCI only for our GSoC participation. We did get a donation from Google some time back, that may be construed as a thank you for our efforts in GCI over the years, but it was never declared as such.
Regards,
Humdinger
Re: Google's Code-In in progress
Re: Google's Code-In in progress
Thanks for the clarification -- it is greatly appreciated.