GSoC/2010/Ideas

Guidelines

Information for Students

These ideas were contributed by our developers and users. They are sometimes vague or incomplete. If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at.

Being accepted as a Google Summer of Code student is quite competitive. Accepted students typically have thoroughly researched the technologies of their proposed project and have been in frequent contact with potential mentors. Simply copying and pasting an idea here will not work. On the other hand, creating a completely new idea without first consulting potential mentors is unlikely to work out.

When writing your proposal or asking for help from the general KDE community don't assume people are familiar with the ideas here. KDE is really big!

If there is no specific contact given you can ask questions on the general KDE development list [email protected]. See the KDE mailing lists page for information on available mailing lists and how to subscribe.

Adding a Proposal

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

• if the application is not widely known, a description of what it does and where its code lives
• a brief explanation
• the expected results
• pre-requisites for working on your project
• if applicable, links to more information or discussions
• mailing list or IRC channel for your application/library/module
• your name and email address for contact (if you're willing to be a mentor)

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

Ideas

Amarok

Amarok is a powerful KDE based music player for Linux and Unix, MacOS X and Windows with an intuitive interface. It makes playing the music you love and discovering new music easier than ever before - and it looks good doing it!

Website - Mailing list - IRC channel: #amarok on Freenode.

Project: Playdar integration

Brief explanation: Integrate playdar into Amarok, both as a collection backend, and as a searchable/playable context applet.

Expected results: Playdar is a new "music content resolver" service (http://www.playdar.org/), started by RJ of Last.Fm fame. Its task is to find how to play any song that it is given, using a number of pluggable backends. Please see the website for more information, as well as http://www.playgrub.com/ for an app example. By integrating playdar into Amarok, you will allow users to explore and play tracks from any of the resolvers that playdar has available. Imagine dynamic playlists that can pull tracks from mp3tunes, amazon full track previews, napster, soundcloud, local LAN computers, and more. Imagine browsing the local network and seeing what tracks are seamlessly available for you to play and organize. An implementation would both supply a collection backend, for browsing, and a context applet, for doing a simple search in the context view.

There would be some work required also on the playdar side of things---although it is planned to support browsing collections, it is not implemented yet. Playdar is written in Erlang, so this is also a perfect opportunity to get your feet wet doing functional programming.

Knowledge Prerequisite: Knowledge of C++ and Qt is a requirement. Knowledge of Erlang a plus, but pretty rare. Enthusiasm for trying new things and pushing the future of social music forward a requirement.

Mentor: Leo Franchi <[email protected]> or another Amarok developer.

Project: Dynamic Playlists Overhaul

Brief explanation: Throw out the old dynamic playlist code, and integrate existing backend code for generating user-specified dynamic playlists as well as design a smashing new intuitive UI for controlling them.

Detailed explanation: The current dynamic playlist system is merely decent at best. It fails a lot of expected use-cases, and the UI misleads the user by lying about what it can do. There is already a new advanced playlist generation framework designed by a developer (Soren Harward) that is sitting in a git branch, ready to be merged. However, the UI is severly lacking, and needs to be redesigned. Designing the UI for such a complex piece of functionality will be a significant UI design / HCI challenge, and the main thrust of this project. While there are some mockups already available, most of the design will need to be drawn up by the student.

Knowledge Prerequisite: Knowledge of C++ and Qt is a requirement. Interest in usability and HCI a plus. Interest in UI design is also important.

Mentor: Leo Franchi <[email protected]> or another Amarok developer.

Project: On the Fly Transcoding

Brief explanation: Allow media to be seamlessly transcoded to another format whenever it is copied from one collection to another.

Expected results: Amaroks concept of collections allows media to be easily moved and copied around. In many cases however, the format you want in one collection is not the same as you might want it to be in when copying it to another collection. A common example is having your entire local collection in lossless FLAC, but wanting to copy songs to a mobile device that only supports mp3 (or even if the device supports open formats, you might want to transcode it to ogg to save space). On completion of this project, an option to enable transcodeing should be integrated into the "Move/Copy to collection" flow in a way that it is available whenever this is used between 2 collections. A big part of this project will be to determine the most suited library or application to use as the backend of the transcoding engine.

Knowledge Prerequisite: Knowledge of C++ and Qt is a requirement. Knowledge of media formats and the different available apps and libraries for transcoding them is a bug plus.

Mentor: Nikolaj Hald Nielsen <[email protected]> or another Amarok developer.

Project: Distributed Collections

Brief explanation: Allow several instances of Amarok on a network, each with their own distinct local collection, to seamlessly search, browse music from each other.

Expected results: On completion of the project, it should be possible to allow other instances of Amarok to access your local collection, as well as have access to the collection of other instances of Amarok, if their users allow it. A protocol for searching, browsing and streaming music should be in place, either developed from scratch or based on an existing standard (if a suitable one can be found). Issues such as authentication and auto discovery must be considered and a solution found.

Knowledge Prerequisite: Knowledge of C++ and Qt is required. Knowledge of XML, JSON or other data exchange schemes will be a big benefit, As there are many open question in this project, the student is also required to be capable of independently coming up with ideas for solutions to many issues, so a high degree of creativity and independence is required.

Mentor: Nikolaj Hald Nielsen <[email protected]> or another Amarok developer.

Project: Amarok & KDE UPnP integration

Brief explanation: UPnP is a network auto-discovery and services protocol that among other things allows serving media to connected devices in the local network.

By creating a UPnP KIO slave and supporting infrastructure it becomes possible to access this media directly from any KDE application. In Amarok some extra integration is needed to make the UPnP MediaServer a full Collection. This includes indexing the contents locally when the server has no, or limited support for search.

Expected results:

• A UPnP KIO slave based on an already existing or in development framework for UPnP.
• An Amarok Collection implementation including a functional QueryMaker using UPnP-search or MemoryQueryMaker.
• Optionally a PlaylistProvider implementation for UPnP-native playlists and playlist files found on the server.

Knowledge Prerequisite: C++ and UPnP. KIO-slave or Amarok experience is recommended.

Mentor: Bart Cerneels

digiKam

Photo Management program

digiKam project web site - Mailinglist - IRC channel: #digikam on Freenode.

Project: Non-Destructive Editing

Brief explanation: Non-destructive means that the original image is not overwritten when editing. Instead, the applied changes are stored and a new version of that image is created. Version history can be accessed.

Expected results:

• Define a format to store editing operations - research existing standards or similar free software approaches, or come up with a home-made XML format.
• Adapt the existing image plugins to read and write their settings from this XML format and to re-apply a described operation to a given image (this is a laborious but relatively easy task)
• work together with your mentor on storing version history in digikam's database and the image's metadata. (this is needed to finish the project, but it's not the core of the student's work). Set up a simple file naming scheme to store the original and derived files.
• Implement the user interface changes: No more Save/Save As in the image editor. Instead, saving as current version, forking a new version, or exporting. Stacks of images (original/current version) in the album icon view.
• Build a widget to display version history. Optionally this is a really nice widget, a tree view with buttons to show information. Optionally there is also support to take a set of applied changes, store it and apply it to a different image.

Knowledge Prerequisite: C++ and Qt. Some interest in image editing.

Mentor: Marcel Wiesweg <marcel dot wiesweg at gmx dot de>

Project: Face Recognition

Brief explanation: Digikam shall be able to detect faces in photos, identify the person depicted and automatically tag the region on the photo with the person's name.

Expected results:

• Face Detection: Refine classifiers provided by OpenCV
• Face Recognition: Improve existing Eigenfaces implementation. Implement Fisherfaces recognition, work with GNU science library to implement the needed QZ algorithm.
• round up this underlying technology in a small library with some test cases
• work on a basic UI integration in digikam. There is an existing UI solution for Nepomuk already.
• optionally, define the format to store tags on regions of images (currently it's only possible to tag an image as a whole) in metadata and database. You will get support here from the digikam core developers.
• optionally, design some user interface solutions for the training tasks involved (telling the classifier what's right and what's wrong)

Knowledge Prerequisite: C++ and Qt. Knowledge of matrices and working with them. Some idea of clustering algorithms and previous OpenCV experience would be useful.

Mentor: Alex Jironkin for face detection part, one of the digikam core developers for the UI part (contact: Marcel Wiesweg <marcel dot wiesweg at gmx dot de>)

Hints:

• Nepomuk could be used to link faces to contacts in Akonadi

Project: Reverse Geocoding and Improved Map Search

Brief explanation: Using the Google Maps or geonames.org reverse geocoding services, location names can be added as tags to images which already have GPS-coordinates.

Expected results:

• Design a GUI to allow the user to choose which parts of the reverse

geocoding (town, country, street) should be added as tags to the images.

• Implement backends for Google Maps and geonames.org to retrieve the

descriptions of the places.

• Modify the map search in digikam to show all

images in the database on the map, via a model that requests the number of images in a certain region from the database.

Knowledge Prerequisite: C++ and Qt. Google Maps reverse geocoding requires some JavaScript knowledge, but should be doable without prior knowledge.

Mentor: Michael G. Hansen <mike at mghansen dot de> and another digikam developer (contact: Marcel Wiesweg <marcel dot wiesweg at gmx dot de>)

KDE Edu

Sabine Emmy Eller suggested the development of a “general conversion tool” for tables to various xml formats and from one xml to another xml format etc. where one can add further formats over time would be great. If this is a good idea we can actually start to think about more detailed specifications for what we need.

Project: Time Support for Marble

Brief explanation: Wouldn't it be great to be able to see the world at different times in Marble? Like having a slider which would give you the ability to browse through the time? Marble's internal datastructure is modelled after KML. But support for time-related tags is missing.

Expected results:

• Having a GUI on the map and as a QWidget based dialog which allows people to "slide" through time.
• Implementation of the KML <TimePrimitive> and <TimeSpan> tag: Creating the KML-handler and needed data classes for the GeoData parser.
• Having a central "internal" clock which the current view would be based on.
• Porting existing features (like the starry sky and the sun shading) over to the new class design.
• Using the new time support in Marbles Online Service plugins.

Knowledge Prerequisite: C++ and Qt. Knowledge about KML is not necessary but would be appreciated.

Mentor: Bastian Holst <bastianholst AT gmx DOT de>

Project: More online plugins for Marble

Brief explanation: Find some online services that provide position data and write online plugins for it

Expected results: A set of online plugins (showing webcams, opendesktop data, twitter messages, etc.) on the marble map. This could also include animations on the marble map and general optimizations of the online services structure. An addition could be including for example earthquake kml data as an online plugin. This would also extend on Marble's Time Support (see "Project: Time Support for Marble"). And finally there would be the idea of an opendesktop plugin: OpenDesktop.org (sister site of kde-apps.org and kde-look.org) has got a Geo API which would allow to visualize e.g. Free Software / KDE users on the globe. So this would allow to turn Marble into a social network tool!

Knowledge Prerequisite: C++. Familiarity with Qt and XML parsing will help.

Mentor: Bastian Holst <bastianholst AT gmx DOT de>

Project: Enhanced KML support for Marble

Brief explanation: Write support for more KML tags to get a more complete KML support for Marble.

Expected results: Marble has a more complete KML support than now. Marble will be able to display some of the KML files one can find on the Internet.

Knowledge Prerequisite: C++. Familiarity with Qt and XML parsing will help.

Mentor: Bastian Holst <bastianholst AT gmx DOT de>

Project: Marble To Go (Navigation Mode)

Brief explanation: Turn Marble into a navigation device.

Expected results: Marble already supports GPS devices and downloading routes from openrouteservice.org. Bring both worlds together! Let the user switch to navigation mode: The map center follows the current GPS position, route instructions fade in when appropriate. The user interface should be prepared for small devices. Marble's existing offline mode should be extended for (optional) precaching tiles along the route. More features are possible (e.g. gpx/kml import/export).

Knowledge Prerequisite: C++. Familiarity with Qt will help.

Mentor: Dennis Nienhüser <earthwings AT gentoo DOT org>

Project: Panoramic Picture Support in Marble ("StreetView")

Brief explanation: Allow Marble to display georeferenced panoramic pictures similar to this one.

Expected results: The position on the globe should be displayed as a placemark and the panoramic picture displayed once the placemark is clicked. The Marble Widget itself would be used to display the panorama picture. Preferred way to store the properties of the panorama image would be extended KML support for Marble (see the PhotoOverlay documentation of the KML-Reference.

Knowledge Prerequisite: C++. Familiarity with Qt will help.

Mentor: Torsten Rahn <rahn AT kde DOT org>

Project: Community Integration for KStars

Brief explanation: This feature is expected to be of use to amateur (hobby) astronomers. The idea is that there are aspects of amateur astronomy which are collaborative. For instance, one might want to view observations by other amateur astronomers around the world before making an observation of an object. Again, one would like to share their own observations with everyone else. There are more possibilities, and the student is encouraged to come up with them.

KStars produces observation logs in an XML format that is expected to adhere to the OAL 2.0 schema. The project will involve extending the existing implementation of the OAL 2.x schema and ensuring that it is fully compatible with the schema.

A very user friendly GUI has to be implemented for viewing imported logs [And a good SQL backend for accessing the information from them efficiently], it must be able to handle objects in the logs which are not there in the current KStars database.

The user must be able to retrive logs from the internet (and other sources) on a filter based query. [Filter could be anything like, object name or location or observer name]

The user should also be able to (eventually) submit his own logs to a server.

Expected results: Better OAL 2.x compliance in KStars, Ability to retrieve observation logs from the internet, Ability to export one's own observations in XML format to a server.

Knowledge Prerequisite: C++. Familiarity with Qt and XML parsing will help.

Mentor: Prakash Mohan <prakash DOT mohan AT kdemail DOT net> / Akarsh Simha <akarsh DOT simha AT kdemail DOT net>

Project: OpenGL support for KStars

Brief explanation: KStars currently renders graphics using QPainter. To provide a realistic and aesthetic representation of the night-sky, GL functionalities like texture-mapping will be beneficial. The aim of this project would be to use the Qt OpenGL module to render graphics in KStars.

Expected results: More realistic simulation of the night-sky, better aesthetic appeal.

Knowledge Prerequisite: C++. Knowledge of Qt and OpenGL will greatly help.

Mentor: Akarsh Simha <akarsh DOT simha AT kdemail DOT net>

Project: Additional Catalogs in KStars

Brief explanation: KStars currently knows about deep-sky objects from the NGC and IC catalogs and stars from the Henry-Draper catalog. Popular objects from many other catalogs are not listed [eg: Collinder] and multiple designations for the same object are not supported. The aim of this project is to implement support for objects from SAO, UGC, PGC, MCG, PK and Saguaro Astronomy Club catalogs. This might involve revamping the way data is stored and accessed in KStars :-).

Expected results: Support for multiple designations, Many more catalogs in KStars.

Knowledge Prerequisite: Database handling will help.

Mentor: Akarsh Simha <akarsh DOT simha AT kdemail DOT net>

Project: Integration of KmPlot into KAlgebra

Brief explanation: Allow to KAlgebra to draw the same kind of functions of KmPlot through reusing code of KmPlot and improved plotting capabilities of KAlgebra.

Expected results: KAlgebra already draws explicit curves in 2D and explicit surfaces in 3D, the new KAlgebra should draw, additionally, implicit curves in 2D, parametric curves in 2D, differential plots and explicit surfaces in spherical and cylindrical coordinates.

Knowledge Prerequisite: C++, Qt, KDE, OpenGL, Eigen, GSL

Mentor: Antonio Larrosa

Project: Rocs - Graph File Formats and Teacher Mode

Rocs is a Graph Theory IDE to study and learn Graph Theory.

Brief explanation: Rocs lacks graphs formats. it currently supports one internally and GML by the amazing work that Wagner is doing on it's plugin system. but we do need more: dot, gml, umbrello files, anything graph - like should be openable by rocs. Also, teacher mode is a mode with various graph scripts ( coloring, smaller path, bigger path, etc. all of the algorithms studied in Graph Theory + a few more )

Expected results: Rocs should be able to open almost all of the graph files around, and also in teacher mode, the student could test if his algorithm is correct by comparing the results with the one in the teacher mode.

Knowledge Prerequisite: Qt - C++ - Javascript are prerequisites. all the rest is optional, but being in a Graph Theory class at university could be cool ;)

Mentor: Tomaz Canabrava

Project: Cantor: Add a new Backend

Brief explanation: Write a new Backend to Cantor, to bring your favourite Mathematical Software, (e.g. Octave, SciLab, XCas or whatever you prefer) to Cantor. Implement needed features in Cantor, to expose the whole potential of the Backend to the user. Implement assistant dialogs for the most commonly used functionalities

Expected results: The user should be able to use the Math package from within Cantor, without (or with very few) limitations, compared to using the standard interface (every important feature should be exposed).

Knowledge Prerequisite: Qt, C++, KDE, are needed to code for Cantor. You should also be familiar with the Math Software you want to write a backend for.

Mentor: Alexander Rieder

Project: Cantor: improve R backend

Brief explanation: Currently the R backend of Cantor is very basic. Goal of this Project is to heavily improve it and implement all the features it is missing, to make Cantor a nice GUI for R.

Expected results: Cantor should be turned into a suitable GUI for R, with Syntax Highlighting, Tab Completion and more.

Knowledge Prerequisite: Qt, C++, KDE, are needed to code for Cantor. Familiar with the use of R

Mentor: Alexander Rieder

Project: KHangMan

Brief explanation: Improve GUI and code refactoring. About the GUI, start with a usability study to redesign the GUI. The menus are to be redone (having an Open Recent Files action for example) and maybe suppress the Categories and Languages menus. Allow an easier management of themes as well, maybe have a GHNS theme manager. For code: refactor the way files are loaded. Allow to start with no file. Separate the data code (about the letters) from the GUI.

Expected results: Makes it visually more attractive for children, give better feedback on result, make the program workflow better

Knowledge Prerequisite: Qt, C++, KDE

Mentor: Anne-Marie Mahfouf

KDE Games

Project: KHighscore2 library

Brief explanation: The KDE Games module features the libkdegames library, which provides common components for games, such as network access and standard UI elements. Among these classes is the highscore system KHighscore, which is starting to show its age. We want you to write a successor based on Qt's model/view framework.

Expected results: The coding work itself should not be too hard, but you need to create a future-proof object-oriented design. The games in the KDE games module have very different requirements for a highscore system, we expect you to evaluate these and come up with a concept that fits most requirements. Backwards compatibility to existing highscore records is desired. When the library is finished, you should port as many of our games to the new classes.

Knowledge Prerequisite: C++ and Qt. Profound experience with Qt's model/view framework.

Mentor: none at the moment (contact [email protected] mailing list for further questions)

Project: New AI for KsirK

Brief explanation: KsirK is a strategy game inside the kdegames module where you must conquer the world country by country. You can also have specific goals. Its current AI, taken from another old implementation of the same game is really no efficient and should be replaced by better one, with a scalable power.

Expected results: You will need to study the theory of AI design for strategy games and the other Free Software implementations of the same game (like TEG for example). You will then develop and integrate the new AI for a release with the next KDE SC version.

Knowledge Prerequisite: C++ and Qt. An experience with strategy games AI would be useful.

Mentor: none at the moment (contact [email protected] or [email protected] mailing list for further questions)

Project: Gluon Player Plasmoid

Brief explanation: Gluon is a game creation and distribution system, and a Gluon Player is an application which is able to fetch and play these games. Plasmoids are, of course, the widgets on the Plasma desktop. A Gluon Player Plasmoid is thus a plasmoid which fetches Gluon games and plays them.

Expected results: A working plasmoid able to fetch games from the Gluon distribution site, and furthermore run the fetched games. Extra features which would make the plasmoid more useful would be the ability to perform donations to game authors and take part in the larger community efforts that other Gluon Player applications would be able to. Please also see Gluon Player for Maemo/MeeGo (pdf, 2.0MiB) for inspiration.

Knowledge Prerequisite: C++ and Qt. knowledge of Open Collaboration Services and Plasmoid production would be good but not required. Gluon experience not required.

Mentor: Dan Leinir Turthra Jensen ([email protected]) (email [email protected] mailing list for further questions)

KDevelop

KDE-based Integrated Development Environment, specializing in c++ support, but including a powerful generic framework (definition use chain) which makes it possible to relatively easily support multiple different languages.

Website - Mailing list - IRC channel: #kdevelop on Freenode.

Project: Quanta+ 4

Brief explanation: Quanta+ 4

Expected results: Revive the Quanta+ brand for KDE 4 and provide a usable IDE for webdevelopment. Take advantage of the KDevelop framework and reuse it's plugins and adapt them to give the user a good experience while programming PHP, CSS, HTML and JavaScript.

Knowledge Prerequisite: KDE, Qt, KDevplatform/KDevelop

Mentor: Niko Sams

Project: Community Integration

Brief explanation: Integrate community related workflow, e.g. VCS support, in KDevelop.

Expected results: Integrate a proper VCS support for SVN and Git into KDevelop and see what other aspects of a community related workflow could be integrated.

Knowledge Prerequisite: KDE, Qt, KDevplatform/KDevelop

Mentor: Andreas Pakulat

Project: OBS (openSUSE Build Service) Integration

Brief explanation: openSUSE build service allows developers to create and release open source software for openSUSE and other Linux distributions easily on different hardware architectures.

Expected results: A plugin for KDevelop that would allow a developer to easily check-in source, build, and get OBS status from within a KDevelop project. In other words, it would allow for seamless development to deployment.

Knowledge Prerequisite: KDE, Qt, KDevplatform/KDevelop

Mentor: ?

KDE PIM

KDE PIM is the interest group working on applications related to personal information management, e.g. contacts, calendar, mails, etc.

One of the current challenges is utilizing the new cross-desktop PIM infrastructure called Akonadi.

There are interesting projects on all levels of the software stack: libraries, application porting, new applications, access to online resources, etc.

Website - Project Wiki - Mailing list - IRC channel: #kontact and #akonadi on Freenode.

For a list of ideas that are not yet fully spelled out, see the brainstorming list of Summer of Code ideas of the last PIM meeting.

Project: New Kontact summary based on Plasma

Brief explanation: Create a new summary for Kontact that is based on Plasma.

Expected results: The new Kontact summary should be based on Plasma and have every feature that the old summary had. The summary should look nice and have lots of bling. It should be possible to place single components of the summary on the desktop as well, as plasmoids.

Knowledge Prerequisite: C++ and Qt knowledge is needed, Plasma experience would be welcome.

Mentor: Contact the KDEPIM Mailing list

Project: PIM integrated Clock applet

Brief explanation: Extend the clock applet to show PIM information via Akonadi

Expected results: Be able to show tasks and appointments in the clock applet's popup. Mark dates in the calendar widget that have tasks/appointments associated. Consider the performance costs of starting Akonadi and querying for data. For best code reuse, find a way to use existing plasma widgets (see above Kontact Summary project) inside the clock popup, rather than implementing new widgets. Close https://bugs.kde.org/show_bug.cgi?id=46262 .

Knowledge Prerequisite: C++ and Qt knowledge is needed, Plasma experience would be welcome. Design skills would be helpful.

Mentor: Contact the KDEPIM Mailing list

Project: Improved HTML support for KMail's composer

Brief explanation: The HTML support for KMail's composer is currently limited. This should be improved: Replying and forwarding should (optionally) preserve the HTML format. The composer should use WebKit editing so that all HTML is fully supported.

Expected results: Replying and forwarding HTML mails should be fully supported. The QTextEdit-based widget in the composer should be replaced by a WebKit-based widget, to support all HTML instead of a small subset.

Knowledge Prerequisite: C++ and Qt

Mentor: Thomas McGuire

Project: Improved theming support for the message viewer

Brief explanation: In KMail, it is currently possible to chose between different header styles, such as 'fancy' or 'brief'. These header styles currently have to be written in C++.

The goal of this project is to use the Grantlee library to provide better and easier theming support.

Expected results: The viewers of KMail, KNode and Akregator should all be ported to Grantlee. Some defaults themes should be provided, at least replacing the existing 'fancy' and 'standard' themes.

Optionally, Get Hot New Stuff should be used so that the user can easily download new themes.

Optionally, the user should have some sort of control over which header fields of the mail are displayed, see Wish 16270.

Knowledge Prerequisite: C++ and Qt

Mentor: Thomas McGuire, Stephan Kelly(?)

Project: Improving google data akonadi resource

Brief explanation: Currently kdepim can use the gdata resources (contacts and gcalendar) to sync with a google account. The idea is to implement some missing features.

Expected results: Implement more features in contacts resource (e.g. birthday field, IM fields, etc) and calendar (e.g. multiple calendar, recurrent events, etc) in both libgcal and akonadi resources. Another idea would be to port libgcal to Qt (currently it uses libcurl and libxml).

Knowledge Prerequisite: C++ and Qt (for the akonadi resource) and ANSI C for the google data library (libgcal). Networking programming is a plus.

Mentor: Adenilson Cavalcanti a.k.a. Savago

Project: Easy Import and Export of all PIM data in Kontact

Brief explanation: There should be an easy way to import and export all PIM data including the configuration data, to make it easy to exchange data and to move the Kontact data to another installation.

Expected results: There should be a central way in Kontact to import and export all data. Right now, some individual applications have their own ways to import and export data, and this should be unified. The new import and export tool should be able to deal with the following

• Configuration data, such as applications settings and account settings
• The actual data, such as mails, feeds, contacts and calendar entries
• Metadata, such as Nepomuk tags and annotations or Akonadi item flags
• Cached data, such as the cache of an IMAP account, to avoid re-downloading the mails

It should be possible for the user to have a fine-grained selection of the above so that the user can decide what to export or import.

Ideally, it should be possible to export all this to a single archive file which can be later re-imported.

There are several bug reports on [bugs.kde.org the KDE bugtracker] that request something like this, you might get additional ideas from them.

Knowledge Prerequisite: C++ and Qt

Mentor: Contact the KDEPIM Mailing list

Project: Unified account wizard for Kontact

Brief explanation: Provide a nice wizard that can set up all of Kontact in one go and is easily extensible to support new configuration templates. The wizard should set up accounts/resources for all Kontact components.

As an example, let's say the user has a Google account: That includes Google Mail, Google Calendar, Google Contacts and Google Reader. The wizard should only ask for the username and password of the Google account of the user, and then set up Akonadi resources for mail, calendar, contacts and feeds automatically.

This should of course not be limited to Google: The system should be based on configuration templates so that many popular providers can be supported. Writing such configuration templates should require no coding so that many people write them, leading to a broader support of providers in the wizard

Expected results: Contact the KDEPIM Mailing list

• Write and integrate a usable wizard for Kontact that combines setting up accounts/resources for mail, calendar, contacts and maybe more.
• Make it easy to use: The user should only need to input the bare minimum of information, and the wizard auto-detects all the correct settings, based on configuration templates
• Provide as many sample configuration templates for popular services as possible, for example for Google, AOL and other popular providers
• Optionally, integrate Get Hot New Stuff so that it is possible to download new configuration templates.

Knowledge Prerequisite: C++ and Qt

Mentor: Contact the KDEPIM Mailing list

Project: More Nepomuk Integration in Kontact

Brief explanation: Nepomuk provides wide possibilities of doing cool new things. The goal of this project is to come up with interesting ideas on how Nepomuk could improve Kontact, and implement the ideas.

Some possibilities:

• Activity Journal for Kontact
• Project-Centric Views
• Person-Centric Views

Expected results:

Knowledge Prerequisite: C++ and Qt

Mentor: Contact the KDEPIM Mailing list

Project: Personalized email addresses for each contact

Brief explanation:Facilitate usage of a different email address for each contact.

Expected results: For instance, if the user owns the domain mickeymouse.com then when he is communicating with [email protected] he would use the personalized address [email protected], and when he is communicating with [email protected] he would use the address [email protected]. The Thunderbird email client supports this with the Virtual Identity extension. See bugs https://bugs.kde.org/show_bug.cgi?id=72926 and https://bugs.kde.org/show_bug.cgi?id=159251

Knowledge Prerequisite:

Mentor: Contact the KDEPIM Mailing list

Note: This entry was not added by KDEPIM developers. It is not enough for a complete Summer of Code project, and should be extended in case this idea is used as a project proposal.

Project: KMail filter on Thread

Brief explanation: Facility in Kmail filter to move messages to folders based on thread

Expected results: User can define filters based on the "In-Reply-to:" message-id of a new message (message A) matching the message-id of an existing message in an existing mail folder (message B).  On match, option to move Message A to the folder that contains Message B.  This will help in continuing threads in the same folder in which they were started.

Please mail me if the problem statement or the requirement for this feature is not clear enough.  Raj Mathur, raju at linux dash delhi dot org

Knowledge Prerequisite: Presumably, knowledge of KMail, understanding of the e-mail message RFC, C++.

Mentor: Contact the KDEPIM Mailing list

Note: This entry was not added by KDEPIM developers. It is in general a nice idea. To make this work, threading has to be done independent from the message list. For example, an Akonadi agent could add attributes to the items that contain threading info. The filter and the message list would read these attributes. This requires a significant rewrite of the message list, and writing a threading agent. Also, this potentially requires fixing the Akonadi filtering framework, which is not yet integrated in KMail 2. All of the above certainly makes this enough for a complete Summer of Code project. Having filters that can read threading information would only be a side effect of all those changes.

KOffice

KPresenter: Create animation effects and tidy our framework, ui

Brief explanation: KPresenter has just gained an animation framework but we need lots of implementations for many kinds of effects. And we need a userinterface to manipulate it.

First step would be to implement loading and showing of about 20 different animation effects. That is actually a simple and contained task which should get you into the basic workings. Next step is to create a user interface.

Expected results: About 20 effects to be implemented. Extend and adapt the animation framework as needed to fulfill that. A user interface for creating and manipulating animations.

Knowledge Prerequisite: basic XML knowledge, C++ and Qt-knowledge, being able to understand complex code.

Mentor: Thorsten Zachmann, Casper Boemann

KSpread: Improve saving to ODF

Brief explanation: ODF is the native fileformat of KSpread. As such one of the most important aspects of KSpread is to be able to load and save OpenDocument Spreadsheet files (ODS). While we are working hard on improving the support for loading, saving is not that well tested yet. The goal would be to change that, to improve the saving to ODF as much as possible. This should be done by adding unittests for loading and saving of ODF documents and fixing bugs where they show up.

First step would be to test different cases and to identify problems. As a starting point a look on the wo rk done on the Schedules, the Specs and the Code may help.

Expected results: Loading, saving and reopening a document should introduce as less unwanted changes as possible. Saving should work as good as loading does already.

Knowledge Prerequisite: ODF specs, Qt-knowledge, being able to understand complex code.

Mentor: Sebastian Sauer

KSpread: Add support for pivot tables

Brief explanation: Many spreadsheet applications support so called pivot tables/data pilot tables. KSpread currently has no such support, but this would be very nice to have, as ODF does contain support for this.

Expected results: It should be possible to insert pivot tables in kspread documents. Being able to save, load and update pivot tables loaded from ods documents would also be very nice.

Knowledge Prerequisite: Qt, C++, some experience with pivot tables in other applications would be nice.

Mentor: Marijn Kruisselbrink

Create an exciting new content type (flake shape)

Brief explanation: KOffice allows developers to create so called flake shapes as plugins. Examples of this are the formula editor, the video player and the music notation shape. We invite the GSoC developer to come up with a content type of his / her own choosing and implement that as a plugin for KOffice.

Expected results: Loading, saving and reopening a document with the shape in it should just work. There should be at least a simple way to edit the content inside the KOffice applications (mouse/keyboard handling, some dialogs).

The project is very flexible and we can have many different ones running at the same time, please feel free to submit more than one if you must. A google search for the musicflake will give you the project from a couple of years back. Further quick examples of shape types may be; knitting patterns, graphs & maths, tagclouds, etc. And naturally its possible to continue working on the existing ones. Like the formula shape and the music shape.

Knowledge requisites:

• C++
• Qt

Add support for e-book formats to KOffice

Brief explanation: Add a new export for one or more formats that are specifically tuned for e-book devices.

With the increased popularity of ebook readers there is going to be a need for tools to create ebook content. While most e-book devices can display PDF there are in fact a lot more formats in use. One such format is .epub, which allows reflowable content (unlike PDF). The format itself is based on XML and uses style sheets (CSS) to format content. There are few free software tools that can generate and manipulate this format and those that exist are restricted to command line.

Since most people creating content will most likely want to use an office suite or word processor to make documents it makes sense to add an export option for this format to KOffice.

Knowledge requisites:

• C++
• XML
• CSS

KDE General

Analyzing and improving KDE startup time

Brief explanation: The time needed from the moment KDM is left till the KDE plasma desktop is visible and till someone is able to start work is long compared with other systems, especially closed-source systems. The first step would be to analyze what causes KDE startup to take so long. In the second phase patches would be implemented withj the goal to address the identified problems and to decrease the overall startup time.

Expected results:

• A document that describes the work done (analyzing, findings, improvements, etc) and that allows to reproduce the analyzing at a later time. The goal here is to have a document that provides long-term results by making future investigations and improvements easier.
• Patches that let KDE startup faster. This is the direct visible result that should result in a faster KDE startup as soon as possible.

Knowledge Prerequisite:

• C++
• independent and organized working style

References:

• my bootchart shows that we can optimize different areas to save some seconds. In the bootchart the ksplashx is the splash screen that is displayed from the moment the displaymanager kdm is left till the moment the KDE plasma desktop is visible and can be used.
• oprofile or sysprof or valgrind to analyze the startup process to know where optimization makes sense.
• probably interesting files related to the startup sequence are in the KDE svn at kdebase/workspace/startkde.cmake, kdelibs/kinit/kinit.cpp, kdelibs/kded/kded.cpp (and kdelibs/kded/kbuildsycoca.cpp), kdebase/workspace/ksmserver/startup.cpp, kdebase/workspace/kwin/main.cpp and kdebase/workspace/plasma/desktop/shell/plasmaapp.cpp

Workflow:

1. Setup KDE development environment (Subversion and Building)

2. Analyzing the startup using our self compiled KDE. We could use bootchart, sysprof, oprofile, etc. to have an idea what KDE does during startup.

3. Get familar with the code that is responsible for the startup.

4. Change the code that is responsible for the startup to improve the overall startup time.

Examples:

• Delay initialization of PowerDevil and DeviceAutomounter was resulting in a one second startup-time improvement
• Disable logout sound was resulting in KDE 4.5 having a much shorter logout song compared to previous versions.
• Don't wait for kwin or kcm's in ksmserver was discarded but we probably like to look at it again + test if it really improves the startup-time + look if it can be done another/better way + etc.
• Remove obsolete kbuildsycoca run on startup does not really improve the startup-time (at least not notable) but removed obsolete code and made it possible again to be able to manually disable the kbuildsycoca (cache database that contains informations that are in the *.desktop files, so KDE's plugin system) run on startup.

Mentor: Sebastian Sauer

Creating a KDE performance testcase

Brief explanation: KDE workspace and applications often have a reputation of having extensive resource requirements, but there are rarely reliable numbers or tests that could be reproduced. As such there are almost no reliable public data on KDE's performance, nor is there a reasonably simple way to check the status.

Expected results: A set of tools, scripts and/or documents on how to measure KDE performance in important areas in a realiable and reproducible way. Using the testcase it should be possible for example to compare how different KDE SC releases change over the time and help identify problematic spots. In other words, the expected result in not improving any specific KDE area, but creating means for helping with it.

Knowledge Prerequisite:

• C++, scripting (required)
• experience with benchmarking (recommended)

References:

• http://ktown.kde.org/~seli/memory/
• http://www.berthels.co.uk/exmap/
• Performance-related entries in http://kdedevelopers.org/blog/280

Mentor: Lubos Lunak

CMake/CDash Testing Improvements: Subprojects

Brief explanation: Most KDE modules are big, which can cause issues of information overload when all developers in a module are emailed about any regressions. Alex has done a considerable amount of work getting nightly KDE CDash submissions (see http://my.cdash.org/), but dividing the modules up into subprojects would improve the granularity of feedback. CMake 2.8 has subproject support, but it still requires a lot of manual work. Working on the KDE CMake build system, and CMake directly, to improve labeling of subprojects and submission to CDash.

Expected results:

• A document that describes the work done (using subprojects, submitting module builds broken up into subprojects).
• Patches to the KDE build system to support subprojects.
• Patches to CMake to improve support of subprojects in KDE.
• Working with KDE modules to deploy subpprojects in those modules.

Knowledge Prerequisite:

• C++, CMake, CDash

Mentor: Marcus Hanwell and Alexander Neundorf

KDE on Windows

DrKonqi on Windows

Brief explanation: DrKonqi, together with the crash handling classes need to be fully ported to Windows. Currently, DrKonqi can run on windows, but it cannot generate a valid backtrace. So, the next step is to investigate on how to produce valid backtraces, probably using the dbghelp API and libbfd from mingw binutils and how to change the current installation process to support debug packages. On the first part, there should be implementations for a debugger which will give valid results for both compilers (mingw/msvc).

Expected results: The student should investigate & document how to produce valid backtraces with dbghelp API and libbfd. Based on these findings, a debugger should be written which will generate those backtraces.

Knowledge Prerequisite:

• C++ (required)
• win32 API (strong recommendation!)
• Qt (recommended)

Mentor: Patrick Spendrin / George Kiagiadakis

KWin

KDE's window manager

Techbase page - Mailinglist - IRC channel: #kwin on Freenode.

KWin scripting support

Brief explanation:

KWin is customizable, but only using GUI options, which limits the possibilities. Adding scripting support would make the possibilities for customization virtually unlimited. See also http://www.kdedevelopers.org/node/3336.

Expected results:

Wrapping KWin internals in a suitable API and adding scripting using standard KDE/Qt scripting support. It should be possible to control various aspects of windows, query window management data, react on various events and write desktop effects in a usable way (sufficient performance and convenience). Scripting usage should be similar to other places in KDE such as Plasma, as reasonable.

Knowledge Prerequisite:

• C++, Qt, scripting language (required)
• X11 (nice to have, but not required)

Mentor: Lubos Lunak

KWin or Mobile / MeeGo

Brief explanation: Get KWin working on devices such as the N900 or other small devices so that KDE Plasma Mobile can provide the full UI stack with proper integration between plasma-mobile and kwin.

Expected results: Completed OpenGL ES support in KWin for effects, an "expose" effect that is appropriate to mobile systems triggerable by a D-Bus interface

Knowledge prerequisite: OpenGL, window management a plus

Mentor: Martin Gräßlin

Improved effects configuration

Brief explanation: Provide a better user interface for managing KWin effects, so that a user can see which effects are mutual exclusive, which work together and which hardware is required for an effect.

Expected results: A new compositing configuration module supporting use cases like "effect for minimizing" and "effect for closing window" should be implemented. Furthermore the window rules should be extendes so that effects can be enabled/disabled for special windows.

Knowledge prerequisite: C++, basics of window management, usability experience

Mentor: Martin Gräßlin

Nepomuk

Website- Documentation/Howtos - Ontologies - Mailing list - IRC channel: #nepomuk-kde on Freenode.

(Also see the Nepomuk techbase page for a long list of Nepomuk-related ToDos and ideas.)

Web Metadata Extractor Framework and Service

Brief explanation:

Currently, the only metadata for files available is extracted by libstreamanalyzer and obviously it's limited to the metadata already present in files. However, there's a lot more metadata that can be mined from web resources such as lyrics, movie plots and bibliographic data.

We need a plugin-based service, which would slowly crawl indexed files in background and let plugins extract additional metadata based on existing metadata. There must be a way to configure the service and plugins.

The project includes writing a number of useful plugins to "field test" the design to make sure it's viable, serve as examples for other plugin writers and provide a visible benefit to users.

Expected results:

Music: lyrics, extra album metadata(year, track count, trivia), artist/band metadata(birth date, gender).

Video: IMDB data

A convenient interface to configure and enable/disable plugins(say, user might want lyrics but doesn't care about artists), configure the service(such as frequency of recrawling to see if new metadata is available)

Mentor satisfied that plugins can be written to use the service for other purposes.

Knowledge Prerequisite:

• C++
• Qt
• SPARQL and Nepomuk or any other semantic background would help

Mentor:

Sebastian Trueg or Eveny Egorochkin

Dedicated Desktop Search GUI

Brief Explanation: While we have powerful search tools in KDE/Nepomuk the representation is still not perfect. Especially non-file results are shown in an unintuitive way. The goal is to have a search GUI (reusable in several applications if possible) that presents search results in a nice manner. File results are simple (but could include snippets), but also contacts and emails (in KDE 4.5) and other results like tasks or projects needs proper display.

A generic approach would in theory be best but is probably impractical in the scope of GSoC. Thus, a GUI handling the mentioned special cases would already be a nice result.

Knowledge Prerequisite:

• C++
• (Qt /KDE)
• SPARQL and Nepomuk or any other semantic background would help

Mentor: Sebastian Trueg

Sub folders in Nepomuk search KIO slave

Brief Explanation: With the nepomuksearch and nepomuk KIO slaves we have powerful search tools at our hands (compare project above). One thing is missing though: subfolders to further restrict a query. Since these can hardly be created automatically the idea would be to have the user create them through a slick GUI. Then they can use and share this manually created hierarchy of queries.

A good example could be music files: define folders for "artists", "albums", "genres", "years", and so on. Then maybe in the "artist" folder we could have another folder "all tracks" and one for each album.

But there could be other hierarchies as well: filter by projects and then by persons related to the things. Or by tasks or both. Or have one subfolder pulling in everything that contains the name of the project.

There are many possibilities.

Expected Results:

• A GUI to create hierarchies of queries with the possibility to upload them to opendesktop.org or get new ones from there.
• Integration of the hierarchy into the KIO slaves. Either with a new KIO slave which makes use of the existing ones or with a extension to the existing ones.
• A description format for the hierarchies (could be XML for example)
• A set of default hierarchies the user can choose from to get started.

Knowledge Prerequisite:

• C++
• (Qt /KDE)
• SPARQL and Nepomuk or any other semantic background would help

Mentor: Sebastian Trueg

Stream Analyzer based on Data Structure Descriptions

Brief explanation:

The analyzers in libstreamanalyzer (part of Strigi) are all written in C++. This gives a lot of flexibility but could be improved. The best way to describe a file format and the data formats used in the file is to write a grammar for it. Ideally, there would be a stream analyzer that takes the data structure descriptions and a mapping to extract from the certain files to metadata triples.

A helper program would convert the data structure description and a mapping description and compile it to a stream analyzer. A simple example using the header for a PNG file. A PNG files starts with 8 bytes of magic, then 4 bytes with the chunk size, then 4 bytes unsigned big endian for the width and 4 bytes unsigned big endian for the height. A simple grammar could say:

magic: 8*Byte
chunksize: BigEndianUInt32
width: BigEndianUInt32
height: BigEndianUInt32

Then a separate mapping could be written to convert this information to triples:

width -> http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#width
height -> http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#height

This way, one could easily write stream analyzers without knowledge of C++. Also one would be able to develop faster analyzers independently from the actual file formats by writing a better code generator.

Other analyzer projects could benefit too, since the format description and mapping is language-independent.

Expected results:

Look for a grammar language or a subset, such as BNF, antlr or the one used in msoscheme, that could describe a wide range of file formats and that is simple enough that one can write a parser for it. The generated code should give an implementation of a Strigi::StreamEventAnalyzer for each structure description plus mapping.

Knowledge Prerequisite:

• C++
• Experience with code generation and data format grammars
• SPARQL and Nepomuk or any other semantic background would help

Mentor: Jos van den Oever

IRC channel:

#strigi on Freenode

See Also...

In this very list:

• More Nepomuk Integration in Kontact
• Integrate Nepomuk in bookmarks
• Financial information in Nepomuk

And more Nepomuk ideas:

• Nepomuk Project Ideas page
• Nepomuk Wishes in the KDE bug db

Plasma

Website - Mailing list - IRC channel: #plasma on Freenode.

Plasma Library Unit Tests

Brief explanation: A set of unit tests regarding Plasma library contents (like widgets, dataengines, animations, and such) which basically helps developers know when a certain modification on the code would generate a regression bug or unexpected behavior. This idea is similar to the Javascript API Test Suite one but with a different goal, which is the Plasma core library itself.

Expected results: A set of unit tests (using QTestLib framework preferably) divided by group and handled by the build-system using CTest. GCOV/LCOV/GENHTML shall be used to generate proper coverage report data (with a coverage threshold at least >=90%). The tests in general will cover signal/slots behaviors and object states (actual data from object class members) given a certain procedure (i.e. clicking on a button). Bonus points for more complex tests which involves graphical behavior aspects of widgets and animations.

Knowledge prerequisite: C++, Qt (including QTestLib), Plasma and code coverage report tools.

Mentor: Bruno Abinader

Javascript API Test Suite

Brief explanation: A test suite system for ensuring quality of the various JS APIs including Javascript Plasmoids, DataEngines, Runners and the plasma-desktop scripting console. Due to the dynamic nature of Javascript, it is prone to errors in the bindings and changes in behavior.

Expected results: A test harness (could link into QTest perhaps?) to run the scripts, a reporting tool (or integration with an existing one) that can show current results and compare against past releases and 90%+ coverage of existing API via JS scripts runnable by the harness. Bonus points for autogenerating tests from the QMetaObjects of the bound classes in kdelibs/plasma/ such as the widgets.

Knowledge prerequisite: Javascript and C++, Qt and Plasma a bonus

Mentor: Aaron Seigo

Grid and Grouping Containments

Brief explanation: Containments that do widget grouping and gridding

Expected results: A desktop and a panel containment which allow widgets to be grouped or put into grids.

Knowledge prerequisite: C++, Qt and Plasma a bonus

Mentor: Aaron Seigo

Plasmoid Data Caching

Brief explanation: Right now when Plasma Netbook does not have a network connection, Plasmoids such as the news/rss, microblogging, etc. plasmoids tend to show nothing in the interfaces. A simple caching system would allow widgets to show the data that was available when networking was last available.

Expected results: Plasmoids / DataEngines relying on network access should cache data for when networking is not available and refresh when networking becomes available.

Knowledge prerequisite: C++

Mentor: Marco Martin, Bruno Abinader

Mobile Status Bar

Brief explanation: Take the system tray used in plasma-desktop and plasma-netbook and make it work properly on mobile devices such as the N900.

Expected results: A functional system tray with battery, networking, etc. plasmoids working along with ability to configure the entries in it.

Knowledge prerequisite: C++, Qt

Mentor: Alexis Menard

Global Menu Bar

Brief explanation: A Plasma panel containment that provides a MacOS-style menu bar

Expected results: The menu bar containment should support showing the application menu and work with Qt/KDE apps as well as Gtk+ apps. See http://frinring.wordpress.com/2009/01/29/mac-style-menubar-for-kde-4-and-others/

Knowledge prerequisite: C++, Qt

Mentor: Aaron Seigo

Plasma Media Center - Media Browser backends and API

Brief explanation: Low level layer to allow browsing media content from web services directly from the media browser applet.

Expected results: Continue what is already there about the media browser backends and dataengine backends and make them cooperate in order to correctly retrieve media contents from web services like YouTube, Flickr, Picasa...

Knowledge prerequisite: C++, Qt, Plasma API is a relevant bonus

Mentors: Alessandro Diaferia, Marco Martin

Plasma Media Center - Ui re-styling

Brief explanation: A re-design of the Media Center Ui in order to guarantee a great user experience.

Expected results: Taking advantage of the QtDeclarativeUi framework the aim is to provide an excellent user experience in accessing local and remote media contents through Plasma.

Knowledge prerequisite: C++, Qt [,Plasma API, QtDeclarativeUi]

Mentors: Marco Martin, Artur Souza, Alessandro Diaferia

Phonon

Abstraction library for sound and video support. Used by KDE notifications, Amarok, Dragon Player and Qt Software.

Website - Mailing list - IRC channel: #phonon on Freenode.

This year Phonon projects are going to be hosted under the VideoLAN banner. See their webpage for ideas.

High-Level Capture API for Phonon (read: Webcam Support)

High Level Capture API for Phonon

Project: Project: Phonon-VLC improvements and test

Phonon-VLC

Project: Phonon API for low-level PCM I/O

Phonon API for low level PCM

Project: Phonon API for implementing effects in applications

Phonon API for Effects in Apps

Kate

Kate is a powerful programmer's editor.

Website - Mailing list - IRC channel: #kate on Freenode.

Project: Vim-like Swap File

Brief explanation: Add swap file support, like vim has, to limit the effects of crashes.

Expected results: Kate, KWrite, etc. should be able to recover (most of) what was written after last save in case of a crash or power failure.

IMHO the dialog presented to the user for recovery could be a bit better than vim's, too: for example, if the file hasn't been modified it doesn't make sense to offer to restore it. A "view diff" option would be extra awesome. --Chani 13:44, 28 February 2010 (UTC)

Knowledge Prerequisite: Knowledge of C++ and Qt is a requirement.

Mentor: Christoph Cullmann <[email protected]>

Project: Kobby (Collaborative editing)

Brief explanation: Document uploading support, allow KTextEditor parts to control undo/redo, infinote server start/stop ability, connection history/management, other UI improvements.

Proposals can feature multiple of these ideas, and are open to ideas not listed here.

Project Page: http://kobby.greghaynes.net/

Technical Details: Technical details for some of the ideas can be found on http://kobby.greghaynes.net/documentation/gsoc-2010-ideas

Knowledge Prerequisite: C++, Qt

Mentor Knowledge Prerequisite: (Preferred but not required) KTextEditor development and or usability experience.

Mentor: Needed.

Konqueror

Mailing-list: https://mail.kde.org/mailman/listinfo/kfm-devel/ https://mail.kde.org/mailman/listinfo/kfm-devel/

Project Page: http://www.konqueror.org/

Project: Integrate Nepomuk in bookmarks

Brief explanation: Make a taggable bookmark system like that of Firefox, taggable and with searching for these tags in the location bar. This should integrate with the KDE semantic system Nepomuk.

Expected results:

Knowledge Prerequisite:

Mentor: ask in the mailinglist kfm-devel

Project: Akonadi-Integration, Syncing bookmarks and history over Internet

Brief explanation: write an Akonadi-modul that enables syncing of konqueror bookmarks from pc to laptop for instance

Expected results:

Knowledge Prerequisite:

Mentor: ask in mailinglist kfm-devel

Project: Mozilla Weave

Brief explanation: Weave is a new Mozilla project / Firefox addon that allows one to synchronize browser tabs, history, bookmarks, passwords & preferences between different computers via a publicly available server. The communications is encrypted and also all data gets encrypted on the client before transferring to the server so privacy is protected. Further it is completely open source so everyone is able to host ones own server, get & modify the code and so on.

Expected results:

Knowledge Prerequisite:

Mentor: ask in mailinglist kfm-devel

Project: Web scripts

Brief explanation: Implement support for modifying web page javascript and css like firefox greasemonkey and stylish, respectively. It should ideally support greasmonkey and stylish scripts as-is.

Expected results:

Knowledge Prerequisite:

Mentor: ask in mailinglist kfm-devel

Krita

Krita is a KDE program for sketching and painting, offering an end–to–end solution for creating digital painting files from scratch by masters.

Mailing-list: https://mail.kde.org/mailman/listinfo/kimageshop/ Project Page: http://www.krita.org/ Irc channel: #koffice on irc.freenode.net Forums: http://forum.kde.org/viewforum.php?f=136

Project: transform tool for Krita

Brief explanation: While Krita already has two transform tools, neither is sufficient for the needs of digital artists working on concept art, comics or textures. We need a transformation tool that can rotate, scale, shear and freeform transform. This project entails a careful design specification stage in consultation with the Krita developers: the student should contact the krita developers beforehand. The implementation will likely be challenging both from a user interface and from an algorithm point of view.

Expected results: a working, polished transform tool

Knowledge Prerequisite: C++, Qt, digital art, image manipulation algorithms.

Mentor:

Project: Tagging and management for Krita resources

Brief explanation: Krita comes with a rich selection of resources: patterns, gradients, brushes, brush presets, soon materials for texture painting. These resources need to be managed: added, deleted, changes and tagged. Existing tagging specifications exist for Gimp and for Viaduct, and Krita should be compatible here. Integration with Get Hot New Stuff and Nepomuk are important aspects of this project. There will be data structures and gui work.

Expected results: A functioning implementation of resource management and tagging.

Knowledge Prerequisite: C++, Qt, digital art.

Mentor:

Project: Guided Painting

Brief explanation: Krita has the beginning of a guided painting system, with guides, levels of magnetism and plugins for guide types. This project is about finishing the implementation of this system: guide management, guide selection, new guide types. The guides are intended replace the geometric tools, so their usability must be very good. Both algorithm and gui work.

Expected results: A polished guided painting system.

Knowledge Prerequisite: C++, Qt, digital art.

Mentor:

Project: Color Selectors/dialogs

Brief explanation: Krita has only very basic color selectors. Two things are needed: a full-blown color selection dialog that makes use of the colorspaces provide by the pigment library and that can shown out-of-gamut colors, and a collection of innovative, polished color selectors geared towards the way painters work. The selectors should be availabe as dockers, but also be pluggable into the quick selection palette. In order to write a proposal, the student will have to study available literature on color selection, as well as give an overview of selectors implemented in other applications like mypaint, gimp, scribus and others.

Expected results: A new set of color selectors.

Knowledge Prerequisite: C++, Qt

Mentor:

KDE Finance

KDE Finance is an emerging group of applications dedicated to financial topics, such as Personal Finances Management, Invoices Management, Point of Sales...

Plasma Dashboard in Skrooge

Skrooge is a Personal Finances Manager, a part of KDE extragear.

Brief explanation: Skrooge currently has a module called Dashboard that contains several widgets showing various information about your financial situation. However we are reinventing the plasma wheel in many areas, so we'd like to switch it to plasma. The dashboard could become a generic componenet that would also be used by other applications (kontact ?)

Expected results:

• implement a newspaper view that will receive skroogoids (linked with this other GSOC project).
• write a dataengine providing data from the current skrooge file (which is in fact an SQLite database).
• create some skroogoids that should be displayed in the newspaper view. Ability to display them on the desktop, without skrooge being opened is something to be discussed (a skrooge file may be password protected using QCA, no idea how this could be handled).
• save the dashboard config inside the Skrooge file (currently not supported by plasma, IIRC)

Knowledge Prerequisite: C++, SQLite, optionnally a scripting language supported by plasma

Mentor: Guillaume DE BURE, + someone from plasma team (?)

Project: Financial information in Nepomuk

Brief explanation: The finance applications generate a lot of data and information that could be included into Nepomuk and then leveraged with other information. This project is about creating a connector that can be used by these applications and work with the apps developer to create the taxonomies and other necessary elements to store this information in Nepomuk and to update it when necessary.

Expected results: Have a library to be included by finance apps to feed contacts and transaction data into Nepomuk.

Knowledge Prerequisite: C++, Qt

Mentor: Alvaro Soliverez + probably someone from Nepomuk

Rekonq

Project: Rekonq with WebKit 2

Brief explanation: Rekonq currently use the regular WebKit model where user input and rendering are done synchronously in response to events of the event loop. A research project of WebKit aim a using asynchronous API between the user agent and the engine, this is called WebKit 2. This project is about improving WebKit 2 to support the use cases of Rekonq, and prototype a version of Rekonq based on WebKit 2.

Expected results: A branch of Rekonq based on WebKit 2.

Knowledge Prerequisite: C++, Qt

Mentor: Benjamin Poulain + hopefully some help from Andrea

ownCloud

An open personal cloud which runs on your personal server. It enables accessing your data from all of your devices. Sharing with other people is also possible. It support automatic backups, versioning and encryption.

Website - Mailing list - IRC channel: #owncloud on Freenode.

Project: Syncing client

Brief explanation: Build a client to sync your ownCloud files with your local disc to enable offline use.

Expected results: Development of an application you run on your local PC. This applications syncs local folders with folders on your personal ownCloud server everytime you are online. This applications needs a GUI written in KDE/Qt to configure the ownCloud url, folders, login and password. The applications sits in the systray and informs the user about the syncing progress or sync conflicts. The idea is that the clients mounts the ownCloud folders via WebDAV into a "hidden" directory and syncs the folders via rsync or an own syncing script. Errors should be reported to the user.

Knowledge Prerequisite: Python, Ruby, PHP or C++ and KDE/Qt depending on the technology you choose for the desktop syncing client. Enthusiasm for Cloud/Desktop integration and trying new things.

Mentor: Frank Karlitschek <[email protected]>.

Project: Photo gallery

Brief explanation: Build a photo gallery plugin for ownCloud

Expected results: Development a photo gallery plugins which reads the photos from a photo folder in you ownCloud file storage and automatically creates different beautiful photo galleries. The idea is that you just save you photos with your KDE application in you ownCloud photo folder via webdav and you automatically get a photo gallery which you can show to your friends. You don´t need to upload you photos to an online photo service. You can present your photos to the world directly without the need to use non free online services.

Knowledge Prerequisite: Knowledge PHP, HTML, CSS and MySQL. Enthusiasm for Cloud/Desktop integration and trying new things.

Mentor: Frank Karlitschek <[email protected]>.

KDE SDK

Project: Umbrello QGraphicsView

Brief explanation: Finish the QGraphicsView port of Umbrello

Expected results: A working Umbrello using QGraphicsView and all features in the current QCanvas version

Knowledge Prerequisite: c++, Qt, QGraphicsView

Mentor: Jonathan Riddell <[email protected]>.

Project: KDE Git front-end and KPart

Brief explanation: Considering the increasing use of Git in KDE, the usual hard learning curve mainly for newbies, and the need for Git integration in SDK tools it would be useful to implement a KDE-based user-friend front-end for Git. Such tool could provide a graph about repository cloning dependency, features for automating the pull/push and merge requests. In addition, a KPart could be provided to make these features available for use in other SDK tools like KDevelop and Plasmate. The KPart should be flexible enough to meet demands from general visualization to fine-grained operations like pull/push, conflict resolution, and merge requests.

Expected results: A KDE Git front-end tool which automate the basic Git operations and make them available in an intuitive and user-friend way. Furthermore, the implementation should use a KPart developed as part of the project which provides a flexible enough API for use in other SDK tools.

Knowledge Prerequisite: Qt - C++. Previous KDE development experience and Git use knowledge is desirable.

Mentor: Sandro Andrade <[email protected]>

KDE Language Bindings

Project: Documentation Extractor

Brief explanation: Write a plugin for the 'smokegen' tool that will parse headers and source files, extract documentation comments and convert them to a suitable format for using with languages such as Ruby, Perl, PHP, C# or JavaScript. Convert any embedded code snippets to the target language.

Expected results: Documentation produced for one or more of the languages above (the more the better!), and possibly documentation viewer tools too.

Knowledge Prerequisite: C++, parsers, Qt

Mentor: Richard Dale <[email protected]>.

Solid

Project: Network Device Detection & Desktop Integration for UPnP

Bried explanation: Universal Plug and Play is a set of technologies for the digital home. Network transparancy has always been a core concept in KDE with the KIO slave technology. Solid is gaining support for network device detection and enumeration as well as multiple backends.

Expected results: The goal of this project is to develop and stabilize a UPnP backend using an existing library, framework or daemon. To proof the usefullness of these new solid features example integration of UPnP in existing KDE SC applications is expected.

Knowledge Prerequisite: Solid, KIO, UPnP

Mentor: Kévin Ottens, Fredrich Kossebau