KDE TechBase - User contributions [en]

Schedules/KDE4/4.6 Feature Plan

2010-10-24T11:09:35Z

Grundleborg: /* kdenetwork */

This is a list of planned features for the SC 4.6 release.

See also:

*[[Schedules/KDE4/4.6 Release Schedule]]
*[[Schedules/KDE4/4.6 Release Goals]]
*[[Schedules/KDE4/4.5 Feature Plan]] (previous major release)

 Legend:

*todo => not started yet
*in-progress => started, but not completed yet
*done => completed

__TOC__

 

= kdebase-apps =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|Konsole|Move to KTabWidget|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureInProgress|Dolphin|Faceted browsing via Nepomuk|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|Dolphin|Searching support for non-indexed files|peter.penz19@gmail.com|Peter Penz}}
{{FeatureInProgress|Dolphin|Git-plugin (implemented by Sebastian Dörner and Johannes Steffen)|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin| Resizeable columns in the column-view|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin| Allow leading zeros when renaming multiple files (implemented by Matthias Fuchs)|peter.penz19@gmail.com|Peter Penz}}
|}

 

= kdebase-runtime =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Plasma|Plasma KPart|ry@n.rix.si|Ryan Rix}}
{{FeatureInProgress|Plasma|Declarative AppletScript to write QML plasmoids|mart@kde.org|Marco Martin}}
{{FeatureInProgress|Plasma|Optimize the Newspaper containment for the use with touchscreens and the Plasma KPart|mart@kde.org|Marco Martin}}
{{FeatureDone|KWin|Focus tracking for the zoom plugin (uses kaccessible)|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KWin|Extend mouse tracking modes for the zoom plugin|mail@dipe.org|Sebastian Sauer}}
{{FeatureInProgress|Nepomuk Backup & Sync| Provide Backup and Sync capabilities to Nepomuk|handa.vish@gmail.com|Vishesh Handa}}
|}

 

= kdebase-workspace =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
|-
! style="text-align: center;" colspan="4" | Plasma
{{FeatureInProgress|libtaskmanager / tasks-applet| support for Windows 7 like launchers |akreuzkamp@web.de|Anton Kreuzkamp}}
{{FeatureInProgress|notifications| rework notification applet appearance |mart@kde.org|Marco Martin}}
{{FeatureInProgress|notifications| make various dataengines use Plasma::Storage |mart@kde.org|Marco Martin}}
{{FeatureDone|plasma-desktop| UI for editing activity name and icon|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureTodo|plasma-desktop| add some default activities|fux@kde.org|Mario Fux}}
{{FeatureTodo|plasma| finish support for activity templates | |??}}
|-
! style="text-align: center;" colspan="4" | KWin
{{FeatureInProgress|dashboard effect| new effect for Plasma dashboard |ademmer@opensuse.org|Andreas Demmer}}
{{FeatureInProgress|kwin/ksmserver| activity sessions |chanika@gmail.com|Chani}}
{{FeatureTodo|libtaskmanager/kwin?| combine the three window-contextmenu codebases into one | |??}}
|}

 

= kdelibs =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureDone|libnepomuk|Convenience operator overloads for query construction|trueg@kde.org|Sebastian Trueg}}
{{FeatureDone|libnepomuk|New query flags and improved handling of full text matching scores including sorting|trueg@kde.org|Sebastian Trueg}}
{{FeatureTodo|kdeui|Generic find bar widget|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureDone|kdeui|Allow getting and setting the size of the pixmap cache in KImageCache|2kmm@gmx.de|Manuel Mommertz}}
{{FeatureDone|katepart|scripted actions|dhaumann@kde.org|Dominik Haumann}}
{{FeatureDone|katepart|QAccessibleInterface's for document+cursor|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|libplasma|PluginLoader class|ry@n.rix.si|Ryan Rix}}
{{FeatureDone|libplasma|Allow SVGs to use systemcolors before rendering|2kmm@gmx.de|Manuel Mommertz}}
{{FeatureInProgress|libplasma|DeclarativeWidget to load QML scenes in Plasma|mart@kde.org|Marco Martin}}
{{FeatureInProgress|libplasma|finish up the gsoc project about Plasma::Storage service|mart@kde.org|Marco Martin}}
{{FeatureInProgress|libnepomuk/KIO|Search excerpts|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|libnepomuk|Standardqueries for convenience|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|libnepomuk|GUI elements for resource/file searching including faceted browsing|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|libnepomuksync|Sync library to be used in BackupSync, Strigi, Akonadi, WebExtractor and Removable Media|handa.vish@gmail.com|Vishesh Handa}}
{{FeatureInProgress|kdecore|Add more possible synchronization primitives to KSharedDataCache to expand OS support. POSIX Semaphores Contributed by Alberto Villa of the FreeBSD project. Windows support may still occur as well.|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|kdecore|Add fallback to QCache<QString,QByteArray> in KSharedDataCache.|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|kdecore|Add cache-wide timestamp to KSharedDataCache.|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|kdecore|Add ability to make KSharedDataCache strictly read-only for laptop support.|mpyne@kde.org|Michael Pyne}}
{{FeatureInProgress|kdeui|Social About Dialog|teo@kde.org|Teo Mrnjavac}}
|}

 

= kdeedu =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Marble|GPX import of routes|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Route printing (map and directions, configurabe)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Route state saving and restoring|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Convert MarbleRunners to plugins|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|worldwide and offline routing|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Extend MarbleRunner interface to handle reverse geocoding and routing requests; Display of alternative routes|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Routing API|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Implement sun locator blendings as derived classes of Marble::Blending|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureTodo|Marble|Separate thread for tile loading and texture blending (not texture mapping at the moment) for more smooth browsing|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureTodo|Marble|Tile loading "read ahead" when idle, prerequisite: threaded tile loading|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureDone|Marble|Tile download along the route for offline usage|akssps011@gmail.com|Siddharth Srivastavah}}
{{FeatureInProgress|Marble|Turn-by-turn navigation mode|akssps011@gmail.com|Siddharth Srivastavah}}
{{FeatureTodo|Marble|Multi threaded texture mapping|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureDone|Marble|Improve GeoData API|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureDone|Marble|Convert Gps tracking to GeoDataDocument|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureDone|Marble|Provide a treeModel for GeoDataDocuments|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureDone|Marble|Draw the geometries of multiple GeoDataDocuments|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureInProgress|Marble|Load Pnt vector data files as GeoData|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureInProgress|Marble|Manipulate Gps track data|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureDone|Cantor|Backend for GNU Octave|miha.cancula@gmail.com|Miha Čančula}}
{{FeatureTodo|Cantor|Merge R improvement branch|alexanderrieder@gmail.com|Alexander Rieder}}
{{FeatureTodo|Cantor|Variable management panel|alexanderrieder@gmail.com|Alexander Rieder}}
{{FeatureDone|Kalzium|Port Kalzium to use QGV based periodic table widget|mhanwell@kde.org|Marcus D. Hanwell}}
{{FeatureDone|KAlgebra|Implicit functions plot|percy.camilo.ta@gmail.com|Percy Aucahuasi}}
{{FeatureDone|KAlgebra|Improved execution speed on the calculator|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureDone|KAlgebra|Better integration between the Console and the Plotting facilities|aleixpol@kde.org|Aleix Pol Gonzalez}}
{{FeatureInProgress|KStars|OpenGL rendering support for KStars|akarshsimha@gmail.com|Harry de Valence, Akarsh Simha}}
{{FeatureInProgress|KStars|Better designed object database|akarshsimha@gmail.com|Victor Carbune, Akarsh Simha}}
{{FeatureInProgress|KStars|Star Hop Generator|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureDone|Kig|LaTeX/TikZ exporter|miha.cancula@gmail.com|Miha Čančula}}
|}

 

= kdemultimedia =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|JuK|Remove Qt/KDE3 support lib requirements|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|JuK|Allow setting covers directly from URLs supported by KIO - drag/drop already allows this however|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|JuK|Add MPRIS support to JuK so that the NowPlaying applet doesn't need to special-case JuK.|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|JuK|Update JuK's MusicBrainz support to a modern version of MusicBrainz.|mpyne@kde.org|Michael Pyne}}

|}

 

= kdegames =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureDone|libkdegames|Import KGameRenderer framework and [[Projects/Games/Porting|port games]] to this unified rendering infrastructure.|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureInProgress|Kigo|Fix KNewStuff provider issues|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureDone|Palapeli|Import Goldberg slicer as the new default slicer plugin.|loehnert.kde@gmx.de|Johannes Loehnert}}
{{FeatureDone|Palapeli|Update libpala API. Improve usability of "Create new puzzle" dialog.|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|Kajongg|Docbook: Describe the basic game, until now I supposed the player already knows how to play Mah Jong.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Tiles can be discarded with drag&drop.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Make robot player AI more intelligent.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Make tiles in the hand larger and the wall tiles smaller for better playability on small screens.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kajongg|Make games suspendable/resumable.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureInProgress|Kajongg|Animate moving tiles.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureTodo|Kajongg|Add more rulesets like other Classical Chinese variants and the international tournament rules.|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|KGoldrunner|Save and restore the current control-mode, keyboard-control option and game-speed settings.|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|KGoldrunner|Add a keyboard-mode option to start moving when a direction-key is pressed and stop when it is released. Support multiple keys being pressed.|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|Klickety|An adaptation of the "clickomania" game.Rewrite the kde3 version.|shuizhuyuanluo@126.com|Ni Hui}}
{{FeatureInProgress|Klickety|IMerge KSame into Klickety.|shuizhuyuanluo@126.com|Ni Hui}}
{{FeatureInProgress|Kolf|Port to KGameRenderer, cleanup all QGraphicsView- and physics-related code (and physics engine), incorporate ideas from Kolf-NG.|majewsky@gmx.net|Stefan Majewsky}}
|}

 

= kdesdk =

{| cellspa/cing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Lokalize|Integrate snowball stemmer for glossary|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Continue implementing XLIFF spec|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Segmentation [editing] functionality|shafff@NOSPAMukr.net |Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Remote translation memories|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Integrate with nepomuk (fast stats retrieval, tag cloud - incl sharing!)|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|loading compressed files and then saving them back in the original compression format (bug 65518)|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Nepomukshell|New Nepomukshell development tool allowing to browse and debug Nepomuk data|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|Dolphin|Git plugin|sebastian@sebastian-doerner.de|Sebastian Doerner}}
|}

 

= kdeutils =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Ark|Add a "Preview with..." context menu item|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Add an options dialog (maybe)|haraldhv@stud.ntnu.no|Harald Hvaal}}
{{FeatureTodo|Ark|Add feedback for the latest operation in the status bar|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Get rid of the Observer code in Kerfuffle|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Make error reporting work as expected in Kerfuffle|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Make Kerfuffle really thread-safe (and use threads in less places)|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Make the internal previewer optional|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Simplify Kerfuffle's API (jobs, interfaces etc) and try to make it stable|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Ark|Support for custom options from the compression interface (eg. a slider for selecting compression level for rar files)|haraldhv@stud.ntnu.no|Harald Hvaal}}
{{FeatureTodo|Ark|Try multiple plugins for each archive type before failing|kubito@gmail.com|Raphael Kubo da Costa}}
{{FeatureTodo|Okteta|Add a general KPart adapter to Kasten, than finish port of Okteta KPart to Okteta Kasten|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add global toggle option for the offset display, hex or decimal|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add Kate-like combined dialogs to query for actions on files|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add Kate-like search tool|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add Okular like embedded notifications|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for import by drop, both url and data|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for memory mapping of files and 64-bit addressing|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for jobs like io, printing, string search or filter|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add view profiles, incl. editor/manager|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|copy again puts also a value or char variant of the data to clipboard|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Improve the titels of the changes to the bytearray to be more descriptive, best using ids to avoid text string|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Make all user interaction in the KastenCore managers plugin-based|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Merge row and column widgets into one|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Store bookmarks|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Store bookmarks and other view settings for next load|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|printer-applet|Restore feature parity with KDEPrint3 where possible.||Jonathon Riddell, John Layt}}
{{FeatureTodo|Okteta|Add view profiles|kossebau@kde.org|Friedrich W. H. Kossebau}}
|}

 

= kdepim =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|Kontact|Plasma-based Summary Page|ry@n.rix.si|Ryan Rix}}
|}

 

= kdeaccessibility =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureDone|KAccessible|Added a dbus-service and a QAccessibleBridgePlugin for focus tracking (used in KMagnifier and the KWin zoom plugin).|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KMagnifier|Follow Focus Mode for Focus Tracking (uses kaccessible).|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KAccessible|Added Screenreader (uses speech-dispatcher)|mail@dipe.org|Sebastian Sauer}}
|}

 
= kdeartwork =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureDone|KDE Asciiquarium|Added a new ASCII sprite (a submarine). Contributed by Ryan Meldrum.|mpyne@kde.org.|Michael Pyne}}
|}

 
= kdeplasma-addons =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureDone|Shelf|Automatic sizing of the popup|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|Shelf|Setting a custom popup icon|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureTodo|Shelf|Cascading popup menus for folders|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|Shelf|Keyboard navigation|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureDone|Shelf|Search completion|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|libLancelot-datamodels|Akonadi integration|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureTodo|libLancelot-datamodels|Folder contents sorting|ivan.cukic@kde.org|Ivan Čukić}}
{{FeatureInProgress|Lancelot|Theme improvements, animations|ivan.cukic@kde.org|Ivan Čukić}}
|}

 
= kdenetwork =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|krfb|Refactor Core to make it more maintainable/extensible|grundleborg@googlemail.com.|George Goldberg}}
{{FeatureInProgress|krfb|Telepathy Tubes support|grundleborg@googlemail.com.|George Goldberg}}
{{FeatureInProgress|krfb|UI Improvements to support new features/deal with some existing bug reports|grundleborg@googlemail.com.|George Goldberg}}
|}

Schedules/KDE4/4.6 Feature Plan

2010-10-24T11:08:41Z

Grundleborg: more krfb features

Schedules/KDE4/4.6 Feature Plan

2010-10-23T18:36:22Z

Grundleborg: add krfb

Contribute/Bugsquad/BugDays/KritaDay1/245143

2010-08-22T21:11:12Z

Grundleborg: /* {{Bug|245143}} */

=== {{Bug|245143}} ===

;Description:
: Krita hangs when you paint with Mixing Brush outside the canvas

* Reproduceable. Hangs after painting outside the canvas. --[[User:Slangkamp|Slangkamp]] 07:25, 22 August 2010 (UTC)

* Confirmed. [[User:Lemma|Lemma]]

* Confirmed. [[User:Grundleborg|Grundleborg]]

Contribute/Bugsquad/BugDays/KritaDay1/247006

2010-08-22T20:54:21Z

Grundleborg: /* {{Bug|247006}} */

=== {{Bug|247006}} ===

;Description:
: Krita crashed when requesting Print Preview

* No crash on print preview with several images, but I don't have a real printer connected. --[[User:Slangkamp|Slangkamp]] 07:56, 22 August 2010 (UTC)

* Can't reproduce either (and I *do* have a printer attached) [[User:Grundleborg|Grundleborg]]

Contribute/Bugsquad/BugDays/KritaDay1/243043

2010-08-22T20:52:42Z

Grundleborg: /* {{Bug|243043}} */

=== {{Bug|243043}} ===

;Description:
: High memory load under normal usage

* I can see RAM usage increasing if I try the operations the original reporter did. However I couldn't observe a rise as high as he did. Unfortunately I fear tracking RAM usage that way might be a bit too fuzzy. Didn't comment on the bug as I wasn't sure if it's actually worth it. [[User:Lemma|Lemma]]

* No noticeable ram usage increase for any of the operations the original poster listed. [[User:Grundleborg|Grundleborg]]

Contribute/Bugsquad/BugDays/KritaDay1/247954

2010-08-22T20:52:17Z

Grundleborg: /* {{Bug|247954}} */

=== {{Bug|247954}} ===

;Description
: krita hangs when using the deform tool

* Painted for some time and it crashed. Attached backtrace to bug. --[[User:Slangkamp|Slangkamp]] 07:01, 22 August 2010 (UTC)

* I can reproduce this bug as well. Backtrace looks equal. Attached a comment to the bug. [[User:Lemma|Lemma]]

* Can't reproduce. Tried deforming for about 5 mins with no crash. [[User:Grundleborg|Grundleborg]]

Contribute/Bugsquad/BugDays/KritaDay1/243043

2010-08-22T20:46:26Z

Grundleborg: /* {{Bug|243043}} */

Contribute/Bugsquad/BugDays/KritaDay1/247954

2010-08-22T20:35:26Z

Grundleborg: /* {{Bug|247954}} */

Contribute/Bugsquad/BugDays/KritaDay1

2010-08-22T20:26:26Z

Grundleborg: /* Sign-in */

==Introduction==
This bug day will take place on Sunday, August 22nd 2010, but feel free to start early. The aim of this bug day is to test the specific Krita bugs on as many different platforms as possible.

===Goals of this Bug Day===

* If possible, triage every bug in the list. Different bugs can behave differently depending on the platform you run Krita on.
* Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)
* You should be working with KDE SC 4.4 and you absolutely HAVE TO use Krita compiled from trunk. Instructions are available on the following page: http://wiki.koffice.org/index.php?title=Building/Building_KOffice

{{Note|If you're having trouble getting Krita to compile, simply ask on our IRC channel. Boudewijn Rempt and others will be around to help everyone get started.}}
{{Warning|Please specify anything you notice which might help the developers decide whether a bug is already fixed or still present no your system.}}

===Keep this page updated!===
After triaging a bug which is still reproducible for you it would be great if you could add yourself to the CC field in bugzilla to get informed about updates. This way you can see if it's worth retrying if the bug has gone away in later versions.

==Sign-in==
Tell developers what you are testing with. Please note your version of KDE SC (or the revision number if running from trunk). Please also note your version of Krita as well as the CPU, the amound of RAM, your video hardware and drivers you're running with.

Please give distro/version or SVN branch/trunk with revision below:

{|
|-
!IRC Nickname !! KDE version !! Krita version !! CPU !! RAM !! Graphics hardware !! Driver
|-
|[[User:Lemma|Lemma]] || r1160177 || r1166473 || Q6600 || 8 GB || NVIDIA 8600 GTS || binary 256.35
|-
| slangkamp || 4.4.5 || svn trunk || Core i5 || 4 GB || Radeon HD 545v || fglrx
|-
| [[User:Grundleborg|grundleborg]] || svn from 4.5 RC time || r116679 || Core 2 Duo || 3GB || Intel || xserver-xorg-intel 2.9.1
|}

{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

== Bugs ==

The following list contains all bugs we're going to triage during this BugDay. Please simply your experience with the bug below the bug.

Please note that this is a page layout designed to reduce the number of edit conflicts on this page. Each section is its own subpage. The best way to work with this is to enable section editing by going to "My preferences" > "editing" > "Enable section editing via [edit] links". When you click edit you will automatically edit the subpage.

{{:Contribute/Bugsquad/BugDays/KritaDay1/247954}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/243043}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/241289}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/222939}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/247006}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/235278}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/217811}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/247434}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/245143}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/243687}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/242505}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/239836}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/247791}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/245565}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/239977}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/231950}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/214632}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/245127}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/244910}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/242800}}

Contribute/Bugsquad/BugDays/KritaDay1

2010-08-22T20:19:08Z

Grundleborg: /* Sign-in */

==Introduction==
This bug day will take place on Sunday, August 22nd 2010, but feel free to start early. The aim of this bug day is to test the specific Krita bugs on as many different platforms as possible.

===Goals of this Bug Day===

* If possible, triage every bug in the list. Different bugs can behave differently depending on the platform you run Krita on.
* Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)
* You should be working with KDE SC 4.4 and you absolutely HAVE TO use Krita compiled from trunk. Instructions are available on the following page: http://wiki.koffice.org/index.php?title=Building/Building_KOffice

{{Note|If you're having trouble getting Krita to compile, simply ask on our IRC channel. Boudewijn Rempt and others will be around to help everyone get started.}}
{{Warning|Please specify anything you notice which might help the developers decide whether a bug is already fixed or still present no your system.}}

===Keep this page updated!===
After triaging a bug which is still reproducible for you it would be great if you could add yourself to the CC field in bugzilla to get informed about updates. This way you can see if it's worth retrying if the bug has gone away in later versions.

==Sign-in==
Tell developers what you are testing with. Please note your version of KDE SC (or the revision number if running from trunk). Please also note your version of Krita as well as the CPU, the amound of RAM, your video hardware and drivers you're running with.

Please give distro/version or SVN branch/trunk with revision below:

{|
|-
!IRC Nickname !! KDE version !! Krita version !! CPU !! RAM !! Graphics hardware !! Driver
|-
|[[User:Lemma|Lemma]] || r1160177 || r1166473 || Q6600 || 8 GB || NVIDIA 8600 GTS || binary 256.35
|-
| slangkamp || 4.4.5 || svn trunk || Core i5 || 4 GB || Radeon HD 545v || fglrx
|-
| [[User:Grundleborg|grundleborg]] || svn from 4.5 RC time || r116679 || Core 2 Duo || 3GB || Intel || Intel something-or-other
|}

{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

== Bugs ==

The following list contains all bugs we're going to triage during this BugDay. Please simply your experience with the bug below the bug.

Please note that this is a page layout designed to reduce the number of edit conflicts on this page. Each section is its own subpage. The best way to work with this is to enable section editing by going to "My preferences" > "editing" > "Enable section editing via [edit] links". When you click edit you will automatically edit the subpage.

{{:Contribute/Bugsquad/BugDays/KritaDay1/247954}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/243043}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/241289}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/222939}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/247006}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/235278}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/217811}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/247434}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/245143}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/243687}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/242505}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/239836}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/247791}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/245565}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/239977}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/231950}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/214632}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/245127}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/244910}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/242800}}

Contribute/Bugsquad/BugDays/KritaDay1

2010-08-22T20:18:48Z

Grundleborg: /* Sign-in */

==Introduction==
This bug day will take place on Sunday, August 22nd 2010, but feel free to start early. The aim of this bug day is to test the specific Krita bugs on as many different platforms as possible.

===Goals of this Bug Day===

* If possible, triage every bug in the list. Different bugs can behave differently depending on the platform you run Krita on.
* Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)
* You should be working with KDE SC 4.4 and you absolutely HAVE TO use Krita compiled from trunk. Instructions are available on the following page: http://wiki.koffice.org/index.php?title=Building/Building_KOffice

{{Note|If you're having trouble getting Krita to compile, simply ask on our IRC channel. Boudewijn Rempt and others will be around to help everyone get started.}}
{{Warning|Please specify anything you notice which might help the developers decide whether a bug is already fixed or still present no your system.}}

===Keep this page updated!===
After triaging a bug which is still reproducible for you it would be great if you could add yourself to the CC field in bugzilla to get informed about updates. This way you can see if it's worth retrying if the bug has gone away in later versions.

==Sign-in==
Tell developers what you are testing with. Please note your version of KDE SC (or the revision number if running from trunk). Please also note your version of Krita as well as the CPU, the amound of RAM, your video hardware and drivers you're running with.

Please give distro/version or SVN branch/trunk with revision below:

{|
|-
!IRC Nickname !! KDE version !! Krita version !! CPU !! RAM !! Graphics hardware !! Driver
|-
|[[User:Lemma|Lemma]] || r1160177 || r1166473 || Q6600 || 8 GB || NVIDIA 8600 GTS || binary 256.35
|-
| slangkamp || 4.4.5 || svn trunk || Core i5 || 4 GB || Radeon HD 545v || fglrx
| [[User:Grundleborg|grundleborg]] || svn from 4.5 RC time || r116679 || Core 2 Duo || 3GB || Intel || Intel something-or-other
|}

{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

== Bugs ==

The following list contains all bugs we're going to triage during this BugDay. Please simply your experience with the bug below the bug.

Please note that this is a page layout designed to reduce the number of edit conflicts on this page. Each section is its own subpage. The best way to work with this is to enable section editing by going to "My preferences" > "editing" > "Enable section editing via [edit] links". When you click edit you will automatically edit the subpage.

{{:Contribute/Bugsquad/BugDays/KritaDay1/247954}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/243043}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/241289}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/222939}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/247006}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/235278}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/217811}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/247434}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/245143}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/243687}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/242505}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/239836}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/247791}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/245565}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/239977}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/231950}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/214632}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/245127}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/244910}}

{{:Contribute/Bugsquad/BugDays/KritaDay1/242800}}

Contribute/Bugsquad/BugDays/DolphinDay1

2010-08-01T14:56:21Z

Grundleborg: /* Division of Labour */

==Introduction==
This bug day will take place on Sunday, August 1st 2010, but feel free to start early. The aim of this bug day is to get as many Dolphin-related bugs done as possible. Our target for triage is bugs listed in [http://bugs.kde.org bugs.kde.org] under the product Dolphin.

===Goals of this Bug Day===

* Check if bugs reported for Dolphin which are previously UNCONFIRMED are reproducible.
* If a bug's description is somewhat unclear, try to provide a better step-by-step procedure on how to reproduce it. This will make it easier for developers to find and fix the bug.
* Some bugs may not be reproducible on every installation of KDE. Thus we use a 4-eye principle, having at least 2 triagers look at the bugs before we make any changes on the bugs themselves.
* Some more information on how to mark bugs can be found on [http://techbase.kde.org/index.php?title=Contribute/Bugsquad This page].
* Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)
* You should be working with KDE SC 4 (either 4.4 or newer, preferably 4.5 RC3 or SVN trunk) for testing these bugs.

{{Warning|Always make a note on the bug of what the status is in the version you are testing with (be explicit as to what version of 4 you are using, mentioning whether it is a source build and which distro the packages come from).}}

===Is it a big bug?===
Prioritizing is good. If a major application doesn't work, this should be taken care of.

===Version field===
Keep an eye on what the "Version:" fields say in Bugzilla. If it says "unspecified", change the version field to match what the report says, i.e. to match version the bug was first reported in. Do not change the version number if it is currently set as a number! (ex. from 4.0 to 4.2)

As requested by the Dolphin maintainter, just leave it to the version where the user has reported it, not to the version where it could be reproduced.

===Keep this page updated!===
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can do this with the tag <s>...</s>

==Details==
Please select a period of bugs from the [[#Division_of_Labour|Division of Labour]] section below and mark your name next to it and mark it with your irc nickname to show that you are working on it. When you have completed all the bugs in that section, please mark it as complete.

For each bug, try and reproduce it as described in the report. Then list it in the appropriate section below. '''If you wish to close or mark as duplicate a bug, please list it here even if you have the bugzilla permissions to do so, in order to get a second opinion from another triager. This will help to reduce the number of incorrect actions taken on bugs.'''

==Sign-in==
Tell developers what you are testing with. (If you expect to upgrade between now and Bug Day, put what version you are using now next to the bugs/comments that you put on this page.)

Please give distro/version or SVN branch/trunk with revision below:

{|
|-
!IRC Nickname !! KDE version used for testing
|-
|[[User:Lemma|Lemma]] || KDE SC 4 svn trunk r1157840 ||
|-
|[[User:jtamate|jtamate]] || KDE SC 4 svn trunk rev. 1156755 ||
|-
|[[User:Stephdg|stephdg]] || KDE 4.3.0 with Fedora 10 ||
|-
|[[User:finex|FiNeX]] || KDE 4.4.5, ArchLinux ||
|-
|[[User:Anselmolsm|anselmolsm]] || KDE SC 4 svn trunk r1157874 ||
|-
|[[User:Grundleborg|grundleborg]] || KDE SC 4 svn trunk r1145046 ||
|}

{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==Division of Labour==
Please choose a batch that is not already taken and then query bugs.kde.org for all bugs in that batch. Please mark you irc nickname in the table below to show which batches bugs you are working on to avoid duplication of effort.

The bugzilla query to use for this triage day can be [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number found here].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 5 || [[User:Jtamate|Jtamate]] || done except 214765 || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=182913&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=220518 Query]
|-
| 2 || 5 || [[User:Lemma|Lemma]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=220668&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=224627 Query]
|-
| 3 || 5 ||[[User:Stephdg|stephdg]] || 3 left, 225280 & 225682 done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=225125&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=226250 Query]
|-
| 4 || 5 || [[User:Lemma|Lemma]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=226441&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=227604 Query]
|-
| 5 || 5 || [[User:Lemma|Lemma]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=227975&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=228892 Query]
|-
| 6 || 5 || [[User:finex|FiNeX]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=229148&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=229732 Query]
|-
| 7 || 5 || [[User:finex|FiNeX]] || one left, I'll check it later || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=229816&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=230292 Query]
|-
| 8 || 5 || [[User:Lemma|Lemma]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=230743&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=233271 Query]
|-
| 9 || 5 || [[User:finex|FiNeX]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=233334&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=233748 Query]
|-
| 10 || 5 || [[User:Jtamate|Jtamate]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=233835&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=234474 Query]
|-
| 11 || 5 || [[User:finex|FiNeX]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=234499&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=234755 Query]
|-
| 12 || 5 || [[User:finex|FiNeX]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=234884&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=235338 Query]
|-
| 13 || 5 || [[User:finex|FiNeX]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=235447&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=235789 Query]
|-
| 14 || 5 || [[User:finex|FiNeX]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=235793&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=236829 Query]
|-
| 15 || 5 || [[User:finex|FiNeX]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=236887&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=237303 Query]
|-
| 16 || 5 || [[User:finex|FiNeX]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=237538&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=237855 Query]
|-
| 17 || 5 || [[User:finex|FiNeX]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=238521&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=239059 Query]
|-
| 18 || 5 || [[User:finex|FiNeX]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=239855&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=240283 Query]
|-
| 19 || 5 || [[User:finex|FiNeX]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=240426&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=240904 Query]
|-
| 20 || 5 || [[User:Jtamate|Jtamate]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=240971&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=241313 Query]
|-
| 21 || 5 || [[User:Grundleborg|grundleborg]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=241503&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=242451 Query]
|-
| 22 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=242737&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=243165 Query]
|-
| 23 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=243236&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=243666 Query]
|-
| 24 || 5 || || 244052 done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=243795&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=244104 Query]
|-
| 25 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=244162&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=244514 Query]
|-
| 26 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=244561&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=245039 Query]
|-
| 27 || 5 || || 245083=dupe || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=245056&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=245227 Query]
|-
| 28 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=245262&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=245741 Query]
|-
| 29 || 5 ||[[User:Anselmolsm|anselmolsm]] || starting || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=246005&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=246239 Query]
|-
| 30 || 2 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=246287&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=1 Query]
|}
(Total bugs 147)

== Completed Bugs ==
Below lists the various sections for completed bugs. This aids everyone in double checking each other's work. In addition this allows those of us that don't have bugzilla permissions to list bugs so that the folks with the permissions can follow up.

Please note that this is an experimental layout designed to reduce the number of edit conflicts on this page. Each section is its own subpage. The best way to work with this is to enable section editing by going to "My preferences" > "editing" > "Enable section editing via [edit] links". When you click edit you will automatically edit the subpage.

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs needing Version Field changed}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs with step-by-step Instructions}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs to be marked as RESOLVED}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs to be marked as DUPLICATE}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs to be marked as INVALID}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs to be marked as NEW}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs needing attention from Dolphin developers}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs needing the reporter's feedback}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs needing users with particular setups}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs not related to today}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs related to nepomuk or strigi}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs that you cant do}}

Contribute/Bugsquad/BugDays/DolphinDay1

2010-08-01T14:54:50Z

Grundleborg: meeeeeee

==Introduction==
This bug day will take place on Sunday, August 1st 2010, but feel free to start early. The aim of this bug day is to get as many Dolphin-related bugs done as possible. Our target for triage is bugs listed in [http://bugs.kde.org bugs.kde.org] under the product Dolphin.

===Goals of this Bug Day===

* Check if bugs reported for Dolphin which are previously UNCONFIRMED are reproducible.
* If a bug's description is somewhat unclear, try to provide a better step-by-step procedure on how to reproduce it. This will make it easier for developers to find and fix the bug.
* Some bugs may not be reproducible on every installation of KDE. Thus we use a 4-eye principle, having at least 2 triagers look at the bugs before we make any changes on the bugs themselves.
* Some more information on how to mark bugs can be found on [http://techbase.kde.org/index.php?title=Contribute/Bugsquad This page].
* Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)
* You should be working with KDE SC 4 (either 4.4 or newer, preferably 4.5 RC3 or SVN trunk) for testing these bugs.

{{Warning|Always make a note on the bug of what the status is in the version you are testing with (be explicit as to what version of 4 you are using, mentioning whether it is a source build and which distro the packages come from).}}

===Is it a big bug?===
Prioritizing is good. If a major application doesn't work, this should be taken care of.

===Version field===
Keep an eye on what the "Version:" fields say in Bugzilla. If it says "unspecified", change the version field to match what the report says, i.e. to match version the bug was first reported in. Do not change the version number if it is currently set as a number! (ex. from 4.0 to 4.2)

As requested by the Dolphin maintainter, just leave it to the version where the user has reported it, not to the version where it could be reproduced.

===Keep this page updated!===
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can do this with the tag <s>...</s>

==Details==
Please select a period of bugs from the [[#Division_of_Labour|Division of Labour]] section below and mark your name next to it and mark it with your irc nickname to show that you are working on it. When you have completed all the bugs in that section, please mark it as complete.

For each bug, try and reproduce it as described in the report. Then list it in the appropriate section below. '''If you wish to close or mark as duplicate a bug, please list it here even if you have the bugzilla permissions to do so, in order to get a second opinion from another triager. This will help to reduce the number of incorrect actions taken on bugs.'''

==Sign-in==
Tell developers what you are testing with. (If you expect to upgrade between now and Bug Day, put what version you are using now next to the bugs/comments that you put on this page.)

Please give distro/version or SVN branch/trunk with revision below:

{|
|-
!IRC Nickname !! KDE version used for testing
|-
|[[User:Lemma|Lemma]] || KDE SC 4 svn trunk r1157840 ||
|-
|[[User:jtamate|jtamate]] || KDE SC 4 svn trunk rev. 1156755 ||
|-
|[[User:Stephdg|stephdg]] || KDE 4.3.0 with Fedora 10 ||
|-
|[[User:finex|FiNeX]] || KDE 4.4.5, ArchLinux ||
|-
|[[User:Anselmolsm|anselmolsm]] || KDE SC 4 svn trunk r1157874 ||
|-
|[[User:Grundleborg|grundleborg]] || KDE SC 4 svn trunk r1145046 ||
|}

{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==Division of Labour==
Please choose a batch that is not already taken and then query bugs.kde.org for all bugs in that batch. Please mark you irc nickname in the table below to show which batches bugs you are working on to avoid duplication of effort.

The bugzilla query to use for this triage day can be [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number found here].

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 5 || [[User:Jtamate|Jtamate]] || done except 214765 || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=182913&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=220518 Query]
|-
| 2 || 5 || [[User:Lemma|Lemma]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=220668&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=224627 Query]
|-
| 3 || 5 ||[[User:Stephdg|stephdg]] || 3 left, 225280 & 225682 done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=225125&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=226250 Query]
|-
| 4 || 5 || [[User:Lemma|Lemma]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=226441&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=227604 Query]
|-
| 5 || 5 || [[User:Lemma|Lemma]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=227975&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=228892 Query]
|-
| 6 || 5 || [[User:finex|FiNeX]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=229148&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=229732 Query]
|-
| 7 || 5 || [[User:finex|FiNeX]] || one left, I'll check it later || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=229816&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=230292 Query]
|-
| 8 || 5 || [[User:Lemma|Lemma]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=230743&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=233271 Query]
|-
| 9 || 5 || [[User:finex|FiNeX]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=233334&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=233748 Query]
|-
| 10 || 5 || [[User:Jtamate|Jtamate]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=233835&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=234474 Query]
|-
| 11 || 5 || [[User:finex|FiNeX]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=234499&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=234755 Query]
|-
| 12 || 5 || [[User:finex|FiNeX]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=234884&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=235338 Query]
|-
| 13 || 5 || [[User:finex|FiNeX]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=235447&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=235789 Query]
|-
| 14 || 5 || [[User:finex|FiNeX]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=235793&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=236829 Query]
|-
| 15 || 5 || [[User:finex|FiNeX]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=236887&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=237303 Query]
|-
| 16 || 5 || [[User:finex|FiNeX]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=237538&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=237855 Query]
|-
| 17 || 5 || [[User:finex|FiNeX]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=238521&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=239059 Query]
|-
| 18 || 5 || [[User:finex|FiNeX]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=239855&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=240283 Query]
|-
| 19 || 5 || [[User:finex|FiNeX]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=240426&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=240904 Query]
|-
| 20 || 5 || [[User:Jtamate|Jtamate]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=240971&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=241313 Query]
|-
| 21 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=241503&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=242451 Query]
|-
| 22 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=242737&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=243165 Query]
|-
| 23 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=243236&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=243666 Query]
|-
| 24 || 5 || || 244052 done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=243795&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=244104 Query]
|-
| 25 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=244162&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=244514 Query]
|-
| 26 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=244561&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=245039 Query]
|-
| 27 || 5 || || 245083=dupe || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=245056&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=245227 Query]
|-
| 28 || 5 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=245262&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=245741 Query]
|-
| 29 || 5 ||[[User:Anselmolsm|anselmolsm]] || starting || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=246005&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=246239 Query]
|-
| 30 || 2 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=dolphin&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=246287&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=1 Query]
|}
(Total bugs 147)

== Completed Bugs ==
Below lists the various sections for completed bugs. This aids everyone in double checking each other's work. In addition this allows those of us that don't have bugzilla permissions to list bugs so that the folks with the permissions can follow up.

Please note that this is an experimental layout designed to reduce the number of edit conflicts on this page. Each section is its own subpage. The best way to work with this is to enable section editing by going to "My preferences" > "editing" > "Enable section editing via [edit] links". When you click edit you will automatically edit the subpage.

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs needing Version Field changed}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs with step-by-step Instructions}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs to be marked as RESOLVED}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs to be marked as DUPLICATE}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs to be marked as INVALID}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs to be marked as NEW}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs needing attention from Dolphin developers}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs needing the reporter's feedback}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs needing users with particular setups}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs not related to today}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs related to nepomuk or strigi}}

{{:Contribute/Bugsquad/BugDays/DolphinDay1/Bugs that you cant do}}

Projects/Telepathy

2010-04-16T14:44:30Z

Grundleborg: we've moved

{{Warning| The Telepathy-On-KDE project pages have moved to [http://community.kde.org/Real-Time_Communication_and_Collaboration community.kde.org/Telepathy]}}

Development/Architecture/KDE4

2010-03-09T20:02:18Z

Grundleborg: linky fail

{{Template:I18n/Language Navigation Bar|Development/Architecture/KDE4}}
== Development Framework ==

# Desktop
#* [[Development/Architecture/KDE4/Plasma|Plasma - The desktop]]
#* [[Development/Architecture/KDE4/Sonnet|Sonnet - Spell- and grammar-checking technology]]
#* [[Development/Architecture/KDE4/KParts|KParts - KDE's component architecture]]
# Hardware
#* [[Development/Architecture/KDE4/Solid|Solid - Hardware and network awareness]]
#* [[Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Communication
#* [[Projects/Telepathy|Telepathy - Real-Time Communication and Collaboration]]
#* [[Development/Architecture/KDE4/Akonadi|Akonadi - Centralized PIM storage solution]]
# User Interface
#* [[Development/Architecture/KDE4/Providing_Online_Help|Providing Online Help]]
#* [[Development/Architecture/KDE4/XMLGUI_Technology|Defining menus and toolbars in XML]]
# Services
#* [[Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]
#* [[Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

; [[Development/Architecture/KDE4/KGGZ|KGGZ]]
: Providing access to the GGZ Gaming Zone, a free online gaming centre.

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Development/Architecture/KDE4

2010-03-09T20:01:15Z

Grundleborg: alter Decibel entry to point to Telepathy pages, since Telepathy has essentially replaced it now.

{{Template:I18n/Language Navigation Bar|Development/Architecture/KDE4}}
== Development Framework ==

# Desktop
#* [[Development/Architecture/KDE4/Plasma|Plasma - The desktop]]
#* [[Development/Architecture/KDE4/Sonnet|Sonnet - Spell- and grammar-checking technology]]
#* [[Development/Architecture/KDE4/KParts|KParts - KDE's component architecture]]
# Hardware
#* [[Development/Architecture/KDE4/Solid|Solid - Hardware and network awareness]]
#* [[Development/Architecture/KDE4/Phonon|Phonon - Multimedia framework]]
# Communication
#* [[/Projects/Telepathy|Telepathy - Real-Time Communication and Collaboration]]
#* [[Development/Architecture/KDE4/Akonadi|Akonadi - Centralized PIM storage solution]]
# User Interface
#* [[Development/Architecture/KDE4/Providing_Online_Help|Providing Online Help]]
#* [[Development/Architecture/KDE4/XMLGUI_Technology|Defining menus and toolbars in XML]]
# Services
#* [[Development/Architecture/KDE4/Starting_Other_Programs|Starting other programs]]
#* [[Development/Architecture/KDE4/Strigi|Strigi - Desktop search engine]]
#* [[Projects/KNS2|KNewStuff2 - Collaborative data sharing]] (might move here from projects)

== Frameworks in other KDE modules ==

; [[Development/Architecture/KDE4/KGGZ|KGGZ]]
: Providing access to the GGZ Gaming Zone, a free online gaming centre.

KOffice 2.0

[[Category:KDE4]][[Category:Architecture]]

Projects/MovetoGit

2010-02-22T21:28:06Z

Grundleborg: add myself to kdenetwork module

This is the page for co-ordinating KDE's move to [http://git-scm.com/ Git].

If you're interested in helping, you should join the [https://mail.kde.org/mailman/listinfo/kde-scm-interest kde-scm-interest@kde.org] mailinglist and [irc://chat.freenode.net/kde-git #kde-git] on freenode.

Meetings are wednesdays, 19:30 UTC, in #kde-git.

=The Plan=

KDE is, eventually, moving to Git. We will be using [https://gitorious.org/ gitorious.org] servers, with funding from Nokia. We will also have our own mirrors using existing KDE servers.

We are working with the Gitorious people to ensure their server will meet all our needs as well as everyone's privacy requirements. The distributed nature of Git will make it easy for us to migrate off gitorious.org at any time should the need arise (but that's unlikely :).

In the summer of 2009, [http://gitorious.org/amarok Amarok] moved to Gitorious to test the waters and find problems that would affect KDE. Once those problems have been solved, all of KDE will be able to switch.

==Why?==

Git offers many advantages over svn, including offline commits and much easier to keep a feature branch up-to-date. Many KDE developers are already using git-svn, but this tool has its limitations. We want to have the full power of Git available, and we have people willing to do the work necessary to migrate.

==How?==

When we move, KDE's svn repository will be migrated into several Git repos, all on gitorious.org. Main modules such as kdelibs and kdebase will each become one repository. Projects in extragear will each have their own repository. The kde.gitorious.org site will have a list (lists?) of all these repositories using the builtin project wiki. Scripts will be provided for downloading, say, all of extragear, so "moving" a project from kdereview to extragear would simply involve editing a file kept online that defined the location of projects.

A few things will stay in subversion - currently websites, translations and manuals. It's possible they could move to Git later, but they won't be part of the mass migration.

On Gitorious, all KDE developers will be part of the [http://gitorious.org/+kde-developers kde-developers group]. Developers in this group are required to set their "full name" for their Gitorious account to their real name. If you are not in this group or do not have an account, a system will be set up to simplify the process. Or you can just go to Gitorious yourself, create an account, and ask to be added to the group. :)

=Blockers=

Tasks that need to get done before we can migrate

==SLA for gitorious.org==
{{Progress bar|20}}
'''Owner:''' aseigo, frank

'''Status:''' ''Progressing well; will take a while''

: The SLA terms need to be documented as well as who will be footing the bill, if any. TZander has talked to Shortcut AS and sent the relevant information (eg cost) to the KDE eV board.

==Write / update importing rules for svn2git==
{{Progress bar|0}}
'''Owner:''' Sho_, sandsmark, tumaix [kdegames], cryos [kdeedu], coles [kdesdk] - volunteers needed!

'''Status:''' ''sandsmark: stuck on a svn2git bug. sho: ???, tumaix:started to read the docs, cryos: getting started [2010-01-06]''

:The importer is on gitorious.org as svn2git we have a set of rules to tell the importer what svn dirs turn into which git repos and those need constant updating whenever a new branch or tag or project is created. Currently the rules are mostly a rough draft, as seen by the large amount of rule-editing that had to be done for Konversation and Amarok. This has not been done for quite some time and so someone should rsync the svn repo run svn2git and fix the rules and importer whenever the import stops.

:This is a very big task, too big for one person; it's probably best to tackle it one module at a time

:To get started on a module, read http://www.gitorious.org/svn2git

:TZander has done the koffice ruleset as of 2009-01-06

:Jpwhiting has finished (more or less) the kdeaccessibility ruleset 2010-01-24.

:aavci has done the k3b ruleset as of 2010-01-27

progress details:
{| border="1"
!repo
!owner
!%
!comments
|-
|SC/kdeaccessibility
|jpwhiting
|99
|"more or less"?
|-
|SC/kdeadmin
|
|0
|
|-
|SC/kdeartwork
|
|0
|
|-
|SC/kdebase
|
|0
|
|-
|SC/kdebindings
|
|0
|
|-
|SC/kdeedu
|cryos?
|?
|update me!
|-
|SC/kdeexamples
|
|0
|
|-
|SC/kdegames
|tumaix?
|?
|update me!
|-
|SC/kdegraphics
|
|0
|
|-
|SC/kdelibs
|
|0
|
|-
|SC/kdemultimedia
|eean
|0
|
|-
|SC/kdenetwork
| grundleborg
|0
|
|-
|SC/kdepim
|
|0
|
|-
|SC/kdepimlibs
|
|0
|
|-
|SC/kdeplasma-addons
|
|0
|
|-
|SC/kdesdk
|
|0
|
|-
|SC/kdetoys
|
|0
|
|-
|SC/kdeutils
|
|0
|
|-
|SC/kdewebdev
|
|0
|
|-
|extragear/*/*
|
|xx
|expand this later (let's focus on the base modules first)
|-
|kde-common
|
|0
|what is this? I'm not sure if it belongs
|-
|kdenox
|
|0
|dunno what this is either.
|-
|kdereview
|
|xx
|does it make any sense to have this?
|-
|kdesecurity
|
|0
|not sure about this one
|-
|kdesupport
|
|0
|how many externals does this have?
|-
|koffice
|tzander
|100
|
|-
|konstruct
|
|0
|wtf is this?
|-
|playground
|
|0
|not sure if we want this?
|-
|promo
|
|0
|
|-
|quality
|
|0
|what's this?
|-
|tests
|
|0
|
|}

==Script for downloading virtual KDE hierarchies==
{{Progress bar|80}}
'''Owner''': Michael Jansen (mjansen)

'''Status:''' build tool created, computer-readable file not done.

:One goal for the whole project is to support how people use KDE SVN as much as possible. One issue is that people often check out 'extragear/multimedia' or 'kdesupport' as a whole. However with git extragear, playground, kdesupport etc projects are going to be split up and are essentially going to exist as a flat list on Gitorious.
:The proposed solution is have a computer-readable file (eg XML) that only sysadmins could edit. It would define a tree of projects mirroring the current SVN tree. A script would then be able to easily perform operations like 'remote update', 'pull', 'clone' on multiple repos at once, in the same way users are able to checkout or update 'extragear' all at once.
:More info is at the [[Projects/MovetoGit/MassCloneScript|scripts development page]]. The tool itself is hosted at: http://rubyforge.org/projects/build-tool/.

:Morice-net will help mjansen with testing once the extensions have been finished.

'''Discussion'''
:Progress 5 since we have a spec. :) --[[User:Eean|eean]]
:Ok now the plan is basically that mjansen will extend his build script to allow clone-only and to update its recipes from an online source. The recipes have the advantage of defining all the build deps as well, so we would end up with official documentation of build dependencies, something thats often been missing. --[[User:Eean|eean]] 17:18, 12 November 2009 (UTC)

'''Link'''
http://techbase.kde.org/Projects/MovetoGit/MassCloneScript

:don't forget the "computer-readable file" part. not much point in a build script that you need a new version of every time the list of git repos changes :)

==Push log==
{{Progress bar|0}}
'''Owner:''' argonel

'''Status:''' hd failure :( [2010-01-06]

:Gitorious records who pushed each commit. This is useful information because commits themselves can say anything, and there are legitimate reasons to push commits with another person's name.

:Internally, Gitorious stores this information in an SQL database, and the information is viewable through the web interface. However we want a way to backup this information for the case that Gitorious suddenly go offline.

:quotes from the mailing list:

> How about every repo has, by convention, a "commits" branch and
> a post commit hook that ensures whatever meta info is required,
> however it can be gleaned, is also checked into that commits branch.
> A bit like how gitosis uses a repo to store auth/acl info to help
> manage the other repos.

That's exactly my idea. And of course it won't be named commits, because we're
not talking about commits.

It's a push log, similar to a local repository's reflog.

---------------

For every push, log:
- who pushed (not the Unix username, which will be "git")
- which branch heads changed (what from, what to)
- which tags were created
- the state of all other branches and tags

Just use git commit-tree with the empty tree and save everything in the commit
message, one after the other.

==pre-receive hooks==
{{Progress bar|0}}
'''Owner:''' ''volunteers needed!!''

* Line endings and encodings

'''Discussion:'''
this got accidentally marked as done or something, but it's not.

'''Notes:'''
> > As for line-endings, be careful because Git is different from Subversion.
>
> different how?

Just ensure that all files are stored as LF only, except if there's a
.gitattributes file saying "-crlf" (i.e., allow it to have CRLF).

==Get rid of svn:externals==
{{Progress bar|50}}
'''Owner:''' David Faure

'''Status:''' ''???''

:not possible with git, broken by design.

::

'''Discussion'''

Must get rid of:
* kdebase/workspace/kwin/clients/oxygen/lib -> will become a shared library in 4.5
* kdenetwork/kget/transfer-plugins/bittorrent/libbtcore

Need to look into:
* playground/utils strigi-chemical/test/ctfr
* playground/devtools kdevelop4-extra-plugins/php/parser/generated/kdevelop-pg-qt
* playground/devtools kdevelop4-extra-plugins/python/parser/generated/kdevelop-pg-qt
* playground/devtools kdevelop4-extra-plugins/qmake/parser/generated/kdevelop-pg-qt

Exists, but ignorable:
* kdesupport shared-desktop-ontologies (temporary)
* playground/devtools kommander-plugins/database3/admin
* playground/devtools kommander-plugins/database/admin
* playground/devtools kommander-plugins/datetimefuncs/admin
* playground/devtools kommander-plugins/htmlpart/admin
* playground/devtools kommander-plugins/httpform/admin
* playground/devtools kommander-plugins/kparts/admin
* playground/devtools kommander-plugins/qtactionproxy/admin
* playground/devtools kommander-plugins/timewidget/admin
* playground/devtools kommander-plugins/webkit3/admin
* playground/devtools kpackagemaker/admin

=Nice to have before the migration=

==Snapshot to read-only svn==
{{Progress bar|0}}
'''Owner:'''

:It's work, but maybe some people would like it. NEEDED for documentation, in order to get it back into SVN for the translators/scripty/?

'''Discussion'''

:Could be done with a git-svn gateway presumably? -Mike Arthur 19/10/2009 16:04

:if we leave the docbook stuff in svn, we can avoid this a bit longer. --[[User:Chani|Chani]] 23:21, 12 November 2009 (UTC)

==[[Development/Tutorials/Git|Techbase Documentation]]==
'''Owner:''' Chani, greeneg, - ''please help out!''
{{Progress bar|10}}

:At least minimal documentation about how to checkout, how to get a Gitorious account, how to request a merge needed, other git documentation and links to other git information would be very useful also.

:see the [[Development/Tutorials/Git|Git Tutorial Page]]. help wanted!!

'''Discussion'''

==Setup git mirrors for cloning==
{{Progress bar|0}}
'''Owner:''' No one (help!)
:Re-purpose the anonsvn servers. This item might be a blocker.
'''Discussion'''

==Local pre-commit hooks==
{{Progress bar|0}}
'''Owner:''' argonel

:A set of recommended local hooks that give useful warnings could be nice to have.

'''Discussion'''
...on the other hand, if we get a lot of bikeshedding about what hooks, then it won't be so nice. so I'd put this in the "very optional" pile. --[[User:Chani|Chani]] 19:10, 16 December 2009 (UTC)

=Post-migration Issues=

==Website Branding==
{{Progress bar|2|text=(initial ideas on the table)}}
'''Owner:''' ruphy

:KDE Gitorious should be branded accordingly, and should be reachable from git.kde.org as well as kde.gitorious.org

'''Discussion'''

=Unscheduled & Open=

==Allow tagging without involving sysadmins==
{{Progress bar|0}}

'''Owner:''' johan

:Pushing a tag currently requires permissions to do a force push, which is a repository-wide checkbox that can only be toggled by a kde-developers admin. Thus the workflow for a dev wanting to do a release tag for his app is to ask an admin to enable force pushing, then to push his tag, and then to tell the admin he can disable force pushing again. This doesn't scale, is insecure, and at odds with KDE's open access policy when it comes to managing the repos (right now in SVN, you need sysadmin to create an app dir in /tags for you, but don't have to ask permission for every individual tag). Johan has promised a solution for this.

:Notable discussion points on kde-scm-interest:
:http://mail.kde.org/pipermail/kde-scm-interest/2009-November/000782.html
:http://mail.kde.org/pipermail/kde-scm-interest/2009-November/000784.html

'''Discussion'''

==Account setup on Gitorious==
{{Progress bar|0}}

'''Owner:''' ''eean, johan, boud, dario''

:Creating an account on Gitorious isn't hard, but asking to be added to the KDE group is inconvenient. For the migration we should set up a system (via email or wiki?) where developers can ask to have an account autocreated for them, or add their existing Gitorious account to a list to be added to the group. Once this is in place an announcement should be sent to all svn accounts explaining the process, and privacy information.

:Basically the currently method of using Bugzilla works fine now and works fine in the longterm. But in the transition month when hundreds of accounts must be created or added, we need a better system. Its important to make it as easy as possible so that we don't lose anyone in the shuffle.

'''Discussion'''

==post-update hooks==
{{Progress bar|90}}
'''Owner:''' ''morice'' ''Ian Monroe''

:* License checker

'''Discussion:'''
We have a fairly complete set of post-update hooks now. See [http://gitorious.org/remotehook remotehook]. However, it would be nice to have a system that lives on the Gitorious server and/or requires less manual maintenance. But its certainly workable and no longer a blocker.

=Completed Tasks=

==EBN==
{{Progress bar|95}}
'''Owner:''' ''drf''

'''Status:''' ''Amarok has EBN checks''

:EBN's krazy checks currently run on kde's svn repo; it needs upgrading to download and check our git repos too.

:This would be easier if there was a repo-list that EBN could parse, as it can no longer just svn up to get everything.

==Talk to people using other distros about git==
{{Progress bar|100}}
'''Owner:''' Sebas, Eike

'''Discussion'''
* Gentoo: They seem to be prepared for moving their live SVN packages to git; their package manager has easily-reusable classes to fetch from an SCM and moving the ebuilds to using the git class rather than the SVN class should be easy. Positive comments to that end from people in #gentoo-kde.
* Fedora: Some unhappyness about git because SVN allows them to remotely produce a diff between two SVN URLs (or two revisions of one and the same URL) without making a checkout first, while git requires making a clone. Kevin Kofler (IRC nick Kevin_Kofler, #fedora-kde) says this will make their packager work harder.
* Debian: Is indifferent about the SCM switch.

==Post Update hooks==
{{Progress bar|100}}
'''Owner:''' ''morice, johan, mattr

:List of scripts needed:
:* BUG/CCMAIL
:* email/CIA

:Gitorious needs to provide a way for hooks to be called; KDE needs to write said hooks.

'''Discussion'''

:There is a branch of gitorious called web-hooks http://gitorious.org/gitorious/mainline/commits/web-hooks --Panagiotis Papadopoulos 1 November 2009
:Same situation as commit emails. I can do it but it doesn't scale well and a Gitorious-supported solution would be nicer. --[[User:Eean|eean]] 16:07, 12 November 2009 (UTC)

==Opt-in privacy exception required for kde-developers==
<strike>
{{Progress bar|0}}
'''Owner:''' ''Gitorious'', ''KDE e.V. Board'', ''eean''

:KDE sysadmins need access to some information that Shortcut could not give them due to their privacy policy. Examples include an email list of all the developers and SQL-level access to information about all the repos in KDE (since it stores who pushes what, information not stored in the git repo itself).

:Such requirements will likely be put into the contract with Shortcut.

'''Discussion'''
:So the e.V. Board is an owner since this is a legal/contract/money issue. Added myself only because I'm shepherding the issue. --[[User:Eean|eean]] 16:16, 12 November 2009 (UTC)

</strike>

:'''We will not get sql access to the information. For the alternative solution see the Push Log issue'''

==Reviewboard==
{{Progress bar|100}}
'''Owner:''' darktears

This should be easily done with Gitorious web interface and merge requests actually.

'''Discussion'''

:but reviewboard has features gitorious (right now) doesn't, like commenting on specific lines and not having to set up a merge request. --chani
::Also email notifications when someone reviews are needed --thomasz
:We're working on this for someone else right now, so pretty soon --johan-s
:I consider the latest changes to gitorious to finish this. If more reviewboard features are still needed, and git supports reviewboard, I think this is something we can look at doing post-conversion. --Ian Monroe

==Gitorious Needs a feature to disable merge request emails for certain repos==
{{Progress bar|100}}
'''Owner:''' [http://gitorious.org/gitorious Gitorious]

Have a sensible system for merge request emails. This is now in place - you can join groups, chose whether to have emails on a per repo basis, etc.

==SSH blocked in corporations and universities.==
{{Progress bar|100}}
'''Owner:''' ''Unknown''

:Some universities tend to block the SSH port. There should be a workaround to use SSH on some different port. github.com already runs a SSH server on port 443. But that assumes you are using a proxy. It has been found that this hasn't worked with a lot of people, especially those who have a direct connection to the internet ( so some transparent blocking by the ISP ). It would be great if (almost) every KDE developer were to be asked to check if other ports work before KDE made the switch. Otherwise there could be an automated email where the git patches could be sent, and appropriately patched to the right location too.

'''Discussion'''

:http://blog.gitorious.org/2009/10/20/stuck-behind-a-firewall/, and there's always been HTTP cloning (although the current impl. in Git is a bit on the slow side) --johan-s

==Talk to windows guys about git.==
{{Progress bar|100}}
'''Owner:''' aseigo

'''Discussion'''

They aren't huge fans of git, but are using it. They require a single mainline and can't cope with multiple branches. Otherwise, it's workable, even if it will take an adjustment period.

==pre-commit hooks==
{{Progress bar|100}}
'''Owner:''' ''(unknown)''

:acltest, docbook, EOL/UTF-8

:A web hook isn't good enough for these because they have to run and return whether to allow the push, for every single push to every KDE repo.

'''Discussion'''

:gitorious guys said they *might* be willing to allow a few scripts on their server for KDE as a special exception, iirc. --chani

:: Yes, at least for basic things, heavier things like doc building would probably have to be mirrored (goes for pre/post) --johan-s

:It turns out that acl and docbook might not be needed so long as web and docs/ stuff stays in svn.

:: Here's where to find the current scripts - http://websvn.kde.org/trunk/kde-common/svn/hooks/ --[[User:Argonel|Argonel]] 23:06, 11 November 2009 (UTC)

::So: this is actually done because it needs no longer to be done? (boud)

::Apparently, so; moving to complete. (aseigo)
= other notes =

==Random==

KDE accounts file is no longer necessary---used for mapping svn ID -> email, but we have that now from Gitorious.

http://mail.kde.org/pipermail/dot-stories/2005-May/000509.html might be a good guide on what docs we need.

some of this stuff was from the list from GCDS that was in this email [http://markmail.org/message/u6eqfjece7fibfyo http://markmail.org/message/u6eqfjece7fibfyo]

==IRC Meetings==
* [[Projects/MovetoGit/Meeting1111|Minutes]] of meeting 11 November 2009
* [[Projects/MovetoGit/Meeting1118|Next meeting]] 18:00, 25 November 2009 (UTC)

= jobs =
''TODO merge this with the todolists above''

michael jansen: talking to kdesvn-build/mpyne
:--Done? -> http://kdesvn-build.kde.org/releases/kdesvn-build-1.10.php -- Panagiotis Papadopoulos 1 November 2009
::Yes, but the __kdesvn-build-remote used in the impl isn't pleasant for users already on git so it still needs more work for them. [[User:Mpyne|Mpyne]] 20:32, 11 November 2009 (UTC)

jonas: domain name

ML: convert to SSH

chani: techbase docs for scripty

sebas/lydia/leo: communication with teams! tell people! keeping track that
everything is being done.

Projects/Telepathy

2010-01-25T20:03:51Z

Grundleborg: point to community.kde.org

{{Warning| The Telepathy-On-KDE project pages have moved to community.kde.org. [http://community.kde.org/Real-Time_Communication_and_Collaboration]}}

==Introduction==
[http://telepathy.freedesktop.org The Telepathy framework] is a DBus specification which provides a cross-desktop and cross-protocol abstraction layer for instant messaging, voice/video over IP and collaborative applications. See the [http://telepathy.freedesktop.org Telepathy web site] for more information about Telepathy itself.

This project is focused on integrating Telepathy with KDE. Our high-level aims are the following:
* to provide a unified instant messaging and voice/video communication framework within KDE, which integrates throughout the desktop experience.
* to provide collaborative features in applications which fit seemlessly into the KDE platform
* to provide the infrastructure within KDE necessary to acheive the above two, using cross-desktop specifications and implementations wherever possible.

==Infrastructure==
This section contains details of all the Telepathy-in-KDE infrastructure components, and their statuses.

===Telepathy Integration Daemon===

{{Warning| Before working on this component, please talk to grundleborg on #kde-telepathy. See [[/TelepathyNepomukPlans|here]] for more information on Telepathy/Semantic Desktop Integration.}}

This is a small light-weight daemon that monitors the Telepathy Account Manager and keeps ensures that all Accounts are recorded in Nepomuk as NCO:Contact instances of "myself" and that they each have a Telepathy Contacts Akonadi Resource instance.

It could possibly be made into a KDED module, but I'm not sure if this is a good idea. [[User:Grundleborg|Grundleborg]]

====Status====
The bare bones are implemented, but the Nepomuk part is blocking on standardising the Ontologies for telepathy specific stuff and how to access the "myself" PIMO:Person through Nepomuk. The Akonadi part is blocking on getting the Telepathy Contacts Akonadi Resource below implemented.

====Source Code====
Source code can be found in KDE svn at:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-integration-daemon
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-integration-daemon websvn link].

===Telepathy Contacts Akonadi Resource===

{{Warning| Before working on this component, please talk to grundleborg on #kde-telepathy. See [[/TelepathyNepomukPlans|here]] for more information on Telepathy/Semantic Desktop Integration.}}

This is an Akonadi Resource that synchronises the contacts of a Telepathy Account into Akonadi as vcards. The instances of this resource are managed by the telepathy-integration-daemon mentioned above.

====Status====
Partially implemented. Requires some Telepathy CM's to implement the org.freedesktop.Telepathy.Connection.Interface.ContactInfo.DRAFT interface to complete it, since we shouldn't try and support legacy CM's which don't support that interface.

====Source Code====
The code can be found in the KDE svn playground at the following URL:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-contacts-resource
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-contacts-resource websvn link].

===Presence Dataengine and Plasmoid===

====Status====

The dataengine is functional, allowing you to set the Requested Presence and Status Message, and view the Current Presence, Status Message, Avatar, Alias and name of all Telepathy Accounts.

The applet is working well on its first version, supporting to set up presence status and presence message. It still needs some polishing and love from designers.

====Source Code====

Applet in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/applets/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/applets/presence websvn link].

Dataengine in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/dataengines/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/dataengines/presence websvn link].

===Account Management KCM===
====Ideas====
* One single UI that any application can load for add/edit/delete Telepathy Accounts

* Creates a dynamic UI on-the-fly using Connection Manager parameters, but this should be used only when a specific UI plugin for that CM isn't installed.

* Create specialised UI plugins for the popular CM's (e.g. gabble) since dynamic UI will be pretty crap usability-wise.

====Status====

Some code is there in svn, but it's pretty much just experimental shell-files. So feel free to ignore existing code to implement this :) [[User:Grundleborg|Grundleborg]]

====Source Code====

Source code is in KDE svn playground at:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-accounts-kcm/
</pre>

[http://websvn.kde.org/trunk/playground/network/telepathy-accounts-kcm/ websvn link].

===KWallet Account Manager===
This was originally intended to be an implementation of the Telepathy AccountManager which was integrated with KDE and KWallet for the account data storage. However, in light of the shared-secrets API being developed on freedesktop.org which will unify the KWallet and Gnome-Keyring API it would probably be a better use of resources to just get Mission Control ported to that instead.

In light of that, its probably best not to work on telepathy-accountmanager-kwallet or telepathy-qt4-accountmanager at the moment.

==Telepathy Enabled Applications==

==Problems==

* QtDBus doesn't have peer-to-peer DBus implemented properly - the classes are just non-functional stubs. This stops us from implementing D-tubes in KDE/Qt based Telepathy applications. Upstream bug is private in Qt Software's tracker and this is unlikely to get fixed by Qt Software, so if anyone feels like implementing it and then merging it upstream into Qt, that would be really fantastic.

* Telepathy-Mission-Control still requires you to use both the channel dispatcher part of it and the Account Manager. For KDE, we need to be able to use only the Channel Dispatcher from Mission-Control and have that talk over the standard Telepathy DBus interfaces to the KDE KWallet based Account Manager.(OR we need MC's AM to start using the shared-secrets API)

==Trying out Telepathy==

=== Prerequisites ===
* telepathy-mission-control 5
* telepathy-qt4
* telepathy-gabble, telepathy-butterfly, telepathy-haze (for jabber/msn/everything else support respectively)

=== KDE Stuff ===
All the KDE Telepathy infrastructure components are detailed above, and they may or may not be in working/compiling order. Any problems, ask in #kde-telepathy.

==How to Get Involved==
Come and talk to us in #kde-telepathy on irc.freenode.net. There is also a #telepathy channel for talking about Telepathy stuff that is not specific to KDE.

==Frequently Asked Questions==

=== What happened to Decibel? ===

Decibel development has completely stagnated and it no longer works with recent Telepathy components. It is not necessary to use Decibel to get Telepathy support in KDE - all the applications/components above do not require Decibel to compile or function.

Development/Tutorials/Metadata/Nepomuk/AdvancedQueries

2009-11-07T17:33:45Z

Grundleborg: Fix a couple of errors in code samples

{{TutorialBrowser|
series=[[../|Nepomuk]]|
name=Advanced Sparql Queries in Nepomuk|
pre=[[../RDFIntroduction|Introduction to RDF and Ontologies]], [[../NepomukServer|Nepomuk Server]]|
next=|
reading=[http://www.dajobe.org/2005/04-sparql/ SPARQL Quick Reference], [http://www.w3.org/TR/rdf-sparql-query/ SPARQL W3C Definition]|
}}

==Advanced Sparql Queries in Nepomuk==

In [[../NepomukServer|Nepomuk Server]] we learned how to access the Nepomuk Server to get a [http://api.kde.org/kdesupport-api/kdesupport-apidocs/soprano/html/classSoprano_1_1Model.html Soprano::Model] instance. We will now take a look at how to perform queries against the Nepomuk data repository.

{{Note|The queries presented here a pretty low-level. Soon Nepomuk will provide a wrapper class that makes every-day queries much simpler.}}

===Query Basics===

Basically performing a query with Nepomuk/Soprano always looks as follows (More details on using the iterator in the [http://api.kde.org/kdesupport-api/kdesupport-apidocs/soprano/html/classSoprano_1_1QueryResultIterator.html Soprano API documentation].):

<code cppqt>
QString query = getFancyQueryString();
Soprano::QueryResultIterator it
= model->executeQuery( query,
Soprano::Query::QueryLanguageSparql );
while( it.next() ) {
Soprano::Node value = it.binding( "someVariableName" );
Soprano::BindingSet allBindings = *it;
}
</code>

===Simple Queries===

Let us have a look at how a query can be constructed. As an example we will query for all resources that are tagged with a certain tag. Let's imagine that we have a reference to this tag stored in ''myTag''. (Please ignore the fact that Nepomuk::Tag::tagOf essentially returns the same information. After all, we are here to learn how it works.)

<code cppqt>
#include <Soprano/Model>
#include <Soprano/QueryResultIterator>
#include <Soprano/Vocabulary/NAO>

[...]

Nepomuk::Tag myTag = getOurFancyTag();

QString query
= QString("select distinct ?r where { ?r %1 %2 . }")
.arg( Soprano::Node::resourceToN3(Soprano::Vocabulary::NAO::hasTag()) )
.arg( Soprano::Node::resourceToN3(myTag.resourceUri()) );

Soprano::QueryResultIterator it
= model->executeQuery( query,
Soprano::Query::QueryLanguageSparql );
while( it.next() ) {
myResourceList << Nepomuk::Resource( it.binding( "r" ).uri() );
}
</code>

We begin by constructing the SPARQL query string. It is a simple query and if you know SQL it should be easy to understand. Basically we select resources that match the patterns in the ''where'' statement. In this case the resource needs to have the ''hasTag'' property with object ''myTag''. As we can see, Soprano already provides a set of standard URIs as static instances in the [http://api.kde.org/kdesupport-api/kdesupport-apidocs/soprano/html/namespaceSoprano_1_1Vocabulary.html Soprano::Vocabulary] namespace. And since we have the Nepomuk resource object for the tag we can simply use its unique URI to directly access the tagged resources.

But what if we do not have the tag URI but only its label, i.e. the name given by the user?

Also no problem with SPARQL:

<code cppqt>
QString myTagLabel = getFancytagLabel();

QString query
= QString("select distinct ?r where { "
"?r %1 ?tag . "
"?tag %2 %3 . }")
.arg( Soprano::Node::resourceToN3(Soprano::Vocabulary::NAO::hasTag()) )
.arg( Soprano::Node::resourceToN3(Soprano::Vocabulary::RDFS::label()) )
.arg( Soprano::Node(myTagLabel).toN3() );
</code>

This already looks a lot more confusing as the previous example but that is mainly due to the QString argument paramters. Let's clean it up w bit by using SPARQL prefix declarations:

<code cppqt>
QString query
= QString("PREFIX nao: %1 "
"PREFIX rdfs: %2 "
"PREFIX xls: %3 "
"select distinct ?r where { "
"?r nao:hasTag ?tag . "
"?tag rdfs:label \"%4\"^^xls:string . }")
.arg( Soprano::Node::resourceToN3(Soprano::Vocabulary::NAO::naoNamespace()) )
.arg( Soprano::Node::resourceToN3(Soprano::Vocabulary::RDFS::rdfsNamespace()) )
.arg( Soprano::Node::resourceToN3(Soprano::Vocabulary::XMLSchema::xlsNamespace()) )
.arg( myTagLabel );
</code>

Both queries are the same and it is up to the query writer to decide which version he or she prefers. We are just presenting both versions here for demonstration purposes.

Now let us analyse what is happening here. Instead of just matching a single graph pattern, we match two where the first one introduces another variable which is then reused in the second one. ''rdfs:label'' has a string literal range, meaning that each object related to a resource via the ''rdfs:label'' property is a string literal. And in this case we want to select the tag that has ''myTagLabel'' as its label.

===Bringing more context into the mix===

In [[../RDFIntroduction|Introduction to RDF and Ontologies]] we briefly learned about ''named graphs'' or ''context'' which make up the fourth part of each statement in Nepomuk. We can now use this information to filter our results based on creation dates. Imagine for example that we want to retrieve all resources tagged before the first of January 2008. We do this by introducing some more complex SPARQL syntax. For simplicity we go back to our first example of matching the tag URI directly to keep the query from getting too unreadable. But of course both can be combined. (Keep in mind that we only use the prefix syntax here for readability. In actual code it may be better to directly add the URIs from [http://api.kde.org/kdesupport-api/kdesupport-apidocs/soprano/html/namespaceSoprano_1_1Vocabulary.html Soprano::Vocabulary] to prevent typing errors in property and class names.)

<code cppqt>
QDateTime firstOfJanuary = getFirstOfJanuary();

QString query
= QString("PREFIX nao: <%1> "
"PREFIX rdfs: <%2> "
"select distinct ?r where { "
"graph ?g { ?r nao:hasTag <%3> . } "
"?g nao:created ?time . "
"FILTER(?time < %4) . }")
.arg( Soprano::Vocabulary::NAO::naoNamespace().toString() )
.arg( Soprano::Vocabulary::RDFS::rdfsNamespace().toString() )
.arg( myTag.resourceUri().toString() )
.arg( Soprano::Node::literalToN3( firstOfJanuary ) );
</code>

This query contains three new concepts:

# As we can see SPARQL does not simple add the context as fourth parameter but needs us to suround the triples we want to match into a certain context with the ''graph'' keyword.
# We use the SPARQL [http://www.w3.org/TR/rdf-sparql-query/#tests ''FILTER''] keyword to filter out only those graphs/contexts that have a ''nao:created'' value smaller than January, first.
# We use [http://api.kde.org/kdesupport-api/kdesupport-apidocs/soprano/html/classSoprano_1_1LiteralValue.html Soprano::LiteralValue] instead of QDateTime directly. This is important since QDateTime does not support the RDF way of formatting a dateTime string. Thus, we need to use Soprano's internal dateTime string conversion algorithm by using LiteralValue.

===Full text queries===

While SPARQL in theory supports full text queries through the [http://www.w3.org/TR/rdf-sparql-query/#funcex-regex ''REGEX FILTER''] keywords the storage backends do not have their own real full text index. Thus, a full text search using SPARQL FILTER may become very slow if there are many statements to filter.

That is why in Soprano we have the [http://clucene.sourceforge.net/ CLucene] based [http://api.kde.org/kdesupport-api/kdesupport-apidocs/soprano/html/namespaceSoprano_1_1Index.html full text index model]. It is stacked on top of the actual storage model within the Nepomuk Server and provides a full text index on all literal object nodes in the repository. Since Soprano does not have a fancy query API yet (using plain strings as queries does not count as ''fancy'') full text queries have still to be performed separately. This may be inconvenient but will hopefully be solved in Soprano 3.

So for now we have to learn a second way to query the repository: using the [http://lucene.apache.org/java/docs/queryparsersyntax.html Lucene Query Language]. But that is much easier in most cases.

Let us assume that we want to search resources that are related to some literal object that matches the value "nepomuk". In SPARQL this would mean to query for:

<code>
select ?r where { ?r ?p ?o .
FILTER REGEX(STR(?o),'nepomuk', 'i') .
FILTER isLiteral(?o) . }
</code>

We convert the object literal into a string and match it to a regular expression ignoring case. This works but may be slow. Using the Soprano lucene full text index we perform this query as follows:

<code cppqt>
Soprano::QueryResultIterator it =
model->executeQuery( "nepomuk",
Soprano::Query::QueryLanguageUser,
"lucene" );
while( it.next() ) {
QUrl resource = it.binding( "resource" ).uri();
double score = it.binding( "score" ).literal().toDouble();
}
</code>

Here we make use of the fact that Soprano allows to add new [http://api.kde.org/kdesupport-api/kdesupport-apidocs/soprano/html/namespaceSoprano_1_1Query.http user defined query languages]. Also we use the fixed mapping from CLucene query results to Soprano query bindings as defined in [http://api.kde.org/kdesupport-api/kdesupport-apidocs/soprano/html/classSoprano_1_1Index_1_1IndexFilterModel.html Soprano::Index::IndexFilterModel]:

* Binding ''resource'' always gives the matched resource.
* Binding ''score'' always gives the lucene score (between 0 and 1).

These results can now be reused to perform further SPARQL queries.

Of course it is possible to use the full range of the [http://lucene.apache.org/java/docs/queryparsersyntax.html Lucene Query Language]. Another simple example would be to only match a certain property:

<code cppqt>
QString query =
Soprano::Vocabulary::RDFS::label().toString()
+ ':' + "nepomuk";
Soprano::QueryResultIterator it =
model->executeQuery( query,
Soprano::Query::QueryLanguageUser,
"lucene" );
</code>

Schedules/KDE4/4.4 Feature Plan

2009-11-06T16:02:26Z

Grundleborg: krdc tubes support is done and merged.

This is a list of planned features for the 4.4 release.

See also:

*[[Schedules/KDE4/4.4 Release Schedule]]
*[[Schedules/KDE4/4.4 Release Goals]]
*[[Schedules/KDE4/4.3 Feature Plan]]

 Legend:

*todo => not started yet
*in-progress => started, but not completed yet
*done => completed

__TOC__

 

= kdeaccessibility =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureDone|kttsd|Clean up kttsd by making it a simple wrapper around speech-dispatcher|jpwhiting@kde.org|Jeremy Whiting}}
|}

 

= kdeadmin =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|system-config-printer-kde|Restore feature parity with KDEPrint3 where possible.||Jonathan Riddell, John Layt}}

|}

 

= kdeartwork =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
|}

 

= kdebase-apps =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Konqueror|Improvements in session-management|edulix@gmail.com|Eduardo Robles Elvira}} {{FeatureTodo|Konqueror|Improvements in tab-bar widget|edulix@gmail.com|Eduardo Robles Elvira}} {{FeatureInProgress|Konqueror|New Konqueror bookmarks using Akonadi and Nepomuk, awesome bar|edulix@gmail.com|Eduardo Robles Elvira}} {{FeatureInProgress|Konqueror|Sidebar cleanups; re-introducing the history module|faure@kde.org|David Faure}} {{FeatureInProgress|Dolphin|
Version control intergration|peter.penz@gmx.at|Peter Penz}} {{FeatureInProgress|Dolphin|
Improved search bar including search configuration|peter.penz@gmx.at|Peter Penz}} {{FeatureInProgress|Dolphin|
Refactoring of Information Panel. KMetaDataWidget and KMetaDataConfigurationDialog should be moved to kdelibs.|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|Dolphin|Remember the Details View expansion state, at least in the DolphinPart
|frank78ac@googlemail.com|Frank Reininghaus}}
{{FeatureInProgress|Dolphin|Open URL in a new tab if the Back, Forward or Up button in the toolbar is middle-clicked
|frank78ac@googlemail.com|Frank Reininghaus}}
{{FeatureInProgress|DolphinPart|Restore the "Edit->Selection" menu that was in Konqueror 3
|frank78ac@googlemail.com|Frank Reininghaus}}

|}

= kdebase-runtime =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|KWallet|Single Sign On using PAM|lemma@confuego.org|Michael Leupold}}
{{FeatureTodo|network kioslave|Backend for UPnP|kossebau@kde.org|Friedrich Kossebau}}
{{FeatureTodo|network kioslave|Backend for LISa|kossebau@kde.org|Friedrich Kossebau}}
{{FeatureTodo|network kioslave|Backend for SMB|kossebau@kde.org|Friedrich Kossebau}}
{{FeatureTodo|network kioslave|Integrate with remote and zeroconf kioslaves|kossebau@kde.org|Friedrich Kossebau}}
{{FeatureTodo|smb kioslave|add kwallet support|brandon.ml@gmail.com|Carlo Segato}} {{FeatureDone|thumbnail kioslave|Support for comic-book cover previews (.cbr, .cbz, .cbt files)|qwertymaniac@gmail.com|Harsh J}}
{{FeatureInProgress|thumbnail kioslave|Support for rotated jpegs|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureInProgress|Nepomuk|Integrate Filesystem service to handle mounting/unmounting of removable devices|trueg@kde.org|Sebastian Trueg}} {{FeatureInProgress|Nepomuk|Add nepomuk kio slave which handles all stating of Nepomuk resources|trueg@kde.org|Sebastian Trueg}} {{FeatureInProgress|Nepomuk|Port Nepomuk to Virtuoso: query service, strigi service|trueg@kde.org|Sebastian Trueg}}
{{FeatureTodo|Nepomuk|Remove the ontologies and make kdebase depend on the upcoming shared-ontologies package|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|Locale KCM|Add support for new KLocale features (see kdelibs section) including Currency Code, Decimal Places, Digit Groups, AM/PM, etc. Improvements to usability of existing options.|john@layt.net|John Layt}} {{FeatureInProgress|Device Automounting|Add support for storage device automounting|tdfischer@fedoraproject.org|Trever Fischer}}

|}

= kdebase-workspace =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
|-
! style="text-align: center;" colspan="4" | Non-Plasma, Non-KWin
{{FeatureTodo|Icons KCM|More configurable icon sizes|christoph@maxiom.de|Christoph Feck}} {{FeatureTodo|Fonts KCM|More configurable fonts|christoph@maxiom.de|Christoph Feck}} {{FeatureTodo|System Activity|Show CPU usage etc|tapsell@kde.org|John Tapsell}} {{FeatureInProgress|Date/Time KCM|Plasma themed clock|christoph@maxiom.de|Christoph Feck}} {{FeatureInProgress|System Activity|Add scripting support|tapsell@kde.org|John Tapsell}}
{{FeatureDone|Solid|RemoteControl Manager/Interface + Lirc backend|michael_zanetti@gmx.net|Michael Zanetti}}
{{FeatureTodo|Solid|Improve SolidBluetooth stack, adding send files and more tipes of pairings (a2dp, modems etc...)|alex@eyeos.org|Alex Fiestas}}
{{FeatureDone|System Activity|KAuth integration|tapsell@kde.org|John Tapsell}}
{{FeatureDone|System Settings|Improve module appearance for Icons View and provide searching hints|sourtooth@gmail.com|Ben Cooksley}}
{{FeatureInProgress|System Setitngs|Reorganize modules|sourtooth@gmail.com|Ben Cooksley}}
{{FeatureInProgress|Mouse KCM|XInput2 support|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Attica KCM|Initial import|ewoerner@kde.org|Eckhart Wörner}}
{{FeatureInProgress|Solid::Control network environment tracking|Access a high level view of wireless networks by interface, testing in playground|wstephenson@kde.org|Will Stephenson}}
|-
! style="text-align: center;" colspan="4" | KRunner
{{FeatureDone|KRunner|Window management runner|kde@martin-graesslin.com|Martin Gräßlin}} {{FeatureTodo|KRunner|Solid device runner|wilderkde@gmail.com|Jacopo De Simoi}} {{FeatureInProgress|KRunner|Add Firefox support to the bookmark runner|jangerrit@weiler-marker.com|Jan Gerrit Marker}} {{FeatureTodo|KRunner|Solid device runner|wilderkde@gmail.com|Jacopo De Simoi}} {{FeatureInProgress|KRunner|Single runner mode|wilderkde@gmail.com|Jacopo De Simoi}} {{FeatureTodo|KRunner|Manage actions in default interface|wilderkde@gmail.com|Jacopo De Simoi}}

|-
! style="text-align: center;" colspan="4" | Plasma - Priority Features
{{FeatureInProgress|netbook shell|a plasma shell and various containments/applets tailored for netbooks (tech preview status in 4.4)|notmart@gmail.com|Marco Martin}}

|-
! style="text-align: center;" colspan="4" | Plasma
{{FeatureTodo|libplasma|better text box look with new svg elements|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|accounts applet|a plasma widget that is a central place to add accounts to social sites like identica and opendesktop, optimized for the netbook shell|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|systemtray|visual connection between notifications and new protocol systray icons|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|libplasma|Improvements to Calendar/Clock widgets. Improved config ui. Allow multiple holidays on same day. Allow multiple Holiday Regions. Holidays in Tooltip. Holiday region shown in info. Weekends. etc.|john@layt.net|John Layt}}
{{FeatureInProgress|knowledge base plasmoid|new plasmoid: Opendesktop.org knowledgebase client|notmart@gmail.com|Marco Martin}} {{FeatureInProgress|Quicklaunch Plasmoid|new icon size/rows config ui|l.appelhans@gmx.de|Lukas Appelhans}} {{FeatureInProgress|libplasma|Allow user to choose Calendar System to be displayed in Calendar widgets|john@layt.net|John Layt}} {{FeatureInProgress|opendesktop plasmoid|show friends activity|notmart@gmail.com|Marco Martin}} {{FeatureDone|libplasma/kwin|slide animation for popups done by kwin|notmart@gmail.com|Marco Martin}} {{FeatureDone|System tray|Plasmoid support in the system tray|notmart@gmail.com|Marco Martin}} {{FeatureDone|System tray|config ui to decide between always shown, always hidden and auto hide for each systray item|notmart@gmail.com|Marco Martin}} {{FeatureInProgress|Plasma Addon|Wikipedia KRunner|sebas@kde.org|Sebastian Kügler}} {{FeatureInProgress|Plasma Addon|Webslice Plasmoid, qgraphicswidget|sebas@kde.org|Sebastian Kügler}} {{FeatureInProgress|Plasma Addon|Battery popup layout improvements|sebas@kde.org|Sebastian Kügler}}
{{FeatureTodo|Plasma Addon| Screen-Management Applet for plasma being an easy-to-use alternative to krandrtray adding some functionality for screen management. Builds on top of Kephal |bjoern@ruberg-wegener.de|Björn Ruberg}}
{{FeatureInProgress|Plasma Mouse Plugins UI|Yet Another UI Redesign|chani@kde.org|Chani}} {{FeatureTodo|libplasma|Plasmoid Cloning - because having to set things up from scratch repeatedly gets old fast|chani@kde.org|Chani}} {{FeatureTodo|taskbar|"other desktops" group - I may not have time for this, feel free to take it|chani@kde.org|Chani}} {{FeatureInProgress|Plasma Weather Ion|New Weather Ion for the wetter.com data source provider|thilo@ginkel.com|Thilo-Alexander Ginkel}} {{FeatureInProgress|Plasma Animator|Create new Plasma::Animator API based on Qt 4.6 Kinetic||Adenilson Cavalcanti, Igor Trindade}} {{FeatureTodo|Plasma KineticScrolling|Port KineticScrolling to Qt 4.6 Kinetic||Adenilson Cavalcanti, Igor Trindade}} {{FeatureInProgress|Plasma-Netbook Animated Layouts|Create Animated Layouts to SAL and NewsPaper||Adenilson Cavalcanti, Igor Trindade}} {{FeatureInProgress|Notification queueing|||Aaron Seigo}} {{FeatureInProgress|Trust Levels|package signing and verification||Rob Sheepmaker Aaron Seigo}} {{FeatureInProgress|JS plasmoid improvements|Animations, KIO and QFile bindings; latter two by security policy||Aaron Seigo}}{{FeatureInProgress|Kiosk improvements|||Aaron Seigo}} {{FeatureInProgress|Activity Bar|||Aaron Seigo}} {{FeatureTodo|folderview|Hover action icons in the icon view|fredrik@kde.org|Fredrik Höglund}}
{{FeatureTodo|folderview|Hover animations|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|libplasma|Show the PopupApplet's BusyWidget inside the popup|giuliocamuffo@gmail.com|Giulio Camuffo}}
{{FeatureInProgress|Widgets Explorer| New widgets explorer |anaceciliamb@gmail.com| Ana Cecília Martins Barbosa}}
{{FeatureInProgress|Widgets Explorer| Install widgets from file, Google Gadgets and GHNS |anselmolsm@gmail.com| Anselmo L S Melo}}

|-
! style="text-align: center;" colspan="4" | KWin - Core
{{FeatureInProgress|KWin|Window tabbing|matamax123@gmail.com|Jorge Emilio Mata}} {{FeatureInProgress|KWin|Window tiling|nsm.nikhil@gmail.com|Nikhil Marathe}} {{FeatureDone|KWin|Quick window maximization and tiling by dragging windows to the edge of the screen|kde@martin-graesslin.com|Martin Gräßlin}} {{FeatureDone|KWin|Improved virtual desktop KCM|kde@martin-graesslin.com|Martin Gräßlin}} {{FeatureDone|KWin|Improved window switcher (Alt+Tab)|kde@martin-graesslin.com|Martin Gräßlin}} {{FeatureDone|KWin|SVG based window decoration theme engine (Aurorae)|kde@martin-graesslin.com|Martin Gräßlin}} {{FeatureDone|KWin|Merged Ozone and Nitrogen window decorations into Oxygen|hugo.pereira@free.fr|Hugo Pereira Da Costa}} {{FeatureInProgress|KWin|Support for new EWMH hints|fredrik@kde.org|Fredrik Höglund}}

|-
! style="text-align: center;" colspan="4" | KWin - Desktop Effects
{{FeatureDone|KWin|Mouse action support in Present Windows effect|kde@martin-graesslin.com|Martin Gräßlin}} {{FeatureDone|KWin|New present windows mode to only display windows from a single application|kde@martin-graesslin.com|Martin Gräßlin}} {{FeatureDone|KWin|Improved flip switch effect|kde@martin-graesslin.com|Martin Gräßlin}} {{FeatureDone|KWin|Improved logout blur effect||Lucas Murray}}

|-
! style="text-align: center;" colspan="4" | KDM
|}

= kdebindings =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|pykde4|Python 3 support for PyKDE4|simon@simonzone.com|Simon Edwards}} {{FeatureInProgress|qyoto|Create a new generator for the C# assemblies|arno@arnorehn.de|Arno Rehn}} {{FeatureTodo|qyoto|Replace the current C# cmake macros with more sophisticated ones that also work on windows.|arno@arnorehn.de|Arno Rehn}}

|}

 

= kdeedu =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|KStars|Display Comet Magnitudes whenever possible|akarshsimha@gmail.com|Akarsh Simha}} {{FeatureTodo|KStars|Information links in-place for each technical term|akarshsimha@gmail.com|Akarsh Simha}} {{FeatureTodo|KStars|Tool to suggest star-hopping techniques???|akarshsimha@gmail.com|Akarsh Simha}} {{FeatureTodo|KStars|Extend conjunction tool to have one object unspecified, but have a genre of objects specified instead|akarshsimha@gmail.com|Akarsh Simha}} {{FeatureTodo|KStars|Simulate Lunar Eclipses|akarshsimha@gmail.com|Akarsh Simha}} {{FeatureTodo|KStars|Simulate Satellites and Iridium Flares|akarshsimha@gmail.com|Akarsh Simha}} {{FeatureTodo|KStars|Social and Geographical Integration for KStars|akarshsimha@gmail.com|Akarsh Simha}} {{FeatureTodo|KStars|Marble widget for Geolocation tool|mboquien@free.fr|Médéric Boquien}} {{FeatureTodo|KStars|Better printed star charts|kstars@30doradus.org|Jason Harris}} {{FeatureTodo|KStars|Better rendering of comets/asteroids|kstars@30doradus.org|Jason Harris}} {{FeatureTodo|KStars|Texture mapping of the skymap???|kstars@30doradus.org|Jason Harris}} {{FeatureDone|Cantor|Import to kdeedu |alexanderrieder@gmail.com|Alexander Rieder}}
{{FeatureInProgress|Rocs|Import to kdeedu |tumaix@gmail.com|Tomaz Canabrava}}
{{FeatureInProgress|KAlgebra|Support for lists|aleixpol@kde.org|Aleix Pol}} {{FeatureInProgress|Marble|Add "download region" feature|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|Editing Tools|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|OSM Import|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|UI Simplification|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Custom Layouts|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Discrete Zoom Levels|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Performance Improvements|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|KML Improvements|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Sky Mode|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Measure Tool Plugin|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Settings for plugins|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Kinetic Scrolling|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Optimized 2D Mode|rahn@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Export map to MxN pixel bitmap|inge@lysator.liu.se|Inge Wallin}}
{{FeatureInProgress|Marble|Bookmarks||Gaurav Gupta}}
{{FeatureInProgress|Marble|Time KML support||Harshit Jain}}
{{FeatureTodo|Marble|Support for MarbleWidget::setEnabled( bool )|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Map Contents translation|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Editing GeoDataFeatures|ewoerner@kde.org|Eckhart Wörner}}
{{FeatureInProgress|Marble|Update Map ("F5")|jensmh@gmx.de|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|Layer Management Class|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Plugin architecture for map layers|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Extending GeoPainter|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Marble Runners|hdevalence@gmail.com|Henry de Valence}}
{{FeatureInProgress|Marble|GeoClue Integration |ewoerner@kde.org|Eckhart Wörner}}
{{FeatureInProgress|Marble|Routing |jensmh@gmx.de|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|More map providers (WMS?) |jensmh@gmx.de|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|GeoData Model/View rework||Thibaut Gridel}}
{{FeatureInProgress|Parley|Rewritten practice|d.laidig@gmx.de|Daniel Laidig}} {{FeatureDone|KAlgebra|Improved MathML Presentation support|aleixpol@kde.org|Aleix Pol}} {{FeatureDone|KAlgebra|Added 2D parametric function plotting|aleixpol@kde.org|Aleix Pol}} {{FeatureDone|KAlgebra|Improved jump detections|aleixpol@kde.org|Aleix Pol}} {{FeatureDone|KAlgebra|Made lambda expressions more usable|aleixpol@kde.org|Aleix Pol}} {{FeatureDone|KStars|Improve Observing List Wizard|prakash.mohan@kdemail.net|Prakash Mohan}} {{FeatureDone|KTurtle|Add F2 context help|nielsslot@gmail.com|Niels Slot}} {{FeatureDone|KTurtle|Add SVG export for the canvas|nielsslot@gmail.com|Niels Slot}} {{FeatureDone|KTurtle|Add HTML export of the code|nielsslot@gmail.com|Niels Slot}} {{FeatureDone|KTurtle|Add printing support for the canvas|nielsslot@gmail.com|Niels Slot}} {{FeatureTodo|Marble|Add proper support for GPX waypoints, tracks and routes display|anders@alweb.dk|Anders Lund}}
{{FeatureInProgress|Kalzium|Remove libavogadro snapshot, port to use system libavogadro|mhanwell@kde.org|Marcus D. Hanwell}}
{{FeatureTodo|Kalzium|Port Kalzium to use QGV based periodic table widget|mhanwell@kde.org|Marcus D. Hanwell}}
|}

 

= kdegames =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|KBreakOut|Level Sets|fela.kde@gmail.com|Fela Winkelmolen}} {{FeatureTodo|KBreakOut|Sound|fela.kde@gmail.com|Fela Winkelmolen}} {{FeatureTodo|KDiamond|Intelligent animation pre-caching|majewsky@gmx.net|Stefan Majewsky}} {{FeatureTodo|KDiamond|Refactor Board and Diamond classes|majewsky@gmx.net|Stefan Majewsky}} {{FeatureTodo|Kolf|Replace with Kolf 2 (help on coding, artwork and level design desired) >>delayed to KDE 4.5<<|majewsky@gmx.net|Stefan Majewsky}} {{FeatureTodo|KsirK|rewrite AI code or at least correct most problems related in bug #170777. Volunteers wanted!|kleag@free.fr|Gaël de Chalendar}} {{FeatureTodo|KsirK|Boost playing over Jabber|kleag@free.fr|Gaël de Chalendar}} {{FeatureTodo|KSquares|Re-write computer player, make it act faster and more intelligent|ewoerner@kde.org|Eckhart Wörner}} {{FeatureTodo|KSquares|Add more types of boards: hexagonal, triangular|ewoerner@kde.org|Eckhart Wörner}} {{FeatureInProgress|Gluon|release first gluon lib with one game. [http://gluon.tuxfamily.org/]|istdasklar@gmail.com|Sacha schutz}} {{FeatureInProgress|Granatier|New Bomberman like game for KDE 4|k.hias@gmx.de|Mathias Kraus}} {{FeatureInProgress|Granatier|Implement all Bonuses from the default theme|k.hias@gmx.de|Mathias Kraus}} {{FeatureDone|Granatier|Add support for a background|k.hias@gmx.de|Mathias Kraus}} {{FeatureTodo|Granatier|Sidebar with informations regarding the players, like bonuses, handicaps ...|k.hias@gmx.de|Mathias Kraus}} {{FeatureTodo|Granatier|Arena Editor|k.hias@gmx.de|Mathias Kraus}} {{FeatureTodo|Granatier|Replace Phonon with QtMultimedia for better sound|k.hias@gmx.de|Mathias Kraus}} {{FeatureInProgress|KAtomic|Level Sets|dimsuz@gmail.com|Dmitry Suzdalev}} {{FeatureInProgress|KsirK|Polish the skin editor (doc, contextual help, ...)|kleag@free.fr|Gaël de Chalendar}} {{FeatureInProgress|Palapeli|New puzzle game for KDE 4|majewsky@gmx.net|Stefan Majewsky}} {{FeatureDone|Bovo|Highlight the last move to be easier to spot|pelladigabor@gmail.com|Pelladi Gabor}} {{FeatureDone|Bovo|Enable undo after the game has ended, to be able to correct a fatal mis-click|pelladigabor@gmail.com|Pelladi Gabor}} {{FeatureDone|KBreakOut|Improved keyboard support|fela.kde@gmail.com|Fela Winkelmolen}} {{FeatureDone|KBreakOut|Fullscreen support|fela.kde@gmail.com|Fela Winkelmolen}} {{FeatureDone|KDiamond|Improve time display|majewsky@gmx.net|Stefan Majewsky}} {{FeatureDone|KGoldrunner|Add Mazes game (37 levels), contributed by Steve Mann.|ianw2@optusnet.com.au|Ian Wadham}} {{FeatureDone|KsirK|Previous/Next in start new game as described in bug #170774|kleag@free.fr|Gaël de Chalendar}} {{FeatureInProgress|Kigo|New Go game for KDE 4|sasch.pe@gmx.de|Sascha Peilicke}} {{FeatureDone|Kigo|Fix smaller issues with KNS2|sasch.pe@gmx.de|Sascha Peilicke}} {{FeatureDone|Kigo|Beautify the default theme|sasch.pe@gmx.de|Sascha Peilicke}} {{FeatureInProgress|Kigo|Allow arbitrary jumps in the undo/redo history|sasch.pe@gmx.de|Sascha Peilicke}} {{FeatureInProgress|Kigo|Improve final score visuals|sasch.pe@gmx.de|Sascha Peilicke}} {{FeatureTodo|KSudoku|Import new engine|joselb@gmx.net|Johannes Bergmeier}} {{FeatureTodo|KSudoku|Port game to new engine|joselb@gmx.net|Johannes Bergmeier}} {{FeatureTodo|KSudoku|Adapt view to show information provided by engine|joselb@gmx.net|Johannes Bergmeier}} {{FeatureTodo|KSudoku|Add new actions to GUI|joselb@gmx.net|Johannes Bergmeier}}

|}

= kdegraphics =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|libkexiv2|Store metadata in libexiv2 containers, do not lossily encode to QByteArray. Bug 183171|marcel.wiesweg@gmx.de|Marcel Wiesweg}} {{FeatureTodo|libkexiv2|Expose exiv2 API for accessing embedded previews in RAW files.|marcel.wiesweg@gmx.de|Marcel Wiesweg}} {{FeatureTodo|libkdcraw|Make color management options more flexible|marcel.wiesweg@gmx.de|Marcel Wiesweg}} {{FeatureDone|libksane|Add basic twain support on Windows|kare.sars@iki.fi|Kåre Särs}} {{FeatureDone|libksane|External API for specifying preview resolution|kare.sars@iki.fi|Kåre Särs}} {{FeatureInProgress|libksane|External API for handling selections|kare.sars@iki.fi|Kåre Särs}} {{FeatureTodo|libksane|Improve auto-selection|kare.sars@iki.fi|Kåre Särs}} {{FeatureInProgress|gwenview|Rework start page|agateau@kde.org|Aurelien Gateau}} {{FeatureInProgress|gwenview|Implement picture importer|agateau@kde.org|Aurelien Gateau}} {{FeatureInProgress|gwenview|New save-as behavior (go to saved as document)|agateau@kde.org|Aurelien Gateau}} {{FeatureTodo|gwenview|Show Nepomuk info in image meta info|agateau@kde.org|Aurelien Gateau}} {{FeatureTodo|gwenview|Persistent changes|agateau@kde.org|Aurelien Gateau}} {{FeatureTodo|gwenview|Folder thumbnails|agateau@kde.org|Aurelien Gateau}}

|}

= kdelibs =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|katepart|Add interface to access highlighting information, port html-export plugin|mail@milianw.de|Milian Wolff}} {{FeatureTodo|KCalendarSystem|Add new astronomical calculation support classes to be used in kdelibs to build new astronomically based calendar systems, and in kdepim to build new version of libkholiday.|john@layt.net|John Layt}} {{FeatureTodo|KCalendarSystem|Add new calendar systems: Bahaii, Coptic, Ethiopean, Chinese, Japanese, Buddhist, etc.|john@layt.net|John Layt}} {{FeatureDone|KCalendarSystem|Add new calendar systems: Indian Civil (Saka), Pure Julian, Pure Gregorian.|john@layt.net|John Layt}} {{FeatureTodo|kdecore|Group policy (Windows) backend for KAuth|drf@kde.org|Dario Freddi}} {{FeatureDone|KDEPrint|Add Odd/Even page selection and server-side page selection when using CUPS.|john@layt.net|John Layt}} {{FeatureTodo|KDEPrint|If no file printing support in Qt4.5, migrate FilePrinter class from Okular to enable file printing for all apps via QPrinter. To be discussed on k-c-d first.|john@layt.net|John Layt}} {{FeatureTodo|KDEPrint|Add framework for standard actions for 'Send to...' for e-mail, fax, etc by printing to PDF/PS.|john@layt.net|John Layt}} {{FeatureTodo|kdeui|Implement caps-lock warning for password entry widgets|lemma@confuego.org|Michael Leupold}} {{FeatureInProgress|KLocale|Implement ISO 4217 Currency Code support (http://en.wikipedia.org/wiki/ISO_4217).|john@layt.net|John Layt}} {{FeatureInProgress|KLocale|Separate numeric decimal places and monetary decimal places.|john@layt.net|John Layt}} {{FeatureTodo|KLocale|Implement support for number grouping other than thousands using LC_NUMERIC and LC_MONETARY formats, e.g. India 00 00 000 and China 0000 0000.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Add configuration for AM/PM symbols.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Full POSIX compliant format support for date, time, numbers and money.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Implement more 'named' date/time formats, e.g. ISO, UnixTimestamp, RFC3339, etc.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Add Full date format in addition to existing short and long.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Add default colour to optionally display negative numbers.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Implement separate backends for each supported platform/desktop to use platform localisation in place of KDE locale.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Implement support for additional Country Code standards: ISO Alpha 3, ISO Numeric 3, FIPS-10.|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Implement support for Country Code sub-regions, i.e. States/Provinces/etc. Needed for new KHolidays.|john@layt.net|John Layt}}
{{FeatureTodo|kdeui|Improvements to KDatePicker/KDateTable for feature parity with Plasma Calendar widget, i.e. holiday support, select calendar system, etc.|john@layt.net|John Layt}}
{{FeatureTodo|Khtml|Improvements in kwallet integration|edulix@gmail.com|Eduardo Robles Elvira}} {{FeatureTodo|Khtml|Basic audio/video tag support|germain@ebooksfrance.org|Michael Howell and Germain Garand}} {{FeatureTodo|Khtml|Implement more of DOM3's CSSOM View module|germain@ebooksfrance.org|Germain Garand}} {{FeatureInProgress|kfile|Move KMetaDataWidget and KMetaDataConfigurationDialog from Dolphin to kfile|peter.penz@gmx.at|Peter Penz}} {{FeatureDone|katepart|Add mapping support for the vi input mode's normal mode|ehambergαgmail.com|Erlend Hamberg}} {{FeatureTodo|katepart|Add visual block mode and make the basic commands support it|ehambergαgmail.com|Erlend Hamberg}} {{FeatureInProgress|katepart|Improve TemplateInterface, i.e. snippet support|mail@milianw.de|Milian Wolff}} {{FeatureInProgress|kdecore|Move event-filter installation out of KApplication and into a new class|lemma@confuego.org|Michael Leupold}} {{FeatureInProgress|kdecore|Polkit-1 backend for KAuth|drf@kde.org|Dario Freddi}} {{FeatureInProgress|kdeui|Support floating point font sizes|christoph@maxiom.de|Christoph Feck}} {{FeatureInProgress|kdeui|Finish the time chooser widget|lemma@confuego.org|Michael Leupold}} {{FeatureInProgress|kio|Limit number of connections per host (per application), add job priorities|ahartmetz@gmail.com|Andreas Hartmetz}} {{FeatureInProgress|kio|Support for automatically renaming conflicting files during copy and move operations|toddrme2178@gmail.com|Todd}} {{FeatureTodo|kio|Better file information in file conflict dialog|toddrme2178@gmail.com|Todd}} {{FeatureInProgress|kio|Remember downloads via Nepomuk|trueg@kde.org|Sebastian Trueg}} {{FeatureInProgress|webkit|Move KDE integration of QtWebKit into kdelibs (but not KPart!)|uwolfer@kde.org|Urs Wolfer}} {{FeatureInProgress|buildsystem|Modular build of KDE modules|neundorf@kde.org|Alexander Neundorf}} {{FeatureDone|katepart|Enable command line scripting again|dhaumann@kde.org|Dominik Haumann}} {{FeatureDone|katepart|Support byte-order mark in unicode files|jowenn@kde.org|Joseph Wenninger}} {{FeatureInProgress|katepart|Improve katepart Vim mode.|alecastanyo@gmail.com|Alejandro Castaño}} {{FeatureInProgress|nepomuk|Add const versions of the accessor methods to the Nepomuk::Types classes|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|nepomuk|Get libnepomukquery into kdelibs|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|kdeui|Finalize the api for the new systemtray: KStatusNotifierItem|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|kdeui|DBus interface in StatusNotifierItem to connect it with freedesktop notifications instances|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|kdeui|API to integrate KStatusNotifierItem and KNotification: both as class api and DBus specification API|davide.bettio@kdemail.net|Davide Bettio}}
{{FeatureInProgress|kfile|Make status of file I/O display on file/folder icons("progress in icons").|shaun.reich@kdemail.net|Shaun Reich}}
{{FeatureInProgress|knewstuff|Introduce binary incompatible knewstuff library (as knewstuff3, keeping knewstuff2 as well) which can talk directly to open desktop services via libattica|jpwhiting@kde.org|Jeremy Whiting}}
{{FeatureInProgress|katepart|Factor out a generic high-level search class from the search bar. To be used by the VI input mode.|bbeschow@cs.tu-berlin.de|Bernhard Beschow}}|}

= kdemultimedia =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|KMix|Nicer OSD (icon, mute state)|esken@kde.org|Christian Esken}} {{FeatureTodo|KMix|Amend Keyboard Shortcuts|esken@kde.org|Christian Esken}} {{FeatureInProgress|KMix|Allow arbitrary ordering of controls|esken@kde.org|Christian Esken}} {{FeatureInProgress|KMix|Add WhatsThis help on controls (Bug 70042)|esken@kde.org|Christian Esken}}
{{FeatureInProgress|KMix|Generic per-App volume tab ( pulse,phonon,oss4)|helio@kde.org|Helio Castro}}

|}

 

= kdenetwork =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Kopete|UPnp Support|mattr@kde.org|Matt Rogers}} {{FeatureTodo|Kopete|Jabber Jingle video support|detlev.casanova@gmail.com|Detlev Casanova}} {{FeatureTodo|Kopete|Jabber Jingle ICE support|detlev.casanova@gmail.com|Detlev Casanova}} {{FeatureTodo|Kopete|Add support for urls to Bonjour plugin|kossebau@kde.org|Friedrich W. H. Kossebau}} {{FeatureTodo|Kopete|Rich text support for ICQ|kedgedev@gmail.com|Roman Jarosz}} {{FeatureInProgress|KGet|Support for verifying signed files|mat69@gmx.net|Matthias Fuchs}} {{FeatureInProgress|KGet|Support for custom NewTransferDialog in BTPlugin|l.appelhans@gmx.de|Lukas Appelhans}} {{FeatureInProgress|Kopete|Contacts plasmoid|earthwings@gentoo.org|Dennis Nienhüser}} {{FeatureInProgress|Kopete|Telepathy protocol plugin|grundleborg@googlemail.com|George Goldberg}} {{FeatureInProgress|Kopete|Telepathy Tubes Desktop Sharing plugin|grundleborg@googlemail.com|George Goldberg}} {{FeatureInProgress|Kopete|Akonadi Logger(modify the history plugin)|roideuniverse@gmail.com|Kaushik Saurabh}} {{FeatureDone|Krdc|Telepathy Tubes support||Abner Silva}} {{FeatureInProgress|Krfb|Telepathy Tubes support|grundleborg@googlemail.com|George Goldberg}} {{FeatureInProgress|Krfb|Core restructuring|grundleborg@googlemail.com|George Goldberg}} {{FeatureInProgress|Telepathy|Account Management KCM|grundleborg@googlemail.com|George Goldberg}} {{FeatureInProgress|Telepathy|Mission Control launcher KDED|grundleborg@googlemail.com|George Goldberg}} {{FeatureDone|Kopete|Create avatars from a webcam device |alex@eyeos.org |Alex Fiestas}} {{FeatureDone|Krdc|Redesigned workflow to create a new connection|uwolfer@kde.org|Urs Wolfer}} {{FeatureDone|Krdc|Full Screen Switching|murraytony@gmail.com|Tony Murray}}

|}

 

= kdepim =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|Akregator|Port to use KNotificationItem|tpr@d5k.net|Teemu Rytilahti}}
{{FeatureInProgress|KAlarm|Implement Akonadi support|djarvie @ kde.org|David Jarvie}}
{{FeatureInProgress|KAlarm|Provide audio-only alarms|djarvie @ kde.org|David Jarvie}}
{{FeatureInProgress|KJots|Port to Grantlee for theming support|steveire|Stephen Kelly}}
{{FeatureInProgress|KJots|Port to Akonadi|steveire|Stephen Kelly}}
|}

= kdepimlibs =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
|}

 

= kdeplasma-addons =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureDone|plasmaboard|Added a virtual keyboard plasmoid for touchscreen users|bjoern@ruberg-wegener.de|Björn Ruberg}}
{{FeatureInProgress|KDE Observatory|A new plasmoid for visualizing KDE projects status (commits, commiters, bugs, krazy status, etc)|sandroandrade@kde.org|Sandro S. Andrade}}
{{FeatureInProgress|opendesktop|Add messaging|ewoerner@kde.org|Eckhart Wörner}} {{FeatureInProgress|opendesktop|Add friendship management|ewoerner@kde.org|Eckhart Wörner}}
{{FeatureInProgress|ocs engine|Add possibility to use different providers, use attica from kdesupport|ewoerner@kde.org|Eckhart Wörner}}
{{FeatureTodo|knowledgebase|port knowledgebase plasmoid to new engine|ewoerner@kde.org|Eckhart Wörner}}
{{FeatureTodo|knowledgebase|Add categories|ewoerner@kde.org|Eckhart Wörner}}
{{FeatureInProgress|opendesktop|port opendesktop plasmoid to new engine and rename accordingly|ewoerner@kde.org|Eckhart Wörner}}
{{FeatureInProgress|opendesktop activities|port opendesktop activities plasmoid to new engine and rename accordingly|ewoerner@kde.org|Eckhart Wörner}}
{{FeatureInProgress|microblogging|new appearance and new twitter api pieces support|notmart@gmail.com|Marco Martin}}
|}

 

= kdesdk =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Lokalize|Integrate snowball stemmer for glossary|shafff@NOSPAMukr.net|Nick Shaforostoff}} {{FeatureTodo|Lokalize|Continue implementing XLIFF spec|shafff@NOSPAMukr.net|Nick Shaforostoff}} {{FeatureTodo|Lokalize|Segmentation [editing] functionality|shafff@NOSPAMukr.net |Nick Shaforostoff}} {{FeatureTodo|Lokalize|Remote translation memories|shafff@NOSPAMukr.net|Nick Shaforostoff}} {{FeatureTodo|Lokalize|Integrate with nepomuk (fast stats retrieval, tag cloud - incl sharing!)|shafff@NOSPAMukr.net|Nick Shaforostoff}} {{FeatureDone|Kate|Add common vim commands like :wq, :new, :bp/bn, etc.|ehambergαgmail.com|Erlend Hamberg}} {{FeatureTodo|Kate|Replace old snippet plugin through TNG plugin|jowenn(you_know)kde(here_too)org|Joseph Wenninger}} {{FeatureTodo|Kate|Integreate GHNS into snippets TNG|jowenn(you_know)kde(here_too)org|Joseph Wenninger}} {{FeatureInProgress|Kate|Refactor parts from snippets TNG plugin into a common library for use by the plugin and for use in kdevelop|jowenn(you_know)kde(here_too)org|Joseph Wenninger}}

|}

 

= kdeutils =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Ark|Add an options dialog (maybe)|haraldhv@stud.ntnu.no|Harald Hvaal}} {{FeatureTodo|Ark|Support for custom options from the compression interface (eg. a slider for selecting compression level for rar files)|haraldhv@stud.ntnu.no|Harald Hvaal}} {{FeatureTodo|Ark|Add feedback for the latest operation in the status bar|kubito@gmail.com|Raphael Kubo da Costa}} {{FeatureTodo|Ark|Add feedback for the latest operation in the status bar|kubito@gmail.com|Raphael Kubo da Costa}} {{FeatureTodo|Ark|Try multiple plugins for each archive type before failing|kubito@gmail.com|Raphael Kubo da Costa}} {{FeatureTodo|Ark|Make the internal previewer optional|kubito@gmail.com|Raphael Kubo da Costa}} {{FeatureTodo|KGpg|Make keyserver actions possible to use on multiple keyservers at once|kde@opensource.sf-tec.de|Rolf Eike Beer}} {{FeatureTodo|KGpg|Add "caff" mode for keysigning|kde@opensource.sf-tec.de|Rolf Eike Beer}} {{FeatureTodo|KGpg|Allow searching for trust path in keyring|kde@opensource.sf-tec.de|Rolf Eike Beer}} {{FeatureTodo|KGpg|Add improved key import result window (with useful summary, filtering, reasonable default size etc.)|kde@opensource.sf-tec.de|Rolf Eike Beer}} {{FeatureTodo|KGpg|Make generating a key a KJob so it get's better notification support|kde@opensource.sf-tec.de|Rolf Eike Beer}} {{FeatureTodo|Okteta|add editing capability to Decoding table |kossebau@kde.org|Friedrich W. H. Kossebau}} {{FeatureTodo|Okteta|add Kate-like search tool|kossebau@kde.org|Friedrich W. H. Kossebau}} {{FeatureTodo|Okteta|add support for import by drop, both url and data|kossebau@kde.org|Friedrich W. H. Kossebau}} {{FeatureTodo|Okteta|copy again puts also a value or char variant of the data to clipboard|kossebau@kde.org|Friedrich W. H. Kossebau}} {{FeatureTodo|Okteta|add support for memory mapping of files and 64-bit addressing|kossebau@kde.org|Friedrich W. H. Kossebau}} {{FeatureTodo|Okteta|add further export formats like s-record and intel 16|kossebau@kde.org|Friedrich W. H. Kossebau}} {{FeatureTodo|Okteta|add support for jobs like io, printing, string search or filter|kossebau@kde.org|Friedrich W. H. Kossebau}} {{FeatureTodo|Okteta|Add Okular like embedded notifications|kossebau@kde.org|Friedrich W. H. Kossebau}} {{FeatureTodo|Okteta|Store bookmarks and other view settings for next load|kossebau@kde.org|Friedrich W. H. Kossebau}} {{FeatureTodo|Okteta|Add global toggle option for the offset display, hex or decimal|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add QIODevice for AbstractByteArrayModel and make mimetype detection use this instead of only filename |kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add Kate-like combined dialogs to query for actions on files|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Improve the titels of the changes to the bytearray to be more descriptive, best using ids to avoid text string|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Merge row and column widgets into one|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Refactor mouse input to controllers for the bytearray widget|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add a general KPart adapter to Kasten, than finish port of Okteta KPart to Okteta Kasten|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Make all user interaction in the KastenCore managers plugin-based|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add UTF-8 option to bytearray lineedit|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add marking of bytearray section to widgets, so tools like strings or pod decoder can mark the source, instead of selecting it|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|printer-applet|Restore feature parity with KDEPrint3 where possible.||Jonathon Riddell, John Layt}} {{FeatureInProgress|Okteta|Make dialogs for Goto, Search & Replace embedded|kossebau@kde.org|Friedrich W. H. Kossebau}} {{FeatureInProgress|Okteta|Add tool to view decoding of complex structures|kossebau@kde.org|Friedrich W. H. Kossebau}} {{FeatureDone|kdelirc|Communicate to lirc through solid|michael_zanetti@gmx.net|Michael Zanetti}} {{FeatureInProgress|kdelirc|Integrate solid backend into kdelirc frontend|fscheffold@googlemail.com|Frank Scheffold}} {{FeatureTodo|kdelirc|Cycle mode function|fscheffold@googlemail.com|Frank Scheffold}} {{FeatureTodo|kdelirc|Add a try button in configurations|michael_zanetti@gmx.net|Michael Zanetti}} {{FeatureDone|Okteta|Rename libkakao to Kasten and make the Okteta KPart use it|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|Add embedded dialog to set selection range|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|Add Base64 encoder|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|Added data generators, like pattern, sequence or from clipboard|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|Added option to split views|kossebau@kde.org|Friedrich W. H. Kossebau}}

|}

= Other =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|kdesupport|Add libattica to kdesupport|ewoerner@kde.org|Eckhart Wörner}}
|}

Schedules/KDE4/4.4 Feature Plan

2009-09-23T13:27:10Z

Grundleborg: update statuses of telepathy and krfb bits

Schedules/KDE4/4.4 Feature Plan

2009-09-16T08:58:49Z

Grundleborg: forgot one thing for telepathy stuff

Schedules/KDE4/4.4 Feature Plan

2009-09-16T08:57:17Z

Grundleborg: Add Telepathy related features I'm working on

Projects/Telepathy

2009-07-22T15:46:25Z

Grundleborg: /* Problems */

==Introduction==
[http://telepathy.freedesktop.org The Telepathy framework] is a DBus specification which provides a cross-desktop and cross-protocol abstraction layer for instant messaging, voice/video over IP and collaborative applications. See the [http://telepathy.freedesktop.org Telepathy web site] for more information about Telepathy itself.

This project is focused on integrating Telepathy with KDE. Our high-level aims are the following:
* to provide a unified instant messaging and voice/video communication framework within KDE, which integrates throughout the desktop experience.
* to provide collaborative features in applications which fit seemlessly into the KDE platform
* to provide the infrastructure within KDE necessary to acheive the above two, using cross-desktop specifications and implementations wherever possible.

==Infrastructure==
This section contains details of all the Telepathy-in-KDE infrastructure components, and their statuses.

===Telepathy Integration Daemon===

{{Warning| Before working on this component, please talk to grundleborg on #kde-telepathy. See [[/TelepathyNepomukPlans|here]] for more information on Telepathy/Semantic Desktop Integration.}}

This is a small light-weight daemon that monitors the Telepathy Account Manager and keeps ensures that all Accounts are recorded in Nepomuk as NCO:Contact instances of "myself" and that they each have a Telepathy Contacts Akonadi Resource instance.

It could possibly be made into a KDED module, but I'm not sure if this is a good idea. [[User:Grundleborg|Grundleborg]]

====Status====
The bare bones are implemented, but the Nepomuk part is blocking on standardising the Ontologies for telepathy specific stuff and how to access the "myself" PIMO:Person through Nepomuk. The Akonadi part is blocking on getting the Telepathy Contacts Akonadi Resource below implemented.

====Source Code====
Source code can be found in KDE svn at:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-integration-daemon
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-integration-daemon websvn link].

===Telepathy Contacts Akonadi Resource===

{{Warning| Before working on this component, please talk to grundleborg on #kde-telepathy. See [[/TelepathyNepomukPlans|here]] for more information on Telepathy/Semantic Desktop Integration.}}

This is an Akonadi Resource that synchronises the contacts of a Telepathy Account into Akonadi as vcards. The instances of this resource are managed by the telepathy-integration-daemon mentioned above.

====Status====
Partially implemented. Requires some Telepathy CM's to implement the org.freedesktop.Telepathy.Connection.Interface.ContactInfo.DRAFT interface to complete it, since we shouldn't try and support legacy CM's which don't support that interface.

====Source Code====
The code can be found in the KDE svn playground at the following URL:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-contacts-resource
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-contacts-resource websvn link].

===Presence Dataengine and Plasmoid===

====Status====

The dataengine is functional, allowing you to set the Requested Presence and Status Message, and view the Current Presence and Status Message of all Telepathy Accounts.

The applet is not really functional. Andrunko has asked Nuno for some mockups of how to make a nice looking applet.

====Source Code====

Applet in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/applets/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/applets/presence websvn link].

Dataengine in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/dataengines/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/dataengines/presence websvn link].

===Account Management KCM===
====Ideas====
* One single UI that any application can load for add/edit/delete Telepathy Accounts

* Creates a dynamic UI on-the-fly using Connection Manager parameters, but this should be used only when a specific UI plugin for that CM isn't installed.

* Create specialised UI plugins for the popular CM's (e.g. gabble) since dynamic UI will be pretty crap usability-wise.

====Status====

Some code is there in svn, but it's pretty much just experimental shell-files. So feel free to ignore existing code to implement this :) [[User:Grundleborg|Grundleborg]]

====Source Code====

Source code is in KDE svn playground at:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-accounts-kcm/
</pre>

[http://websvn.kde.org/trunk/playground/network/telepathy-accounts-kcm/ websvn link].

===KWallet Account Manager===
This was originally intended to be an implementation of the Telepathy AccountManager which was integrated with KDE and KWallet for the account data storage. However, in light of the shared-secrets API being developed on freedesktop.org which will unify the KWallet and Gnome-Keyring API it would probably be a better use of resources to just get Mission Control ported to that instead.

In light of that, its probably best not to work on telepathy-accountmanager-kwallet or telepathy-qt4-accountmanager at the moment.

==Telepathy Enabled Applications==

==Problems==

* QtDBus doesn't have peer-to-peer DBus implemented properly - the classes are just non-functional stubs. This stops us from implementing D-tubes in KDE/Qt based Telepathy applications. Upstream bug is private in Qt Software's tracker and this is unlikely to get fixed by Qt Software, so if anyone feels like implementing it and then merging it upstream into Qt, that would be really fantastic.

* Telepathy-Mission-Control still requires you to use both the channel dispatcher part of it and the Account Manager. For KDE, we need to be able to use only the Channel Dispatcher from Mission-Control and have that talk over the standard Telepathy DBus interfaces to the KDE KWallet based Account Manager.(OR we need MC's AM to start using the shared-secrets API)

==Trying out Telepathy==

=== Prerequisites ===
* telepathy-mission-control 5
* telepathy-qt4
* telepathy-gabble, telepathy-butterfly, telepathy-haze (for jabber/msn/everything else support respectively)

=== KDE Stuff ===
All the KDE Telepathy infrastructure components are detailed above, and they may or may not be in working/compiling order. Any problems, ask in #kde-telepathy.

==How to Get Involved==
Come and talk to us in #kde-telepathy on irc.freenode.net. There is also a #telepathy channel for talking about Telepathy stuff that is not specific to KDE.

==Frequently Asked Questions==

=== What happened to Decibel? ===

Decibel development has completely stagnated and it no longer works with recent Telepathy components. It is not necessary to use Decibel to get Telepathy support in KDE - all the applications/components above do not require Decibel to compile or function.

Projects/Telepathy/TelepathyNepomukPlans

2009-07-22T15:44:24Z

Grundleborg: create page

==Telepathy->Nepomuk Integration Plans==
This section contains a dump of some of the things discussed amongst grundleborg (KDE+Telepathy) trueg (KDE+Nepomuk), barisione (Gnome+Telepathy), davyd (Gnome+Telepathy) and others on the issue of integration between Nepomuk and Telepathy.

=== Cross Desktop Compatability ===
We want to make the Nepomuk integration be the same as much as possible across Gnome and KDE. Things we'd like to have in common.
- Ontologies for storing the Telepathy specific metadata
- Implementation of a daemon to keep this metadata in sync

=== Ontologies ===
barisione (in #telepathy) is working on writing these, at which point they'll be shown to Nepomuk people for review.

Photos of the whiteboard showing a proposed diagram of the ontologies to follow as soon as I get hold of them :)

=== Daemon ===
The daemon will be responsible for keeping the nepomuk metadata in sync with Telepathy. Since tracker and soprano-server will eventually use the same (xesam2) dbus API, we should be able to write a QtCore/QtDBus only daemon which will use Soprano as the API to keep stuff in sync. This single implementation should then be usable by both KDE and Gnome, reducing code duplication.

grundleborg (in #kde-telepathy) is working on this.

This means the telepathy-integration-daemon will either be deprecated or have its role changed to only be responsible for the Akonadi Telepathy contact resource management.

=== Do we still need Akonadi integration? ===
This question is as yet unanswered. What does it give us that direct nepomuk integration doesn't give?

Projects/Telepathy

2009-07-22T15:27:25Z

Grundleborg: add warning

==Introduction==
[http://telepathy.freedesktop.org The Telepathy framework] is a DBus specification which provides a cross-desktop and cross-protocol abstraction layer for instant messaging, voice/video over IP and collaborative applications. See the [http://telepathy.freedesktop.org Telepathy web site] for more information about Telepathy itself.

This project is focused on integrating Telepathy with KDE. Our high-level aims are the following:
* to provide a unified instant messaging and voice/video communication framework within KDE, which integrates throughout the desktop experience.
* to provide collaborative features in applications which fit seemlessly into the KDE platform
* to provide the infrastructure within KDE necessary to acheive the above two, using cross-desktop specifications and implementations wherever possible.

==Infrastructure==
This section contains details of all the Telepathy-in-KDE infrastructure components, and their statuses.

===Telepathy Integration Daemon===

{{Warning| Before working on this component, please talk to grundleborg on #kde-telepathy. See [[/TelepathyNepomukPlans|here]] for more information on Telepathy/Semantic Desktop Integration.}}

This is a small light-weight daemon that monitors the Telepathy Account Manager and keeps ensures that all Accounts are recorded in Nepomuk as NCO:Contact instances of "myself" and that they each have a Telepathy Contacts Akonadi Resource instance.

It could possibly be made into a KDED module, but I'm not sure if this is a good idea. [[User:Grundleborg|Grundleborg]]

====Status====
The bare bones are implemented, but the Nepomuk part is blocking on standardising the Ontologies for telepathy specific stuff and how to access the "myself" PIMO:Person through Nepomuk. The Akonadi part is blocking on getting the Telepathy Contacts Akonadi Resource below implemented.

====Source Code====
Source code can be found in KDE svn at:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-integration-daemon
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-integration-daemon websvn link].

===Telepathy Contacts Akonadi Resource===

{{Warning| Before working on this component, please talk to grundleborg on #kde-telepathy. See [[/TelepathyNepomukPlans|here]] for more information on Telepathy/Semantic Desktop Integration.}}

This is an Akonadi Resource that synchronises the contacts of a Telepathy Account into Akonadi as vcards. The instances of this resource are managed by the telepathy-integration-daemon mentioned above.

====Status====
Partially implemented. Requires some Telepathy CM's to implement the org.freedesktop.Telepathy.Connection.Interface.ContactInfo.DRAFT interface to complete it, since we shouldn't try and support legacy CM's which don't support that interface.

====Source Code====
The code can be found in the KDE svn playground at the following URL:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-contacts-resource
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-contacts-resource websvn link].

===Presence Dataengine and Plasmoid===

====Status====

The dataengine is functional, allowing you to set the Requested Presence and Status Message, and view the Current Presence and Status Message of all Telepathy Accounts.

The applet is not really functional. Andrunko has asked Nuno for some mockups of how to make a nice looking applet.

====Source Code====

Applet in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/applets/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/applets/presence websvn link].

Dataengine in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/dataengines/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/dataengines/presence websvn link].

===Account Management KCM===
====Ideas====
* One single UI that any application can load for add/edit/delete Telepathy Accounts

* Creates a dynamic UI on-the-fly using Connection Manager parameters, but this should be used only when a specific UI plugin for that CM isn't installed.

* Create specialised UI plugins for the popular CM's (e.g. gabble) since dynamic UI will be pretty crap usability-wise.

====Status====

Some code is there in svn, but it's pretty much just experimental shell-files. So feel free to ignore existing code to implement this :) [[User:Grundleborg|Grundleborg]]

====Source Code====

Source code is in KDE svn playground at:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-accounts-kcm/
</pre>

[http://websvn.kde.org/trunk/playground/network/telepathy-accounts-kcm/ websvn link].

===KWallet Account Manager===
This was originally intended to be an implementation of the Telepathy AccountManager which was integrated with KDE and KWallet for the account data storage. However, in light of the shared-secrets API being developed on freedesktop.org which will unify the KWallet and Gnome-Keyring API it would probably be a better use of resources to just get Mission Control ported to that instead.

In light of that, its probably best not to work on telepathy-accountmanager-kwallet or telepathy-qt4-accountmanager at the moment.

==Telepathy Enabled Applications==

==Problems==

* QtDBus doesn't have peer-to-peer DBus implemented properly - the classes are just non-functional stubs. This stops us from implementing D-tubes in KDE/Qt based Telepathy applications. Upstream bug is private in Qt Software's tracker and this is unlikely to get fixed by Qt Software, so if anyone feels like implementing it and then merging it upstream into Qt, that would be really fantastic.

* Telepathy-Mission-Control still requires you to use both the channel dispatcher part of it and the Account Manager. For KDE, we need to be able to use only the Channel Dispatcher from Mission-Control and have that talk over the standard Telepathy DBus interfaces to the KDE KWallet based Account Manager.

==Trying out Telepathy==

=== Prerequisites ===
* telepathy-mission-control 5
* telepathy-qt4
* telepathy-gabble, telepathy-butterfly, telepathy-haze (for jabber/msn/everything else support respectively)

=== KDE Stuff ===
All the KDE Telepathy infrastructure components are detailed above, and they may or may not be in working/compiling order. Any problems, ask in #kde-telepathy.

==How to Get Involved==
Come and talk to us in #kde-telepathy on irc.freenode.net. There is also a #telepathy channel for talking about Telepathy stuff that is not specific to KDE.

==Frequently Asked Questions==

=== What happened to Decibel? ===

Decibel development has completely stagnated and it no longer works with recent Telepathy components. It is not necessary to use Decibel to get Telepathy support in KDE - all the applications/components above do not require Decibel to compile or function.

Projects/Telepathy

2009-07-22T15:26:27Z

Grundleborg: /* Telepathy Integration Daemon */

==Introduction==
[http://telepathy.freedesktop.org The Telepathy framework] is a DBus specification which provides a cross-desktop and cross-protocol abstraction layer for instant messaging, voice/video over IP and collaborative applications. See the [http://telepathy.freedesktop.org Telepathy web site] for more information about Telepathy itself.

This project is focused on integrating Telepathy with KDE. Our high-level aims are the following:
* to provide a unified instant messaging and voice/video communication framework within KDE, which integrates throughout the desktop experience.
* to provide collaborative features in applications which fit seemlessly into the KDE platform
* to provide the infrastructure within KDE necessary to acheive the above two, using cross-desktop specifications and implementations wherever possible.

==Infrastructure==
This section contains details of all the Telepathy-in-KDE infrastructure components, and their statuses.

===Telepathy Integration Daemon===

{{Warning| Before working on this component, please talk to grundleborg on #kde-telepathy. See [[/TelepathyNepomukPlans|here]] for more information on Telepathy/Semantic Desktop Integration.}}

This is a small light-weight daemon that monitors the Telepathy Account Manager and keeps ensures that all Accounts are recorded in Nepomuk as NCO:Contact instances of "myself" and that they each have a Telepathy Contacts Akonadi Resource instance.

It could possibly be made into a KDED module, but I'm not sure if this is a good idea. [[User:Grundleborg|Grundleborg]]

====Status====
The bare bones are implemented, but the Nepomuk part is blocking on standardising the Ontologies for telepathy specific stuff and how to access the "myself" PIMO:Person through Nepomuk. The Akonadi part is blocking on getting the Telepathy Contacts Akonadi Resource below implemented.

====Source Code====
Source code can be found in KDE svn at:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-integration-daemon
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-integration-daemon websvn link].

===Telepathy Contacts Akonadi Resource===
This is an Akonadi Resource that synchronises the contacts of a Telepathy Account into Akonadi as vcards. The instances of this resource are managed by the telepathy-integration-daemon mentioned above.

====Status====
Partially implemented. Requires some Telepathy CM's to implement the org.freedesktop.Telepathy.Connection.Interface.ContactInfo.DRAFT interface to complete it, since we shouldn't try and support legacy CM's which don't support that interface.

====Source Code====
The code can be found in the KDE svn playground at the following URL:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-contacts-resource
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-contacts-resource websvn link].

===Presence Dataengine and Plasmoid===

====Status====

The dataengine is functional, allowing you to set the Requested Presence and Status Message, and view the Current Presence and Status Message of all Telepathy Accounts.

The applet is not really functional. Andrunko has asked Nuno for some mockups of how to make a nice looking applet.

====Source Code====

Applet in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/applets/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/applets/presence websvn link].

Dataengine in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/dataengines/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/dataengines/presence websvn link].

===Account Management KCM===
====Ideas====
* One single UI that any application can load for add/edit/delete Telepathy Accounts

* Creates a dynamic UI on-the-fly using Connection Manager parameters, but this should be used only when a specific UI plugin for that CM isn't installed.

* Create specialised UI plugins for the popular CM's (e.g. gabble) since dynamic UI will be pretty crap usability-wise.

====Status====

Some code is there in svn, but it's pretty much just experimental shell-files. So feel free to ignore existing code to implement this :) [[User:Grundleborg|Grundleborg]]

====Source Code====

Source code is in KDE svn playground at:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-accounts-kcm/
</pre>

[http://websvn.kde.org/trunk/playground/network/telepathy-accounts-kcm/ websvn link].

===KWallet Account Manager===
This was originally intended to be an implementation of the Telepathy AccountManager which was integrated with KDE and KWallet for the account data storage. However, in light of the shared-secrets API being developed on freedesktop.org which will unify the KWallet and Gnome-Keyring API it would probably be a better use of resources to just get Mission Control ported to that instead.

In light of that, its probably best not to work on telepathy-accountmanager-kwallet or telepathy-qt4-accountmanager at the moment.

==Telepathy Enabled Applications==

==Problems==

* QtDBus doesn't have peer-to-peer DBus implemented properly - the classes are just non-functional stubs. This stops us from implementing D-tubes in KDE/Qt based Telepathy applications. Upstream bug is private in Qt Software's tracker and this is unlikely to get fixed by Qt Software, so if anyone feels like implementing it and then merging it upstream into Qt, that would be really fantastic.

* Telepathy-Mission-Control still requires you to use both the channel dispatcher part of it and the Account Manager. For KDE, we need to be able to use only the Channel Dispatcher from Mission-Control and have that talk over the standard Telepathy DBus interfaces to the KDE KWallet based Account Manager.

==Trying out Telepathy==

=== Prerequisites ===
* telepathy-mission-control 5
* telepathy-qt4
* telepathy-gabble, telepathy-butterfly, telepathy-haze (for jabber/msn/everything else support respectively)

=== KDE Stuff ===
All the KDE Telepathy infrastructure components are detailed above, and they may or may not be in working/compiling order. Any problems, ask in #kde-telepathy.

==How to Get Involved==
Come and talk to us in #kde-telepathy on irc.freenode.net. There is also a #telepathy channel for talking about Telepathy stuff that is not specific to KDE.

==Frequently Asked Questions==

=== What happened to Decibel? ===

Decibel development has completely stagnated and it no longer works with recent Telepathy components. It is not necessary to use Decibel to get Telepathy support in KDE - all the applications/components above do not require Decibel to compile or function.

Projects/Telepathy

2009-07-22T15:25:55Z

Grundleborg: add warning

==Introduction==
[http://telepathy.freedesktop.org The Telepathy framework] is a DBus specification which provides a cross-desktop and cross-protocol abstraction layer for instant messaging, voice/video over IP and collaborative applications. See the [http://telepathy.freedesktop.org Telepathy web site] for more information about Telepathy itself.

This project is focused on integrating Telepathy with KDE. Our high-level aims are the following:
* to provide a unified instant messaging and voice/video communication framework within KDE, which integrates throughout the desktop experience.
* to provide collaborative features in applications which fit seemlessly into the KDE platform
* to provide the infrastructure within KDE necessary to acheive the above two, using cross-desktop specifications and implementations wherever possible.

==Infrastructure==
This section contains details of all the Telepathy-in-KDE infrastructure components, and their statuses.

===Telepathy Integration Daemon===

{{Warning| Before working on this component, please talk to grundleborg on #kde-telepathy. See [[TelepathyNepomukPlans|here]] for more information on Telepathy/Semantic Desktop Integration.}}

This is a small light-weight daemon that monitors the Telepathy Account Manager and keeps ensures that all Accounts are recorded in Nepomuk as NCO:Contact instances of "myself" and that they each have a Telepathy Contacts Akonadi Resource instance.

It could possibly be made into a KDED module, but I'm not sure if this is a good idea. [[User:Grundleborg|Grundleborg]]

====Status====
The bare bones are implemented, but the Nepomuk part is blocking on standardising the Ontologies for telepathy specific stuff and how to access the "myself" PIMO:Person through Nepomuk. The Akonadi part is blocking on getting the Telepathy Contacts Akonadi Resource below implemented.

====Source Code====
Source code can be found in KDE svn at:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-integration-daemon
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-integration-daemon websvn link].

===Telepathy Contacts Akonadi Resource===
This is an Akonadi Resource that synchronises the contacts of a Telepathy Account into Akonadi as vcards. The instances of this resource are managed by the telepathy-integration-daemon mentioned above.

====Status====
Partially implemented. Requires some Telepathy CM's to implement the org.freedesktop.Telepathy.Connection.Interface.ContactInfo.DRAFT interface to complete it, since we shouldn't try and support legacy CM's which don't support that interface.

====Source Code====
The code can be found in the KDE svn playground at the following URL:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-contacts-resource
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-contacts-resource websvn link].

===Presence Dataengine and Plasmoid===

====Status====

The dataengine is functional, allowing you to set the Requested Presence and Status Message, and view the Current Presence and Status Message of all Telepathy Accounts.

The applet is not really functional. Andrunko has asked Nuno for some mockups of how to make a nice looking applet.

====Source Code====

Applet in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/applets/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/applets/presence websvn link].

Dataengine in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/dataengines/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/dataengines/presence websvn link].

===Account Management KCM===
====Ideas====
* One single UI that any application can load for add/edit/delete Telepathy Accounts

* Creates a dynamic UI on-the-fly using Connection Manager parameters, but this should be used only when a specific UI plugin for that CM isn't installed.

* Create specialised UI plugins for the popular CM's (e.g. gabble) since dynamic UI will be pretty crap usability-wise.

====Status====

Some code is there in svn, but it's pretty much just experimental shell-files. So feel free to ignore existing code to implement this :) [[User:Grundleborg|Grundleborg]]

====Source Code====

Source code is in KDE svn playground at:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-accounts-kcm/
</pre>

[http://websvn.kde.org/trunk/playground/network/telepathy-accounts-kcm/ websvn link].

===KWallet Account Manager===
This was originally intended to be an implementation of the Telepathy AccountManager which was integrated with KDE and KWallet for the account data storage. However, in light of the shared-secrets API being developed on freedesktop.org which will unify the KWallet and Gnome-Keyring API it would probably be a better use of resources to just get Mission Control ported to that instead.

In light of that, its probably best not to work on telepathy-accountmanager-kwallet or telepathy-qt4-accountmanager at the moment.

==Telepathy Enabled Applications==

==Problems==

* QtDBus doesn't have peer-to-peer DBus implemented properly - the classes are just non-functional stubs. This stops us from implementing D-tubes in KDE/Qt based Telepathy applications. Upstream bug is private in Qt Software's tracker and this is unlikely to get fixed by Qt Software, so if anyone feels like implementing it and then merging it upstream into Qt, that would be really fantastic.

* Telepathy-Mission-Control still requires you to use both the channel dispatcher part of it and the Account Manager. For KDE, we need to be able to use only the Channel Dispatcher from Mission-Control and have that talk over the standard Telepathy DBus interfaces to the KDE KWallet based Account Manager.

==Trying out Telepathy==

=== Prerequisites ===
* telepathy-mission-control 5
* telepathy-qt4
* telepathy-gabble, telepathy-butterfly, telepathy-haze (for jabber/msn/everything else support respectively)

=== KDE Stuff ===
All the KDE Telepathy infrastructure components are detailed above, and they may or may not be in working/compiling order. Any problems, ask in #kde-telepathy.

==How to Get Involved==
Come and talk to us in #kde-telepathy on irc.freenode.net. There is also a #telepathy channel for talking about Telepathy stuff that is not specific to KDE.

==Frequently Asked Questions==

=== What happened to Decibel? ===

Decibel development has completely stagnated and it no longer works with recent Telepathy components. It is not necessary to use Decibel to get Telepathy support in KDE - all the applications/components above do not require Decibel to compile or function.

Projects/Telepathy

2009-07-22T15:20:27Z

Grundleborg: /* KWallet Account Manager */

==Introduction==
[http://telepathy.freedesktop.org The Telepathy framework] is a DBus specification which provides a cross-desktop and cross-protocol abstraction layer for instant messaging, voice/video over IP and collaborative applications. See the [http://telepathy.freedesktop.org Telepathy web site] for more information about Telepathy itself.

This project is focused on integrating Telepathy with KDE. Our high-level aims are the following:
* to provide a unified instant messaging and voice/video communication framework within KDE, which integrates throughout the desktop experience.
* to provide collaborative features in applications which fit seemlessly into the KDE platform
* to provide the infrastructure within KDE necessary to acheive the above two, using cross-desktop specifications and implementations wherever possible.

==Infrastructure==
This section contains details of all the Telepathy-in-KDE infrastructure components, and their statuses.

===Telepathy Integration Daemon===
This is a small light-weight daemon that monitors the Telepathy Account Manager and keeps ensures that all Accounts are recorded in Nepomuk as NCO:Contact instances of "myself" and that they each have a Telepathy Contacts Akonadi Resource instance.

It could possibly be made into a KDED module, but I'm not sure if this is a good idea. [[User:Grundleborg|Grundleborg]]

====Status====
The bare bones are implemented, but the Nepomuk part is blocking on standardising the Ontologies for telepathy specific stuff and how to access the "myself" PIMO:Person through Nepomuk. The Akonadi part is blocking on getting the Telepathy Contacts Akonadi Resource below implemented.

====Source Code====
Source code can be found in KDE svn at:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-integration-daemon
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-integration-daemon websvn link].

===Telepathy Contacts Akonadi Resource===
This is an Akonadi Resource that synchronises the contacts of a Telepathy Account into Akonadi as vcards. The instances of this resource are managed by the telepathy-integration-daemon mentioned above.

====Status====
Partially implemented. Requires some Telepathy CM's to implement the org.freedesktop.Telepathy.Connection.Interface.ContactInfo.DRAFT interface to complete it, since we shouldn't try and support legacy CM's which don't support that interface.

====Source Code====
The code can be found in the KDE svn playground at the following URL:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-contacts-resource
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-contacts-resource websvn link].

===Presence Dataengine and Plasmoid===

====Status====

The dataengine is functional, allowing you to set the Requested Presence and Status Message, and view the Current Presence and Status Message of all Telepathy Accounts.

The applet is not really functional. Andrunko has asked Nuno for some mockups of how to make a nice looking applet.

====Source Code====

Applet in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/applets/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/applets/presence websvn link].

Dataengine in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/dataengines/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/dataengines/presence websvn link].

===Account Management KCM===
====Ideas====
* One single UI that any application can load for add/edit/delete Telepathy Accounts

* Creates a dynamic UI on-the-fly using Connection Manager parameters, but this should be used only when a specific UI plugin for that CM isn't installed.

* Create specialised UI plugins for the popular CM's (e.g. gabble) since dynamic UI will be pretty crap usability-wise.

====Status====

Some code is there in svn, but it's pretty much just experimental shell-files. So feel free to ignore existing code to implement this :) [[User:Grundleborg|Grundleborg]]

====Source Code====

Source code is in KDE svn playground at:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-accounts-kcm/
</pre>

[http://websvn.kde.org/trunk/playground/network/telepathy-accounts-kcm/ websvn link].

===KWallet Account Manager===
This was originally intended to be an implementation of the Telepathy AccountManager which was integrated with KDE and KWallet for the account data storage. However, in light of the shared-secrets API being developed on freedesktop.org which will unify the KWallet and Gnome-Keyring API it would probably be a better use of resources to just get Mission Control ported to that instead.

In light of that, its probably best not to work on telepathy-accountmanager-kwallet or telepathy-qt4-accountmanager at the moment.

==Telepathy Enabled Applications==

==Problems==

* QtDBus doesn't have peer-to-peer DBus implemented properly - the classes are just non-functional stubs. This stops us from implementing D-tubes in KDE/Qt based Telepathy applications. Upstream bug is private in Qt Software's tracker and this is unlikely to get fixed by Qt Software, so if anyone feels like implementing it and then merging it upstream into Qt, that would be really fantastic.

* Telepathy-Mission-Control still requires you to use both the channel dispatcher part of it and the Account Manager. For KDE, we need to be able to use only the Channel Dispatcher from Mission-Control and have that talk over the standard Telepathy DBus interfaces to the KDE KWallet based Account Manager.

==Trying out Telepathy==

=== Prerequisites ===
* telepathy-mission-control 5
* telepathy-qt4
* telepathy-gabble, telepathy-butterfly, telepathy-haze (for jabber/msn/everything else support respectively)

=== KDE Stuff ===
All the KDE Telepathy infrastructure components are detailed above, and they may or may not be in working/compiling order. Any problems, ask in #kde-telepathy.

==How to Get Involved==
Come and talk to us in #kde-telepathy on irc.freenode.net. There is also a #telepathy channel for talking about Telepathy stuff that is not specific to KDE.

==Frequently Asked Questions==

=== What happened to Decibel? ===

Decibel development has completely stagnated and it no longer works with recent Telepathy components. It is not necessary to use Decibel to get Telepathy support in KDE - all the applications/components above do not require Decibel to compile or function.

Projects/Telepathy

2009-07-10T13:40:08Z

Grundleborg: FAQ: What happened to Decibel

==Introduction==
[http://telepathy.freedesktop.org The Telepathy framework] is a DBus specification which provides a cross-desktop and cross-protocol abstraction layer for instant messaging, voice/video over IP and collaborative applications. See the [http://telepathy.freedesktop.org Telepathy web site] for more information about Telepathy itself.

This project is focused on integrating Telepathy with KDE. Our high-level aims are the following:
* to provide a unified instant messaging and voice/video communication framework within KDE, which integrates throughout the desktop experience.
* to provide collaborative features in applications which fit seemlessly into the KDE platform
* to provide the infrastructure within KDE necessary to acheive the above two, using cross-desktop specifications and implementations wherever possible.

==Infrastructure==
This section contains details of all the Telepathy-in-KDE infrastructure components, and their statuses.

===Telepathy Integration Daemon===
This is a small light-weight daemon that monitors the Telepathy Account Manager and keeps ensures that all Accounts are recorded in Nepomuk as NCO:Contact instances of "myself" and that they each have a Telepathy Contacts Akonadi Resource instance.

It could possibly be made into a KDED module, but I'm not sure if this is a good idea. [[User:Grundleborg|Grundleborg]]

====Status====
The bare bones are implemented, but the Nepomuk part is blocking on standardising the Ontologies for telepathy specific stuff and how to access the "myself" PIMO:Person through Nepomuk. The Akonadi part is blocking on getting the Telepathy Contacts Akonadi Resource below implemented.

====Source Code====
Source code can be found in KDE svn at:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-integration-daemon
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-integration-daemon websvn link].

===Telepathy Contacts Akonadi Resource===
This is an Akonadi Resource that synchronises the contacts of a Telepathy Account into Akonadi as vcards. The instances of this resource are managed by the telepathy-integration-daemon mentioned above.

====Status====
Partially implemented. Requires some Telepathy CM's to implement the org.freedesktop.Telepathy.Connection.Interface.ContactInfo.DRAFT interface to complete it, since we shouldn't try and support legacy CM's which don't support that interface.

====Source Code====
The code can be found in the KDE svn playground at the following URL:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-contacts-resource
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-contacts-resource websvn link].

===Presence Dataengine and Plasmoid===

====Status====

The dataengine is functional, allowing you to set the Requested Presence and Status Message, and view the Current Presence and Status Message of all Telepathy Accounts.

The applet is not really functional. Andrunko has asked Nuno for some mockups of how to make a nice looking applet.

====Source Code====

Applet in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/applets/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/applets/presence websvn link].

Dataengine in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/dataengines/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/dataengines/presence websvn link].

===Account Management KCM===
====Ideas====
* One single UI that any application can load for add/edit/delete Telepathy Accounts

* Creates a dynamic UI on-the-fly using Connection Manager parameters, but this should be used only when a specific UI plugin for that CM isn't installed.

* Create specialised UI plugins for the popular CM's (e.g. gabble) since dynamic UI will be pretty crap usability-wise.

====Status====

Some code is there in svn, but it's pretty much just experimental shell-files. So feel free to ignore existing code to implement this :) [[User:Grundleborg|Grundleborg]]

====Source Code====

Source code is in KDE svn playground at:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-accounts-kcm/
</pre>

[http://websvn.kde.org/trunk/playground/network/telepathy-accounts-kcm/ websvn link].

===KWallet Account Manager===

==Telepathy Enabled Applications==

==Problems==

* QtDBus doesn't have peer-to-peer DBus implemented properly - the classes are just non-functional stubs. This stops us from implementing D-tubes in KDE/Qt based Telepathy applications. Upstream bug is private in Qt Software's tracker and this is unlikely to get fixed by Qt Software, so if anyone feels like implementing it and then merging it upstream into Qt, that would be really fantastic.

* Telepathy-Mission-Control still requires you to use both the channel dispatcher part of it and the Account Manager. For KDE, we need to be able to use only the Channel Dispatcher from Mission-Control and have that talk over the standard Telepathy DBus interfaces to the KDE KWallet based Account Manager.

==Trying out Telepathy==

=== Prerequisites ===
* telepathy-mission-control 5
* telepathy-qt4
* telepathy-gabble, telepathy-butterfly, telepathy-haze (for jabber/msn/everything else support respectively)

=== KDE Stuff ===
All the KDE Telepathy infrastructure components are detailed above, and they may or may not be in working/compiling order. Any problems, ask in #kde-telepathy.

==How to Get Involved==
Come and talk to us in #kde-telepathy on irc.freenode.net. There is also a #telepathy channel for talking about Telepathy stuff that is not specific to KDE.

==Frequently Asked Questions==

=== What happened to Decibel? ===

Decibel development has completely stagnated and it no longer works with recent Telepathy components. It is not necessary to use Decibel to get Telepathy support in KDE - all the applications/components above do not require Decibel to compile or function.

Projects/Telepathy

2009-07-10T13:37:28Z

Grundleborg: basic info on what to install/compile to try telepathy

==Introduction==
[http://telepathy.freedesktop.org The Telepathy framework] is a DBus specification which provides a cross-desktop and cross-protocol abstraction layer for instant messaging, voice/video over IP and collaborative applications. See the [http://telepathy.freedesktop.org Telepathy web site] for more information about Telepathy itself.

This project is focused on integrating Telepathy with KDE. Our high-level aims are the following:
* to provide a unified instant messaging and voice/video communication framework within KDE, which integrates throughout the desktop experience.
* to provide collaborative features in applications which fit seemlessly into the KDE platform
* to provide the infrastructure within KDE necessary to acheive the above two, using cross-desktop specifications and implementations wherever possible.

==Infrastructure==
This section contains details of all the Telepathy-in-KDE infrastructure components, and their statuses.

===Telepathy Integration Daemon===
This is a small light-weight daemon that monitors the Telepathy Account Manager and keeps ensures that all Accounts are recorded in Nepomuk as NCO:Contact instances of "myself" and that they each have a Telepathy Contacts Akonadi Resource instance.

It could possibly be made into a KDED module, but I'm not sure if this is a good idea. [[User:Grundleborg|Grundleborg]]

====Status====
The bare bones are implemented, but the Nepomuk part is blocking on standardising the Ontologies for telepathy specific stuff and how to access the "myself" PIMO:Person through Nepomuk. The Akonadi part is blocking on getting the Telepathy Contacts Akonadi Resource below implemented.

====Source Code====
Source code can be found in KDE svn at:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-integration-daemon
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-integration-daemon websvn link].

===Telepathy Contacts Akonadi Resource===
This is an Akonadi Resource that synchronises the contacts of a Telepathy Account into Akonadi as vcards. The instances of this resource are managed by the telepathy-integration-daemon mentioned above.

====Status====
Partially implemented. Requires some Telepathy CM's to implement the org.freedesktop.Telepathy.Connection.Interface.ContactInfo.DRAFT interface to complete it, since we shouldn't try and support legacy CM's which don't support that interface.

====Source Code====
The code can be found in the KDE svn playground at the following URL:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-contacts-resource
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-contacts-resource websvn link].

===Presence Dataengine and Plasmoid===

====Status====

The dataengine is functional, allowing you to set the Requested Presence and Status Message, and view the Current Presence and Status Message of all Telepathy Accounts.

The applet is not really functional. Andrunko has asked Nuno for some mockups of how to make a nice looking applet.

====Source Code====

Applet in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/applets/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/applets/presence websvn link].

Dataengine in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/dataengines/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/dataengines/presence websvn link].

===Account Management KCM===
====Ideas====
* One single UI that any application can load for add/edit/delete Telepathy Accounts

* Creates a dynamic UI on-the-fly using Connection Manager parameters, but this should be used only when a specific UI plugin for that CM isn't installed.

* Create specialised UI plugins for the popular CM's (e.g. gabble) since dynamic UI will be pretty crap usability-wise.

====Status====

Some code is there in svn, but it's pretty much just experimental shell-files. So feel free to ignore existing code to implement this :) [[User:Grundleborg|Grundleborg]]

====Source Code====

Source code is in KDE svn playground at:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-accounts-kcm/
</pre>

[http://websvn.kde.org/trunk/playground/network/telepathy-accounts-kcm/ websvn link].

===KWallet Account Manager===

==Telepathy Enabled Applications==

==Problems==

* QtDBus doesn't have peer-to-peer DBus implemented properly - the classes are just non-functional stubs. This stops us from implementing D-tubes in KDE/Qt based Telepathy applications. Upstream bug is private in Qt Software's tracker and this is unlikely to get fixed by Qt Software, so if anyone feels like implementing it and then merging it upstream into Qt, that would be really fantastic.

* Telepathy-Mission-Control still requires you to use both the channel dispatcher part of it and the Account Manager. For KDE, we need to be able to use only the Channel Dispatcher from Mission-Control and have that talk over the standard Telepathy DBus interfaces to the KDE KWallet based Account Manager.

==Trying out Telepathy==

=== Prerequisites ===
* telepathy-mission-control 5
* telepathy-qt4
* telepathy-gabble, telepathy-butterfly, telepathy-haze (for jabber/msn/everything else support respectively)

=== KDE Stuff ===
All the KDE Telepathy infrastructure components are detailed above, and they may or may not be in working/compiling order. Any problems, ask in #kde-telepathy.

==How to Get Involved==
Come and talk to us in #kde-telepathy on irc.freenode.net. There is also a #telepathy channel for talking about Telepathy stuff that is not specific to KDE.

==Frequently Asked Questions==

Projects/Telepathy

2009-07-10T13:34:30Z

Grundleborg: fix links

==Introduction==
[http://telepathy.freedesktop.org The Telepathy framework] is a DBus specification which provides a cross-desktop and cross-protocol abstraction layer for instant messaging, voice/video over IP and collaborative applications. See the [http://telepathy.freedesktop.org Telepathy web site] for more information about Telepathy itself.

This project is focused on integrating Telepathy with KDE. Our high-level aims are the following:
* to provide a unified instant messaging and voice/video communication framework within KDE, which integrates throughout the desktop experience.
* to provide collaborative features in applications which fit seemlessly into the KDE platform
* to provide the infrastructure within KDE necessary to acheive the above two, using cross-desktop specifications and implementations wherever possible.

==Infrastructure==
This section contains details of all the Telepathy-in-KDE infrastructure components, and their statuses.

===Telepathy Integration Daemon===
This is a small light-weight daemon that monitors the Telepathy Account Manager and keeps ensures that all Accounts are recorded in Nepomuk as NCO:Contact instances of "myself" and that they each have a Telepathy Contacts Akonadi Resource instance.

It could possibly be made into a KDED module, but I'm not sure if this is a good idea. [[User:Grundleborg|Grundleborg]]

====Status====
The bare bones are implemented, but the Nepomuk part is blocking on standardising the Ontologies for telepathy specific stuff and how to access the "myself" PIMO:Person through Nepomuk. The Akonadi part is blocking on getting the Telepathy Contacts Akonadi Resource below implemented.

====Source Code====
Source code can be found in KDE svn at:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-integration-daemon
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-integration-daemon websvn link].

===Telepathy Contacts Akonadi Resource===
This is an Akonadi Resource that synchronises the contacts of a Telepathy Account into Akonadi as vcards. The instances of this resource are managed by the telepathy-integration-daemon mentioned above.

====Status====
Partially implemented. Requires some Telepathy CM's to implement the org.freedesktop.Telepathy.Connection.Interface.ContactInfo.DRAFT interface to complete it, since we shouldn't try and support legacy CM's which don't support that interface.

====Source Code====
The code can be found in the KDE svn playground at the following URL:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-contacts-resource
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-contacts-resource websvn link].

===Presence Dataengine and Plasmoid===

====Status====

The dataengine is functional, allowing you to set the Requested Presence and Status Message, and view the Current Presence and Status Message of all Telepathy Accounts.

The applet is not really functional. Andrunko has asked Nuno for some mockups of how to make a nice looking applet.

====Source Code====

Applet in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/applets/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/applets/presence websvn link].

Dataengine in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/dataengines/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/dataengines/presence websvn link].

===Account Management KCM===
====Ideas====
* One single UI that any application can load for add/edit/delete Telepathy Accounts

* Creates a dynamic UI on-the-fly using Connection Manager parameters, but this should be used only when a specific UI plugin for that CM isn't installed.

* Create specialised UI plugins for the popular CM's (e.g. gabble) since dynamic UI will be pretty crap usability-wise.

====Status====

Some code is there in svn, but it's pretty much just experimental shell-files. So feel free to ignore existing code to implement this :) [[User:Grundleborg|Grundleborg]]

====Source Code====

Source code is in KDE svn playground at:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-accounts-kcm/
</pre>

[http://websvn.kde.org/trunk/playground/network/telepathy-accounts-kcm/ websvn link].

===KWallet Account Manager===

==Telepathy Enabled Applications==

==Problems==

* QtDBus doesn't have peer-to-peer DBus implemented properly - the classes are just non-functional stubs. This stops us from implementing D-tubes in KDE/Qt based Telepathy applications. Upstream bug is private in Qt Software's tracker and this is unlikely to get fixed by Qt Software, so if anyone feels like implementing it and then merging it upstream into Qt, that would be really fantastic.

* Telepathy-Mission-Control still requires you to use both the channel dispatcher part of it and the Account Manager. For KDE, we need to be able to use only the Channel Dispatcher from Mission-Control and have that talk over the standard Telepathy DBus interfaces to the KDE KWallet based Account Manager.

==Trying out Telepathy==

==How to Get Involved==
Come and talk to us in #kde-telepathy on irc.freenode.net. There is also a #telepathy channel for talking about Telepathy stuff that is not specific to KDE.

==Frequently Asked Questions==

Projects/Telepathy

2009-07-10T13:29:56Z

Grundleborg: add plasma applet/engine details

==Introduction==
[http://telepathy.freedesktop.org The Telepathy framework] is a DBus specification which provides a cross-desktop and cross-protocol abstraction layer for instant messaging, voice/video over IP and collaborative applications. See the [http://telepathy.freedesktop.org Telepathy web site] for more information about Telepathy itself.

This project is focused on integrating Telepathy with KDE. Our high-level aims are the following:
* to provide a unified instant messaging and voice/video communication framework within KDE, which integrates throughout the desktop experience.
* to provide collaborative features in applications which fit seemlessly into the KDE platform
* to provide the infrastructure within KDE necessary to acheive the above two, using cross-desktop specifications and implementations wherever possible.

==Infrastructure==
This section contains details of all the Telepathy-in-KDE infrastructure components, and their statuses.

===Telepathy Integration Daemon===
This is a small light-weight daemon that monitors the Telepathy Account Manager and keeps ensures that all Accounts are recorded in Nepomuk as NCO:Contact instances of "myself" and that they each have a Telepathy Contacts Akonadi Resource instance.

It could possibly be made into a KDED module, but I'm not sure if this is a good idea. [[User:Grundleborg|Grundleborg]]

====Status====
The bare bones are implemented, but the Nepomuk part is blocking on standardising the Ontologies for telepathy specific stuff and how to access the "myself" PIMO:Person through Nepomuk. The Akonadi part is blocking on getting the Telepathy Contacts Akonadi Resource below implemented.

====Source Code====
Source code can be found in KDE svn at:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-integration-daemon
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-integration-daemon websvn link].

===Telepathy Contacts Akonadi Resource===
This is an Akonadi Resource that synchronises the contacts of a Telepathy Account into Akonadi as vcards. The instances of this resource are managed by the telepathy-integration-daemon mentioned above.

====Status====
Partially implemented. Requires some Telepathy CM's to implement the org.freedesktop.Telepathy.Connection.Interface.ContactInfo.DRAFT interface to complete it, since we shouldn't try and support legacy CM's which don't support that interface.

====Source Code====
The code can be found in the KDE svn playground at the following URL:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-contacts-resource
</pre>
[http://websvn.kde.org/trunk/playground/network/telepathy-contacts-resource websvn link].

===Presence Dataengine and Plasmoid===

====Status====

The dataengine is functional, allowing you to set the Requested Presence and Status Message, and view the Current Presence and Status Message of all Telepathy Accounts.

The applet is not really functional. Andrunko has asked Nuno for some mockups of how to make a nice looking applet.

====Source Code====

Applet in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/applets/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/applets/presence webvn link].

Dataengine in KDE svn:
<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/base/plasma/engines/presence
</pre>

[http://websvn.kde.org/trunk/playground/base/plasma/engines/presence webvn link].

===Account Management KCM===
====Ideas====
* One single UI that any application can load for add/edit/delete Telepathy Accounts

* Creates a dynamic UI on-the-fly using Connection Manager parameters, but this should be used only when a specific UI plugin for that CM isn't installed.

* Create specialised UI plugins for the popular CM's (e.g. gabble) since dynamic UI will be pretty crap usability-wise.

====Status====

Some code is there in svn, but it's pretty much just experimental shell-files. So feel free to ignore existing code to implement this :) [[User:Grundleborg|Grundleborg]]

====Source Code====

Source code is in KDE svn playground at:

<pre>
svn://anonsvn.kde.org/home/kde/trunk/playground/network/telepathy-accounts-kcm/
</pre>

[http://websvn.kde.org/trunk/playground/network/telepathy-accounts-kcm/ websvn link].

===KWallet Account Manager===

==Telepathy Enabled Applications==

==Problems==

* QtDBus doesn't have peer-to-peer DBus implemented properly - the classes are just non-functional stubs. This stops us from implementing D-tubes in KDE/Qt based Telepathy applications. Upstream bug is private in Qt Software's tracker and this is unlikely to get fixed by Qt Software, so if anyone feels like implementing it and then merging it upstream into Qt, that would be really fantastic.

* Telepathy-Mission-Control still requires you to use both the channel dispatcher part of it and the Account Manager. For KDE, we need to be able to use only the Channel Dispatcher from Mission-Control and have that talk over the standard Telepathy DBus interfaces to the KDE KWallet based Account Manager.

==Trying out Telepathy==

==How to Get Involved==
Come and talk to us in #kde-telepathy on irc.freenode.net. There is also a #telepathy channel for talking about Telepathy stuff that is not specific to KDE.

==Frequently Asked Questions==

Projects/Telepathy

2009-07-10T12:29:26Z

Grundleborg: add IRC channels

Projects/Telepathy

2009-07-10T12:27:12Z

Grundleborg: mission control separate am/cd

Projects/Telepathy

2009-07-10T12:13:56Z

Grundleborg: remove stray equals sign

Projects/Telepathy

2009-07-09T18:57:56Z

Grundleborg: write up about accounts kcm

Projects/Telepathy

2009-07-09T17:52:20Z

Grundleborg: qt dbus peer to peer fail

Projects/Telepathy

2009-07-09T17:30:33Z

Grundleborg: add some extra headings to the page skeleton

Projects/Telepathy

2009-07-09T17:27:19Z

Grundleborg: minor correction

Projects/Telepathy

2009-07-09T17:25:36Z

Grundleborg: consistency++

Projects/Telepathy

2009-07-09T17:24:57Z

Grundleborg: akonadi contacts resource writeup

Projects/Telepathy

2009-07-09T16:58:13Z

Grundleborg: write up telepathy-integration-daemon section

Projects/Telepathy

2009-07-09T16:45:14Z

Grundleborg: headings for rest of page structure

Projects/Telepathy

2009-07-09T16:42:26Z

Grundleborg: shell section on telepathy infrastructure

Projects/Telepathy

2009-07-09T16:28:03Z

Grundleborg: modify title

Projects/Telepathy

2009-07-09T16:27:16Z

Grundleborg: intro and aims

==Telepathy KDE Integration Project Page==
[http://telepathy.freedesktop.org The Telepathy framework] is a DBus specification which provides a cross-desktop and cross-protocol abstraction layer for instant messaging, voice/video over IP and collaborative applications. See the [http://telepathy.freedesktop.org Telepathy web site] for more information about Telepathy itself.

This project is focused on integrating Telepathy with KDE. Our high-level aims are the following:
* to provide a unified instant messaging and voice/video communication framework within KDE, which integrates throughout the desktop experience.
* to provide collaborative features in applications which fit seemlessly into the KDE platform
* to provide the infrastructure within KDE necessary to acheive the above two, using cross-desktop specifications and implementations wherever possible.

Projects

2009-07-09T16:08:51Z

Grundleborg:

{{Template:I18n/Language Navigation Bar|Projects}}
{{note|KDE TechBase Translators: The Projects part is rather a scratchpad for arbitrary projects. It contains texts like IRC logs and rough ideas. '''It probably does not make sense to translate this'''.}}
{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|[[Image:Klogo-official-crystal.svg|noframe|left|40px]] ||
;[http://www.kde.org/getinvolved Get Involved with KDE]
:General information for getting involved with KDE projects. Includes a mentor directory for many projects.
|-
|[[Image:Klogo-official-crystal.svg|noframe|left|40px]] ||
;[[/Release_Team|KDE Release Team]]
:The KDE Release Team.
|-
|[[Image:Klogo-official-crystal.svg|noframe|left|40px]] ||
;[[/kdelibs|KDE Core Libraries]]
:For the core developers working on the kdelibs module.
|-
|[[Image:Klogo-official-crystal.svg|noframe|left|40px]] ||
;[[/Documentation|KDE Documentation Project]]
:Creating and maintaining KDE documentation.
|-
|[[Image:Action_book2.svg|noframe|left|40px]] ||
;[[/Edu|KDE Education Project]]
:Developing educational software for KDE.
|-
|[[Image:Kdegameslogo_40.png|noframe|left|40px]] ||
;[[/Games|KDE Games Project]]
:Developing desktop's games for KDE.
|-
|[[Image:Action_mail_generic.svg|noframe|left|40px]] ||
;[[/PIM|KDE PIM Project]]
:KDE Personal Information Management.
|-
|[[Image:Klogo-official-crystal.svg|noframe|left|40px]] ||
;[[/kde.org|kde.org]]
:Information around the *.kde.org websites.
|-
|[[Image:Action_filequickprint.svg|noframe|left|40px]] ||
;[[/KDEPrint|KDEPrint]]
:Printing related information for KDE.
|-
|[[Image:Action_pencil.svg|noframe|left|40px]] ||
;[http://wiki.koffice.org KOffice.org]
:Developing an Office suite based on KDE.
|-
|[[Image:logo_oxygen.png|noframe|left|40px]] ||
;[[/Oxygen|The Oxygen Project]]
:Artwork for KDE4.
|-
|[[Image:Klogo-official-crystal.svg|noframe|left|40px]] ||
;[[/Promo|KDE Promotion]]
:Promoting KDE and conference organization.
|-
|[[Image:Action_world.svg|noframe|left|40px]] ||
;[[/Partners|Partner Program]]
:KDE partner program targetting ISVs.
|-
|[[Image:Plasma_logo.jpg|noframe|left|40px]] ||
;[[/Plasma|Plasma]]
:Plasma project. A new way to desktop. (Yes, it's now a verb)
|-
|[[Image:Marble.png|noframe|left|40px]] ||
;[[/Marble|Marble]]
:Marble Desktop Globe - Can You Feel The Earth Spinning?
|-
|[[Image:Decibel.png|noframe|left|40px]] ||
;[[/Decibel|Decibel]]
:Decibel - Realtime communications framework
|-
| ||
;[[Contribute/Bugsquad|KDE BugSquad]]
:The KDE BugSquad keeps track of incoming bugs in KDE software, and goes through old bugs.
|-
| ||
;[[/Summer_of_Code|Summer of Code Projects]]
:Information on Summer of Code projects and prospects related to KDE
|-
|[[Image:Kopete.svg|noframe|left|40px]] ||
;[[/Kopete|Kopete]]
:Kopete, the KDE Instant Messaging program.
|-
|[[Image:superkaramba.png|noframe|left|40px]] ||
;[[/SuperKaramba|SuperKaramba]]
:SuperKaramba is a tool that allows you to easily create interactive eye-candy on your KDE desktop.
|-
| ||
;[[/Okular|Okular]]
:Okular, the unified document viewer.
|-
| ||
;[[/Gwenview|Gwenview]]
:Gwenview, the image viewer.
|-
| ||
;[[/Widgets and Classes|Widgets & Classes]]
:Widgets and classes that are not in kdelibs but which you may find useful.
|-
| ||
;[[/English Breakfast Network|KDE Code Quality (EBN)]]
: The English Breakfast Network and associated tools dedicated to KDE Quality, including: KDE API Documentation Validation, User Documentation Validation, Source Code Checking, ...
|-
| ||
;[[/KDE Research|KDE Research]]
: Project and community for everyone who is interested in contributing to (funded) research projects with(in) the KDE community.
|-
|[[Image:KDE-Mac.png|noframe|left|40px]] ||
;[[/KDE on Mac OS X|KDE on Mac OS X]]
: KDE libraries and applications on Mac OS X.
|-
|[[Image:Konqi-win.png|38px]] ||
;[[/KDE on Windows|KDE on Windows]]
: KDE libraries and applications on MS Windows.
|-
| ||
;[[/KDE on Solaris|KDE on Solaris]]
: KDE libraries and applications on Sun Microsystems Solaris and OpenSolaris.
|-
| ||
;[[/KDE on FreeBSD|KDE on FreeBSD]]
: KDE libraries and applications on FreeBSD and other BSDs.
|-
| ||
;[[/kdesu|kdesu]]
: Considerations and coordination to make kdesu work well with several backends.
|-
| ||
;[[/KioFuse|KioFuse]]
: Insert KIO resources (remote, archived or compressed files) into the root filesystem hierarchy.
|-
| ||
;[[/SystemSettings|System Settings]]
: Development on the System Settings configuration tool.
|-
| ||
;[[/KWin|KWin]]
: The KDE Window Manager.
|-
|[[Image:kdeutils-logo.svg|noframe|left|40px]] ||
;[[/Utils|KDE Utilities Team]]
:For the developers working on the kdeutils module.
|-
| ||
;[[/extragearReleases|Extragear Releases]]
: A current list of what extragear apps are to be released in sync with the core KDE release schedule.
|-
| ||
;[[/Related|Related Projects]]
: Projects which are related to KDE in any way, as dependencies or build tools.
|-
|[[Image:knetworkmanager.png|noframe|left|40px]] ||
;[[/Network_Management|Network Management]]
: Development on Solid Networking, KNetworkManager applet and configuration tool.
|-
| ||
;[[/D-Bus-WS|D-Bus Web Service Proxy]]
: Fusion of D-Bus services and web services.
|-
| [[Image:Hisc-apps-kget.svg|noframe|left|40px]]||
;[[/KGet|KGet]]
: KGet, a KDE Downloader
|-
| ||
;[[/WebKit|WebKit (webkitkde)]]
: Project which aims to integrate WebKit (QtWebKit) into KDE.
|-
| ||
;[[/Maemo|Maemo]]
: Project for porting KDE to the Maemo platform.
|-
| ||
;[[/Kdetoys | Kdetoys]]
: The Kdetoys project
|-
| ||
;[[/KGLEngine2D | KGLEngine2D]]
: KGLEngine2D is a framework designed to greatly simplify the development of reach multimedia applications on KDE enabled platforms.
|-
| ||
;[[/Usability | KDE Usability project]]
: The KDE Usability Project is an initiative to apply usability principles and practices to the K Desktop Environment.
|-
|[[Image:Nepomuk_logo.png|noframe|left|40px]] ||
;[[/Nepomuk|Nepomuk]]
:Nepomuk Semantic Desktop project - Annotation/Indexing/Search/Linking
|-
| ||
;[[/KdeFinance | KDE Finance]]
: KDE Finance is a group of KDE-related financial applications
|-
|[[Image:telepathy-logo-rect.png|noframe|left|40px]] ||
;[[/Telepathy|Telepathy]]
:Telepathy Realtime Communication Framework - Instant Messaging, VoIP and Collaboration.
|-
|}

__NOTOC__

Contribute/Bugsquad/BugDays/PlasmaDay1

2009-04-25T13:18:59Z

Grundleborg: /* Sign-in */

==Introduction==

If this is the first time you're taking part in a bug triage, don't be scared by the amount of explanatory text on this page. We hope it's easily understandable - if it isn't bug us on IRC :-)

This is the page for PlasmaDay1 which takes place on Saturday/Sunday, April 25th/26th 2009, but feel free to start early. The aim of this bug day is to organize as many of the Plasma bugs as possible, identifying duplicate bug reports and already fixed bugs. Our targets for triage are bugs listed in [http://bugs.kde.org bugs.kde.org] under the product plasma.

==Requirements==
You don't need any programming experience to help out with Triaging, but you will need a very recent version of KDE compiled from svn. Information on setting up KDE from trunk can be [http://techbase.kde.org/Getting_Started found here]. If you're having trouble installing KDE, feel free to drop by on #kde-bugs early to get some help.

==General information==
* [http://techbase.kde.org/Contribute/Bugsquad This page] has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". Generally we don't want to claim things are duplicates when they aren't. Make sure you get '''approval from a developer''' before you mark something a duplicate. We don't want to create more work for the developers!
* Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)

==Preparations==
First of all, put your name and the version of KDE you are testing with into the Sign-in section. Then read the descriptions of the various sections to file bugs in carefully.

==Workflow==
# Select one of the batches of bugs you'd like to do and pick it by putting your name into the appropriate column.
# Execute the query to get the list of bugs and go through the bugs one by one.
## Read the bug description and the comments carefully and try to reproduce the bug.
## Post a comment on bugzilla explaining what you found out. Be sure to also put the version of KDE you are testing with in the comment.
## Put the bug into the appropriate section and describe your findings here as well (eg. "Can't reproduce any longer" or "This bug is still reproducible for me"). If there's something special about a bug, you can prepend a little label like eg. '''crash'''. Please mark every bug with your IRC nickname. You can easily do that by appending <nowiki>~~~</nowiki>.
## Check if the bug's Version field is set properly. The version field for Plasma bugs should always contain the last KDE version the bug is/was reproducible with. If the bug is no longer reproducible and it's unclear which version the bug last appeared in, please set it to the version you '''think''' it last happened.
## Check if the bug's component is set correctly. It will be of great help when checking for duplicates (eg. comparing similar bugreports in the "panel" component). If you lack permissions to change the component or are unsure about it, please put the bugs in the "needs component change" section along with a comment.
## Mark the bug as triaged by adding the '''triaged''' keyword on the bug. Again if you lack the permissions to do so, additionally put it in the "Needs triaged keyword" section.
# If you're done with your batch, pick another one and start from the top :-)

===Testcases===
Some bugs might have documents that expose the bugs attached, for some bugs you might be able to create data that shows the buggy behaviour. In both cases we have to add the '''testcase''' keyword. If you lack permissions to do so, additionally add the bug to the "Needs testcase keyword" section.

===Unclear===
If something has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. We're especially interested in problems that result in an unuseable desktop. Let's keep track of them.

===Double Check!===
'''Please list bugs here to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.'''

{{Warning|Many Plasma bugreports might be specific to a certain graphics card or the version of Qt/X.org you are using. This means that just because you can't reproduce a bug it might still be there.}}

===Keep this page updated!===
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can use the tag <s>...</s> to mark a bug as done <s>like this</s>.

==Hints==
* You can edit single sections of this page if you you check '''Enable section editing via edit links''' in your [[Special:Preferences|TechBase Preferences]].
* Sometimes you might encounter '''edit conflicts''' if several people are working on the wiki page at once. We can mostly avoid those by keeping notes of the bugs we encounter in a text editor and file several of them later at once (don't forget to save).

{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==Common Bugs==
There are some bugs which are commonly reported several times. If you found such a bug (or think you did), you can put it here:

==Sign-in==
Tell developers what you are testing with. (If you expect to upgrade between now and BugDay, put what version you are using now next to the bugs/comments that you put on this page.)

Please give distro/version or SVN branch/trunk with revision below (or just beta2 if you're using that). Also put your graphics driver, the version of Qt and X you are using:

{|
|-
!IRC Nickname !! KDE version used for testing !! Graphics driver !! Qt !! X
|-
|[[User:Lemma|Lemma]]||svn trunk r958924||NVIDIA 185.19||qt-copy||1.6.1
|-
|[[User:jtamate|jtamate]]||opensuse r954171||free ati radeon||4.5.1||1.6
|-
|[[User:DarioAndres|Dario_Andres]]||trunk 958964||intel2.6.3||4.5.0+942255||1.6.1
|-
|[[User:Anselmolsm|anselmolsm]]||trunk 958853||NVidia 180.51||4.5.0+942255||1.5.3-r5
|-
|[[User:Grundleborg|grundleborg]]||trunk 959002||fglrx||4.5.0+955572||1.5.2
|}

==Division of Labour==
Please choose a batch that is not already taken and then query bugs.kde.org for all bugs in that batch. Please mark you irc nickname in the table below to show which month's bugs you are working on to avoid duplication of effort.

If you have to leave before you can finish your batch, please put the last bug you triaged as well as if you're going to finish triaging in the table so others will know where you left off.

{{Warning| With these more recent bugs, if the report has been looked at by a developer (i.e. they cc'd themself or commented on it or posted a patch), and it seems like the issue is fixed, BUT the developer didn't close it, make sure the bug really can be closed. Often it can't.}}

===The batches===
Information mostly for people organizing:
* The template query for the batches is [ this one].
* If you want to choose a batch but none are left, bug [[User:Lemma|Lemma]] on IRC.

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=153580&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=162624 Query]
|-
| 2 || 7 || [[User:jtamate|jtamate]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=164241&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=167244 Query]
|-
| 3 || 7 || [[User:jtamate|jtamate]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=167700&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=170438 Query]
|-
| 4 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=170449&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=172174 Query]
|-
| 5 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=172474&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=175088 Query]
|-
| 6 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=175160&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=175955 Query]
|-
| 7 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=175985&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=176754 Query]
|-
| 8 || 7 || [[User:Lemma|Lemma]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=176847&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=177675 Query]
|-
| 9 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=177707&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=178033 Query]
|-
| 10 || 7 || [[User:DarioAndres|Dario_Andres]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=178131&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=178488 Query]
|-
| 11 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=178514&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=178977 Query]
|-
| 12 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=179155&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=179443 Query]
|-
| 13 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=179448&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=179647 Query]
|-
| 14 || 7 || [[User:Grundleborg|grundleborg]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=179661&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=180058 Query]
|-
| 15 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=180073&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=180602 Query]
|-
| 16 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=180624&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=180811 Query]
|-
| 17 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=180812&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=180910 Query]
|-
| 18 || 7 || [[User:Anselmolsm|anselmolsm]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=180927&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=181016 Query]
|-
| 19 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=181020&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=181165 Query]
|-
| 20 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=181174&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=181270 Query]
|}

== Bugs that need changes that require permissions ==
If you put a bug into this section, please be sure you additionally put it into the appropriate '''Completed Bugs''' section.

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs to be marked as TRIAGED}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs to be marked as TESTCASE}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs needing version field changed}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs needing component field changed}}

== Special interest bugs ==

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/High Profile}}

== Completed Bugs ==
Below lists the various sections for completed bugs. This aids everyone in double checking each other's work. In addition this allows those of us that don't have bugzilla permissions to list bugs so that the folks with the permissions can follow up.

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs to be marked as RESOLVED}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs with test-cases}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs with step-by-step instructions}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs to be marked as INVALID}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs to be marked as DUPLICATE}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs that should be WISHES}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs needing users with particular setups}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Non english locales}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs needing attention from Plasma developers}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs awaiting feedback}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs that you cant do}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs not related to Plasma}}

Contribute/Bugsquad/BugDays/PlasmaDay1

2009-04-25T13:18:28Z

Grundleborg: /* Sign-in */

==Introduction==

If this is the first time you're taking part in a bug triage, don't be scared by the amount of explanatory text on this page. We hope it's easily understandable - if it isn't bug us on IRC :-)

This is the page for PlasmaDay1 which takes place on Saturday/Sunday, April 25th/26th 2009, but feel free to start early. The aim of this bug day is to organize as many of the Plasma bugs as possible, identifying duplicate bug reports and already fixed bugs. Our targets for triage are bugs listed in [http://bugs.kde.org bugs.kde.org] under the product plasma.

==Requirements==
You don't need any programming experience to help out with Triaging, but you will need a very recent version of KDE compiled from svn. Information on setting up KDE from trunk can be [http://techbase.kde.org/Getting_Started found here]. If you're having trouble installing KDE, feel free to drop by on #kde-bugs early to get some help.

==General information==
* [http://techbase.kde.org/Contribute/Bugsquad This page] has useful information on how to not mis-mark bugs. In particular, "duplicates are hard". Generally we don't want to claim things are duplicates when they aren't. Make sure you get '''approval from a developer''' before you mark something a duplicate. We don't want to create more work for the developers!
* Be sure to join #kde-bugs on irc.freenode.net, as this is where the bug-day will be coordinated. (You can even join now!)

==Preparations==
First of all, put your name and the version of KDE you are testing with into the Sign-in section. Then read the descriptions of the various sections to file bugs in carefully.

==Workflow==
# Select one of the batches of bugs you'd like to do and pick it by putting your name into the appropriate column.
# Execute the query to get the list of bugs and go through the bugs one by one.
## Read the bug description and the comments carefully and try to reproduce the bug.
## Post a comment on bugzilla explaining what you found out. Be sure to also put the version of KDE you are testing with in the comment.
## Put the bug into the appropriate section and describe your findings here as well (eg. "Can't reproduce any longer" or "This bug is still reproducible for me"). If there's something special about a bug, you can prepend a little label like eg. '''crash'''. Please mark every bug with your IRC nickname. You can easily do that by appending <nowiki>~~~</nowiki>.
## Check if the bug's Version field is set properly. The version field for Plasma bugs should always contain the last KDE version the bug is/was reproducible with. If the bug is no longer reproducible and it's unclear which version the bug last appeared in, please set it to the version you '''think''' it last happened.
## Check if the bug's component is set correctly. It will be of great help when checking for duplicates (eg. comparing similar bugreports in the "panel" component). If you lack permissions to change the component or are unsure about it, please put the bugs in the "needs component change" section along with a comment.
## Mark the bug as triaged by adding the '''triaged''' keyword on the bug. Again if you lack the permissions to do so, additionally put it in the "Needs triaged keyword" section.
# If you're done with your batch, pick another one and start from the top :-)

===Testcases===
Some bugs might have documents that expose the bugs attached, for some bugs you might be able to create data that shows the buggy behaviour. In both cases we have to add the '''testcase''' keyword. If you lack permissions to do so, additionally add the bug to the "Needs testcase keyword" section.

===Unclear===
If something has no clear instructions on how to reproduce it, or has little useful information, add a comment asking the reporter for more detail. Then list it in the [[#Bugs_awaiting_feedback|bugs awaiting feedback]] section. Be polite, we want to be nice to our bug reporters!

===Is it a big bug?===
Prioritizing is good. We're especially interested in problems that result in an unuseable desktop. Let's keep track of them.

===Double Check!===
'''Please list bugs here to get a second opinion before making the change in bugzilla. This also gives a record of what we've done for the developers to check.'''

{{Warning|Many Plasma bugreports might be specific to a certain graphics card or the version of Qt/X.org you are using. This means that just because you can't reproduce a bug it might still be there.}}

===Keep this page updated!===
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.

You can use the tag <s>...</s> to mark a bug as done <s>like this</s>.

==Hints==
* You can edit single sections of this page if you you check '''Enable section editing via edit links''' in your [[Special:Preferences|TechBase Preferences]].
* Sometimes you might encounter '''edit conflicts''' if several people are working on the wiki page at once. We can mostly avoid those by keeping notes of the bugs we encounter in a text editor and file several of them later at once (don't forget to save).

{{Tip|Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup <nowiki>~~~</nowiki> to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).}}

==Common Bugs==
There are some bugs which are commonly reported several times. If you found such a bug (or think you did), you can put it here:

==Sign-in==
Tell developers what you are testing with. (If you expect to upgrade between now and BugDay, put what version you are using now next to the bugs/comments that you put on this page.)

Please give distro/version or SVN branch/trunk with revision below (or just beta2 if you're using that). Also put your graphics driver, the version of Qt and X you are using:

{|
|-
!IRC Nickname !! KDE version used for testing !! Graphics driver !! Qt !! X
|-
|[[User:Lemma|Lemma]]||svn trunk r958924||NVIDIA 185.19||qt-copy||1.6.1
|-
|[[User:jtamate|jtamate]]||opensuse r954171||free ati radeon||4.5.1||1.6
|-
|[[User:DarioAndres|Dario_Andres]]||trunk 958964||intel2.6.3||4.5.0+942255||1.6.1
|-
|[[User:Anselmolsm|anselmolsm]]||trunk 958853||NVidia 180.51||4.5.0+942255||1.5.3-r5
|-
|[[User:Grundleborg|grundleborg]]|trunk 959002||fglrx||4.5.0+955572||1.5.2
|}

==Division of Labour==
Please choose a batch that is not already taken and then query bugs.kde.org for all bugs in that batch. Please mark you irc nickname in the table below to show which month's bugs you are working on to avoid duplication of effort.

If you have to leave before you can finish your batch, please put the last bug you triaged as well as if you're going to finish triaging in the table so others will know where you left off.

{{Warning| With these more recent bugs, if the report has been looked at by a developer (i.e. they cc'd themself or commented on it or posted a patch), and it seems like the issue is fixed, BUT the developer didn't close it, make sure the bug really can be closed. Often it can't.}}

===The batches===
Information mostly for people organizing:
* The template query for the batches is [ this one].
* If you want to choose a batch but none are left, bug [[User:Lemma|Lemma]] on IRC.

{|
|-
!Batch !! No of bugs !! IRC Nickname !! Status !! Query
|-
| 1 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=153580&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=162624 Query]
|-
| 2 || 7 || [[User:jtamate|jtamate]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=164241&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=167244 Query]
|-
| 3 || 7 || [[User:jtamate|jtamate]] || done || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=167700&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=170438 Query]
|-
| 4 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=170449&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=172174 Query]
|-
| 5 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=172474&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=175088 Query]
|-
| 6 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=175160&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=175955 Query]
|-
| 7 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=175985&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=176754 Query]
|-
| 8 || 7 || [[User:Lemma|Lemma]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=176847&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=177675 Query]
|-
| 9 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=177707&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=178033 Query]
|-
| 10 || 7 || [[User:DarioAndres|Dario_Andres]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=178131&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=178488 Query]
|-
| 11 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=178514&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=178977 Query]
|-
| 12 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=179155&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=179443 Query]
|-
| 13 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=179448&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=179647 Query]
|-
| 14 || 7 || [[User:Grundleborg|grundleborg]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=179661&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=180058 Query]
|-
| 15 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=180073&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=180602 Query]
|-
| 16 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=180624&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=180811 Query]
|-
| 17 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=180812&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=180910 Query]
|-
| 18 || 7 || [[User:Anselmolsm|anselmolsm]] || working || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=180927&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=181016 Query]
|-
| 19 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=181020&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=181165 Query]
|-
| 20 || 7 || || || [https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=plasma&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=nowords&keywords=triaged&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&bug_severity=minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=bug_id&type0-0-0=greaterthan&value0-0-0=181174&field0-1-0=bug_id&type0-1-0=lessthan&value0-1-0=181270 Query]
|}

== Bugs that need changes that require permissions ==
If you put a bug into this section, please be sure you additionally put it into the appropriate '''Completed Bugs''' section.

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs to be marked as TRIAGED}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs to be marked as TESTCASE}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs needing version field changed}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs needing component field changed}}

== Special interest bugs ==

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/High Profile}}

== Completed Bugs ==
Below lists the various sections for completed bugs. This aids everyone in double checking each other's work. In addition this allows those of us that don't have bugzilla permissions to list bugs so that the folks with the permissions can follow up.

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs to be marked as RESOLVED}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs with test-cases}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs with step-by-step instructions}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs to be marked as INVALID}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs to be marked as DUPLICATE}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs that should be WISHES}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs needing users with particular setups}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Non english locales}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs needing attention from Plasma developers}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs awaiting feedback}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs that you cant do}}

{{:Contribute/Bugsquad/BugDays/PlasmaDay1/Bugs not related to Plasma}}

Schedules/KDE4/4.3 Feature Plan

2009-04-01T17:01:56Z

Grundleborg: /* kdenetwork */

This is a list of planned features for the 4.3 release.

See also:
* [[Schedules/KDE4/4.3 Release Schedule]]
* [[Schedules/KDE4/4.3 Release Goals]]
* [[Schedules/KDE4/4.2 Feature Plan]]

Legend:
* todo => not started yet
* in-progress => started, but not completed yet
* done => completed
__TOC__

= Other =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|Akonadi|Various Akonadi related items can be found here http://techbase.kde.org/Projects/PIM/Akonadi#Scheduled_for_KDE_4.3_.2F_Akonadi_1.2|kde-pim@kde.org|Akonadi Developers}}
{{FeatureInProgress|KPackageKit|Pushing in KPackageKit (dependant on PolicyKit integration)|dantti85-dev@yahoo.com.br|Daniel}}
|}

= kdelibs =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|KLocale|Investigate adding Currency Code and currency minor units support based on ISO 4217 (http://en.wikipedia.org/wiki/ISO_4217).|john@layt.net|John Layt}}
{{FeatureInProgress|kdecore|Thread safety in ksycoca (KService, KMimeType etc.)|faure:AT:kde.org|David Faure}}
{{FeatureInProgress|Sonnet|Implement language detection|qbast@go2.pl|Jakub Stachowski}}
{{FeatureInProgress|Sonnet|Integrate language detection with spellchecking|qbast@go2.pl|Jakub Stachowski}}
{{FeatureTodo|Sonnet|Integrate language detection with strigi|qbast@go2.pl|Jakub Stachowski}}
{{FeatureTodo|Sonnet|Grammar checking (at least for English)|qbast@go2.pl|Jakub Stachowski}}
{{FeatureInProgress|kio|Move KTcpSocket to kio and make it public; some cleanup required|ahartmetz@gmail.com|Andreas Hartmetz}}
{{FeatureTodo|KCalendarSystem|Add new astronomical calculation support classes to be used in kdelibs to build new astronomically based calendar systems, and in kdepim to build new version of libkholiday.|john@layt.net|John Layt}}
{{FeatureTodo|KCalendarSystem|Add new calendar systems: Indian Civil (Saka), Ethiopean, Chinese, Pure Julian, Pure Gregorian, etc.|john@layt.net|John Layt}}
{{FeatureTodo|KDEPrint|If no file printing support in Qt4.5, migrate FilePrinter class from Okular to enable file printing for all apps via QPrinter. To be discussed on k-c-d first.|john@layt.net|John Layt}}
{{FeatureTodo|KDEPrint|Add framework for standard actions for 'Send to...' for e-mail, fax, etc by printing to PDF/PS.|john@layt.net|John Layt}}
{{FeatureTodo|kdeui|entries to help menu and aboutdata pointing to UserBase entry and forum.kde.org|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|kdesu|Classes to help kde-apps open ports in the local firewall (via IPTables/IPFW, etc...)|tejas@gja.in|Tejas Dinkar}}
|}

= kdebase-workspace =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact

|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |Non-Plasma, Non-KWin
{{FeatureTodo|Kxkb|Support for languages in keyboard layout descriptions|rysin:AT:kde.org|Andriy Rysin}}
{{FeatureDone|PolicyKit integration|Import PolicyKit-KDE from extragear|drf54321@gmail.com|Dario Freddi}}
{{FeatureDone|Solid Actions KCM|Import Solid actions KControl module from playground|ben@eclipse.endoftheinternet.org|Ben Cooksley}}
{{FeatureTodo|KControl4|Import refactor of systemsettings with Tree and Icon view support|ben(at)eclipse(dot)endoftheinternet(dot)org+msoeken(at)informatik(dot)uni-bremen(dot)de|Ben Cooksley and Mathias Soeken}}
{{FeatureDone|KSysguard|Added GetHotNewStuff support|a@b.com|name}}
{{FeatureInProgress|KActiveEdges|Split active screen edges from KWin|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureInProgress|Solid Wicd Engine|Import Solid Wicd engine from github/playground|drf54321@gmail.com|Dario Freddi}}
{{FeatureDone|Klipper|Made klipper automatically find possible actions based on filename copied to clipboard|dimsuz@gmail.com|Dmitry Suzdalev}}
{{FeatureDone|Klipper|Improved action adding/editing workflow by implementing a special dialog for editing a certain action|dimsuz@gmail.com|Dmitry Suzdalev}}

|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |KRunner

|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |Plasma - Priority Features

|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |Plasma
{{FeatureTodo|Now Playing data engine|Support for MPD|kde:AT:randomguy3.me.uk|Alex Merry}}
{{FeatureDone|Classic Menu Launcher|Optional recently used applications and System Settings menu|mail:AT:dipe.org|Sebastian Sauer}}
{{FeatureInProgress|Reusable video widget|A widget in libplasma that can play video and audio|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Message box|A message box shown as an overlay over plasmoids|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Systemtray protocol|New systemtray protocol beginnings: daemon and systemtray widget part|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Default theme|Air: new default Plasma theme|notmart@gmail.com|Marco Martin and Nuno Pinheiro}}
{{FeatureInProgress|screensaver|security constraints|chanika@gmail.com|Chani}}
{{FeatureInProgress|keyboard shortcuts|configuration|chanika@gmail.com|Chani}}
{{FeatureTodo|icon plasmoid|make it suck less|chanika@gmail.com|Chani}}
{{FeatureTodo|desktop|make a plasmoid when I paste stuff|chanika@gmail.com|Chani}}
{{FeatureInProgress|extenders|Add grouping support to extenders|r.scheepmaker@student.utwente.nl|Rob Scheepmaker}}
{{FeatureInProgress|systemtray|Group multiple jobs and notifications|r.scheepmaker@student.utwente.nl|Rob Scheepmaker}}

|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |KWin - Core
{{FeatureTodo|KWin|Redesign KWin system settings GUI|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureTodo|KWin|ARGB support for decorations|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureInProgress|KWin|Window docking/quick tiling|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureTodo|KWin|Internal desktop layout/pager support|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureInProgress|KWin|Non-composited Present Windows|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|KWin|Tabbox improvements|kde@martin-graesslin.com|Martin Gräßlin}}
|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |KWin - Desktop Effects
{{FeatureTodo|KWin|Expand present windows into other effects (E.g. Desktop Grid)|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|KWin|OpenGL 3 compatible Shaders|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|KWin|Improved cube reflection|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KWin|Fade desktop effect (Desktop switcher)|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureDone|KWin|Highlight window effect|lmurray@undefinedfire.com|Lucas Murray}}
|}

= kdepimlibs =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|Buildsystem|Require OpenLDAP (coordinate with the Windows team)|winter@kde.org|Allen Winter}}
{{FeatureTodo|Buildsystem|Require Cyrus-SASL (coordinate with the Windows team)|winter@kde.org|Allen Winter}}
{{FeatureTodo|libkleopatraclient|New interface library for kleopatra uiserver clients|marc@kdab.net|Marc Mutz}}
{{FeatureTodo|pimtextedit|New library around text edits, to provide support for inline images in the signature editor, among others|mcguire@kde.org|Thomas McGuire}}
|}

= kdenetwork =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|Kopete|UPnp Support|mattr@kde.org|Matt Rogers}}
{{FeatureDone|Kopete|Updated contact list interface (uses Qt 4 rather than Qt 3)|mattr@kde.org|Matt Rogers}}
{{FeatureTodo|Kopete|Update Kopete to better support Decibel|kopete-devel@kde.org|Kopete Developers}}
{{FeatureTodo|Kopete|Jabber Jingle video support|detlev.casanova@gmail.com|Detlev Casanova}}
{{FeatureTodo|Kopete|Jabber Jingle ICE support|detlev.casanova@gmail.com|Detlev Casanova}}
{{FeatureInProgress|Kopete|Contacts plasmoid|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|KGet|MultiSource-Downloading|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureTodo|KGet|Support mms://-protocol, see https://launchpad.net/libmms|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureTodo|KGet|MLDonkey-Plugin based on libkmldonkey|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureTodo|KGet|Advanced Details|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureInProgress|KRDC|NX support|gdavid.devel@gmail.com|David Gross}}
{{FeatureTodo|KRDC|Minimal-clutter mode to optimize screen real estate usage|gpothier@gmail.com|Guillaume Pothier}}
{{FeatureInProgress|Telepathy|Telepathy-specification compliant Account Manager using KWallet to store account data|grundleborg@googlemail.com|George Goldberg}}
{{FeatureInProgress|Telepathy|Account Editing UI for Telepathy|grundleborg@googlemail.com|George Goldberg}}
|}

= kdepim =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|Akonadi|Migration of contacts and calendar data from KResource to Akonadi ([http://techbase.kde.org/Projects/PIM/Akonadi#Scheduled_for_4.3 Details])|kde-pim@kde.org|Volker Krause, Kevin Krammer, Tobias Koenig}}
{{FeatureInProgress|Akregator|Support for syncing the feed list with Google Reader |osterfeld@kde.org|Frank Osterfeld}}
{{FeatureDone|[http://www.astrojar.org.uk/kalarm KAlarm]|Add export of alarms to a new calendar file|djarvie@kde.org|David Jarvie}}
{{FeatureDone|[http://www.astrojar.org.uk/kalarm KAlarm]|Allow configuration of default deferral time interval|djarvie@kde.org|David Jarvie}}
{{FeatureDone|[http://www.astrojar.org.uk/kalarm KAlarm]|Accept drag-and-drop of Todo entries to create a new alarm|djarvie@kde.org|David Jarvie}}
{{FeatureDone|[http://www.astrojar.org.uk/kalarm KAlarm]|Show command execution error indication in alarm list|djarvie@kde.org|David Jarvie}}
{{FeatureDone|[http://www.astrojar.org.uk/kalarm KAlarm]|Add option to spread alarm windows across screen|djarvie@kde.org|David Jarvie}}
{{FeatureTodo|[http://www.astrojar.org.uk/kalarm KAlarm]|Port to Akonadi|djarvie@kde.org|David Jarvie}}
{{FeatureTodo|[http://kblogger.pwsp.net KBlogger]|KBlogger, a blogging application|christian_weilbach@.web.de|Christian Weilbach}}
{{FeatureTodo|KBlogger|Port to use KRichTextEdit (Or KMEditor)|steveire@gmail.com|Stephen Kelly}}
{{FeatureInProgress|KContactManager|A new Akonadi-based address book to replace KAddressbook|tokoe@kde.org|Tobias Koenig}}
{{FeatureInProgress|Kjots| Create and port to akonadi model. |steveire@gmail.com|Stephen Kelly}}
{{FeatureTodo|Kjots| Add support for nepomuk including tagging, possibly storage, and linking. Also a nepomuk tag proxy model for representing the structure as tagged.|steveire@gmail.com|Stephen Kelly}}
{{FeatureInProgress|Kjots| Create plasmoid capable of showing the entire tree, or a single book.|steveire@gmail.com|Stephen Kelly}}
{{FeatureTodo|Kjots| Email KJots pages using default mail client ({{bug|124509}}. |steveire@gmail.com|Stephen Kelly}}
{{FeatureInProgress|Kleopatra|OpenPGP support|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureDone|KMail|Add support for HTML images|yez@familieschepers.nl|Edwin Schepers}}
{{FeatureTodo|KMail|Use asynchronous Kleo|marc@kdab.net|Marc Mutz}}
{{FeatureTodo|KMail|Save metadata about attachments to Nepomuk when saving them|onurf@su.sabanciuniv.edu|Ismail Onur Filiz}}
{{FeatureTodo|KNode|Port to use KRichTextEdit (Or KMEditor)|steveire@gmail.com|Stephen Kelly}}
{{FeatureTodo|Kontact|Support for Kontact wide profiles|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|Kontact|Tip-of-the-Day summary|molkentin@kde.org|Daniel Molkentin}}
{{FeatureTodo|KOrganizer|Support for extended free-busy lists|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureInProgress|KPilot|Port old conduits to new base conduit architecture and KDE4/Qt4|jkasper@kde.org|Jason 'vanRijn' Kasper}}
{{FeatureInProgress|KPilot|Finish Keyring conduit, base conduit code and test cases, category syncing|jkasper@kde.org|Jason 'vanRijn' Kasper}}
|}

= kdeutils =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|printer-applet|Restore feature parity with KDEPrint3 where possible.|john@layt.net|John Layt}}
{{FeatureTodo|Okteta|make editing capability to Decoding table |kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add Kate-like search tool|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for import by drop, both url and data|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|copy again puts also a value or char variant of the data to clipboard|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for memory mapping of files|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add further export formats like s-record and intel 16|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for jobs like io, printing, string search or filter|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|kwalletmanager|Move kwalletmanager to the Model/View architecture and redesign the UI.|lemma@confuego.org|Michael Leupold}}
{{FeatureInProgress|kdelirc|Bring back kdelirc|michael_zanetti@gmx.net|Michael Zanetti}}
|}

= kdebindings =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|krossjava|Integrate into e.g. SuperKaramba and fix issues that show up.|mail@dipe.org|Sebastian Sauer}}
{{FeatureTodo|krossjava|Documentation++|mail@dipe.org|Sebastian Sauer}}
{{FeatureTodo|krossfalcon|Documentation++|mail@dipe.org|Sebastian Sauer}}
|}

= kdegames =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|KGoldrunner|Add Curse of the Mummy game (20 levels), contributed by Steve Mann.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureInProgress|KGoldrunner|Major rewrite, mainly of the game engine and editor.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureInProgress|KGoldrunner|More accurate and reliable pause and resume.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureTodo|KGoldrunner|Save and reload at any instant in a game.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureTodo|KGoldrunner|Record and replay games.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureTodo|KGoldrunner|Run demos ... especially at startup or as hints for difficult levels.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureTodo|KGoldrunner|Hot-new-stuff support for themes and game sets.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureTodo|KGoldrunner|Integration of the Scavenger game (180 new levels) and its rule-set. This would also involve allowing different grid dimensions for different games, as a feature of the new game engine.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureTodo|KGoldrunner|Better support for beginners, such as graphical cues for false bricks and hidden ladders, extra messages with "don't tell me this again", etc.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureInProgress|Killbots|Add "sonic screwdriver" functionality.|parker.coates@gmail.com|Parker Coates}}
{{FeatureTodo|Killbots|Add a tutorial for beginners.|parker.coates@gmail.com|Parker Coates}}
{{FeatureTodo|Kolf|Replace with Kolf 2 (please help!)|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|KPatience|Add a command line switch to manually launch a game of a certain type.|parker.coates@gmail.com|Parker Coates}}
{{FeatureDone|KPatience|Add an option to save the game state at shutdown to be automatically be restored on next run.|parker.coates@gmail.com|Parker Coates}}
{{FeatureDone|KPatience|Add the ability to return to the game selection screen after selecting a game.|parker.coates@gmail.com|Parker Coates}}
{{FeatureTodo|KsirK|rewrite AI code or at least correct most problems related in bug #170777. Volunteers wanted!|kleag@free.fr|Gaël de Chalendar}}
{{FeatureTodo|KsirK|Previous/Next in start new game as described in bug #170774|kleag@free.fr|Gaël de Chalendar}}
{{FeatureTodo|KsirK|Polish the skin editor (doc, contextual help, ...)|kleag@free.fr|Gaël de Chalendar}}
{{FeatureTodo|KsirK|Boost playing over Jabber|kleag@free.fr|Gaël de Chalendar}}
{{FeatureTodo|KSpaceDuel|rewrite AI code|dirkrathlev@gmx.de|Dirk Rathlev}}
{{FeatureDone|ktron|Port and remake the KTron game for KDE 4.3|legolas@legolasweb.nl|Stas Verberkt}}
|}

= kdeadmin =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|KGrubEditor|Integrate KGrubEditor into KDE Admin http://sourceforge.net/projects/kgrubeditor. Approved by Nicolas Ternisien <nicolas.ternisien@gmail.com> |artemis_dot_fowl_dot_2007@gmail_dot_com|Konstantinos Smanis}}
{{FeatureTodo|Guidance|Port Guidance to KDE 4, and move it to KDE Admin http://www.simonzone.com/software/guidance/.|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureTodo|system-config-printer-kde|Restore feature parity with KDEPrint3 where possible.|john@layt.net|john Layt}}
|}

= kdesdk =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|Lokalize|XLIFF support|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Lokalize|various Translation Memory enhancements|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Lokalize|Kross-based scripting|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|QA: glossary checklists|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureTodo|KAppTemplate|Add DBUS support in templates|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureDone|Umbrello|Replace all q3 widgets in the refactoring assistant|andi.fischer@hispeed.ch|Andi Fischer}}
{{FeatureInProgress|Umbrello|Merge in SoC qgraphicsview port branch|krishna.ggk@gmail.com|Gopala Krishna A}}
|}

= kdeedu =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|KAlgebra|Export to MathML Presentation Markup|aleixpol@gmail.com|Aleix Pol}}
{{FeatureTodo|KAlgebra|Some integration with the new KFormula widget|aleixpol@gmail.com|Aleix Pol}}
{{FeatureInProgress|KAlgebra|Add ability to draw 3D plots in cylindrical and spherical coordinates.|orgyforever@gmail.com|Percy Camilo Triveño Aucahuasi}}
{{FeatureTodo|Kalzium|Port Kalzium's periodic table to use new QGraphicsView.|marcus@cryos.org|Marcus D. Hanwell}}
{{FeatureTodo|Kalzium|Remove the libavogadro snapshot, depend on libavogadro directly.|jacob@math.jussieu.fr|Benoit Jacob}}
{{FeatureTodo|Kalzium|Plasmoid to access Kalzium database|cniehaus@kde.org|Carsten Niehaus}}
{{FeatureInProgress|KEduca|Rewrite of the classic test writing/taking application|matt@milliams.com|Matt Williams}}
{{FeatureTodo|KHangMan|Integrate an editor|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KHangMan|Plasmoid|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KHangMan|Theme manager|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Kig|Properties dialog for objects.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Improve construction of bisect lines.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Improve feedback when constructing objects.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|More geometric objects.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Script objects as macros (to be reused more than once).|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Improve the Cabri import filter.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Improve the new/edit script wizard.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|KLettres|Visual Indicator when letter is wrong|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KLettres|Number support|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KLettres|Theme manager|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KStars|Marble widget for Geolocation tool|mboquien@free.fr|Médéric Boquien}}
{{FeatureTodo|KStars|Better printed star charts|kstars@30doradus.org|Jason Harris}}
{{FeatureTodo|KStars|Sync KStars time from device|mutlaqja@ikarustech.com|Jasem Mutlaq}}
{{FeatureTodo|KStars|Better rendering of comets/asteroids|kstars@30doradus.org|Jason Harris}}
{{FeatureTodo|KStars|Texture mapping of the skymap???|kstars@30doradus.org|Jason Harris}}
{{FeatureTodo|KStars|Improve Observing List Wizard|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Display Comet Magnitudes whenever possible|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Information links in-place for each technical term|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Tool to suggest star-hopping techniques???|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Extend conjunction tool to have one object unspecified, but have a genre of objects specified instead|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Simulate Lunar Eclipses|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Simulate Satellites and Iridium Flares|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Social and Geographical Integration for KStars|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KTurtle|Optional rulers/grid for canvas units|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureTodo|Marble|Export map to MxN pixel bitmap|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Bookmarks|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Support for MarbleWidget::setEnabled( bool )|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Map Contents translation|tackat@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Editing GeoDataFeatures|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Layer Management Class|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Plugin architecture for map layers|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Extending GeoPainter|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Marble Runners|hdevalence@gmail.com|Henry de Valence}}
{{FeatureInProgress|Marble|GeoClue Integration |jensmh@gmx.de|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|Routing |jensmh@gmx.de|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|More map providers (WMS?) |jensmh@gmx.de|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|Winkel Triple projection / equivalent |hdevalence@gmail.com|Henry de Valence}}
{{FeatureInProgress|Marble|Marble WorldClock Plasmoid|hdevalence@gmail.com|Henry de Valence}}
{{FeatureInProgress|Marble|Qt-Version settings dialog|hdevalence@gmail.com|Henry de Valence}}
{{FeatureInProgress|Marble|Panoramio Support||Shashank Singh}}
{{FeatureInProgress|Marble|Twitter Plugin||Shashank Singh}}
{{FeatureInProgress|Marble|TimeZone Support|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Support for other planets and the moon|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|DGML2 Support|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Support for imperial units|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Graticule plugin|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|MeasureTool plugin|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Port authors list from the Qt-About dialog to the KDE-About dialog|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Basic KML support|ps_ml@gmx.de|Patrick Spendrin}}
{{FeatureInProgress|Marble|GeoData Model/View Visualization|ps_ml@gmx.de|Patrick Spendrin}}
{{FeatureInProgress|Marble|More generic projection support|inge@lysator.liu.se|Inge Wallin}}
{{FeatureInProgress|Marble|Network plugins|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Parley|Declensions|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureTodo|Step|Improve GUI for creating softbody|ksvladimir@gmail.com|Vladimir Kuznetsov}}
{{FeatureTodo|Step|Use common constraints handling code for collisions|ksvladimir@gmail.com|Vladimir Kuznetsov}}
|}

= kdemultimedia =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|JuK|Remove Qt/KDE3 support lib requirements|michael.pyne@kdemail.net|Michael Pyne}}
{{FeatureTodo|JuK|Allow setting covers directly from URLs supported by KIO - drag/drop already allows this however|michael.pyne@kdemail.net|Michael Pyne}}
{{FeatureDone|JuK|Use XCOMPOSITE real transparency when available for the track announcement popup|michael.pyne@kdemail.net|Michael Pyne}}
{{FeatureTodo|JuK|Allow disabling crossfade|michael.pyne@kdemail.net|Michael Pyne}}
|}

= kdeaccessibility =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdegraphics =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Okular|Generator for Mobipocket format|qbast@go2.pl|Jakub Stachowski}}
{{FeatureDone|strigi|Thumbnailer and analyzer for Mobipocket format|qbast@go2.pl|Jakub Stachowski}}
{{FeatureDone|strigi|Analyzer for epub format|qbast@go2.pl|Jakub Stachowski}}
{{FeatureTodo|Okular|Sound annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Link annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Caret annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Support .snp and .emf file formats|bradh@kde.org|Brad Hards}}
{{FeatureTodo|Okular|Synctex support.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Rich-text for annotations text.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|kruler|More ruler shapes.|msoeken_at_tzi_dot_de|Mathias Soeken}}
{{FeatureDone|kruler|Configurable shortcuts.|msoeken_at_tzi_dot_de|Mathias Soeken}}
{{FeatureTodo|kruler|DBUS Interface.|msoeken_at_tzi_dot_de|Mathias Soeken}}
{{FeatureDone|kruler|Transparent background and opaque drawing of the lines and numbers (Qt 4.5).|msoeken_at_tzi_dot_de|Mathias Soeken}}
{{FeatureTodo|gwenview|Folder view.|agateau@kde.org|Aurélien Gâteau}}
{{FeatureTodo|gwenview|Make thumbnail bar more customizable (orientation, number of row/column).|agateau@kde.org|Aurélien Gâteau}}
{{FeatureTodo|gwenview|Add back video support.|agateau@kde.org|Aurélien Gâteau}}
{{FeatureDone|libksane|Add "Auto selection" after preview.|kare.sars@iki.fi|Kåre Särs}}
|}

= kdebase-runtime =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|drkonqi|DrKonqi new dialog UI + Guided crash reporting tool|andresbajotierra@gmail.com|Dario Andres|}}
{{FeatureInProgress|drkonqi|Backtrace parsing and rating|gkiagiad@csd.uoc.gr|George Kiagiadakis|}}
{{FeatureTodo|drkonqi|DrKonqi native english texts + guide|andresbajotierra@gmail.com|Dario Andres|}}
|}

= kdebase-apps =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|konq_thumbnails|Basic thumbnail support for KHTMLPart views(almost finished, now cleanup code)|yinshuiboy@gmail.com|Siyuan Cao}}
{{FeatureTodo|konq_thumbnails|thumbnail support for all KonqFrame|yinshuiboy@gmail.com|Siyuan Cao}}
{{FeatureTodo|konq_thumbnails|more thumbnail page styles and customization|yinshuiboy@gmail.com|Siyuan Cao}}
{{FeatureTodo|konqueror|"Places" sidebar to replace KDE3's "media:/"|kdedevel_at_etotheipiplusone_dot_com|Simon St James}}
{{FeatureTodo|konqueror|Move Dolphin's Treeview to libkonq so that it can be used in Konqueror|kdedevel_at_etotheipiplusone_dot_com|Simon St James}}
{{FeatureTodo|konqueror|Move Dolphin's Information panel to libkonq so that it can be used in Konqueror|kdedevel_at_etotheipiplusone_dot_com|Simon St James}}
{{FeatureInProgress|dolphin|Matthias's Audio/ Video preview in Information panel|kdedevel_at_etotheipiplusone_dot_com|Simon St James}}
{{FeatureTodo|dolphin|Allow to configure and download service menus|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|dolphin|Nepomuk search integration|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|dolphin|Use Nepomuk to receive the meta data for the Information panel|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|konsole|Get a working DBus interface|kurt.hindenburg@gmail.com|Kurt Hindenburg}}
{{FeatureTodo|konsole|Redesign manage profile dialog to allow users to sort profiles|kurt.hindenburg@gmail.com|Kurt Hindenburg}}
{{FeatureTodo|konsole|Allow window/terminal size to be set in profiles|kurt.hindenburg@gmail.com|Kurt Hindenburg}}
|}

= kdeplasma-addons =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact

{{FeatureInProgress|Video Plasmoid|a media player widget complete with a basic dbus interface|notmart@gmail.com|Marco Martin}}
{{FeatureDone|System Load Viewer|A tiny monitor for CPU, RAM and swap usage (known as System Monitor in KDE3)|dhaumann@kde.org|Dominik Haumann}}
{{FeatureInProgress|Comic Plasmoid|Clean up the config-dialog|mat69@gmx.net|Matthias Fuchs}}
{{FeatureTodo|Comic Plasmoid|Port to popup applet|mat69@gmx.net|Matthias Fuchs}}
{{FeatureTodo|PoTD Engine|Import PoTD engine|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Metadata Engine|Import Metadata engine|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Frame Plasmoid|Display Picture Metadata|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Frame Plasmoid|Add url as setting|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Frame Plasmoid|Add buttons Next/Previous/pause in slideshow mode|annma@kde.org|Anne-Marie Mahfouf}}
|}

Schedules/KDE4/4.3 Feature Plan

2009-04-01T16:59:52Z

Grundleborg: /* kdenetwork */

This is a list of planned features for the 4.3 release.

See also:
* [[Schedules/KDE4/4.3 Release Schedule]]
* [[Schedules/KDE4/4.3 Release Goals]]
* [[Schedules/KDE4/4.2 Feature Plan]]

Legend:
* todo => not started yet
* in-progress => started, but not completed yet
* done => completed
__TOC__

= Other =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|Akonadi|Various Akonadi related items can be found here http://techbase.kde.org/Projects/PIM/Akonadi#Scheduled_for_KDE_4.3_.2F_Akonadi_1.2|kde-pim@kde.org|Akonadi Developers}}
{{FeatureInProgress|KPackageKit|Pushing in KPackageKit (dependant on PolicyKit integration)|dantti85-dev@yahoo.com.br|Daniel}}
|}

= kdelibs =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|KLocale|Investigate adding Currency Code and currency minor units support based on ISO 4217 (http://en.wikipedia.org/wiki/ISO_4217).|john@layt.net|John Layt}}
{{FeatureInProgress|kdecore|Thread safety in ksycoca (KService, KMimeType etc.)|faure:AT:kde.org|David Faure}}
{{FeatureInProgress|Sonnet|Implement language detection|qbast@go2.pl|Jakub Stachowski}}
{{FeatureInProgress|Sonnet|Integrate language detection with spellchecking|qbast@go2.pl|Jakub Stachowski}}
{{FeatureTodo|Sonnet|Integrate language detection with strigi|qbast@go2.pl|Jakub Stachowski}}
{{FeatureTodo|Sonnet|Grammar checking (at least for English)|qbast@go2.pl|Jakub Stachowski}}
{{FeatureInProgress|kio|Move KTcpSocket to kio and make it public; some cleanup required|ahartmetz@gmail.com|Andreas Hartmetz}}
{{FeatureTodo|KCalendarSystem|Add new astronomical calculation support classes to be used in kdelibs to build new astronomically based calendar systems, and in kdepim to build new version of libkholiday.|john@layt.net|John Layt}}
{{FeatureTodo|KCalendarSystem|Add new calendar systems: Indian Civil (Saka), Ethiopean, Chinese, Pure Julian, Pure Gregorian, etc.|john@layt.net|John Layt}}
{{FeatureTodo|KDEPrint|If no file printing support in Qt4.5, migrate FilePrinter class from Okular to enable file printing for all apps via QPrinter. To be discussed on k-c-d first.|john@layt.net|John Layt}}
{{FeatureTodo|KDEPrint|Add framework for standard actions for 'Send to...' for e-mail, fax, etc by printing to PDF/PS.|john@layt.net|John Layt}}
{{FeatureTodo|kdeui|entries to help menu and aboutdata pointing to UserBase entry and forum.kde.org|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|kdesu|Classes to help kde-apps open ports in the local firewall (via IPTables/IPFW, etc...)|tejas@gja.in|Tejas Dinkar}}
|}

= kdebase-workspace =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact

|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |Non-Plasma, Non-KWin
{{FeatureTodo|Kxkb|Support for languages in keyboard layout descriptions|rysin:AT:kde.org|Andriy Rysin}}
{{FeatureDone|PolicyKit integration|Import PolicyKit-KDE from extragear|drf54321@gmail.com|Dario Freddi}}
{{FeatureDone|Solid Actions KCM|Import Solid actions KControl module from playground|ben@eclipse.endoftheinternet.org|Ben Cooksley}}
{{FeatureTodo|KControl4|Import refactor of systemsettings with Tree and Icon view support|ben(at)eclipse(dot)endoftheinternet(dot)org+msoeken(at)informatik(dot)uni-bremen(dot)de|Ben Cooksley and Mathias Soeken}}
{{FeatureDone|KSysguard|Added GetHotNewStuff support|a@b.com|name}}
{{FeatureInProgress|KActiveEdges|Split active screen edges from KWin|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureInProgress|Solid Wicd Engine|Import Solid Wicd engine from github/playground|drf54321@gmail.com|Dario Freddi}}
{{FeatureDone|Klipper|Made klipper automatically find possible actions based on filename copied to clipboard|dimsuz@gmail.com|Dmitry Suzdalev}}
{{FeatureDone|Klipper|Improved action adding/editing workflow by implementing a special dialog for editing a certain action|dimsuz@gmail.com|Dmitry Suzdalev}}

|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |KRunner

|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |Plasma - Priority Features

|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |Plasma
{{FeatureTodo|Now Playing data engine|Support for MPD|kde:AT:randomguy3.me.uk|Alex Merry}}
{{FeatureDone|Classic Menu Launcher|Optional recently used applications and System Settings menu|mail:AT:dipe.org|Sebastian Sauer}}
{{FeatureInProgress|Reusable video widget|A widget in libplasma that can play video and audio|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Message box|A message box shown as an overlay over plasmoids|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Systemtray protocol|New systemtray protocol beginnings: daemon and systemtray widget part|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Default theme|Air: new default Plasma theme|notmart@gmail.com|Marco Martin and Nuno Pinheiro}}
{{FeatureInProgress|screensaver|security constraints|chanika@gmail.com|Chani}}
{{FeatureInProgress|keyboard shortcuts|configuration|chanika@gmail.com|Chani}}
{{FeatureTodo|icon plasmoid|make it suck less|chanika@gmail.com|Chani}}
{{FeatureTodo|desktop|make a plasmoid when I paste stuff|chanika@gmail.com|Chani}}
{{FeatureInProgress|extenders|Add grouping support to extenders|r.scheepmaker@student.utwente.nl|Rob Scheepmaker}}
{{FeatureInProgress|systemtray|Group multiple jobs and notifications|r.scheepmaker@student.utwente.nl|Rob Scheepmaker}}

|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |KWin - Core
{{FeatureTodo|KWin|Redesign KWin system settings GUI|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureTodo|KWin|ARGB support for decorations|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureInProgress|KWin|Window docking/quick tiling|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureTodo|KWin|Internal desktop layout/pager support|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureInProgress|KWin|Non-composited Present Windows|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|KWin|Tabbox improvements|kde@martin-graesslin.com|Martin Gräßlin}}
|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |KWin - Desktop Effects
{{FeatureTodo|KWin|Expand present windows into other effects (E.g. Desktop Grid)|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|KWin|OpenGL 3 compatible Shaders|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|KWin|Improved cube reflection|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KWin|Fade desktop effect (Desktop switcher)|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureDone|KWin|Highlight window effect|lmurray@undefinedfire.com|Lucas Murray}}
|}

= kdepimlibs =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|Buildsystem|Require OpenLDAP (coordinate with the Windows team)|winter@kde.org|Allen Winter}}
{{FeatureTodo|Buildsystem|Require Cyrus-SASL (coordinate with the Windows team)|winter@kde.org|Allen Winter}}
{{FeatureTodo|libkleopatraclient|New interface library for kleopatra uiserver clients|marc@kdab.net|Marc Mutz}}
{{FeatureTodo|pimtextedit|New library around text edits, to provide support for inline images in the signature editor, among others|mcguire@kde.org|Thomas McGuire}}
|}

= kdenetwork =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|Kopete|UPnp Support|mattr@kde.org|Matt Rogers}}
{{FeatureDone|Kopete|Updated contact list interface (uses Qt 4 rather than Qt 3)|mattr@kde.org|Matt Rogers}}
{{FeatureTodo|Kopete|Update Kopete to better support Decibel|kopete-devel@kde.org|Kopete Developers}}
{{FeatureTodo|Kopete|Jabber Jingle video support|detlev.casanova@gmail.com|Detlev Casanova}}
{{FeatureTodo|Kopete|Jabber Jingle ICE support|detlev.casanova@gmail.com|Detlev Casanova}}
{{FeatureInProgress|Kopete|Contacts plasmoid|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|KGet|MultiSource-Downloading|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureTodo|KGet|Support mms://-protocol, see https://launchpad.net/libmms|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureTodo|KGet|MLDonkey-Plugin based on libkmldonkey|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureTodo|KGet|Advanced Details|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureInProgress|KRDC|NX support|gdavid.devel@gmail.com|David Gross}}
{{FeatureTodo|KRDC|Minimal-clutter mode to optimize screen real estate usage|gpothier@gmail.com|Guillaume Pothier}}
{{FeatureInProgress|Telepathy|Telepathy-specification compliant Account Manager using KWallet to store account data|grundleborg@googlemail.com|George Goldberg}}
|}
{{FeatureInProgress|Telepathy|Account Editing UI for Telepathy|grundleborg@googlemail.com|George Goldberg}}
|}

= kdepim =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|Akonadi|Migration of contacts and calendar data from KResource to Akonadi ([http://techbase.kde.org/Projects/PIM/Akonadi#Scheduled_for_4.3 Details])|kde-pim@kde.org|Volker Krause, Kevin Krammer, Tobias Koenig}}
{{FeatureInProgress|Akregator|Support for syncing the feed list with Google Reader |osterfeld@kde.org|Frank Osterfeld}}
{{FeatureDone|[http://www.astrojar.org.uk/kalarm KAlarm]|Add export of alarms to a new calendar file|djarvie@kde.org|David Jarvie}}
{{FeatureDone|[http://www.astrojar.org.uk/kalarm KAlarm]|Allow configuration of default deferral time interval|djarvie@kde.org|David Jarvie}}
{{FeatureDone|[http://www.astrojar.org.uk/kalarm KAlarm]|Accept drag-and-drop of Todo entries to create a new alarm|djarvie@kde.org|David Jarvie}}
{{FeatureDone|[http://www.astrojar.org.uk/kalarm KAlarm]|Show command execution error indication in alarm list|djarvie@kde.org|David Jarvie}}
{{FeatureDone|[http://www.astrojar.org.uk/kalarm KAlarm]|Add option to spread alarm windows across screen|djarvie@kde.org|David Jarvie}}
{{FeatureTodo|[http://www.astrojar.org.uk/kalarm KAlarm]|Port to Akonadi|djarvie@kde.org|David Jarvie}}
{{FeatureTodo|[http://kblogger.pwsp.net KBlogger]|KBlogger, a blogging application|christian_weilbach@.web.de|Christian Weilbach}}
{{FeatureTodo|KBlogger|Port to use KRichTextEdit (Or KMEditor)|steveire@gmail.com|Stephen Kelly}}
{{FeatureInProgress|KContactManager|A new Akonadi-based address book to replace KAddressbook|tokoe@kde.org|Tobias Koenig}}
{{FeatureInProgress|Kjots| Create and port to akonadi model. |steveire@gmail.com|Stephen Kelly}}
{{FeatureTodo|Kjots| Add support for nepomuk including tagging, possibly storage, and linking. Also a nepomuk tag proxy model for representing the structure as tagged.|steveire@gmail.com|Stephen Kelly}}
{{FeatureInProgress|Kjots| Create plasmoid capable of showing the entire tree, or a single book.|steveire@gmail.com|Stephen Kelly}}
{{FeatureTodo|Kjots| Email KJots pages using default mail client ({{bug|124509}}. |steveire@gmail.com|Stephen Kelly}}
{{FeatureInProgress|Kleopatra|OpenPGP support|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureDone|KMail|Add support for HTML images|yez@familieschepers.nl|Edwin Schepers}}
{{FeatureTodo|KMail|Use asynchronous Kleo|marc@kdab.net|Marc Mutz}}
{{FeatureTodo|KMail|Save metadata about attachments to Nepomuk when saving them|onurf@su.sabanciuniv.edu|Ismail Onur Filiz}}
{{FeatureTodo|KNode|Port to use KRichTextEdit (Or KMEditor)|steveire@gmail.com|Stephen Kelly}}
{{FeatureTodo|Kontact|Support for Kontact wide profiles|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|Kontact|Tip-of-the-Day summary|molkentin@kde.org|Daniel Molkentin}}
{{FeatureTodo|KOrganizer|Support for extended free-busy lists|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureInProgress|KPilot|Port old conduits to new base conduit architecture and KDE4/Qt4|jkasper@kde.org|Jason 'vanRijn' Kasper}}
{{FeatureInProgress|KPilot|Finish Keyring conduit, base conduit code and test cases, category syncing|jkasper@kde.org|Jason 'vanRijn' Kasper}}
|}

= kdeutils =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|printer-applet|Restore feature parity with KDEPrint3 where possible.|john@layt.net|John Layt}}
{{FeatureTodo|Okteta|make editing capability to Decoding table |kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add Kate-like search tool|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for import by drop, both url and data|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|copy again puts also a value or char variant of the data to clipboard|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for memory mapping of files|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add further export formats like s-record and intel 16|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|add support for jobs like io, printing, string search or filter|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|kwalletmanager|Move kwalletmanager to the Model/View architecture and redesign the UI.|lemma@confuego.org|Michael Leupold}}
{{FeatureInProgress|kdelirc|Bring back kdelirc|michael_zanetti@gmx.net|Michael Zanetti}}
|}

= kdebindings =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|krossjava|Integrate into e.g. SuperKaramba and fix issues that show up.|mail@dipe.org|Sebastian Sauer}}
{{FeatureTodo|krossjava|Documentation++|mail@dipe.org|Sebastian Sauer}}
{{FeatureTodo|krossfalcon|Documentation++|mail@dipe.org|Sebastian Sauer}}
|}

= kdegames =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|KGoldrunner|Add Curse of the Mummy game (20 levels), contributed by Steve Mann.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureInProgress|KGoldrunner|Major rewrite, mainly of the game engine and editor.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureInProgress|KGoldrunner|More accurate and reliable pause and resume.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureTodo|KGoldrunner|Save and reload at any instant in a game.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureTodo|KGoldrunner|Record and replay games.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureTodo|KGoldrunner|Run demos ... especially at startup or as hints for difficult levels.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureTodo|KGoldrunner|Hot-new-stuff support for themes and game sets.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureTodo|KGoldrunner|Integration of the Scavenger game (180 new levels) and its rule-set. This would also involve allowing different grid dimensions for different games, as a feature of the new game engine.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureTodo|KGoldrunner|Better support for beginners, such as graphical cues for false bricks and hidden ladders, extra messages with "don't tell me this again", etc.|ianw2@optusnet.com.au|Ian Wadham}}
{{FeatureInProgress|Killbots|Add "sonic screwdriver" functionality.|parker.coates@gmail.com|Parker Coates}}
{{FeatureTodo|Killbots|Add a tutorial for beginners.|parker.coates@gmail.com|Parker Coates}}
{{FeatureTodo|Kolf|Replace with Kolf 2 (please help!)|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|KPatience|Add a command line switch to manually launch a game of a certain type.|parker.coates@gmail.com|Parker Coates}}
{{FeatureDone|KPatience|Add an option to save the game state at shutdown to be automatically be restored on next run.|parker.coates@gmail.com|Parker Coates}}
{{FeatureDone|KPatience|Add the ability to return to the game selection screen after selecting a game.|parker.coates@gmail.com|Parker Coates}}
{{FeatureTodo|KsirK|rewrite AI code or at least correct most problems related in bug #170777. Volunteers wanted!|kleag@free.fr|Gaël de Chalendar}}
{{FeatureTodo|KsirK|Previous/Next in start new game as described in bug #170774|kleag@free.fr|Gaël de Chalendar}}
{{FeatureTodo|KsirK|Polish the skin editor (doc, contextual help, ...)|kleag@free.fr|Gaël de Chalendar}}
{{FeatureTodo|KsirK|Boost playing over Jabber|kleag@free.fr|Gaël de Chalendar}}
{{FeatureTodo|KSpaceDuel|rewrite AI code|dirkrathlev@gmx.de|Dirk Rathlev}}
{{FeatureDone|ktron|Port and remake the KTron game for KDE 4.3|legolas@legolasweb.nl|Stas Verberkt}}
|}

= kdeadmin =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|KGrubEditor|Integrate KGrubEditor into KDE Admin http://sourceforge.net/projects/kgrubeditor. Approved by Nicolas Ternisien <nicolas.ternisien@gmail.com> |artemis_dot_fowl_dot_2007@gmail_dot_com|Konstantinos Smanis}}
{{FeatureTodo|Guidance|Port Guidance to KDE 4, and move it to KDE Admin http://www.simonzone.com/software/guidance/.|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureTodo|system-config-printer-kde|Restore feature parity with KDEPrint3 where possible.|john@layt.net|john Layt}}
|}

= kdesdk =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|Lokalize|XLIFF support|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Lokalize|various Translation Memory enhancements|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Lokalize|Kross-based scripting|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|QA: glossary checklists|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureTodo|KAppTemplate|Add DBUS support in templates|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureDone|Umbrello|Replace all q3 widgets in the refactoring assistant|andi.fischer@hispeed.ch|Andi Fischer}}
{{FeatureInProgress|Umbrello|Merge in SoC qgraphicsview port branch|krishna.ggk@gmail.com|Gopala Krishna A}}
|}

= kdeedu =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|KAlgebra|Export to MathML Presentation Markup|aleixpol@gmail.com|Aleix Pol}}
{{FeatureTodo|KAlgebra|Some integration with the new KFormula widget|aleixpol@gmail.com|Aleix Pol}}
{{FeatureInProgress|KAlgebra|Add ability to draw 3D plots in cylindrical and spherical coordinates.|orgyforever@gmail.com|Percy Camilo Triveño Aucahuasi}}
{{FeatureTodo|Kalzium|Port Kalzium's periodic table to use new QGraphicsView.|marcus@cryos.org|Marcus D. Hanwell}}
{{FeatureTodo|Kalzium|Remove the libavogadro snapshot, depend on libavogadro directly.|jacob@math.jussieu.fr|Benoit Jacob}}
{{FeatureTodo|Kalzium|Plasmoid to access Kalzium database|cniehaus@kde.org|Carsten Niehaus}}
{{FeatureInProgress|KEduca|Rewrite of the classic test writing/taking application|matt@milliams.com|Matt Williams}}
{{FeatureTodo|KHangMan|Integrate an editor|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KHangMan|Plasmoid|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KHangMan|Theme manager|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Kig|Properties dialog for objects.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Improve construction of bisect lines.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Improve feedback when constructing objects.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|More geometric objects.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Script objects as macros (to be reused more than once).|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Improve the Cabri import filter.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Kig|Improve the new/edit script wizard.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|KLettres|Visual Indicator when letter is wrong|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KLettres|Number support|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KLettres|Theme manager|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KStars|Marble widget for Geolocation tool|mboquien@free.fr|Médéric Boquien}}
{{FeatureTodo|KStars|Better printed star charts|kstars@30doradus.org|Jason Harris}}
{{FeatureTodo|KStars|Sync KStars time from device|mutlaqja@ikarustech.com|Jasem Mutlaq}}
{{FeatureTodo|KStars|Better rendering of comets/asteroids|kstars@30doradus.org|Jason Harris}}
{{FeatureTodo|KStars|Texture mapping of the skymap???|kstars@30doradus.org|Jason Harris}}
{{FeatureTodo|KStars|Improve Observing List Wizard|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Display Comet Magnitudes whenever possible|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Information links in-place for each technical term|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Tool to suggest star-hopping techniques???|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Extend conjunction tool to have one object unspecified, but have a genre of objects specified instead|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Simulate Lunar Eclipses|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Simulate Satellites and Iridium Flares|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KStars|Social and Geographical Integration for KStars|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureTodo|KTurtle|Optional rulers/grid for canvas units|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureTodo|Marble|Export map to MxN pixel bitmap|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Bookmarks|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Support for MarbleWidget::setEnabled( bool )|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Map Contents translation|tackat@kde.org|Torsten Rahn}}
{{FeatureTodo|Marble|Editing GeoDataFeatures|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Layer Management Class|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Plugin architecture for map layers|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Extending GeoPainter|rahn@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Marble Runners|hdevalence@gmail.com|Henry de Valence}}
{{FeatureInProgress|Marble|GeoClue Integration |jensmh@gmx.de|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|Routing |jensmh@gmx.de|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|More map providers (WMS?) |jensmh@gmx.de|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|Winkel Triple projection / equivalent |hdevalence@gmail.com|Henry de Valence}}
{{FeatureInProgress|Marble|Marble WorldClock Plasmoid|hdevalence@gmail.com|Henry de Valence}}
{{FeatureInProgress|Marble|Qt-Version settings dialog|hdevalence@gmail.com|Henry de Valence}}
{{FeatureInProgress|Marble|Panoramio Support||Shashank Singh}}
{{FeatureInProgress|Marble|Twitter Plugin||Shashank Singh}}
{{FeatureInProgress|Marble|TimeZone Support|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Support for other planets and the moon|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|DGML2 Support|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Support for imperial units|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Graticule plugin|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|MeasureTool plugin|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Port authors list from the Qt-About dialog to the KDE-About dialog|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Basic KML support|ps_ml@gmx.de|Patrick Spendrin}}
{{FeatureInProgress|Marble|GeoData Model/View Visualization|ps_ml@gmx.de|Patrick Spendrin}}
{{FeatureInProgress|Marble|More generic projection support|inge@lysator.liu.se|Inge Wallin}}
{{FeatureInProgress|Marble|Network plugins|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Parley|Declensions|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureTodo|Step|Improve GUI for creating softbody|ksvladimir@gmail.com|Vladimir Kuznetsov}}
{{FeatureTodo|Step|Use common constraints handling code for collisions|ksvladimir@gmail.com|Vladimir Kuznetsov}}
|}

= kdemultimedia =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureTodo|JuK|Remove Qt/KDE3 support lib requirements|michael.pyne@kdemail.net|Michael Pyne}}
{{FeatureTodo|JuK|Allow setting covers directly from URLs supported by KIO - drag/drop already allows this however|michael.pyne@kdemail.net|Michael Pyne}}
{{FeatureDone|JuK|Use XCOMPOSITE real transparency when available for the track announcement popup|michael.pyne@kdemail.net|Michael Pyne}}
{{FeatureTodo|JuK|Allow disabling crossfade|michael.pyne@kdemail.net|Michael Pyne}}
|}

= kdeaccessibility =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
|}

= kdegraphics =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureDone|Okular|Generator for Mobipocket format|qbast@go2.pl|Jakub Stachowski}}
{{FeatureDone|strigi|Thumbnailer and analyzer for Mobipocket format|qbast@go2.pl|Jakub Stachowski}}
{{FeatureDone|strigi|Analyzer for epub format|qbast@go2.pl|Jakub Stachowski}}
{{FeatureTodo|Okular|Sound annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Link annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Caret annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Support .snp and .emf file formats|bradh@kde.org|Brad Hards}}
{{FeatureTodo|Okular|Synctex support.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Rich-text for annotations text.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|kruler|More ruler shapes.|msoeken_at_tzi_dot_de|Mathias Soeken}}
{{FeatureDone|kruler|Configurable shortcuts.|msoeken_at_tzi_dot_de|Mathias Soeken}}
{{FeatureTodo|kruler|DBUS Interface.|msoeken_at_tzi_dot_de|Mathias Soeken}}
{{FeatureDone|kruler|Transparent background and opaque drawing of the lines and numbers (Qt 4.5).|msoeken_at_tzi_dot_de|Mathias Soeken}}
{{FeatureTodo|gwenview|Folder view.|agateau@kde.org|Aurélien Gâteau}}
{{FeatureTodo|gwenview|Make thumbnail bar more customizable (orientation, number of row/column).|agateau@kde.org|Aurélien Gâteau}}
{{FeatureTodo|gwenview|Add back video support.|agateau@kde.org|Aurélien Gâteau}}
{{FeatureDone|libksane|Add "Auto selection" after preview.|kare.sars@iki.fi|Kåre Särs}}
|}

= kdebase-runtime =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|drkonqi|DrKonqi new dialog UI + Guided crash reporting tool|andresbajotierra@gmail.com|Dario Andres|}}
{{FeatureInProgress|drkonqi|Backtrace parsing and rating|gkiagiad@csd.uoc.gr|George Kiagiadakis|}}
{{FeatureTodo|drkonqi|DrKonqi native english texts + guide|andresbajotierra@gmail.com|Dario Andres|}}
|}

= kdebase-apps =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact
{{FeatureInProgress|konq_thumbnails|Basic thumbnail support for KHTMLPart views(almost finished, now cleanup code)|yinshuiboy@gmail.com|Siyuan Cao}}
{{FeatureTodo|konq_thumbnails|thumbnail support for all KonqFrame|yinshuiboy@gmail.com|Siyuan Cao}}
{{FeatureTodo|konq_thumbnails|more thumbnail page styles and customization|yinshuiboy@gmail.com|Siyuan Cao}}
{{FeatureTodo|konqueror|"Places" sidebar to replace KDE3's "media:/"|kdedevel_at_etotheipiplusone_dot_com|Simon St James}}
{{FeatureTodo|konqueror|Move Dolphin's Treeview to libkonq so that it can be used in Konqueror|kdedevel_at_etotheipiplusone_dot_com|Simon St James}}
{{FeatureTodo|konqueror|Move Dolphin's Information panel to libkonq so that it can be used in Konqueror|kdedevel_at_etotheipiplusone_dot_com|Simon St James}}
{{FeatureInProgress|dolphin|Matthias's Audio/ Video preview in Information panel|kdedevel_at_etotheipiplusone_dot_com|Simon St James}}
{{FeatureTodo|dolphin|Allow to configure and download service menus|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|dolphin|Nepomuk search integration|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|dolphin|Use Nepomuk to receive the meta data for the Information panel|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|konsole|Get a working DBus interface|kurt.hindenburg@gmail.com|Kurt Hindenburg}}
{{FeatureTodo|konsole|Redesign manage profile dialog to allow users to sort profiles|kurt.hindenburg@gmail.com|Kurt Hindenburg}}
{{FeatureTodo|konsole|Allow window/terminal size to be set in profiles|kurt.hindenburg@gmail.com|Kurt Hindenburg}}
|}

= kdeplasma-addons =
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Project !! Description !! Contact

{{FeatureInProgress|Video Plasmoid|a media player widget complete with a basic dbus interface|notmart@gmail.com|Marco Martin}}
{{FeatureDone|System Load Viewer|A tiny monitor for CPU, RAM and swap usage (known as System Monitor in KDE3)|dhaumann@kde.org|Dominik Haumann}}
{{FeatureInProgress|Comic Plasmoid|Clean up the config-dialog|mat69@gmx.net|Matthias Fuchs}}
{{FeatureTodo|Comic Plasmoid|Port to popup applet|mat69@gmx.net|Matthias Fuchs}}
{{FeatureTodo|PoTD Engine|Import PoTD engine|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Metadata Engine|Import Metadata engine|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Frame Plasmoid|Display Picture Metadata|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Frame Plasmoid|Add url as setting|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Frame Plasmoid|Add buttons Next/Previous/pause in slideshow mode|annma@kde.org|Anne-Marie Mahfouf}}
|}

Projects/Summer of Code/2009/Ideas

2009-02-22T13:15:31Z

Grundleborg: /* Plasma */

== 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 kde-devel@kde.org. See [http://www.kde.org/mailinglists/ 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==
===Plasma===
[http://plasma.kde.org Website] - [https://mail.kde.org/mailman/listinfo/panel-dev Mailing list] - IRC channel: #plasma on Freenode.

====Project: Generic SOAP Plasma::Service====
'''Brief explanation:'''
The Service should be able to parse WSDL files and let Plasmoids connect to the described Webservices.

====Project: Simple Media Center components====
'''Brief explanation:'''
Plasma could offer a Media center mode, where features a really simple ui to browse media files and plasmoids that shows the actual media. All should be operable with mouse, keyboard or a simple remote control. the work could consist in building the whole thing or just writing a plasmoid able to browse media files, that is the most important missing part.
Mockups for it by Nuno Pinheiro can be seen [http://img213.imageshack.us/img213/3200/image3231picturefz5.png here] and [http://img26.imageshack.us/img26/3407/image323musicoloectionck2.png here]

'''Expected results:'''
An applet to browse and thumbnail media files, like the first mockup and control the actual media viewing applets, like the media player applet or the picture frame applet. At this stage the functionality will be really minimum

'''Knowledge prerequisite:'''
Knowledge of C++ and some familiarity with Qt especially QGraphicsView related classes.

'''Mentor:'''
Marco Martin (notmart a gmail dot org), or other Plasma developers. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Plasmate====
'''Brief explanation:'''
PlasMate is an application that gives people a way to start creating scripted plasmoids without worrying about anything except making their bits. It hides the whole metadata.desktop thing, the package layout details, making a Plasmoid package (aka "zipping up the directory"), uploading content and version control system.

'''Expected results:'''
Working application that one can do the tasks described above, making it easy to create and distribute a scripted plasmoid.

'''Knowledge prerequisite:'''
Knowledge of C++ and familiarity with Qt (QWidgets and QGraphicsView related classes).

'''Mentor:'''
Artur Duque de Souza (morpheuz a gmail dot org), or other Plasma developers. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Qt Kinetic + Plasma====
'''Brief explanation:'''
A layer over Qt Kinetic to provide a standardized set of "out of the box"
animations and bring them into libplasma. The work will be done with the Plasma developers to make this API as efficient as possible. The work will be based on Kinetic, the next framework for animations in Qt.

'''Expected results:'''
We can kill Plasma::Animator class. The goal is to bring fancy effects/animations in Plasma to have one of the best desktop ever.

'''Knowledge prerequisite:'''
Knowledge of C++, familiarity with QGraphicsView related classes and some familiarity with animations bits.

'''Mentor:'''
Alexis Ménard (alexis.menard at nokia dot com) or Artur Duque de Souza (morpheuz a gmail dot org). Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Eduactional layout====
'''Brief explanation:'''
A set of Containments and Plasmoids specifically designed for primary school
students.

'''Expected results:'''
A simplified panel containment that contains basic launchers and user feedback
for the student, a widget that allows teachers to provide context-specific
sets of applications and documents to the student (context being a combination
of the student logged in and the current class subject), a widget that
provides some basic teacher->student communication and status (e.g. what the
current assignment is, how long the student has been logged in, etc) and
optionally some widgets that work with KDE edu apps.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Desktop dock====
'''Brief explanation:'''
A MacOS style dock containment.

'''Expected results:'''
A containment that provides a similar user experience to the MacOS dock:
application launchers that are also task bar entries when the application is
active and a separate area for widgets such as the trash, battery, etc.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Kdm frontend using plasma====
'''Brief explanation:'''
A log-in screen layout manager for KDM that uses libplasma.

'''Expected results:'''
A KDM screen that is rendered completely using Plasma. This means both using
libplasma in KDM for the log in screen as well as writing Plasmoids for
entering the user name and password, listing users, session switching, etc.
Some of these widgets already exist for the desktop shell, so in some cases
this will be simply integrating existing Plasmoids, but in other cases will
mean writing new ones from the ground up.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Raptor====
'''Brief explanation:'''
Raptor aims to deliver a new kind of launch menu system for KDE. It is designed with usability and beauty in mind.
Raptor-Menu does not try to be the final answer to the menu question, instead aspires to be the best answer we can give, merging many ideas form modern desktop launch menus.

'''Expected results:'''
http://www.raptor-menu.org/

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: New Widget Explorer====
'''Brief explanation:'''
A new widget explorer that supports both our own widgets as well as others
more seamlessly.

'''Expected results:'''
A usable and pretty browser for widgets that allows a user to see an icon or
snapshot of the widget, select a widget to be placed in a containment, search
for a widget based on name/description, sort the widgets into categories, rate
widgets and provide ways to launch the online browsers and installers for both
native Plasmoids as well as third party tools such as Google Gadgets (which is
already supported in the Package class). All the required support
functionality already exists, this project is really about creating a
beautiful and dynamic user interface for looking through a widget catalog that
looks "Plasma".

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: D-Bus Interface====
'''Brief explanation:'''
A comprehensive set of D-Bus interfaces for the plasma-desktop Plasma shell.

'''Expected results:'''
The D-Bus interface must provide access to the Corona (DestkopCorona class),
which in turn will list all existing Containments and allow Containments to be
added, removed, saved, etc.

A D-Bus interface for each existing Containment will be made available as
well, which will provide a standard set of tools including listing, adding and
removing widgets as well as positioning and sizing for PanelContaiments. Ways
to control the wallpaper, if any, will also be provided in the per-Containment
D-Bus interface.

In turn, a D-Bus interface for each widget representing its available
contextual actions will be provided dynamically upon request.

Finally, the application D-Bus interface for things such as locking/unlocking
widgets will be designed and implemented.

The result will be a Plasma that is fully accessible via D-Bus.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Security====
'''Brief explanation:'''
A set of methods to define the existing security state of the Plasma
application, the security requirements of individual widgets, mechanisms to
respect those two sets of information and cryptographic signing of Plasmoid
packages.

'''Expected results:'''
A set of functionality descriptions will be enumerated (e.g. "Network access",
"Local file system access", etc.). Individual widgets will advertise which of
these functionality sets they require.

The plasma-overlay shell (used on the screensaver) will have code added to it
to respect these settings and not run widgets that advertise they need things
that aren't safe to provide on a screensaver (due to it being locked to
prevent others from accessing the system).

The plasma-desktop shell will gain the ability to be put into various lock down
states which will map to different sets of functionality. Part of this project
will be enumerate the various states, but that list must include "only load
trusted widgets", "no external access", "no local file system access".

The JavaScript engine will provide methods for each of the functionality sets
(e.g. a set of functions to access local files) which will be exported or not
based on the current Security state. This implies providing a security state
to the Corona which can then be passed on down to Applets and AppletScripts.

Finally, GPG signing of Plasmoid packages will be implemented along with a way
of checking the validity of these at runtime.

'''Knowledge prerequisite:'''
Knowledge of C++ and some experience with security.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Telepathy Integration====

See [[#Project:_Telepathy_Plasma_Integration| here]] for more project details.

===Amarok===
A KDE music manager and player.

[http://amarok.kde.org Website] - [https://mail.kde.org/mailman/listinfo/amarok Mailing list] - IRC channel: #amarok on Freenode.

====Project: DLNA/UPnP Support====
'''Brief explanation:'''
Using the UPnP protocol users can, for example, share music from their Vista computer to a PS3. Amarok lacks any sort of UPnP support. Being able to act as a client or possibly a UPnP media server would be useful. In addition to that controlling a UPnP Media Renderer from within Amarok is possible with framework support.

The [http://coherence.beebits.net/ Coherence server] would likely be used since it is also intended to be used by a KIO slave.

'''Expected results:'''
*Using the Amarok Collection framework, create a plugin which allows Amarok to browse, search and play music off of a UPnP share. Playing music may use the UPnP KIO-slave, but more advanced functionality requires Amarok to handle this directly.
*Allow Amarok to share it's collection with other devices or control other devices via UPnP. This is secondary priority but it may be pretty easy with Coherence.
*Control UPnP Media Renderers (DMR: Digital Media Renderer device class in DLNA) from within Amarok.

'''Material Prerequisite:''' Some UPnP devices or computers to test with. Good excuse to buy a PS3. If you live in Europe a Philips Streamium DMR can be borrowed.

'''Knowledge Prerequisite:''' C++ and Qt. Coherence uses Python and D-Bus but doesn't need to be hacked on in the scope of this project.

And of course, understanding of UPnP networking and devices wouldn't hurt!

'''Mentor:''' Stecchino (bart.cerneels at kde dot org)
----

====Project: New meta-applets for the Context View====
'''Brief Explanation:'''
The Context View (CV) is currently used to display multiple applets that expose various information. However, due to the fact that each applet displays a certain type of information from one data source, there is significant amount of wasted space, and it is hard to show much more than 3 different pieces of data at once.

Meta-Applets are large applets that integrate date from multiple data sources in order to display more semantically related information coherently and efficiently. This could mean, for example, an applet that brings together lyrics, artist info, upcoming concerts, and related songs/artists.

More info is available here [http://amarok.kde.org/wiki/Proposals/More_Contexual_Information on the amarok wiki]

'''Expected Results:'''
Two or three (to be discussed with mentor in application writing process) applets that elegantly execute the ideas discussed above.

'''Knowledge prerequisite:'''
Knowledge of C++ is required, and some familiarity with Qt is helpful (especially QGraphicsView) but not necessary.

'''Mentor:'''
Leo Franchi (lfranchi AAAT kde DT org), or other Amarok developers. Contact at amarok@kde.org or #amarok on freenode.

----
====Project: Code regression test suite, implemented with QtScript ====
'''Brief explanation:'''
Amarok currently has no automatic code regression testing ("unit testing") in place at all. We very much need such a system in place (for as many components as possible), as we sometimes accidentally break certain components of the program by extending the code.

'''Expected results:'''
Code regression test suite for Amarok 2, implemented as one "Amarok-Script" (JavaScript), and internally split into multiple separate files and components, so that it would be possible to run arbitray tests (or the full suite) with very little effort, and no compiling, at any time. A requirement would also be testing of the collection scanning code (with test case collections), and testing of GUI correctness with the QTest library.

Also see:
http://amarok.kde.org/wiki/Development/Scripting_HowTo_2.0

A plus would be the generation of suitable statistics (possibly with document export), and possibly a visual representation of the data.

'''Material Prerequisite:'''
Amarok 2 trunk, KDE SVN account, git. Linux, OSX, or Windows.

'''Knowledge Prerequisite:'''
C++, Qt, KDE-Libs, QtScript (JavaScript), SVN, git, code testing.

'''Mentor:'''
Potentially one of several. Contact the amarok mailing list or ask in our IRC channel #amarok
----

====Project: Multilevel playlist sorting and sorting GUI ====
'''Brief explanation:'''
In Amarok 2.1, the layout of the playlist will be very configurable, being able to show as much or as little information about each track as each user might wish. Currently however, it is lacking an advanced system for sorting in the playlist, something that many users comming from Amarok 1 are missing. While simple sorting is relatively easy to do (and has already been partly implemented) we would like to aim a bit higher with Amarok 2.

'''Expected results:'''
A proxy model allowing the tracks in the playlist to be sorted using an arbitrary number of "layered" sort criteria. for instance, a sort setup could be "artist-album-tracknumber" This would sort all tracks by artist, then sort the tracks from each artist by album, and finally the tracks from each album based on track number. Once this model is working, a GUI is needed for making this functionality easilly avaialble to the user. Ideally this gui should tie in well with the playlist layout and search/filter stuff. Also, all track navigators (the classes that determines the order of playback, such as normal, random, random album and so on) need to be updated to use and work correctly with the new proxy model.

'''Material Prerequisite:'''
Amarok 2 trunk, KDE SVN account, Linux, OSX, or Windows.

'''Knowledge Prerequisite:'''
C++, Qt, KDE-Libs, SVN/git.

'''Mentor:'''
Nikolaj Hald Nielsen <nhnFreespirit@gmail.com> or contact the amarok mailing list or ask in our IRC channel #amarok
----

====Project: Playlist and Collection synchronization====
'''Brief explanation:'''
Mediadevices and services can add tracks and playlists to Amarok. Synchronization would automatically copy over tracks between the main Amarok Collection and devices or services or even between each other, either for a single playlist or the complete collection.
An algorithm needs to be implemented that does this automatically in a fast and efficient way with minimal intervention needed by the user.

'''Expected results:'''
Playlists set up on both the local collection and a portable mediaplayer will get synchronized the moment the player is connected.

'''Material Prerequisite:'''
Amarok 2 trunk, KDE SVN account, Linux, OSX, or Windows.

'''Knowledge Prerequisite:'''
C++, Qt, KDE-Libs, SVN/git.

'''Mentor:'''
Bart Cerneels <bart.cerneels at kde dot org> or contact the amarok mailing list or ask in our IRC channel #amarok

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

[http://phonon.kde.org Website] - [https://mail.kde.org/mailman/listinfo/phonon-backends Mailing list] - IRC channel: #phonon on Freenode.

====Project: Analyzer Support====
'''Brief explanation:'''
Applications such as Amarok and Dragon Player cannot have an analyzer or visualizations since they use Phonon which does not yet have the functionality to do it. The analyzer is the little bar graph thing which bounces around while music is playing. Users like it as its pretty and gives them a visual indication of their music playing.

'''Expected results:'''
As this project is working on extending a library, it has three parts: the Phonon library itself, a Phonon backend, and an application. The Phonon library would need the new API calls. At least phonon-xine and preferably 1 or 2 other Phonon backends must then implement the new API. An application like Amarok or Dragon Player should be used to demonstrate the use of the new API.

'''Knowledge Prerequisite:''' C++ and Qt. Experience with Xine or GStreamer is probably useful.

'''Mentor:''' Ian Monroe (contact on the [https://mail.kde.org/mailman/listinfo/amarok Amarok mailing list]) or possibly another Amarok or Phonon developer.
----
===Marble===
A desktop globe and map application. Also provides a map Qt Widget.

[http://edu.kde.org/marble/ Website] - [https://mail.kde.org/mailman/listinfo/marble-devel Mailing list]

====Project: Satellite navigation====
'''Brief explanation:'''
Satellite navigation devices have become widely used and the quality of openstreetmap data is becoming high, with some cities completely mapped already. Providing satellite navigation would be a useful desktop app for many as well as adding appeal for the use of KDE in embedded devices.

It also opens the possibility to bringing many of the free software ideals to interaction with the real world such as collaborative/social POIs.

'''Expected results:'''
The project would aim at getting a basic satellite navigation application running. The most basic features required would be getting the current location from a GPS device and providing route calculation to a destination.

The AndNav project (http://andnav.org) has already achieved something similar for Android so it could be a point of reference for how to use OpenStreetMap data to achieve this.

'''Knowledge Prerequisite:''' C++ and Qt. Experience with GPS devices under linux would be beneficial. Knowing java may also be of benefit in order to study the AndNav implementation.

'''Mentor:''' I (Alan Jones, skyphyr using gmail) am willing to mentor, but not having any GPS or Marble experience there is most likely somebody far more suited to undertake this role.

Comment from a Marble Project guy: Alan, please get in touch with the Marble Project. Our mailing list is marble-devel@kde.org. We'd like to support this project if a student is willing to do it.

----

====Project: Add Time support to 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 [http://code.google.com/apis/kml/documentation/kmlreference.html#timeprimitive <TimePrimitive>] and [http://code.google.com/apis/kml/documentation/kmlreference.html#timespan <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.

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

'''Mentor:''' Torsten Rahn / Patrick Spendrin.

----

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

[http://www.kdevelop.org Website] - [http://www.kdevelop.org/index.html?filename=mailinglist.html Mailing list] - IRC channel: #kdevelop on Freenode.

====Project: C++ Refactoring Support====
'''Brief explanation:'''
C++ support in KDevelop is already highly advanced, often equalling or surpassing what the user and compiler understand about the code. A few refactoring tools have been developed already, but they have been constructed in a crude fashion, generating code via string concatenation.

This project would aim to create a new system to implement refactoring tools, and to create, test and deploy several advanced refactoring tools for c++.

'''Expected results:'''
A library would be created to enable refactoring based on the c++ AST (abstract syntax tree). A reverse parser (AST to code) already exists, but classes would be created to allow programatic manipulation of an AST. Optionally this library would also cover a generic framework based on the duchain which would be re-usable by other languages and make refactoring plugins easier to develop and partially shareable between languages.

See the [http://api.kde.org/4.x-api/kdevplatform-apidocs/language/codegen/html/index.html Code Generation Design] documents for the initial plan for this project.

'''Knowledge Prerequisite:''' C++ and Qt. Experience with parsers would be a bonus.

'''Mentor:''' Hamish Rodda (Definition-Use chain code creator) rodda at kde/dot/org, possibly also David Nolden (DUChain guru)(to be confirmed)
----
=== KStars ===
KStars is a Desktop Planetarium for KDE. It displays a map of the sky and provides a lot of tools to learn astronomy, or to calculate and predict astronomical phenomena. See [[http://edu.kde.org/kstars|The KStars Homepage]] for more information.

==== Project: Community Integration for KStars ====
'''Project Information:''' KStars is a desktop planetarium program for KDE.

'''Brief explanation:''' Amateur Astronomy (which is one of the important use-cases of KStars) is typically done in communities. KStars permits users to save their own observing logs. It would be nicer if the user could share his observing logs with other users and see other observers' logs within KStars. It would also be nice if KStars had a map (using MarbleWidget) to display various Astronomy-related establishments (like amateur associations, observatories, research institutes). Another possible idea could be an observing report generator that would generate a report based on observing logs, and at the user's will, share it / post it on the internet.

'''Expected results:''' Implement some features that will make it easier for users to collaborate, as suggested above.

'''Knowledge Pre-Requisite:''' Required: C++. Prior knowledge of KIO_HTTP will help.

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

==== Project: FITS Image Overlay on the sky map. ====

'''Project Information:''' KStars is a desktop planetarium program for KDE.

'''Brief explanation:''' It would be great if a FITS image could be overlayed on the sky map so that the field drawn by KStars could be compared with the field in the FITS image. This would be of great benefit to observational astronomers, astrophotographers and comet / asteroid observers. An extension would be to download a DSS image using KStars' already existing tool and map it onto the sky map. The support of shapes like ds9 region, annotations on the sky, etc. could also be added.

'''Expected results:''' Functionality to overlay a FITS image or a DSS image obtained through KStars on to the sky map.

'''Knowledge Pre-Requisite:''' Required: C++. Prior knowledge of the FITS format and cfitsio library will help.

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

==== Project: Tools for Eclipses ====

'''Project Information:''' KStars is a desktop planetarium program for KDE. Currently, it can predict Solar Eclipses (using the Conjunctions tool), but cannot plot trajectory of shadows, or predict Lunar Eclipses.

'''Brief explanation:''' The project's primary goals are to include simulation and prediction (maybe using the existing Conjunction backend) of Lunar eclipses, and to create a tool to mark the trajectories of Solar and Lunar eclipse shadows on a map of the earth, including marking of totality, partial eclipse and annular eclipse. Something similar to this: [http://eclipse.gsfc.nasa.gov/SEmono/TSE2009/TSE2009iau/TSE2009-fig01.GIF]

'''Expected results:''' A complete set of tools to deal with eclipses.

'''Knowledge Pre-Requisite:''' C++

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

==== Project: KStars: Prettyfication ====
'''Project Information:''' KStars is a desktop planetarium program for KDE. The display is interactive, but it could be made more beautiful.

'''Brief explanation:''' We often get good suggestions for making KStars look better. Choose any of the following ideas: realistic rendering of asteroids and comets (including tails!); texture-mapping of the sky (this would mostly allow a photorealistic Milky Way); texture-mapping of planets; realistic sky-lighting effects (i.e., sky is blue in the daytime, gets gradually darker and colorful at sunset). One could also think of using Qt-GL rendering optionally.

'''Expected results:''' Successful implementation of any of these ideas to make KStars more beautiful.

'''Knowledge Pre-Requisite:''' Required: C++.

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

==== Project: Printable star charts ====
'''Project Information:''' KStars is a desktop planetarium program for KDE. It already has a print feature, but the printed chart could be much better.

'''Brief explanation:''' A printed star chart should at least include a legend explaining the symbols, and provide some information on the location of the user, the time and date, etc. The user would ideally be able to annotate the chart in various ways.

'''Expected results:''' Significant improvements to the printed star charts in KStars.

'''Knowledge Pre-Requisite:''' Basic programming skills, ability to quickly learn QPainter API.

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

==== Project: Many Moons ====
'''Project Information:''' KStars is a desktop planetarium program for KDE. It currently includes Earth's moon and 4 of Jupiter's moons.

'''Brief explanation:''' Generalize the JupiterMoons class to encapsulate any planet's Moons. The project will require some research to identify a public source of orbital data for planetary moons, most likely from a NASA webpage.

'''Expected results:''' Implement moons for at least Mars, Jupiter, Saturn, and Pluto with the new system.

'''Knowledge Pre-Requisite:''' Required: C++. The project doesn't require much contact with Qt/KDE APIs, and the existing JupiterMoons class can be used as a template.

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

==== Project: Support many catalogs ====
'''Project Information:''' KStars is a Desktop Planetarium for KDE. Currently KStars loads some star catalogs that are made available in a KStars native format.

'''Brief Explanation:''' KStars currently loads Tycho-2 and parts of USNO NOMAD catalog of stars. These catalogs are required to be in KStars' native format which uses the Hirearcheal Triangular Mesh to index regions in the sky. Popular star catalogs like USNO A organize stars and divide the sky into regions differently. Most users of astronomy software typically have one of these popular catalogs downloaded, and it would be great if KStars could support them somehow. While ability to read the non-native catalogs straight off is desirable, tools to convert these catalogs into KStars' native format would also help.

'''Expected Results:''' Implement support for at least the most popular catalogs like USNO-A2.0, Stellarium's Extra catalog, Cartes du Ciel's Tycho and Tycho-2 catalogs.

'''Knowledge Pre-Requisite:''' Required: C++. Ability to read documentation and quickly understand the existing code and ability to deal with binary files will help.

=== Kalzium ===

==== Project: Strigi integration ====

'''Project Information:'''
The goal of this project is to integrate Strigi as backend behind the periodic table and the glossary (and possible other elements).

'''Brief explanation:'''
The idea here is to have a GUI element that shows Strigi search results based on the element selected from the periodic table, or the item from the glossary, found on the users desktop. For element, this would include the elements name, and possible even the element symbol, if integration with last years Strigi-Chemistry GSoC project is achieved. For glossary items, a simple text search would suffice.

Another idea is to make it possible to querry like this: "Give me all molecules with a molecularweigth of 123u and at least one Carbon atom". For this we can use the [http://chem-file.sourceforge.net/ Chemical File Database] (or of course every other database, even those for [http://www.rcsb.org/pdb/home/home.do proteins].

'''Expected results:'''
* provide GUI for Strigi search results for an element selected in the periodic table
* provide GUI for Strigi search results for an glossary item

'''Knowledge Pre-Requisite:''' Required: C++, DBUS. Could be useful: Qt.

'''Mentor:''' Undecided.

----

==== Project: Kalzium beautification ====

'''Project Information:'''
Many parts of [http://edu.kde.org/kalzium Kalzium] could need a fresh up of the interface. For example, the main table should be written using Qt Model/View technique and for example use SVGs as a background. A first (uncomplete but working) code is already existing.

At the same time, many dialogs are not as beautiful as they could be. This project could also include the creation of a "simplified Kalzium" mode in which some parts of the feature set are hidden; this would be good for schools.

A third idea is to make more use of Plasma, for example improve the already written Plasmoids and/or extent Kalzium so that a Plasmoid could open a information dialog using Kalzium.

'''Expected results:'''
Depending on the chosen project for example a cleaned up codebase with an improved interface.

'''Knowledge Pre-Requisite:''' Required: C++, Qt, possible Plasma, Debug.

'''Mentor:''' Carsten Niehaus

=== KOffice ===
-----

'''Project:''' support for versionned OpenDocument files.

'''Explanation:''' The OpenDocument specification doesn't include support for multiple versions of the same document in a single file. But that feature is supported by OpenOffice.org. The objective for this Summer of Code is to add support for that versionning system in KOffice. Since KOffice shares the OpenDocument loading/saving code, it should be possible to add this support in every KOffice application in one Summer of Code.

'''Expected results:''' Being able to load a specific version of a file, and create/manage versions

'''Knowledge Pre-Requisite:''' C++, excellent english reading skills.

==== KWord ====
-----

==== KPresenter ====
-----

'''Project:''' Powerpoint import.

'''Explanation:''' From some years ago another gSoc project implemented the basis for powerpoint import, but it was never finished. So there is a good basis to start from. From a quick look it seems like styles support is the thing missing most to complete the work, however a thorough analysis of what is there and what is not needs to be done. And then the actual work needs to be done too, obviously

==== Krita ====

-----

'''Project:''' Sketch-pad interface for Krita

'''Project Information:''' Krita is a large and complex application built around a sophisticated painting engine. The goal of this project is to create a new interface around the Krita engine, specialized for quick sketching.

'''Expected results:''' This project should implement a new interface around Krita, presenting the user a single-layer plus tracing paper interface with a single freehand sketching tool. Easy to use and graphic color and paint operation (brush, pencil, eraser etc.) interface elements must be designed and implemented.

'''Knowledge Pre-Requisite:''' C++

-----

'''Project:''' Shader filters and generators for Krita

'''Project Information:''' Some initial work has already been done to make it possible to write filters in the OpenGL shading language. This project should take that initial code as a basis and implement a fully functioning plugin for Krita that allows filters and shaders to be executed on images in any colorspace.

'''Expected results:''' The plugin should have a finished user interface and make it possible to experiment with shader filters in an interactive way. Example filters must be implemented.

'''Knowledge Pre-Requisite:''' C++, OpenGL.

-----

'''Project:''' Animation support

'''Project Information:''' There is no support at all in Krita for animated images such as GIF or MNG or for working with images in an animation context, such as textures or backgrounds in applications like Blender. The applicant should first investigate user needs and use cases and then implement support in the user interface and in the import/export filters.

'''Expected results:''' A user-friendly way of working with animated images (i.e., not by making each frame a layer), but e.g. a docker that shows the the animation running in thumbnail format. Import/export filters for relevant file formats.

'''Knowledge Pre-Requisite:''' C++

-----

'''Project:''' PSD and Gimp plugins

'''Project Information:''' Krita is powerful enough to handle nearly all that the Gimp and Photoshop are capable of saving. This project is about creating dedicated file import/export filters that can handle as much of these file formats as possible, possibly through the use of existing libraries.

'''Expected results:''' 4 plugins: psd import/export and xcf import/export. These plugins should be able to handle complex files in all supported colorspaces. Ideally the project would also deliver a library to convert PSD/XF to/from Open Raster files.

'''Knowledge Pre-Requisite:''' C++

-----

'''Project:''' Workspaces

'''Project Information:''' A workspace is a loadable package of settings that finetune Krita for a particular purpose. A workspace could contain additional plugins (like an image browser plugin for batch operations) and a subset of resources. Example workspaces could be batch-editing of images, editing of animation sequences or painting or sketching.

'''Expected results:''' the user interface and framework to make packages of plugins and resources that users can switch between. Also extra plugins to extend krita in areas like batch processing that do not exist yet.

'''Knowledge Pre-Requisite:''' C++, artistic workflow

-----

'''Project:''' Kipi and digikam plugins compatibility

'''Project Information:''' Kipi and digikam provide lots of interesting plugins for working with 8 and 16 bit RGBA images. It would be great to be able to re-use those plugins from within Krita.

'''Expected results:''' Two plugins that load kipi and digikam filters into two new menus in the filter menu. Code to convert Krita layers to the digikam image representation and back, taking care of icc profiles and other niceties.

'''Knowledge Pre-Requisite:''' C++, artistic workflow

===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 [http://www.akonadi-project.org/ Akonadi].

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

[http://pim.kde.org/ Website] - [http://techbase.kde.org/Projects/PIM Project Wiki] - [https://mail.kde.org/mailman/listinfo/kde-pim Mailing list] - IRC channel: #kontact and #akonadi on Freenode.

====Project: Akonadi Janitor Agent====
'''Brief explanation:'''
An [[Development/Architecture/KDE4/Akonadi#Akonadi_Agents|Akonadi Agent]] is a service process for performing tasks on data provided through the Akonadi server.

The task of a Janitor agent would be to keep the user's PIM data neatly organized, for example deleting news feed items which are above a certain age and not flagged, moving last week's mail to an archive, etc.

'''Expected results:'''
* An Akonadi Agent capable of managing actions on Akonadi collections triggered by various criteria
* At least fully working implementation of actions based on "Expire" criterias for mail, e.g. delete mail above certain age, move/copy to different collection, etc
* GUI for configuring actions and their trigger criteria.

'''Knowledge Prerequisite:''' C++ and Qt. Ideally would already have gone through the [[Development/Tutorials/Akonadi/Resources|Akonadi Resource Tutorial]] since Resources are a specialized form of agents and thus share some of the API and characteristics.

'''Mentor:''' Kevin Krammer (kevin dot krammer at gmx dot at)
----
====Project: Alternative Akonadi Client Library====
'''Brief explanation:'''
Akonadi has a server/client like architecture where clients such as applications (but also resource) connect to a service and communicate with it through a suitable protocol.

Currently this is implemented for KDE in library called libakonadi-kde, however it is desirable to have additional implementations to be suitable for other library stacks, e.g. GLib/GObject based ones.

'''Expected results:'''
* A non-KDE based, preferably GLib/GObject based, Akonadi client library which
** can connect to a running Akonadi server
** fetch Akonadi collections
** fetch Akonadi items
** receive Akonadi change notifications (D-Bus based)

* A set of demo programs using the library which can
** recursively list (id and content MIME types) collections
** list (id and MIME type)oif items in a collection
** get the raw payload of an item

'''Knowledge Prerequisite:''' Depends on the chosen language and toolstack, e.g. C/Vala and GLib/GObject knowledge for a GLib/GObject based implementation.

'''Mentor:'''
----
====Project: Akonadi Consistency Checker====
'''Brief explanation:'''
Akonadi provides a structure of collections and items, similar to folders and files of a filesystem. Similarly the internal structures have to follow certain constraints which must not be violated. Nevertheless, this can happen as result of bugs, hardware failures, power loss and a million other reasons.

Filesystem checks exist to detect and possibly fix such situations. Such functionality would also be desirable for Akonadi.

'''Expected results:'''
* A consistency checker (built into the Akonadi server or stand-alone) that performs an extensible set of checks on the internal data structures of the Akonadi server, such as:
** items belong to existing collections
** collections are child collections of existing collections
** the collection tree is non-cyclic
** every collections is owned by an existing resource
** collection sub-trees are owned by the same resource
** every item payload part belongs to an existing item
** content type constraints of collections are not violated
** ...
* each check should be accompanied with recovery code, such as moving orphaned items into a lost+found folder
* integration into Akonadiconsole
* integration into unit-tests

'''Knowledge Prerequisite:''' C++ and Qt mandatory, SQL/database knowledge would be useful.

'''Mentor:''' Volker Krause <vkrause@kde.org>
----
====Project: Akonadi Resource for KMail local folders====
'''Brief explanation:'''
KMail stores its mail in a folder hierachy where each folder can contain mails '''and''' further sub folders.

While mails are stored either as mbox or maildir, additional index files are used to speed up message listing and to store message status and flags.

The already existing Akonadi MailDir resource can handle the maildir aspects but cannot handle either mbox based folders nor the additional information stored in the index files.

'''Expected results:'''
* a set of classes, probably as a library, capable of
** recursively listing the KMail folder tree given a base directory
** reading mails from the mbox and maildir folders in the KMail folder tree
** reading KMail index files
* an Akonadi resource using these classes to provide read-only access to all mails currently handled by KMail. The resource should also be able to transfer the flags stored in KMail's index file to Akonadi.
* Writing a migrator, similar to the current KResource->Akonadi migrator, that automatically reads the KMail config file and creates a Akonadi resource out of it. Optionally, depending on the overall progress, the migrator would also convert some of KMail's folder settings, like the folder icon or the expiry settings, to Akonadi collection attributes.

'''Knowledge Prerequisite:''' C++ and Qt mandatory, code analysis skills would be helpful regarding the handling of index files, refactoring skills if KMail's classes are to be extracted from KMail's code base (not required).

'''Mentor:''' Thomas McGuire <mcguire at kde dot org>
----

===KDE on Windows===
====Solid API backend====
'''Brief explanation:'''
The porting efforts to make KDE available across platforms do need some backends for system dependent tasks. One of the KDE libraries that bundles this is Solid.

'''Expected results:'''
You implement a backend for the [http://solid.kde.org Solid API] using WINAPI.
It has to work with both MinGW and MSVC compilers. Not every function is required, but the basic functionality (network access, removable drives/harddisks and power) should be implemented.

'''Knowledge Prerequisite:''' Windows API and C++/Qt. You should be able to set up the [http://techbase.kde.org/Getting_Started/Build/KDE4/Windows development environment] yourself and be familiar with it.

'''Mentor:''' Carlo Segato (brandon dot ml at gmail dot com) or Patrick Spendrin (ps_ml at gmx dot de)
----

===KDE Games===
====Project: Kolf 2 landscape object====
'''Brief explanation:'''
Kolf 2 is the second incarnation of KDE's minigolf game. We are currently rewriting it from scratch to take advantage of the powerful technologies provided by Qt 4 and KDE 4.

'''Expected results:'''
The task in this project is to create an object (or multiple objects) that provide(s) landscape textures, slopes, puddles and sand bunkers.

If you finish this task before the end of the summer, you can fill the remaining time by porting as much game objects from Kolf 1 to Kolf 2 as possible (e.g. windmills, floating blocks, signs or bumpers).

'''Knowledge Prerequisite:''' C++/Qt. Experiences in graphics programming with Qt will definitely help, as you are expected to implement 2D rendering for the landscape object.

'''Mentor:''' Stefan Majewsky (majewsky at gmx dot net) – Please contact me to let me help you to improve your proposal.

====Project: Kolf 2 editor interface====
'''Brief explanation:'''
The minigolf game Kolf provided an editor interface from the beginning, to allow the users to create custom courses. For Kolf 2, we are rewriting the game engine and can therefore not use the old editor code.

'''Expected results:'''
Your task would be to create an editor interface (may be embedded in the game, or a standalone application). A few basic parts are available, and the Kolf 2 engine supports generic methods to provide data to editor interfaces, and display editor overlays on the game view.

If you finish the editor interface before the end of the summer, you can fill the remaining time by porting as much game objects from Kolf 1 to Kolf 2 as possible (e.g. windmills, floating blocks, signs or bumpers).

'''Knowledge Prerequisite:''' C++/Qt. Experiences in model/view programming with Qt will be of good use.

'''Mentor:''' Stefan Majewsky (majewsky at gmx dot net) – Please contact me to let me help you to improve your proposal.

----

===Solid===
====Project: UPnP support through Jolie====
'''Brief explanation:'''
Adding UPnP support to Solid would mean offering transparent UPnP support to every KDE application using the Solid API, keeping them clean from every UPnP implementation aspect.
At the present, the [http://www.jolie-lang.org/ Jolie language] is being integrated with Plasma by means of the [http://websvn.kde.org/branches/work/~ervin/sodep/ QtSodep] library, soon to offer higher levels of abstraction.

The aim of this project would be to implement a UPnP protocol for Jolie, so that Solid could re-use the integration being made with QtSodep and gain UPnP support without having to worry about implementation details. Having a UPnP protocol implementation in Jolie would have other considerable consequences, like the possibility to act easily as a UPnP server or to compose and export existing UPnP services.

'''Expected results:'''
*The creation of a "upnp" protocol in Jolie, supporting at least the Internet Gateway Device (IGD) and MediaServer profiles.
*The creation of a UPnP Jolie service for UPnP service discovery and monitoring.
*Extending libsolid to expose UPnP devices found on the network.

'''Material Prerequisite:''' Having UPnP devices or software applications to test with. Most home routers support IGD, and there exists free software supporting the MediaServer profile ([http://mediatomb.cc/ mediatomb]).

'''Knowledge Prerequisite:''' Understanding of the UPnP specifications, Java (for the development of the Jolie UPnP protocol) and basic knowledge of the Jolie language.

'''Mentors:''' ervin (ervin at kde dot org) fmontesi (famontesi at gmail dot com)
----

===KWin===

KDE's window manager

[http://techbase.kde.org/Projects/KWin Techbase page] - [https://mail.kde.org/mailman/listinfo/kwin Mailinglist] - IRC channel: #kwin on Freenode.

====Project: Window tabbing====

'''Brief explanation:'''
Window tabbing is a feature that allows you to group multiple application windows together to cover the same space. It is identical to what is already available in any modern web browser except it applies the the window as a whole. Window managers that have this feature available include Fluxbox and Ion. This feature was [http://bugs.kde.org/show_bug.cgi?id=42023 originally requested] in 2002.

'''Knowledge Prerequisite:''' C++ and Qt. Understanding of the X window system and Xlib is a benefit but not required.

'''Mentors:''' Lucas Murray (lmurray undefinedfire com)

====Project: Window tiling====

'''Brief explanation:'''
Window tiling is a technique of displaying application windows side-by-side without overlap. The position, size and layout of the windows can either be specified by the user or determined automatically to best fit the screen. Examples of existing tiling window managers include Awesome, XMonad, Ion and Ratpoison. One of the main advantages of tiling is that is makes application windows easy to navigate solely by the keyboard. This feature was [http://bugs.kde.org/show_bug.cgi?id=59338 originally requested] in 2003.

'''Expected results:'''
* Users should be able tile existing floating windows on-the-fly with simple keyboard shortcuts or mouse gestures.
* It should also be possible to run the entire desktop environment entirely in tiled mode (Enabled by configuration settings). In this mode new window would be added to the tiling grid by default yet can be removed by the user if required.
* The final tiling system should not interfere in any way with the existing floating window management.

'''Knowledge Prerequisite:''' C++ and Qt. Understanding of the X window system and Xlib is a benefit but not required.

'''Mentors:''' Lucas Murray (lmurray undefinedfire com)

----

=== digiKam ===

Photo Management program

[http://www.digikam.org digiKam project web site] - [https://mail.kde.org/mailman/listinfo/digikam-devel Mailinglist] - IRC channel: #digikam on Freenode.

====Project: High Dynamic Range (HDR) plugin====

'''Project Information:''' digiKam is an advanced digital photo management application for KDE, which makes importing and organizing digital photos a "snap". The photos are organized in albums which can be sorted chronologically, by folder layout or by custom collections. digiKam has an Image Editor which has its own plugin subsystem with some common tools e.g. red eye correction or Gamma correction. Additional plugins are provided with the main application to process advanced corrections on image like color management, noise reduction, or special effects. digiKam image editor support 16 bits color depth image internally. The goal of this project is to create a new plugin dedicated to create [http://en.wikipedia.org/wiki/High_dynamic_range_imaging HDR image].

'''Expected results:''' This project should implement an HDR tool will mix two or more (nearly) identical images having different exposure into a new image representing a wider dynamic range, which is closer to human perception of a photographic scene. [http://en.wikipedia.org/wiki/Tone_mapping Tone-mapping method] must be used to create HDR images. An open-source implementation is already available at [http://zynaddsubfx.sourceforge.net/other/tonemapping this url] and can be re-used as well. There is an old [https://bugs.kde.org/show_bug.cgi?id=144593 feature request].

'''Knowledge Pre-Requisite:''' C++/Qt.

'''Mentors:''' Gilles Caulier (caulier dot gilles at gmail dot com)

----

===KDE Telepathy Integration===
The [http://telepathy.freedesktop.org Telepathy Framework] is a desktop independent framework for real-time communication, such as VoIP and Instant Messaging. The projects below are some ideas for integrating telepathy into KDE.

If you want to know any more about Telepathy and KDE, drop by the irc channel #decibel and talk to '''grundleborg''', or use the mailing list decibel AT kde DOT org.

====Project: Message Logging====

'''Project Information:''' The Telepathy Framework allows for components which can watch channels whilst a user is interacting with them through another application. A program could be created to log the content of text instant messages into an Akonadi collection.

'''Expected results:''' This project should result in a telepathy watcher which is capable of logging the contents of text chats into an Akonadi collection. It should be possible to go off-the-record in a particular conversation from telepathy user interfaces and the logger should not save any messages in this situation. This project might also include modifying the Kopete logging plugin to use the same akonadi collection for logs, and making a migration tool from Kopete's old logging format to the new Akonadi collection.

'''Knowledge Pre-Requisite:''' C++/Qt, some basic knowledge of the Telepathy Framework is an advantage, but not necessary if you have an interest in real-time communcation and are prepared to learn fast.

'''Mentors:''' George Goldberg (grundleborg at gmail dot com) IRC: grundleborg

====Project: Telepathy Integration to any KDE application====

'''Project Information:''' Provide some collaborative feature or instant messaging integration for your favourite KDE application.

'''Expected results:''' This project should result in a collaborative feature or instant messaging integration being added to the chosen KDE application. It should be complete enough to provide at least basic functionality to end users, with the possibility of further improvement after the summer of code period ends.

'''Knowledge Pre-Requisite:''' C++/Qt, some basic knowledge of the Telepathy Framework is an advantage, but not necessary if you have an interest in real-time communcation and are prepared to learn fast.

'''Mentors:''' George Goldberg (grundleborg at gmail dot com) IRC: grundleborg. You should also discuss your idea with the development team of the application in which you would like to provide a Telepathy feature.

====Project: Telepathy Plasma Integration====

'''Project Information:''' Provide integration of presence and buddy information into plasma.

'''Expected results:''' You should provide multiple points of integration between presence and contact information and plasma. Plasmoids allowing the display and manipulation of your own presence information should be made available, building on the plasma applets and datengines already in existance for presence information. Plasma activities could also be made aware of presence, and the contacts plasmoid could be made aware of your buddies from Telepathy instant messaging accounts.

'''Knowledge Pre-Requisite:''' C++/Qt

'''Mentors:''' George Goldberg (grundleborg at gmail dot com) IRC: grundleborg. You should also discuss your ideas with the plasma development team before making a proposal.

----

Projects/Summer of Code/2009/Ideas

2009-02-22T13:13:26Z

Grundleborg:

== 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 kde-devel@kde.org. See [http://www.kde.org/mailinglists/ 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==
===Plasma===
[http://plasma.kde.org Website] - [https://mail.kde.org/mailman/listinfo/panel-dev Mailing list] - IRC channel: #plasma on Freenode.

====Project: Generic SOAP Plasma::Service====
'''Brief explanation:'''
The Service should be able to parse WSDL files and let Plasmoids connect to the described Webservices.

====Project: Simple Media Center components====
'''Brief explanation:'''
Plasma could offer a Media center mode, where features a really simple ui to browse media files and plasmoids that shows the actual media. All should be operable with mouse, keyboard or a simple remote control. the work could consist in building the whole thing or just writing a plasmoid able to browse media files, that is the most important missing part.
Mockups for it by Nuno Pinheiro can be seen [http://img213.imageshack.us/img213/3200/image3231picturefz5.png here] and [http://img26.imageshack.us/img26/3407/image323musicoloectionck2.png here]

'''Expected results:'''
An applet to browse and thumbnail media files, like the first mockup and control the actual media viewing applets, like the media player applet or the picture frame applet. At this stage the functionality will be really minimum

'''Knowledge prerequisite:'''
Knowledge of C++ and some familiarity with Qt especially QGraphicsView related classes.

'''Mentor:'''
Marco Martin (notmart a gmail dot org), or other Plasma developers. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Plasmate====
'''Brief explanation:'''
PlasMate is an application that gives people a way to start creating scripted plasmoids without worrying about anything except making their bits. It hides the whole metadata.desktop thing, the package layout details, making a Plasmoid package (aka "zipping up the directory"), uploading content and version control system.

'''Expected results:'''
Working application that one can do the tasks described above, making it easy to create and distribute a scripted plasmoid.

'''Knowledge prerequisite:'''
Knowledge of C++ and familiarity with Qt (QWidgets and QGraphicsView related classes).

'''Mentor:'''
Artur Duque de Souza (morpheuz a gmail dot org), or other Plasma developers. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Qt Kinetic + Plasma====
'''Brief explanation:'''
A layer over Qt Kinetic to provide a standardized set of "out of the box"
animations and bring them into libplasma. The work will be done with the Plasma developers to make this API as efficient as possible. The work will be based on Kinetic, the next framework for animations in Qt.

'''Expected results:'''
We can kill Plasma::Animator class. The goal is to bring fancy effects/animations in Plasma to have one of the best desktop ever.

'''Knowledge prerequisite:'''
Knowledge of C++, familiarity with QGraphicsView related classes and some familiarity with animations bits.

'''Mentor:'''
Alexis Ménard (alexis.menard at nokia dot com) or Artur Duque de Souza (morpheuz a gmail dot org). Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Eduactional layout====
'''Brief explanation:'''
A set of Containments and Plasmoids specifically designed for primary school
students.

'''Expected results:'''
A simplified panel containment that contains basic launchers and user feedback
for the student, a widget that allows teachers to provide context-specific
sets of applications and documents to the student (context being a combination
of the student logged in and the current class subject), a widget that
provides some basic teacher->student communication and status (e.g. what the
current assignment is, how long the student has been logged in, etc) and
optionally some widgets that work with KDE edu apps.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Desktop dock====
'''Brief explanation:'''
A MacOS style dock containment.

'''Expected results:'''
A containment that provides a similar user experience to the MacOS dock:
application launchers that are also task bar entries when the application is
active and a separate area for widgets such as the trash, battery, etc.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Kdm frontend using plasma====
'''Brief explanation:'''
A log-in screen layout manager for KDM that uses libplasma.

'''Expected results:'''
A KDM screen that is rendered completely using Plasma. This means both using
libplasma in KDM for the log in screen as well as writing Plasmoids for
entering the user name and password, listing users, session switching, etc.
Some of these widgets already exist for the desktop shell, so in some cases
this will be simply integrating existing Plasmoids, but in other cases will
mean writing new ones from the ground up.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Raptor====
'''Brief explanation:'''
Raptor aims to deliver a new kind of launch menu system for KDE. It is designed with usability and beauty in mind.
Raptor-Menu does not try to be the final answer to the menu question, instead aspires to be the best answer we can give, merging many ideas form modern desktop launch menus.

'''Expected results:'''
http://www.raptor-menu.org/

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: New Widget Explorer====
'''Brief explanation:'''
A new widget explorer that supports both our own widgets as well as others
more seamlessly.

'''Expected results:'''
A usable and pretty browser for widgets that allows a user to see an icon or
snapshot of the widget, select a widget to be placed in a containment, search
for a widget based on name/description, sort the widgets into categories, rate
widgets and provide ways to launch the online browsers and installers for both
native Plasmoids as well as third party tools such as Google Gadgets (which is
already supported in the Package class). All the required support
functionality already exists, this project is really about creating a
beautiful and dynamic user interface for looking through a widget catalog that
looks "Plasma".

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: D-Bus Interface====
'''Brief explanation:'''
A comprehensive set of D-Bus interfaces for the plasma-desktop Plasma shell.

'''Expected results:'''
The D-Bus interface must provide access to the Corona (DestkopCorona class),
which in turn will list all existing Containments and allow Containments to be
added, removed, saved, etc.

A D-Bus interface for each existing Containment will be made available as
well, which will provide a standard set of tools including listing, adding and
removing widgets as well as positioning and sizing for PanelContaiments. Ways
to control the wallpaper, if any, will also be provided in the per-Containment
D-Bus interface.

In turn, a D-Bus interface for each widget representing its available
contextual actions will be provided dynamically upon request.

Finally, the application D-Bus interface for things such as locking/unlocking
widgets will be designed and implemented.

The result will be a Plasma that is fully accessible via D-Bus.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Security====
'''Brief explanation:'''
A set of methods to define the existing security state of the Plasma
application, the security requirements of individual widgets, mechanisms to
respect those two sets of information and cryptographic signing of Plasmoid
packages.

'''Expected results:'''
A set of functionality descriptions will be enumerated (e.g. "Network access",
"Local file system access", etc.). Individual widgets will advertise which of
these functionality sets they require.

The plasma-overlay shell (used on the screensaver) will have code added to it
to respect these settings and not run widgets that advertise they need things
that aren't safe to provide on a screensaver (due to it being locked to
prevent others from accessing the system).

The plasma-desktop shell will gain the ability to be put into various lock down
states which will map to different sets of functionality. Part of this project
will be enumerate the various states, but that list must include "only load
trusted widgets", "no external access", "no local file system access".

The JavaScript engine will provide methods for each of the functionality sets
(e.g. a set of functions to access local files) which will be exported or not
based on the current Security state. This implies providing a security state
to the Corona which can then be passed on down to Applets and AppletScripts.

Finally, GPG signing of Plasmoid packages will be implemented along with a way
of checking the validity of these at runtime.

'''Knowledge prerequisite:'''
Knowledge of C++ and some experience with security.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

===Amarok===
A KDE music manager and player.

[http://amarok.kde.org Website] - [https://mail.kde.org/mailman/listinfo/amarok Mailing list] - IRC channel: #amarok on Freenode.

====Project: DLNA/UPnP Support====
'''Brief explanation:'''
Using the UPnP protocol users can, for example, share music from their Vista computer to a PS3. Amarok lacks any sort of UPnP support. Being able to act as a client or possibly a UPnP media server would be useful. In addition to that controlling a UPnP Media Renderer from within Amarok is possible with framework support.

The [http://coherence.beebits.net/ Coherence server] would likely be used since it is also intended to be used by a KIO slave.

'''Expected results:'''
*Using the Amarok Collection framework, create a plugin which allows Amarok to browse, search and play music off of a UPnP share. Playing music may use the UPnP KIO-slave, but more advanced functionality requires Amarok to handle this directly.
*Allow Amarok to share it's collection with other devices or control other devices via UPnP. This is secondary priority but it may be pretty easy with Coherence.
*Control UPnP Media Renderers (DMR: Digital Media Renderer device class in DLNA) from within Amarok.

'''Material Prerequisite:''' Some UPnP devices or computers to test with. Good excuse to buy a PS3. If you live in Europe a Philips Streamium DMR can be borrowed.

'''Knowledge Prerequisite:''' C++ and Qt. Coherence uses Python and D-Bus but doesn't need to be hacked on in the scope of this project.

And of course, understanding of UPnP networking and devices wouldn't hurt!

'''Mentor:''' Stecchino (bart.cerneels at kde dot org)
----

====Project: New meta-applets for the Context View====
'''Brief Explanation:'''
The Context View (CV) is currently used to display multiple applets that expose various information. However, due to the fact that each applet displays a certain type of information from one data source, there is significant amount of wasted space, and it is hard to show much more than 3 different pieces of data at once.

Meta-Applets are large applets that integrate date from multiple data sources in order to display more semantically related information coherently and efficiently. This could mean, for example, an applet that brings together lyrics, artist info, upcoming concerts, and related songs/artists.

More info is available here [http://amarok.kde.org/wiki/Proposals/More_Contexual_Information on the amarok wiki]

'''Expected Results:'''
Two or three (to be discussed with mentor in application writing process) applets that elegantly execute the ideas discussed above.

'''Knowledge prerequisite:'''
Knowledge of C++ is required, and some familiarity with Qt is helpful (especially QGraphicsView) but not necessary.

'''Mentor:'''
Leo Franchi (lfranchi AAAT kde DT org), or other Amarok developers. Contact at amarok@kde.org or #amarok on freenode.

----
====Project: Code regression test suite, implemented with QtScript ====
'''Brief explanation:'''
Amarok currently has no automatic code regression testing ("unit testing") in place at all. We very much need such a system in place (for as many components as possible), as we sometimes accidentally break certain components of the program by extending the code.

'''Expected results:'''
Code regression test suite for Amarok 2, implemented as one "Amarok-Script" (JavaScript), and internally split into multiple separate files and components, so that it would be possible to run arbitray tests (or the full suite) with very little effort, and no compiling, at any time. A requirement would also be testing of the collection scanning code (with test case collections), and testing of GUI correctness with the QTest library.

Also see:
http://amarok.kde.org/wiki/Development/Scripting_HowTo_2.0

A plus would be the generation of suitable statistics (possibly with document export), and possibly a visual representation of the data.

'''Material Prerequisite:'''
Amarok 2 trunk, KDE SVN account, git. Linux, OSX, or Windows.

'''Knowledge Prerequisite:'''
C++, Qt, KDE-Libs, QtScript (JavaScript), SVN, git, code testing.

'''Mentor:'''
Potentially one of several. Contact the amarok mailing list or ask in our IRC channel #amarok
----

====Project: Multilevel playlist sorting and sorting GUI ====
'''Brief explanation:'''
In Amarok 2.1, the layout of the playlist will be very configurable, being able to show as much or as little information about each track as each user might wish. Currently however, it is lacking an advanced system for sorting in the playlist, something that many users comming from Amarok 1 are missing. While simple sorting is relatively easy to do (and has already been partly implemented) we would like to aim a bit higher with Amarok 2.

'''Expected results:'''
A proxy model allowing the tracks in the playlist to be sorted using an arbitrary number of "layered" sort criteria. for instance, a sort setup could be "artist-album-tracknumber" This would sort all tracks by artist, then sort the tracks from each artist by album, and finally the tracks from each album based on track number. Once this model is working, a GUI is needed for making this functionality easilly avaialble to the user. Ideally this gui should tie in well with the playlist layout and search/filter stuff. Also, all track navigators (the classes that determines the order of playback, such as normal, random, random album and so on) need to be updated to use and work correctly with the new proxy model.

'''Material Prerequisite:'''
Amarok 2 trunk, KDE SVN account, Linux, OSX, or Windows.

'''Knowledge Prerequisite:'''
C++, Qt, KDE-Libs, SVN/git.

'''Mentor:'''
Nikolaj Hald Nielsen <nhnFreespirit@gmail.com> or contact the amarok mailing list or ask in our IRC channel #amarok
----

====Project: Playlist and Collection synchronization====
'''Brief explanation:'''
Mediadevices and services can add tracks and playlists to Amarok. Synchronization would automatically copy over tracks between the main Amarok Collection and devices or services or even between each other, either for a single playlist or the complete collection.
An algorithm needs to be implemented that does this automatically in a fast and efficient way with minimal intervention needed by the user.

'''Expected results:'''
Playlists set up on both the local collection and a portable mediaplayer will get synchronized the moment the player is connected.

'''Material Prerequisite:'''
Amarok 2 trunk, KDE SVN account, Linux, OSX, or Windows.

'''Knowledge Prerequisite:'''
C++, Qt, KDE-Libs, SVN/git.

'''Mentor:'''
Bart Cerneels <bart.cerneels at kde dot org> or contact the amarok mailing list or ask in our IRC channel #amarok

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

[http://phonon.kde.org Website] - [https://mail.kde.org/mailman/listinfo/phonon-backends Mailing list] - IRC channel: #phonon on Freenode.

====Project: Analyzer Support====
'''Brief explanation:'''
Applications such as Amarok and Dragon Player cannot have an analyzer or visualizations since they use Phonon which does not yet have the functionality to do it. The analyzer is the little bar graph thing which bounces around while music is playing. Users like it as its pretty and gives them a visual indication of their music playing.

'''Expected results:'''
As this project is working on extending a library, it has three parts: the Phonon library itself, a Phonon backend, and an application. The Phonon library would need the new API calls. At least phonon-xine and preferably 1 or 2 other Phonon backends must then implement the new API. An application like Amarok or Dragon Player should be used to demonstrate the use of the new API.

'''Knowledge Prerequisite:''' C++ and Qt. Experience with Xine or GStreamer is probably useful.

'''Mentor:''' Ian Monroe (contact on the [https://mail.kde.org/mailman/listinfo/amarok Amarok mailing list]) or possibly another Amarok or Phonon developer.
----
===Marble===
A desktop globe and map application. Also provides a map Qt Widget.

[http://edu.kde.org/marble/ Website] - [https://mail.kde.org/mailman/listinfo/marble-devel Mailing list]

====Project: Satellite navigation====
'''Brief explanation:'''
Satellite navigation devices have become widely used and the quality of openstreetmap data is becoming high, with some cities completely mapped already. Providing satellite navigation would be a useful desktop app for many as well as adding appeal for the use of KDE in embedded devices.

It also opens the possibility to bringing many of the free software ideals to interaction with the real world such as collaborative/social POIs.

'''Expected results:'''
The project would aim at getting a basic satellite navigation application running. The most basic features required would be getting the current location from a GPS device and providing route calculation to a destination.

The AndNav project (http://andnav.org) has already achieved something similar for Android so it could be a point of reference for how to use OpenStreetMap data to achieve this.

'''Knowledge Prerequisite:''' C++ and Qt. Experience with GPS devices under linux would be beneficial. Knowing java may also be of benefit in order to study the AndNav implementation.

'''Mentor:''' I (Alan Jones, skyphyr using gmail) am willing to mentor, but not having any GPS or Marble experience there is most likely somebody far more suited to undertake this role.

Comment from a Marble Project guy: Alan, please get in touch with the Marble Project. Our mailing list is marble-devel@kde.org. We'd like to support this project if a student is willing to do it.

----

====Project: Add Time support to 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 [http://code.google.com/apis/kml/documentation/kmlreference.html#timeprimitive <TimePrimitive>] and [http://code.google.com/apis/kml/documentation/kmlreference.html#timespan <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.

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

'''Mentor:''' Torsten Rahn / Patrick Spendrin.

----

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

[http://www.kdevelop.org Website] - [http://www.kdevelop.org/index.html?filename=mailinglist.html Mailing list] - IRC channel: #kdevelop on Freenode.

====Project: C++ Refactoring Support====
'''Brief explanation:'''
C++ support in KDevelop is already highly advanced, often equalling or surpassing what the user and compiler understand about the code. A few refactoring tools have been developed already, but they have been constructed in a crude fashion, generating code via string concatenation.

This project would aim to create a new system to implement refactoring tools, and to create, test and deploy several advanced refactoring tools for c++.

'''Expected results:'''
A library would be created to enable refactoring based on the c++ AST (abstract syntax tree). A reverse parser (AST to code) already exists, but classes would be created to allow programatic manipulation of an AST. Optionally this library would also cover a generic framework based on the duchain which would be re-usable by other languages and make refactoring plugins easier to develop and partially shareable between languages.

See the [http://api.kde.org/4.x-api/kdevplatform-apidocs/language/codegen/html/index.html Code Generation Design] documents for the initial plan for this project.

'''Knowledge Prerequisite:''' C++ and Qt. Experience with parsers would be a bonus.

'''Mentor:''' Hamish Rodda (Definition-Use chain code creator) rodda at kde/dot/org, possibly also David Nolden (DUChain guru)(to be confirmed)
----
=== KStars ===
KStars is a Desktop Planetarium for KDE. It displays a map of the sky and provides a lot of tools to learn astronomy, or to calculate and predict astronomical phenomena. See [[http://edu.kde.org/kstars|The KStars Homepage]] for more information.

==== Project: Community Integration for KStars ====
'''Project Information:''' KStars is a desktop planetarium program for KDE.

'''Brief explanation:''' Amateur Astronomy (which is one of the important use-cases of KStars) is typically done in communities. KStars permits users to save their own observing logs. It would be nicer if the user could share his observing logs with other users and see other observers' logs within KStars. It would also be nice if KStars had a map (using MarbleWidget) to display various Astronomy-related establishments (like amateur associations, observatories, research institutes). Another possible idea could be an observing report generator that would generate a report based on observing logs, and at the user's will, share it / post it on the internet.

'''Expected results:''' Implement some features that will make it easier for users to collaborate, as suggested above.

'''Knowledge Pre-Requisite:''' Required: C++. Prior knowledge of KIO_HTTP will help.

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

==== Project: FITS Image Overlay on the sky map. ====

'''Project Information:''' KStars is a desktop planetarium program for KDE.

'''Brief explanation:''' It would be great if a FITS image could be overlayed on the sky map so that the field drawn by KStars could be compared with the field in the FITS image. This would be of great benefit to observational astronomers, astrophotographers and comet / asteroid observers. An extension would be to download a DSS image using KStars' already existing tool and map it onto the sky map. The support of shapes like ds9 region, annotations on the sky, etc. could also be added.

'''Expected results:''' Functionality to overlay a FITS image or a DSS image obtained through KStars on to the sky map.

'''Knowledge Pre-Requisite:''' Required: C++. Prior knowledge of the FITS format and cfitsio library will help.

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

==== Project: Tools for Eclipses ====

'''Project Information:''' KStars is a desktop planetarium program for KDE. Currently, it can predict Solar Eclipses (using the Conjunctions tool), but cannot plot trajectory of shadows, or predict Lunar Eclipses.

'''Brief explanation:''' The project's primary goals are to include simulation and prediction (maybe using the existing Conjunction backend) of Lunar eclipses, and to create a tool to mark the trajectories of Solar and Lunar eclipse shadows on a map of the earth, including marking of totality, partial eclipse and annular eclipse. Something similar to this: [http://eclipse.gsfc.nasa.gov/SEmono/TSE2009/TSE2009iau/TSE2009-fig01.GIF]

'''Expected results:''' A complete set of tools to deal with eclipses.

'''Knowledge Pre-Requisite:''' C++

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

==== Project: KStars: Prettyfication ====
'''Project Information:''' KStars is a desktop planetarium program for KDE. The display is interactive, but it could be made more beautiful.

'''Brief explanation:''' We often get good suggestions for making KStars look better. Choose any of the following ideas: realistic rendering of asteroids and comets (including tails!); texture-mapping of the sky (this would mostly allow a photorealistic Milky Way); texture-mapping of planets; realistic sky-lighting effects (i.e., sky is blue in the daytime, gets gradually darker and colorful at sunset). One could also think of using Qt-GL rendering optionally.

'''Expected results:''' Successful implementation of any of these ideas to make KStars more beautiful.

'''Knowledge Pre-Requisite:''' Required: C++.

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

==== Project: Printable star charts ====
'''Project Information:''' KStars is a desktop planetarium program for KDE. It already has a print feature, but the printed chart could be much better.

'''Brief explanation:''' A printed star chart should at least include a legend explaining the symbols, and provide some information on the location of the user, the time and date, etc. The user would ideally be able to annotate the chart in various ways.

'''Expected results:''' Significant improvements to the printed star charts in KStars.

'''Knowledge Pre-Requisite:''' Basic programming skills, ability to quickly learn QPainter API.

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

==== Project: Many Moons ====
'''Project Information:''' KStars is a desktop planetarium program for KDE. It currently includes Earth's moon and 4 of Jupiter's moons.

'''Brief explanation:''' Generalize the JupiterMoons class to encapsulate any planet's Moons. The project will require some research to identify a public source of orbital data for planetary moons, most likely from a NASA webpage.

'''Expected results:''' Implement moons for at least Mars, Jupiter, Saturn, and Pluto with the new system.

'''Knowledge Pre-Requisite:''' Required: C++. The project doesn't require much contact with Qt/KDE APIs, and the existing JupiterMoons class can be used as a template.

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

==== Project: Support many catalogs ====
'''Project Information:''' KStars is a Desktop Planetarium for KDE. Currently KStars loads some star catalogs that are made available in a KStars native format.

'''Brief Explanation:''' KStars currently loads Tycho-2 and parts of USNO NOMAD catalog of stars. These catalogs are required to be in KStars' native format which uses the Hirearcheal Triangular Mesh to index regions in the sky. Popular star catalogs like USNO A organize stars and divide the sky into regions differently. Most users of astronomy software typically have one of these popular catalogs downloaded, and it would be great if KStars could support them somehow. While ability to read the non-native catalogs straight off is desirable, tools to convert these catalogs into KStars' native format would also help.

'''Expected Results:''' Implement support for at least the most popular catalogs like USNO-A2.0, Stellarium's Extra catalog, Cartes du Ciel's Tycho and Tycho-2 catalogs.

'''Knowledge Pre-Requisite:''' Required: C++. Ability to read documentation and quickly understand the existing code and ability to deal with binary files will help.

=== Kalzium ===

==== Project: Strigi integration ====

'''Project Information:'''
The goal of this project is to integrate Strigi as backend behind the periodic table and the glossary (and possible other elements).

'''Brief explanation:'''
The idea here is to have a GUI element that shows Strigi search results based on the element selected from the periodic table, or the item from the glossary, found on the users desktop. For element, this would include the elements name, and possible even the element symbol, if integration with last years Strigi-Chemistry GSoC project is achieved. For glossary items, a simple text search would suffice.

Another idea is to make it possible to querry like this: "Give me all molecules with a molecularweigth of 123u and at least one Carbon atom". For this we can use the [http://chem-file.sourceforge.net/ Chemical File Database] (or of course every other database, even those for [http://www.rcsb.org/pdb/home/home.do proteins].

'''Expected results:'''
* provide GUI for Strigi search results for an element selected in the periodic table
* provide GUI for Strigi search results for an glossary item

'''Knowledge Pre-Requisite:''' Required: C++, DBUS. Could be useful: Qt.

'''Mentor:''' Undecided.

----

==== Project: Kalzium beautification ====

'''Project Information:'''
Many parts of [http://edu.kde.org/kalzium Kalzium] could need a fresh up of the interface. For example, the main table should be written using Qt Model/View technique and for example use SVGs as a background. A first (uncomplete but working) code is already existing.

At the same time, many dialogs are not as beautiful as they could be. This project could also include the creation of a "simplified Kalzium" mode in which some parts of the feature set are hidden; this would be good for schools.

A third idea is to make more use of Plasma, for example improve the already written Plasmoids and/or extent Kalzium so that a Plasmoid could open a information dialog using Kalzium.

'''Expected results:'''
Depending on the chosen project for example a cleaned up codebase with an improved interface.

'''Knowledge Pre-Requisite:''' Required: C++, Qt, possible Plasma, Debug.

'''Mentor:''' Carsten Niehaus

=== KOffice ===
-----

'''Project:''' support for versionned OpenDocument files.

'''Explanation:''' The OpenDocument specification doesn't include support for multiple versions of the same document in a single file. But that feature is supported by OpenOffice.org. The objective for this Summer of Code is to add support for that versionning system in KOffice. Since KOffice shares the OpenDocument loading/saving code, it should be possible to add this support in every KOffice application in one Summer of Code.

'''Expected results:''' Being able to load a specific version of a file, and create/manage versions

'''Knowledge Pre-Requisite:''' C++, excellent english reading skills.

==== KWord ====
-----

==== KPresenter ====
-----

'''Project:''' Powerpoint import.

'''Explanation:''' From some years ago another gSoc project implemented the basis for powerpoint import, but it was never finished. So there is a good basis to start from. From a quick look it seems like styles support is the thing missing most to complete the work, however a thorough analysis of what is there and what is not needs to be done. And then the actual work needs to be done too, obviously

==== Krita ====

-----

'''Project:''' Sketch-pad interface for Krita

'''Project Information:''' Krita is a large and complex application built around a sophisticated painting engine. The goal of this project is to create a new interface around the Krita engine, specialized for quick sketching.

'''Expected results:''' This project should implement a new interface around Krita, presenting the user a single-layer plus tracing paper interface with a single freehand sketching tool. Easy to use and graphic color and paint operation (brush, pencil, eraser etc.) interface elements must be designed and implemented.

'''Knowledge Pre-Requisite:''' C++

-----

'''Project:''' Shader filters and generators for Krita

'''Project Information:''' Some initial work has already been done to make it possible to write filters in the OpenGL shading language. This project should take that initial code as a basis and implement a fully functioning plugin for Krita that allows filters and shaders to be executed on images in any colorspace.

'''Expected results:''' The plugin should have a finished user interface and make it possible to experiment with shader filters in an interactive way. Example filters must be implemented.

'''Knowledge Pre-Requisite:''' C++, OpenGL.

-----

'''Project:''' Animation support

'''Project Information:''' There is no support at all in Krita for animated images such as GIF or MNG or for working with images in an animation context, such as textures or backgrounds in applications like Blender. The applicant should first investigate user needs and use cases and then implement support in the user interface and in the import/export filters.

'''Expected results:''' A user-friendly way of working with animated images (i.e., not by making each frame a layer), but e.g. a docker that shows the the animation running in thumbnail format. Import/export filters for relevant file formats.

'''Knowledge Pre-Requisite:''' C++

-----

'''Project:''' PSD and Gimp plugins

'''Project Information:''' Krita is powerful enough to handle nearly all that the Gimp and Photoshop are capable of saving. This project is about creating dedicated file import/export filters that can handle as much of these file formats as possible, possibly through the use of existing libraries.

'''Expected results:''' 4 plugins: psd import/export and xcf import/export. These plugins should be able to handle complex files in all supported colorspaces. Ideally the project would also deliver a library to convert PSD/XF to/from Open Raster files.

'''Knowledge Pre-Requisite:''' C++

-----

'''Project:''' Workspaces

'''Project Information:''' A workspace is a loadable package of settings that finetune Krita for a particular purpose. A workspace could contain additional plugins (like an image browser plugin for batch operations) and a subset of resources. Example workspaces could be batch-editing of images, editing of animation sequences or painting or sketching.

'''Expected results:''' the user interface and framework to make packages of plugins and resources that users can switch between. Also extra plugins to extend krita in areas like batch processing that do not exist yet.

'''Knowledge Pre-Requisite:''' C++, artistic workflow

-----

'''Project:''' Kipi and digikam plugins compatibility

'''Project Information:''' Kipi and digikam provide lots of interesting plugins for working with 8 and 16 bit RGBA images. It would be great to be able to re-use those plugins from within Krita.

'''Expected results:''' Two plugins that load kipi and digikam filters into two new menus in the filter menu. Code to convert Krita layers to the digikam image representation and back, taking care of icc profiles and other niceties.

'''Knowledge Pre-Requisite:''' C++, artistic workflow

===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 [http://www.akonadi-project.org/ Akonadi].

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

[http://pim.kde.org/ Website] - [http://techbase.kde.org/Projects/PIM Project Wiki] - [https://mail.kde.org/mailman/listinfo/kde-pim Mailing list] - IRC channel: #kontact and #akonadi on Freenode.

====Project: Akonadi Janitor Agent====
'''Brief explanation:'''
An [[Development/Architecture/KDE4/Akonadi#Akonadi_Agents|Akonadi Agent]] is a service process for performing tasks on data provided through the Akonadi server.

The task of a Janitor agent would be to keep the user's PIM data neatly organized, for example deleting news feed items which are above a certain age and not flagged, moving last week's mail to an archive, etc.

'''Expected results:'''
* An Akonadi Agent capable of managing actions on Akonadi collections triggered by various criteria
* At least fully working implementation of actions based on "Expire" criterias for mail, e.g. delete mail above certain age, move/copy to different collection, etc
* GUI for configuring actions and their trigger criteria.

'''Knowledge Prerequisite:''' C++ and Qt. Ideally would already have gone through the [[Development/Tutorials/Akonadi/Resources|Akonadi Resource Tutorial]] since Resources are a specialized form of agents and thus share some of the API and characteristics.

'''Mentor:''' Kevin Krammer (kevin dot krammer at gmx dot at)
----
====Project: Alternative Akonadi Client Library====
'''Brief explanation:'''
Akonadi has a server/client like architecture where clients such as applications (but also resource) connect to a service and communicate with it through a suitable protocol.

Currently this is implemented for KDE in library called libakonadi-kde, however it is desirable to have additional implementations to be suitable for other library stacks, e.g. GLib/GObject based ones.

'''Expected results:'''
* A non-KDE based, preferably GLib/GObject based, Akonadi client library which
** can connect to a running Akonadi server
** fetch Akonadi collections
** fetch Akonadi items
** receive Akonadi change notifications (D-Bus based)

* A set of demo programs using the library which can
** recursively list (id and content MIME types) collections
** list (id and MIME type)oif items in a collection
** get the raw payload of an item

'''Knowledge Prerequisite:''' Depends on the chosen language and toolstack, e.g. C/Vala and GLib/GObject knowledge for a GLib/GObject based implementation.

'''Mentor:'''
----
====Project: Akonadi Consistency Checker====
'''Brief explanation:'''
Akonadi provides a structure of collections and items, similar to folders and files of a filesystem. Similarly the internal structures have to follow certain constraints which must not be violated. Nevertheless, this can happen as result of bugs, hardware failures, power loss and a million other reasons.

Filesystem checks exist to detect and possibly fix such situations. Such functionality would also be desirable for Akonadi.

'''Expected results:'''
* A consistency checker (built into the Akonadi server or stand-alone) that performs an extensible set of checks on the internal data structures of the Akonadi server, such as:
** items belong to existing collections
** collections are child collections of existing collections
** the collection tree is non-cyclic
** every collections is owned by an existing resource
** collection sub-trees are owned by the same resource
** every item payload part belongs to an existing item
** content type constraints of collections are not violated
** ...
* each check should be accompanied with recovery code, such as moving orphaned items into a lost+found folder
* integration into Akonadiconsole
* integration into unit-tests

'''Knowledge Prerequisite:''' C++ and Qt mandatory, SQL/database knowledge would be useful.

'''Mentor:''' Volker Krause <vkrause@kde.org>
----
====Project: Akonadi Resource for KMail local folders====
'''Brief explanation:'''
KMail stores its mail in a folder hierachy where each folder can contain mails '''and''' further sub folders.

While mails are stored either as mbox or maildir, additional index files are used to speed up message listing and to store message status and flags.

The already existing Akonadi MailDir resource can handle the maildir aspects but cannot handle either mbox based folders nor the additional information stored in the index files.

'''Expected results:'''
* a set of classes, probably as a library, capable of
** recursively listing the KMail folder tree given a base directory
** reading mails from the mbox and maildir folders in the KMail folder tree
** reading KMail index files
* an Akonadi resource using these classes to provide read-only access to all mails currently handled by KMail. The resource should also be able to transfer the flags stored in KMail's index file to Akonadi.
* Writing a migrator, similar to the current KResource->Akonadi migrator, that automatically reads the KMail config file and creates a Akonadi resource out of it. Optionally, depending on the overall progress, the migrator would also convert some of KMail's folder settings, like the folder icon or the expiry settings, to Akonadi collection attributes.

'''Knowledge Prerequisite:''' C++ and Qt mandatory, code analysis skills would be helpful regarding the handling of index files, refactoring skills if KMail's classes are to be extracted from KMail's code base (not required).

'''Mentor:''' Thomas McGuire <mcguire at kde dot org>
----

===KDE on Windows===
====Solid API backend====
'''Brief explanation:'''
The porting efforts to make KDE available across platforms do need some backends for system dependent tasks. One of the KDE libraries that bundles this is Solid.

'''Expected results:'''
You implement a backend for the [http://solid.kde.org Solid API] using WINAPI.
It has to work with both MinGW and MSVC compilers. Not every function is required, but the basic functionality (network access, removable drives/harddisks and power) should be implemented.

'''Knowledge Prerequisite:''' Windows API and C++/Qt. You should be able to set up the [http://techbase.kde.org/Getting_Started/Build/KDE4/Windows development environment] yourself and be familiar with it.

'''Mentor:''' Carlo Segato (brandon dot ml at gmail dot com) or Patrick Spendrin (ps_ml at gmx dot de)
----

===KDE Games===
====Project: Kolf 2 landscape object====
'''Brief explanation:'''
Kolf 2 is the second incarnation of KDE's minigolf game. We are currently rewriting it from scratch to take advantage of the powerful technologies provided by Qt 4 and KDE 4.

'''Expected results:'''
The task in this project is to create an object (or multiple objects) that provide(s) landscape textures, slopes, puddles and sand bunkers.

If you finish this task before the end of the summer, you can fill the remaining time by porting as much game objects from Kolf 1 to Kolf 2 as possible (e.g. windmills, floating blocks, signs or bumpers).

'''Knowledge Prerequisite:''' C++/Qt. Experiences in graphics programming with Qt will definitely help, as you are expected to implement 2D rendering for the landscape object.

'''Mentor:''' Stefan Majewsky (majewsky at gmx dot net) – Please contact me to let me help you to improve your proposal.

====Project: Kolf 2 editor interface====
'''Brief explanation:'''
The minigolf game Kolf provided an editor interface from the beginning, to allow the users to create custom courses. For Kolf 2, we are rewriting the game engine and can therefore not use the old editor code.

'''Expected results:'''
Your task would be to create an editor interface (may be embedded in the game, or a standalone application). A few basic parts are available, and the Kolf 2 engine supports generic methods to provide data to editor interfaces, and display editor overlays on the game view.

If you finish the editor interface before the end of the summer, you can fill the remaining time by porting as much game objects from Kolf 1 to Kolf 2 as possible (e.g. windmills, floating blocks, signs or bumpers).

'''Knowledge Prerequisite:''' C++/Qt. Experiences in model/view programming with Qt will be of good use.

'''Mentor:''' Stefan Majewsky (majewsky at gmx dot net) – Please contact me to let me help you to improve your proposal.

----

===Solid===
====Project: UPnP support through Jolie====
'''Brief explanation:'''
Adding UPnP support to Solid would mean offering transparent UPnP support to every KDE application using the Solid API, keeping them clean from every UPnP implementation aspect.
At the present, the [http://www.jolie-lang.org/ Jolie language] is being integrated with Plasma by means of the [http://websvn.kde.org/branches/work/~ervin/sodep/ QtSodep] library, soon to offer higher levels of abstraction.

The aim of this project would be to implement a UPnP protocol for Jolie, so that Solid could re-use the integration being made with QtSodep and gain UPnP support without having to worry about implementation details. Having a UPnP protocol implementation in Jolie would have other considerable consequences, like the possibility to act easily as a UPnP server or to compose and export existing UPnP services.

'''Expected results:'''
*The creation of a "upnp" protocol in Jolie, supporting at least the Internet Gateway Device (IGD) and MediaServer profiles.
*The creation of a UPnP Jolie service for UPnP service discovery and monitoring.
*Extending libsolid to expose UPnP devices found on the network.

'''Material Prerequisite:''' Having UPnP devices or software applications to test with. Most home routers support IGD, and there exists free software supporting the MediaServer profile ([http://mediatomb.cc/ mediatomb]).

'''Knowledge Prerequisite:''' Understanding of the UPnP specifications, Java (for the development of the Jolie UPnP protocol) and basic knowledge of the Jolie language.

'''Mentors:''' ervin (ervin at kde dot org) fmontesi (famontesi at gmail dot com)
----

===KWin===

KDE's window manager

[http://techbase.kde.org/Projects/KWin Techbase page] - [https://mail.kde.org/mailman/listinfo/kwin Mailinglist] - IRC channel: #kwin on Freenode.

====Project: Window tabbing====

'''Brief explanation:'''
Window tabbing is a feature that allows you to group multiple application windows together to cover the same space. It is identical to what is already available in any modern web browser except it applies the the window as a whole. Window managers that have this feature available include Fluxbox and Ion. This feature was [http://bugs.kde.org/show_bug.cgi?id=42023 originally requested] in 2002.

'''Knowledge Prerequisite:''' C++ and Qt. Understanding of the X window system and Xlib is a benefit but not required.

'''Mentors:''' Lucas Murray (lmurray undefinedfire com)

====Project: Window tiling====

'''Brief explanation:'''
Window tiling is a technique of displaying application windows side-by-side without overlap. The position, size and layout of the windows can either be specified by the user or determined automatically to best fit the screen. Examples of existing tiling window managers include Awesome, XMonad, Ion and Ratpoison. One of the main advantages of tiling is that is makes application windows easy to navigate solely by the keyboard. This feature was [http://bugs.kde.org/show_bug.cgi?id=59338 originally requested] in 2003.

'''Expected results:'''
* Users should be able tile existing floating windows on-the-fly with simple keyboard shortcuts or mouse gestures.
* It should also be possible to run the entire desktop environment entirely in tiled mode (Enabled by configuration settings). In this mode new window would be added to the tiling grid by default yet can be removed by the user if required.
* The final tiling system should not interfere in any way with the existing floating window management.

'''Knowledge Prerequisite:''' C++ and Qt. Understanding of the X window system and Xlib is a benefit but not required.

'''Mentors:''' Lucas Murray (lmurray undefinedfire com)

----

=== digiKam ===

Photo Management program

[http://www.digikam.org digiKam project web site] - [https://mail.kde.org/mailman/listinfo/digikam-devel Mailinglist] - IRC channel: #digikam on Freenode.

====Project: High Dynamic Range (HDR) plugin====

'''Project Information:''' digiKam is an advanced digital photo management application for KDE, which makes importing and organizing digital photos a "snap". The photos are organized in albums which can be sorted chronologically, by folder layout or by custom collections. digiKam has an Image Editor which has its own plugin subsystem with some common tools e.g. red eye correction or Gamma correction. Additional plugins are provided with the main application to process advanced corrections on image like color management, noise reduction, or special effects. digiKam image editor support 16 bits color depth image internally. The goal of this project is to create a new plugin dedicated to create [http://en.wikipedia.org/wiki/High_dynamic_range_imaging HDR image].

'''Expected results:''' This project should implement an HDR tool will mix two or more (nearly) identical images having different exposure into a new image representing a wider dynamic range, which is closer to human perception of a photographic scene. [http://en.wikipedia.org/wiki/Tone_mapping Tone-mapping method] must be used to create HDR images. An open-source implementation is already available at [http://zynaddsubfx.sourceforge.net/other/tonemapping this url] and can be re-used as well. There is an old [https://bugs.kde.org/show_bug.cgi?id=144593 feature request].

'''Knowledge Pre-Requisite:''' C++/Qt.

'''Mentors:''' Gilles Caulier (caulier dot gilles at gmail dot com)

----

===KDE Telepathy Integration===
The [http://telepathy.freedesktop.org Telepathy Framework] is a desktop independent framework for real-time communication, such as VoIP and Instant Messaging. The projects below are some ideas for integrating telepathy into KDE.

If you want to know any more about Telepathy and KDE, drop by the irc channel #decibel and talk to '''grundleborg''', or use the mailing list decibel AT kde DOT org.

====Project: Message Logging====

'''Project Information:''' The Telepathy Framework allows for components which can watch channels whilst a user is interacting with them through another application. A program could be created to log the content of text instant messages into an Akonadi collection.

'''Expected results:''' This project should result in a telepathy watcher which is capable of logging the contents of text chats into an Akonadi collection. It should be possible to go off-the-record in a particular conversation from telepathy user interfaces and the logger should not save any messages in this situation. This project might also include modifying the Kopete logging plugin to use the same akonadi collection for logs, and making a migration tool from Kopete's old logging format to the new Akonadi collection.

'''Knowledge Pre-Requisite:''' C++/Qt, some basic knowledge of the Telepathy Framework is an advantage, but not necessary if you have an interest in real-time communcation and are prepared to learn fast.

'''Mentors:''' George Goldberg (grundleborg at gmail dot com) IRC: grundleborg

====Project: Telepathy Integration to any KDE application====

'''Project Information:''' Provide some collaborative feature or instant messaging integration for your favourite KDE application.

'''Expected results:''' This project should result in a collaborative feature or instant messaging integration being added to the chosen KDE application. It should be complete enough to provide at least basic functionality to end users, with the possibility of further improvement after the summer of code period ends.

'''Knowledge Pre-Requisite:''' C++/Qt, some basic knowledge of the Telepathy Framework is an advantage, but not necessary if you have an interest in real-time communcation and are prepared to learn fast.

'''Mentors:''' George Goldberg (grundleborg at gmail dot com) IRC: grundleborg. You should also discuss your idea with the development team of the application in which you would like to provide a Telepathy feature.

====Project: Telepathy Plasma Integration====

'''Project Information:''' Provide integration of presence and buddy information into plasma.

'''Expected results:''' You should provide multiple points of integration between presence and contact information and plasma. Plasmoids allowing the display and manipulation of your own presence information should be made available, building on the plasma applets and datengines already in existance for presence information. Plasma activities could also be made aware of presence, and the contacts plasmoid could be made aware of your buddies from Telepathy instant messaging accounts.

'''Knowledge Pre-Requisite:''' C++/Qt

'''Mentors:''' George Goldberg (grundleborg at gmail dot com) IRC: grundleborg. You should also discuss your ideas with the plasma development team before making a proposal.

----

Projects/Summer of Code/2009/Ideas

2009-02-22T13:11:53Z

Grundleborg: /* KDE Telepathy Integration */

== 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 kde-devel@kde.org. See [http://www.kde.org/mailinglists/ 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==
===Plasma===
[http://plasma.kde.org Website] - [https://mail.kde.org/mailman/listinfo/panel-dev Mailing list] - IRC channel: #plasma on Freenode.

====Project: Generic SOAP Plasma::Service====
'''Brief explanation:'''
The Service should be able to parse WSDL files and let Plasmoids connect to the described Webservices.

====Project: Simple Media Center components====
'''Brief explanation:'''
Plasma could offer a Media center mode, where features a really simple ui to browse media files and plasmoids that shows the actual media. All should be operable with mouse, keyboard or a simple remote control. the work could consist in building the whole thing or just writing a plasmoid able to browse media files, that is the most important missing part.
Mockups for it by Nuno Pinheiro can be seen [http://img213.imageshack.us/img213/3200/image3231picturefz5.png here] and [http://img26.imageshack.us/img26/3407/image323musicoloectionck2.png here]

'''Expected results:'''
An applet to browse and thumbnail media files, like the first mockup and control the actual media viewing applets, like the media player applet or the picture frame applet. At this stage the functionality will be really minimum

'''Knowledge prerequisite:'''
Knowledge of C++ and some familiarity with Qt especially QGraphicsView related classes.

'''Mentor:'''
Marco Martin (notmart a gmail dot org), or other Plasma developers. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Plasmate====
'''Brief explanation:'''
PlasMate is an application that gives people a way to start creating scripted plasmoids without worrying about anything except making their bits. It hides the whole metadata.desktop thing, the package layout details, making a Plasmoid package (aka "zipping up the directory"), uploading content and version control system.

'''Expected results:'''
Working application that one can do the tasks described above, making it easy to create and distribute a scripted plasmoid.

'''Knowledge prerequisite:'''
Knowledge of C++ and familiarity with Qt (QWidgets and QGraphicsView related classes).

'''Mentor:'''
Artur Duque de Souza (morpheuz a gmail dot org), or other Plasma developers. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Qt Kinetic + Plasma====
'''Brief explanation:'''
A layer over Qt Kinetic to provide a standardized set of "out of the box"
animations and bring them into libplasma. The work will be done with the Plasma developers to make this API as efficient as possible. The work will be based on Kinetic, the next framework for animations in Qt.

'''Expected results:'''
We can kill Plasma::Animator class. The goal is to bring fancy effects/animations in Plasma to have one of the best desktop ever.

'''Knowledge prerequisite:'''
Knowledge of C++, familiarity with QGraphicsView related classes and some familiarity with animations bits.

'''Mentor:'''
Alexis Ménard (alexis.menard at nokia dot com) or Artur Duque de Souza (morpheuz a gmail dot org). Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Eduactional layout====
'''Brief explanation:'''
A set of Containments and Plasmoids specifically designed for primary school
students.

'''Expected results:'''
A simplified panel containment that contains basic launchers and user feedback
for the student, a widget that allows teachers to provide context-specific
sets of applications and documents to the student (context being a combination
of the student logged in and the current class subject), a widget that
provides some basic teacher->student communication and status (e.g. what the
current assignment is, how long the student has been logged in, etc) and
optionally some widgets that work with KDE edu apps.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Desktop dock====
'''Brief explanation:'''
A MacOS style dock containment.

'''Expected results:'''
A containment that provides a similar user experience to the MacOS dock:
application launchers that are also task bar entries when the application is
active and a separate area for widgets such as the trash, battery, etc.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Kdm frontend using plasma====
'''Brief explanation:'''
A log-in screen layout manager for KDM that uses libplasma.

'''Expected results:'''
A KDM screen that is rendered completely using Plasma. This means both using
libplasma in KDM for the log in screen as well as writing Plasmoids for
entering the user name and password, listing users, session switching, etc.
Some of these widgets already exist for the desktop shell, so in some cases
this will be simply integrating existing Plasmoids, but in other cases will
mean writing new ones from the ground up.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Raptor====
'''Brief explanation:'''
Raptor aims to deliver a new kind of launch menu system for KDE. It is designed with usability and beauty in mind.
Raptor-Menu does not try to be the final answer to the menu question, instead aspires to be the best answer we can give, merging many ideas form modern desktop launch menus.

'''Expected results:'''
http://www.raptor-menu.org/

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: New Widget Explorer====
'''Brief explanation:'''
A new widget explorer that supports both our own widgets as well as others
more seamlessly.

'''Expected results:'''
A usable and pretty browser for widgets that allows a user to see an icon or
snapshot of the widget, select a widget to be placed in a containment, search
for a widget based on name/description, sort the widgets into categories, rate
widgets and provide ways to launch the online browsers and installers for both
native Plasmoids as well as third party tools such as Google Gadgets (which is
already supported in the Package class). All the required support
functionality already exists, this project is really about creating a
beautiful and dynamic user interface for looking through a widget catalog that
looks "Plasma".

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: D-Bus Interface====
'''Brief explanation:'''
A comprehensive set of D-Bus interfaces for the plasma-desktop Plasma shell.

'''Expected results:'''
The D-Bus interface must provide access to the Corona (DestkopCorona class),
which in turn will list all existing Containments and allow Containments to be
added, removed, saved, etc.

A D-Bus interface for each existing Containment will be made available as
well, which will provide a standard set of tools including listing, adding and
removing widgets as well as positioning and sizing for PanelContaiments. Ways
to control the wallpaper, if any, will also be provided in the per-Containment
D-Bus interface.

In turn, a D-Bus interface for each widget representing its available
contextual actions will be provided dynamically upon request.

Finally, the application D-Bus interface for things such as locking/unlocking
widgets will be designed and implemented.

The result will be a Plasma that is fully accessible via D-Bus.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Security====
'''Brief explanation:'''
A set of methods to define the existing security state of the Plasma
application, the security requirements of individual widgets, mechanisms to
respect those two sets of information and cryptographic signing of Plasmoid
packages.

'''Expected results:'''
A set of functionality descriptions will be enumerated (e.g. "Network access",
"Local file system access", etc.). Individual widgets will advertise which of
these functionality sets they require.

The plasma-overlay shell (used on the screensaver) will have code added to it
to respect these settings and not run widgets that advertise they need things
that aren't safe to provide on a screensaver (due to it being locked to
prevent others from accessing the system).

The plasma-desktop shell will gain the ability to be put into various lock down
states which will map to different sets of functionality. Part of this project
will be enumerate the various states, but that list must include "only load
trusted widgets", "no external access", "no local file system access".

The JavaScript engine will provide methods for each of the functionality sets
(e.g. a set of functions to access local files) which will be exported or not
based on the current Security state. This implies providing a security state
to the Corona which can then be passed on down to Applets and AppletScripts.

Finally, GPG signing of Plasmoid packages will be implemented along with a way
of checking the validity of these at runtime.

'''Knowledge prerequisite:'''
Knowledge of C++ and some experience with security.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

===Amarok===
A KDE music manager and player.

[http://amarok.kde.org Website] - [https://mail.kde.org/mailman/listinfo/amarok Mailing list] - IRC channel: #amarok on Freenode.

====Project: DLNA/UPnP Support====
'''Brief explanation:'''
Using the UPnP protocol users can, for example, share music from their Vista computer to a PS3. Amarok lacks any sort of UPnP support. Being able to act as a client or possibly a UPnP media server would be useful. In addition to that controlling a UPnP Media Renderer from within Amarok is possible with framework support.

The [http://coherence.beebits.net/ Coherence server] would likely be used since it is also intended to be used by a KIO slave.

'''Expected results:'''
*Using the Amarok Collection framework, create a plugin which allows Amarok to browse, search and play music off of a UPnP share. Playing music may use the UPnP KIO-slave, but more advanced functionality requires Amarok to handle this directly.
*Allow Amarok to share it's collection with other devices or control other devices via UPnP. This is secondary priority but it may be pretty easy with Coherence.
*Control UPnP Media Renderers (DMR: Digital Media Renderer device class in DLNA) from within Amarok.

'''Material Prerequisite:''' Some UPnP devices or computers to test with. Good excuse to buy a PS3. If you live in Europe a Philips Streamium DMR can be borrowed.

'''Knowledge Prerequisite:''' C++ and Qt. Coherence uses Python and D-Bus but doesn't need to be hacked on in the scope of this project.

And of course, understanding of UPnP networking and devices wouldn't hurt!

'''Mentor:''' Stecchino (bart.cerneels at kde dot org)
----

====Project: New meta-applets for the Context View====
'''Brief Explanation:'''
The Context View (CV) is currently used to display multiple applets that expose various information. However, due to the fact that each applet displays a certain type of information from one data source, there is significant amount of wasted space, and it is hard to show much more than 3 different pieces of data at once.

Meta-Applets are large applets that integrate date from multiple data sources in order to display more semantically related information coherently and efficiently. This could mean, for example, an applet that brings together lyrics, artist info, upcoming concerts, and related songs/artists.

More info is available here [http://amarok.kde.org/wiki/Proposals/More_Contexual_Information on the amarok wiki]

'''Expected Results:'''
Two or three (to be discussed with mentor in application writing process) applets that elegantly execute the ideas discussed above.

'''Knowledge prerequisite:'''
Knowledge of C++ is required, and some familiarity with Qt is helpful (especially QGraphicsView) but not necessary.

'''Mentor:'''
Leo Franchi (lfranchi AAAT kde DT org), or other Amarok developers. Contact at amarok@kde.org or #amarok on freenode.

----
====Project: Code regression test suite, implemented with QtScript ====
'''Brief explanation:'''
Amarok currently has no automatic code regression testing ("unit testing") in place at all. We very much need such a system in place (for as many components as possible), as we sometimes accidentally break certain components of the program by extending the code.

'''Expected results:'''
Code regression test suite for Amarok 2, implemented as one "Amarok-Script" (JavaScript), and internally split into multiple separate files and components, so that it would be possible to run arbitray tests (or the full suite) with very little effort, and no compiling, at any time. A requirement would also be testing of the collection scanning code (with test case collections), and testing of GUI correctness with the QTest library.

Also see:
http://amarok.kde.org/wiki/Development/Scripting_HowTo_2.0

A plus would be the generation of suitable statistics (possibly with document export), and possibly a visual representation of the data.

'''Material Prerequisite:'''
Amarok 2 trunk, KDE SVN account, git. Linux, OSX, or Windows.

'''Knowledge Prerequisite:'''
C++, Qt, KDE-Libs, QtScript (JavaScript), SVN, git, code testing.

'''Mentor:'''
Potentially one of several. Contact the amarok mailing list or ask in our IRC channel #amarok
----

====Project: Multilevel playlist sorting and sorting GUI ====
'''Brief explanation:'''
In Amarok 2.1, the layout of the playlist will be very configurable, being able to show as much or as little information about each track as each user might wish. Currently however, it is lacking an advanced system for sorting in the playlist, something that many users comming from Amarok 1 are missing. While simple sorting is relatively easy to do (and has already been partly implemented) we would like to aim a bit higher with Amarok 2.

'''Expected results:'''
A proxy model allowing the tracks in the playlist to be sorted using an arbitrary number of "layered" sort criteria. for instance, a sort setup could be "artist-album-tracknumber" This would sort all tracks by artist, then sort the tracks from each artist by album, and finally the tracks from each album based on track number. Once this model is working, a GUI is needed for making this functionality easilly avaialble to the user. Ideally this gui should tie in well with the playlist layout and search/filter stuff. Also, all track navigators (the classes that determines the order of playback, such as normal, random, random album and so on) need to be updated to use and work correctly with the new proxy model.

'''Material Prerequisite:'''
Amarok 2 trunk, KDE SVN account, Linux, OSX, or Windows.

'''Knowledge Prerequisite:'''
C++, Qt, KDE-Libs, SVN/git.

'''Mentor:'''
Nikolaj Hald Nielsen <nhnFreespirit@gmail.com> or contact the amarok mailing list or ask in our IRC channel #amarok
----

====Project: Playlist and Collection synchronization====
'''Brief explanation:'''
Mediadevices and services can add tracks and playlists to Amarok. Synchronization would automatically copy over tracks between the main Amarok Collection and devices or services or even between each other, either for a single playlist or the complete collection.
An algorithm needs to be implemented that does this automatically in a fast and efficient way with minimal intervention needed by the user.

'''Expected results:'''
Playlists set up on both the local collection and a portable mediaplayer will get synchronized the moment the player is connected.

'''Material Prerequisite:'''
Amarok 2 trunk, KDE SVN account, Linux, OSX, or Windows.

'''Knowledge Prerequisite:'''
C++, Qt, KDE-Libs, SVN/git.

'''Mentor:'''
Bart Cerneels <bart.cerneels at kde dot org> or contact the amarok mailing list or ask in our IRC channel #amarok

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

[http://phonon.kde.org Website] - [https://mail.kde.org/mailman/listinfo/phonon-backends Mailing list] - IRC channel: #phonon on Freenode.

====Project: Analyzer Support====
'''Brief explanation:'''
Applications such as Amarok and Dragon Player cannot have an analyzer or visualizations since they use Phonon which does not yet have the functionality to do it. The analyzer is the little bar graph thing which bounces around while music is playing. Users like it as its pretty and gives them a visual indication of their music playing.

'''Expected results:'''
As this project is working on extending a library, it has three parts: the Phonon library itself, a Phonon backend, and an application. The Phonon library would need the new API calls. At least phonon-xine and preferably 1 or 2 other Phonon backends must then implement the new API. An application like Amarok or Dragon Player should be used to demonstrate the use of the new API.

'''Knowledge Prerequisite:''' C++ and Qt. Experience with Xine or GStreamer is probably useful.

'''Mentor:''' Ian Monroe (contact on the [https://mail.kde.org/mailman/listinfo/amarok Amarok mailing list]) or possibly another Amarok or Phonon developer.
----
===Marble===
A desktop globe and map application. Also provides a map Qt Widget.

[http://edu.kde.org/marble/ Website] - [https://mail.kde.org/mailman/listinfo/marble-devel Mailing list]

====Project: Satellite navigation====
'''Brief explanation:'''
Satellite navigation devices have become widely used and the quality of openstreetmap data is becoming high, with some cities completely mapped already. Providing satellite navigation would be a useful desktop app for many as well as adding appeal for the use of KDE in embedded devices.

It also opens the possibility to bringing many of the free software ideals to interaction with the real world such as collaborative/social POIs.

'''Expected results:'''
The project would aim at getting a basic satellite navigation application running. The most basic features required would be getting the current location from a GPS device and providing route calculation to a destination.

The AndNav project (http://andnav.org) has already achieved something similar for Android so it could be a point of reference for how to use OpenStreetMap data to achieve this.

'''Knowledge Prerequisite:''' C++ and Qt. Experience with GPS devices under linux would be beneficial. Knowing java may also be of benefit in order to study the AndNav implementation.

'''Mentor:''' I (Alan Jones, skyphyr using gmail) am willing to mentor, but not having any GPS or Marble experience there is most likely somebody far more suited to undertake this role.

Comment from a Marble Project guy: Alan, please get in touch with the Marble Project. Our mailing list is marble-devel@kde.org. We'd like to support this project if a student is willing to do it.

----

====Project: Add Time support to 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 [http://code.google.com/apis/kml/documentation/kmlreference.html#timeprimitive <TimePrimitive>] and [http://code.google.com/apis/kml/documentation/kmlreference.html#timespan <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.

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

'''Mentor:''' Torsten Rahn / Patrick Spendrin.

----

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

[http://www.kdevelop.org Website] - [http://www.kdevelop.org/index.html?filename=mailinglist.html Mailing list] - IRC channel: #kdevelop on Freenode.

====Project: C++ Refactoring Support====
'''Brief explanation:'''
C++ support in KDevelop is already highly advanced, often equalling or surpassing what the user and compiler understand about the code. A few refactoring tools have been developed already, but they have been constructed in a crude fashion, generating code via string concatenation.

This project would aim to create a new system to implement refactoring tools, and to create, test and deploy several advanced refactoring tools for c++.

'''Expected results:'''
A library would be created to enable refactoring based on the c++ AST (abstract syntax tree). A reverse parser (AST to code) already exists, but classes would be created to allow programatic manipulation of an AST. Optionally this library would also cover a generic framework based on the duchain which would be re-usable by other languages and make refactoring plugins easier to develop and partially shareable between languages.

See the [http://api.kde.org/4.x-api/kdevplatform-apidocs/language/codegen/html/index.html Code Generation Design] documents for the initial plan for this project.

'''Knowledge Prerequisite:''' C++ and Qt. Experience with parsers would be a bonus.

'''Mentor:''' Hamish Rodda (Definition-Use chain code creator) rodda at kde/dot/org, possibly also David Nolden (DUChain guru)(to be confirmed)
----
=== KStars ===
KStars is a Desktop Planetarium for KDE. It displays a map of the sky and provides a lot of tools to learn astronomy, or to calculate and predict astronomical phenomena. See [[http://edu.kde.org/kstars|The KStars Homepage]] for more information.

==== Project: Community Integration for KStars ====
'''Project Information:''' KStars is a desktop planetarium program for KDE.

'''Brief explanation:''' Amateur Astronomy (which is one of the important use-cases of KStars) is typically done in communities. KStars permits users to save their own observing logs. It would be nicer if the user could share his observing logs with other users and see other observers' logs within KStars. It would also be nice if KStars had a map (using MarbleWidget) to display various Astronomy-related establishments (like amateur associations, observatories, research institutes). Another possible idea could be an observing report generator that would generate a report based on observing logs, and at the user's will, share it / post it on the internet.

'''Expected results:''' Implement some features that will make it easier for users to collaborate, as suggested above.

'''Knowledge Pre-Requisite:''' Required: C++. Prior knowledge of KIO_HTTP will help.

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

==== Project: FITS Image Overlay on the sky map. ====

'''Project Information:''' KStars is a desktop planetarium program for KDE.

'''Brief explanation:''' It would be great if a FITS image could be overlayed on the sky map so that the field drawn by KStars could be compared with the field in the FITS image. This would be of great benefit to observational astronomers, astrophotographers and comet / asteroid observers. An extension would be to download a DSS image using KStars' already existing tool and map it onto the sky map. The support of shapes like ds9 region, annotations on the sky, etc. could also be added.

'''Expected results:''' Functionality to overlay a FITS image or a DSS image obtained through KStars on to the sky map.

'''Knowledge Pre-Requisite:''' Required: C++. Prior knowledge of the FITS format and cfitsio library will help.

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

==== Project: Tools for Eclipses ====

'''Project Information:''' KStars is a desktop planetarium program for KDE. Currently, it can predict Solar Eclipses (using the Conjunctions tool), but cannot plot trajectory of shadows, or predict Lunar Eclipses.

'''Brief explanation:''' The project's primary goals are to include simulation and prediction (maybe using the existing Conjunction backend) of Lunar eclipses, and to create a tool to mark the trajectories of Solar and Lunar eclipse shadows on a map of the earth, including marking of totality, partial eclipse and annular eclipse. Something similar to this: [http://eclipse.gsfc.nasa.gov/SEmono/TSE2009/TSE2009iau/TSE2009-fig01.GIF]

'''Expected results:''' A complete set of tools to deal with eclipses.

'''Knowledge Pre-Requisite:''' C++

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

==== Project: KStars: Prettyfication ====
'''Project Information:''' KStars is a desktop planetarium program for KDE. The display is interactive, but it could be made more beautiful.

'''Brief explanation:''' We often get good suggestions for making KStars look better. Choose any of the following ideas: realistic rendering of asteroids and comets (including tails!); texture-mapping of the sky (this would mostly allow a photorealistic Milky Way); texture-mapping of planets; realistic sky-lighting effects (i.e., sky is blue in the daytime, gets gradually darker and colorful at sunset). One could also think of using Qt-GL rendering optionally.

'''Expected results:''' Successful implementation of any of these ideas to make KStars more beautiful.

'''Knowledge Pre-Requisite:''' Required: C++.

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

==== Project: Printable star charts ====
'''Project Information:''' KStars is a desktop planetarium program for KDE. It already has a print feature, but the printed chart could be much better.

'''Brief explanation:''' A printed star chart should at least include a legend explaining the symbols, and provide some information on the location of the user, the time and date, etc. The user would ideally be able to annotate the chart in various ways.

'''Expected results:''' Significant improvements to the printed star charts in KStars.

'''Knowledge Pre-Requisite:''' Basic programming skills, ability to quickly learn QPainter API.

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

==== Project: Many Moons ====
'''Project Information:''' KStars is a desktop planetarium program for KDE. It currently includes Earth's moon and 4 of Jupiter's moons.

'''Brief explanation:''' Generalize the JupiterMoons class to encapsulate any planet's Moons. The project will require some research to identify a public source of orbital data for planetary moons, most likely from a NASA webpage.

'''Expected results:''' Implement moons for at least Mars, Jupiter, Saturn, and Pluto with the new system.

'''Knowledge Pre-Requisite:''' Required: C++. The project doesn't require much contact with Qt/KDE APIs, and the existing JupiterMoons class can be used as a template.

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

==== Project: Support many catalogs ====
'''Project Information:''' KStars is a Desktop Planetarium for KDE. Currently KStars loads some star catalogs that are made available in a KStars native format.

'''Brief Explanation:''' KStars currently loads Tycho-2 and parts of USNO NOMAD catalog of stars. These catalogs are required to be in KStars' native format which uses the Hirearcheal Triangular Mesh to index regions in the sky. Popular star catalogs like USNO A organize stars and divide the sky into regions differently. Most users of astronomy software typically have one of these popular catalogs downloaded, and it would be great if KStars could support them somehow. While ability to read the non-native catalogs straight off is desirable, tools to convert these catalogs into KStars' native format would also help.

'''Expected Results:''' Implement support for at least the most popular catalogs like USNO-A2.0, Stellarium's Extra catalog, Cartes du Ciel's Tycho and Tycho-2 catalogs.

'''Knowledge Pre-Requisite:''' Required: C++. Ability to read documentation and quickly understand the existing code and ability to deal with binary files will help.

=== Kalzium ===

==== Project: Strigi integration ====

'''Project Information:'''
The goal of this project is to integrate Strigi as backend behind the periodic table and the glossary (and possible other elements).

'''Brief explanation:'''
The idea here is to have a GUI element that shows Strigi search results based on the element selected from the periodic table, or the item from the glossary, found on the users desktop. For element, this would include the elements name, and possible even the element symbol, if integration with last years Strigi-Chemistry GSoC project is achieved. For glossary items, a simple text search would suffice.

Another idea is to make it possible to querry like this: "Give me all molecules with a molecularweigth of 123u and at least one Carbon atom". For this we can use the [http://chem-file.sourceforge.net/ Chemical File Database] (or of course every other database, even those for [http://www.rcsb.org/pdb/home/home.do proteins].

'''Expected results:'''
* provide GUI for Strigi search results for an element selected in the periodic table
* provide GUI for Strigi search results for an glossary item

'''Knowledge Pre-Requisite:''' Required: C++, DBUS. Could be useful: Qt.

'''Mentor:''' Undecided.

----

==== Project: Kalzium beautification ====

'''Project Information:'''
Many parts of [http://edu.kde.org/kalzium Kalzium] could need a fresh up of the interface. For example, the main table should be written using Qt Model/View technique and for example use SVGs as a background. A first (uncomplete but working) code is already existing.

At the same time, many dialogs are not as beautiful as they could be. This project could also include the creation of a "simplified Kalzium" mode in which some parts of the feature set are hidden; this would be good for schools.

A third idea is to make more use of Plasma, for example improve the already written Plasmoids and/or extent Kalzium so that a Plasmoid could open a information dialog using Kalzium.

'''Expected results:'''
Depending on the chosen project for example a cleaned up codebase with an improved interface.

'''Knowledge Pre-Requisite:''' Required: C++, Qt, possible Plasma, Debug.

'''Mentor:''' Carsten Niehaus

=== KOffice ===
-----

'''Project:''' support for versionned OpenDocument files.

'''Explanation:''' The OpenDocument specification doesn't include support for multiple versions of the same document in a single file. But that feature is supported by OpenOffice.org. The objective for this Summer of Code is to add support for that versionning system in KOffice. Since KOffice shares the OpenDocument loading/saving code, it should be possible to add this support in every KOffice application in one Summer of Code.

'''Expected results:''' Being able to load a specific version of a file, and create/manage versions

'''Knowledge Pre-Requisite:''' C++, excellent english reading skills.

==== KWord ====
-----

==== KPresenter ====
-----

'''Project:''' Powerpoint import.

'''Explanation:''' From some years ago another gSoc project implemented the basis for powerpoint import, but it was never finished. So there is a good basis to start from. From a quick look it seems like styles support is the thing missing most to complete the work, however a thorough analysis of what is there and what is not needs to be done. And then the actual work needs to be done too, obviously

==== Krita ====

-----

'''Project:''' Sketch-pad interface for Krita

'''Project Information:''' Krita is a large and complex application built around a sophisticated painting engine. The goal of this project is to create a new interface around the Krita engine, specialized for quick sketching.

'''Expected results:''' This project should implement a new interface around Krita, presenting the user a single-layer plus tracing paper interface with a single freehand sketching tool. Easy to use and graphic color and paint operation (brush, pencil, eraser etc.) interface elements must be designed and implemented.

'''Knowledge Pre-Requisite:''' C++

-----

'''Project:''' Shader filters and generators for Krita

'''Project Information:''' Some initial work has already been done to make it possible to write filters in the OpenGL shading language. This project should take that initial code as a basis and implement a fully functioning plugin for Krita that allows filters and shaders to be executed on images in any colorspace.

'''Expected results:''' The plugin should have a finished user interface and make it possible to experiment with shader filters in an interactive way. Example filters must be implemented.

'''Knowledge Pre-Requisite:''' C++, OpenGL.

-----

'''Project:''' Animation support

'''Project Information:''' There is no support at all in Krita for animated images such as GIF or MNG or for working with images in an animation context, such as textures or backgrounds in applications like Blender. The applicant should first investigate user needs and use cases and then implement support in the user interface and in the import/export filters.

'''Expected results:''' A user-friendly way of working with animated images (i.e., not by making each frame a layer), but e.g. a docker that shows the the animation running in thumbnail format. Import/export filters for relevant file formats.

'''Knowledge Pre-Requisite:''' C++

-----

'''Project:''' PSD and Gimp plugins

'''Project Information:''' Krita is powerful enough to handle nearly all that the Gimp and Photoshop are capable of saving. This project is about creating dedicated file import/export filters that can handle as much of these file formats as possible, possibly through the use of existing libraries.

'''Expected results:''' 4 plugins: psd import/export and xcf import/export. These plugins should be able to handle complex files in all supported colorspaces. Ideally the project would also deliver a library to convert PSD/XF to/from Open Raster files.

'''Knowledge Pre-Requisite:''' C++

-----

'''Project:''' Workspaces

'''Project Information:''' A workspace is a loadable package of settings that finetune Krita for a particular purpose. A workspace could contain additional plugins (like an image browser plugin for batch operations) and a subset of resources. Example workspaces could be batch-editing of images, editing of animation sequences or painting or sketching.

'''Expected results:''' the user interface and framework to make packages of plugins and resources that users can switch between. Also extra plugins to extend krita in areas like batch processing that do not exist yet.

'''Knowledge Pre-Requisite:''' C++, artistic workflow

-----

'''Project:''' Kipi and digikam plugins compatibility

'''Project Information:''' Kipi and digikam provide lots of interesting plugins for working with 8 and 16 bit RGBA images. It would be great to be able to re-use those plugins from within Krita.

'''Expected results:''' Two plugins that load kipi and digikam filters into two new menus in the filter menu. Code to convert Krita layers to the digikam image representation and back, taking care of icc profiles and other niceties.

'''Knowledge Pre-Requisite:''' C++, artistic workflow

===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 [http://www.akonadi-project.org/ Akonadi].

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

[http://pim.kde.org/ Website] - [http://techbase.kde.org/Projects/PIM Project Wiki] - [https://mail.kde.org/mailman/listinfo/kde-pim Mailing list] - IRC channel: #kontact and #akonadi on Freenode.

====Project: Akonadi Janitor Agent====
'''Brief explanation:'''
An [[Development/Architecture/KDE4/Akonadi#Akonadi_Agents|Akonadi Agent]] is a service process for performing tasks on data provided through the Akonadi server.

The task of a Janitor agent would be to keep the user's PIM data neatly organized, for example deleting news feed items which are above a certain age and not flagged, moving last week's mail to an archive, etc.

'''Expected results:'''
* An Akonadi Agent capable of managing actions on Akonadi collections triggered by various criteria
* At least fully working implementation of actions based on "Expire" criterias for mail, e.g. delete mail above certain age, move/copy to different collection, etc
* GUI for configuring actions and their trigger criteria.

'''Knowledge Prerequisite:''' C++ and Qt. Ideally would already have gone through the [[Development/Tutorials/Akonadi/Resources|Akonadi Resource Tutorial]] since Resources are a specialized form of agents and thus share some of the API and characteristics.

'''Mentor:''' Kevin Krammer (kevin dot krammer at gmx dot at)
----
====Project: Alternative Akonadi Client Library====
'''Brief explanation:'''
Akonadi has a server/client like architecture where clients such as applications (but also resource) connect to a service and communicate with it through a suitable protocol.

Currently this is implemented for KDE in library called libakonadi-kde, however it is desirable to have additional implementations to be suitable for other library stacks, e.g. GLib/GObject based ones.

'''Expected results:'''
* A non-KDE based, preferably GLib/GObject based, Akonadi client library which
** can connect to a running Akonadi server
** fetch Akonadi collections
** fetch Akonadi items
** receive Akonadi change notifications (D-Bus based)

* A set of demo programs using the library which can
** recursively list (id and content MIME types) collections
** list (id and MIME type)oif items in a collection
** get the raw payload of an item

'''Knowledge Prerequisite:''' Depends on the chosen language and toolstack, e.g. C/Vala and GLib/GObject knowledge for a GLib/GObject based implementation.

'''Mentor:'''
----
====Project: Akonadi Consistency Checker====
'''Brief explanation:'''
Akonadi provides a structure of collections and items, similar to folders and files of a filesystem. Similarly the internal structures have to follow certain constraints which must not be violated. Nevertheless, this can happen as result of bugs, hardware failures, power loss and a million other reasons.

Filesystem checks exist to detect and possibly fix such situations. Such functionality would also be desirable for Akonadi.

'''Expected results:'''
* A consistency checker (built into the Akonadi server or stand-alone) that performs an extensible set of checks on the internal data structures of the Akonadi server, such as:
** items belong to existing collections
** collections are child collections of existing collections
** the collection tree is non-cyclic
** every collections is owned by an existing resource
** collection sub-trees are owned by the same resource
** every item payload part belongs to an existing item
** content type constraints of collections are not violated
** ...
* each check should be accompanied with recovery code, such as moving orphaned items into a lost+found folder
* integration into Akonadiconsole
* integration into unit-tests

'''Knowledge Prerequisite:''' C++ and Qt mandatory, SQL/database knowledge would be useful.

'''Mentor:''' Volker Krause <vkrause@kde.org>
----
====Project: Akonadi Resource for KMail local folders====
'''Brief explanation:'''
KMail stores its mail in a folder hierachy where each folder can contain mails '''and''' further sub folders.

While mails are stored either as mbox or maildir, additional index files are used to speed up message listing and to store message status and flags.

The already existing Akonadi MailDir resource can handle the maildir aspects but cannot handle either mbox based folders nor the additional information stored in the index files.

'''Expected results:'''
* a set of classes, probably as a library, capable of
** recursively listing the KMail folder tree given a base directory
** reading mails from the mbox and maildir folders in the KMail folder tree
** reading KMail index files
* an Akonadi resource using these classes to provide read-only access to all mails currently handled by KMail. The resource should also be able to transfer the flags stored in KMail's index file to Akonadi.
* Writing a migrator, similar to the current KResource->Akonadi migrator, that automatically reads the KMail config file and creates a Akonadi resource out of it. Optionally, depending on the overall progress, the migrator would also convert some of KMail's folder settings, like the folder icon or the expiry settings, to Akonadi collection attributes.

'''Knowledge Prerequisite:''' C++ and Qt mandatory, code analysis skills would be helpful regarding the handling of index files, refactoring skills if KMail's classes are to be extracted from KMail's code base (not required).

'''Mentor:''' Thomas McGuire <mcguire at kde dot org>
----

===KDE on Windows===
====Solid API backend====
'''Brief explanation:'''
The porting efforts to make KDE available across platforms do need some backends for system dependent tasks. One of the KDE libraries that bundles this is Solid.

'''Expected results:'''
You implement a backend for the [http://solid.kde.org Solid API] using WINAPI.
It has to work with both MinGW and MSVC compilers. Not every function is required, but the basic functionality (network access, removable drives/harddisks and power) should be implemented.

'''Knowledge Prerequisite:''' Windows API and C++/Qt. You should be able to set up the [http://techbase.kde.org/Getting_Started/Build/KDE4/Windows development environment] yourself and be familiar with it.

'''Mentor:''' Carlo Segato (brandon dot ml at gmail dot com) or Patrick Spendrin (ps_ml at gmx dot de)
----

===KDE Games===
====Project: Kolf 2 landscape object====
'''Brief explanation:'''
Kolf 2 is the second incarnation of KDE's minigolf game. We are currently rewriting it from scratch to take advantage of the powerful technologies provided by Qt 4 and KDE 4.

'''Expected results:'''
The task in this project is to create an object (or multiple objects) that provide(s) landscape textures, slopes, puddles and sand bunkers.

If you finish this task before the end of the summer, you can fill the remaining time by porting as much game objects from Kolf 1 to Kolf 2 as possible (e.g. windmills, floating blocks, signs or bumpers).

'''Knowledge Prerequisite:''' C++/Qt. Experiences in graphics programming with Qt will definitely help, as you are expected to implement 2D rendering for the landscape object.

'''Mentor:''' Stefan Majewsky (majewsky at gmx dot net) – Please contact me to let me help you to improve your proposal.

====Project: Kolf 2 editor interface====
'''Brief explanation:'''
The minigolf game Kolf provided an editor interface from the beginning, to allow the users to create custom courses. For Kolf 2, we are rewriting the game engine and can therefore not use the old editor code.

'''Expected results:'''
Your task would be to create an editor interface (may be embedded in the game, or a standalone application). A few basic parts are available, and the Kolf 2 engine supports generic methods to provide data to editor interfaces, and display editor overlays on the game view.

If you finish the editor interface before the end of the summer, you can fill the remaining time by porting as much game objects from Kolf 1 to Kolf 2 as possible (e.g. windmills, floating blocks, signs or bumpers).

'''Knowledge Prerequisite:''' C++/Qt. Experiences in model/view programming with Qt will be of good use.

'''Mentor:''' Stefan Majewsky (majewsky at gmx dot net) – Please contact me to let me help you to improve your proposal.

----

===Solid===
====Project: UPnP support through Jolie====
'''Brief explanation:'''
Adding UPnP support to Solid would mean offering transparent UPnP support to every KDE application using the Solid API, keeping them clean from every UPnP implementation aspect.
At the present, the [http://www.jolie-lang.org/ Jolie language] is being integrated with Plasma by means of the [http://websvn.kde.org/branches/work/~ervin/sodep/ QtSodep] library, soon to offer higher levels of abstraction.

The aim of this project would be to implement a UPnP protocol for Jolie, so that Solid could re-use the integration being made with QtSodep and gain UPnP support without having to worry about implementation details. Having a UPnP protocol implementation in Jolie would have other considerable consequences, like the possibility to act easily as a UPnP server or to compose and export existing UPnP services.

'''Expected results:'''
*The creation of a "upnp" protocol in Jolie, supporting at least the Internet Gateway Device (IGD) and MediaServer profiles.
*The creation of a UPnP Jolie service for UPnP service discovery and monitoring.
*Extending libsolid to expose UPnP devices found on the network.

'''Material Prerequisite:''' Having UPnP devices or software applications to test with. Most home routers support IGD, and there exists free software supporting the MediaServer profile ([http://mediatomb.cc/ mediatomb]).

'''Knowledge Prerequisite:''' Understanding of the UPnP specifications, Java (for the development of the Jolie UPnP protocol) and basic knowledge of the Jolie language.

'''Mentors:''' ervin (ervin at kde dot org) fmontesi (famontesi at gmail dot com)
----

===KWin===

KDE's window manager

[http://techbase.kde.org/Projects/KWin Techbase page] - [https://mail.kde.org/mailman/listinfo/kwin Mailinglist] - IRC channel: #kwin on Freenode.

====Project: Window tabbing====

'''Brief explanation:'''
Window tabbing is a feature that allows you to group multiple application windows together to cover the same space. It is identical to what is already available in any modern web browser except it applies the the window as a whole. Window managers that have this feature available include Fluxbox and Ion. This feature was [http://bugs.kde.org/show_bug.cgi?id=42023 originally requested] in 2002.

'''Knowledge Prerequisite:''' C++ and Qt. Understanding of the X window system and Xlib is a benefit but not required.

'''Mentors:''' Lucas Murray (lmurray undefinedfire com)

====Project: Window tiling====

'''Brief explanation:'''
Window tiling is a technique of displaying application windows side-by-side without overlap. The position, size and layout of the windows can either be specified by the user or determined automatically to best fit the screen. Examples of existing tiling window managers include Awesome, XMonad, Ion and Ratpoison. One of the main advantages of tiling is that is makes application windows easy to navigate solely by the keyboard. This feature was [http://bugs.kde.org/show_bug.cgi?id=59338 originally requested] in 2003.

'''Expected results:'''
* Users should be able tile existing floating windows on-the-fly with simple keyboard shortcuts or mouse gestures.
* It should also be possible to run the entire desktop environment entirely in tiled mode (Enabled by configuration settings). In this mode new window would be added to the tiling grid by default yet can be removed by the user if required.
* The final tiling system should not interfere in any way with the existing floating window management.

'''Knowledge Prerequisite:''' C++ and Qt. Understanding of the X window system and Xlib is a benefit but not required.

'''Mentors:''' Lucas Murray (lmurray undefinedfire com)

----

=== digiKam ===

Photo Management program

[http://www.digikam.org digiKam project web site] - [https://mail.kde.org/mailman/listinfo/digikam-devel Mailinglist] - IRC channel: #digikam on Freenode.

====Project: High Dynamic Range (HDR) plugin====

'''Project Information:''' digiKam is an advanced digital photo management application for KDE, which makes importing and organizing digital photos a "snap". The photos are organized in albums which can be sorted chronologically, by folder layout or by custom collections. digiKam has an Image Editor which has its own plugin subsystem with some common tools e.g. red eye correction or Gamma correction. Additional plugins are provided with the main application to process advanced corrections on image like color management, noise reduction, or special effects. digiKam image editor support 16 bits color depth image internally. The goal of this project is to create a new plugin dedicated to create [http://en.wikipedia.org/wiki/High_dynamic_range_imaging HDR image].

'''Expected results:''' This project should implement an HDR tool will mix two or more (nearly) identical images having different exposure into a new image representing a wider dynamic range, which is closer to human perception of a photographic scene. [http://en.wikipedia.org/wiki/Tone_mapping Tone-mapping method] must be used to create HDR images. An open-source implementation is already available at [http://zynaddsubfx.sourceforge.net/other/tonemapping this url] and can be re-used as well. There is an old [https://bugs.kde.org/show_bug.cgi?id=144593 feature request].

'''Knowledge Pre-Requisite:''' C++/Qt.

'''Mentors:''' Gilles Caulier (caulier dot gilles at gmail dot com)

===KDE Telepathy Integration===
The [http://telepathy.freedesktop.org Telepathy Framework] is a desktop independent framework for real-time communication, such as VoIP and Instant Messaging. The projects below are some ideas for integrating telepathy into KDE.

If you want to know any more about Telepathy and KDE, drop by the irc channel #decibel and talk to '''grundleborg''', or use the mailing list decibel AT kde DOT org.

====Project: Message Logging====

'''Project Information:''' The Telepathy Framework allows for components which can watch channels whilst a user is interacting with them through another application. A program could be created to log the content of text instant messages into an Akonadi collection.

'''Expected results:''' This project should result in a telepathy watcher which is capable of logging the contents of text chats into an Akonadi collection. It should be possible to go off-the-record in a particular conversation from telepathy user interfaces and the logger should not save any messages in this situation. This project might also include modifying the Kopete logging plugin to use the same akonadi collection for logs, and making a migration tool from Kopete's old logging format to the new Akonadi collection.

'''Knowledge Pre-Requisite:''' C++/Qt, some basic knowledge of the Telepathy Framework is an advantage, but not necessary if you have an interest in real-time communcation and are prepared to learn fast.

'''Mentors:''' George Goldberg (grundleborg at gmail dot com) IRC: grundleborg

====Project: Telepathy Integration to any KDE application====

'''Project Information:''' Provide some collaborative feature or instant messaging integration for your favourite KDE application.

'''Expected results:''' This project should result in a collaborative feature or instant messaging integration being added to the chosen KDE application. It should be complete enough to provide at least basic functionality to end users, with the possibility of further improvement after the summer of code period ends.

'''Knowledge Pre-Requisite:''' C++/Qt, some basic knowledge of the Telepathy Framework is an advantage, but not necessary if you have an interest in real-time communcation and are prepared to learn fast.

'''Mentors:''' George Goldberg (grundleborg at gmail dot com) IRC: grundleborg. You should also discuss your idea with the development team of the application in which you would like to provide a Telepathy feature.

====Project: Telepathy Plasma Integration====

'''Project Information:''' Provide integration of presence and buddy information into plasma.

'''Expected results:''' You should provide multiple points of integration between presence and contact information and plasma. Plasmoids allowing the display and manipulation of your own presence information should be made available, building on the plasma applets and datengines already in existance for presence information. Plasma activities could also be made aware of presence, and the contacts plasmoid could be made aware of your buddies from Telepathy instant messaging accounts.

'''Knowledge Pre-Requisite:''' C++/Qt

'''Mentors:''' George Goldberg (grundleborg at gmail dot com) IRC: grundleborg. You should also discuss your ideas with the plasma development team before making a proposal.

Projects/Summer of Code/2009/Ideas

2009-02-22T13:05:41Z

Grundleborg: /* KDE Telepathy Integration */

== 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 kde-devel@kde.org. See [http://www.kde.org/mailinglists/ 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==
===Plasma===
[http://plasma.kde.org Website] - [https://mail.kde.org/mailman/listinfo/panel-dev Mailing list] - IRC channel: #plasma on Freenode.

====Project: Generic SOAP Plasma::Service====
'''Brief explanation:'''
The Service should be able to parse WSDL files and let Plasmoids connect to the described Webservices.

====Project: Simple Media Center components====
'''Brief explanation:'''
Plasma could offer a Media center mode, where features a really simple ui to browse media files and plasmoids that shows the actual media. All should be operable with mouse, keyboard or a simple remote control. the work could consist in building the whole thing or just writing a plasmoid able to browse media files, that is the most important missing part.
Mockups for it by Nuno Pinheiro can be seen [http://img213.imageshack.us/img213/3200/image3231picturefz5.png here] and [http://img26.imageshack.us/img26/3407/image323musicoloectionck2.png here]

'''Expected results:'''
An applet to browse and thumbnail media files, like the first mockup and control the actual media viewing applets, like the media player applet or the picture frame applet. At this stage the functionality will be really minimum

'''Knowledge prerequisite:'''
Knowledge of C++ and some familiarity with Qt especially QGraphicsView related classes.

'''Mentor:'''
Marco Martin (notmart a gmail dot org), or other Plasma developers. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Plasmate====
'''Brief explanation:'''
PlasMate is an application that gives people a way to start creating scripted plasmoids without worrying about anything except making their bits. It hides the whole metadata.desktop thing, the package layout details, making a Plasmoid package (aka "zipping up the directory"), uploading content and version control system.

'''Expected results:'''
Working application that one can do the tasks described above, making it easy to create and distribute a scripted plasmoid.

'''Knowledge prerequisite:'''
Knowledge of C++ and familiarity with Qt (QWidgets and QGraphicsView related classes).

'''Mentor:'''
Artur Duque de Souza (morpheuz a gmail dot org), or other Plasma developers. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Qt Kinetic + Plasma====
'''Brief explanation:'''
A layer over Qt Kinetic to provide a standardized set of "out of the box"
animations and bring them into libplasma. The work will be done with the Plasma developers to make this API as efficient as possible. The work will be based on Kinetic, the next framework for animations in Qt.

'''Expected results:'''
We can kill Plasma::Animator class. The goal is to bring fancy effects/animations in Plasma to have one of the best desktop ever.

'''Knowledge prerequisite:'''
Knowledge of C++, familiarity with QGraphicsView related classes and some familiarity with animations bits.

'''Mentor:'''
Alexis Ménard (alexis.menard at nokia dot com) or Artur Duque de Souza (morpheuz a gmail dot org). Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Eduactional layout====
'''Brief explanation:'''
A set of Containments and Plasmoids specifically designed for primary school
students.

'''Expected results:'''
A simplified panel containment that contains basic launchers and user feedback
for the student, a widget that allows teachers to provide context-specific
sets of applications and documents to the student (context being a combination
of the student logged in and the current class subject), a widget that
provides some basic teacher->student communication and status (e.g. what the
current assignment is, how long the student has been logged in, etc) and
optionally some widgets that work with KDE edu apps.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Desktop dock====
'''Brief explanation:'''
A MacOS style dock containment.

'''Expected results:'''
A containment that provides a similar user experience to the MacOS dock:
application launchers that are also task bar entries when the application is
active and a separate area for widgets such as the trash, battery, etc.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Kdm frontend using plasma====
'''Brief explanation:'''
A log-in screen layout manager for KDM that uses libplasma.

'''Expected results:'''
A KDM screen that is rendered completely using Plasma. This means both using
libplasma in KDM for the log in screen as well as writing Plasmoids for
entering the user name and password, listing users, session switching, etc.
Some of these widgets already exist for the desktop shell, so in some cases
this will be simply integrating existing Plasmoids, but in other cases will
mean writing new ones from the ground up.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Raptor====
'''Brief explanation:'''
Raptor aims to deliver a new kind of launch menu system for KDE. It is designed with usability and beauty in mind.
Raptor-Menu does not try to be the final answer to the menu question, instead aspires to be the best answer we can give, merging many ideas form modern desktop launch menus.

'''Expected results:'''
http://www.raptor-menu.org/

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: New Widget Explorer====
'''Brief explanation:'''
A new widget explorer that supports both our own widgets as well as others
more seamlessly.

'''Expected results:'''
A usable and pretty browser for widgets that allows a user to see an icon or
snapshot of the widget, select a widget to be placed in a containment, search
for a widget based on name/description, sort the widgets into categories, rate
widgets and provide ways to launch the online browsers and installers for both
native Plasmoids as well as third party tools such as Google Gadgets (which is
already supported in the Package class). All the required support
functionality already exists, this project is really about creating a
beautiful and dynamic user interface for looking through a widget catalog that
looks "Plasma".

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: D-Bus Interface====
'''Brief explanation:'''
A comprehensive set of D-Bus interfaces for the plasma-desktop Plasma shell.

'''Expected results:'''
The D-Bus interface must provide access to the Corona (DestkopCorona class),
which in turn will list all existing Containments and allow Containments to be
added, removed, saved, etc.

A D-Bus interface for each existing Containment will be made available as
well, which will provide a standard set of tools including listing, adding and
removing widgets as well as positioning and sizing for PanelContaiments. Ways
to control the wallpaper, if any, will also be provided in the per-Containment
D-Bus interface.

In turn, a D-Bus interface for each widget representing its available
contextual actions will be provided dynamically upon request.

Finally, the application D-Bus interface for things such as locking/unlocking
widgets will be designed and implemented.

The result will be a Plasma that is fully accessible via D-Bus.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Security====
'''Brief explanation:'''
A set of methods to define the existing security state of the Plasma
application, the security requirements of individual widgets, mechanisms to
respect those two sets of information and cryptographic signing of Plasmoid
packages.

'''Expected results:'''
A set of functionality descriptions will be enumerated (e.g. "Network access",
"Local file system access", etc.). Individual widgets will advertise which of
these functionality sets they require.

The plasma-overlay shell (used on the screensaver) will have code added to it
to respect these settings and not run widgets that advertise they need things
that aren't safe to provide on a screensaver (due to it being locked to
prevent others from accessing the system).

The plasma-desktop shell will gain the ability to be put into various lock down
states which will map to different sets of functionality. Part of this project
will be enumerate the various states, but that list must include "only load
trusted widgets", "no external access", "no local file system access".

The JavaScript engine will provide methods for each of the functionality sets
(e.g. a set of functions to access local files) which will be exported or not
based on the current Security state. This implies providing a security state
to the Corona which can then be passed on down to Applets and AppletScripts.

Finally, GPG signing of Plasmoid packages will be implemented along with a way
of checking the validity of these at runtime.

'''Knowledge prerequisite:'''
Knowledge of C++ and some experience with security.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

===Amarok===
A KDE music manager and player.

[http://amarok.kde.org Website] - [https://mail.kde.org/mailman/listinfo/amarok Mailing list] - IRC channel: #amarok on Freenode.

====Project: DLNA/UPnP Support====
'''Brief explanation:'''
Using the UPnP protocol users can, for example, share music from their Vista computer to a PS3. Amarok lacks any sort of UPnP support. Being able to act as a client or possibly a UPnP media server would be useful. In addition to that controlling a UPnP Media Renderer from within Amarok is possible with framework support.

The [http://coherence.beebits.net/ Coherence server] would likely be used since it is also intended to be used by a KIO slave.

'''Expected results:'''
*Using the Amarok Collection framework, create a plugin which allows Amarok to browse, search and play music off of a UPnP share. Playing music may use the UPnP KIO-slave, but more advanced functionality requires Amarok to handle this directly.
*Allow Amarok to share it's collection with other devices or control other devices via UPnP. This is secondary priority but it may be pretty easy with Coherence.
*Control UPnP Media Renderers (DMR: Digital Media Renderer device class in DLNA) from within Amarok.

'''Material Prerequisite:''' Some UPnP devices or computers to test with. Good excuse to buy a PS3. If you live in Europe a Philips Streamium DMR can be borrowed.

'''Knowledge Prerequisite:''' C++ and Qt. Coherence uses Python and D-Bus but doesn't need to be hacked on in the scope of this project.

And of course, understanding of UPnP networking and devices wouldn't hurt!

'''Mentor:''' Stecchino (bart.cerneels at kde dot org)
----

====Project: New meta-applets for the Context View====
'''Brief Explanation:'''
The Context View (CV) is currently used to display multiple applets that expose various information. However, due to the fact that each applet displays a certain type of information from one data source, there is significant amount of wasted space, and it is hard to show much more than 3 different pieces of data at once.

Meta-Applets are large applets that integrate date from multiple data sources in order to display more semantically related information coherently and efficiently. This could mean, for example, an applet that brings together lyrics, artist info, upcoming concerts, and related songs/artists.

More info is available here [http://amarok.kde.org/wiki/Proposals/More_Contexual_Information on the amarok wiki]

'''Expected Results:'''
Two or three (to be discussed with mentor in application writing process) applets that elegantly execute the ideas discussed above.

'''Knowledge prerequisite:'''
Knowledge of C++ is required, and some familiarity with Qt is helpful (especially QGraphicsView) but not necessary.

'''Mentor:'''
Leo Franchi (lfranchi AAAT kde DT org), or other Amarok developers. Contact at amarok@kde.org or #amarok on freenode.

----
====Project: Code regression test suite, implemented with QtScript ====
'''Brief explanation:'''
Amarok currently has no automatic code regression testing ("unit testing") in place at all. We very much need such a system in place (for as many components as possible), as we sometimes accidentally break certain components of the program by extending the code.

'''Expected results:'''
Code regression test suite for Amarok 2, implemented as one "Amarok-Script" (JavaScript), and internally split into multiple separate files and components, so that it would be possible to run arbitray tests (or the full suite) with very little effort, and no compiling, at any time. A requirement would also be testing of the collection scanning code (with test case collections), and testing of GUI correctness with the QTest library.

Also see:
http://amarok.kde.org/wiki/Development/Scripting_HowTo_2.0

A plus would be the generation of suitable statistics (possibly with document export), and possibly a visual representation of the data.

'''Material Prerequisite:'''
Amarok 2 trunk, KDE SVN account, git. Linux, OSX, or Windows.

'''Knowledge Prerequisite:'''
C++, Qt, KDE-Libs, QtScript (JavaScript), SVN, git, code testing.

'''Mentor:'''
Potentially one of several. Contact the amarok mailing list or ask in our IRC channel #amarok
----

====Project: Multilevel playlist sorting and sorting GUI ====
'''Brief explanation:'''
In Amarok 2.1, the layout of the playlist will be very configurable, being able to show as much or as little information about each track as each user might wish. Currently however, it is lacking an advanced system for sorting in the playlist, something that many users comming from Amarok 1 are missing. While simple sorting is relatively easy to do (and has already been partly implemented) we would like to aim a bit higher with Amarok 2.

'''Expected results:'''
A proxy model allowing the tracks in the playlist to be sorted using an arbitrary number of "layered" sort criteria. for instance, a sort setup could be "artist-album-tracknumber" This would sort all tracks by artist, then sort the tracks from each artist by album, and finally the tracks from each album based on track number. Once this model is working, a GUI is needed for making this functionality easilly avaialble to the user. Ideally this gui should tie in well with the playlist layout and search/filter stuff. Also, all track navigators (the classes that determines the order of playback, such as normal, random, random album and so on) need to be updated to use and work correctly with the new proxy model.

'''Material Prerequisite:'''
Amarok 2 trunk, KDE SVN account, Linux, OSX, or Windows.

'''Knowledge Prerequisite:'''
C++, Qt, KDE-Libs, SVN/git.

'''Mentor:'''
Nikolaj Hald Nielsen <nhnFreespirit@gmail.com> or contact the amarok mailing list or ask in our IRC channel #amarok
----

====Project: Playlist and Collection synchronization====
'''Brief explanation:'''
Mediadevices and services can add tracks and playlists to Amarok. Synchronization would automatically copy over tracks between the main Amarok Collection and devices or services or even between each other, either for a single playlist or the complete collection.
An algorithm needs to be implemented that does this automatically in a fast and efficient way with minimal intervention needed by the user.

'''Expected results:'''
Playlists set up on both the local collection and a portable mediaplayer will get synchronized the moment the player is connected.

'''Material Prerequisite:'''
Amarok 2 trunk, KDE SVN account, Linux, OSX, or Windows.

'''Knowledge Prerequisite:'''
C++, Qt, KDE-Libs, SVN/git.

'''Mentor:'''
Bart Cerneels <bart.cerneels at kde dot org> or contact the amarok mailing list or ask in our IRC channel #amarok

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

[http://phonon.kde.org Website] - [https://mail.kde.org/mailman/listinfo/phonon-backends Mailing list] - IRC channel: #phonon on Freenode.

====Project: Analyzer Support====
'''Brief explanation:'''
Applications such as Amarok and Dragon Player cannot have an analyzer or visualizations since they use Phonon which does not yet have the functionality to do it. The analyzer is the little bar graph thing which bounces around while music is playing. Users like it as its pretty and gives them a visual indication of their music playing.

'''Expected results:'''
As this project is working on extending a library, it has three parts: the Phonon library itself, a Phonon backend, and an application. The Phonon library would need the new API calls. At least phonon-xine and preferably 1 or 2 other Phonon backends must then implement the new API. An application like Amarok or Dragon Player should be used to demonstrate the use of the new API.

'''Knowledge Prerequisite:''' C++ and Qt. Experience with Xine or GStreamer is probably useful.

'''Mentor:''' Ian Monroe (contact on the [https://mail.kde.org/mailman/listinfo/amarok Amarok mailing list]) or possibly another Amarok or Phonon developer.
----
===Marble===
A desktop globe and map application. Also provides a map Qt Widget.

[http://edu.kde.org/marble/ Website] - [https://mail.kde.org/mailman/listinfo/marble-devel Mailing list]

====Project: Satellite navigation====
'''Brief explanation:'''
Satellite navigation devices have become widely used and the quality of openstreetmap data is becoming high, with some cities completely mapped already. Providing satellite navigation would be a useful desktop app for many as well as adding appeal for the use of KDE in embedded devices.

It also opens the possibility to bringing many of the free software ideals to interaction with the real world such as collaborative/social POIs.

'''Expected results:'''
The project would aim at getting a basic satellite navigation application running. The most basic features required would be getting the current location from a GPS device and providing route calculation to a destination.

The AndNav project (http://andnav.org) has already achieved something similar for Android so it could be a point of reference for how to use OpenStreetMap data to achieve this.

'''Knowledge Prerequisite:''' C++ and Qt. Experience with GPS devices under linux would be beneficial. Knowing java may also be of benefit in order to study the AndNav implementation.

'''Mentor:''' I (Alan Jones, skyphyr using gmail) am willing to mentor, but not having any GPS or Marble experience there is most likely somebody far more suited to undertake this role.

Comment from a Marble Project guy: Alan, please get in touch with the Marble Project. Our mailing list is marble-devel@kde.org. We'd like to support this project if a student is willing to do it.

----

====Project: Add Time support to 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 [http://code.google.com/apis/kml/documentation/kmlreference.html#timeprimitive <TimePrimitive>] and [http://code.google.com/apis/kml/documentation/kmlreference.html#timespan <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.

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

'''Mentor:''' Torsten Rahn / Patrick Spendrin.

----

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

[http://www.kdevelop.org Website] - [http://www.kdevelop.org/index.html?filename=mailinglist.html Mailing list] - IRC channel: #kdevelop on Freenode.

====Project: C++ Refactoring Support====
'''Brief explanation:'''
C++ support in KDevelop is already highly advanced, often equalling or surpassing what the user and compiler understand about the code. A few refactoring tools have been developed already, but they have been constructed in a crude fashion, generating code via string concatenation.

This project would aim to create a new system to implement refactoring tools, and to create, test and deploy several advanced refactoring tools for c++.

'''Expected results:'''
A library would be created to enable refactoring based on the c++ AST (abstract syntax tree). A reverse parser (AST to code) already exists, but classes would be created to allow programatic manipulation of an AST. Optionally this library would also cover a generic framework based on the duchain which would be re-usable by other languages and make refactoring plugins easier to develop and partially shareable between languages.

See the [http://api.kde.org/4.x-api/kdevplatform-apidocs/language/codegen/html/index.html Code Generation Design] documents for the initial plan for this project.

'''Knowledge Prerequisite:''' C++ and Qt. Experience with parsers would be a bonus.

'''Mentor:''' Hamish Rodda (Definition-Use chain code creator) rodda at kde/dot/org, possibly also David Nolden (DUChain guru)(to be confirmed)
----
=== KStars ===
KStars is a Desktop Planetarium for KDE. It displays a map of the sky and provides a lot of tools to learn astronomy, or to calculate and predict astronomical phenomena. See [[http://edu.kde.org/kstars|The KStars Homepage]] for more information.

==== Project: Community Integration for KStars ====
'''Project Information:''' KStars is a desktop planetarium program for KDE.

'''Brief explanation:''' Amateur Astronomy (which is one of the important use-cases of KStars) is typically done in communities. KStars permits users to save their own observing logs. It would be nicer if the user could share his observing logs with other users and see other observers' logs within KStars. It would also be nice if KStars had a map (using MarbleWidget) to display various Astronomy-related establishments (like amateur associations, observatories, research institutes). Another possible idea could be an observing report generator that would generate a report based on observing logs, and at the user's will, share it / post it on the internet.

'''Expected results:''' Implement some features that will make it easier for users to collaborate, as suggested above.

'''Knowledge Pre-Requisite:''' Required: C++. Prior knowledge of KIO_HTTP will help.

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

==== Project: FITS Image Overlay on the sky map. ====

'''Project Information:''' KStars is a desktop planetarium program for KDE.

'''Brief explanation:''' It would be great if a FITS image could be overlayed on the sky map so that the field drawn by KStars could be compared with the field in the FITS image. This would be of great benefit to observational astronomers, astrophotographers and comet / asteroid observers. An extension would be to download a DSS image using KStars' already existing tool and map it onto the sky map. The support of shapes like ds9 region, annotations on the sky, etc. could also be added.

'''Expected results:''' Functionality to overlay a FITS image or a DSS image obtained through KStars on to the sky map.

'''Knowledge Pre-Requisite:''' Required: C++. Prior knowledge of the FITS format and cfitsio library will help.

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

==== Project: Tools for Eclipses ====

'''Project Information:''' KStars is a desktop planetarium program for KDE. Currently, it can predict Solar Eclipses (using the Conjunctions tool), but cannot plot trajectory of shadows, or predict Lunar Eclipses.

'''Brief explanation:''' The project's primary goals are to include simulation and prediction (maybe using the existing Conjunction backend) of Lunar eclipses, and to create a tool to mark the trajectories of Solar and Lunar eclipse shadows on a map of the earth, including marking of totality, partial eclipse and annular eclipse. Something similar to this: [http://eclipse.gsfc.nasa.gov/SEmono/TSE2009/TSE2009iau/TSE2009-fig01.GIF]

'''Expected results:''' A complete set of tools to deal with eclipses.

'''Knowledge Pre-Requisite:''' C++

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

==== Project: KStars: Prettyfication ====
'''Project Information:''' KStars is a desktop planetarium program for KDE. The display is interactive, but it could be made more beautiful.

'''Brief explanation:''' We often get good suggestions for making KStars look better. Choose any of the following ideas: realistic rendering of asteroids and comets (including tails!); texture-mapping of the sky (this would mostly allow a photorealistic Milky Way); texture-mapping of planets; realistic sky-lighting effects (i.e., sky is blue in the daytime, gets gradually darker and colorful at sunset). One could also think of using Qt-GL rendering optionally.

'''Expected results:''' Successful implementation of any of these ideas to make KStars more beautiful.

'''Knowledge Pre-Requisite:''' Required: C++.

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

==== Project: Printable star charts ====
'''Project Information:''' KStars is a desktop planetarium program for KDE. It already has a print feature, but the printed chart could be much better.

'''Brief explanation:''' A printed star chart should at least include a legend explaining the symbols, and provide some information on the location of the user, the time and date, etc. The user would ideally be able to annotate the chart in various ways.

'''Expected results:''' Significant improvements to the printed star charts in KStars.

'''Knowledge Pre-Requisite:''' Basic programming skills, ability to quickly learn QPainter API.

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

==== Project: Many Moons ====
'''Project Information:''' KStars is a desktop planetarium program for KDE. It currently includes Earth's moon and 4 of Jupiter's moons.

'''Brief explanation:''' Generalize the JupiterMoons class to encapsulate any planet's Moons. The project will require some research to identify a public source of orbital data for planetary moons, most likely from a NASA webpage.

'''Expected results:''' Implement moons for at least Mars, Jupiter, Saturn, and Pluto with the new system.

'''Knowledge Pre-Requisite:''' Required: C++. The project doesn't require much contact with Qt/KDE APIs, and the existing JupiterMoons class can be used as a template.

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

==== Project: Support many catalogs ====
'''Project Information:''' KStars is a Desktop Planetarium for KDE. Currently KStars loads some star catalogs that are made available in a KStars native format.

'''Brief Explanation:''' KStars currently loads Tycho-2 and parts of USNO NOMAD catalog of stars. These catalogs are required to be in KStars' native format which uses the Hirearcheal Triangular Mesh to index regions in the sky. Popular star catalogs like USNO A organize stars and divide the sky into regions differently. Most users of astronomy software typically have one of these popular catalogs downloaded, and it would be great if KStars could support them somehow. While ability to read the non-native catalogs straight off is desirable, tools to convert these catalogs into KStars' native format would also help.

'''Expected Results:''' Implement support for at least the most popular catalogs like USNO-A2.0, Stellarium's Extra catalog, Cartes du Ciel's Tycho and Tycho-2 catalogs.

'''Knowledge Pre-Requisite:''' Required: C++. Ability to read documentation and quickly understand the existing code and ability to deal with binary files will help.

=== Kalzium ===

==== Project: Strigi integration ====

'''Project Information:'''
The goal of this project is to integrate Strigi as backend behind the periodic table and the glossary (and possible other elements).

'''Brief explanation:'''
The idea here is to have a GUI element that shows Strigi search results based on the element selected from the periodic table, or the item from the glossary, found on the users desktop. For element, this would include the elements name, and possible even the element symbol, if integration with last years Strigi-Chemistry GSoC project is achieved. For glossary items, a simple text search would suffice.

Another idea is to make it possible to querry like this: "Give me all molecules with a molecularweigth of 123u and at least one Carbon atom". For this we can use the [http://chem-file.sourceforge.net/ Chemical File Database] (or of course every other database, even those for [http://www.rcsb.org/pdb/home/home.do proteins].

'''Expected results:'''
* provide GUI for Strigi search results for an element selected in the periodic table
* provide GUI for Strigi search results for an glossary item

'''Knowledge Pre-Requisite:''' Required: C++, DBUS. Could be useful: Qt.

'''Mentor:''' Undecided.

----

==== Project: Kalzium beautification ====

'''Project Information:'''
Many parts of [http://edu.kde.org/kalzium Kalzium] could need a fresh up of the interface. For example, the main table should be written using Qt Model/View technique and for example use SVGs as a background. A first (uncomplete but working) code is already existing.

At the same time, many dialogs are not as beautiful as they could be. This project could also include the creation of a "simplified Kalzium" mode in which some parts of the feature set are hidden; this would be good for schools.

A third idea is to make more use of Plasma, for example improve the already written Plasmoids and/or extent Kalzium so that a Plasmoid could open a information dialog using Kalzium.

'''Expected results:'''
Depending on the chosen project for example a cleaned up codebase with an improved interface.

'''Knowledge Pre-Requisite:''' Required: C++, Qt, possible Plasma, Debug.

'''Mentor:''' Carsten Niehaus

=== KOffice ===
-----

'''Project:''' support for versionned OpenDocument files.

'''Explanation:''' The OpenDocument specification doesn't include support for multiple versions of the same document in a single file. But that feature is supported by OpenOffice.org. The objective for this Summer of Code is to add support for that versionning system in KOffice. Since KOffice shares the OpenDocument loading/saving code, it should be possible to add this support in every KOffice application in one Summer of Code.

'''Expected results:''' Being able to load a specific version of a file, and create/manage versions

'''Knowledge Pre-Requisite:''' C++, excellent english reading skills.

==== KWord ====
-----

==== KPresenter ====
-----

'''Project:''' Powerpoint import.

'''Explanation:''' From some years ago another gSoc project implemented the basis for powerpoint import, but it was never finished. So there is a good basis to start from. From a quick look it seems like styles support is the thing missing most to complete the work, however a thorough analysis of what is there and what is not needs to be done. And then the actual work needs to be done too, obviously

==== Krita ====

-----

'''Project:''' Sketch-pad interface for Krita

'''Project Information:''' Krita is a large and complex application built around a sophisticated painting engine. The goal of this project is to create a new interface around the Krita engine, specialized for quick sketching.

'''Expected results:''' This project should implement a new interface around Krita, presenting the user a single-layer plus tracing paper interface with a single freehand sketching tool. Easy to use and graphic color and paint operation (brush, pencil, eraser etc.) interface elements must be designed and implemented.

'''Knowledge Pre-Requisite:''' C++

-----

'''Project:''' Shader filters and generators for Krita

'''Project Information:''' Some initial work has already been done to make it possible to write filters in the OpenGL shading language. This project should take that initial code as a basis and implement a fully functioning plugin for Krita that allows filters and shaders to be executed on images in any colorspace.

'''Expected results:''' The plugin should have a finished user interface and make it possible to experiment with shader filters in an interactive way. Example filters must be implemented.

'''Knowledge Pre-Requisite:''' C++, OpenGL.

-----

'''Project:''' Animation support

'''Project Information:''' There is no support at all in Krita for animated images such as GIF or MNG or for working with images in an animation context, such as textures or backgrounds in applications like Blender. The applicant should first investigate user needs and use cases and then implement support in the user interface and in the import/export filters.

'''Expected results:''' A user-friendly way of working with animated images (i.e., not by making each frame a layer), but e.g. a docker that shows the the animation running in thumbnail format. Import/export filters for relevant file formats.

'''Knowledge Pre-Requisite:''' C++

-----

'''Project:''' PSD and Gimp plugins

'''Project Information:''' Krita is powerful enough to handle nearly all that the Gimp and Photoshop are capable of saving. This project is about creating dedicated file import/export filters that can handle as much of these file formats as possible, possibly through the use of existing libraries.

'''Expected results:''' 4 plugins: psd import/export and xcf import/export. These plugins should be able to handle complex files in all supported colorspaces. Ideally the project would also deliver a library to convert PSD/XF to/from Open Raster files.

'''Knowledge Pre-Requisite:''' C++

-----

'''Project:''' Workspaces

'''Project Information:''' A workspace is a loadable package of settings that finetune Krita for a particular purpose. A workspace could contain additional plugins (like an image browser plugin for batch operations) and a subset of resources. Example workspaces could be batch-editing of images, editing of animation sequences or painting or sketching.

'''Expected results:''' the user interface and framework to make packages of plugins and resources that users can switch between. Also extra plugins to extend krita in areas like batch processing that do not exist yet.

'''Knowledge Pre-Requisite:''' C++, artistic workflow

-----

'''Project:''' Kipi and digikam plugins compatibility

'''Project Information:''' Kipi and digikam provide lots of interesting plugins for working with 8 and 16 bit RGBA images. It would be great to be able to re-use those plugins from within Krita.

'''Expected results:''' Two plugins that load kipi and digikam filters into two new menus in the filter menu. Code to convert Krita layers to the digikam image representation and back, taking care of icc profiles and other niceties.

'''Knowledge Pre-Requisite:''' C++, artistic workflow

===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 [http://www.akonadi-project.org/ Akonadi].

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

[http://pim.kde.org/ Website] - [http://techbase.kde.org/Projects/PIM Project Wiki] - [https://mail.kde.org/mailman/listinfo/kde-pim Mailing list] - IRC channel: #kontact and #akonadi on Freenode.

====Project: Akonadi Janitor Agent====
'''Brief explanation:'''
An [[Development/Architecture/KDE4/Akonadi#Akonadi_Agents|Akonadi Agent]] is a service process for performing tasks on data provided through the Akonadi server.

The task of a Janitor agent would be to keep the user's PIM data neatly organized, for example deleting news feed items which are above a certain age and not flagged, moving last week's mail to an archive, etc.

'''Expected results:'''
* An Akonadi Agent capable of managing actions on Akonadi collections triggered by various criteria
* At least fully working implementation of actions based on "Expire" criterias for mail, e.g. delete mail above certain age, move/copy to different collection, etc
* GUI for configuring actions and their trigger criteria.

'''Knowledge Prerequisite:''' C++ and Qt. Ideally would already have gone through the [[Development/Tutorials/Akonadi/Resources|Akonadi Resource Tutorial]] since Resources are a specialized form of agents and thus share some of the API and characteristics.

'''Mentor:''' Kevin Krammer (kevin dot krammer at gmx dot at)
----
====Project: Alternative Akonadi Client Library====
'''Brief explanation:'''
Akonadi has a server/client like architecture where clients such as applications (but also resource) connect to a service and communicate with it through a suitable protocol.

Currently this is implemented for KDE in library called libakonadi-kde, however it is desirable to have additional implementations to be suitable for other library stacks, e.g. GLib/GObject based ones.

'''Expected results:'''
* A non-KDE based, preferably GLib/GObject based, Akonadi client library which
** can connect to a running Akonadi server
** fetch Akonadi collections
** fetch Akonadi items
** receive Akonadi change notifications (D-Bus based)

* A set of demo programs using the library which can
** recursively list (id and content MIME types) collections
** list (id and MIME type)oif items in a collection
** get the raw payload of an item

'''Knowledge Prerequisite:''' Depends on the chosen language and toolstack, e.g. C/Vala and GLib/GObject knowledge for a GLib/GObject based implementation.

'''Mentor:'''
----
====Project: Akonadi Consistency Checker====
'''Brief explanation:'''
Akonadi provides a structure of collections and items, similar to folders and files of a filesystem. Similarly the internal structures have to follow certain constraints which must not be violated. Nevertheless, this can happen as result of bugs, hardware failures, power loss and a million other reasons.

Filesystem checks exist to detect and possibly fix such situations. Such functionality would also be desirable for Akonadi.

'''Expected results:'''
* A consistency checker (built into the Akonadi server or stand-alone) that performs an extensible set of checks on the internal data structures of the Akonadi server, such as:
** items belong to existing collections
** collections are child collections of existing collections
** the collection tree is non-cyclic
** every collections is owned by an existing resource
** collection sub-trees are owned by the same resource
** every item payload part belongs to an existing item
** content type constraints of collections are not violated
** ...
* each check should be accompanied with recovery code, such as moving orphaned items into a lost+found folder
* integration into Akonadiconsole
* integration into unit-tests

'''Knowledge Prerequisite:''' C++ and Qt mandatory, SQL/database knowledge would be useful.

'''Mentor:''' Volker Krause <vkrause@kde.org>
----
====Project: Akonadi Resource for KMail local folders====
'''Brief explanation:'''
KMail stores its mail in a folder hierachy where each folder can contain mails '''and''' further sub folders.

While mails are stored either as mbox or maildir, additional index files are used to speed up message listing and to store message status and flags.

The already existing Akonadi MailDir resource can handle the maildir aspects but cannot handle either mbox based folders nor the additional information stored in the index files.

'''Expected results:'''
* a set of classes, probably as a library, capable of
** recursively listing the KMail folder tree given a base directory
** reading mails from the mbox and maildir folders in the KMail folder tree
** reading KMail index files
* an Akonadi resource using these classes to provide read-only access to all mails currently handled by KMail. The resource should also be able to transfer the flags stored in KMail's index file to Akonadi.
* Writing a migrator, similar to the current KResource->Akonadi migrator, that automatically reads the KMail config file and creates a Akonadi resource out of it. Optionally, depending on the overall progress, the migrator would also convert some of KMail's folder settings, like the folder icon or the expiry settings, to Akonadi collection attributes.

'''Knowledge Prerequisite:''' C++ and Qt mandatory, code analysis skills would be helpful regarding the handling of index files, refactoring skills if KMail's classes are to be extracted from KMail's code base (not required).

'''Mentor:''' Thomas McGuire <mcguire at kde dot org>
----

===KDE on Windows===
====Solid API backend====
'''Brief explanation:'''
The porting efforts to make KDE available across platforms do need some backends for system dependent tasks. One of the KDE libraries that bundles this is Solid.

'''Expected results:'''
You implement a backend for the [http://solid.kde.org Solid API] using WINAPI.
It has to work with both MinGW and MSVC compilers. Not every function is required, but the basic functionality (network access, removable drives/harddisks and power) should be implemented.

'''Knowledge Prerequisite:''' Windows API and C++/Qt. You should be able to set up the [http://techbase.kde.org/Getting_Started/Build/KDE4/Windows development environment] yourself and be familiar with it.

'''Mentor:''' Carlo Segato (brandon dot ml at gmail dot com) or Patrick Spendrin (ps_ml at gmx dot de)
----

===KDE Games===
====Project: Kolf 2 landscape object====
'''Brief explanation:'''
Kolf 2 is the second incarnation of KDE's minigolf game. We are currently rewriting it from scratch to take advantage of the powerful technologies provided by Qt 4 and KDE 4.

'''Expected results:'''
The task in this project is to create an object (or multiple objects) that provide(s) landscape textures, slopes, puddles and sand bunkers.

If you finish this task before the end of the summer, you can fill the remaining time by porting as much game objects from Kolf 1 to Kolf 2 as possible (e.g. windmills, floating blocks, signs or bumpers).

'''Knowledge Prerequisite:''' C++/Qt. Experiences in graphics programming with Qt will definitely help, as you are expected to implement 2D rendering for the landscape object.

'''Mentor:''' Stefan Majewsky (majewsky at gmx dot net) – Please contact me to let me help you to improve your proposal.

====Project: Kolf 2 editor interface====
'''Brief explanation:'''
The minigolf game Kolf provided an editor interface from the beginning, to allow the users to create custom courses. For Kolf 2, we are rewriting the game engine and can therefore not use the old editor code.

'''Expected results:'''
Your task would be to create an editor interface (may be embedded in the game, or a standalone application). A few basic parts are available, and the Kolf 2 engine supports generic methods to provide data to editor interfaces, and display editor overlays on the game view.

If you finish the editor interface before the end of the summer, you can fill the remaining time by porting as much game objects from Kolf 1 to Kolf 2 as possible (e.g. windmills, floating blocks, signs or bumpers).

'''Knowledge Prerequisite:''' C++/Qt. Experiences in model/view programming with Qt will be of good use.

'''Mentor:''' Stefan Majewsky (majewsky at gmx dot net) – Please contact me to let me help you to improve your proposal.

----

===Solid===
====Project: UPnP support through Jolie====
'''Brief explanation:'''
Adding UPnP support to Solid would mean offering transparent UPnP support to every KDE application using the Solid API, keeping them clean from every UPnP implementation aspect.
At the present, the [http://www.jolie-lang.org/ Jolie language] is being integrated with Plasma by means of the [http://websvn.kde.org/branches/work/~ervin/sodep/ QtSodep] library, soon to offer higher levels of abstraction.

The aim of this project would be to implement a UPnP protocol for Jolie, so that Solid could re-use the integration being made with QtSodep and gain UPnP support without having to worry about implementation details. Having a UPnP protocol implementation in Jolie would have other considerable consequences, like the possibility to act easily as a UPnP server or to compose and export existing UPnP services.

'''Expected results:'''
*The creation of a "upnp" protocol in Jolie, supporting at least the Internet Gateway Device (IGD) and MediaServer profiles.
*The creation of a UPnP Jolie service for UPnP service discovery and monitoring.
*Extending libsolid to expose UPnP devices found on the network.

'''Material Prerequisite:''' Having UPnP devices or software applications to test with. Most home routers support IGD, and there exists free software supporting the MediaServer profile ([http://mediatomb.cc/ mediatomb]).

'''Knowledge Prerequisite:''' Understanding of the UPnP specifications, Java (for the development of the Jolie UPnP protocol) and basic knowledge of the Jolie language.

'''Mentors:''' ervin (ervin at kde dot org) fmontesi (famontesi at gmail dot com)
----

===KWin===

KDE's window manager

[http://techbase.kde.org/Projects/KWin Techbase page] - [https://mail.kde.org/mailman/listinfo/kwin Mailinglist] - IRC channel: #kwin on Freenode.

====Project: Window tabbing====

'''Brief explanation:'''
Window tabbing is a feature that allows you to group multiple application windows together to cover the same space. It is identical to what is already available in any modern web browser except it applies the the window as a whole. Window managers that have this feature available include Fluxbox and Ion. This feature was [http://bugs.kde.org/show_bug.cgi?id=42023 originally requested] in 2002.

'''Knowledge Prerequisite:''' C++ and Qt. Understanding of the X window system and Xlib is a benefit but not required.

'''Mentors:''' Lucas Murray (lmurray undefinedfire com)

====Project: Window tiling====

'''Brief explanation:'''
Window tiling is a technique of displaying application windows side-by-side without overlap. The position, size and layout of the windows can either be specified by the user or determined automatically to best fit the screen. Examples of existing tiling window managers include Awesome, XMonad, Ion and Ratpoison. One of the main advantages of tiling is that is makes application windows easy to navigate solely by the keyboard. This feature was [http://bugs.kde.org/show_bug.cgi?id=59338 originally requested] in 2003.

'''Expected results:'''
* Users should be able tile existing floating windows on-the-fly with simple keyboard shortcuts or mouse gestures.
* It should also be possible to run the entire desktop environment entirely in tiled mode (Enabled by configuration settings). In this mode new window would be added to the tiling grid by default yet can be removed by the user if required.
* The final tiling system should not interfere in any way with the existing floating window management.

'''Knowledge Prerequisite:''' C++ and Qt. Understanding of the X window system and Xlib is a benefit but not required.

'''Mentors:''' Lucas Murray (lmurray undefinedfire com)

----

=== digiKam ===

Photo Management program

[http://www.digikam.org digiKam project web site] - [https://mail.kde.org/mailman/listinfo/digikam-devel Mailinglist] - IRC channel: #digikam on Freenode.

====Project: High Dynamic Range (HDR) plugin====

'''Project Information:''' digiKam is an advanced digital photo management application for KDE, which makes importing and organizing digital photos a "snap". The photos are organized in albums which can be sorted chronologically, by folder layout or by custom collections. digiKam has an Image Editor which has its own plugin subsystem with some common tools e.g. red eye correction or Gamma correction. Additional plugins are provided with the main application to process advanced corrections on image like color management, noise reduction, or special effects. digiKam image editor support 16 bits color depth image internally. The goal of this project is to create a new plugin dedicated to create [http://en.wikipedia.org/wiki/High_dynamic_range_imaging HDR image].

'''Expected results:''' This project should implement an HDR tool will mix two or more (nearly) identical images having different exposure into a new image representing a wider dynamic range, which is closer to human perception of a photographic scene. [http://en.wikipedia.org/wiki/Tone_mapping Tone-mapping method] must be used to create HDR images. An open-source implementation is already available at [http://zynaddsubfx.sourceforge.net/other/tonemapping this url] and can be re-used as well. There is an old [https://bugs.kde.org/show_bug.cgi?id=144593 feature request].

'''Knowledge Pre-Requisite:''' C++/Qt.

'''Mentors:''' Gilles Caulier (caulier dot gilles at gmail dot com)

===KDE Telepathy Integration===
The [http://telepathy.freedesktop.org Telepathy Framework] is a desktop independent framework for real-time communication, such as VoIP and Instant Messaging. The projects below are some ideas for integrating telepathy into KDE.

====Project: Message Logging====

'''Project Information:''' The Telepathy Framework allows for components which can watch channels whilst a user is interacting with them through another application. A program could be created to log the content of text instant messages into an Akonadi collection.

'''Expected results:''' This project should result in a telepathy watcher which is capable of logging the contents of text chats into an Akonadi collection. It should be possible to go off-the-record in a particular conversation from telepathy user interfaces and the logger should not save any messages in this situation. This project might also include modifying the Kopete logging plugin to use the same akonadi collection for logs, and making a migration tool from Kopete's old logging format to the new Akonadi collection.

'''Knowledge Pre-Requisite:''' C++/Qt, some basic knowledge of the Telepathy Framework is an advantage, but not necessary if you have an interest in real-time communcation and are prepared to learn fast.

'''Mentors:''' George Goldberg (grundleborg at gmail dot com) IRC: grundleborg

====Project: Telepathy Integration to any KDE application====

'''Project Information:''' Provide some collaborative feature or instant messaging integration for your favourite KDE application.

'''Expected results:''' This project should result in a collaborative feature or instant messaging integration being added to the chosen KDE application. It should be complete enough to provide at least basic functionality to end users, with the possibility of further improvement after the summer of code period ends.

'''Knowledge Pre-Requisite:''' C++/Qt, some basic knowledge of the Telepathy Framework is an advantage, but not necessary if you have an interest in real-time communcation and are prepared to learn fast.

'''Mentors:''' George Goldberg (grundleborg at gmail dot com) IRC: grundleborg. You should also discuss your idea with the development team of the application in which you would like to provide a Telepathy feature.

Projects/Summer of Code/2009/Ideas

2009-02-22T12:54:56Z

Grundleborg: Add telepathy section

== 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 kde-devel@kde.org. See [http://www.kde.org/mailinglists/ 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==
===Plasma===
[http://plasma.kde.org Website] - [https://mail.kde.org/mailman/listinfo/panel-dev Mailing list] - IRC channel: #plasma on Freenode.

====Project: Generic SOAP Plasma::Service====
'''Brief explanation:'''
The Service should be able to parse WSDL files and let Plasmoids connect to the described Webservices.

====Project: Simple Media Center components====
'''Brief explanation:'''
Plasma could offer a Media center mode, where features a really simple ui to browse media files and plasmoids that shows the actual media. All should be operable with mouse, keyboard or a simple remote control. the work could consist in building the whole thing or just writing a plasmoid able to browse media files, that is the most important missing part.
Mockups for it by Nuno Pinheiro can be seen [http://img213.imageshack.us/img213/3200/image3231picturefz5.png here] and [http://img26.imageshack.us/img26/3407/image323musicoloectionck2.png here]

'''Expected results:'''
An applet to browse and thumbnail media files, like the first mockup and control the actual media viewing applets, like the media player applet or the picture frame applet. At this stage the functionality will be really minimum

'''Knowledge prerequisite:'''
Knowledge of C++ and some familiarity with Qt especially QGraphicsView related classes.

'''Mentor:'''
Marco Martin (notmart a gmail dot org), or other Plasma developers. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Plasmate====
'''Brief explanation:'''
PlasMate is an application that gives people a way to start creating scripted plasmoids without worrying about anything except making their bits. It hides the whole metadata.desktop thing, the package layout details, making a Plasmoid package (aka "zipping up the directory"), uploading content and version control system.

'''Expected results:'''
Working application that one can do the tasks described above, making it easy to create and distribute a scripted plasmoid.

'''Knowledge prerequisite:'''
Knowledge of C++ and familiarity with Qt (QWidgets and QGraphicsView related classes).

'''Mentor:'''
Artur Duque de Souza (morpheuz a gmail dot org), or other Plasma developers. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Qt Kinetic + Plasma====
'''Brief explanation:'''
A layer over Qt Kinetic to provide a standardized set of "out of the box"
animations and bring them into libplasma. The work will be done with the Plasma developers to make this API as efficient as possible. The work will be based on Kinetic, the next framework for animations in Qt.

'''Expected results:'''
We can kill Plasma::Animator class. The goal is to bring fancy effects/animations in Plasma to have one of the best desktop ever.

'''Knowledge prerequisite:'''
Knowledge of C++, familiarity with QGraphicsView related classes and some familiarity with animations bits.

'''Mentor:'''
Alexis Ménard (alexis.menard at nokia dot com) or Artur Duque de Souza (morpheuz a gmail dot org). Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Eduactional layout====
'''Brief explanation:'''
A set of Containments and Plasmoids specifically designed for primary school
students.

'''Expected results:'''
A simplified panel containment that contains basic launchers and user feedback
for the student, a widget that allows teachers to provide context-specific
sets of applications and documents to the student (context being a combination
of the student logged in and the current class subject), a widget that
provides some basic teacher->student communication and status (e.g. what the
current assignment is, how long the student has been logged in, etc) and
optionally some widgets that work with KDE edu apps.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Desktop dock====
'''Brief explanation:'''
A MacOS style dock containment.

'''Expected results:'''
A containment that provides a similar user experience to the MacOS dock:
application launchers that are also task bar entries when the application is
active and a separate area for widgets such as the trash, battery, etc.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Kdm frontend using plasma====
'''Brief explanation:'''
A log-in screen layout manager for KDM that uses libplasma.

'''Expected results:'''
A KDM screen that is rendered completely using Plasma. This means both using
libplasma in KDM for the log in screen as well as writing Plasmoids for
entering the user name and password, listing users, session switching, etc.
Some of these widgets already exist for the desktop shell, so in some cases
this will be simply integrating existing Plasmoids, but in other cases will
mean writing new ones from the ground up.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Raptor====
'''Brief explanation:'''
Raptor aims to deliver a new kind of launch menu system for KDE. It is designed with usability and beauty in mind.
Raptor-Menu does not try to be the final answer to the menu question, instead aspires to be the best answer we can give, merging many ideas form modern desktop launch menus.

'''Expected results:'''
http://www.raptor-menu.org/

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: New Widget Explorer====
'''Brief explanation:'''
A new widget explorer that supports both our own widgets as well as others
more seamlessly.

'''Expected results:'''
A usable and pretty browser for widgets that allows a user to see an icon or
snapshot of the widget, select a widget to be placed in a containment, search
for a widget based on name/description, sort the widgets into categories, rate
widgets and provide ways to launch the online browsers and installers for both
native Plasmoids as well as third party tools such as Google Gadgets (which is
already supported in the Package class). All the required support
functionality already exists, this project is really about creating a
beautiful and dynamic user interface for looking through a widget catalog that
looks "Plasma".

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: D-Bus Interface====
'''Brief explanation:'''
A comprehensive set of D-Bus interfaces for the plasma-desktop Plasma shell.

'''Expected results:'''
The D-Bus interface must provide access to the Corona (DestkopCorona class),
which in turn will list all existing Containments and allow Containments to be
added, removed, saved, etc.

A D-Bus interface for each existing Containment will be made available as
well, which will provide a standard set of tools including listing, adding and
removing widgets as well as positioning and sizing for PanelContaiments. Ways
to control the wallpaper, if any, will also be provided in the per-Containment
D-Bus interface.

In turn, a D-Bus interface for each widget representing its available
contextual actions will be provided dynamically upon request.

Finally, the application D-Bus interface for things such as locking/unlocking
widgets will be designed and implemented.

The result will be a Plasma that is fully accessible via D-Bus.

'''Knowledge prerequisite:'''
Knowledge of C++.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

====Project: Security====
'''Brief explanation:'''
A set of methods to define the existing security state of the Plasma
application, the security requirements of individual widgets, mechanisms to
respect those two sets of information and cryptographic signing of Plasmoid
packages.

'''Expected results:'''
A set of functionality descriptions will be enumerated (e.g. "Network access",
"Local file system access", etc.). Individual widgets will advertise which of
these functionality sets they require.

The plasma-overlay shell (used on the screensaver) will have code added to it
to respect these settings and not run widgets that advertise they need things
that aren't safe to provide on a screensaver (due to it being locked to
prevent others from accessing the system).

The plasma-desktop shell will gain the ability to be put into various lock down
states which will map to different sets of functionality. Part of this project
will be enumerate the various states, but that list must include "only load
trusted widgets", "no external access", "no local file system access".

The JavaScript engine will provide methods for each of the functionality sets
(e.g. a set of functions to access local files) which will be exported or not
based on the current Security state. This implies providing a security state
to the Corona which can then be passed on down to Applets and AppletScripts.

Finally, GPG signing of Plasmoid packages will be implemented along with a way
of checking the validity of these at runtime.

'''Knowledge prerequisite:'''
Knowledge of C++ and some experience with security.

'''Mentor:'''
Plasma team. Contact at plasma-devel@kde.org or #plasma on freenode.

===Amarok===
A KDE music manager and player.

[http://amarok.kde.org Website] - [https://mail.kde.org/mailman/listinfo/amarok Mailing list] - IRC channel: #amarok on Freenode.

====Project: DLNA/UPnP Support====
'''Brief explanation:'''
Using the UPnP protocol users can, for example, share music from their Vista computer to a PS3. Amarok lacks any sort of UPnP support. Being able to act as a client or possibly a UPnP media server would be useful. In addition to that controlling a UPnP Media Renderer from within Amarok is possible with framework support.

The [http://coherence.beebits.net/ Coherence server] would likely be used since it is also intended to be used by a KIO slave.

'''Expected results:'''
*Using the Amarok Collection framework, create a plugin which allows Amarok to browse, search and play music off of a UPnP share. Playing music may use the UPnP KIO-slave, but more advanced functionality requires Amarok to handle this directly.
*Allow Amarok to share it's collection with other devices or control other devices via UPnP. This is secondary priority but it may be pretty easy with Coherence.
*Control UPnP Media Renderers (DMR: Digital Media Renderer device class in DLNA) from within Amarok.

'''Material Prerequisite:''' Some UPnP devices or computers to test with. Good excuse to buy a PS3. If you live in Europe a Philips Streamium DMR can be borrowed.

'''Knowledge Prerequisite:''' C++ and Qt. Coherence uses Python and D-Bus but doesn't need to be hacked on in the scope of this project.

And of course, understanding of UPnP networking and devices wouldn't hurt!

'''Mentor:''' Stecchino (bart.cerneels at kde dot org)
----

====Project: New meta-applets for the Context View====
'''Brief Explanation:'''
The Context View (CV) is currently used to display multiple applets that expose various information. However, due to the fact that each applet displays a certain type of information from one data source, there is significant amount of wasted space, and it is hard to show much more than 3 different pieces of data at once.

Meta-Applets are large applets that integrate date from multiple data sources in order to display more semantically related information coherently and efficiently. This could mean, for example, an applet that brings together lyrics, artist info, upcoming concerts, and related songs/artists.

More info is available here [http://amarok.kde.org/wiki/Proposals/More_Contexual_Information on the amarok wiki]

'''Expected Results:'''
Two or three (to be discussed with mentor in application writing process) applets that elegantly execute the ideas discussed above.

'''Knowledge prerequisite:'''
Knowledge of C++ is required, and some familiarity with Qt is helpful (especially QGraphicsView) but not necessary.

'''Mentor:'''
Leo Franchi (lfranchi AAAT kde DT org), or other Amarok developers. Contact at amarok@kde.org or #amarok on freenode.

----
====Project: Code regression test suite, implemented with QtScript ====
'''Brief explanation:'''
Amarok currently has no automatic code regression testing ("unit testing") in place at all. We very much need such a system in place (for as many components as possible), as we sometimes accidentally break certain components of the program by extending the code.

'''Expected results:'''
Code regression test suite for Amarok 2, implemented as one "Amarok-Script" (JavaScript), and internally split into multiple separate files and components, so that it would be possible to run arbitray tests (or the full suite) with very little effort, and no compiling, at any time. A requirement would also be testing of the collection scanning code (with test case collections), and testing of GUI correctness with the QTest library.

Also see:
http://amarok.kde.org/wiki/Development/Scripting_HowTo_2.0

A plus would be the generation of suitable statistics (possibly with document export), and possibly a visual representation of the data.

'''Material Prerequisite:'''
Amarok 2 trunk, KDE SVN account, git. Linux, OSX, or Windows.

'''Knowledge Prerequisite:'''
C++, Qt, KDE-Libs, QtScript (JavaScript), SVN, git, code testing.

'''Mentor:'''
Potentially one of several. Contact the amarok mailing list or ask in our IRC channel #amarok
----

====Project: Multilevel playlist sorting and sorting GUI ====
'''Brief explanation:'''
In Amarok 2.1, the layout of the playlist will be very configurable, being able to show as much or as little information about each track as each user might wish. Currently however, it is lacking an advanced system for sorting in the playlist, something that many users comming from Amarok 1 are missing. While simple sorting is relatively easy to do (and has already been partly implemented) we would like to aim a bit higher with Amarok 2.

'''Expected results:'''
A proxy model allowing the tracks in the playlist to be sorted using an arbitrary number of "layered" sort criteria. for instance, a sort setup could be "artist-album-tracknumber" This would sort all tracks by artist, then sort the tracks from each artist by album, and finally the tracks from each album based on track number. Once this model is working, a GUI is needed for making this functionality easilly avaialble to the user. Ideally this gui should tie in well with the playlist layout and search/filter stuff. Also, all track navigators (the classes that determines the order of playback, such as normal, random, random album and so on) need to be updated to use and work correctly with the new proxy model.

'''Material Prerequisite:'''
Amarok 2 trunk, KDE SVN account, Linux, OSX, or Windows.

'''Knowledge Prerequisite:'''
C++, Qt, KDE-Libs, SVN/git.

'''Mentor:'''
Nikolaj Hald Nielsen <nhnFreespirit@gmail.com> or contact the amarok mailing list or ask in our IRC channel #amarok
----

====Project: Playlist and Collection synchronization====
'''Brief explanation:'''
Mediadevices and services can add tracks and playlists to Amarok. Synchronization would automatically copy over tracks between the main Amarok Collection and devices or services or even between each other, either for a single playlist or the complete collection.
An algorithm needs to be implemented that does this automatically in a fast and efficient way with minimal intervention needed by the user.

'''Expected results:'''
Playlists set up on both the local collection and a portable mediaplayer will get synchronized the moment the player is connected.

'''Material Prerequisite:'''
Amarok 2 trunk, KDE SVN account, Linux, OSX, or Windows.

'''Knowledge Prerequisite:'''
C++, Qt, KDE-Libs, SVN/git.

'''Mentor:'''
Bart Cerneels <bart.cerneels at kde dot org> or contact the amarok mailing list or ask in our IRC channel #amarok

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

[http://phonon.kde.org Website] - [https://mail.kde.org/mailman/listinfo/phonon-backends Mailing list] - IRC channel: #phonon on Freenode.

====Project: Analyzer Support====
'''Brief explanation:'''
Applications such as Amarok and Dragon Player cannot have an analyzer or visualizations since they use Phonon which does not yet have the functionality to do it. The analyzer is the little bar graph thing which bounces around while music is playing. Users like it as its pretty and gives them a visual indication of their music playing.

'''Expected results:'''
As this project is working on extending a library, it has three parts: the Phonon library itself, a Phonon backend, and an application. The Phonon library would need the new API calls. At least phonon-xine and preferably 1 or 2 other Phonon backends must then implement the new API. An application like Amarok or Dragon Player should be used to demonstrate the use of the new API.

'''Knowledge Prerequisite:''' C++ and Qt. Experience with Xine or GStreamer is probably useful.

'''Mentor:''' Ian Monroe (contact on the [https://mail.kde.org/mailman/listinfo/amarok Amarok mailing list]) or possibly another Amarok or Phonon developer.
----
===Marble===
A desktop globe and map application. Also provides a map Qt Widget.

[http://edu.kde.org/marble/ Website] - [https://mail.kde.org/mailman/listinfo/marble-devel Mailing list]

====Project: Satellite navigation====
'''Brief explanation:'''
Satellite navigation devices have become widely used and the quality of openstreetmap data is becoming high, with some cities completely mapped already. Providing satellite navigation would be a useful desktop app for many as well as adding appeal for the use of KDE in embedded devices.

It also opens the possibility to bringing many of the free software ideals to interaction with the real world such as collaborative/social POIs.

'''Expected results:'''
The project would aim at getting a basic satellite navigation application running. The most basic features required would be getting the current location from a GPS device and providing route calculation to a destination.

The AndNav project (http://andnav.org) has already achieved something similar for Android so it could be a point of reference for how to use OpenStreetMap data to achieve this.

'''Knowledge Prerequisite:''' C++ and Qt. Experience with GPS devices under linux would be beneficial. Knowing java may also be of benefit in order to study the AndNav implementation.

'''Mentor:''' I (Alan Jones, skyphyr using gmail) am willing to mentor, but not having any GPS or Marble experience there is most likely somebody far more suited to undertake this role.

Comment from a Marble Project guy: Alan, please get in touch with the Marble Project. Our mailing list is marble-devel@kde.org. We'd like to support this project if a student is willing to do it.

----

====Project: Add Time support to 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 [http://code.google.com/apis/kml/documentation/kmlreference.html#timeprimitive <TimePrimitive>] and [http://code.google.com/apis/kml/documentation/kmlreference.html#timespan <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.

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

'''Mentor:''' Torsten Rahn / Patrick Spendrin.

----

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

[http://www.kdevelop.org Website] - [http://www.kdevelop.org/index.html?filename=mailinglist.html Mailing list] - IRC channel: #kdevelop on Freenode.

====Project: C++ Refactoring Support====
'''Brief explanation:'''
C++ support in KDevelop is already highly advanced, often equalling or surpassing what the user and compiler understand about the code. A few refactoring tools have been developed already, but they have been constructed in a crude fashion, generating code via string concatenation.

This project would aim to create a new system to implement refactoring tools, and to create, test and deploy several advanced refactoring tools for c++.

'''Expected results:'''
A library would be created to enable refactoring based on the c++ AST (abstract syntax tree). A reverse parser (AST to code) already exists, but classes would be created to allow programatic manipulation of an AST. Optionally this library would also cover a generic framework based on the duchain which would be re-usable by other languages and make refactoring plugins easier to develop and partially shareable between languages.

See the [http://api.kde.org/4.x-api/kdevplatform-apidocs/language/codegen/html/index.html Code Generation Design] documents for the initial plan for this project.

'''Knowledge Prerequisite:''' C++ and Qt. Experience with parsers would be a bonus.

'''Mentor:''' Hamish Rodda (Definition-Use chain code creator) rodda at kde/dot/org, possibly also David Nolden (DUChain guru)(to be confirmed)
----
=== KStars ===
KStars is a Desktop Planetarium for KDE. It displays a map of the sky and provides a lot of tools to learn astronomy, or to calculate and predict astronomical phenomena. See [[http://edu.kde.org/kstars|The KStars Homepage]] for more information.

==== Project: Community Integration for KStars ====
'''Project Information:''' KStars is a desktop planetarium program for KDE.

'''Brief explanation:''' Amateur Astronomy (which is one of the important use-cases of KStars) is typically done in communities. KStars permits users to save their own observing logs. It would be nicer if the user could share his observing logs with other users and see other observers' logs within KStars. It would also be nice if KStars had a map (using MarbleWidget) to display various Astronomy-related establishments (like amateur associations, observatories, research institutes). Another possible idea could be an observing report generator that would generate a report based on observing logs, and at the user's will, share it / post it on the internet.

'''Expected results:''' Implement some features that will make it easier for users to collaborate, as suggested above.

'''Knowledge Pre-Requisite:''' Required: C++. Prior knowledge of KIO_HTTP will help.

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

==== Project: FITS Image Overlay on the sky map. ====

'''Project Information:''' KStars is a desktop planetarium program for KDE.

'''Brief explanation:''' It would be great if a FITS image could be overlayed on the sky map so that the field drawn by KStars could be compared with the field in the FITS image. This would be of great benefit to observational astronomers, astrophotographers and comet / asteroid observers. An extension would be to download a DSS image using KStars' already existing tool and map it onto the sky map. The support of shapes like ds9 region, annotations on the sky, etc. could also be added.

'''Expected results:''' Functionality to overlay a FITS image or a DSS image obtained through KStars on to the sky map.

'''Knowledge Pre-Requisite:''' Required: C++. Prior knowledge of the FITS format and cfitsio library will help.

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

==== Project: Tools for Eclipses ====

'''Project Information:''' KStars is a desktop planetarium program for KDE. Currently, it can predict Solar Eclipses (using the Conjunctions tool), but cannot plot trajectory of shadows, or predict Lunar Eclipses.

'''Brief explanation:''' The project's primary goals are to include simulation and prediction (maybe using the existing Conjunction backend) of Lunar eclipses, and to create a tool to mark the trajectories of Solar and Lunar eclipse shadows on a map of the earth, including marking of totality, partial eclipse and annular eclipse. Something similar to this: [http://eclipse.gsfc.nasa.gov/SEmono/TSE2009/TSE2009iau/TSE2009-fig01.GIF]

'''Expected results:''' A complete set of tools to deal with eclipses.

'''Knowledge Pre-Requisite:''' C++

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

==== Project: KStars: Prettyfication ====
'''Project Information:''' KStars is a desktop planetarium program for KDE. The display is interactive, but it could be made more beautiful.

'''Brief explanation:''' We often get good suggestions for making KStars look better. Choose any of the following ideas: realistic rendering of asteroids and comets (including tails!); texture-mapping of the sky (this would mostly allow a photorealistic Milky Way); texture-mapping of planets; realistic sky-lighting effects (i.e., sky is blue in the daytime, gets gradually darker and colorful at sunset). One could also think of using Qt-GL rendering optionally.

'''Expected results:''' Successful implementation of any of these ideas to make KStars more beautiful.

'''Knowledge Pre-Requisite:''' Required: C++.

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

==== Project: Printable star charts ====
'''Project Information:''' KStars is a desktop planetarium program for KDE. It already has a print feature, but the printed chart could be much better.

'''Brief explanation:''' A printed star chart should at least include a legend explaining the symbols, and provide some information on the location of the user, the time and date, etc. The user would ideally be able to annotate the chart in various ways.

'''Expected results:''' Significant improvements to the printed star charts in KStars.

'''Knowledge Pre-Requisite:''' Basic programming skills, ability to quickly learn QPainter API.

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

==== Project: Many Moons ====
'''Project Information:''' KStars is a desktop planetarium program for KDE. It currently includes Earth's moon and 4 of Jupiter's moons.

'''Brief explanation:''' Generalize the JupiterMoons class to encapsulate any planet's Moons. The project will require some research to identify a public source of orbital data for planetary moons, most likely from a NASA webpage.

'''Expected results:''' Implement moons for at least Mars, Jupiter, Saturn, and Pluto with the new system.

'''Knowledge Pre-Requisite:''' Required: C++. The project doesn't require much contact with Qt/KDE APIs, and the existing JupiterMoons class can be used as a template.

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

==== Project: Support many catalogs ====
'''Project Information:''' KStars is a Desktop Planetarium for KDE. Currently KStars loads some star catalogs that are made available in a KStars native format.

'''Brief Explanation:''' KStars currently loads Tycho-2 and parts of USNO NOMAD catalog of stars. These catalogs are required to be in KStars' native format which uses the Hirearcheal Triangular Mesh to index regions in the sky. Popular star catalogs like USNO A organize stars and divide the sky into regions differently. Most users of astronomy software typically have one of these popular catalogs downloaded, and it would be great if KStars could support them somehow. While ability to read the non-native catalogs straight off is desirable, tools to convert these catalogs into KStars' native format would also help.

'''Expected Results:''' Implement support for at least the most popular catalogs like USNO-A2.0, Stellarium's Extra catalog, Cartes du Ciel's Tycho and Tycho-2 catalogs.

'''Knowledge Pre-Requisite:''' Required: C++. Ability to read documentation and quickly understand the existing code and ability to deal with binary files will help.

=== Kalzium ===

==== Project: Strigi integration ====

'''Project Information:'''
The goal of this project is to integrate Strigi as backend behind the periodic table and the glossary (and possible other elements).

'''Brief explanation:'''
The idea here is to have a GUI element that shows Strigi search results based on the element selected from the periodic table, or the item from the glossary, found on the users desktop. For element, this would include the elements name, and possible even the element symbol, if integration with last years Strigi-Chemistry GSoC project is achieved. For glossary items, a simple text search would suffice.

Another idea is to make it possible to querry like this: "Give me all molecules with a molecularweigth of 123u and at least one Carbon atom". For this we can use the [http://chem-file.sourceforge.net/ Chemical File Database] (or of course every other database, even those for [http://www.rcsb.org/pdb/home/home.do proteins].

'''Expected results:'''
* provide GUI for Strigi search results for an element selected in the periodic table
* provide GUI for Strigi search results for an glossary item

'''Knowledge Pre-Requisite:''' Required: C++, DBUS. Could be useful: Qt.

'''Mentor:''' Undecided.

----

==== Project: Kalzium beautification ====

'''Project Information:'''
Many parts of [http://edu.kde.org/kalzium Kalzium] could need a fresh up of the interface. For example, the main table should be written using Qt Model/View technique and for example use SVGs as a background. A first (uncomplete but working) code is already existing.

At the same time, many dialogs are not as beautiful as they could be. This project could also include the creation of a "simplified Kalzium" mode in which some parts of the feature set are hidden; this would be good for schools.

A third idea is to make more use of Plasma, for example improve the already written Plasmoids and/or extent Kalzium so that a Plasmoid could open a information dialog using Kalzium.

'''Expected results:'''
Depending on the chosen project for example a cleaned up codebase with an improved interface.

'''Knowledge Pre-Requisite:''' Required: C++, Qt, possible Plasma, Debug.

'''Mentor:''' Carsten Niehaus

=== KOffice ===
-----

'''Project:''' support for versionned OpenDocument files.

'''Explanation:''' The OpenDocument specification doesn't include support for multiple versions of the same document in a single file. But that feature is supported by OpenOffice.org. The objective for this Summer of Code is to add support for that versionning system in KOffice. Since KOffice shares the OpenDocument loading/saving code, it should be possible to add this support in every KOffice application in one Summer of Code.

'''Expected results:''' Being able to load a specific version of a file, and create/manage versions

'''Knowledge Pre-Requisite:''' C++, excellent english reading skills.

==== KWord ====
-----

==== KPresenter ====
-----

'''Project:''' Powerpoint import.

'''Explanation:''' From some years ago another gSoc project implemented the basis for powerpoint import, but it was never finished. So there is a good basis to start from. From a quick look it seems like styles support is the thing missing most to complete the work, however a thorough analysis of what is there and what is not needs to be done. And then the actual work needs to be done too, obviously

==== Krita ====

-----

'''Project:''' Sketch-pad interface for Krita

'''Project Information:''' Krita is a large and complex application built around a sophisticated painting engine. The goal of this project is to create a new interface around the Krita engine, specialized for quick sketching.

'''Expected results:''' This project should implement a new interface around Krita, presenting the user a single-layer plus tracing paper interface with a single freehand sketching tool. Easy to use and graphic color and paint operation (brush, pencil, eraser etc.) interface elements must be designed and implemented.

'''Knowledge Pre-Requisite:''' C++

-----

'''Project:''' Shader filters and generators for Krita

'''Project Information:''' Some initial work has already been done to make it possible to write filters in the OpenGL shading language. This project should take that initial code as a basis and implement a fully functioning plugin for Krita that allows filters and shaders to be executed on images in any colorspace.

'''Expected results:''' The plugin should have a finished user interface and make it possible to experiment with shader filters in an interactive way. Example filters must be implemented.

'''Knowledge Pre-Requisite:''' C++, OpenGL.

-----

'''Project:''' Animation support

'''Project Information:''' There is no support at all in Krita for animated images such as GIF or MNG or for working with images in an animation context, such as textures or backgrounds in applications like Blender. The applicant should first investigate user needs and use cases and then implement support in the user interface and in the import/export filters.

'''Expected results:''' A user-friendly way of working with animated images (i.e., not by making each frame a layer), but e.g. a docker that shows the the animation running in thumbnail format. Import/export filters for relevant file formats.

'''Knowledge Pre-Requisite:''' C++

-----

'''Project:''' PSD and Gimp plugins

'''Project Information:''' Krita is powerful enough to handle nearly all that the Gimp and Photoshop are capable of saving. This project is about creating dedicated file import/export filters that can handle as much of these file formats as possible, possibly through the use of existing libraries.

'''Expected results:''' 4 plugins: psd import/export and xcf import/export. These plugins should be able to handle complex files in all supported colorspaces. Ideally the project would also deliver a library to convert PSD/XF to/from Open Raster files.

'''Knowledge Pre-Requisite:''' C++

-----

'''Project:''' Workspaces

'''Project Information:''' A workspace is a loadable package of settings that finetune Krita for a particular purpose. A workspace could contain additional plugins (like an image browser plugin for batch operations) and a subset of resources. Example workspaces could be batch-editing of images, editing of animation sequences or painting or sketching.

'''Expected results:''' the user interface and framework to make packages of plugins and resources that users can switch between. Also extra plugins to extend krita in areas like batch processing that do not exist yet.

'''Knowledge Pre-Requisite:''' C++, artistic workflow

-----

'''Project:''' Kipi and digikam plugins compatibility

'''Project Information:''' Kipi and digikam provide lots of interesting plugins for working with 8 and 16 bit RGBA images. It would be great to be able to re-use those plugins from within Krita.

'''Expected results:''' Two plugins that load kipi and digikam filters into two new menus in the filter menu. Code to convert Krita layers to the digikam image representation and back, taking care of icc profiles and other niceties.

'''Knowledge Pre-Requisite:''' C++, artistic workflow

===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 [http://www.akonadi-project.org/ Akonadi].

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

[http://pim.kde.org/ Website] - [http://techbase.kde.org/Projects/PIM Project Wiki] - [https://mail.kde.org/mailman/listinfo/kde-pim Mailing list] - IRC channel: #kontact and #akonadi on Freenode.

====Project: Akonadi Janitor Agent====
'''Brief explanation:'''
An [[Development/Architecture/KDE4/Akonadi#Akonadi_Agents|Akonadi Agent]] is a service process for performing tasks on data provided through the Akonadi server.

The task of a Janitor agent would be to keep the user's PIM data neatly organized, for example deleting news feed items which are above a certain age and not flagged, moving last week's mail to an archive, etc.

'''Expected results:'''
* An Akonadi Agent capable of managing actions on Akonadi collections triggered by various criteria
* At least fully working implementation of actions based on "Expire" criterias for mail, e.g. delete mail above certain age, move/copy to different collection, etc
* GUI for configuring actions and their trigger criteria.

'''Knowledge Prerequisite:''' C++ and Qt. Ideally would already have gone through the [[Development/Tutorials/Akonadi/Resources|Akonadi Resource Tutorial]] since Resources are a specialized form of agents and thus share some of the API and characteristics.

'''Mentor:''' Kevin Krammer (kevin dot krammer at gmx dot at)
----
====Project: Alternative Akonadi Client Library====
'''Brief explanation:'''
Akonadi has a server/client like architecture where clients such as applications (but also resource) connect to a service and communicate with it through a suitable protocol.

Currently this is implemented for KDE in library called libakonadi-kde, however it is desirable to have additional implementations to be suitable for other library stacks, e.g. GLib/GObject based ones.

'''Expected results:'''
* A non-KDE based, preferably GLib/GObject based, Akonadi client library which
** can connect to a running Akonadi server
** fetch Akonadi collections
** fetch Akonadi items
** receive Akonadi change notifications (D-Bus based)

* A set of demo programs using the library which can
** recursively list (id and content MIME types) collections
** list (id and MIME type)oif items in a collection
** get the raw payload of an item

'''Knowledge Prerequisite:''' Depends on the chosen language and toolstack, e.g. C/Vala and GLib/GObject knowledge for a GLib/GObject based implementation.

'''Mentor:'''
----
====Project: Akonadi Consistency Checker====
'''Brief explanation:'''
Akonadi provides a structure of collections and items, similar to folders and files of a filesystem. Similarly the internal structures have to follow certain constraints which must not be violated. Nevertheless, this can happen as result of bugs, hardware failures, power loss and a million other reasons.

Filesystem checks exist to detect and possibly fix such situations. Such functionality would also be desirable for Akonadi.

'''Expected results:'''
* A consistency checker (built into the Akonadi server or stand-alone) that performs an extensible set of checks on the internal data structures of the Akonadi server, such as:
** items belong to existing collections
** collections are child collections of existing collections
** the collection tree is non-cyclic
** every collections is owned by an existing resource
** collection sub-trees are owned by the same resource
** every item payload part belongs to an existing item
** content type constraints of collections are not violated
** ...
* each check should be accompanied with recovery code, such as moving orphaned items into a lost+found folder
* integration into Akonadiconsole
* integration into unit-tests

'''Knowledge Prerequisite:''' C++ and Qt mandatory, SQL/database knowledge would be useful.

'''Mentor:''' Volker Krause <vkrause@kde.org>
----
====Project: Akonadi Resource for KMail local folders====
'''Brief explanation:'''
KMail stores its mail in a folder hierachy where each folder can contain mails '''and''' further sub folders.

While mails are stored either as mbox or maildir, additional index files are used to speed up message listing and to store message status and flags.

The already existing Akonadi MailDir resource can handle the maildir aspects but cannot handle either mbox based folders nor the additional information stored in the index files.

'''Expected results:'''
* a set of classes, probably as a library, capable of
** recursively listing the KMail folder tree given a base directory
** reading mails from the mbox and maildir folders in the KMail folder tree
** reading KMail index files
* an Akonadi resource using these classes to provide read-only access to all mails currently handled by KMail. The resource should also be able to transfer the flags stored in KMail's index file to Akonadi.
* Writing a migrator, similar to the current KResource->Akonadi migrator, that automatically reads the KMail config file and creates a Akonadi resource out of it. Optionally, depending on the overall progress, the migrator would also convert some of KMail's folder settings, like the folder icon or the expiry settings, to Akonadi collection attributes.

'''Knowledge Prerequisite:''' C++ and Qt mandatory, code analysis skills would be helpful regarding the handling of index files, refactoring skills if KMail's classes are to be extracted from KMail's code base (not required).

'''Mentor:''' Thomas McGuire <mcguire at kde dot org>
----

===KDE on Windows===
====Solid API backend====
'''Brief explanation:'''
The porting efforts to make KDE available across platforms do need some backends for system dependent tasks. One of the KDE libraries that bundles this is Solid.

'''Expected results:'''
You implement a backend for the [http://solid.kde.org Solid API] using WINAPI.
It has to work with both MinGW and MSVC compilers. Not every function is required, but the basic functionality (network access, removable drives/harddisks and power) should be implemented.

'''Knowledge Prerequisite:''' Windows API and C++/Qt. You should be able to set up the [http://techbase.kde.org/Getting_Started/Build/KDE4/Windows development environment] yourself and be familiar with it.

'''Mentor:''' Carlo Segato (brandon dot ml at gmail dot com) or Patrick Spendrin (ps_ml at gmx dot de)
----

===KDE Games===
====Project: Kolf 2 landscape object====
'''Brief explanation:'''
Kolf 2 is the second incarnation of KDE's minigolf game. We are currently rewriting it from scratch to take advantage of the powerful technologies provided by Qt 4 and KDE 4.

'''Expected results:'''
The task in this project is to create an object (or multiple objects) that provide(s) landscape textures, slopes, puddles and sand bunkers.

If you finish this task before the end of the summer, you can fill the remaining time by porting as much game objects from Kolf 1 to Kolf 2 as possible (e.g. windmills, floating blocks, signs or bumpers).

'''Knowledge Prerequisite:''' C++/Qt. Experiences in graphics programming with Qt will definitely help, as you are expected to implement 2D rendering for the landscape object.

'''Mentor:''' Stefan Majewsky (majewsky at gmx dot net) – Please contact me to let me help you to improve your proposal.

====Project: Kolf 2 editor interface====
'''Brief explanation:'''
The minigolf game Kolf provided an editor interface from the beginning, to allow the users to create custom courses. For Kolf 2, we are rewriting the game engine and can therefore not use the old editor code.

'''Expected results:'''
Your task would be to create an editor interface (may be embedded in the game, or a standalone application). A few basic parts are available, and the Kolf 2 engine supports generic methods to provide data to editor interfaces, and display editor overlays on the game view.

If you finish the editor interface before the end of the summer, you can fill the remaining time by porting as much game objects from Kolf 1 to Kolf 2 as possible (e.g. windmills, floating blocks, signs or bumpers).

'''Knowledge Prerequisite:''' C++/Qt. Experiences in model/view programming with Qt will be of good use.

'''Mentor:''' Stefan Majewsky (majewsky at gmx dot net) – Please contact me to let me help you to improve your proposal.

----

===Solid===
====Project: UPnP support through Jolie====
'''Brief explanation:'''
Adding UPnP support to Solid would mean offering transparent UPnP support to every KDE application using the Solid API, keeping them clean from every UPnP implementation aspect.
At the present, the [http://www.jolie-lang.org/ Jolie language] is being integrated with Plasma by means of the [http://websvn.kde.org/branches/work/~ervin/sodep/ QtSodep] library, soon to offer higher levels of abstraction.

The aim of this project would be to implement a UPnP protocol for Jolie, so that Solid could re-use the integration being made with QtSodep and gain UPnP support without having to worry about implementation details. Having a UPnP protocol implementation in Jolie would have other considerable consequences, like the possibility to act easily as a UPnP server or to compose and export existing UPnP services.

'''Expected results:'''
*The creation of a "upnp" protocol in Jolie, supporting at least the Internet Gateway Device (IGD) and MediaServer profiles.
*The creation of a UPnP Jolie service for UPnP service discovery and monitoring.
*Extending libsolid to expose UPnP devices found on the network.

'''Material Prerequisite:''' Having UPnP devices or software applications to test with. Most home routers support IGD, and there exists free software supporting the MediaServer profile ([http://mediatomb.cc/ mediatomb]).

'''Knowledge Prerequisite:''' Understanding of the UPnP specifications, Java (for the development of the Jolie UPnP protocol) and basic knowledge of the Jolie language.

'''Mentors:''' ervin (ervin at kde dot org) fmontesi (famontesi at gmail dot com)
----

===KWin===

KDE's window manager

[http://techbase.kde.org/Projects/KWin Techbase page] - [https://mail.kde.org/mailman/listinfo/kwin Mailinglist] - IRC channel: #kwin on Freenode.

====Project: Window tabbing====

'''Brief explanation:'''
Window tabbing is a feature that allows you to group multiple application windows together to cover the same space. It is identical to what is already available in any modern web browser except it applies the the window as a whole. Window managers that have this feature available include Fluxbox and Ion. This feature was [http://bugs.kde.org/show_bug.cgi?id=42023 originally requested] in 2002.

'''Knowledge Prerequisite:''' C++ and Qt. Understanding of the X window system and Xlib is a benefit but not required.

'''Mentors:''' Lucas Murray (lmurray undefinedfire com)

====Project: Window tiling====

'''Brief explanation:'''
Window tiling is a technique of displaying application windows side-by-side without overlap. The position, size and layout of the windows can either be specified by the user or determined automatically to best fit the screen. Examples of existing tiling window managers include Awesome, XMonad, Ion and Ratpoison. One of the main advantages of tiling is that is makes application windows easy to navigate solely by the keyboard. This feature was [http://bugs.kde.org/show_bug.cgi?id=59338 originally requested] in 2003.

'''Expected results:'''
* Users should be able tile existing floating windows on-the-fly with simple keyboard shortcuts or mouse gestures.
* It should also be possible to run the entire desktop environment entirely in tiled mode (Enabled by configuration settings). In this mode new window would be added to the tiling grid by default yet can be removed by the user if required.
* The final tiling system should not interfere in any way with the existing floating window management.

'''Knowledge Prerequisite:''' C++ and Qt. Understanding of the X window system and Xlib is a benefit but not required.

'''Mentors:''' Lucas Murray (lmurray undefinedfire com)

----

=== digiKam ===

Photo Management program

[http://www.digikam.org digiKam project web site] - [https://mail.kde.org/mailman/listinfo/digikam-devel Mailinglist] - IRC channel: #digikam on Freenode.

====Project: High Dynamic Range (HDR) plugin====

'''Project Information:''' digiKam is an advanced digital photo management application for KDE, which makes importing and organizing digital photos a "snap". The photos are organized in albums which can be sorted chronologically, by folder layout or by custom collections. digiKam has an Image Editor which has its own plugin subsystem with some common tools e.g. red eye correction or Gamma correction. Additional plugins are provided with the main application to process advanced corrections on image like color management, noise reduction, or special effects. digiKam image editor support 16 bits color depth image internally. The goal of this project is to create a new plugin dedicated to create [http://en.wikipedia.org/wiki/High_dynamic_range_imaging HDR image].

'''Expected results:''' This project should implement an HDR tool will mix two or more (nearly) identical images having different exposure into a new image representing a wider dynamic range, which is closer to human perception of a photographic scene. [http://en.wikipedia.org/wiki/Tone_mapping Tone-mapping method] must be used to create HDR images. An open-source implementation is already available at [http://zynaddsubfx.sourceforge.net/other/tonemapping this url] and can be re-used as well. There is an old [https://bugs.kde.org/show_bug.cgi?id=144593 feature request].

'''Knowledge Pre-Requisite:''' C++/Qt.

'''Mentors:''' Gilles Caulier (caulier dot gilles at gmail dot com)

===KDE Telepathy Integration===
The [http://telepathy.freedesktop.org Telepathy Framework] is a desktop independent framework for real-time communication, such as VoIP and Instant Messaging. The projects below are some ideas for integrating telepathy into KDE.

User:Grundleborg/Bugsquad Canned Responses

2009-01-29T16:14:48Z

Grundleborg: /* Closing user-support request */

==Bugsquad Proposed Canned Responses==
This page contains a selection of canned responses that I am proposing as guidelines/example responses to bug-triagers. They are not meant to be taken as the law for responding to bugs, but there is no harm in using them as templates when replying to applicable bugs.

===Closing report due to being non-reproducible in latest released version===
Hi <name>. Thanks for taking the time to report this bug. It seems to be fixed in KDE <latest-released-version>, so I am closing this report. However, if you still continue to experience this bug in KDE <latest-released-version>, please let us know by reopening the report and leaving a comment and we will attempt to investigate it again.

===Closing report due to being non-reproducible in current svn===
Hi <name>. Thanks for taking the time to report this bug. It seems to be fixed in the current svn trunk of KDE, so I am closing this report. The fix for this bug will be included in KDE <next-release-version>. However, if you still continue to experience this bug in svn trunk or KDE <next-release-version>, please let us know by reopening the report and leaving a comment and we will attempt to investigate it again.

===Closing report due to being in another software project===
Hi <name>. Thanks for taking the time to report this bug. However, it is actually in <actual-product-with-bug>, so should be reported to them rather than the KDE team. Their bug tracker can be found at <tracker-url>, and it would be very much appreciated if you could re-report this bug there.

===Closing user-support request===
Hi <name>. The KDE bug tracker should be used to report defects or feature requests in KDE software. For help or support with KDE, please use one of the following alternatives:

- The KDE forum: http://forum.kde.org

- The KDE mailing lists: http://userbase.kde.org/Mailing_Lists#General_Help_Lists

User:Grundleborg/Bugsquad Canned Responses

2009-01-29T16:10:44Z

Grundleborg: /* Closing user-support request */

User:Grundleborg/Bugsquad Canned Responses

2009-01-29T14:58:05Z

Grundleborg: /* Closing user-support request */

User:Grundleborg/Bugsquad Canned Responses

2009-01-29T14:57:40Z

Grundleborg: /* Bugsquad Proposed Canned Responses */

==Bugsquad Proposed Canned Responses==
This page contains a selection of canned responses that I am proposing as guidelines/example responses to bug-triagers. They are not meant to be taken as the law for responding to bugs, but there is no harm in using them as templates when replying to applicable bugs.

===Closing report due to being non-reproducible in latest released version===
Hi <name>. Thanks for taking the time to report this bug. It seems to be fixed in KDE <latest-released-version>, so I am closing this report. However, if you still continue to experience this bug in KDE <latest-released-version>, please let us know by reopening the report and leaving a comment and we will attempt to investigate it again.

===Closing report due to being non-reproducible in current svn===
Hi <name>. Thanks for taking the time to report this bug. It seems to be fixed in the current svn trunk of KDE, so I am closing this report. The fix for this bug will be included in KDE <next-release-version>. However, if you still continue to experience this bug in svn trunk or KDE <next-release-version>, please let us know by reopening the report and leaving a comment and we will attempt to investigate it again.

===Closing report due to being in another software project===
Hi <name>. Thanks for taking the time to report this bug. However, it is actually in <actual-product-with-bug>, so should be reported to them rather than the KDE team. Their bug tracker can be found at <tracker-url>, and it would be very much appreciated if you could re-report this bug there.

===Closing user-support request===
Hi <name>. The KDE bug tracker should be used to report defects or feature requests in KDE software. For help or support with KDE, please use one of the following alternatives:
- The KDE forum: http://forum.kde.org
- The KDE user support mailing list: kde@kde.org

User:Grundleborg/Bugsquad Canned Responses

2009-01-29T14:45:11Z

Grundleborg: /* Bugsquad Proposed Canned Responses */

User:Grundleborg/Bugsquad Canned Responses

2009-01-29T14:44:52Z

Grundleborg: /* Bugsquad Proposed Canned Responses */

User:Grundleborg

2009-01-29T14:44:46Z

Grundleborg: /* Bugsquad canned responses */

==Pages I'm constructing==
[[User:Grundleborg/Code_Quality]] - Introduction on how to contribute to code quality (with subsections).

[[User:Grundleborg/BugDay]] - My latest crazy idea (nb. pick a day of the week, say, Wednesday) - have a 24 hour period each week where the bugsquad tackles triage of a particular product/period etc... Try and stir up some publicity for it to get more people involved.

[[User:Grundleborg/TriageGuide]] - How to triage bugs?

[[/StepsOfTriagingBugs]] - Step by step guide to what to do to the bug.

[[/BugsquadHomePage]] - the new main page for the bugsquad.#

[[/OutstandingBugChanges]] - page for posting bugs that need to be changed/changes approved.

[[/BugsquadKMailWorkflowTest]] - page describing the new Just-In-Time bug triage workflow we are testing with KMail.

==Tutorials Under Construction==
<s>;[[User:Grundleborg/Handling_TextChannels|Handling text channels in Decibel.]]
:''This tutorial introduces the basics of handling incoming TextChannels by guiding you through building a simple text chat application.''</s> DONE 11:39, 30 March 2008 (CEST)

;[[User:Grundleborg/Decibel_User_Introduction|Introduction to Decibel for users.]]
:''This article is an introduction to what Decibel is and is not for end users.''

;[[User:Grundleborg/Decibel_Architecture|An Introduction to the Decibel Architecture for Developers.]]
:''This explains amongst other things how Decibel works, and where tapioca and telepathy come into the equation...''

==BugDay Notes==
[[/BugDayNotes/2008-04-20]]
[[/BugSquad/BugDayPlanning/kdepim-krush-1]]

User:Grundleborg/Bugsquad Canned Responses

2009-01-29T14:44:18Z

Grundleborg: create page with intor

Contribute/Bugsquad/BugDays/KOfficeDay2/KWord

2009-01-25T12:31:28Z

Grundleborg: /* Testers */

===KWord===

====Application specific tips====

At Beta5 the state of KWord is that the application has been stabilized to a large extend and all present features should work with small exceptions.
The loading and saving of documents has not received a lot of attention and therefor it is well known that there will be loads of problems in loading ODFs. So testing KWord by loading may give you some silly results beware of that. And I'd rather have interaction and new document creation be the focus of testing due to that. (ThomasZ)

====Testers====
Please put your IRC nickname and KOffice svn revision number (or beta5) in the table if you are testing this app.
{|
|-
!IRC Nickname !! KOffice svn revision number tested !! Testing details
|-
||[[User:Grundleborg|Grundleborg]] || r916455 || In progress... ||
|}

====Bugs====
Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with <nowiki>~~~</nowiki>.

* After starting kword, with the colorful document, the default tool is Text Editing, without doing anything else, when I choose Paragraph tool, the options bars suffer a little colapse. Look at: [[Image:Kword_toolbar1.png]] [[User:Jtamate|Jtamate]]
NOTE: It happens also with a lot of tools. 
NOTE: This only happens with the colorful document, with a blank document it does not happen.

* The tool toolbar can not be horizontally srinked to only one or two tools (specially usefull on small screens). [[User:Jtamate|Jtamate]] 
NOTE: This only happens with one user account (that has used previous betas), with a fresh new account it does not happen.

* Find does nothing. Hope the find interface will change to something similar to what kate has. [[User:Jtamate|Jtamate]]

* The hand drawing plots are not saved (or loaded). What I wrote: 
[[Image:Screen_with_free_hand_drawings.png]] 
But only the text is restored. If there are some things that can not be saved or restored, it should be shown when saving the file.[[User:Jtamate|Jtamate]]

* With a chart in a document, autosave crashed (unfortunately I can not provide backtraces) [[User:Jtamate|Jtamate]]

* There is no menu entry to configure Kword (including Autosave time) [[User:Jtamate|Jtamate]]

* Changing to some tools, the window height is increased beyond the screen limit. [[User:Jtamate|Jtamate]]

* Overstriking more than one text line, only does it good in the first line. The others get overstriked at the end. [[User:Jtamate|Jtamate]]

* Predefined Format does not revert paragraph formats.
[[User:Jtamate|Jtamate]]

* The paragraph formats does have some problems with the second line in the right part. It is always displaced to the right. [[User:Jtamate|Jtamate]]

* When the view is divided, the toolbars are multiplied. [[User:Jtamate|Jtamate]]

* Selecting "character tipography", in spanish "tipo de letra", there is no tipography preview (very usefull). [[User:Jtamate|Jtamate]]

* Selecting "character tipography", in spanish "tipo de letra", the cursor is a hand in the tipography, but not in the size or format. [[User:Jtamate|Jtamate]]

* In decoration (text properties), the ... button clears the color section. Is not better a <x button?
[[User:Jtamate|Jtamate]]