GoogleCodeIn/2010/Ideas

Guidelines

Information for Students

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

Adding a Proposal

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

• if the application is not widely known, a description of what it does and where its code lives
• a brief explanation
• the expected results
• pre-requisites for working on your project if any
• if applicable, links to more information or discussions
• mailing list or IRC channel for your application/library/module
• your name and email address for contact (if you're willing to be a mentor)
• difficulty of the proposal - must be one of easy, medium, hard
• time to complete the proposal
• the area the proposal is related to. This can be any of the following:
  • 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

If you are not a developer but have a good idea for a proposal, get in contact with relevant developers first.

Ideas

Oxygen

Icon junior joobs

Area: Design
Description: Oxygen need many many icons, some need to be updated to the new look and feel, some need to be created from scratch
Outcome: A more complete/modern oxygen icon set
Difficulty: medium
Time: 1 month
IRC: #Oxygen on freenode
Mailing List: all at oxygen-icons org
Mentor: Nuno Pinheiro ([email protected])

Amarok

conference poster

Area: Outreach
Description: Amarok needs a poster giving an overview of what Amarok is. It should be big, good-looking, easy to read and informative. http://amarok.kde.org/en/features can be taken as the basis for the poster but needs to be checked for correctness with the Amarok promo team.
Outcome: ready to print PDF of a shiny poster that will tell conference visitors more about Amarok.
Difficulty: medium
Time: 1 week
IRC: #amarok on freenode
Mailing List: amarok at kde org
Mentor: Lydia Pintscher (lydia at kde org)

KAlgebra

Mobile applet

Area: Code
Description: Think of what utilities you would like to have in your calculator and add them to KAlgebra Mobile version, it would be using some JavaScript bindings for KAlgebra so it would be quite simple.
Outcome: New and useful little tools ready to use on your device.
Difficulty: hard
Time: 1 week
IRC: #kde-edu on freenode
Mailing List: kde-edu at kde org
Mentor: Aleix Pol ([email protected])

Physics Library

Area: Code
Description: Think of one area that you like from your physics book and translate the formulae from your book into KAlgebra language.
Outcome: New library that will be available for everyone to use.
Difficulty: medium
Time: 1 week
IRC: #kde-edu on freenode
Mailing List: kde-edu at kde org
Mentor: Aleix Pol ([email protected])

Homework

Area: Documentation
Description: Try to solve different mathematics problems from class using KAlgebra. Explain how you did it, what turned out good and bad.
Outcome: For us, a good example on how KAlgebra is being used, for the rest an example of how to properly use KAlgebra.
Difficulty: medium
Time: 1 week
IRC: #kde-edu on freenode
Mailing List: kde-edu at kde org
Mentor: Aleix Pol ([email protected])