Revision as of 13:53, 30 October 2012

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

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:

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

Ideas

Code

KDE Telepathy: Allow the user to configure the theme for group chats

Description: Currently a user can configure the theme used for normal 1-1 chats, but group chats are hardcoded to use a different theme. We should have a way to configure which theme is used for group chats as well

https://bugs.kde.org/show_bug.cgi?id=282518

Prerequisites: C++, Qt

Mentor

The KDE Telepathy Team (#kde-telepathy on freenode, or [email protected] (be sure to join the mailing list first, otherwise your email may get lost))

KDE Telepathy: Provide an option on whether to go offline when the contact list closes

Description: Currently when a user goes offline they remain online if the presence applet is visible, otherwise it shows a prompt "Do you wish to go disconnect your accounts y/n". If a user selects the option "Do not show again" this never appears again and the user can never change this. Student should add an option in KDE Telepathy to say what should happen when the contact list closes.

https://bugs.kde.org/show_bug.cgi?id=306853

Prerequisites: C++, Qt

Mentor

The KDE Telepathy Team (#kde-telepathy on freenode, or [email protected] (be sure to join the mailing list first, otherwise your email may get lost))

Amarok: Check Copyright Headers and Collect Contributor Email Addresses

Description: Amarok should be GPLv2+ licensed throughout, but not all license headers seem to contain the correct statement. Some files even miss a license header. If there is a incorrect license stated in a header the copyright holders should be contacted before making the fix. It could have been intentional (unlikely). It's useful to know who contributed to various parts of Amarok and during which period for statistical reasons. If we get a complete list and manage to maintain it, any future license changes (ex. to GPLv3) will be easier.

Mentors

Kexi: add d-pointers to classes

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

Prerequisites: General C++ knowledge, prior knowledge of Qt is a plus.

Mentor: Jstaniek (talk)

Pairs: add Get Hot New Stuff upload feature to Pairseditor

Description: Create a new action to provide the user to upload hers/his new Pairs Theme to a public server to make it available for the Get Hot New Stuff feature in the game.

Mentors: Marco Calignano and Aleix Pol

KGet: Code Stlye Check and Cleanup

Description: KGet currently consists of several lines of code which do not confirm to the KDE coding conventions. The task is to have KGet's codebase follow the coding conventions.

Mentors: Aish Raj Dahal [1], Lukas Appelhans [2]

KStars: Review formatting styles used in KStars

Description: There are many coding styles and variable naming conventions used in KStars. We would like to have them reviewed, file by file, to get an overview of the situation. This information would be then used to decide on recommended style guide for KStars.

Mentors: Rafal Kulaga (rl.kulaga [at] gmail.com)

Documentation/Training

KDE Telepathy: Update account creation documentation

Description

This task consists of 3 parts all of which must be completed:

* Update http://userbase.kde.org/Telepathy#1._How_do_I_add_a_new_IM_accounts to be more detailed with a step by step walkthrough with pictures
* Add a guide on how to add a GTalk account if you use Google 2 Factor Authentication (https://bugs.kde.org/show_bug.cgi?id=303351) 
* Update this page http://kdetalk.net/howtoregister.php to show how you'd do it with KTp details (https://bugs.kde.org/show_bug.cgi?id=303923)

Prerequisites

Be a user of KDE Telepathy. Good grasp of English. Able to take screenshots

Mentor

The KDE Telepathy Team (#kde-telepathy on freenode, or [email protected] (be sure to join the mailing list first, otherwise your email may get lost))

Amarok: Reorganize wiki in its new location

Description: Amarok is changing the location of its wiki and also needs to reorganize its wiki structure. Previously everything was in the same wiki, now we are moving to the 3 wiki site of KDE: Techbase, Community and Userbase. The existing pages need to be checked for consistency and moved to their new location after having made a structure plan.

Prerequisites: The student should be able to grasp large sets of data and be able to organize these in a logical manner. Some basic mediawiki editing knowledge is a plus.

Links

Mentor: Myriam Schweingruber, Mamarok in #amarok on irc.freenode.net

Update KSirK documentation

Description: KSirK documentation is moderate outdated (outdated screenshots, no description of new main menu items). Student should download documentation source and update it using HTML version as a reference, new screenshots for the default KDE theme (Oxygen) should be also presented.

Prerequisites: Moderate level of English, KDE distribution installed or run from live image.

Links

Mentor: Yuir Chornoivan

Kamoso: Create documentation

Description: Kamoso is a great program to use your webcam to take pictures or make videos, but we don't have a documentation to help our users. The student should download, install this application and use it and make a good documentation describing the main elements of the interface, such as how to take a picture, a video, what's the burst mode doing and how to share pictures and videos through facebook or youtube.

Prerequisites: Be able to install Kamoso. Good grasp of written English.

Links

Kamoso in KDE-Apps

Mentor: Alex Fiestas

Pairs Editor: Create documentation

Description: Pairs is a relatively new educational aplication of KDE Edu family. Pairs stimulates your memory and logic skills. It aims to help the learning for pre-school kids. We don't have a documentation to help our users to create their themes. The student should download, install this application and use it and make a good documentation describing the main elements of the interface, such as how to open a theme, create a new one and add all the needed information to have it ready for usage.

Prerequisites: Be able to install Pairs. Good grasp of written English.

Links

Pairs in userbase

Mentor: Aleix Pol

Pairs Editor: Create Tooltips strings

Description: The students should add tooltips on each component in the GUI to give valuable help to the user. These should be short and clear.

Prerequisites: Be able to use QTDesigner. Good grasp of written English.

Mentor: Marco Calignano

Pairs Editor: Create What's This strings

Description: The students should add "What's This" string on each component in the GUI to give valuable help to the user. These should be short and clear.

Prerequisites: Be able to use QTDesigner. Good grasp of written English.

Mentor: Marco Calignano

Outreach/Research

Amarok: Make a "Team" page

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 [3] or [4]. We're specifically interested in a nice design and layout, and can fill out the data ourselves later on.

Mentor

Amarok: LikeBack statistics

Description: Amarok uses the Likeback feedback gathering system. Likeback is a client-server system. Its client component is a library which puts like/dislike buttons in the top right area of all the windows in an application, that allow users to send context-sensitive feedback. The server component runs on a web server hosted by the Amarok team which stores the feedback entries in a database. There's quite a lot of feedback messages, and the Amarok team hardly has the time to go through all of them. We need someone to take the database dump and analyze all the feedback gathered in the past year or so and produce a detailed report with like/dislike/feature statistics and prominent requests.

Expected results: A thorough report, maybe in a PDF document or spreadsheet, with statistics and comments.

Prerequisites: spreadsheet use, basic writing skills and lots of patience.

Mentor: Teo or Myriam, tbd

KDE Forums: clean up KDE Brainstorm

Description: Currently the KDE Brainstorm (http://brainstorm.forum.kde.org) includes a lot of invalid, duplicate, or already fixed ideas. In order for both users and developers to screen them effectively, they need to be reorganized. The Brainstorm interface already allows to do this: the task involves looking through the open ideas and mark them as fixed, invalid, in [Teo Mrnjavac <[email protected]>progress, or finished.

Prerequisites: Some general knowledge about the current progress of KDE software, including recent developments.

Mentor: Luca Beltrame ([email protected])

Metrics: Check Ohloh organisation page

Description: KDE is a showcase in Ohloh's new organisation feature. We need to make sure the information in the project is accurate. Please check if there are any missing projects in the project listing and if they are correctly categorized as being a KDE project. Check for other improvements that can be done and suggest them.

Mentor: Lydia Pintscher

Metrics: MLStats

Description: Investigate MLStats and create some useful statistics for 3 mailing lists. Document your findings and work so it can be extended later.

Mentor: Lydia Pintscher

Metrics: Git stats

Description: Investigate some options to get statistics out of git that let us learn more about the project and the people working on it. Document your findings and their benefits, drawbacks and what the individual options can do.

Mentor: Lydia Pintscher

Promo: new Twitter and identi.ca backgrounds

Description: Create new backgrounds for identi.ca and Twitter similar to the ones at Promo/Material/Microblogging.

Mentor: Lydia Pintscher

KDE e.V.: Create board timeline

Description: Create a timeline for the board of directors of KDE e.V. similar to http://meta.wikimedia.org/wiki/Wikimedia_Board_of_Trustees#Chart.

Mentor: Lydia Pintscher

Promo: Create a timeline of important events in KDE's history

Description: Create a timeline of important events in KDE's history.

Mentor: Lydia Pintscher

Promo: Create an overview of KDE

Description: Create a mindmap to give an overview of KDE similar to http://de.wikipedia.org/w/index.php?title=Datei:WikimediaMovementMindmap-October2012.svg.

Mentor: Lydia Pintscher

KStars: Add a custom catalog

Description: The Catalog selected is the "Saguaro Astronomy Club catalog". Reformat and clean up the existing catalog to make it compatible for loading into KStars.

Mentor: Rishab Arora (ra.rishab [at] gmail.com)

KStars: Propose outreach actions to popularize KStars among amateur astronomers

Description: We would like to hear some fresh and unbiased opinions about outreach actions we can undertake to popularize KStars. Maybe we should use social media? Or maybe there are some nice astronomy related websites whose APIs we should implement to make KStars more attractive and useful?

Mentor: Rafal Kulaga (rl.kulaga [at] gmail.com)

Promo: Propose updates for KDE's events calendar

Description: KDE maintains an event calendar at http://events.kde.org/upcoming.php. Research dates of future events we've attended before and make a list of dates, locations and links for them.

Mentor: Lydia Pintscher

Join the Game: Come up with ideas for a social media campaign

Description: KDE e.V. is running an individual supporting membership program called Join the Game to help raise funds and connect to members. Come up with ideas for a social media campaign to raise awareness of the program. Look at what other organisations have done like the Ada Initiative.

Mentor: Lydia Pintscher

Quality Assurance

KDE Telepathy: go through our testing specification

Description

We have a testing specification that we go through before every release. http://community.kde.org/Real-Time_Communication_and_Collaboration/ReleaseTesting. We require a student to go through this test procedure and see if there are any problems with the current code

Prerequisites: Running the latest KTp from source

Mentor

The KDE Telepathy Team (#kde-telepathy on freenode, or [email protected] (be sure to join the mailing list first, otherwise your email may get lost))

Pairs Editor: testing it

Description: The Pairs Editor is a new application and needs to be tested by actual users. The student will have to try create a pairs theme using the editor and help us figure out the parts that are not working that well.

Mentors: Marco Calignano and Aleix Pol

Amarok: Testing from git

Description: While Amarok ships a stable version there also is the current development version. The student should build a development installation from git and test the main functions of Amarok and report back eventual errors, inconsistencies and bugs.

Prerequisites: The student must be able to follow clear written instructions, have a logical way of thinking. Must be able to test software independently after a short introduction

Links

Mentor: Myriam Schweingruber, Mamarok in #amarok on irc.freenode.net

User Interface

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

Prerequisites: Ability of gathering data from users, aggregating it and structuring; UI design/analytic skills are welcome.

Mentor: Jstaniek (talk)

Pairs: create a new icon for Pairs Editor

Description: Modify the Pairs game icon to create a new icon for the Pairs Editor

Mentors: Marco Calignano and Aleix Pol

KAlgebra Mobile: figure out a touch-friendly keyboard

Description: We have had KAlgebra working for more than a year now and it works great. Now the problem is that the input method we're using uses the default keyboard in the device. That's good because it feels integrated, but it would be interesting to have our own keyboard targeting KAlgebra's language. In this task you'll have to design a keyboard either through a mock-up or a QML file (better) that will let the user enter any equation supported by KAlgebra's language.

Mentor: Aleix Pol Gonzalez <[email protected]>

KStars: propose UI design for mobile version of KStars

Description: We are planning to port KStars to mobile devices, tablets in particular. We would like to gather as many UI design concepts as possible. The scope of the design is to be considered, as well as the method of recording it.

Prerequisites: UI design skills and enthusiasm for work. Preferably amateur astronomer and KStars user. No coding skills needed.

Mentor: Rafal Kulaga (rl.kulaga [at] gmail.com)

KStars: design an icon for AstroBin.com API feature

Description: We are introducing AstroBin.com API support in KStars, so we're looking for a neat icon for its configuration page in Options window.

Mentor: Rafal Kulaga (rl.kulaga [at] gmail.com)

@@ Line 175: / Line 175: @@
 ;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 [http://tomahawk-player.org/about.html] or [http://chakra-project.org/team.html]. We're specifically interested in a nice design and layout, and can fill out the data ourselves later on.
 ;Mentor:
+=== Amarok: LikeBack statistics ===
+;Description: Amarok uses the Likeback feedback gathering system. Likeback is a client-server system. Its client component is a library which puts like/dislike buttons in the top right area of all the windows in an application, that allow users to send context-sensitive feedback. The server component runs on a web server hosted by the Amarok team which stores the feedback entries in a database. There's quite a lot of feedback messages, and the Amarok team hardly has the time to go through all of them. We need someone to take the database dump and analyze all the feedback gathered in the past year or so and produce a detailed report with like/dislike/feature statistics and prominent requests.
+;Expected results: A thorough report, maybe in a PDF document or spreadsheet, with statistics and comments.
+;Prerequisites: spreadsheet use, basic writing skills and lots of patience.
+;Mentor: Teo or Myriam, tbd
 === KDE Forums: clean up KDE Brainstorm ===
-;Description: Currently the KDE Brainstorm (http://brainstorm.forum.kde.org) includes a lot of invalid, duplicate, or already fixed ideas. In order for both users and developers to screen them effectively, they need to be reorganized. The Brainstorm interface already allows to do this: the task involves looking through the open ideas and mark them as fixed, invalid, in progress, or finished.
+;Description: Currently the KDE Brainstorm (http://brainstorm.forum.kde.org) includes a lot of invalid, duplicate, or already fixed ideas. In order for both users and developers to screen them effectively, they need to be reorganized. The Brainstorm interface already allows to do this: the task involves looking through the open ideas and mark them as fixed, invalid, in [Teo Mrnjavac <[email protected]>progress, or finished.
 ;Prerequisites: Some general knowledge about the current progress of KDE software, including recent developments.