- 1 Guidelines
- 2 Ideas
- 2.1 Code
- 2.2 Documentation/Training
- 2.3 Outreach/Research
- 2.4 Quality Assurance
- 2.5 User Interface
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.
Kexi: add d-pointers to classes
- Improve internal APIs in Kexi. This can be done easily by introducing d-poitners to classes that lack them. Details on Kexi wiki.
Pairs: add Get Hot New Stuff upload feature to Pairseditor
- 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.
Amarok: Reorganize wiki in its new location
- 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.
- 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.
- Current wiki location
- Main target in the community wiki
- Techbase main target page
- Userbase main target page
- Myriam Schweingruber
Amarok: Make a "Team" page
- 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  or . We're specifically interested in a nice design and layout, and can fill out the data ourselves later on.
KDE Forums: clean up KDE Brainstorm
- 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.
- Some general knowledge about the current progress of KDE software, including recent developments.
- Luca Beltrame ([email protected])
Metrics: Check Ohloh organisation page
- 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.
- Lydia Pintscher
- Investigate MLStats and create some useful statistics for 3 mailing lists. Document your findings and work so it can be extended later.
- Lydia Pintscher
Pairs Editor: testing it
- 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.
- Aleix Pol and Marco Calignano
Amarok: Testing from git
- 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.
- 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
- Myriam Schweingruber
Kexi: find UI issues while running under non-KDE desktop
- 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.
Pairs: create a new icon for Pairseditor
- Modify the Pairs game icon to create a new icon for the Pairseditor