Information for Students

This page is for collecting ideas for Google Code-in tasks. The tasks will be moved into the GCi app for you to claim when appropriate.

Adding a Proposal

Please only add proposals you are willing to mentor!

Please keep in mind that the tasks are going to be solved by 13 to 17 year olds. We have a particular need for beginner tasks.

When adding an idea to this section, please try to include the following data:

  • a brief explanation
  • the expected results
  • prerequisites for working on your project if any
  • if applicable, links to more information or discussions
  • your name and email address for contact

The proposals should be ordered by area:

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

If you have a good idea for a proposal but are not going to mentor it, get in contact with relevant team/contributor first.



Beginner: Do your first commit

Clone the project the firstcommit. Add your name to the in the format specified. And push your commit to the repo. Take the screenshot of the uploaded commit by visiting



Beginner: Connect to the #KDE-soc channel on freenode, introduce yourself, and have a conversation with someone

  • To connect to IRC, either install and use a client, such as KDE's Konversation, mIRC on Windows, or Colloquoy on Mac; OR use webchat:
  • Once you have connected to, join the #kde-soc channel (/join #kde-soc) and introduce yourself. Explain that you are doing a beginner GCi task, and that to finish that, you need to talk to someone. You might ask questions that help you in your future tasks, as IRC is how many of us communicate on a daily basis.
  • Submit a screenshot of the beginning or end of the conversation.

Beginner: Subscribe to the KDE-Soc mail list, and introduce yourself

  • Subscribe to our student mail list, KDE-Soc. This is for all students who want to subscribe, whether or not they are enrolled in Google Code-in, Google Summer of Code, or Season of KDE. for information on how to subscribe.
  • Once you have confirmed your subscription, send a post to the list introducing yourself. This means sending an email to [email protected]
  • Once you have sent your post, find it in the archives at and submit the link to your email to finish the task.
  • You may unsubscribe after posting if you like, however you are welcome to stay subscribed if you like. This is valuable if you plan to participate in later student programs.

Beginner: How did you get to know about KDE?

Write a short 5 paragraph essay answering and explaining the above. You should ideally state your experience about "that first time" when you heard/read about KDE. You can also include the information about what you know about KDE till now.

Quality assurance

User interface

This page was last edited on 22 October 2017, at 20:20. Content is available under Creative Commons License SA 4.0 unless otherwise noted.