GoogleCodeIn/2011/Ideas: Difference between revisions
m s/less that/less than/g |
add Mentoring category |
||
| (51 intermediate revisions by 9 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Mentoring]] | |||
'''Warning: please do not modify this wiki anymore, we are currently transfering it to a spreadsheet!''' | |||
= Guidelines = | = Guidelines = | ||
| Line 184: | Line 188: | ||
Time to complete: 2-4 days maximum depending on the ability and effort of the student. | Time to complete: 2-4 days maximum depending on the ability and effort of the student. | ||
Mentor: Laszlo Papp <[email protected]> | |||
==== Build Mula on Mac OSX ==== | |||
Description: Mula is a Multi Language Dictionary with online, offline dictionary and text-to-speech support design in mind. Unfortunately, I am mostly a Linux and Windows developer, thus cannot test the build procedure on Mac. It would be nice to get Mula built on Mac OSX. It might need some minor fixes. No major issues expected. It would also be a great addition to have the building steps documented. | |||
Expected results: Mula builds fine on Mac and the build steps are documented. | |||
Prerequisites: Having a Mac computer. :) | |||
Time to complete: 1-2 days maximum | |||
Mentor: Laszlo Papp <[email protected]> | |||
==== Make a proper CPack/CMake support for generating Mula binary for Mac installation ==== | |||
Description: Mula already has NSIS CPack/CMake support for generating a binary for Windows installation. deb and rpm support are also available for generating binaries for Meego and Maemo installations. The concept is already available by the existing cmake/cpack system. The task would be to get that concept adopted for Mac and provide a proper package for Mac installation. That would be the missing bit to cover on desktop machines for people learning languages. | |||
Expected results: Mula has a proper CPack/CMake support for Mac installation. Screenshots about the graphical steps and workflow are encouraged at the end. | |||
Prerequisites: Having a Mac computer. :) | |||
Time to complete: 2-3 days depending on the ability and effort of the student. | |||
Mentor: Laszlo Papp <[email protected]> | Mentor: Laszlo Papp <[email protected]> | ||
| Line 196: | Line 222: | ||
Time to complete: 2 days | Time to complete: 2 days | ||
Mentor: Martin Klapetek <[email protected]> | Mentor: Martin Klapetek <[email protected]> | ||
==== Making Join The Game website multilingual ==== | |||
Description: [http://jointhegame.kde.org Join The Game] is KDE's individual sponsorship program, in which people could donate to KDE on a regular basis. The website needs to become multilingual. | |||
Expected results: An integrated translation workflow with KDE's translation system. (A Messages.sh that uses xgettext to extract all messages) | |||
Prerequisites: PHP | |||
Time to complete: 2-4 days | |||
Mentor: Emil Sedgh <[email protected]> | |||
==== Allowing everyone to create sprints on sprints.kde.org ==== | |||
Description: [http://sprints.kde.org Sprints.kde.org] is KDE's internally-used program for organizing sprints. | |||
Currently, it only allows certain people to create and manage sprints. Ideally, all kde contributors should be able to create new sprints or edit them without the need to poke sysadmins. | |||
This also means we will need proper logging system to know who-did-what. | |||
Expected results: An open sprints.kde.org website which allows contributors to create new sprints. | |||
Prerequisites: PHP | |||
Time to complete: 1-3 days | |||
Mentor: Emil Sedgh <[email protected]> | |||
=== medium === | === medium === | ||
| Line 341: | Line 395: | ||
Mentor: Furkan Üzümcü ([email protected]) | Mentor: Furkan Üzümcü ([email protected]) | ||
==== Rekonq: Forget/Delete history entries from the History Panel context menu ==== | |||
Description: Add two actions to the history panel context menu to forget or delete an history entry. In the same way, a third action has to be created to delete all history entries of a day. | |||
Prerequisites: Basic Qt | |||
Time to complete: Three days | |||
Mentor: Yoann Laissus (yoann.laissus at gmail.com) | |||
==== Choqok: Add tools from menu to toolbar ==== | ==== Choqok: Add tools from menu to toolbar ==== | ||
| Line 499: | Line 562: | ||
Mentor: Jens-Michael Hoffmann | Mentor: Jens-Michael Hoffmann | ||
=== | ==== Kst: add Matlab .mat data source using matio ==== | ||
Description: The Kst plotting tool has a plugin-based data source mechanism to be able to add new formats easily. It already supports ASCII, netCDF, images, dirfile and CFitsIO and could be extended fairly easily to read matlab binary files with matio (http://sourceforge.net/projects/matio/files/) | |||
Expected results: ability to load scalars, vectors and matrices from .mat into Kst. | |||
Prerequisites: Knowledge of Qt and C++ | |||
Time to complete: | Time to complete: 3 days | ||
Mentor: | Mentor: Nicolas Brisset <[email protected], Kst mailing list> | ||
==== Kst: date/time support for the ASCII data source ==== | |||
Description: Kst's ASCII data source is already one of the most versatile and efficient, but it currently lacks the ability to read times or dates as formatted strings (e.g. HH:MM:SS.SSS or YYYY/MM/DD). This should be easy to add using Qt's date and time classes and a few more UI options in the ASCII config dialog. | |||
Expected results: ability to read time and dates from formatted ASCII strings into Kst. | |||
Prerequisites: Knowledge of Qt and C++ | |||
Time to complete: 3 days | |||
Mentor: Nicolas Brisset <[email protected], Kst mailing list> | |||
==== Make The Selection Pop-up Menu in Okular Work Perfectly ==== | |||
Description: If somebody clicks the selection pop-up menu, the options do not always come instantly. I need on average 3 clicks to get it worked. | |||
Expected results: Make the pop-up menu working in single click. | |||
Prerequisites: Qt | |||
Time to complete: 2 days | |||
Mentor: Mohammad Mahfuzur Rahman <[email protected]> | |||
==== | ==== Disable the copy option after making an empty selection in okular ==== | ||
Description: If text selection is activated and someone right clicks the mouse button after making an empty selection the copy text option still appears which logically should not. The target of this task is to make it solved. | |||
Expected results: No copy option appears after empty selection. | |||
Prerequisites: Qt | |||
Time to complete: 2 days | |||
Mentor: Mohammad Mahfuzur Rahman <[email protected]> | |||
=== hard === | |||
==== Prevent screen saver from kicking in in Dragon player. ==== | |||
Description: Currently KDEs video player Dragon Player lack a function which prevents the screen saver from kicking in while playing. KDE's energy management can be made aware of a running video player through a few lines of code, documented here (link to blog entry, need to add later since I am out of internet at the moment) | |||
Time to complete: 2 days | |||
Mentor: Harald | |||
Prerequisites: | Prerequisites: basic Qt, willingness to dive thru layers of abstraction. The issue might be in workspace. | ||
==== Add Support for SugarCRM "tasks" to respective resource ==== | |||
Description: The Akonadi data source handle for the SugarCRM web service currently only provides data from the SugarCRM module "contacts" as an Akonadi address book. The module "tasks" contains what KDE PIM calls TODOs, so the task is to map "tasks" entries to a respective Akonadi calendar. | |||
Expected results: SugarCRM resource capable of loading and optional saving of tasks through KOrganizer. | |||
Prerequisites: development packages of kdelibs and kdepimlibs, Knowlegde of C++, ideally also Qt. Local installation of SugarCRM (freely downloadable, PHP based) | |||
Time to complete: 5 days | |||
Mentor: Kevin Krammer <krammer@kde.org> | |||
==== Rekonq: Reopened closed Tab Should Go, As Best As Possible, Where the Original Tab Was ==== | |||
Description: Re-opened closed tab should go, as best as possible, where the original tab was. The student who chooses to do this task should come to #rekonq on IRC for a in-depth discussion. | |||
Prerequisites: Basic Qt | |||
Time to complete: A Week | |||
Mentor: Furkan Üzümcü (furkanuzumcu@gmail.com) | |||
==== Rekonq: Middle Click a Bookmark Folder to Open the Folder in New Tabs ==== | |||
Description: Middle Click a bookmark folder to open the folder in new tabs. (More Info in #rekonq IRC channel ) | |||
Prerequisites: Basic Qt | |||
Time to complete: A Week | |||
Mentor: Furkan Üzümcü ([email protected]) | |||
=== | ==== Choqok: Add support for Twitter photo upload API method ==== | ||
Description: Recently Twitter added ability to attach a photo to tweets, just like StatusNet had before. So the purpose is supporting this feature just like supporting StatusNet feature in Choqok. So, You have an example of whatever you need to do (from GUI to Backend), in Laconica(old name of StatusNet) microblog plugin of Choqok. | |||
And here is the API method ref: https://dev.twitter.com/docs/api/1/post/statuses/update_with_media | |||
Prerequisites: KIO library/ knowing XML or JSON / and basic understanding of HTTP methods | |||
Time to complete: Four days | |||
Mentor: Mehrdad Momeny (mehrdad.momeny{at}gmail.com) | |||
==== Marble: Create a settings dialog for Marble Plugins ==== | |||
Description: This is a medium task that helps you to get introduced to the Marble code base. There are many plugins missing a settings dialog which allows to tweak some of the settings of the plugin. Examples are GpsInfo, Navigation, OpenDesktop Items (Social Plugin), Download Progress Indicator, Sun, Stars. | |||
Have a look at existing settings dialogs for other plugins that you can use as a template for implementation. | |||
Expected results: A settings dialog for a plugin which so far has no such dialog. The dialog should provide some basic means to make useful tweaks to the plugin. | |||
Prerequisites: An installation of Marble master. Basic knowledge of C++ and Qt. | |||
Time to complete: 120 hours | |||
Mentor: rahn@kde.org | |||
==== Marble: Refactor the Measure Tool into a plugin of its own ==== | |||
Description: The current Measure Tool is not a Marble plugin yet. Make it one. | |||
Expected results: The Measure Tool refactored into a plugin. | |||
Prerequisites: An installation of Marble master. Basic knowledge of C++ and Qt. | |||
Time to complete: 120 hours | |||
Mentor: rahn@kde.org | |||
==== Marble: Create a basic "window manager" for float items ==== | |||
Description: Float items in Marble are the info boxes that are displayed on top of the map. They can be enabled and disabled and can be moved freely over the map. So far this also allows to have the float items overlap. However this is not desired: we'd like to have the floatitems snap to positions, so that they maintain a certain distance to other float items (e.g. 10 pixels). In the most basic implementation the float items would just snap to the new position if they overlap initially. | |||
Expected results: A basic implementation of a float item manager provided as a patch. | |||
Prerequisites: An installation of Marble master. Basic knowledge of C++ and Qt. | |||
Time to complete: 120 hours | |||
Mentor: rahn@kde.org | |||
== Documentation == | |||
=== easy === | |||
==== Update part of the Calligra documentation ==== | |||
Description: Calligra project has some outdated documentation. The task consists in updating a part of the online docs | |||
Expected results: have an up-to-date Online Help. | |||
Prertequisites: English language,some basic HTML knowledge. | |||
Time to complete: 48 hours. | |||
Mentors: happy.snizzo@gmail.com | |||
==== Update the Amarok Manual to the latest version (approx. 5x) ==== | |||
Description: The current Amarok Manual refers to version 2.4.0 which is already rather old. The task is to check for each entry if the text and screen shots still apply to the current stable version of Amarok and adapt if necessary. | |||
Expected results: have an up-to-date Manual in Userbase. | |||
Prerequisites: English language, some basic HTML knowledge and basic Mediawiki knowledge. | |||
Time to complete: 48 hours. | |||
==== | Mentors: [email protected], [email protected] | ||
==== Move KWin Scripting documentation to techbase ==== | |||
Description: | Description: The user documentation and tutorial for the KWin Scripting module is currently only in two blog posts written by the author of the module. The documentation should be imported into techbase.kde.org and adapted to the Wiki syntax and integrated into the general structure. | ||
Expected results: | Expected results: have KWin scripting documentation and tutorial in Techbase. | ||
Prerequisites: | Prerequisites: English language, basic Mediawiki knowledge. | ||
Time to complete: 24 | Time to complete: 24 hour | ||
Mentors: mgraesslin@kde.org | |||
==== | ==== Redo KTouch handbook screenshots ==== | ||
Description: | Description: Redo all documentation screenshots for KTouch because they are outdated. Get KTouch source from git or ask the mentor to provide you a tarball. Use KSnapshot and read http://l10n.kde.org/docs/screenshots.php in order to redo the screenshots in png format with the default KDE theme and windows decoration. | ||
Use | |||
Expected results: | Expected results: send the new screenshots to the mentor who will commit them in the repository. | ||
Prerequisites: | Prerequisites: preferably look at KTouch user manual prior to doing the task. | ||
Files location: https://projects.kde.org/projects/kde/kdeedu/ | Files location: https://projects.kde.org/projects/kde/kdeedu/ktouch/repository/revisions/master/show/doc | ||
Time to complete: 24 hour | Time to complete: 24 hour | ||
Mentors: | Mentors: annma@kde.org | ||
==== Redo Kalzium userbase screenshots ==== | |||
Description: Redo all [http://userbase.kde.org/kalzium userbase documentation] screenshots for Kalzium because they are outdated. Use KSnapshot and read http://l10n.kde.org/docs/screenshots.php in order to redo the screenshots in png format with the default KDE theme and windows decoration. The [http://docs.kde.org/development/en/kdeedu/kalzium/index.html handbook] has already updated screenshots. | |||
Expected results: The screenshots on userbase are updated. | |||
Prerequisites: preferably look at Kalzium user manual and userbase prior to doing the task. | |||
Files location: https://projects.kde.org/projects/kde/kdeedu/kalzium/repository/revisions/master/show/doc | |||
Time to complete: 24 hour | |||
Mentors: etienne.[email protected] | |||
==== Update the Kiten handbook and userbase documentation ==== | |||
Description: Both [http://userbase.kde.org/Kiten userbase documentation] and [http://docs.kde.org/development/en/kdeedu/kiten/index.html handbook] are outdated. The task consists on updating the screenshots and features included in the docs to be consistent to the latest version of Kiten. | |||
Expected results: send the updated files to the mentor to commit them. | |||
Expected results: | |||
Prerequisites: In case you don't know Kiten, then install it and use it to see what features it offers you. You will probably need a Japanese font on your system in order to search in the dictionary, or you can copy-paste some words on it. Also look to the [http://l10n.kde.org/docs/screenshots.php KDE documentation screenshots requirements]. | |||
Time to complete: 24 to 48 hours | |||
Mentor: Daniel E. Moctezuma ([email protected]) | |||
==== Fill missing data of oxidation states in Kalzium ==== | |||
Description: Oxidation state support was introduced in Kalzium 4.7. Not all Atoms have currently a value in the [https://projects.kde.org/projects/kde/kdeedu/kalzium/repository/revisions/master/changes/libscience/data/elements.xml elements.xml] file. The task would be to add all missing oxidation states data into the elements.xml. Existing data should also be reviewed. | |||
Use [http://en.wikipedia.org/wiki/Hydrogen wikipedia] to get the data of each atom. | |||
Expected results: Send the finished elements.xml to the mentor. | |||
Prerequisites: You should not be afraid of xml. Chemistry knowledge is not needed. | |||
Files location: https://projects.kde.org/projects/kde/kdeedu/kalzium/repository/revisions/master/changes/libscience/data/elements.xml | |||
Time to complete: 24 hour | |||
Mentors: [email protected] | |||
==== Rewrite part of KDE Accessibility Documentation ==== | |||
Description: Rewrite and update the documentation for KDE Accessibility settings on userbase here: http://userbase.kde.org/System_Settings/Accessibility | |||
Expected results: Detailed documentation of kde accessibility settings. | |||
Prerequisites: English language, some basic HTML knowledge. | |||
Time to complete: a few hours. | |||
Mentor: jpwhiting@kde.org | |||
==== Update KAlgebra handbook ==== | |||
Description: The KAlgebra handbook was written by its original developer some time ago already and has some outdated parts. Make sure everything in there is true and provide more explanation where needed. | |||
Expected results: Good documentation that can be understood by someone unrelated to KAlgebra's development. | |||
Prerequisites: Math vocabulary and writing skills. | |||
Time to complete: 1 week | |||
Mentor: Aleix Pol <aleixpol@kde.org> | |||
Expected results: | ==== Konquest documentation update ==== | ||
Description: Update Konquest documentation (DocBook formatted) for the current code in trunk. Add a screenshot of the game window. | |||
Expected results: Fix inconsistencies in documentation with the current game. Describe new feature (Standing order) of the new version. Add screenshot of the game window. | |||
Prerequisites: English, compiled Konquest version from [http://websvn.kde.org/trunk/KDE/kdegames/konquest/ KDE trunk], basic [http://l10n.kde.org/docs/doc-primer/docbook-reference.html docbook syntax] knowledge. | |||
Time to complete: 48 hrs. | |||
Mentor: Yuri Chornoivan <yurchor@ukr.net> | |||
==== Gluon game logic scripting documentation ==== | |||
Description: Complete the documentation for the Gluon game logic system, which is in progress at the Gluon website: [http://gluon.gamingfreedom.org/documentation/creating-games/creating-game-logic/scripting-reference Scripting Reference]. | |||
Expected results: Completed documentation set for the Gluon scripting API as a single page (as seen in the current state). | |||
Prerequisites: English, light knowledge of C++ and/or javascript | |||
Time to complete: 3 days | |||
Mentor: Dan Leinir Turthra Jensen <admin@leinir.dk> | |||
==== Gluon game logic scripting documentation, option 2 ==== | |||
Description: Build documentation for the Gluon game logic system, using a documentation management system (allow commenting on each article etc.). Optionally the documentation should be automatically generated, though this is of secondary concern. | |||
Expected results: Complete documentation collection for the wrapped Qt classes (list available at [http://gluon.gamingfreedom.org/documentation/creating-games/creating-game-logic/scripting-reference Scripting Reference]). | |||
Prerequisites: English, knowledge of web CMSes, light knowledge of C++ and/or javascript | |||
Time to complete: 1 week | |||
Mentor: Dan Leinir Turthra Jensen <admin@leinir.dk> | |||
==== Screenshots for Gluon documentation ==== | |||
Description: The current documentation for Gluon Creator has a large amount of text and very few pictures. This task aims to fix this issue by letting you go crazy and produce screenshots of every feature and workflow you can find. | |||
Expected results: Screenshots for the documentation on the website at [http://gluon.gamingfreedom.org/documentation the Gluon website's documentation section] | |||
Prerequisites: None per se | |||
Time to complete: 3 days | |||
Mentor: Dan Leinir Turthra Jensen <[email protected]> | |||
==== Expand Plasma Active FAQ ==== | |||
Description: We have created a [[Plasma/Active/Info/FAQ|Beginner's FAQ]] for [http://www.plasma-active.org Plasma Active] which lists answers to some questions that novice users of Plasma Active often encounter. | |||
The first part of this task is to expand this list with questions that have come up in the forums, on IRC, on the mailing list or which you ask yourself while using Plasma Active. After adding the questions, the second part is to ask the Plasma Active team to | |||
Expected results: At least ten new questions and answers in the FAQ. | |||
Prerequisites: None. Access to a device running Plasma Active ( see [[Plasma/Active/Devices|Device List]] ) or a virtual machine running Plasma Active is necessary if you want to add your own questions instead of those asked by others. | |||
Time to complete: 3 Days | |||
Mentor: Thomas Pfeiffer ( colomar@autistici.org ) | |||
=== medium === | |||
==== Import KWin Scripting API documentation to techbase ==== | |||
Description: The JavaScript API documentation for KWin Scripting module is currently only available through an application in the KWin source directory which generates an HTML page. The documentation should be made available in techbase.kde.org and follow the structure of JavaScript API documentation for Plasma. | |||
Expected results: KWin Scripting API documentation in Techbase | |||
Prerequisites: Being able to compile source code to generate the API documentation and MediaWiki knowledge | |||
Time to complete: 48 hours | |||
Mentor: mgraesslin@kde.org | |||
==== Prepare illustrated introduction to integrating Kontact with Google services (to be hosted on UserBase) ==== | |||
Expectation: A set of screen-shots and/or short screen-casts showing how to set up Google integration. They should include setting up forwarded mail from GMail, using GMail IMAP resources, integrating contact information, and integrating Google Calendar with KOrganizer calendar. | |||
Ideally there should be scope for language-independence. This might take the form of animated gifs with a text description suitable for translation, or, preferably, video with the possibility of soundtrack overlays. | |||
Pre-requisites: A working Kontact of the latest stable version, to include a calendar suitable for testing with Google Calendar. A GMail account. Installed software for preparation of animated gifs or full screen-casts. Basic wiki markup skills. An IRC client installed. | |||
Time to complete: 168 hours | |||
==== User documentation for setup and use of Kmail ==== | |||
Description: Kmail is being adopted by more users and should have simple to understand, easy to follow setup and use instructions for people wanting to use it with existing webmail or office accounts. | |||
Expected results: Kmail User documentation in Userbase | |||
Prerequisites: Being able to give clear instructions and proofread. | |||
Time to complete: 24 hours | |||
Mentor: broeksema@kde.org | |||
==== Describe how to create a custom voice navigation speaker for Marble ==== | |||
Description: Marble has a route guidance mode that can make use of speakers (pre-recorded sound files) to indicate directions. There are some existing ones to download at http://edu.kde.org/marble/speakers.php and instructions to install them at http://userbase.kde.org/Marble/CustomSpeakers#Voice_Installation and also instructions how to record a custom voice at http://community.kde.org/Marble/VoiceOfMarble. Your task is to combine these information into a comprehensible guide that describes how to record and install a custom voice such that in the end one has Marble speak your own voice in guidance mode. | |||
Expected results: A finished section http://userbase.kde.org/Marble/CustomSpeakers#Creating_Custom_Voices that users can easily follow. | |||
Prerequisites: An installation of Marble 1.2 (KDE 4.7). Can be compiled from source code as well. An installation of Marble on the N900 would be nice, but is not absolutely necessary. | |||
Time to complete: 24 hours | |||
Mentor: [email protected] | |||
=== | ==== Document the Kate Snippets plugin ==== | ||
Description: Many of Kate's plugins are currently undocumented, so users are potentially missing out on some awesome features because they don't know how to use them. [http://milianw.de/blog/snippets-in-kdevelop-kate Kate Snippets] allow users to insert chunks of text in their files to save them some typing. Your task is to explain to users how this plugin works. | |||
Expected results: A section of the [http://docs.kde.org/stable/en/kdebase-runtime/kate/plugins.html plugins chapter] describing the Kate Snippets plugin. It should include a basic introduction that explains how to use the plugin, a list of the menu options provided by the plugin, and a description of all the elements in the plugin's user interface. The [http://docs.kde.org/stable/en/kdebase-runtime/kate/kate-application-plugin-filetemplate.html File Templates plugin documentation] is an excellent example of complete plugin documentation. You don't have to know DocBook, the XML language KDE documentation is written in; just use plain text or your favorite word processor. | |||
Prerequisites: A good command of the English language, a working Kate installation and the ability and desire to try things out, see how they work, and explain it to others. | |||
Time to complete: 1-2 days | |||
Time to complete: 2 | |||
Mentor: [mailto:[email protected] T.C. Hollingsworth <[email protected]>] | Mentor: [mailto:[email protected] T.C. Hollingsworth <[email protected]>] | ||
== | ==== KAlgebra's console userbase tutorial ==== | ||
Description: Provide a document explaining KAlgebra's console features to be put on the userbase's wiki. | |||
Expected results: A good review of the KAlgebra language and its features in a console. | |||
Prerequisites: Math and writing skills. Functional Programming knowledge will help for sure. | |||
Time to complete: 3 days | |||
Mentor: Aleix Pol <[email protected]> | |||
==== | ==== Plasma QtComponents documentation ==== | ||
Description: | Description: document the api of the new Plasma QtComponents in the code, with a doxygen style notation (even tough doxygen doesn't support qml, so it could have to be copied over manyally to techbase). | ||
Expected results: At least 10-15 widgets with a completely documented api comprised with use cases. | |||
Prerequisites: a basic level of Qt/QML knowledge. | |||
Time to complete: 5 days | |||
Mentor: Marco Martin <mart@kde.org> | |||
==== Gluon Video Tutorial ==== | |||
Description: Record and mix one of the pre-scripted tutorials on the [http://community.kde.org/Gluon/Video-tutorial-scripts the Video Tutorial Scripts] page. | |||
Expected results: One completed video tutorial, uploaded to vimeo under a suitable CC license | |||
Prerequisites: Good vocal English skills, basic KDEnlive skills | |||
Time to complete: 3 days for first video (to create project and style), 2 for subsequent | |||
Mentor: Dan Leinir Turthra Jensen <admin@leinir.dk> | |||
==== Kst: refresh Kst documentation for Kst 2.x ==== | |||
Description: Take the existing Kst 1.x documentation and refresh it to Kst 2.x | |||
Expected results: Choice how to handle documentation (Userbase ?) and a first clear structure with tags towards what needs to be updated, deleted or added. | |||
Prerequisites: Good English skills | |||
Time to complete: 4 days, 3 if already familiar with Kst | |||
Mentor: Nicolas Brisset <kst@kde.org, Kst mailing list> | |||
=== hard === | |||
==== Document a Kate plugin for developers ==== | |||
Description: Many of Kate's plugins are currently undocumented, so users are potentially missing out on some awesome features because they don't know how to use them. Among these plugins are ones that interface with some powerful tools used by developers to make programming easier. If you're familar with things like debuggers, compiling programs, or SQL, and want to learn how to more easily do these things and help others learn too, this is the task for you. Plugins that need documenting include the [http://kate-editor.org/2011/06/21/kate-plugin-updates-part-1/ build plugin], [http://kate-editor.org/2010/10/06/introducing-kate-gdb-plugin/ GDB plugin], and the [http://kate-editor.org/2010/07/29/katesql-a-new-plugin-for-kate/ SQL plugin]. Your task is to pick one, and explain how it works. | |||
Expected results: A section of the [http://docs.kde.org/stable/en/kdebase-runtime/kate/plugins.html plugins chapter] describing the plugin you choose. It should include a basic introduction that explains how to use the plugin, a list of the menu options provided by the plugin, and a description of all the elements in the plugin's user interface. The [http://docs.kde.org/stable/en/kdebase-runtime/kate/kate-application-plugin-filetemplate.html File Templates plugin documentation] is an excellent example of complete plugin documentation. You don't have to know DocBook, the XML language KDE documentation is written in; just use plain text or your favorite word processor. | |||
Prerequisites: A good command of the English language, a working Kate installation, the ability and desire to try things out, see how they work, and explain it to others, and some knowledge of the tools involved in the plugin. (e.g. you should have some knowledge of how databases and SQL work if you're going to work on the SQL plugin.) If you're not familiar with these tools, you might find the Kate snippets plugin easier. | |||
Time to complete: 2-4 days | |||
Mentor: [mailto:[email protected] T.C. Hollingsworth <tchollingsworth@gmail.com>] | |||
==== A Documentation on Okular document and paging system ==== | |||
Description: In okular, the full document open for reading is called document and every pages are called page. All the text in a page is called a textpage. So, basically a document consists of pages and each page consist one textpage. This is a very basic concept of okular which every developer need to know if they want to start development with okular. | |||
There is a good document about how to implement a generator at: http://api.kde.org/4.7-api/kdegraphics-apidocs/okular/html/okular_generators.html . It might be a reference example on how to write a document for okular. | |||
The Student should study on some part of okular codebase and made a good documentation on how okular document and page system works. You are goint to need to see the document, page and textpage files(.h and .cpp) in detail. | |||
Expected results: A good documentation to be included in kdegraphics api of okular. | |||
Prerequisites: Good English skills, Some knowledge of okular should be a plus. | |||
Time to complete: 3-4 days | |||
Mentor: Mohammad Mahfuzur Rahman <[email protected]> | |||
== Outreach == | |||
==== | === easy === | ||
==== Update the feedlist in Akregator to a usefull set of KDE/Linux related feeds ==== | |||
Description: Akregator contains a short list of KDE related feeds which are shown on first start. This list is partially outdated. Create a suggestion for an updated list, may be add some more KDE/Linux related feeds. Also check, if it is possible to have a different list depending on the users language. | |||
Expected results: An updated list of KDE/Linux-related feeds integrated in to Akregator | |||
Time to complete: | Time to complete: 24 hours | ||
Mentor: | Mentor: Sune | ||
=== | ==== Update KDEs bookmark list to a useful set of KDE/Linux related feeds ==== | ||
Description: KDE contains a short list of KDE related bookmarks which are shown in Konqueror and Rekonqon first. Update them, look for useful KDE/Linux related links. If necessary, ask in KDE forum for useful suggestions. Also check, if it is possible to have a different list depending on the users language. | |||
An updated list of KDE/Linux-related bookmarks integrated into KDE. | |||
Time to complete: 24 hours | |||
Mentor: Sune | |||
==== Create Demo data for KDE's Addressbook application ==== | |||
Description: When demonstrating KDE PIM software at fairs or exhibitions, we usually lack data for our applications to show their features. This task is about creating contact data for fake personas, i.e. inventing a name and life of a person and creating addressbooks that such a person would likely have. | |||
Expected results: descriptions of three personas and at least one addressbook per persona. Contact data should contain at least names, addresses and email addresses. | |||
Prerequisites: any version of KAddressbook, preferably a current one. | |||
Time to complete: 2 days | |||
Mentor: Kevin Krammer <[email protected]> | |||
==== | ==== Create Demo data for KDE's Calendaring application ==== | ||
Description: | Description: When demonstrating KDE PIM software at fairs or exhibitions, we usually lack data for our applications to show their features. This task is about creating calendar data for fake personas, i.e. inventing a name and life of a person and creating calendars that such a person would likely have. | ||
Expected results: descriptions of three personas and at least one calendar per persona. Calendar data should contain events, normal and recurring ones, todos in different state of completion. | |||
Prerequisites: any version of KOrganizer, preferably a current one. | |||
Time to complete: 2 days | |||
Mentor: Sérgio Martins <iamsergio@gmail.com> | |||
==== Create Demo data for KDE's mail application ==== | |||
Description: When demonstrating KDE PIM software at fairs or exhibitions, we usually lack data for our applications to show their features. This task is about creating mail data for fake personas, i.e. inventing a name and life of a person and creating a mail setup that such a person would likely have. | |||
Expected results: | Expected results: descriptions of three personas and some email data for each one. You can subscribe to mailinglists and/or exchange emails between your personas (and/or between them and yourself). | ||
Prerequisites: | Prerequisites: any version of KMail, preferably a current one and either some accounts at a free mail provider or other means to send and receive mails with different email addresses. | ||
Time to complete: | Time to complete: 3 days | ||
Mentor: | Mentor: Kevin Krammer <[email protected]> | ||
==== | ==== Create Demo data for KDE's groupware application ==== | ||
Description: | Description: When demonstrating KDE PIM software at fairs or exhibitions, we usually lack data for our applications to show their features. This task is about creating data to show integration between PIM components. | ||
Expected results: using personas and their data to create more advanced data such as events with participants selected from the addressbook, sent invitations to them and receive their answers. | |||
Prerequisites: any version of Kontact, preferably a current one and either some accounts at a free mail provider or other means to send and receive mails with different email addresses. | |||
Time to complete: 2 days | |||
Mentor: Kevin Krammer <krammer@kde.org> | |||
==== Commit Digest: review 100 commits ==== | |||
The | Description: Commit-Digest is a weekly review of the KDE developer activity. The task is to review 100 commits and decide if they should be included in the weekly digest. You can find the guidelines here: http://community.kde.org/Commit_Digest/Guidelines | ||
Expected results: | Expected results: 100 correctly reviewed commits in the Enzyme system http://enzyme.commit-digest.org/ | ||
Prerequisites: | Prerequisites: an account in Enzyme, ask for it in advance. | ||
Time to complete: | Time to complete: 2 days | ||
Mentor: | Mentor: Marta Rybczynska <[email protected]> | ||
==== | ==== Commit Digest: classify 50 commits ==== | ||
Description: KDE | Description: Commit-Digest is a weekly review of the KDE developer activity. The task is to classify 50 reviewed commits into one of pre-defined categories. You can find the guidelines here: http://community.kde.org/Commit_Digest/Guidelines | ||
Expected results: 50 correctly classified commits in the Enzyme system http://enzyme.commit-digest.org/ | |||
Prerequisites: an account in Enzyme, ask for it in advance. | |||
Time to complete: 2 days | |||
Mentor: Marta Rybczynska <[email protected]> | |||
==== Kst: set-up dedicated forum on forum.kde.org ==== | |||
Description: the Kst plotting tool currently offers only a developer-oriented mailing list and there have been requests to have a specific forum on forum.kde.org. It could even be a joint plotting forum with areas for kig, Kst, labplot, etc... | |||
Expected results: operational Kst forum on forum.kde.org | |||
Prerequisites: an account on forum.kde.org and contacts to the forum admins. | |||
Time to complete: 2 days | |||
Mentor: Nicolas Brisset <kst@kde.org, Kst mailing list> | |||
=== medium === | |||
==== Marble: Create a nice blog entry about your favorite Marble feature ==== | |||
Description: | |||
Marble has lots of nice features. Have a look at it and create a nice blog entry that goes into details describing your favorite feature. The blog entry should have at least 3 screenshots, should have about 500+ words and should encourage people to use Marble. You can write it either in your own language or in English. For a successful completion you need to have your blog appear on planet.kde.org and you need to publish your blog there. | |||
Suggested topics: Recent features that have been added (OSM Vector support, Marble Touch, Satellite View, etc.) | |||
Expected results: A blog entry about your favorite Marble feature that appears on planet.kde.org. | |||
Prerequisites: Knowledge about how to write a blog entry / Knowledge about Marble | |||
Time to complete: 72h | |||
Mentor: rahn@kde.org | |||
==== Video ad for KDE - Emotions ==== | |||
Description: | |||
Use all your creativity to create an innovating short film promoting KDE. We are looking for an advertisement with new ideas that communicates the spirit behind KDE. | |||
Must show KDE on different platforms. Creativity is very important. | |||
Your video must convey a KDE feeling and obey to KDE quality standards. | |||
Your video must | |||
Quality has to be at least 720p, real action, animation or stop-motion. | Quality has to be at least 720p, real action, animation or stop-motion. | ||
No screen-cast only video and no 3D animation video are allowed. | No screen-cast, only video and no 3D animation video are allowed. | ||
Every video, sound and image used must be GPL 3.0 or Creative Commons BY-SA. | Every video, sound and image used must be GPL 3.0 or Creative Commons BY-SA. | ||
| Line 1,132: | Line 1,154: | ||
Mentor: Claudio Desideri (happy dot snizzo at gmail dot com) | Mentor: Claudio Desideri (happy dot snizzo at gmail dot com) | ||
==== Video ad for KDE - | ==== Video ad for KDE - KDE Everywhere ==== | ||
Description: | Description: | ||
| Line 1,158: | Line 1,180: | ||
Time to complete: 168h | Time to complete: 168h | ||
Mentor: | Mentor: Jorge Salgueiro (jorge dot salgueiro at gmail dot com) | ||
==== | ==== Research: Enriching KDE News content ==== | ||
Description: | Description: KDE has a news site at dot.kde.org known as "The Dot". The Dot has a few regular features such as weekly reports of development activities and release announcements. Even in these situations, Dot editors depend on other people submitting stories rather than proactively seeking out KDE news of interest. | ||
This project involves: | |||
* In general, enabling KDE Dot editors to proactively recruit stories of interest to the KDE Community | |||
* Identifying KDE newsmakers by researching blogs and other on-line channels | |||
* Contacting KDE newsmakers and influencers for general story ideas--topics, people, projects, | |||
* Making recommendations for stories, including the above and timing or frequency (for example, a story about a main KDE project every week; a profile on a key contributor monthly). | |||
This project is intended to generate story ideas and methods for completing them; it may also involve writing story drafts if a subject seems to warrant that. | |||
Expected results: A written list of at least ten subjects and contacts that would result in Dot stories on a continuing basis. | |||
Time to complete: 40h | |||
Mentor: Carl Symons (carlsymons@gmail.com) | |||
=== hard === | |||
==== Create a nice suggestion for a Wikpedia article for Marble in your own native language ==== | |||
Description: | |||
Marble is covered in Wikipedia in several languages. See | |||
http://de.wikipedia.org/wiki/Marble_%28Computerprogramm%29 | |||
http://en.wikipedia.org/wiki/Marble_%28software%29 | |||
http://it.wikipedia.org/wiki/Marble_%28KDE%29 | |||
However taking Marble's significance into account and comparing it to other Wikipedia articles like: | |||
http://en.wikipedia.org/wiki/Google_Earth | |||
http://en.wikipedia.org/wiki/NASA_World_Wind | |||
.. the Marble Wikipedia article has room for lots of improvements. In fact Marble does already provide much of the feature set provided by Google Earth and NASA World Wind, see the feature matrix here: | |||
http://en.wikipedia.org/wiki/Virtual_Globe | |||
Create a suggestion for a Marble Wikipedia article in your own language. This might be an article in a language that is not yet covered or an article that has major improvements over the current version in your language. The article should adhere to Wikipedia principles. | |||
Expected results: A high quality wikipedia article that is in line with Wikipedia rules and principles. | |||
Prerequisites: A good understanding of Technical Writing and knowledge about Marble. | |||
Time to complete: 120h | |||
Mentor: rahn@kde.org | |||
==== Video ad for KDE - Join The Game ==== | |||
Description: | |||
Join the Game - create a video ad for the "Join The Game" campaign to reach new supporting members for KDE e.V. (the non-profit organisation that supports the KDE community). | |||
The video should promote the idea and look and feel of the Join the Game campagne, see http://jointhegame.kde.org/ for more. The video should be according to KDE quality standards. | |||
Quality has to be at least 720p, real action, animation or stop-motion. No screen-cast only video and no 3D animation video are allowed. | |||
Every video, sound and image used must be GPL 3.0 or Creative Commons BY-SA. The video license will be GPL 3.0 or Creative commons BY-SA. The work will have a text file with the following information: - License - Authors - Actors - Technical staff - Score | |||
KDE | Expected results: An ad (less than 2 minutes) promoting KDE. | ||
Prerequisites: Script. | |||
Time to complete: 168h | |||
Mentors: Claudio Desideri (happy dot snizzo at gmail dot com) and Claudia Rauch, rauch@kde.org | |||
==== Video ad for KDE - Experience Freedom ==== | |||
Description: | |||
Use all your creativity to create an innovating short film promoting KDE. We are looking for an advertise with new ideas that communicate the spirit behind KDE. | |||
Must verse KDE in different platforms. Creativity is very important. | |||
Your video must have a KDE feeling (lettering, imagery, etc.). Must be according to KDE quality standards. | |||
Quality has to be at least 720p, real action, animation or stop-motion. | |||
No screen-cast only video and no 3D animation video are allowed. | |||
Every video, sound and image used must be GPL 3.0 or Creative Commons BY-SA. | |||
The video license will be GPL 3.0 or Creative commons BY-SA. The work will have a text file with the following information: | |||
- License | |||
- Authors | |||
- Actors | |||
- Technical staff | |||
- Score | |||
Expected results: An ad (less than 2 minutes) promoting KDE. | |||
Prerequisites: Script. | |||
Time to complete: 168h | |||
Mentor: Claudio Desideri (happy dot snizzo at gmail dot com) | |||
==== Video ad for KDE - Love ==== | |||
Description: | |||
Use all your creativity to create an innovating short film promoting KDE. We are looking for an advertise with new ideas that communicate the spirit behind KDE. | |||
Must verse KDE in different platforms. Creativity is very important. | |||
Your video must have a KDE feeling (lettering, imagery, etc.). Must be according to KDE quality standards. | |||
Quality has to be at least 720p, real action, animation or stop-motion. | |||
No screen-cast only video and no 3D animation video are allowed. | |||
Every video, sound and image used must be GPL 3.0 or Creative Commons BY-SA. | |||
The video license will be GPL 3.0 or Creative commons BY-SA. The work will have a text file with the following information: | |||
- License | |||
- Authors | |||
- Actors | |||
- Technical staff | |||
- Score | |||
Expected results: An ad (less than 2 minutes) promoting KDE. | |||
Prerequisites: Script. | |||
Time to complete: 168h | |||
Mentor: Claudio Desideri (happy dot snizzo at gmail dot com) | |||
==== Video ad for KDE - Plasma Active ==== | |||
Description: | |||
Use all your creativity to create an innovating short film promoting KDE. We are looking for an advertise with new ideas that communicate the spirit behind KDE. | |||
Must verse Plasma Active. Creativity is very important. | |||
Your video must have a Kde feeling (lettering, imagery, etc.). Must be according to Kde quality standards. | |||
Quality has to be at least 720p, real action, animation or stop-motion. | |||
No screen-cast only video and no 3D animation video are allowed. | |||
Every video, sound and image used must be GPL 3.0 or Creative Commons BY-SA. | |||
The video license will be GPL 3.0 or Creative commons BY-SA. The work will have a text file with the following information: | |||
- License | |||
- Authors | |||
- Actors | |||
- Technical staff | |||
- Score | |||
Expected results: An ad (less than 2 minutes) promoting KDE Plasma Active. | |||
Prerequisites: Script. | |||
Time to complete: 168h | |||
Mentor: Jorge Salgueiro (jorge dot salgueiro at gmail dot com) | |||
==== Video ad for KDE - Coming together ==== | |||
Description: | |||
Use all your creativity to create an innovating short film promoting KDE. We are looking for an advertise with new ideas that communicate the spirit behind KDE. | |||
Must verse KDE Community. Creativity is very important. | |||
Your video must have a KDE feeling (lettering, imagery, etc.). Must be according to KDE quality standards. | |||
Quality has to be at least 720p, real action, animation or stop-motion. | |||
No screen-cast only video and no 3D animation video are allowed. | |||
Every video, sound and image used must be GPL 3.0 or Creative Commons BY-SA. | |||
The video license will be GPL 3.0 or Creative commons BY-SA. The work will have a text file with the following information: | |||
- License | |||
- Authors | |||
- Actors | |||
- Technical staff | |||
- Score | |||
Expected results: An ad (less than 2 minutes) promoting KDE Community. | |||
Prerequisites: Script. | |||
Time to complete: 168h | |||
Mentor: Jorge Salgueiro (jorge dot salgueiro at gmail dot com) | |||
==== Research: Understanding KDE Users (Individuals) ==== | |||
Description: KDE users number in the millions. However, aside from general information, not much is known about them. With better intelligence, the KDE community could be more effective at reaching and serving KDE users and potential users. | |||
KDE outreach efforts are stymied by the lack of direct contact with users. Typically, KDE technology is included seamlessly in downstream Linux distributions such as Kubuntu, openSUSE and many more. It is also available as an option for most Linux and similar operating systems. | |||
This project involves: | |||
* planning for the project | |||
* understanding and documenting pertinent background information, | |||
* the possibility of working with KDE development teams, | |||
* Creating research goals (what information should be gathered, how will it be used, what would be helpful to know), | |||
* exploring and analyzing research methods, and | |||
* determining the effectiveness of various research methods. | |||
This project is intended to produce well-reasoned recommendations; it does not involve doing the actual research. | |||
Expected results: | Expected results: At least five suggestions of methods for gathering pertinent, actionable information, including pros and cons, rationale, recommendations. | ||
Time to complete: 120h | |||
Mentor: Carl Symons (carl dot symons at gmail dot com) | |||
==== Research: Understanding KDE Users (Organizations) ==== | |||
Description: KDE technology is used within companies and other organizations. In some cases, individual users have the ability to choose their computer operating environments; in others, this is an organizational decision. Beyond this general information, not much is known about the use of KDE in organizational settings. With better intelligence, the KDE community could be more effective at working with organizations and the users in them. In addition, developing closer relationships with organizations could be useful for gaining financial support for KDE operations. | |||
KDE outreach efforts are stymied by the lack of direct contact with users. Typically, KDE technology is included seamlessly in downstream Linux distributions such as Kubuntu, openSUSE and many more. It is also available as an option for most Linux and similar operating systems. Currently, there is no reliable way to know about KDE use in organizations, even if KDE is a key part of a widespread Linux deployment. | |||
This project involves: | |||
* planning for the project | |||
* understanding and documenting pertinent background information, | |||
* the possibility of working with KDE development teams, | |||
* creating research goals (what information should be gathered and how will it be used), | |||
* exploring and analyzing research methods, and | |||
* determining the effectiveness of various research methods. | |||
This project is intended to produce well-reasoned recommendations; it does not involve doing the actual research. | |||
Expected results: | Expected results: At least five suggestions of methods for gathering pertinent, actionable information, including pros and cons, rationale, recommendations. | ||
Time to complete: 120h | |||
Mentor: Carl Symons (carl dot symons at gmail dot com) | |||
== Quality Assurance == | |||
==== | === easy === | ||
==== Bug triaging: searching for duplicates (approx. 20x) ==== | |||
Description: Many KDE bug reports need to be triaged (checked) before they can be forwarded to the developers. The task consists in selecting individual KDE projects and check the database for duplicate entries. | |||
Expected results: have a better triaged bug database to facilitate the developer's work. | |||
Prerequisites: Having good analytical skills, having read and understood the triaging Guide: http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging | |||
Time to complete:48 hours. | |||
Mentor: [email protected], kde-bugsquad, coordination in #kde-bugs | |||
==== | ==== Gluon: Unit tests for Gluon Audio ==== | ||
Description: | Description: Gluon, and in this special case Gluon Audio, needs unit tests for quality assurance. It will be very important because of a potential backend replacement, but at least extension from a project called "alure" to QtOpenAL, For the smooth transient, it will aid a lot if we can always test the previously working functionalities for regressions. | ||
Prerequisites: Basic Qt, Audio, QtTest | |||
Time to complete: about 2-5 days depending on the ability and effort of the student. | |||
Mentor: Laszlo Papp <[email protected]> | |||
==== KMail: check if old KMail 1 bugs/wishes are valid for KMail 2 (approx. 20x for bugs or 40x for wishes) ==== | |||
Description: There are lots of open [https://bugs.kde.org/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&columnlist=bug_severity%2Cpriority%2Cassigned_to%2Cbug_status%2Cresolution%2Cop_sys%2Cvotes%2Cshort_desc&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=bug_severity&field-1-1-0=bug_status&field-1-2-0=product&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=substring&product=kmail&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type-1-2-0=anyexact&type0-0-0=noop&value-1-0-0=critical%2Cgrave%2Cmajor%2Ccrash%2Cnormal%2Cminor&value-1-1-0=UNCONFIRMED%2CNEW%2CASSIGNED%2CREOPENED&value-1-2-0=kmail&value0-0-0=&votes=&order=bugs.votes%20desc%2Cbugs.bug_id&query_based_on= bugreports] and [https://bugs.kde.org/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_severity=wishlist&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&columnlist=bug_severity%2Cpriority%2Cassigned_to%2Cbug_status%2Cresolution%2Cop_sys%2Cvotes%2Cshort_desc&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=bug_severity&field-1-1-0=bug_status&field-1-2-0=product&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=substring&product=kmail&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type-1-2-0=anyexact&type0-0-0=noop&value-1-0-0=wishlist&value-1-1-0=UNCONFIRMED%2CNEW%2CASSIGNED%2CREOPENED&value-1-2-0=kmail&value0-0-0=&votes=&order=bugs.votes%2Cbugs.bug_id&query_based_on= wishes] for KMail 1 which is out of maintenance. These bugreports and wishes have to be checked. If they are still valid for KMail 2, the "product" field in bugzilla should be changed to KMail 2. Bugs and wishes that are no longer valid (for example because they have been implemented/fixed) should be closed. | |||
Note: coordinate with the KMail developers to get write access to the KMail 1 bugreports. | |||
Prerequisites: A system with latest KDE and KMail installed. Having used KMail before is an advantage. | |||
Time to complete: | Time to complete: 1 day | ||
Mentor: | Mentor: | ||
=== medium === | === medium === | ||
==== Amarok: | ==== Amarok: Unit tests for Amazon store ==== | ||
Description: | Description: The Amazon store needs unit tests for quality assurance. Especially the parser and meta object creation. Maybe also the collection. We already have unit tests for other areas as inspiration. | ||
Prerequisites: Basic Qt, QtTest | |||
Time to complete: about a day if you already know QtTest, maybe two if you don't | |||
Mentor: Sven Krohlas <sven@getamarok.com> | |||
==== Unit tests for KDE-Telepathy Contact List ==== | |||
Description: Contact List should have some unit tests for QA. | |||
Description: | |||
Prerequisites: Qt, QtTest | |||
Time to complete: probably 3-5 days | |||
Mentor: Martin Klapetek <martin.klapetek@gmail.com> | |||
Mentor: | |||
=== hard === | === hard === | ||
==== Write some backend QA tests ==== | |||
Description: Its easy to test libphonon. Write a dummy backend and throw it all into some unit tests. Its a lot harder to test pgst or pvlc since they aren't exactly suitably designed for unit testing. We would like to have a basic checklist of test situations to run through before a release to make sure all the kinks are found and regressions don't occur. Examples: | |||
* Open dragon, play a .wav, close dragon. | |||
* Open dragon, play a .wav, play the same .wav again, close dragon. | |||
* Open dragon, queue up three .avis, play them, close dragon. | |||
* Play a DVD and navigate the menus to enable subtitles | |||
Sounds very tedious to try and cover all the bases, but doing so can help teach a *lot* about multimedia software development. | |||
Expected results: Have a nice list of things to test that you can't just stuff in a bunch of unit tests. At least 5 or so scripts produced per student, with multiple students creating different lists independently. | |||
Prerequisites: Patience, a careful eye, and a willingness to learn the basics of the libphonon API. Maybe some familiarity with basic combinatorics. | |||
Time to complete: 2 days | |||
Mentor: Trever Fischer <[email protected]>, coordination in #kde-multimedia with the other phonon developers, apachelogger and bambee. | |||
== Research == | |||
== | |||
=== easy === | === easy === | ||
==== | ==== KDE3 Documentation Update Listing ==== | ||
Description: | Description: Create a list of pages on KDE's Techbase that are describing KDE3 | ||
Expected results: | Expected results: A list of all the pages on Techbase with categorization of topics that are covered. If the page is deemed to be trivial to update to KDE4 then some attempt should be made to facilitate that. | ||
Prerequisites: | Prerequisites: Knowledge of Wiki Use, Communication. | ||
Time to complete: | Time to complete: 48 hours | ||
Mentor: | Mentor: skreech2 at gmail dot come | ||
==== | ==== KDE Multimedia Census ==== | ||
Description: | Description: With the recent(ish) rejuvenation of the KDE-MM community, its probably a good time to step back and have a look at what exactly our community is made of. Some simple statistics would be needed, in order of importance: | ||
* What projects consider themselves to be part of kde-mm | |||
* The number of developers on each project, to identify projects in need of help | |||
* Some background history on some of the developers, so the community can get to know everyone | |||
* Feedback and suggestions on what "kde multimedia" really means | |||
* Anything else the minion comes up with ;P | |||
Expected results: Answers to the above questions, silly. At the very least, a better list of questions so that we can perform the census ourselves. | |||
Prerequisites: People skills, basic understanding of simple statistics. | |||
Time to complete: 3 days | |||
Mentor: Trever Fischer <tdfischer@fedoraproject.org>, coordination in #kde-multimedia and the [email protected] list. | |||
==== Research Akademy 2012 visitor information ==== | |||
Description: The annual KDE community conference Akademy takes place in a different city and country every year. To make it easier for the Akademy attendees to find their way around the city where Akademy 2012 will take place, we will provide various tips and information on the Akademy website. | |||
Your task would be to do online research and edit the following details, so that we can publish them on the Akademy 2012 website: | |||
* description of transport options and travel recommendation for the Akademy 2012 city | |||
* a list of restaurants and cafes with addresses and price range, including options for vegetarians and vegans | |||
* a list of recommended sights in the Akademy 2012 city | |||
You can find examples for past events here: | |||
* http://akademy2010.kde.org/travel | |||
* http://wiki.desktopsummit.org/Getting_around | |||
* http://akademy2010.kde.org/goingout | |||
* http://wiki.desktopsummit.org/Food#Restaurants_and_cafes_close_to_conference_venue | |||
Expected results: see description :) | |||
Time to complete: 10-15 hours | |||
Mentor: Claudia Rauch, rauch@kde.org | |||
=== medium === | |||
==== Amarok: Likeback statistics and report ==== | |||
Description: Amarok uses the Likeback feedback gathering system in beta releases and git builds. 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. | |||
Time to complete: 3 days. | |||
Mentor: Teo Mrnjavac <teo@kde.org> | |||
==== Accumulate Transparency issues in okular ==== | |||
Description: There are some problems with transparency in okular. A problem was on selection of text in odt files. A very basic solution was made, which is better than prior but not satisfactory at all. It would be nice to know the transparency issues, as many as possible to collect. The student is needed to give a report in which cases this kind of transparency problems arises. | |||
Expected results: A thorough report, maybe in PDF or doc format. | |||
Prerequisites: basic writing skills and patience. | |||
Time to complete: 2-3 days. | |||
Mentor: Mohammad Mahfuzur Rahman <[email protected]> | |||
== | ==== Pairs Touch-Friendly Interface ==== | ||
Description: Right now Pairs is working great on the desktop but we want to look further and make it work on touch devices. We need an interface written in QtQuick that doesn't make use of the menus, toolbars and status bar and puts everything in a canvas, in a pretty way. Also it shouldn't have the new game dialog, this should be on the canvas as well. | |||
Expected results: Make it possible to have an interface to be ported to Pairs, that can be used easily on a touch device, like a tablet. | |||
Prerequisites: QtQuick, UI Design | |||
Time to complete: 1 week | |||
Mentor: Aleix Pol <[email protected]> | |||
=== hard === | |||
==== New KAlgebra Mobile tool ==== | |||
Description: If you try the KAlgebra Mobile you'll see the feature set is smaller than the Desktop's version. The possibility to create new tools opens new possibilities that we still need to explore. | |||
Expected results: Provide a QtQuick mockup of the tool you'd like to have in your calculator when you're at class or while doing framework. It doesn't need to work, but if it doesn't it needs to specify what should every bit of the UI do. | |||
Prerequisites: QtQuick knowledge, ideas about applied mathematics | |||
Time to complete: 1 week | |||
Mentor: Aleix Pol <[email protected]> | |||
==== KAlgebra Mobile on the Desktop ==== | |||
Description: Right now the KAlgebra Mobile version for desktop is quite ugly and useless. Provide a mockup of a better workflow. | |||
Expected results: A version that can actually be used on the desktop and possibly replace the regular KAlgebra in the future. | |||
Prerequisites: QtQuick knowledge, UI design | |||
Time to complete: 4 days | |||
Mentor: Aleix Pol <aleixpol@kde.org> | |||
== Training == | |||
=== easy === | |||
==== Import KWin Scripting Tutorial into KDE Examples ==== | |||
Description: There is one tutorial for KWin scripting written by the developer. This should be imported into a new kwin scripting module in the KDE Examples git repository. | |||
Expected results: Existing KWin Scripting Tutorial in kde-examples repository. | |||
Prerequisites: basic git knowledge | |||
Time to complete: 24 hours | |||
Mentor: [email protected] | |||
==== Recover files for Akonadi Resource tutorial ==== | |||
Description: The files used for the [http://techbase.kde.org/Development/Tutorials/Akonadi/Resources Akonadi Resource tutorial] have been lost due to a failed backup. The task is to work through the tutorial and reconstruct all necessary files in the process. | |||
Expected results: An archive (e.g. tar.gz, zip) of all the files necessary to build and run the resource described in the tutorial. | |||
Prerequisites: Devleopment packages for kdelibs and kdepimlibs and a recent version of KAppTemplate or KDevelop. | |||
Time to complete: 1 day | |||
Mentor: Kevin Krammer <krammer@kde.org> | |||
==== Recover files for Akonadi Application tutorial ==== | |||
Description: The files used for the [http://techbase.kde.org/Development/Tutorials/Akonadi/Application Akonadi Application tutorial] have been lost due to a failed backup. The task is to work through the tutorial and reconstruct all necessary files in the process. | |||
Expected results: An archive (e.g. tar.gz, zip) of all the files necessary to build and run the application described in the tutorial. | |||
Prerequisites: Devleopment packages for kdelibs and kdepimlibs and a recent version of KAppTemplate or KDevelop. | |||
Time to complete: 1 day | |||
Mentor: Kevin Krammer <[email protected]> | |||
=== medium === | |||
==== Phonon Demos! ==== | |||
Description: More phonon demos! Right now, we have a simpleplayer demo with a very simple UI that plays a file. Simply. Some other things that should be done include demonstrating how to handle DVD menus, audio effects, etc. One significant improvement would be some non-graphical demos. Thinking along the lines of a command line metadata extractor or audio player. | |||
Expected results: More phonon demos! | |||
Prerequisites: C++ and libphonon knowledge. | |||
Time to complete: 2 days | |||
Mentor: The Phonominals of #kde-multimedia, maybe tdfischer. | |||
==== Example KWin Script ==== | |||
Description: An example KWin script should be implemented and added to the kde-examples repository. The script could make a window follow the active desktop, so that it is always on the active desktop but not set on all desktops. This could be useful for e.g. a chat client and is a feature provided by other window managers. | |||
Expected results: Example KWin Script implemented | |||
Prerequisites: JavaScript knowledge | |||
Time to complete: 48 hours | |||
Mentor: [email protected] | |||
=== hard === | |||
==== Create solutions for the exercises of the Akonadi Resource tutorial ==== | |||
Description: The [http://techbase.kde.org/Development/Tutorials/Akonadi/Resources Akonadi Resource tutorial] contains several exercise sections for more advanced resource functionality. The task is to solve at least three of them, document the solutions on a separate Wiki page and link the solutions from the respective exercise. | |||
Expected results: An archive (e.g. tar.gz, zip) of all the files necessary to build and run the resource with the exercises' solutions and a Wiki page documenting the necessary steps for each solution. | |||
Prerequisites: Devleopment packages for kdelibs and kdepimlibs and a recent version of KAppTemplate or KDevelop. | |||
Time to complete: 1 week | |||
Mentor: Kevin Krammer <[email protected]> | |||
Hint: most described problems have already been solved for other resources available as part of kdepim-runtime | |||
== Translation == | |||
=== easy === | |||
==== Screenshots for Ukrainian documentation of Kig ==== | |||
Description: Update and complete Ukrainian screenshots for Kig documentation | |||
Expected results: Complete set of 15 screenshots, synced with [https://projects.kde.org/projects/kde/kdeedu/kig/repository/revisions/master/show/doc English originals]. | |||
Prerequisites: moderate knowledge of geometry, basic skills in screenshoting, current stable version of Kig | |||
Time to complete: 24 hrs | |||
Mentor: Yuri Chornoivan yurchor@ukr.net | |||
==== Translate strings in a Python Kig script from Italian to English ==== | |||
Description: Download and edit the following script https://projects.kde.org/projects/kde/kdeedu/kig/repository/revisions/master/changes/pykig/pykig.py and translate all Italian strings to very good English ones without altering any markup of the script. | |||
Expected results: All Italian strings are translated to English in this script | |||
Prerequisites: Italian and English excellent speakers and writers, preferred Kig knowledge (install Kig and use it a bit) | |||
Time to complete: 48 hrs | |||
Mentor: Anne-Marie Mahfouf annma@kde.org | |||
==== Documentation translation (Polish): Update kinfocenter documentation ==== | |||
Description: Update documentation of the kinfocenter program, ~100 messages. | |||
Expected results: All strings are translated and it builds correctly. | |||
Prerequisites: Basic knowledge of shell to be able to run commands that build the documentation (will provide guidelines) | |||
Time to complete: 48h | |||
Mentor: Marta Rybczynska (kde-i18n@rybczynska.net) | |||
==== Documentation translation (Polish): Update glossary documentation ==== | |||
Description: Update documentation of KDE glossary, approx 150 messages. | |||
Expected results: All strings are translated and it builds correctly. | |||
Prerequisites: Basic knowledge of shell to be able to run commands that build the documentation (will provide guidelines) | |||
==== | Time to complete: 48h | ||
Mentor: Marta Rybczynska ([email protected]) | |||
==== Documentation translation (Polish): Update kdegraphics documentation ==== | |||
Description: | Description: Update documentation of the kdegraphics package: gwenview, kolourpaint, kruler, ksnapshot, okular. Approx 200 messages. | ||
Expected results: | Expected results: All strings are translated and it builds correctly. | ||
Prerequisites: | Prerequisites: Basic knowledge of shell to be able to run commands that build the documentation (will provide guidelines), basic knowledge of the programs | ||
Time to complete: | Time to complete: 4 days | ||
Mentor: | Mentor: Marta Rybczynska (kde-i18n@rybczynska.net) | ||
==== | ==== Documentation translation (Polish): Update Amarok QuickStartGuide on Userbase ==== | ||
Description: | Description: Update Amarok QuickStartGuide on userbase (pages Amarok/QuickStartGuide) | ||
Expected results: | Expected results: All pages are fully translated. | ||
Prerequisites: | Prerequisites: Basic knowledge of amarok, userbase account | ||
Time to complete: 48h | Time to complete: 48h | ||
Mentor: | Mentor: Marta Rybczynska (kde-i18n@rybczynska.net) | ||
==== | ==== Update KLettres screenshots (French) ==== | ||
Description: Update | Description: Update KLettres French documentation screenshots. In a default KDE installation, use KSnapshot to do all the 9 screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/klettres/repository/revisions/master/show/doc (all .png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php | ||
Expected results: The | Expected results: The 9 screenshots in French interface are up-to-date with current KLettres interface and current KDE default style and default window decoration. | ||
Prerequisites: | Prerequisites: KLettres installed with French interface, KSnapshot | ||
Time to complete: | Time to complete: 24h | ||
Mentor: Anne-Marie Mahfouf ([email protected]) | Mentor: Anne-Marie Mahfouf ([email protected]) | ||
==== | ==== Update Blinken screenshots (French) ==== | ||
Description: Update | Description: Update Blinken French documentation screenshots (8). In a default KDE installation, use KSnapshot to do all the 8 screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/blinken/repository/revisions/master/show/doc (all .png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php | ||
Expected results: The | Expected results: The 8 screenshots in French interface are up-to-date with current Blinken interface and current KDE default style and default window decoration. | ||
Prerequisites: | Prerequisites: Blinken installed with French interface, KSnapshot | ||
Time to complete: | Time to complete: 24h | ||
Mentor: Anne-Marie Mahfouf ([email protected]) | Mentor: Anne-Marie Mahfouf ([email protected]) | ||
==== | ==== Update KHangMan screenshots (French) ==== | ||
Description: | Description: Update KHangMan French documentation screenshots. In a default KDE installation, use KSnapshot to do all the 9 screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/khangman/repository/revisions/master/show/doc (all .png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php | ||
Expected results: The | Expected results: The 9 screenshots in French interface are up-to-date with current KHangMan interface and current KDE default style and default window decoration. | ||
Prerequisites: | Prerequisites: KHangMan installed with French interface, KSnapshot | ||
Time to complete: | Time to complete: 24h | ||
Mentor: Anne-Marie Mahfouf ([email protected]) | Mentor: Anne-Marie Mahfouf ([email protected]) | ||
==== Make | ==== Make Kanagram screenshots (French) ==== | ||
Description: | Description: Update Kanagram French documentation screenshots (10). In a default KDE installation, use KSnapshot to do all the 10 screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/kanagram/repository/revisions/master/show/doc (all .png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php | ||
Expected results: The | Expected results: The 10 screenshots in French interface are up-to-date with current Kanagram interface and current KDE default style and default window decoration. | ||
Prerequisites: | Prerequisites: Kanagram installed with French interface, KSnapshot | ||
Time to complete: | Time to complete: 24h | ||
Mentor: Anne-Marie Mahfouf ([email protected]) | Mentor: Anne-Marie Mahfouf ([email protected]) | ||
==== | ==== Update KTouch screenshots (French) ==== | ||
Description: | Description: Update KTouch French documentation screenshots. In a default KDE installation, use KSnapshot to do all the 9 screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/ktouch/repository/revisions/master/show/doc (all .png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php | ||
Expected results: The | Expected results: The 9 screenshots in French interface are up-to-date with current KTouch interface and current KDE default style and default window decoration. | ||
Prerequisites: | Prerequisites: KTouch installed with French interface, KSnapshot | ||
Time to complete: | Time to complete: 24h | ||
Mentor: Anne-Marie Mahfouf ([email protected]) | Mentor: Anne-Marie Mahfouf ([email protected]) | ||
==== | ==== Update KBruch screenshots (French) ==== | ||
Description: | Description: Update KBruch French documentation screenshots(12). In a default KDE installation, use KSnapshot to do all the 12 screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/kbruch/repository/revisions/master/show/doc (all .png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php | ||
Expected results: The | Expected results: The 12 screenshots in French interface are up-to-date with current KBruch interface and current KDE default style and default window decoration. | ||
Prerequisites: | Prerequisites: KBruch installed with French interface, KSnapshot | ||
Time to complete: | Time to complete: 24h | ||
Mentor: Anne-Marie Mahfouf ([email protected]) | Mentor: Anne-Marie Mahfouf ([email protected]) | ||
==== | ==== Make Step screenshots (French) ==== | ||
Description: | Description: Make Step French documentation screenshots (8). In a default KDE installation, use KSnapshot to do all the 8 screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/step/repository/revisions/master/show/doc (all .png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php | ||
Expected results: The | Expected results: The 8 screenshots in French interface are up-to-date with current Step interface and current KDE default style and default window decoration. | ||
Prerequisites: | Prerequisites: Step installed with French interface, KSnapshot | ||
Time to complete: | Time to complete: 24h | ||
Mentor: Anne-Marie Mahfouf ([email protected]) | Mentor: Anne-Marie Mahfouf ([email protected]) | ||
==== | ==== Make KmPlot screenshots (French) ==== | ||
Description: Make KmPlot French documentation screenshots (14). In a default KDE installation, use KSnapshot to do all the 14 screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/kmplot/repository/revisions/master/show/doc (all .png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php | |||
Expected results: The 14 screenshots in French interface are up-to-date with current KmPlot interface and current KDE default style and default window decoration. | |||
Prerequisites: KmPlot installed with French interface, KSnapshot | |||
Time to complete: 48h | |||
Mentor: Anne-Marie Mahfouf ([email protected]) | |||
==== Make Marble screenshots (French) ==== | |||
Description: Update Marble French documentation screenshots (20). In a default KDE installation, use KSnapshot to do all the screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/marble/repository/revisions/master/show/doc. Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php. Some screenshots are existing but in an outdated window decoration here http://websvn.kde.org/trunk/l10n-kde4/fr/docs/kdeedu/marble/ and they all need to be redone. | |||
Expected results: The 20 screenshots in French interface are up-to-date with current Marble interface and current KDE default style and default window decoration. | |||
Prerequisites: Marble installed with French interface, KSnapshot, Marble knowledge | |||
Time to complete: 72h | |||
Mentor: Anne-Marie Mahfouf ([email protected]) | |||
==== Make Kig screenshots (French) ==== | |||
Description: Update Kig French documentation screenshots (15). In a default KDE installation, use KSnapshot to do all the screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/kig/repository/revisions/master/show/doc (.png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php. | |||
==== Russian translation of Calligra Flow stencils ==== | Expected results: The 15 screenshots in French interface are up-to-date with current Kig interface and current KDE default style and default window decoration. | ||
Description: Complete Russian translation of Calligra Flow stencils ([http://websvn.kde.org/*checkout*/trunk/l10n-kde4/ru/messages/calligra/desktop_calligra.po desktop_calligra.po], ~1160 short messages) | |||
Prerequisites: Kig installed with French interface, KSnapshot | |||
Expected results: All stencils descriptions should be translated according to KDE Russian Team guidelines without typos, the result should be checked against stencil images from the Flow/Dia repository. | |||
Time to complete: 48h | |||
Prerequisites: Good Russian, basic knowledge of physics and computer science. | |||
Mentor: Anne-Marie Mahfouf ([email protected]) | |||
Time to complete: 168 hrs. | |||
==== Make KWordQuiz screenshots (French) ==== | |||
Mentor: Yuri Efremov [email protected] | |||
Description: Make KWordQuiz French documentation screenshots (21). In a default KDE installation, use KSnapshot to do all the screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/kwordquiz/repository/revisions/master/show/doc (.png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php. | |||
Expected results: The 21 screenshots in French interface are up-to-date with current Kalzium interface and current KDE default style and default window decoration. | |||
Prerequisites: KWordQuiz installed with French interface, KSnapshot | |||
Time to complete: 48h | |||
Mentor: Anne-Marie Mahfouf ([email protected]) | |||
==== Make Kalzium screenshots (French) ==== | |||
Description: Make Kalzium French documentation screenshots (33). In a default KDE installation, use KSnapshot to do all the screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/kalzium/repository/revisions/master/show/doc (.png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php. | |||
Expected results: The 21 screenshots in French interface are up-to-date with current Kalzium interface and current KDE default style and default window decoration. | |||
Prerequisites: Kalzium installed with French interface, KSnapshot, Kalzium knowledge | |||
Time to complete: 48h | |||
Mentor: Anne-Marie Mahfouf ([email protected]) | |||
==== Make KStars screenshots (French) ==== | |||
Description: Make KWordQuiz French documentation screenshots (46). In a default KDE installation, use KSnapshot to do all the screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/kstars/repository/revisions/master/show/doc (.png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php. | |||
Expected results: The 46 screenshots in French interface are up-to-date with current KStars interface and current KDE default style and default window decoration. | |||
Prerequisites: KStars installed with French interface, KSnapshot | |||
Time to complete: 72h | |||
Mentor: Anne-Marie Mahfouf ([email protected]) | |||
==== Make Parley screenshots (French) ==== | |||
Description: Make Parley French documentation screenshots (71). In a default KDE installation, use KSnapshot to do all the screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/parley/repository/revisions/master/show/doc (.png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php. | |||
Expected results: The 71 screenshots in French interface are up-to-date with current Parley interface and current KDE default style and default window decoration. | |||
Prerequisites: Parley installed with French interface, KSnapshot | |||
Time to complete: 1 week | |||
Mentor: Anne-Marie Mahfouf ([email protected]) | |||
==== Documentation translation (French): Translate KImageMapEditor documentation + 2 screenshots ==== | |||
Description: Translate KImageMapEditor User Manual http://websvn.kde.org/*checkout*/trunk/l10n-kde4/templates/docmessages/kdewebdev/kimagemapeditor.pot to French using Lokalize (39 strings) and make the screenshots in French interface based on the English one http://websvn.kde.org/trunk/KDE/kdewebdev/doc/kimagemapeditor/ (2 screenshots) | |||
Expected results: The .po fully translated to French + the 2 screenshots. | |||
Prerequisites: Basic knowledge of Kiten, knowledge of Japanese, Lokalize and KSnapshot | |||
Time to complete: 1 days | |||
Mentor: Anne-Marie Mahfouf ([email protected]) | |||
==== Complete Russian translation of Kalzium interface ==== | |||
Description: Complete Russian translation for Kalzium | |||
Expected results: Full translation of [http://websvn.kde.org/*checkout*/trunk/l10n-kde4/ru/messages/kdeedu/kalzium.po Kalzium interface] (317 messages) into Russian (should be tested on current unstable of Kalzium). | |||
Prerequisites: Good Russian, basic chemistry knowledge. | |||
Time to complete: 5 days | |||
Mentor: Yuri Chornoivan [email protected] | |||
==== Add context information to Gluon code where it's missing ==== | |||
Description: As the title implies, the messages in code are already translated, but in places require context to be added. The context is a description of what the message is supposed to convey in the user interface, and is used by the translators. | |||
Expected results: Context added to all translated messages in the code | |||
Prerequisites: Good English skills, code knowledge not required (only need to know how to find text in multiple files) | |||
Time to complete: 2 days | |||
Mentor: Dan Leinir Turthra Jensen <[email protected]> and Arjen Hiemstra <[email protected]> | |||
==== Finnish translation of some Extragear_sysadmin files ==== | |||
Description: Translate message id strings from English into Finnish ([http://websvn.kde.org/*checkout*/branches/stable/l10n-kde4/templates/messages/extragear-sysadmin/desktop_extragear-sysadmin_libqapt.pot desktop_extragear-sysadmin_libqapt.pot], 6 short messages), | |||
([http://websvn.kde.org/*checkout*/branches/stable/l10n-kde4/templates/messages/extragear-sysadmin/plasma-runner-installer.pot plasma-runner-installer.pot], 3 short messages), | |||
([http://websvn.kde.org/*checkout*/branches/stable/l10n-kde4/templates/messages/extragear-sysadmin/qapt-deb-installer.pot qapt-deb-installer.pot], 37 short messages), and | |||
([http://websvn.kde.org/*checkout*/branches/stable/l10n-kde4/templates/messages/extragear-sysadmin/qapt-gst-helper.pot qapt-gst-helper.pot], 53 short messages). | |||
Expected results: All msgid strings translated into msgstr strings. Rename desktop_extragear-sysadmin_libqapt.pot to desktop_extragear-sysadmin_libqapt.po, plasma-runner-installer.pot to plasma-runner-installer.po, qapt-deb-installer.pot to qapt-deb-installer.po, and qapt-gst-helper.pot to qapt-gst-helper.po. Edit and update the header fields at the beginning of the file. | |||
Prerequisites: Good Finnish | |||
Time to complete: 4 days. | |||
Mentor: Jorma Karvonen [email protected] | |||
=== medium === | |||
==== Finnish translation of KAddressbook for the mobile devices ==== | |||
Description: Translate message id strings from English into Finnish ([http://websvn.kde.org/*checkout*/branches/stable/l10n-kde4/templates/messages/kdepim/kaddressbook-mobile.pot kaddressbook-mobile.pot], 196 short messages) | |||
Expected results: All msgid strings translated into msgstr strings. Rename kaddressbook-mobile.pot to kaddressbook-mobile.po. Edit and update the header fields at the beginning of the file. | |||
Prerequisites: Good Finnish | |||
Time to complete: 5 days. | |||
Mentor: Jorma Karvonen [email protected] | |||
==== Finnish translation of Plasma Gas and Concentration Calculators ==== | |||
Description: Translate message id strings from English into Finnish ([http://websvn.kde.org/*checkout*/branches/stable/l10n-kde4/templates/messages/kdeedu/plasma_applet_concentrationCalculator.pot plasma_applet_concentrationCalculator.pot], 68 short messages) and ([http://websvn.kde.org/*checkout*/branches/stable/l10n-kde4/templates/messages/kdeedu/plasma_applet_gasCalculator.pot plasma_applet_gasCalculator.pot], 49 short messages) | |||
Expected results: All msgid strings translated into msgstr strings. Rename plasma_applet_concentrationCalculator.pot to plasma_applet_concentrationCalculator.po and plasma_applet_gasCalculator.pot to plasma_applet_gasCalculator.po. Edit and update the header fields at the beginning of the files. | |||
Prerequisites: Good Finnish, some knowledge of physics. | |||
Time to complete: 4 days. | |||
Mentor: Jorma Karvonen [email protected] | |||
==== Finnish translation of Step Physics Simulation Engine ==== | |||
Description: Tranlate message id strings from English into Finnish ([http://websvn.kde.org/*checkout*/branches/stable/l10n-kde4/templates/messages/kdeedu/step.pot step.pot], 225 short messages) | |||
Expected results: All msgid strings translated into msgstr strings. Rename step.pot to step.po. Edit and update the header fields at the beginning of the file. | |||
Prerequisites: Good Finnish, some knowledge of physics. | |||
Time to complete: 5 days. | |||
Mentor: Jorma Karvonen [email protected] | |||
==== Finnish translation of Cantor Worksheet Interface for the Mathematical applications ==== | |||
Description: Translate message id strings from English into Finnish ([http://websvn.kde.org/*checkout*/branches/stable/l10n-kde4/templates/messages/kdeedu/cantor.pot cantor.pot], 210 short messages) | |||
Expected results: All msgid strings translated into msgstr strings. Rename cantor.pot to cantor.po. Edit and update the header fields at the beginning of the file. | |||
Prerequisites: Good Finnish, some knowledge of mathematics. | |||
Time to complete: 4 days. | |||
Mentor: Jorma Karvonen [email protected] | |||
==== Russian translation of Calligra Flow stencils ==== | |||
Description: Complete Russian translation of Calligra Flow stencils ([http://websvn.kde.org/*checkout*/trunk/l10n-kde4/ru/messages/calligra/desktop_calligra.po desktop_calligra.po], ~1160 short messages) | |||
Expected results: All stencils descriptions should be translated according to KDE Russian Team guidelines without typos, the result should be checked against stencil images from the Flow/Dia repository. | |||
Prerequisites: Good Russian, basic knowledge of physics and computer science. | |||
Time to complete: 168 hrs. | |||
Mentor: Yuri Efremov [email protected] | |||
==== New Ukrainian sound files for KTuberling ==== | |||
Description: Update and complete Ukrainian sound files for KTuberling | |||
Expected results: New sound files of good quality (should be tested on current stable of KTuberling). Sample list can be found [http://websvn.kde.org/trunk/l10n-kde4/ru/data/kdegames/ktuberling/ here]. | |||
Prerequisites: Microphone, basic skills in audio editor | |||
Time to complete: 72 hrs | |||
Mentor: Yuri Chornoivan [email protected] | |||
==== Documentation translation (Polish): Translate Amarok Manual on Userbase ==== | |||
Description: Translate Amarok Manula on userbase (pages Amarok/Manual) | |||
Expected results: All pages are fully translated. | |||
Prerequisites: Basic knowledge of amarok, userbase account | |||
Time to complete: 7 days | |||
Mentor: Marta Rybczynska ([email protected]) | |||
==== Documentation translation (French): Translate Granatier documentation + screenshots ==== | |||
Description: Translate Granatier User Manual http://websvn.kde.org/*checkout*/trunk/l10n-kde4/templates/docmessages/kdegames/granatier.pot to French using Lokalize and make the screenshots in French interface based on the English ones http://websvn.kde.org/trunk/KDE/kdegames/doc/granatier/ | |||
Expected results: The .po fully translated to French + the screenshots. | |||
Prerequisites: Basic knowledge of Granatier, knowledge of Lokalize and KSnapshot | |||
Time to complete: 2 days | |||
Mentor: Anne-Marie Mahfouf ([email protected]) | |||
==== Documentation translation (French): Translate Kigo documentation + screenshots ==== | |||
Description: Translate Granatier User Manual http://websvn.kde.org/*checkout*/trunk/l10n-kde4/templates/docmessages/kdegames/kigo.pot to French using Lokalize (133 strings) and make the screenshots in French interface based on the English ones http://websvn.kde.org/trunk/KDE/kdegames/doc/kigo/ (7 screenshots) | |||
Expected results: The .po fully translated to French + the 7 screenshots. | |||
Prerequisites: Basic knowledge of Kigo, knowledge of Lokalize and KSnapshot | |||
Time to complete: 3 days | |||
Mentor: Anne-Marie Mahfouf ([email protected]) | |||
==== Documentation translation (French): Translate Klickety documentation + screenshots ==== | |||
Description: Translate Klickety User Manual http://websvn.kde.org/*checkout*/trunk/l10n-kde4/templates/docmessages/kdegames/klickety.pot to French using Lokalize (172 strings) and make the screenshots in French interface based on the English ones http://websvn.kde.org/trunk/KDE/kdegames/doc/klickety/ (9 screenshots) | |||
Expected results: The .po fully translated to French + the 9 screenshots. | |||
Prerequisites: Basic knowledge of Klickety, knowledge of Lokalize and KSnapshot | |||
Time to complete: 3 days | |||
Mentor: Anne-Marie Mahfouf ([email protected]) | |||
==== Documentation translation (French): Translate Palapeli documentation + 1 screenshot ==== | |||
==== Documentation translation (French): Translate Palapeli documentation + 1 screenshot ==== | |||
Description: Translate Palapeli User Manual http://websvn.kde.org/*checkout*/trunk/l10n-kde4/templates/docmessages/kdegames/palapeli.pot to French using Lokalize (143 strings) and make the screenshot in French interface based on the English one http://websvn.kde.org/trunk/KDE/kdegames/doc/palapeli/ (1 screenshot) | Description: Translate Palapeli User Manual http://websvn.kde.org/*checkout*/trunk/l10n-kde4/templates/docmessages/kdegames/palapeli.pot to French using Lokalize (143 strings) and make the screenshot in French interface based on the English one http://websvn.kde.org/trunk/KDE/kdegames/doc/palapeli/ (1 screenshot) | ||
| Line 1,951: | Line 2,154: | ||
Mentor: Utku Aydın ([email protected]) | Mentor: Utku Aydın ([email protected]) | ||
==== Kst 2.x: get ready for translation ==== | |||
Description: Kst 2.x is no longer translated due to changes in KDE's infrastructure and the port to a Qt application. Now is the time to find a solution to that, as suggested here: http://mail.kde.org/pipermail/kst/2011-September/020092.html | |||
Expected results: Kst 2.x ready to be translated (strings listed, infrastructure in the right place). | |||
Prerequisites: Knowledge of KDE's translation facilities | |||
Time to complete: 3 days | |||
Mentor: Nicolas Brisset <[email protected], Kst mailing list> | |||
=== hard === | === hard === | ||
| Line 1,977: | Line 2,193: | ||
Mentor: Anne-Marie Mahfouf ([email protected]) | Mentor: Anne-Marie Mahfouf ([email protected]) | ||
==== Create a custom voice navigation speaker for Marble ==== | ==== Create a custom voice navigation speaker for Marble (10x) ==== | ||
Description: Marble has a route guidance mode that can make use of speakers (pre-recorded sound files) to indicate directions. There are some existing ones to download at http://edu.kde.org/marble/speakers.php and instructions to install them at http://userbase.kde.org/Marble/CustomSpeakers#Voice_Installation and also instructions how to record a custom voice at http://community.kde.org/Marble/VoiceOfMarble. Your task is to follow the instructions and speak and record the full set of voices in a language of choice. The aim is to create a high quality voice set. To get best results you might want to consider recording the voice of a different person (e.g. a local radio speaker or someone else who has experience with voice recording). The voice recording should be done for a language + gender (male/female) combination which has not been covered by other speakers yet or where the quality can be improved upon (e.g. German (Female), French (Female or Male), Japanese (Female or Male), Norwegian (Female or Male), Arabic (Female or Male), Hebrew (Female or Male), etc..). | Description: Marble has a route guidance mode that can make use of speakers (pre-recorded sound files) to indicate directions. There are some existing ones to download at http://edu.kde.org/marble/speakers.php and instructions to install them at http://userbase.kde.org/Marble/CustomSpeakers#Voice_Installation and also instructions how to record a custom voice at http://community.kde.org/Marble/VoiceOfMarble. Your task is to follow the instructions and speak and record the full set of voices in a language of choice. The aim is to create a high quality voice set. To get best results you might want to consider recording the voice of a different person (e.g. a local radio speaker or someone else who has experience with voice recording). The voice recording should be done for a language + gender (male/female) combination which has not been covered by other speakers yet or where the quality can be improved upon (e.g. German (Female), French (Female or Male), Japanese (Female or Male), Norwegian (Female or Male), Arabic (Female or Male), Hebrew (Female or Male), etc..). | ||
| Line 2,109: | Line 2,325: | ||
Mentor: [email protected] | Mentor: [email protected] | ||
==== User Preference for Review Tools in Okular ==== | |||
Description: It will be very convenient for users, if there are some options to change | |||
defaults for the Review tools. This means width of lines, colors of highlights, | |||
transparency and so on. | |||
https://bugs.kde.org/show_bug.cgi?id=284946 | |||
The Student needs to develop a design document which includes where should we add the configurations, how should it look like etc. Open a file and then go to Tools->Review and you can see the current review tool system. Now, think about where and how can we add user preferences. Try to create the whole scenario. You can see other softwares to get some idea and then propose the design in detail. | |||
Design Submission using some design tool like Qt Designer will be nice. If the student do now want to use Designing tool, he can also use some drawing software to draw the design. A Report with some little explanation of the design is necessary in this case. | |||
Expected results: A UI Design for the review tool preference setting. | |||
Prerequisites: Knowledge of UI Design, Experience of using okular, Qt Designer and a good sense of UI. | |||
Time to complete: 3 days | |||
Mentor: Mohammad Mahfuzur Rahman <[email protected]> | |||
Latest revision as of 10:56, 20 March 2013
Warning: please do not modify this wiki anymore, we are currently transfering it to a spreadsheet!
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!
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
- time to complete the proposal
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
- Translation: Tasks related to localization
- User Interface: Tasks related to user experience research or user interface design and interaction
Inside these areas they should be ordered by difficulty of the proposal (must be one of easy, medium, hard)
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
easy
Amarok: add a separation between Authors and former Authors in the About dialog and rearrange former contributors
Description: currently all Authors, past and present, are lumped together in the same list. Find a way, possibly similar to the way former contributors are handled, to nicely place former authors at the bottom of the list. Also, go through the Contributors list and bump down to former contributors those who haven't been active in a while.
Expected results: clear separation between former and present Authors, while still giving due credit to everyone, and an up to date contributors list.
Prerequisites: C++ basics
Time to complete: A few hours to a few days tops for research.
Mentor: Teo Mrnjavac <[email protected]>
Establish Section for KWin Scripts on kde-apps
Description: Users have no way to exchange KWin scripts. A solution is to add a section to kde-apps.org and at the same time request the GHNS integration.
Expected results: Section for KWin scripts available on kde-apps.org
Prerequisites: none
Time to complete: few hours
Mentor: [email protected]
Implement in-place editing in KGpg when renaming groups
Description: When a key group should be renamed currently a window pops up where the user can enter the new group name. This should be ported to allow editing in place (using the usual model-view way, just pressing F2 and editing the stuff).
Expected results: No popup window should be needed anymore for renaming groups
Prerequisites: basic Qt
Time to complete: few hours
Mentor: [email protected]
Rekonq: Add a "Clear All" Button to the Downloads Page
Description: Add a "Clear All" button to delete the downloads history to the downloads page similiar to the one in Chromium. (More Info in #rekonq IRC channel )
Prerequisites: Basic Qt
Time to complete: Two days
Mentor: Furkan Üzümcü ([email protected])
Rekonq: Assign a Shortcut for Opening Downloads Page
Description: Assign a shortcut for opening Downloads page. Ctrl + J is probably the best. (More Info in #rekonq IRC channel )
Prerequisites: Basic Qt
Time to complete: Two days
Mentor: Furkan Üzümcü ([email protected])
Rekonq: Option to Open Links From a Different Domain in New Tab
Description: Add an option in tabs settings page to open links from a different domain in new tab. (More Info in #rekonq IRC channel )
Prerequisites: Basic Qt
Time to complete: Two days
Mentor: Furkan Üzümcü ([email protected])
Rekonq: Add Context Menu Action to TabBar to Close Right/Left Tabs.
Description: Add context menu action to TabBar to close right/left tabs. (More Info in #rekonq IRC channel )
Prerequisites: Basic Qt
Time to complete: Two days
Mentor: Furkan Üzümcü ([email protected])
Rekonq: Move "New Window" Action to the "Tools" Main Menu.
Description: Move "New Window" action to the "Tools" main menu. (More Info in #rekonq IRC channel)
Prerequisites: Basic Qt
Time to complete: Two days
Mentor: Furkan Üzümcü ([email protected])
Description: Give the users a way to navigate between their search requests, similar as in a web browser by adding two buttons: "<" and ">" and make them behave in the expected way.
Prerequisites: Basic Qt
Time to complete: A few hours
Mentor: Sven Krohlas <[email protected]>
Add Support for SugarCRM "leads" to respective resource
Description: The Akonadi data source handle for the SugarCRM web service currently only provides data from the SugarCRM module "contacts" as an Akonadi address book. The module "leads" is very similar in structure, so it could also be mapped into an address book.
Expected results: SugarCRM resource capable of loading and optional saving of leads through KAddressBook.
Prerequisites: development packages of kdelibs and kdepimlibs, Knowlegde of C++, ideally also Qt. Local installation of SugarCRM (freely downloadable, PHP based)
Time to complete: 5 days
Mentor: Kevin Krammer <[email protected]>
Desciption: Add a copy “email address” into the context menu when right clicking on an email address. See BUG 244678
Time to complete: 2 days
Prerequisites: basic qt
Mentor: Sune
Create an about dialog for Marble Plugins
Description: This is an easy task that helps you to get introduced to the Marble code base. There are many plugins missing an about dialog which tells all (license, credits, etc.) about the plugin. Examples are GpsInfo, Navigation, OpenDesktop Items (Social Plugin), Overview map, Photos, Download Progress Indicator, Sun, Stars, Routing. Have a look at existing about dialogs for other plugins that you can use as a template for implementation. Every student can only cover this task for a single plugin.
Expected results: an about dialog with all the correct information about the plugin.
Prerequisites: An installation of Marble master. Basic knowledge of C++ and Qt.
Time to complete: 24 hours
Mentor: [email protected]
Build Gluon on Mac OSX
Description: Gluon build has already been tested on Mac a while ago. Unfortunately, we have mostly Linux and Windows developers, thus nobody tested it recently. It would be nice to get Gluon built on Mac OSX. It might need some minor fixes. No major issues expected. It would also be a great addition to have the building steps documented.
Expected results: Gluon builds fine on Mac and the build steps are documented.
Prerequisites: Having a Mac computer. :)
Time to complete: 1-2 days maximum
Mentor: Laszlo Papp <[email protected]>
Make a proper CPack/CMake support for generating Gluon binary for Mac installation
Description: Gluon already has NSIS CPack/CMake support for generating a binary for Windows installation. deb and rpm support are also available for generating binaries for Meego and Maemo installations. The concept is already available by the existing cmake/cpack system. The task would be to get that concept adopted for Mac and provide a proper package for Mac installation. That would be the missing bit to cover on desktop machines for game players and developers regarding Gluon.
Expected results: Gluon has a proper CPack/CMake support for Mac installation. Screenshots about the graphical steps and workflow are encouraged at the end.
Prerequisites: Having a Mac computer. :)
Time to complete: 2-4 days maximum depending on the ability and effort of the student.
Mentor: Laszlo Papp <[email protected]>
Build Mula on Mac OSX
Description: Mula is a Multi Language Dictionary with online, offline dictionary and text-to-speech support design in mind. Unfortunately, I am mostly a Linux and Windows developer, thus cannot test the build procedure on Mac. It would be nice to get Mula built on Mac OSX. It might need some minor fixes. No major issues expected. It would also be a great addition to have the building steps documented.
Expected results: Mula builds fine on Mac and the build steps are documented.
Prerequisites: Having a Mac computer. :)
Time to complete: 1-2 days maximum
Mentor: Laszlo Papp <[email protected]>
Make a proper CPack/CMake support for generating Mula binary for Mac installation
Description: Mula already has NSIS CPack/CMake support for generating a binary for Windows installation. deb and rpm support are also available for generating binaries for Meego and Maemo installations. The concept is already available by the existing cmake/cpack system. The task would be to get that concept adopted for Mac and provide a proper package for Mac installation. That would be the missing bit to cover on desktop machines for people learning languages.
Expected results: Mula has a proper CPack/CMake support for Mac installation. Screenshots about the graphical steps and workflow are encouraged at the end.
Prerequisites: Having a Mac computer. :)
Time to complete: 2-3 days depending on the ability and effort of the student.
Mentor: Laszlo Papp <[email protected]>
Make Ctrl+Tab in KDE-Telepathy Text UI work
Description: Pressing Ctrl+Tab (and Ctrl+Shift+Tab) in any tabbed application switches tabs. This is currently missing in our tabbed chat interface. Here's a bug for that: https://bugs.kde.org/show_bug.cgi?id=277220 (and no, the patch is not yet in review ;)
Expected results: Working Ctrl+Tab in Text UI.
Prerequisites: Qt
Time to complete: 2 days
Mentor: Martin Klapetek <[email protected]>
Making Join The Game website multilingual
Description: Join The Game is KDE's individual sponsorship program, in which people could donate to KDE on a regular basis. The website needs to become multilingual.
Expected results: An integrated translation workflow with KDE's translation system. (A Messages.sh that uses xgettext to extract all messages)
Prerequisites: PHP
Time to complete: 2-4 days
Mentor: Emil Sedgh <[email protected]>
Allowing everyone to create sprints on sprints.kde.org
Description: Sprints.kde.org is KDE's internally-used program for organizing sprints. Currently, it only allows certain people to create and manage sprints. Ideally, all kde contributors should be able to create new sprints or edit them without the need to poke sysadmins. This also means we will need proper logging system to know who-did-what.
Expected results: An open sprints.kde.org website which allows contributors to create new sprints.
Prerequisites: PHP
Time to complete: 1-3 days
Mentor: Emil Sedgh <[email protected]>
medium
Help with PlasmaQtComponents
Description: QtComponents are simple ui elements such as pushbuttons, lineedits etc. a version for Plasma Desktop widgets is in progress, a version targeted to apps of tablet devices will be needed as well. good as tasks since are many little independednt code snippets
Expected results: a number of completed components agreed at project start
Prerequisites: Knowledge of QML and JS
Time to complete: 4 days
Mentor: Marco Martin
Add Support for KWallet to Akonadi SugarCRM resource
Description: The Akonadi data source handle for the SugarCRM web service currently saves the user's password in its configuration file. The task is to make it save the login information in KDE's password storage service KWallet.
Expected results: SugarCRM resource capable of saving and retrieving login information through KWallet.
Prerequisites: development packages of kdelibs and kdepimlibs, Knowlegde of C++, ideally also Qt. Local installation of SugarCRM (freely downloadable, PHP based)
Time to complete: 5 days
Mentor: Kevin Krammer <[email protected]>
Create a set of actions for KDEs Clipboard application Klipper
Description: Klipper allows to create actions which are based on mimetype or content of the clipboard which are suggested to the user if the rules match. Unfortunately there a very few. Think about useful ones, ask about need in KDE forum and implement them.
Expected results: Create at least 3 new rules
Time to complete: 2 days
Mentor: Sune
Configuration Module for KWin Scripting
Description: There is currently no way to manage KWin Scripts. A small KCM should be added to just list the available scripts similar to the rules listing. It should be possible to add, import, remove and export scripts.
Expected results: A KCM to list the available KWin scripts
Prerequisites: Qt programming knowledge
Time to complete: 36 hours
Mentor: [email protected]
GHNS integration for KWin Scripting KCM
Description: When the KWin Scripting KCM is available it would be nice to have the possibility to easily download and share scripts. Therefore GHNS integration should be added.
Expected results: GHNS integration in KWin Scripting KCM
Time to complete: 48 hours
Mentor: [email protected]
GHNS integration for Window Switching layouts
Description: The Alt+Tab (Tabbox) Window Switching is about to be ported to QtQuick interfaces. This allows that users could create their own layout. To support this the existing Tabbox configuration module should receive GHNS support.
Expected results: GHNS integration in Window Switching KCM
Time to complete: 48 hours
Mentor: [email protected]
Add QWhatsThis help and Tooltips in KTouch Settings dialog
Description: KTouch Settings dialog is made with QtDesigner pages. You need to edit these .ui files in QtDesigner and add WhatsThis and Tooltips for the visual widgets that are missing them. Tooltips explain shortly what the setting should do and WhatsThis explains it in more details.
References: http://techbase.kde.org/Development/Architecture/KDE4/Providing_Online_Help
Files to work on: ktouchprefgeneralpage.ui, ktouchprefkeyboardpage.ui, ktouchprefcolorspage.ui and ktouchpreftrainingpage.ui in https://projects.kde.org/projects/kde/kdeedu/ktouch/repository/revisions/master/show/src/ui
Expected results: All settings widgets should have tooltips and whatsthis information in KTouch Settings dialog
Prerequisites: QtDesigner basic knowledge, KTouch knowledge, good English writing
Time to complete: 48 hours
Mentor: [email protected]
Improve visualimagecompare, one of Calligra's testing tools
Description: Improve visualimagecompare, one of Calligra's testing tools. visualimagecompare is a tool used together with cstester to check the difference between rendering of different versions of Calligra output to see if there are regressions. This tool helps us quite a lot to find regressions and see the improvements and control them. There is one bug and one feature to be implemented. The bug to fix is that the window of visualimagecompare should not be larger than the desktop.
Expected results: The window should be no larger than the desktop and the content should be resized to fit.
Additional information: See http://community.kde.org/Calligra/Building on how to build Calligra
Prerequisites: Basic knowledge of C++, knowledge of Qt is a plus
Time to complete: 40h
Mentor: zachmann at kde dot org
Improve visualimagecompare, one of Calligra's testing tools
Description: Improve visualimagecompare, one of Calligra's testing tools. visualimagecompare is a tool used together with cstester to check the difference between rendering of different versions of Calligra output to see if there are regressions. This tool helps us quite a lot to find regressions and see the improvements and control them. There is one bug and one feature to be implemented. The bug to fix is that the window of visualimagecompare should not resize if the filename is longer then the screen size. The new feature is to display the number of documents that have changes and the number of the current document.
Expected results: The window does not resize when the document name is longer then the window. The full title should still be visible. The user should be able to see the current/total number of files that have changes.
Additional information: See http://community.kde.org/Calligra/Building on how to build Calligra
Prerequisites: Basic knowledge of C++, knowledge of Qt is a plus
Time to complete: 40h
Mentor: zachmann at kde dot org
Improve visualimagecompare, one of calligras testing tools
Description: Improve visualimagecompare, one of calligras testing tools. visualimagecompare is a tool used together with cstester to check the difference between rendering of different versions of calligra output to see if there are regresessions. This tool helps us quite a lot to find regressions and see the improvements and control them. Add filtering by filetype to visualimagecompare so that it is possible to hide some filetypes when comapring the files. Design a way show the user can select the file types he wants to see.
Expected results: The user needs to be able to limit the number of results by filetype.
Additional information: See http://community.kde.org/Calligra/Building on how to build Calligra
Prerequisites: Basic knowledge of C++, knowledge of Qt is a plus
Time to complete: 40h
Mentor: zachmann at kde dot org
Improve visualimagecompare, one of calligras testing tools
Description: Improve visualimagecompare, one of calligras testing tools. visualimagecompare is a tool used together with cstester to check the difference between rendering of different versions of calligra output to see if there are regresessions. This tool helps us quite a lot to find regressions and see the improvements and control them. Add searching by filename to the userinterface. The search should start automatically if the user types text. The current visible presentation should automatically switch to the next result that matches the searched string.
Expected results: The user needs to be able to search a result by the filename
Additional information: See http://community.kde.org/Calligra/Building on how to build Calligra
Prerequisites: Basic knowledge of C++, knowledge of Qt is a plus
Time to complete: 40h
Mentor: zachmann at kde dot org
Rekonq: Remove Two Actions From Tabs' Context Menu
Description: Remove the "Open The Last Closed Tab" and "Closed Tabs" actions and set "New Tab" button's context menu to the empty area context menu on TabBar. (More Info in #rekonq IRC channel )
Prerequisites: Basic Qt
Time to complete: Three days
Mentor: Furkan Üzümcü ([email protected])
Description: Add two actions to the history panel context menu to forget or delete an history entry. In the same way, a third action has to be created to delete all history entries of a day.
Prerequisites: Basic Qt
Time to complete: Three days
Mentor: Yoann Laissus (yoann.laissus at gmail.com)
Description: Add an optional toolbar to Choqok UI, then user can add/remove actions available in menus to it. Here is a wish regarding this: https://bugs.kde.org/show_bug.cgi?id=274646
Prerequisites: KDE UI
Time to complete: two day
Mentor: Mehrdad Momeny (mehrdad.momeny{at}gmail.com)
Amarok: Amazon store context view
Description: The "info" context applet used to display infos for services is not yet being used in a meaningful way in that service. It should show some infos about the album, fetched from Amazon
Prerequisites: Basic Qt, regular expressions
Time to complete: Two days
Mentor: Sven Krohlas <[email protected]>
Dictionary for KAlgebra Mobile
Description: Create a KAlgebra Mobile tool with information similar to the dictionary tab in the KAlgebra desktop version.
Prerequisites: QtQuick
Time to complete: 3 days
Mentor: Aleix Pol <[email protected]>
Implement a reload all tabs function in Akregator
Description: Sometimes some tabs are not loaded on start because the network connection or a server was down. Right now a user has to reload every single tab. Implement the possibility of reloading them all and give access to this function via shortcut, menu, toolbar (possibly hidden) and the error page. See also: BUG: 203229
Prerequisites: basic Qt
Time to complete: 2 days
Expected results: A reload all tabs function integrated as described above.
Mentor: Sune
Implement a search bar for feed folders in Akregator
Description: If a user has many feeds, it takes to much time to scroll through the list of feeds and find the one he is searching for. In Kmail the same problem is solved by a search bar. Your task is to implement this search bar in Akregator. See also BUG: 194858
Prerequisites: basic Qt
Time to complete: 2 days
Mentor: Sune
Make Akregator network aware
At the moment Akregator are not network aware, which means they try to restore tabs on start up or check feeds for new messages even though the network is not available yet or temporally unavailable. This uses unnecessary system resources and does not look very good. Please read Sune Vuorela's blog post about network aware applications
Expected results: Akregator should suspend all network activity when the network is not available and continue with it as soon as the network is available
Time to complete: 2 days
Mentor: Sune
Akregator Make clicking on a feed-folder always activate the tab showing its contents
Description: At the moment Akregator does not jump to/activate the feed-folder-tab if you click on it, if you are already in it. This means you have to click on an other folder and then the folder you actually want to access. See also Bug 202498
Expected results: When a users clicks on a feed-folder, the feed-folder-tab showing its contents should always be activated and shown.
Prerequisites: basic Qt
Time to complete: 1 day
Mentor: Sune
Add link to phonon settings to Kmix panel applet
Description: The Kmix panel applet should give access to phonon systemsettings module so that the user has the possibility to configure his sound settings. On right click the kmix panel applet should give access (a “link”) to the phonon systemsettings module. See also Bug 226124
Time to complete: 1 day
Prerequisites: basic Qt
Mentor: Harald
Prevent loading of more than one Dragon player instance
Description: Currently a new instance of Dragon player is loaded every time video file is opened. In most cases this does not make sense. Add an option which loads the newly opened video file in the existing Dragon Player instance.
Time to complete: 2 days
Mentor: Harald
Prerequisites: basic Qt
Build a set of game specific QML components
Description: Since Gluon uses QML for in-game UI, it would be advantageous to have a set of simple UI components on which to base game UI on. This will enable game developers to develop more complete games more rapidly. You should remember to consider theming when designing these components (for example by using the Gluon asset system).
Expected results: A set of basic UI components (buttons, check boxes and the like), as well as a couple of dialogues (such as a simple main menu component)
Prerequisites: Qt Quick, game UI design an advantage. Gluon knowledge not requires, we'll help with that.
Time to complete: 10 days
Mentor: Arjen Hiemstra <[email protected]>
Create a simple game using Gluon
Description: Gluon's game creation tool Gluon Creator is a highly specialised tool, designed to assist the makers of games in creating games as easily as possible. So, this task is designed to let you use this tool, to build a simple game in a week. Bring your own idea, put it together and publish it.
Expected results: A complete game (with win/loose conditions appropriate to concept, interaction with mouse and keyboard), published on gamingfreedom.org.
Prerequisites: A game concept (bring your own), coding knowledge (game logic is written using ecmascript, assistance in Gluon scripting concepts will be provided)
Time to complete: 1 week
Mentor: Dan Leinir Turthra Jensen <[email protected]> and Arjen Hiemstra <[email protected]>
Continue/Finish the Pong game creation using Gluon
Description: Gluon's game creation tool Gluon Creator is a highly specialised tool, designed to assist the makers of games in creating games as easily as possible. So, this task is designed to let you use this tool, to get the Pong game ready in a week. Pong (marketed as PONG) is one of the earliest arcade video games, and is a tennis sports game featuring simple two-dimensional graphics. There are already certain things implemented, and you could get a good mentorship working together with the author who started to make it work. There are still interesting bits to solve.
Expected results: A complete Pong game for enjoyment. :) published on gamingfreedom.org.
Prerequisites: Coding knowledge (game logic is written using ecmascript, assistance in Gluon scripting concepts will be provided)
Time to complete: 1 week
Mentor: Laszlo Papp <[email protected]>
Continue/Finish the Snake game using Gluon
Description: Gluon's game creation tool Gluon Creator is a highly specialised tool, designed to assist the makers of games in creating games as easily as possible. So, this task is designed to let you use this tool, to get the Snake game ready in a week. Nokia is well known for putting Snake on the majority of their phones. After it became the standard pre-loaded game on Nokia phones in 1998, Snake found a massive audience. There are already certain things implemented, and you could get a good mentorship working together with the author who started to make it work. There are still interesting bits to solve.
Expected results: A complete Snake game for enjoyment. :) published on gamingfreedom.org.
Prerequisites: Coding knowledge (game logic is written using ecmascript, assistance in Gluon scripting concepts will be provided)
Time to complete: 1 week
Mentor: Laszlo Papp <[email protected]>
Implement QWidget-based tooltips for KDE-Telepathy Contact List
Description: Default Qt tooltips allows just a HTML/RichText formatting. We'd like to have tooltips based on QWidget (or QML) like System Settings has, so we can have better control over the tooltip and it's content.
Expected results: Working tooltips in Contact List.
Prerequisites: Qt
Time to complete: 3 days
Mentor: Martin Klapetek <[email protected]>
Marble: Visualize data aging (tiles)
Description: Marble usually downloads the map data in the form of texture tiles. These tiles get downloaded incrementally whenever a certain area of is viewed at a certain zoom level. As soon as each tile has been downloaded it starts to age: after some time the tile expiration time has passed. Once this happens and once the tile is supposed to get displayed the tile is downloaded again to allow for an update of the tile. For debugging purposes it would be nice to display the age of the tile encoded in color shades. This can be easily done using the blending framework.
Expected results: tiles show color tints that represent the age of a tile.
Prerequisites: Knowledge of Qt and C++
Time to complete: 4 days
Mentor: Jens-Michael Hoffmann
Kst: add Matlab .mat data source using matio
Description: The Kst plotting tool has a plugin-based data source mechanism to be able to add new formats easily. It already supports ASCII, netCDF, images, dirfile and CFitsIO and could be extended fairly easily to read matlab binary files with matio (http://sourceforge.net/projects/matio/files/)
Expected results: ability to load scalars, vectors and matrices from .mat into Kst.
Prerequisites: Knowledge of Qt and C++
Time to complete: 3 days
Mentor: Nicolas Brisset <[email protected], Kst mailing list>
Kst: date/time support for the ASCII data source
Description: Kst's ASCII data source is already one of the most versatile and efficient, but it currently lacks the ability to read times or dates as formatted strings (e.g. HH:MM:SS.SSS or YYYY/MM/DD). This should be easy to add using Qt's date and time classes and a few more UI options in the ASCII config dialog.
Expected results: ability to read time and dates from formatted ASCII strings into Kst.
Prerequisites: Knowledge of Qt and C++
Time to complete: 3 days
Mentor: Nicolas Brisset <[email protected], Kst mailing list>
Make The Selection Pop-up Menu in Okular Work Perfectly
Description: If somebody clicks the selection pop-up menu, the options do not always come instantly. I need on average 3 clicks to get it worked.
Expected results: Make the pop-up menu working in single click.
Prerequisites: Qt
Time to complete: 2 days
Mentor: Mohammad Mahfuzur Rahman <[email protected]>
Disable the copy option after making an empty selection in okular
Description: If text selection is activated and someone right clicks the mouse button after making an empty selection the copy text option still appears which logically should not. The target of this task is to make it solved.
Expected results: No copy option appears after empty selection.
Prerequisites: Qt
Time to complete: 2 days
Mentor: Mohammad Mahfuzur Rahman <[email protected]>
hard
Prevent screen saver from kicking in in Dragon player.
Description: Currently KDEs video player Dragon Player lack a function which prevents the screen saver from kicking in while playing. KDE's energy management can be made aware of a running video player through a few lines of code, documented here (link to blog entry, need to add later since I am out of internet at the moment)
Time to complete: 2 days
Mentor: Harald
Prerequisites: basic Qt, willingness to dive thru layers of abstraction. The issue might be in workspace.
Add Support for SugarCRM "tasks" to respective resource
Description: The Akonadi data source handle for the SugarCRM web service currently only provides data from the SugarCRM module "contacts" as an Akonadi address book. The module "tasks" contains what KDE PIM calls TODOs, so the task is to map "tasks" entries to a respective Akonadi calendar.
Expected results: SugarCRM resource capable of loading and optional saving of tasks through KOrganizer.
Prerequisites: development packages of kdelibs and kdepimlibs, Knowlegde of C++, ideally also Qt. Local installation of SugarCRM (freely downloadable, PHP based)
Time to complete: 5 days
Mentor: Kevin Krammer <[email protected]>
Rekonq: Reopened closed Tab Should Go, As Best As Possible, Where the Original Tab Was
Description: Re-opened closed tab should go, as best as possible, where the original tab was. The student who chooses to do this task should come to #rekonq on IRC for a in-depth discussion.
Prerequisites: Basic Qt
Time to complete: A Week
Mentor: Furkan Üzümcü ([email protected])
Rekonq: Middle Click a Bookmark Folder to Open the Folder in New Tabs
Description: Middle Click a bookmark folder to open the folder in new tabs. (More Info in #rekonq IRC channel )
Prerequisites: Basic Qt
Time to complete: A Week
Mentor: Furkan Üzümcü ([email protected])
Choqok: Add support for Twitter photo upload API method
Description: Recently Twitter added ability to attach a photo to tweets, just like StatusNet had before. So the purpose is supporting this feature just like supporting StatusNet feature in Choqok. So, You have an example of whatever you need to do (from GUI to Backend), in Laconica(old name of StatusNet) microblog plugin of Choqok. And here is the API method ref: https://dev.twitter.com/docs/api/1/post/statuses/update_with_media
Prerequisites: KIO library/ knowing XML or JSON / and basic understanding of HTTP methods
Time to complete: Four days
Mentor: Mehrdad Momeny (mehrdad.momeny{at}gmail.com)
Marble: Create a settings dialog for Marble Plugins
Description: This is a medium task that helps you to get introduced to the Marble code base. There are many plugins missing a settings dialog which allows to tweak some of the settings of the plugin. Examples are GpsInfo, Navigation, OpenDesktop Items (Social Plugin), Download Progress Indicator, Sun, Stars. Have a look at existing settings dialogs for other plugins that you can use as a template for implementation.
Expected results: A settings dialog for a plugin which so far has no such dialog. The dialog should provide some basic means to make useful tweaks to the plugin.
Prerequisites: An installation of Marble master. Basic knowledge of C++ and Qt.
Time to complete: 120 hours
Mentor: [email protected]
Marble: Refactor the Measure Tool into a plugin of its own
Description: The current Measure Tool is not a Marble plugin yet. Make it one.
Expected results: The Measure Tool refactored into a plugin.
Prerequisites: An installation of Marble master. Basic knowledge of C++ and Qt.
Time to complete: 120 hours
Mentor: [email protected]
Marble: Create a basic "window manager" for float items
Description: Float items in Marble are the info boxes that are displayed on top of the map. They can be enabled and disabled and can be moved freely over the map. So far this also allows to have the float items overlap. However this is not desired: we'd like to have the floatitems snap to positions, so that they maintain a certain distance to other float items (e.g. 10 pixels). In the most basic implementation the float items would just snap to the new position if they overlap initially.
Expected results: A basic implementation of a float item manager provided as a patch.
Prerequisites: An installation of Marble master. Basic knowledge of C++ and Qt.
Time to complete: 120 hours
Mentor: [email protected]
Documentation
easy
Update part of the Calligra documentation
Description: Calligra project has some outdated documentation. The task consists in updating a part of the online docs
Expected results: have an up-to-date Online Help.
Prertequisites: English language,some basic HTML knowledge.
Time to complete: 48 hours.
Mentors: [email protected]
Update the Amarok Manual to the latest version (approx. 5x)
Description: The current Amarok Manual refers to version 2.4.0 which is already rather old. The task is to check for each entry if the text and screen shots still apply to the current stable version of Amarok and adapt if necessary.
Expected results: have an up-to-date Manual in Userbase.
Prerequisites: English language, some basic HTML knowledge and basic Mediawiki knowledge.
Time to complete: 48 hours.
Mentors: [email protected], [email protected]
Move KWin Scripting documentation to techbase
Description: The user documentation and tutorial for the KWin Scripting module is currently only in two blog posts written by the author of the module. The documentation should be imported into techbase.kde.org and adapted to the Wiki syntax and integrated into the general structure.
Expected results: have KWin scripting documentation and tutorial in Techbase.
Prerequisites: English language, basic Mediawiki knowledge.
Time to complete: 24 hour
Mentors: [email protected]
Redo KTouch handbook screenshots
Description: Redo all documentation screenshots for KTouch because they are outdated. Get KTouch source from git or ask the mentor to provide you a tarball. Use KSnapshot and read http://l10n.kde.org/docs/screenshots.php in order to redo the screenshots in png format with the default KDE theme and windows decoration.
Expected results: send the new screenshots to the mentor who will commit them in the repository.
Prerequisites: preferably look at KTouch user manual prior to doing the task.
Files location: https://projects.kde.org/projects/kde/kdeedu/ktouch/repository/revisions/master/show/doc
Time to complete: 24 hour
Mentors: [email protected]
Redo Kalzium userbase screenshots
Description: Redo all userbase documentation screenshots for Kalzium because they are outdated. Use KSnapshot and read http://l10n.kde.org/docs/screenshots.php in order to redo the screenshots in png format with the default KDE theme and windows decoration. The handbook has already updated screenshots.
Expected results: The screenshots on userbase are updated.
Prerequisites: preferably look at Kalzium user manual and userbase prior to doing the task.
Files location: https://projects.kde.org/projects/kde/kdeedu/kalzium/repository/revisions/master/show/doc
Time to complete: 24 hour
Mentors: [email protected]
Update the Kiten handbook and userbase documentation
Description: Both userbase documentation and handbook are outdated. The task consists on updating the screenshots and features included in the docs to be consistent to the latest version of Kiten.
Expected results: send the updated files to the mentor to commit them.
Prerequisites: In case you don't know Kiten, then install it and use it to see what features it offers you. You will probably need a Japanese font on your system in order to search in the dictionary, or you can copy-paste some words on it. Also look to the KDE documentation screenshots requirements.
Time to complete: 24 to 48 hours
Mentor: Daniel E. Moctezuma ([email protected])
Fill missing data of oxidation states in Kalzium
Description: Oxidation state support was introduced in Kalzium 4.7. Not all Atoms have currently a value in the elements.xml file. The task would be to add all missing oxidation states data into the elements.xml. Existing data should also be reviewed. Use wikipedia to get the data of each atom.
Expected results: Send the finished elements.xml to the mentor.
Prerequisites: You should not be afraid of xml. Chemistry knowledge is not needed.
Files location: https://projects.kde.org/projects/kde/kdeedu/kalzium/repository/revisions/master/changes/libscience/data/elements.xml
Time to complete: 24 hour
Mentors: [email protected]
Rewrite part of KDE Accessibility Documentation
Description: Rewrite and update the documentation for KDE Accessibility settings on userbase here: http://userbase.kde.org/System_Settings/Accessibility
Expected results: Detailed documentation of kde accessibility settings.
Prerequisites: English language, some basic HTML knowledge.
Time to complete: a few hours.
Mentor: [email protected]
Update KAlgebra handbook
Description: The KAlgebra handbook was written by its original developer some time ago already and has some outdated parts. Make sure everything in there is true and provide more explanation where needed.
Expected results: Good documentation that can be understood by someone unrelated to KAlgebra's development.
Prerequisites: Math vocabulary and writing skills.
Time to complete: 1 week
Mentor: Aleix Pol <[email protected]>
Konquest documentation update
Description: Update Konquest documentation (DocBook formatted) for the current code in trunk. Add a screenshot of the game window.
Expected results: Fix inconsistencies in documentation with the current game. Describe new feature (Standing order) of the new version. Add screenshot of the game window.
Prerequisites: English, compiled Konquest version from KDE trunk, basic docbook syntax knowledge.
Time to complete: 48 hrs.
Mentor: Yuri Chornoivan <[email protected]>
Gluon game logic scripting documentation
Description: Complete the documentation for the Gluon game logic system, which is in progress at the Gluon website: Scripting Reference.
Expected results: Completed documentation set for the Gluon scripting API as a single page (as seen in the current state).
Prerequisites: English, light knowledge of C++ and/or javascript
Time to complete: 3 days
Mentor: Dan Leinir Turthra Jensen <[email protected]>
Gluon game logic scripting documentation, option 2
Description: Build documentation for the Gluon game logic system, using a documentation management system (allow commenting on each article etc.). Optionally the documentation should be automatically generated, though this is of secondary concern.
Expected results: Complete documentation collection for the wrapped Qt classes (list available at Scripting Reference).
Prerequisites: English, knowledge of web CMSes, light knowledge of C++ and/or javascript
Time to complete: 1 week
Mentor: Dan Leinir Turthra Jensen <[email protected]>
Screenshots for Gluon documentation
Description: The current documentation for Gluon Creator has a large amount of text and very few pictures. This task aims to fix this issue by letting you go crazy and produce screenshots of every feature and workflow you can find.
Expected results: Screenshots for the documentation on the website at the Gluon website's documentation section
Prerequisites: None per se
Time to complete: 3 days
Mentor: Dan Leinir Turthra Jensen <[email protected]>
Expand Plasma Active FAQ
Description: We have created a Beginner's FAQ for Plasma Active which lists answers to some questions that novice users of Plasma Active often encounter. The first part of this task is to expand this list with questions that have come up in the forums, on IRC, on the mailing list or which you ask yourself while using Plasma Active. After adding the questions, the second part is to ask the Plasma Active team to
Expected results: At least ten new questions and answers in the FAQ.
Prerequisites: None. Access to a device running Plasma Active ( see Device List ) or a virtual machine running Plasma Active is necessary if you want to add your own questions instead of those asked by others.
Time to complete: 3 Days
Mentor: Thomas Pfeiffer ( [email protected] )
medium
Import KWin Scripting API documentation to techbase
Description: The JavaScript API documentation for KWin Scripting module is currently only available through an application in the KWin source directory which generates an HTML page. The documentation should be made available in techbase.kde.org and follow the structure of JavaScript API documentation for Plasma.
Expected results: KWin Scripting API documentation in Techbase
Prerequisites: Being able to compile source code to generate the API documentation and MediaWiki knowledge
Time to complete: 48 hours
Mentor: [email protected]
Prepare illustrated introduction to integrating Kontact with Google services (to be hosted on UserBase)
Expectation: A set of screen-shots and/or short screen-casts showing how to set up Google integration. They should include setting up forwarded mail from GMail, using GMail IMAP resources, integrating contact information, and integrating Google Calendar with KOrganizer calendar.
Ideally there should be scope for language-independence. This might take the form of animated gifs with a text description suitable for translation, or, preferably, video with the possibility of soundtrack overlays.
Pre-requisites: A working Kontact of the latest stable version, to include a calendar suitable for testing with Google Calendar. A GMail account. Installed software for preparation of animated gifs or full screen-casts. Basic wiki markup skills. An IRC client installed.
Time to complete: 168 hours
Mentor: [email protected] (wiki), [email protected] (Kontact), [email protected](Video)
User documentation for setup and use of Kmail
Description: Kmail is being adopted by more users and should have simple to understand, easy to follow setup and use instructions for people wanting to use it with existing webmail or office accounts.
Expected results: Kmail User documentation in Userbase
Prerequisites: Being able to give clear instructions and proofread.
Time to complete: 24 hours
Mentor: [email protected]
Description: Marble has a route guidance mode that can make use of speakers (pre-recorded sound files) to indicate directions. There are some existing ones to download at http://edu.kde.org/marble/speakers.php and instructions to install them at http://userbase.kde.org/Marble/CustomSpeakers#Voice_Installation and also instructions how to record a custom voice at http://community.kde.org/Marble/VoiceOfMarble. Your task is to combine these information into a comprehensible guide that describes how to record and install a custom voice such that in the end one has Marble speak your own voice in guidance mode.
Expected results: A finished section http://userbase.kde.org/Marble/CustomSpeakers#Creating_Custom_Voices that users can easily follow.
Prerequisites: An installation of Marble 1.2 (KDE 4.7). Can be compiled from source code as well. An installation of Marble on the N900 would be nice, but is not absolutely necessary.
Time to complete: 24 hours
Mentor: [email protected]
Document the Kate Snippets plugin
Description: Many of Kate's plugins are currently undocumented, so users are potentially missing out on some awesome features because they don't know how to use them. Kate Snippets allow users to insert chunks of text in their files to save them some typing. Your task is to explain to users how this plugin works.
Expected results: A section of the plugins chapter describing the Kate Snippets plugin. It should include a basic introduction that explains how to use the plugin, a list of the menu options provided by the plugin, and a description of all the elements in the plugin's user interface. The File Templates plugin documentation is an excellent example of complete plugin documentation. You don't have to know DocBook, the XML language KDE documentation is written in; just use plain text or your favorite word processor.
Prerequisites: A good command of the English language, a working Kate installation and the ability and desire to try things out, see how they work, and explain it to others.
Time to complete: 1-2 days
Mentor: T.C. Hollingsworth <[email protected]>
KAlgebra's console userbase tutorial
Description: Provide a document explaining KAlgebra's console features to be put on the userbase's wiki.
Expected results: A good review of the KAlgebra language and its features in a console.
Prerequisites: Math and writing skills. Functional Programming knowledge will help for sure.
Time to complete: 3 days
Mentor: Aleix Pol <[email protected]>
Plasma QtComponents documentation
Description: document the api of the new Plasma QtComponents in the code, with a doxygen style notation (even tough doxygen doesn't support qml, so it could have to be copied over manyally to techbase).
Expected results: At least 10-15 widgets with a completely documented api comprised with use cases.
Prerequisites: a basic level of Qt/QML knowledge.
Time to complete: 5 days
Mentor: Marco Martin <[email protected]>
Gluon Video Tutorial
Description: Record and mix one of the pre-scripted tutorials on the the Video Tutorial Scripts page.
Expected results: One completed video tutorial, uploaded to vimeo under a suitable CC license
Prerequisites: Good vocal English skills, basic KDEnlive skills
Time to complete: 3 days for first video (to create project and style), 2 for subsequent
Mentor: Dan Leinir Turthra Jensen <[email protected]>
Kst: refresh Kst documentation for Kst 2.x
Description: Take the existing Kst 1.x documentation and refresh it to Kst 2.x
Expected results: Choice how to handle documentation (Userbase ?) and a first clear structure with tags towards what needs to be updated, deleted or added.
Prerequisites: Good English skills
Time to complete: 4 days, 3 if already familiar with Kst
Mentor: Nicolas Brisset <[email protected], Kst mailing list>
hard
Document a Kate plugin for developers
Description: Many of Kate's plugins are currently undocumented, so users are potentially missing out on some awesome features because they don't know how to use them. Among these plugins are ones that interface with some powerful tools used by developers to make programming easier. If you're familar with things like debuggers, compiling programs, or SQL, and want to learn how to more easily do these things and help others learn too, this is the task for you. Plugins that need documenting include the build plugin, GDB plugin, and the SQL plugin. Your task is to pick one, and explain how it works.
Expected results: A section of the plugins chapter describing the plugin you choose. It should include a basic introduction that explains how to use the plugin, a list of the menu options provided by the plugin, and a description of all the elements in the plugin's user interface. The File Templates plugin documentation is an excellent example of complete plugin documentation. You don't have to know DocBook, the XML language KDE documentation is written in; just use plain text or your favorite word processor.
Prerequisites: A good command of the English language, a working Kate installation, the ability and desire to try things out, see how they work, and explain it to others, and some knowledge of the tools involved in the plugin. (e.g. you should have some knowledge of how databases and SQL work if you're going to work on the SQL plugin.) If you're not familiar with these tools, you might find the Kate snippets plugin easier.
Time to complete: 2-4 days
Mentor: T.C. Hollingsworth <[email protected]>
A Documentation on Okular document and paging system
Description: In okular, the full document open for reading is called document and every pages are called page. All the text in a page is called a textpage. So, basically a document consists of pages and each page consist one textpage. This is a very basic concept of okular which every developer need to know if they want to start development with okular.
There is a good document about how to implement a generator at: http://api.kde.org/4.7-api/kdegraphics-apidocs/okular/html/okular_generators.html . It might be a reference example on how to write a document for okular.
The Student should study on some part of okular codebase and made a good documentation on how okular document and page system works. You are goint to need to see the document, page and textpage files(.h and .cpp) in detail.
Expected results: A good documentation to be included in kdegraphics api of okular.
Prerequisites: Good English skills, Some knowledge of okular should be a plus.
Time to complete: 3-4 days
Mentor: Mohammad Mahfuzur Rahman <[email protected]>
Outreach
easy
Description: Akregator contains a short list of KDE related feeds which are shown on first start. This list is partially outdated. Create a suggestion for an updated list, may be add some more KDE/Linux related feeds. Also check, if it is possible to have a different list depending on the users language.
Expected results: An updated list of KDE/Linux-related feeds integrated in to Akregator
Time to complete: 24 hours
Mentor: Sune
Description: KDE contains a short list of KDE related bookmarks which are shown in Konqueror and Rekonqon first. Update them, look for useful KDE/Linux related links. If necessary, ask in KDE forum for useful suggestions. Also check, if it is possible to have a different list depending on the users language.
An updated list of KDE/Linux-related bookmarks integrated into KDE.
Time to complete: 24 hours
Mentor: Sune
Create Demo data for KDE's Addressbook application
Description: When demonstrating KDE PIM software at fairs or exhibitions, we usually lack data for our applications to show their features. This task is about creating contact data for fake personas, i.e. inventing a name and life of a person and creating addressbooks that such a person would likely have.
Expected results: descriptions of three personas and at least one addressbook per persona. Contact data should contain at least names, addresses and email addresses.
Prerequisites: any version of KAddressbook, preferably a current one.
Time to complete: 2 days
Mentor: Kevin Krammer <[email protected]>
Create Demo data for KDE's Calendaring application
Description: When demonstrating KDE PIM software at fairs or exhibitions, we usually lack data for our applications to show their features. This task is about creating calendar data for fake personas, i.e. inventing a name and life of a person and creating calendars that such a person would likely have.
Expected results: descriptions of three personas and at least one calendar per persona. Calendar data should contain events, normal and recurring ones, todos in different state of completion.
Prerequisites: any version of KOrganizer, preferably a current one.
Time to complete: 2 days
Mentor: Sérgio Martins <[email protected]>
Create Demo data for KDE's mail application
Description: When demonstrating KDE PIM software at fairs or exhibitions, we usually lack data for our applications to show their features. This task is about creating mail data for fake personas, i.e. inventing a name and life of a person and creating a mail setup that such a person would likely have.
Expected results: descriptions of three personas and some email data for each one. You can subscribe to mailinglists and/or exchange emails between your personas (and/or between them and yourself).
Prerequisites: any version of KMail, preferably a current one and either some accounts at a free mail provider or other means to send and receive mails with different email addresses.
Time to complete: 3 days
Mentor: Kevin Krammer <[email protected]>
Create Demo data for KDE's groupware application
Description: When demonstrating KDE PIM software at fairs or exhibitions, we usually lack data for our applications to show their features. This task is about creating data to show integration between PIM components.
Expected results: using personas and their data to create more advanced data such as events with participants selected from the addressbook, sent invitations to them and receive their answers.
Prerequisites: any version of Kontact, preferably a current one and either some accounts at a free mail provider or other means to send and receive mails with different email addresses.
Time to complete: 2 days
Mentor: Kevin Krammer <[email protected]>
Commit Digest: review 100 commits
Description: Commit-Digest is a weekly review of the KDE developer activity. The task is to review 100 commits and decide if they should be included in the weekly digest. You can find the guidelines here: http://community.kde.org/Commit_Digest/Guidelines
Expected results: 100 correctly reviewed commits in the Enzyme system http://enzyme.commit-digest.org/
Prerequisites: an account in Enzyme, ask for it in advance.
Time to complete: 2 days
Mentor: Marta Rybczynska <[email protected]>
Commit Digest: classify 50 commits
Description: Commit-Digest is a weekly review of the KDE developer activity. The task is to classify 50 reviewed commits into one of pre-defined categories. You can find the guidelines here: http://community.kde.org/Commit_Digest/Guidelines
Expected results: 50 correctly classified commits in the Enzyme system http://enzyme.commit-digest.org/
Prerequisites: an account in Enzyme, ask for it in advance.
Time to complete: 2 days
Mentor: Marta Rybczynska <[email protected]>
Kst: set-up dedicated forum on forum.kde.org
Description: the Kst plotting tool currently offers only a developer-oriented mailing list and there have been requests to have a specific forum on forum.kde.org. It could even be a joint plotting forum with areas for kig, Kst, labplot, etc...
Expected results: operational Kst forum on forum.kde.org
Prerequisites: an account on forum.kde.org and contacts to the forum admins.
Time to complete: 2 days
Mentor: Nicolas Brisset <[email protected], Kst mailing list>
medium
Marble: Create a nice blog entry about your favorite Marble feature
Description:
Marble has lots of nice features. Have a look at it and create a nice blog entry that goes into details describing your favorite feature. The blog entry should have at least 3 screenshots, should have about 500+ words and should encourage people to use Marble. You can write it either in your own language or in English. For a successful completion you need to have your blog appear on planet.kde.org and you need to publish your blog there.
Suggested topics: Recent features that have been added (OSM Vector support, Marble Touch, Satellite View, etc.)
Expected results: A blog entry about your favorite Marble feature that appears on planet.kde.org.
Prerequisites: Knowledge about how to write a blog entry / Knowledge about Marble
Time to complete: 72h
Mentor: [email protected]
Video ad for KDE - Emotions
Description:
Use all your creativity to create an innovating short film promoting KDE. We are looking for an advertisement with new ideas that communicates the spirit behind KDE.
Must show KDE on different platforms. Creativity is very important.
Your video must convey a KDE feeling and obey to KDE quality standards.
Quality has to be at least 720p, real action, animation or stop-motion. No screen-cast, only video and no 3D animation video are allowed.
Every video, sound and image used must be GPL 3.0 or Creative Commons BY-SA. The video license will be GPL 3.0 or Creative commons BY-SA. The work will have a text file with the following information: - License - Authors - Actors - Technical staff - Score
Expected results: An ad (less than 2 minutes) promoting KDE.
Prerequisites: Script.
Time to complete: 168h
Mentor: Claudio Desideri (happy dot snizzo at gmail dot com)
Video ad for KDE - KDE Everywhere
Description:
Use all your creativity to create an innovating short film promoting KDE. We are looking for an advertise with new ideas that communicate the spirit behind KDE.
Must verse KDE in different platforms. Creativity is very important.
Your video must have a KDE feeling (lettering, imagery, etc.). Must be according to KDE quality standards.
Quality has to be at least 720p, real action, animation or stop-motion. No screen-cast only video and no 3D animation video are allowed.
Every video, sound and image used must be GPL 3.0 or Creative Commons BY-SA. The video license will be GPL 3.0 or Creative commons BY-SA. The work will have a text file with the following information: - License - Authors - Actors - Technical staff - Score
Expected results: An ad (less than 2 minutes) promoting KDE.
Prerequisites: Script.
Time to complete: 168h
Mentor: Jorge Salgueiro (jorge dot salgueiro at gmail dot com)
Research: Enriching KDE News content
Description: KDE has a news site at dot.kde.org known as "The Dot". The Dot has a few regular features such as weekly reports of development activities and release announcements. Even in these situations, Dot editors depend on other people submitting stories rather than proactively seeking out KDE news of interest.
This project involves:
- In general, enabling KDE Dot editors to proactively recruit stories of interest to the KDE Community
- Identifying KDE newsmakers by researching blogs and other on-line channels
- Contacting KDE newsmakers and influencers for general story ideas--topics, people, projects,
- Making recommendations for stories, including the above and timing or frequency (for example, a story about a main KDE project every week; a profile on a key contributor monthly).
This project is intended to generate story ideas and methods for completing them; it may also involve writing story drafts if a subject seems to warrant that.
Expected results: A written list of at least ten subjects and contacts that would result in Dot stories on a continuing basis.
Time to complete: 40h
Mentor: Carl Symons ([email protected])
hard
Create a nice suggestion for a Wikpedia article for Marble in your own native language
Description:
Marble is covered in Wikipedia in several languages. See
http://de.wikipedia.org/wiki/Marble_%28Computerprogramm%29
http://en.wikipedia.org/wiki/Marble_%28software%29
http://it.wikipedia.org/wiki/Marble_%28KDE%29
However taking Marble's significance into account and comparing it to other Wikipedia articles like:
http://en.wikipedia.org/wiki/Google_Earth
http://en.wikipedia.org/wiki/NASA_World_Wind
.. the Marble Wikipedia article has room for lots of improvements. In fact Marble does already provide much of the feature set provided by Google Earth and NASA World Wind, see the feature matrix here:
http://en.wikipedia.org/wiki/Virtual_Globe
Create a suggestion for a Marble Wikipedia article in your own language. This might be an article in a language that is not yet covered or an article that has major improvements over the current version in your language. The article should adhere to Wikipedia principles.
Expected results: A high quality wikipedia article that is in line with Wikipedia rules and principles.
Prerequisites: A good understanding of Technical Writing and knowledge about Marble.
Time to complete: 120h
Mentor: [email protected]
Video ad for KDE - Join The Game
Description:
Join the Game - create a video ad for the "Join The Game" campaign to reach new supporting members for KDE e.V. (the non-profit organisation that supports the KDE community).
The video should promote the idea and look and feel of the Join the Game campagne, see http://jointhegame.kde.org/ for more. The video should be according to KDE quality standards.
Quality has to be at least 720p, real action, animation or stop-motion. No screen-cast only video and no 3D animation video are allowed.
Every video, sound and image used must be GPL 3.0 or Creative Commons BY-SA. The video license will be GPL 3.0 or Creative commons BY-SA. The work will have a text file with the following information: - License - Authors - Actors - Technical staff - Score
Expected results: An ad (less than 2 minutes) promoting KDE. Prerequisites: Script. Time to complete: 168h
Mentors: Claudio Desideri (happy dot snizzo at gmail dot com) and Claudia Rauch, [email protected]
Video ad for KDE - Experience Freedom
Description:
Use all your creativity to create an innovating short film promoting KDE. We are looking for an advertise with new ideas that communicate the spirit behind KDE.
Must verse KDE in different platforms. Creativity is very important.
Your video must have a KDE feeling (lettering, imagery, etc.). Must be according to KDE quality standards.
Quality has to be at least 720p, real action, animation or stop-motion. No screen-cast only video and no 3D animation video are allowed.
Every video, sound and image used must be GPL 3.0 or Creative Commons BY-SA. The video license will be GPL 3.0 or Creative commons BY-SA. The work will have a text file with the following information: - License - Authors - Actors - Technical staff - Score
Expected results: An ad (less than 2 minutes) promoting KDE.
Prerequisites: Script.
Time to complete: 168h
Mentor: Claudio Desideri (happy dot snizzo at gmail dot com)
Video ad for KDE - Love
Description:
Use all your creativity to create an innovating short film promoting KDE. We are looking for an advertise with new ideas that communicate the spirit behind KDE.
Must verse KDE in different platforms. Creativity is very important.
Your video must have a KDE feeling (lettering, imagery, etc.). Must be according to KDE quality standards.
Quality has to be at least 720p, real action, animation or stop-motion. No screen-cast only video and no 3D animation video are allowed.
Every video, sound and image used must be GPL 3.0 or Creative Commons BY-SA. The video license will be GPL 3.0 or Creative commons BY-SA. The work will have a text file with the following information: - License - Authors - Actors - Technical staff - Score
Expected results: An ad (less than 2 minutes) promoting KDE.
Prerequisites: Script.
Time to complete: 168h
Mentor: Claudio Desideri (happy dot snizzo at gmail dot com)
Video ad for KDE - Plasma Active
Description:
Use all your creativity to create an innovating short film promoting KDE. We are looking for an advertise with new ideas that communicate the spirit behind KDE.
Must verse Plasma Active. Creativity is very important.
Your video must have a Kde feeling (lettering, imagery, etc.). Must be according to Kde quality standards.
Quality has to be at least 720p, real action, animation or stop-motion. No screen-cast only video and no 3D animation video are allowed.
Every video, sound and image used must be GPL 3.0 or Creative Commons BY-SA. The video license will be GPL 3.0 or Creative commons BY-SA. The work will have a text file with the following information: - License - Authors - Actors - Technical staff - Score
Expected results: An ad (less than 2 minutes) promoting KDE Plasma Active.
Prerequisites: Script.
Time to complete: 168h
Mentor: Jorge Salgueiro (jorge dot salgueiro at gmail dot com)
Video ad for KDE - Coming together
Description:
Use all your creativity to create an innovating short film promoting KDE. We are looking for an advertise with new ideas that communicate the spirit behind KDE.
Must verse KDE Community. Creativity is very important.
Your video must have a KDE feeling (lettering, imagery, etc.). Must be according to KDE quality standards.
Quality has to be at least 720p, real action, animation or stop-motion. No screen-cast only video and no 3D animation video are allowed.
Every video, sound and image used must be GPL 3.0 or Creative Commons BY-SA. The video license will be GPL 3.0 or Creative commons BY-SA. The work will have a text file with the following information: - License - Authors - Actors - Technical staff - Score
Expected results: An ad (less than 2 minutes) promoting KDE Community.
Prerequisites: Script.
Time to complete: 168h
Mentor: Jorge Salgueiro (jorge dot salgueiro at gmail dot com)
Research: Understanding KDE Users (Individuals)
Description: KDE users number in the millions. However, aside from general information, not much is known about them. With better intelligence, the KDE community could be more effective at reaching and serving KDE users and potential users.
KDE outreach efforts are stymied by the lack of direct contact with users. Typically, KDE technology is included seamlessly in downstream Linux distributions such as Kubuntu, openSUSE and many more. It is also available as an option for most Linux and similar operating systems.
This project involves:
- planning for the project
- understanding and documenting pertinent background information,
- the possibility of working with KDE development teams,
- Creating research goals (what information should be gathered, how will it be used, what would be helpful to know),
- exploring and analyzing research methods, and
- determining the effectiveness of various research methods.
This project is intended to produce well-reasoned recommendations; it does not involve doing the actual research.
Expected results: At least five suggestions of methods for gathering pertinent, actionable information, including pros and cons, rationale, recommendations.
Time to complete: 120h
Mentor: Carl Symons (carl dot symons at gmail dot com)
Research: Understanding KDE Users (Organizations)
Description: KDE technology is used within companies and other organizations. In some cases, individual users have the ability to choose their computer operating environments; in others, this is an organizational decision. Beyond this general information, not much is known about the use of KDE in organizational settings. With better intelligence, the KDE community could be more effective at working with organizations and the users in them. In addition, developing closer relationships with organizations could be useful for gaining financial support for KDE operations.
KDE outreach efforts are stymied by the lack of direct contact with users. Typically, KDE technology is included seamlessly in downstream Linux distributions such as Kubuntu, openSUSE and many more. It is also available as an option for most Linux and similar operating systems. Currently, there is no reliable way to know about KDE use in organizations, even if KDE is a key part of a widespread Linux deployment.
This project involves:
- planning for the project
- understanding and documenting pertinent background information,
- the possibility of working with KDE development teams,
- creating research goals (what information should be gathered and how will it be used),
- exploring and analyzing research methods, and
- determining the effectiveness of various research methods.
This project is intended to produce well-reasoned recommendations; it does not involve doing the actual research.
Expected results: At least five suggestions of methods for gathering pertinent, actionable information, including pros and cons, rationale, recommendations.
Time to complete: 120h
Mentor: Carl Symons (carl dot symons at gmail dot com)
Quality Assurance
easy
Bug triaging: searching for duplicates (approx. 20x)
Description: Many KDE bug reports need to be triaged (checked) before they can be forwarded to the developers. The task consists in selecting individual KDE projects and check the database for duplicate entries.
Expected results: have a better triaged bug database to facilitate the developer's work.
Prerequisites: Having good analytical skills, having read and understood the triaging Guide: http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging
Time to complete:48 hours.
Mentor: [email protected], kde-bugsquad, coordination in #kde-bugs
Gluon: Unit tests for Gluon Audio
Description: Gluon, and in this special case Gluon Audio, needs unit tests for quality assurance. It will be very important because of a potential backend replacement, but at least extension from a project called "alure" to QtOpenAL, For the smooth transient, it will aid a lot if we can always test the previously working functionalities for regressions.
Prerequisites: Basic Qt, Audio, QtTest
Time to complete: about 2-5 days depending on the ability and effort of the student.
Mentor: Laszlo Papp <[email protected]>
KMail: check if old KMail 1 bugs/wishes are valid for KMail 2 (approx. 20x for bugs or 40x for wishes)
Description: There are lots of open bugreports and wishes for KMail 1 which is out of maintenance. These bugreports and wishes have to be checked. If they are still valid for KMail 2, the "product" field in bugzilla should be changed to KMail 2. Bugs and wishes that are no longer valid (for example because they have been implemented/fixed) should be closed.
Note: coordinate with the KMail developers to get write access to the KMail 1 bugreports.
Prerequisites: A system with latest KDE and KMail installed. Having used KMail before is an advantage.
Time to complete: 1 day
Mentor:
medium
Amarok: Unit tests for Amazon store
Description: The Amazon store needs unit tests for quality assurance. Especially the parser and meta object creation. Maybe also the collection. We already have unit tests for other areas as inspiration.
Prerequisites: Basic Qt, QtTest
Time to complete: about a day if you already know QtTest, maybe two if you don't
Mentor: Sven Krohlas <[email protected]>
Unit tests for KDE-Telepathy Contact List
Description: Contact List should have some unit tests for QA.
Prerequisites: Qt, QtTest
Time to complete: probably 3-5 days
Mentor: Martin Klapetek <[email protected]>
hard
Write some backend QA tests
Description: Its easy to test libphonon. Write a dummy backend and throw it all into some unit tests. Its a lot harder to test pgst or pvlc since they aren't exactly suitably designed for unit testing. We would like to have a basic checklist of test situations to run through before a release to make sure all the kinks are found and regressions don't occur. Examples:
- Open dragon, play a .wav, close dragon.
- Open dragon, play a .wav, play the same .wav again, close dragon.
- Open dragon, queue up three .avis, play them, close dragon.
- Play a DVD and navigate the menus to enable subtitles
Sounds very tedious to try and cover all the bases, but doing so can help teach a *lot* about multimedia software development.
Expected results: Have a nice list of things to test that you can't just stuff in a bunch of unit tests. At least 5 or so scripts produced per student, with multiple students creating different lists independently.
Prerequisites: Patience, a careful eye, and a willingness to learn the basics of the libphonon API. Maybe some familiarity with basic combinatorics.
Time to complete: 2 days
Mentor: Trever Fischer <[email protected]>, coordination in #kde-multimedia with the other phonon developers, apachelogger and bambee.
Research
easy
KDE3 Documentation Update Listing
Description: Create a list of pages on KDE's Techbase that are describing KDE3
Expected results: A list of all the pages on Techbase with categorization of topics that are covered. If the page is deemed to be trivial to update to KDE4 then some attempt should be made to facilitate that.
Prerequisites: Knowledge of Wiki Use, Communication.
Time to complete: 48 hours
Mentor: skreech2 at gmail dot come
KDE Multimedia Census
Description: With the recent(ish) rejuvenation of the KDE-MM community, its probably a good time to step back and have a look at what exactly our community is made of. Some simple statistics would be needed, in order of importance:
- What projects consider themselves to be part of kde-mm
- The number of developers on each project, to identify projects in need of help
- Some background history on some of the developers, so the community can get to know everyone
- Feedback and suggestions on what "kde multimedia" really means
- Anything else the minion comes up with ;P
Expected results: Answers to the above questions, silly. At the very least, a better list of questions so that we can perform the census ourselves.
Prerequisites: People skills, basic understanding of simple statistics.
Time to complete: 3 days
Mentor: Trever Fischer <[email protected]>, coordination in #kde-multimedia and the [email protected] list.
Research Akademy 2012 visitor information
Description: The annual KDE community conference Akademy takes place in a different city and country every year. To make it easier for the Akademy attendees to find their way around the city where Akademy 2012 will take place, we will provide various tips and information on the Akademy website.
Your task would be to do online research and edit the following details, so that we can publish them on the Akademy 2012 website:
- description of transport options and travel recommendation for the Akademy 2012 city
- a list of restaurants and cafes with addresses and price range, including options for vegetarians and vegans
- a list of recommended sights in the Akademy 2012 city
You can find examples for past events here:
- http://akademy2010.kde.org/travel
- http://wiki.desktopsummit.org/Getting_around
- http://akademy2010.kde.org/goingout
- http://wiki.desktopsummit.org/Food#Restaurants_and_cafes_close_to_conference_venue
Expected results: see description :)
Time to complete: 10-15 hours
Mentor: Claudia Rauch, [email protected]
medium
Amarok: Likeback statistics and report
Description: Amarok uses the Likeback feedback gathering system in beta releases and git builds. 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.
Time to complete: 3 days.
Mentor: Teo Mrnjavac <[email protected]>
Accumulate Transparency issues in okular
Description: There are some problems with transparency in okular. A problem was on selection of text in odt files. A very basic solution was made, which is better than prior but not satisfactory at all. It would be nice to know the transparency issues, as many as possible to collect. The student is needed to give a report in which cases this kind of transparency problems arises.
Expected results: A thorough report, maybe in PDF or doc format.
Prerequisites: basic writing skills and patience.
Time to complete: 2-3 days.
Mentor: Mohammad Mahfuzur Rahman <[email protected]>
Pairs Touch-Friendly Interface
Description: Right now Pairs is working great on the desktop but we want to look further and make it work on touch devices. We need an interface written in QtQuick that doesn't make use of the menus, toolbars and status bar and puts everything in a canvas, in a pretty way. Also it shouldn't have the new game dialog, this should be on the canvas as well.
Expected results: Make it possible to have an interface to be ported to Pairs, that can be used easily on a touch device, like a tablet.
Prerequisites: QtQuick, UI Design
Time to complete: 1 week
Mentor: Aleix Pol <[email protected]>
hard
New KAlgebra Mobile tool
Description: If you try the KAlgebra Mobile you'll see the feature set is smaller than the Desktop's version. The possibility to create new tools opens new possibilities that we still need to explore.
Expected results: Provide a QtQuick mockup of the tool you'd like to have in your calculator when you're at class or while doing framework. It doesn't need to work, but if it doesn't it needs to specify what should every bit of the UI do.
Prerequisites: QtQuick knowledge, ideas about applied mathematics
Time to complete: 1 week
Mentor: Aleix Pol <[email protected]>
KAlgebra Mobile on the Desktop
Description: Right now the KAlgebra Mobile version for desktop is quite ugly and useless. Provide a mockup of a better workflow.
Expected results: A version that can actually be used on the desktop and possibly replace the regular KAlgebra in the future.
Prerequisites: QtQuick knowledge, UI design
Time to complete: 4 days
Mentor: Aleix Pol <[email protected]>
Training
easy
Import KWin Scripting Tutorial into KDE Examples
Description: There is one tutorial for KWin scripting written by the developer. This should be imported into a new kwin scripting module in the KDE Examples git repository.
Expected results: Existing KWin Scripting Tutorial in kde-examples repository.
Prerequisites: basic git knowledge
Time to complete: 24 hours
Mentor: [email protected]
Recover files for Akonadi Resource tutorial
Description: The files used for the Akonadi Resource tutorial have been lost due to a failed backup. The task is to work through the tutorial and reconstruct all necessary files in the process.
Expected results: An archive (e.g. tar.gz, zip) of all the files necessary to build and run the resource described in the tutorial.
Prerequisites: Devleopment packages for kdelibs and kdepimlibs and a recent version of KAppTemplate or KDevelop.
Time to complete: 1 day
Mentor: Kevin Krammer <[email protected]>
Recover files for Akonadi Application tutorial
Description: The files used for the Akonadi Application tutorial have been lost due to a failed backup. The task is to work through the tutorial and reconstruct all necessary files in the process.
Expected results: An archive (e.g. tar.gz, zip) of all the files necessary to build and run the application described in the tutorial.
Prerequisites: Devleopment packages for kdelibs and kdepimlibs and a recent version of KAppTemplate or KDevelop.
Time to complete: 1 day
Mentor: Kevin Krammer <[email protected]>
medium
Phonon Demos!
Description: More phonon demos! Right now, we have a simpleplayer demo with a very simple UI that plays a file. Simply. Some other things that should be done include demonstrating how to handle DVD menus, audio effects, etc. One significant improvement would be some non-graphical demos. Thinking along the lines of a command line metadata extractor or audio player.
Expected results: More phonon demos!
Prerequisites: C++ and libphonon knowledge.
Time to complete: 2 days
Mentor: The Phonominals of #kde-multimedia, maybe tdfischer.
Example KWin Script
Description: An example KWin script should be implemented and added to the kde-examples repository. The script could make a window follow the active desktop, so that it is always on the active desktop but not set on all desktops. This could be useful for e.g. a chat client and is a feature provided by other window managers.
Expected results: Example KWin Script implemented
Prerequisites: JavaScript knowledge
Time to complete: 48 hours
Mentor: [email protected]
hard
Create solutions for the exercises of the Akonadi Resource tutorial
Description: The Akonadi Resource tutorial contains several exercise sections for more advanced resource functionality. The task is to solve at least three of them, document the solutions on a separate Wiki page and link the solutions from the respective exercise.
Expected results: An archive (e.g. tar.gz, zip) of all the files necessary to build and run the resource with the exercises' solutions and a Wiki page documenting the necessary steps for each solution.
Prerequisites: Devleopment packages for kdelibs and kdepimlibs and a recent version of KAppTemplate or KDevelop.
Time to complete: 1 week
Mentor: Kevin Krammer <[email protected]>
Hint: most described problems have already been solved for other resources available as part of kdepim-runtime
Translation
easy
Screenshots for Ukrainian documentation of Kig
Description: Update and complete Ukrainian screenshots for Kig documentation
Expected results: Complete set of 15 screenshots, synced with English originals.
Prerequisites: moderate knowledge of geometry, basic skills in screenshoting, current stable version of Kig
Time to complete: 24 hrs
Mentor: Yuri Chornoivan [email protected]
Translate strings in a Python Kig script from Italian to English
Description: Download and edit the following script https://projects.kde.org/projects/kde/kdeedu/kig/repository/revisions/master/changes/pykig/pykig.py and translate all Italian strings to very good English ones without altering any markup of the script.
Expected results: All Italian strings are translated to English in this script
Prerequisites: Italian and English excellent speakers and writers, preferred Kig knowledge (install Kig and use it a bit)
Time to complete: 48 hrs
Mentor: Anne-Marie Mahfouf [email protected]
Documentation translation (Polish): Update kinfocenter documentation
Description: Update documentation of the kinfocenter program, ~100 messages.
Expected results: All strings are translated and it builds correctly.
Prerequisites: Basic knowledge of shell to be able to run commands that build the documentation (will provide guidelines)
Time to complete: 48h
Mentor: Marta Rybczynska ([email protected])
Documentation translation (Polish): Update glossary documentation
Description: Update documentation of KDE glossary, approx 150 messages.
Expected results: All strings are translated and it builds correctly.
Prerequisites: Basic knowledge of shell to be able to run commands that build the documentation (will provide guidelines)
Time to complete: 48h
Mentor: Marta Rybczynska ([email protected])
Documentation translation (Polish): Update kdegraphics documentation
Description: Update documentation of the kdegraphics package: gwenview, kolourpaint, kruler, ksnapshot, okular. Approx 200 messages.
Expected results: All strings are translated and it builds correctly.
Prerequisites: Basic knowledge of shell to be able to run commands that build the documentation (will provide guidelines), basic knowledge of the programs
Time to complete: 4 days
Mentor: Marta Rybczynska ([email protected])
Documentation translation (Polish): Update Amarok QuickStartGuide on Userbase
Description: Update Amarok QuickStartGuide on userbase (pages Amarok/QuickStartGuide)
Expected results: All pages are fully translated.
Prerequisites: Basic knowledge of amarok, userbase account
Time to complete: 48h
Mentor: Marta Rybczynska ([email protected])
Update KLettres screenshots (French)
Description: Update KLettres French documentation screenshots. In a default KDE installation, use KSnapshot to do all the 9 screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/klettres/repository/revisions/master/show/doc (all .png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php
Expected results: The 9 screenshots in French interface are up-to-date with current KLettres interface and current KDE default style and default window decoration.
Prerequisites: KLettres installed with French interface, KSnapshot
Time to complete: 24h
Mentor: Anne-Marie Mahfouf ([email protected])
Update Blinken screenshots (French)
Description: Update Blinken French documentation screenshots (8). In a default KDE installation, use KSnapshot to do all the 8 screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/blinken/repository/revisions/master/show/doc (all .png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php
Expected results: The 8 screenshots in French interface are up-to-date with current Blinken interface and current KDE default style and default window decoration.
Prerequisites: Blinken installed with French interface, KSnapshot
Time to complete: 24h
Mentor: Anne-Marie Mahfouf ([email protected])
Update KHangMan screenshots (French)
Description: Update KHangMan French documentation screenshots. In a default KDE installation, use KSnapshot to do all the 9 screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/khangman/repository/revisions/master/show/doc (all .png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php
Expected results: The 9 screenshots in French interface are up-to-date with current KHangMan interface and current KDE default style and default window decoration.
Prerequisites: KHangMan installed with French interface, KSnapshot
Time to complete: 24h
Mentor: Anne-Marie Mahfouf ([email protected])
Make Kanagram screenshots (French)
Description: Update Kanagram French documentation screenshots (10). In a default KDE installation, use KSnapshot to do all the 10 screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/kanagram/repository/revisions/master/show/doc (all .png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php
Expected results: The 10 screenshots in French interface are up-to-date with current Kanagram interface and current KDE default style and default window decoration.
Prerequisites: Kanagram installed with French interface, KSnapshot
Time to complete: 24h
Mentor: Anne-Marie Mahfouf ([email protected])
Update KTouch screenshots (French)
Description: Update KTouch French documentation screenshots. In a default KDE installation, use KSnapshot to do all the 9 screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/ktouch/repository/revisions/master/show/doc (all .png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php
Expected results: The 9 screenshots in French interface are up-to-date with current KTouch interface and current KDE default style and default window decoration.
Prerequisites: KTouch installed with French interface, KSnapshot
Time to complete: 24h
Mentor: Anne-Marie Mahfouf ([email protected])
Update KBruch screenshots (French)
Description: Update KBruch French documentation screenshots(12). In a default KDE installation, use KSnapshot to do all the 12 screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/kbruch/repository/revisions/master/show/doc (all .png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php
Expected results: The 12 screenshots in French interface are up-to-date with current KBruch interface and current KDE default style and default window decoration.
Prerequisites: KBruch installed with French interface, KSnapshot
Time to complete: 24h
Mentor: Anne-Marie Mahfouf ([email protected])
Make Step screenshots (French)
Description: Make Step French documentation screenshots (8). In a default KDE installation, use KSnapshot to do all the 8 screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/step/repository/revisions/master/show/doc (all .png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php
Expected results: The 8 screenshots in French interface are up-to-date with current Step interface and current KDE default style and default window decoration.
Prerequisites: Step installed with French interface, KSnapshot
Time to complete: 24h
Mentor: Anne-Marie Mahfouf ([email protected])
Make KmPlot screenshots (French)
Description: Make KmPlot French documentation screenshots (14). In a default KDE installation, use KSnapshot to do all the 14 screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/kmplot/repository/revisions/master/show/doc (all .png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php
Expected results: The 14 screenshots in French interface are up-to-date with current KmPlot interface and current KDE default style and default window decoration.
Prerequisites: KmPlot installed with French interface, KSnapshot
Time to complete: 48h
Mentor: Anne-Marie Mahfouf ([email protected])
Make Marble screenshots (French)
Description: Update Marble French documentation screenshots (20). In a default KDE installation, use KSnapshot to do all the screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/marble/repository/revisions/master/show/doc. Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php. Some screenshots are existing but in an outdated window decoration here http://websvn.kde.org/trunk/l10n-kde4/fr/docs/kdeedu/marble/ and they all need to be redone.
Expected results: The 20 screenshots in French interface are up-to-date with current Marble interface and current KDE default style and default window decoration.
Prerequisites: Marble installed with French interface, KSnapshot, Marble knowledge
Time to complete: 72h
Mentor: Anne-Marie Mahfouf ([email protected])
Make Kig screenshots (French)
Description: Update Kig French documentation screenshots (15). In a default KDE installation, use KSnapshot to do all the screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/kig/repository/revisions/master/show/doc (.png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php.
Expected results: The 15 screenshots in French interface are up-to-date with current Kig interface and current KDE default style and default window decoration.
Prerequisites: Kig installed with French interface, KSnapshot
Time to complete: 48h
Mentor: Anne-Marie Mahfouf ([email protected])
Make KWordQuiz screenshots (French)
Description: Make KWordQuiz French documentation screenshots (21). In a default KDE installation, use KSnapshot to do all the screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/kwordquiz/repository/revisions/master/show/doc (.png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php.
Expected results: The 21 screenshots in French interface are up-to-date with current Kalzium interface and current KDE default style and default window decoration.
Prerequisites: KWordQuiz installed with French interface, KSnapshot
Time to complete: 48h
Mentor: Anne-Marie Mahfouf ([email protected])
Make Kalzium screenshots (French)
Description: Make Kalzium French documentation screenshots (33). In a default KDE installation, use KSnapshot to do all the screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/kalzium/repository/revisions/master/show/doc (.png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php.
Expected results: The 21 screenshots in French interface are up-to-date with current Kalzium interface and current KDE default style and default window decoration.
Prerequisites: Kalzium installed with French interface, KSnapshot, Kalzium knowledge
Time to complete: 48h
Mentor: Anne-Marie Mahfouf ([email protected])
Make KStars screenshots (French)
Description: Make KWordQuiz French documentation screenshots (46). In a default KDE installation, use KSnapshot to do all the screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/kstars/repository/revisions/master/show/doc (.png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php.
Expected results: The 46 screenshots in French interface are up-to-date with current KStars interface and current KDE default style and default window decoration.
Prerequisites: KStars installed with French interface, KSnapshot
Time to complete: 72h
Mentor: Anne-Marie Mahfouf ([email protected])
Make Parley screenshots (French)
Description: Make Parley French documentation screenshots (71). In a default KDE installation, use KSnapshot to do all the screenshots to match the English ones from https://projects.kde.org/projects/kde/kdeedu/parley/repository/revisions/master/show/doc (.png files). Instructions about screenshots: http://l10n.kde.org/docs/screenshots.php.
Expected results: The 71 screenshots in French interface are up-to-date with current Parley interface and current KDE default style and default window decoration.
Prerequisites: Parley installed with French interface, KSnapshot
Time to complete: 1 week
Mentor: Anne-Marie Mahfouf ([email protected])
Documentation translation (French): Translate KImageMapEditor documentation + 2 screenshots
Description: Translate KImageMapEditor User Manual http://websvn.kde.org/*checkout*/trunk/l10n-kde4/templates/docmessages/kdewebdev/kimagemapeditor.pot to French using Lokalize (39 strings) and make the screenshots in French interface based on the English one http://websvn.kde.org/trunk/KDE/kdewebdev/doc/kimagemapeditor/ (2 screenshots)
Expected results: The .po fully translated to French + the 2 screenshots.
Prerequisites: Basic knowledge of Kiten, knowledge of Japanese, Lokalize and KSnapshot
Time to complete: 1 days
Mentor: Anne-Marie Mahfouf ([email protected])
Complete Russian translation of Kalzium interface
Description: Complete Russian translation for Kalzium
Expected results: Full translation of Kalzium interface (317 messages) into Russian (should be tested on current unstable of Kalzium).
Prerequisites: Good Russian, basic chemistry knowledge.
Time to complete: 5 days
Mentor: Yuri Chornoivan [email protected]
Add context information to Gluon code where it's missing
Description: As the title implies, the messages in code are already translated, but in places require context to be added. The context is a description of what the message is supposed to convey in the user interface, and is used by the translators.
Expected results: Context added to all translated messages in the code
Prerequisites: Good English skills, code knowledge not required (only need to know how to find text in multiple files)
Time to complete: 2 days
Mentor: Dan Leinir Turthra Jensen <[email protected]> and Arjen Hiemstra <[email protected]>
Finnish translation of some Extragear_sysadmin files
Description: Translate message id strings from English into Finnish (desktop_extragear-sysadmin_libqapt.pot, 6 short messages), (plasma-runner-installer.pot, 3 short messages), (qapt-deb-installer.pot, 37 short messages), and (qapt-gst-helper.pot, 53 short messages).
Expected results: All msgid strings translated into msgstr strings. Rename desktop_extragear-sysadmin_libqapt.pot to desktop_extragear-sysadmin_libqapt.po, plasma-runner-installer.pot to plasma-runner-installer.po, qapt-deb-installer.pot to qapt-deb-installer.po, and qapt-gst-helper.pot to qapt-gst-helper.po. Edit and update the header fields at the beginning of the file.
Prerequisites: Good Finnish
Time to complete: 4 days.
Mentor: Jorma Karvonen [email protected]
medium
Finnish translation of KAddressbook for the mobile devices
Description: Translate message id strings from English into Finnish (kaddressbook-mobile.pot, 196 short messages)
Expected results: All msgid strings translated into msgstr strings. Rename kaddressbook-mobile.pot to kaddressbook-mobile.po. Edit and update the header fields at the beginning of the file.
Prerequisites: Good Finnish
Time to complete: 5 days.
Mentor: Jorma Karvonen [email protected]
Finnish translation of Plasma Gas and Concentration Calculators
Description: Translate message id strings from English into Finnish (plasma_applet_concentrationCalculator.pot, 68 short messages) and (plasma_applet_gasCalculator.pot, 49 short messages)
Expected results: All msgid strings translated into msgstr strings. Rename plasma_applet_concentrationCalculator.pot to plasma_applet_concentrationCalculator.po and plasma_applet_gasCalculator.pot to plasma_applet_gasCalculator.po. Edit and update the header fields at the beginning of the files.
Prerequisites: Good Finnish, some knowledge of physics.
Time to complete: 4 days.
Mentor: Jorma Karvonen [email protected]
Finnish translation of Step Physics Simulation Engine
Description: Tranlate message id strings from English into Finnish (step.pot, 225 short messages)
Expected results: All msgid strings translated into msgstr strings. Rename step.pot to step.po. Edit and update the header fields at the beginning of the file.
Prerequisites: Good Finnish, some knowledge of physics.
Time to complete: 5 days.
Mentor: Jorma Karvonen [email protected]
Finnish translation of Cantor Worksheet Interface for the Mathematical applications
Description: Translate message id strings from English into Finnish (cantor.pot, 210 short messages)
Expected results: All msgid strings translated into msgstr strings. Rename cantor.pot to cantor.po. Edit and update the header fields at the beginning of the file.
Prerequisites: Good Finnish, some knowledge of mathematics.
Time to complete: 4 days.
Mentor: Jorma Karvonen [email protected]
Russian translation of Calligra Flow stencils
Description: Complete Russian translation of Calligra Flow stencils (desktop_calligra.po, ~1160 short messages)
Expected results: All stencils descriptions should be translated according to KDE Russian Team guidelines without typos, the result should be checked against stencil images from the Flow/Dia repository.
Prerequisites: Good Russian, basic knowledge of physics and computer science.
Time to complete: 168 hrs.
Mentor: Yuri Efremov [email protected]
New Ukrainian sound files for KTuberling
Description: Update and complete Ukrainian sound files for KTuberling
Expected results: New sound files of good quality (should be tested on current stable of KTuberling). Sample list can be found here.
Prerequisites: Microphone, basic skills in audio editor
Time to complete: 72 hrs
Mentor: Yuri Chornoivan [email protected]
Documentation translation (Polish): Translate Amarok Manual on Userbase
Description: Translate Amarok Manula on userbase (pages Amarok/Manual)
Expected results: All pages are fully translated.
Prerequisites: Basic knowledge of amarok, userbase account
Time to complete: 7 days
Mentor: Marta Rybczynska ([email protected])
Documentation translation (French): Translate Granatier documentation + screenshots
Description: Translate Granatier User Manual http://websvn.kde.org/*checkout*/trunk/l10n-kde4/templates/docmessages/kdegames/granatier.pot to French using Lokalize and make the screenshots in French interface based on the English ones http://websvn.kde.org/trunk/KDE/kdegames/doc/granatier/
Expected results: The .po fully translated to French + the screenshots.
Prerequisites: Basic knowledge of Granatier, knowledge of Lokalize and KSnapshot
Time to complete: 2 days
Mentor: Anne-Marie Mahfouf ([email protected])
Documentation translation (French): Translate Kigo documentation + screenshots
Description: Translate Granatier User Manual http://websvn.kde.org/*checkout*/trunk/l10n-kde4/templates/docmessages/kdegames/kigo.pot to French using Lokalize (133 strings) and make the screenshots in French interface based on the English ones http://websvn.kde.org/trunk/KDE/kdegames/doc/kigo/ (7 screenshots)
Expected results: The .po fully translated to French + the 7 screenshots.
Prerequisites: Basic knowledge of Kigo, knowledge of Lokalize and KSnapshot
Time to complete: 3 days
Mentor: Anne-Marie Mahfouf ([email protected])
Documentation translation (French): Translate Klickety documentation + screenshots
Description: Translate Klickety User Manual http://websvn.kde.org/*checkout*/trunk/l10n-kde4/templates/docmessages/kdegames/klickety.pot to French using Lokalize (172 strings) and make the screenshots in French interface based on the English ones http://websvn.kde.org/trunk/KDE/kdegames/doc/klickety/ (9 screenshots)
Expected results: The .po fully translated to French + the 9 screenshots.
Prerequisites: Basic knowledge of Klickety, knowledge of Lokalize and KSnapshot
Time to complete: 3 days
Mentor: Anne-Marie Mahfouf ([email protected])
Documentation translation (French): Translate Palapeli documentation + 1 screenshot
Description: Translate Palapeli User Manual http://websvn.kde.org/*checkout*/trunk/l10n-kde4/templates/docmessages/kdegames/palapeli.pot to French using Lokalize (143 strings) and make the screenshot in French interface based on the English one http://websvn.kde.org/trunk/KDE/kdegames/doc/palapeli/ (1 screenshot)
Expected results: The .po fully translated to French + the screenshot.
Prerequisites: Basic knowledge of Palapeli, knowledge of Lokalize and KSnapshot
Time to complete: 3 days
Mentor: Anne-Marie Mahfouf ([email protected])
Documentation translation (French): Translate KFileReplace documentation + 9 screenshots
Description: Translate KFileReplace User Manual http://websvn.kde.org/*checkout*/trunk/l10n-kde4/templates/docmessages/kdewebdev/kfilereplace.pot to French using Lokalize (143 strings) and make the screenshot in French interface based on the English one http://websvn.kde.org/trunk/KDE/kdewebdev/doc/kfilereplace/ (9 screenshots)
Expected results: The .po fully translated to French + the 9 screenshots.
Prerequisites: Basic knowledge of KFileReplace, knowledge of Lokalize and KSnapshot
Time to complete: 3 days
Mentor: Anne-Marie Mahfouf ([email protected])
Documentation translation (French): Translate Kiten documentation + 2 screenshots
Description: Translate Kiten User Manual http://websvn.kde.org/*checkout*/trunk/l10n-kde4/templates/docmessages/kdeedu/kiten.pot to French using Lokalize (70 strings) and make the screenshot in French interface based on the English one https://projects.kde.org/projects/kde/kdeedu/kiten/repository/revisions/master/show/doc (2 screenshots)
Expected results: The .po fully translated to French + the 2 screenshots.
Prerequisites: Basic knowledge of Kiten, knowledge of Japanese, Lokalize and KSnapshot
Time to complete: 2 days
Mentor: Anne-Marie Mahfouf ([email protected])
Documentation translation (French): Translate Rocs documentation
Description: Translate Rocs User Manual http://websvn.kde.org/*checkout*/trunk/l10n-kde4/templates/docmessages/kdeedu/rocs.pot to French using Lokalize (82 strings)
Expected results: The .po fully translated to French
Prerequisites: Basic knowledge of Rocs, knowledge of Lokalize and KSnapshot
Time to complete: 2 days
Mentor: Anne-Marie Mahfouf ([email protected])
Complete Russian translation of Marble interface
Description: Complete Russian translation for Marble
Expected results: Full translation of marble.po and marble_qt.po (662 messages) into Russian (should be tested on current stable version of Marble).
Prerequisites: Good Russian, basic geography knowledge.
Time to complete: 5 days
Mentor: Yuri Chornoivan ([email protected])
Complete Turkish translation of Marble interface
Description: Complete Turkish translation for Marble
Expected results: Full translation of marble.po and marble_qt.po into Turkish (should be tested on current stable version of Marble).
Prerequisites: Good Turkish and English, basic geography knowledge.
Time to complete: 5 days
Mentor: Utku Aydın ([email protected])
Kst 2.x: get ready for translation
Description: Kst 2.x is no longer translated due to changes in KDE's infrastructure and the port to a Qt application. Now is the time to find a solution to that, as suggested here: http://mail.kde.org/pipermail/kst/2011-September/020092.html
Expected results: Kst 2.x ready to be translated (strings listed, infrastructure in the right place).
Prerequisites: Knowledge of KDE's translation facilities
Time to complete: 3 days
Mentor: Nicolas Brisset <[email protected], Kst mailing list>
hard
Documentation translation (Polish): Update kcontrol documentation
Description: Update documentation of the kcontrol program and module. Several hundred messages in multiple files.
Expected results: All strings are translated and it builds correctly.
Prerequisites: Basic knowledge of shell to be able to run commands that build the documentation (will provide guidelines)
Time to complete: 7 days
Mentor: Marta Rybczynska ([email protected])
Documentation translation (French): translate Kajongg User Manual + screenshots
Description: Use Lokalize to translate the Kajongg .pot file http://websvn.kde.org/*checkout*/trunk/l10n-kde4/templates/docmessages/kdegames/kajongg.pot (364 strings). Use KSnapShot to make the screenshots (10) based on the English ones http://websvn.kde.org/trunk/KDE/kdegames/doc/kajongg/
Expected results: The .po file is fully translated to French and the 10 screenshots are made in KDE defaults with a French interface.
Prerequisites: Basic knowledge of Kajongg, knowledge of Lokalize and KSnapshot Time to complete: 5 days
Mentor: Anne-Marie Mahfouf ([email protected])
Description: Marble has a route guidance mode that can make use of speakers (pre-recorded sound files) to indicate directions. There are some existing ones to download at http://edu.kde.org/marble/speakers.php and instructions to install them at http://userbase.kde.org/Marble/CustomSpeakers#Voice_Installation and also instructions how to record a custom voice at http://community.kde.org/Marble/VoiceOfMarble. Your task is to follow the instructions and speak and record the full set of voices in a language of choice. The aim is to create a high quality voice set. To get best results you might want to consider recording the voice of a different person (e.g. a local radio speaker or someone else who has experience with voice recording). The voice recording should be done for a language + gender (male/female) combination which has not been covered by other speakers yet or where the quality can be improved upon (e.g. German (Female), French (Female or Male), Japanese (Female or Male), Norwegian (Female or Male), Arabic (Female or Male), Hebrew (Female or Male), etc..).
Expected results: A full set of high-quality voice recordings ready for usage in Marble for a specific language.
Prerequisites: An installation of Marble 1.2 (KDE 4.7). Can be compiled from source code as well. An installation of Marble on the N900 would be nice, but is not absolutely necessary.
Time to complete: 96 hours
Mentor: [email protected] / [email protected]
User Interface
easy
Port Desktop Switching OSD to QtQuick
Description: The Desktop Switching On-Screen-Display is implemented with the GraphicsView framework. For code maintainability this should be rewritten using QtQuick and the existing code should be removed.
Expected results: Desktop Switching OSD with QtQuick
Prerequisites: Basic QtQuick and JavaScript knowledge
Time to complete: 24 hours
Mentor: [email protected]
medium
Verify that three applications are using system color scheme
Description: If applications use hard coded colors or don't use the system color scheme they are hard to use for people with vision issues. Ensuring an application is using the system color scheme makes our applications easy to use by everyone.
Expected results: Report of which if any applications are not following (or having an option to follow) the system color scheme.
Prerequisites: basic Qt
Time to complete: few hours
Mentor: [email protected]
Identify necessary changes to make non-Active apps shipped with Plasma Active touch-friendly
Description: Currently we ship some applications with Plasma Active which were not specifically designed for touch devices (e.g. Okular for PDF viewing, Banagarang for media playback, Konsole etc.). These applications work reasonably well on a tablet, but it is still obvious they were not made for them (e.g. they still use righ-click actions, small click targets etc.). The task is be to identify (ideally including research with actual users) what exactly the "pain points" are when these applications are used on a touch device and what would be necessary to eliminate them.
Expected results: List of pain points with solutions for each non-active application shipped with Plasma Active One (six in total).
Prerequisites: Ideally a tablet computer that can run Plasma Active ( see Device List ), otherwise a virtual machine running Plasma Active would work as well. No technical skills required.
Time to complete: 24 hours.
Mentor: Thomas Pfeiffer ( [email protected] )
Create a new OpenStreetMap based map theme for Marble (3x)
Description: Marble offers several Map Themes already - some of them are based on OpenStreetMap Tile data. Many of them can be downloaded using KDE's Get Hot New Stuff feature. Have a look at the existing ones (Like "OpenStreetMap" (using Mapnik as well as OsmaRender), the "Hike and Bike" map, "OpenCycleMap", etc. Have a look at how map themes can be created using the wizard as well as by editing the dgml (xml) files.
Have a look at:
http://wiki.openstreetmap.org/wiki/DE:Anwender#Online.2C_also_mit_Internetverbindung
which lists a few services some of which might be candidates for new maps (use your favorite translation tool for translation of the website).
Create a new map based on such a service (the license of the whole work including the data needs to be compatible with Marble's license requirements, e.g. CC by SA is fine). The new map needs to display the new map material and needs to have a proper icon (in the style of existing ones) including a name. The new map theme also needs to have a proper legend describing all the important colors and icons. The finished map theme needs to be ready for upload to the KDE GHNS service.
Expected results: A new functional map theme based on OpenStreetMap data.
Prerequisites: Knowledge of editing xml files, basic knowledge of Krita, Gimp or Photoshop for the legend.
Time to complete: 96 hours.
Mentor: [email protected]
hard
Identify KDE applications that would be useful on a mobile device and how to make them touch-friendly
Description: We currently only ship the subset of available KDE applications with Plasma Active which we identified as either having an interface suitable for tablets or as central elements for typical mobile use cases. The first part of the task is to look at as many KDE / Qt applications as possible and identify those which would be very useful in a mobile context. Most of these applications will probably not be working on a touch device well yet because they were created with desktops / laptops in mind, so the second part is to identify how they would need to be adapted in order to offer good touch interaction and work well on a mobile device (tablet, smartphone).
Expected results: A list of applications (at least 15) that would be useful on a mobile device along with a list of necessary changes to each application to make it "touch-friendly".
Prerequisites: Access to a comprehensive KDE software repository (available in most Linux or BSD distributions that ship KDE 4). Access to a device running Plasma Active ( see Device List ) or a virtual machine running Plasma Active would be helpful.
Time to complete: 48 hours.
Mentor: Thomas Pfeiffer ( [email protected] )
Create user scenarios for Plasma Active
Description: We use user scenarios ( wikipedia:Scenario_(computing) ) to guide the devlopment of Plasma Active. These scenarios describe where, when, by whom and how a device with Plasma Active might be used (e.g. "Import fotos of a trip from your camera to your tablet, organize them, and show a selection of them to your friends"). The task is to imagine new user scenarios for a device running Plasma Active inlcuding people involved, contexts, goals, tasks etc.)
Expected results: At least three complete user scenarios.
Prerequisites: None. Experience with creating user scenarios or user stories would be helpful.
Time to complete: 36 hours.
Mentor: Thomas Pfeiffer ( [email protected] )
Create a new "Historic World Map" map theme for Marble (3x)
Description: Marble features a lot of historic maps from the age of discoveries, such as the Schagen map, see:
http://techbase.kde.org/Projects/Marble/HistoricalMaps/WorldMapSchagen1689
as an example. See
http://en.wikipedia.org/wiki/Ancient_world_maps
http://de.wikipedia.org/wiki/Benutzer:Kronf/Liste_historischer_Weltkarten
as a possible source for more maps. Don't forget to check license and whether Marble includes such a map already. You can also create a historical map of Mars or the Moon if you find such data.
For conversion of the Marble data to a suitable format you can check:
http://techbase.kde.org/Projects/Marble/HistoricalMaps
For stereo graphic projections there is a tool available. Please read:
http://blogs.kde.org/node/4322
Once the map has been morphed you need to retouch the map using Gimp, Krita or Photoshop. This requires good skills on how to touch up graphics using e.g. the clone tool. The new map needs to have a legend included (like the other historical maps - you can use the existing ones as a template).
Expected results: A new historical map ready for upload to the GHNS server.
Prerequisites: Knowledge of editing xml files, Advanced knowledge of Krita, Gimp or Photoshop for touching up the morphed image and for creation of the map key.
Time to complete: 120 hours.
Mentor: [email protected]
User Preference for Review Tools in Okular
Description: It will be very convenient for users, if there are some options to change defaults for the Review tools. This means width of lines, colors of highlights, transparency and so on.
https://bugs.kde.org/show_bug.cgi?id=284946
The Student needs to develop a design document which includes where should we add the configurations, how should it look like etc. Open a file and then go to Tools->Review and you can see the current review tool system. Now, think about where and how can we add user preferences. Try to create the whole scenario. You can see other softwares to get some idea and then propose the design in detail.
Design Submission using some design tool like Qt Designer will be nice. If the student do now want to use Designing tool, he can also use some drawing software to draw the design. A Report with some little explanation of the design is necessary in this case.
Expected results: A UI Design for the review tool preference setting.
Prerequisites: Knowledge of UI Design, Experience of using okular, Qt Designer and a good sense of UI.
Time to complete: 3 days
Mentor: Mohammad Mahfuzur Rahman <[email protected]>