Google Code-in preparation

Google Summer of Code has been a huge success for KDE in the last 6 years. Google is now accepting applications for Google Code-in. It is a contest for high-school students aged 13 to 18. Students can work on tasks in 8 different areas:

  • Code: Tasks related to writing or refactoring code
  • Documentation: Tasks related to creating/editing documents
  • Outreach: Tasks related to community management and outreach/marketing
  • Quality Assurance: Tasks related to testing and ensuring code is of high quality
  • Research: Tasks related to studying a problem and recommending solutions
  • Training: Tasks related to helping others learn more
  • Translation: Tasks related to localization
  • User Interface: Tasks related to user experience research or user interface design and interaction

and tasks are categorized as easy medium and hard. Students will be able to claim those tasks and work on them for a given timespan. After that the mentor can decide if the task was successfully completed or goes back into the pool for other students to claim it. Cool prizes are waiting for the best students at the end of the program.

For KDE to have a chance at taking part in Google Code-In this year we need to prepare an ideas page with a lot of great ideas to claim during the program. Please help me fill this page before Friday: Go Go Go!

If you want to find out a bit more about Google Code-In you can check or come to our info session on IRC this week. (Akarsh will blog more about it soon.)

5 thoughts on “Google Code-in preparation”

  1. Hello, it looks really nice, it is a really great opportunity. Do you thing creating “monochromatic” icons for Amarok, Akregator, KPackageKit… is a good task? (Section: User Interface.)

  2. … and Kopete – this one is quite important to me (personally, I prefer Kopete status icon to Message indicator one – Kopete reflects status and some other things much better – it can afford that, it depends on only one application).

  3. Yes that could be a good idea indeed. Best get in touch with the Oxygen team and see what they think about it. If they like it ask them to add it to the wiki page asap.

  4. Sounds nice…
    But I think as I’m already having a KDE svn-account, there’s no way for me to participate?

  5. I fear that is correct. You can probably participate for another project though. And of course you can help us find ideas 😉

Comments are closed.