Revision as of 07:31, 24 October 2012

Guidelines

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

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.

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

The proposals should be ordered by area:

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
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.

Description: Improve internal APIs in Kexi. This can be done easily by introducing d-poitners to classes that lack them. Details on Kexi wiki.

Description: The content that is still useful should be moved to: community.kde.org/Amarok, userbase or techbase depending on target audience. Links to be made from a new page on amarok.kde.org linked to from the site's menu.

Description: Based on information from Amarok's "About" dialog, various social networks such as openDesktop.org, and talking to team members, make a "Team" page on Amarok's project website, like [1] or [2]. We're specifically interested in a nice design and layout, and can fill out the data ourselves later on.

Description: Review Kexi UI to find glitches while running under non-KDE desktop such as Unity, GNOME or Xfce. Since Kexi is highly portable software, it is desired to have it adaptable to current look and feel of the underlying desktop.
Any found issue, suggestion or doubt should be reported. Proposing solutions is welcome too but not necessary. Providing screen shots and details of system (desktop) configuration is expected. No software engineering skills are needed. User-level understanding of Kexi is preferred.
Mentor: Jstaniek (talk)

@@ Line 82: / Line 82: @@
 === Kexi: find UI issues while running under non-KDE desktop ===
-;Description:Review Kexi UI to find glitches while running under non-KDE desktop such as Unity, GNOME or Xfce. Since Kexi is highly portable software, it is desired to have it adaptable to current look and feel of the underlying desktop. <br>Any found issue, suggestion or doubt should be reported. Proposing solutions is welcome too but not necessary. Providing screen shots and details of system (desktop) configuration is expected. No software engineering skills are needed.
+;Description:Review Kexi UI to find glitches while running under non-KDE desktop such as Unity, GNOME or Xfce. Since Kexi is highly portable software, it is desired to have it adaptable to current look and feel of the underlying desktop. <br>Any found issue, suggestion or doubt should be reported. Proposing solutions is welcome too but not necessary. Providing screen shots and details of system (desktop) configuration is expected. No software engineering skills are needed. User-level understanding of Kexi is preferred.
 ;Mentor: [[User:Jstaniek|Jstaniek]] ([[User talk:Jstaniek|talk]])