KDE TechBase - User contributions [en]

Development/ECM SourceIncompatChanges

2011-11-24T23:56:46Z

Steveire:

=== FindFLEX.cmake ===

We use the version from CMake now, which is named FindFlex.cmake (different casing !).
Beside that there should be no changes in behaviour.

* find_package(FLEX) -> find_package(Flex)

=== FindGetText.cmake ===

We use the version from CMake now.
The syntax of GETTEXT_PROCESS_PO_FILES() changed a bit, it now needs the additional keyword "PO_FILES.

* gettext_process_po_files(de ALL INSTALL_DESTINATION ${dest} file1.po file2.po) -> gettext_process_po_files(de ALL INSTALL_DESTINATION ${dest} PO_FILES file1.po file2.po)

=== FindGIF.cmake ===

We use the version from CMake now.
There is a minor difference, which will not affect many systems. The KDE version accepted only giflib version 4, while the CMake version accepted any version of giflib. If giflib version 4 .x is required, the version can now be specified:

* find_package(GIF) -> find_package(GIF 4 )

This actually only was an issue on some relatively old Sun machines in 2006. Maybe today it is not even there a problem anymore.

=== FindLibXslt.cmake ===

We use the version from CMake 2.8.7 now.
There are two changes compared to the one in kdelibs:

* ${LIBEXSLT_LIBRARIES} -> ${LIBXSLT_EXSLT_LIBRARIES}
* WinCE is probably not supported anymore, patches are welcome

=== FindRUBY.cmake ===

This file does not exist anymore, use FindRuby.cmake coming with CMake instead. Most variables are the same. Below are the changes:

* find_package(RUBY) -> find_package(Ruby)
* RUBY_INCLUDE_PATH -> RUBY_INCLUDE_DIRS

=== FindX11.cmake ===

The following two variables have been removed, use the newer ones instead:

* X11_Xss_FOUND -> X11_Xscreensaver_FOUND
* X11_Xss_LIB -> X11_Xscreensaver_LIB

The following libraries are now not part of X11_LIBRARIES anymore, so they may have to be added to target_link_libraries() explicitely where needed:

* X11_Xau_LIB
* X11_Xft_LIB
* X11_Xdmcp_LIB
* X11_Xpm_LIB

=== MacroAddCompileFlags.cmake ===

This file has been removed. Use set_property(.. APPEND_STRING) instead (new in CMake 2.8.6).

* include(MacroAddCompileFlags) -> delete
* macro_add_compile_flags(target "-O2 -g") -> set_property(TARGET target APPEND_STRING PROPERTY COMPILE_FLAGS " -O2 -g")

=== MacroAddLinkFlags.cmake ===

This file has been removed. Use set_property(.. APPEND_STRING) instead (new in CMake 2.8.6).

* include(MacroAddLinkFlags) -> delete
* macro_add_link_flags(target "-no-rpath") -> set_property(TARGET target APPEND_STRING PROPERTY LINK_FLAGS " -no-rpath")

=== MacroAdditionalCleanFiles.cmake ===

This file has been removed. Use set_property(... APPEND ...) instead.

* include(MacroAdditionalCleanFiles) -> delete
* macro_additional_clean_files(file1 file2 fileN) -> set_property(DIRECTORY APPEND PROPERTY ADDITIONAL_MAKE_CLEAN_FILES "file1;file2;fileN" )

=== MacroLogFeature.cmake ===

This file has been removed, instead FeatureSummary.cmake from CMake >= 2.8.6 has to be used, which has even more functionality.
Please have a look at the documentation of FeatureSummary.cmake on the cmake manpage.

* macro_log_feature(<variable> <FEATURE> <DESCRIPTION> <URL> <REQUIRED> <MIN_VERSION> <COMMENTS>) -> set_package_properties(FEATURE PROPERTIES DESCRIPTION <DESCRIPTION> URL <URL> TYPE (RUNTIME|OPTIONAL|RECOMMENDED|REQUIRED) PURPOSE "good for something")

* macro_display_feature_log() -> feature_summary(WHAT ALL FATAL_ON_MISSING_REQUIRED_PACKAGE)

=== MacroOptionalAddSubdirectory.cmake ===

This file is now part of the extra-cmake-modules package and thus has been renamed to ECMOptionalAddSubdirectory.cmake

* include(MacroOptionalAddSubdirectory) -> include (ECMOptionalAddSubdirectory)
* macro_optional_add_subdirectory(...) -> ecm_optional_add_subdirectory(...)

=== MacroOptionalDependPackage.cmake ===

This file has been removed, the purpose was broken.

* include (MacroOptionalDependPackage) -> delete
* macro_optional_depend_package() -> delete

=== MacroOptionalFindPackage.cmake ===

This file does not exist anymore. Instead, starting with CMake 2.8.6, every find_package() call which is not REQUIRED can be disabled by setting the variable CMAKE_DISABLE_FIND_PACKAGE_<PackageName> to TRUE. This makes this macro unnecessary.

* include(MacroFindPackage) -> delete
* macro_optional_find_package(Foo ...) -> find_package(Foo ... )

=== MacroPushRequiredVars.cmake ===

This file has been merged into CMake, but has been renamed to CMakePushCheckState.cmake.

* include(MacroPushRequiredVars) -> include(CMakePushCheckState)
* macro_push_required_vars() -> cmake_push_check_state()
* macro_pop_required_vars() -> cmake_pop_check_state()

=== MacroWriteBasicCMakeVersionFile.cmake ===

This macro has been merged into CMake, but has been renamed to WriteBasicConfigVersionFile.cmake, also the syntax changed slightly. To get exactly the same behaviour as with the old macro, do as shown below. For details see the documentation in the man page.

* include(MacroWriteBasicCMakeVersionFile) -> include (WriteBasicConfigVersionFile)
* macro_write_basic_cmake_version_file(<outfilename> 1 2 3) -> write_basic_config_version_file(<outfilename> VERSION 1.2.3 COMPATIBILITY AnyNewerVersion )

=== GenerateExportHeader.cmake ===

This has been added to CMake and provides the generate_export_header macro. This macro is the replacement of kde4_create_exports_header.

Projects/KDELibsModifications

2011-02-14T21:58:27Z

Steveire: Redirect to communitybase

This page has been moved to [http://community.kde.org/KDE_Core/Modularization communitybase]

Development/Tutorials/Localization/i18n Build Systems

2011-01-26T18:53:43Z

Steveire: /* Writing a Messages.sh script */ Document scripts to extract strings from QML and Grantlee files.

{{Template:I18n/Language Navigation Bar|Development/Tutorials/Localization/i18n Build Systems}}

{{TutorialBrowser|

series=Localization|

name=Building KDE's l10n Module|

pre=[[../i18n|Writing Applications With Localization in Mind]]|
next=[[../Language Change|Dealing with language changes]]|
}}

== Abstract ==

Now that your application is ready to be localized, we next look at how to incorporate the necessary mechanisms into the CMake build system of your application.

First we'll explain the "theory" of the steps that need to happen from extracting message strings to installing the generated .po files. After that we'll look at how to implement those steps ([[#Theory: The xgettext toolchain]]). If your application is developed in KDE's subversion repository, many of those steps will happen automatically (see [[#handling i18n in KDE's subversion repository]]). Else you will want to read on in the [[#handling i18n in third party applications]] section.

== Theory: The xgettext toolchain ==

Making translations work consists of the following steps:
# Extract the translatable strings
# Merge the new or changed strings with existing translations
# Compile the translations into message catalogs
# Install the message catalogs
# Use the message catalogs in the application

=== Extracting the strings ===

In this step, all the strings you marked as i18n()/ki18n()/etc. in your sources need to be collected into a translation template (.pot) file. Some translateable strings are also contained in .ui, .rc, or .kcfg files. Also tips-of-the-day need to be collected into the .pot file.

These steps are handled by {{path|xgettext}}, {{path|extractrc}}, and {{path|preparetips}} programs, respectively. In some cases you may also need {{path|extractattr}}.

=== Merging translations ===

Generally, only a few translatable string will change at a time, in an application. Some will be removed, some will be added, some will be changed into different strings, and some will be moved around in the source files. These changes need to be reflected in the translations, but of course it would be a huge effort to redo the entire translation every time a string was changed. Rather the changes should be merged with the existing translations. This is the job of the {{path|msgmerge}} tool.

=== Compiling the translations ===

In order to make message lookup fast, the .po files need to be compiled into so-called "message catalogs" (.mo / .gmo). This is done using the {{path|msgfmt}} tool.

=== Installing the message catalogs ===

The compiled message catalogs need to be installed alongside the application. In KDE, the standard location for message catalogs is {{path|$KDEDIR/share/locale/xx/LC_MESSAGES/}}.

=== Using the message catalogs ===

Finally, when the application is run, it needs to load the appropriate message catalog in order to be able to look up and show translated strings. In KDE applications, this is the job of the {{class|KLocale}} class, and in the great majority of cases happens automatically.

For some special cases, such as plugins, look at [[#Runtime Loading Of Catalogs]].

== handling i18n in KDE's subversion repository ==

If your application is developed inside KDE's subversion repository, most of the steps outlined above are automated. In this case, generally, all you will need to do is provide a simple script called {{path|Messages.sh}}, which we will look at below.

In addition, if your top-level folder and .pot file have the same name, the svn2dist script will automatically include .po files when you use it to make a source tarball for your app.

Of course, for the curious, a more detailed account of what happens behind the scences is also provided.

=== Writing a Messages.sh script ===

Basically, the only thing that is necessary to prepare and install translations for applications in KDE's subversion repository, is to provide information, which sources, ui-files or tips need to be translated. For this purpose, you write a small script called {{path|Messages.sh}} and place it in your sources. Here is an example with inline comments:

<code bash n>
#!bin/sh

# invoke the extractrc script on all .ui, .rc, and .kcfg files in the sources
# the results are stored in a pseudo .cpp file to be picked up by xgettext.
$EXTRACTRC `find . -name \*.rc -o -name \*.ui -o -name \*.kcfg` >> rc.cpp
# if your application contains tips-of-the-day, call preparetips as well.
$PREPARETIPS > tips.cpp
# call xgettext on all source files. If your sources have other filename
# extensions besides .cc, .cpp, and .h, just add them in the find call.
$XGETTEXT `find . -name \*.cc -o -name \*.cpp -o -name \*.h` -o $podir/APPNAME.pot
</code>

As you can see, this script contains only three actual lines of code, and not all may even be needed. The $XGETTEXT, $PREPARETIPS, $EXTRACTRC, and $podir environment variables are predefined, you do not need to worry about setting these. The only thing that you will need to do is to replace "APPNAME" with the name of your application (but see [[#Naming .pot Files]] for exceptions).

Translatable strings are automatically extracted from c++ files. For non c++ files, the following scripts are used
* $EXTRACTRC - Extract translatable strings from xml configuration and ui files.
* $EXTRACTQML - Extract translatable strings from QML files.
* $EXTRACT_GRANTLEE_TEMPLATE_STRINGS - Extract translatable strings from Grantlee template files.

Try to make sure your Messages.sh script collects only those messages that are really needed. If in doubt, look at other Messages.sh files in the KDE subversion repository for inspiration, or - of course - ask.

=== What's happening behind the scenes ===

{{tip|If your application is in the KDE code repository, all this happens automatically. If your code is not in the KDE repository, you must perform these steps yourself. See [[#handling i18n in third party applications]].}}

Periodically, the script {{path|extract-messages.sh}} (a.k.a. scripty) runs on the KDE server. This program basically calls all Messages.sh scripts in the repository with the appropriate parameters. The extracted messages are stored in template (.pot) files in the templates folder of the l10n module. See [[What Is Scripty]] for more information.

The KDE translation teams translate the messages and commit them into a messages folder corresponding to the language, which is further broken down by module. For example, German translated messages for konqueror are committed to {{path|l10n/de/messages/kdebase/konqueror.po}}.

When the l10n module is built, the .po files are compiled into a binary format for fast lookup and installed as .mo files to {{path|$KDEDIR/share/locale/xx/LC_MESSAGES/}}, where xx is the two-letter ISO 639 code for the language. These are called the message catalogs.

At runtime, the <tt>i18n(...)</tt> function, using the original string you coded, looks up the string in the message catalog of the user's desktop language and returns the translated string. If the message catalog is missing, or the specific string is not found, <tt>i18n(...)</tt> falls back to the original string in your code.

.desktop files in your project are handled separately. {{path|makemessages}} extracts strings, such as Name and Comment from the .desktop files and places them into a file named {{path|desktop_mmmm.pot}}, where mmmm is the module name, in the templates folder. Once translators have translated this file, makemessages inserts the translated strings back into the .desktop files. The list of strings extracted is in {{path|l10n/scripts/apply.cc}}. Here's the code that checks for them:

<code cppqt n>if (checkTag("Name", in, argc, argv, newFile))
continue;
if (checkTag("Comment", in, argc, argv, newFile))
continue;
if (checkTag("Language", in, argc, argv, newFile))
continue;
if (checkTag("Keywords", in, argc, argv, newFile))
continue;
if (checkTag("About", in, argc, argv, newFile))
continue;
if (checkTag("Description", in, argc, argv, newFile))
continue;
if (checkTag("GenericName", in, argc, argv, newFile))
continue;
if (checkTag("Query", in, argc, argv, newFile))
continue;
if (checkTag("ExtraNames", in, argc, argv, newFile))
continue;</code>

== handling i18n in third party applications ==

If your application is developed outside of KDE's subversion repository, you need to take care of generating and installing message catalogs yourself. This is not too hard to do, but you should make sure you have a basic understanding of all steps involved, so you will probably want to read [[#Theory: The xgettext toolchain]], first.

Also, there is more than one way to deal with i18n in your application. We will outline one approach to do so for simple applications, but you may want to diverge from this, if you like to.

=== General considerations ===

The i18n generation process can roughly be divided into two steps:

# Extracting and merging messages
# Compiling and installing message catalogs

The first step really concerns the ''sources'', while the second step is a natural part of compiling and installing an application. Hence, while the second step should definitely be incorporated into the build system for your application (we assume CMake, here), there is no striking reason for the first step to be handled by the build system.

In fact, the extraction and merging of messages does not map well onto the CMake concept of out-of-source builds, and CMake can't provide too much help for this step, either.

Hence, in this tutorial, we will handle the first step with a standalone shell script, and only the second step will be handled by CMake.

=== Extracting and merging messages ===

If you have read the section [[#handling i18n in KDE's subversion repository]] you will know that in the KDE repository, message extraction and merging is handled by a simple script called Messages.sh, which is invoked by a script called {{path|extract-messages.sh}}. Outside of KDE's repository, you will need to take care of both parts, but fortunately, this is easy enough. Here's a sample script:

<code bash n>
#!/bin/sh
BASEDIR="../rkward/" # root of translatable sources
PROJECT="rkward" # project name
BUGADDR="http://sourceforge.net/tracker/?group_id=50231&atid=459007" # MSGID-Bugs
WDIR=`pwd` # working dir

echo "Preparing rc files"
cd ${BASEDIR}
# we use simple sorting to make sure the lines do not jump around too much from system to system
find . -name '*.rc' -o -name '*.ui' -o -name '*.kcfg' | sort > ${WDIR}/rcfiles.list
xargs --arg-file=${WDIR}/rcfiles.list extractrc > ${WDIR}/rc.cpp
# additional string for KAboutData
echo 'i18nc("NAME OF TRANSLATORS","Your names");' >> ${WDIR}/rc.cpp
echo 'i18nc("EMAIL OF TRANSLATORS","Your emails");' >> ${WDIR}/rc.cpp
cd ${WDIR}
echo "Done preparing rc files"

echo "Extracting messages"
cd ${BASEDIR}
# see above on sorting
find . -name '*.cpp' -o -name '*.h' -o -name '*.c' | sort > ${WDIR}/infiles.list
echo "rc.cpp" >> ${WDIR}/infiles.list
cd ${WDIR}
xgettext --from-code=UTF-8 -C -kde -ci18n -ki18n:1 -ki18nc:1c,2 -ki18np:1,2 -ki18ncp:1c,2,3 -ktr2i18n:1 \
-kI18N_NOOP:1 -kI18N_NOOP2:1c,2 -kaliasLocale -kki18n:1 -kki18nc:1c,2 -kki18np:1,2 -kki18ncp:1c,2,3 \
--msgid-bugs-address="${BUGADDR}" \
--files-from=infiles.list -D ${BASEDIR} -D ${WDIR} -o ${PROJECT}.pot || { echo "error while calling xgettext. aborting."; exit 1; }
echo "Done extracting messages"

echo "Merging translations"
catalogs=`find . -name '*.po'`
for cat in $catalogs; do
echo $cat
msgmerge -o $cat.new $cat ${PROJECT}.pot
mv $cat.new $cat
done
echo "Done merging translations"

echo "Cleaning up"
cd ${WDIR}
rm rcfiles.list
rm infiles.list
rm rc.cpp
echo "Done"
</code>

Of course you will want to adjust the variable definitions at the top, and - if needed - add code to extract tips-of-the-day or other additional strings.

The example script assumes that all .po files and the .pot file are kept in a single directory, which is appropriate for most projects.

=== Compiling and installing message catalogs ===

Assuming you use the script from the previous section, you can place the following CMakeLists.txt in the directory containing the .po files:

<code>
FIND_PROGRAM(GETTEXT_MSGFMT_EXECUTABLE msgfmt)

IF(NOT GETTEXT_MSGFMT_EXECUTABLE)
MESSAGE(
"------
NOTE: msgfmt not found. Translations will *not* be installed
------")
ELSE(NOT GETTEXT_MSGFMT_EXECUTABLE)

SET(catalogname rkward)

ADD_CUSTOM_TARGET(translations ALL)

FILE(GLOB PO_FILES *.po)

FOREACH(_poFile ${PO_FILES})
GET_FILENAME_COMPONENT(_poFileName ${_poFile} NAME)
STRING(REGEX REPLACE "^${catalogname}_?" "" _langCode ${_poFileName} )
STRING(REGEX REPLACE "\\.po$" "" _langCode ${_langCode} )

IF( _langCode )
GET_FILENAME_COMPONENT(_lang ${_poFile} NAME_WE)
SET(_gmoFile ${CMAKE_CURRENT_BINARY_DIR}/${_lang}.gmo)

ADD_CUSTOM_COMMAND(TARGET translations
COMMAND ${GETTEXT_MSGFMT_EXECUTABLE} --check -o ${_gmoFile} ${_poFile}
DEPENDS ${_poFile})
INSTALL(FILES ${_gmoFile} DESTINATION ${LOCALE_INSTALL_DIR}/${_langCode}/LC_MESSAGES/ RENAME ${catalogname}.mo)
ENDIF( _langCode )

ENDFOREACH(_poFile ${PO_FILES})

ENDIF(NOT GETTEXT_MSGFMT_EXECUTABLE)
</code>

This iterates over all .po files in the directory, compiles them using msgfmt, and installs them to the standard location. You will want to change "catalogname" to the name of your application.

=== Getting translations ===

Now you just have to find translators to translate the extracted messages into the various languages. As your application gets used by more people, you will find that translators will volunteer to do this. Translated PO files then have to be stored in the po folder with the naming scheme <languagecode>.po.

=== Translating .desktop Files ===

Translating .desktop files is a bit tricky because the translation of .desktop files isn't fetched from .po/.gmo files, but must be part of the .desktop file itself. So we have 2 tasks:

* extract messages from the .desktop file
* merge the translations in the .desktop file

Our friends from Gnome provide the [http://freedesktop.org/wiki/Software/intltool intltool] package. While this tools is mainly written for the old autotools build system (but KDE uses CMake since KDE 4), we can use this package nevertheless for our purpose. Here is a step-by-step guide:

# Install the [http://freedesktop.org/wiki/Software/intltool intltool] package
# We assume that your .desktop file is named "MYPROGRAM.desktop".
# Make a copy of "MYPROGRAM.desktop" which is named "MYPROGRAM.desktop.template".
# In MYPROGRAM.desktop.template substitute the keys "Name" by "_Name", "GenericName" by "_GenericName" and "Comment" by "_Comment".
# Remove all translations from "MYPROGRAM.desktop.template".
# Add the following lines to the above described build script, at the end of the section "Preparing rc files":<code>intltool-extract --quiet --type=gettext/ini PATH/MYPROGRAM.desktop.template
cat PATH/MYPROGRAM.desktop.template.h >> ${WDIR}/rc.cpp
rm PATH/MYPROGRAM.desktop.template.h
cd ${WDIR}</code>intltool-extract will create a dummy C++ header (PATH/MYPROGRAM.desktop.template.h) with the strings whose key starts with "_". We append the content of this header file into our "rc.cpp" and remove remove the file than. (We assume that "PATH" is the path to "MYPROGRAM.desktop.template", relative to the working directory of the script.)
# Add "-kN_:1" as additional parameter to the xgettext call in the section "Extracting messages". This is necessary because dummy code that intltool-extract produces uses "N_()" instead of "i18n()".
# Add the following lines to the above described build script, at the end of the section "Merging translations":<code>cd ${WDIR}
intltool-merge --quiet --desktop-style ${WDIR} PATH/MYPROGRAM.desktop.template PATH2/MYPROGRAM.desktop</code>This will produce MYPROGRAM.desktop from MYPROGRAM.desktop.template, inserting all available translations in the .po files in the directory ${WDIR}. (We assume that "PATH" is the path to "MYPROGRAM.desktop.template", relative to the working directory of the script. We assume that "PATH2" is the path to the final location of "MYPROGRAM.desktop", relative to the working directory of the script.)

{{note|Names of .po files):For intltool, it is ''required'' that the .po files have the name <languagecode>.po without other characters (NOT programname_<languagecode>.po). This is important because intltool-merge simply uses the .po file name (without ".po") as language key in the .desktop file.}}

== Special cases (plugins, multiple catalogs, etc.) ==

=== Runtime Loading Of Catalogs ===

To have translations show up properly in an application, the name of the .pot file must match the name of the message catalog (.mo) file that your application will read at runtime. But what name will be used at runtime?

In general, it will be the value returned by <tt>{{class|KGlobal}}::instance()->instanceName()</tt>. But what will that be? The general rules for standalone applications are:
* the message catalog will default to the name of the application passed as the first argument to {{class|KAboutData}}
* if your code calls <tt>{{class|KLocale}}::setMainCatalog()</tt>, that name will be used instead
* if your code calls <tt>{{class|KLocale}}::insertCatalog(const QString&)</tt>, the specified catalog will also be searched in addition to the main catalog

If your code does not call either of the {{class|KLocale}} methods mentioned above and your application is a plugin, it gets a little more complicated. If your code exports your plugin using the <tt>K_EXPORT_COMPONENT_FACTORY</tt> macro, like this:

<code cppqt>K_EXPORT_COMPONENT_FACTORY( libkhtmlkttsdplugin,
KGenericFactory<KHTMLPluginKTTSD>("khtmlkttsd") )</code>

then the catalog name will be the name passed in the {{class|KGenericFactory}} constructor - in the example above that woudl be <tt>khtmlkttsd</tt>. This is because the macro creates a {{class|Kinstance}} for you with the specified name.

However, some classes, such as <tt>KTextEditor</tt> create a <tt>KPart</tt> containing your component and the name passed in the macro is not used. In this case, you should call <tt>{{class|KLocale}}::insertCatalog(const QString&)</tt> in the component's constructor.

If in doubt, the safest thing to do is to call <tt>{{class|KLocale}}::insertCatalog(const QString&)</tt>.

{{tip|If you're not using the export macro for your plugin, you probably should be. See the API documentation of KGenericFactory for more information.}}

Calling <tt>{{class|KLocale}}::insertCatalog(const QString&)</tt> if the catalog has already been inserted does nothing. However, calling <tt>{{class|KLocale}}::removeCatalog(const QString&)</tt> removes the catalog no matter how many times it has been inserted. Therefore, take care that you do not inadvertently remove the catalog when multiple components are sharing a single catalog. For example, the following sequence will break translations:

<code cppqt n>// Component A loads and uses catalog xyz by calling
insertCatalogue("xyz");
// Component B loads and also uses the same catalog.
insertCatalogue("xyz");
// component B unloads and calls
removeCatalogue("xyz")
// Component A now doesn't translate properly.</code>

Notice that a sequence such as above will occur automatically if both components A and B are loaded using the <tt>K_EXPORT_COMPONENT_FACTORY</tt> macro and pass the same name argument to the KGenericFactory constructor.

=== Naming .pot Files ===

The name that you settle on for both the .pot file and catalog should be governed by where your code resides. If it is a component of another application and resides in that application's source tree, you'll want to share the main catalog of the application.

If is a component of another application but resides elsewhere in the code repository, you will probably have to create a separate .pot, but keep in mind that .pot filenames must be unique across all of KDE.

If it is a component of another application, but resides in the source tree of a second application, you should share with the second application. For example, the KDE text-to-speach daemon (KTTSD) includes a plugin for embedded Kate in {{path|kdeaccessibility/kttsd}} source tree. Since the plugin is not installed unless kttsd is installed, it shares its catalog with kttsd and calls <tt>{{class|KLocale}}::insertCatalog("kttsd")</tt> to do this.

== Handbooks ==

Handbooks, which are written in docbook format, are handled different from applications. The translated Handbooks are committed into the l10n module in the docs folder under each language. In addition, the docs folder is broken down by module and application. For example, the German Kate Handbook is committed to the {{path|l10n/de/docs/kdebase/kate/}} folder. When compiled, the German Kate Handbook is installed to {{path|$KDEDIR/share/doc/HTML/de/kate/index.cache.bz2}}.

Note that it is up to each translation team to generate the translated Handbook when they feel it is complete.

[[Category:Programming]]

Projects/KDELibsModifications

2010-10-31T18:45:45Z

Steveire: Add another relevant thread from last year

== KDELibs Rearchitecture ==

=== Background ===

Several directions of Qt development and growth present opportunities to make technology created by the KDE community available to more platforms and to more developers of Qt based applications.

* The advancement of Qt to more and more varied hardware
* The use of Qt as the basis of MeeGo
* The use of Qt as the basis of other platforms in the future
* The use of Qt as the basis of other computer workspaces and interfaces in the future (http://mdzlog.alcor.net/2010/10/20/ubuntu-and-qt/)
* The increased use of Qt in environments such as Industrial Embedded (the machines in your kitchen and house)
* The increased use of Qt in creating Free and NonFree applications on desktop and mobile environments

This availability raises questions for Qt developers in those situations

* What can I use to create a primary widget-based workspace interface for my device? The answer should be libplasma.
* How do I initialize some hardware or software asynchronously and report progress? The answer should be KJob.
* What can I use for asynchronous access to IMAP servers? The answer should be KIMAP and KJob.
* Are there classes available for advanced model-view, or rich text editing? Yes, in Kdeui/itemviews

If GNOME ever switches to Qt, but wants to keep their own platformy bits like configuration format etc, where will they get Qt based libraries to create functionality for their Qt based platform?

=== The problem ===

One reason kde libraries are not currently the answer to the issues that Qt developers face is that 'platform parts' of kdelibs are introduced early instead of late in the module. For example the use of kdecore introduces requirements for things like KGlobal, KStandardDirs, KComponentData, KLocale, KConfig. While all useful for a workspace and application suite like KDE provides, none of those should be needed to use an asynchronous job API or itemviews library. Many for many Qt applications, QSettings and QObject::tr are sufficient because the application is deployed by the software vendor with specific hardware in a limited number of languages for example.

The bundling of the functional libraries of kdelibs and the platform integration pieces of kdelibs makes encouraging the use by third parties of the libraries but not the platform (where the KDE platform is irrelevant) difficult, not least from a point of view of communicating it clearly.

Discussion on k-c-d:
* http://thread.gmane.org/gmane.comp.kde.devel.core/67458
* http://thread.gmane.org/gmane.comp.kde.devel.core/59835

=== An option ===

One way of making the functional libraries of KDElibs more easily available is to split the kdelibs module into two modules named KLibs and KPlatform here for clarity. KLibs would be a 3 tier module:

==== Tier 0: Interfaces. ====
Some low level modules need access to platform specific data. For example, KLocale uses KStandardDirs to locate gettext translation catalogs. This makes KLocale dependent on the KDE platformy bits. An alternative design is to introduce an interface to get the paths, and implement it trivially on the Qt level, and with KDE integration at the platform level.

The interfaces tier would contain all the interfaces needed (probably few) to access platform specific 'simple types' like strings, urls etc.

It is possible that very pervasive classes in the current KDE4 would need to be in this tier (such as KDateTime), but that would be highly undesirable.

==== Tier 1: Independent libraries ====

Libraries such as KJob, KLocale (in theory at least), KItemViews, KConfig etc which can (be made to) exist standalone and depend only whatever dependencies give them their functionality (eg gettext) belong in Tier 1. Tier 1 libraries can not depend on each other, but can use the Tier 0 interfaces. The Tier 1 module is not QtCore only, but individual libraries might be.

==== Tier 2: Dependent libraries ====

Libraries such as KIMAP, KMIME, KMBox, libakonadi-kde can have hard dependencies on Tier 1 libraries (such as KJob) and on other Tier 2 libraries (KIMAP can use KMIME). Dependencies on platformy libraries from Tier 1 such as KConfig should be discouraged where using Tier 0 interfaces produces the same effect.

==== Platforms ====

KPlatform depends on many but not all of the libraries in the Tiers of KLibs. It implements the interfaces from Tier 0 in terms of the platformy stuff, KConfig, KStandardDirs, KStandardAction etc and contains classes like KComponentData, which all 'applications from the KDE community' use.

Pieces like KDED, KLauncher, KDEinit, KSyCoCa etc are also here.

It should be possible for an integrator similar to MeeGo which defines their own configuration system etc and implement the interfaces to create their own coherent platform and use the functional libraries.

=== Definitions ===

With increasing modularity of kde libraries, we can more easily communicate what the benefits are and what is available. Today, kdelibs could be described as 'A platform and set of integrated libraries to support the development of applications written by the KDE community'.

A more modular architecture could be described as 'KLibs, a set of Free Software functional libraries for Qt based applications' and 'KPlatform, an integrated set of libraries for applications written by the KDE community'.

=== Tasks ===

{| cellspacing="0" cellpadding="5" border="1" class="sortable" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;"
|- 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
! Object
! Change description
! Responsible
{{FeatureTodo|kdelibs|Split platformy code from functional libraries||}}
{{FeatureTodo|kdelibs|Merge kdesupport(which is all functional libraries) into kdelibs||}}
{{FeatureTodo|kdelibs|Remove K-Classes where Q-Classes are available and sufficient||}}
{{FeatureTodo|kdelibs|Consider refactoring K-Classes where Q-Classes are available but insufficient. Rather than subclasses and wrappers (which other libraries must use, increasing interdependence), it may be possible to redesign to use Builder pattern in some cases. Eg http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/classKRichTextEdit.html does not really need to be a subclass of QTextEdit.||}}
{{FeatureTodo|kdelibs|Consider splitting kdecore and kdeui into smaller non-platformy libraries. Additional library loading may be detrimental on some platforms.||}}
{{FeatureTodo|kdelibs|Consider contributing to Qt parts of kdelibs that are eligable and would be better to have there.||}}
{{FeatureTodo|kdepimlibs|Merge kdepimlibs non-platformy bits into kdelibs. Be more explicit about dependencies. Eg, KIMAP and libakonadi do not depend on all of kdecore, but mostly just kjob.||}}
{{FeatureTodo|kdepimlibs|Turn the remaining bits of kdepimlibs into pim platformy stuff only (depending on the kde platformy stuff)||}}
|}

Projects/KDELibsModifications

2010-10-30T01:36:48Z

Steveire: Add page about more modularization in libraries

== KDELibs Rearchitecture ==

=== Background ===

Several directions of Qt development and growth present opportunities to make technology created by the KDE community available to more platforms and to more developers of Qt based applications.

* The advancement of Qt to more and more varied hardware
* The use of Qt as the basis of MeeGo
* The use of Qt as the basis of other platforms in the future
* The use of Qt as the basis of other computer workspaces and interfaces in the future (http://mdzlog.alcor.net/2010/10/20/ubuntu-and-qt/)
* The increased use of Qt in environments such as Industrial Embedded (the machines in your kitchen and house)
* The increased use of Qt in creating Free and NonFree applications on desktop and mobile environments

This availability raises questions for Qt developers in those situations

* What can I use to create a primary widget-based workspace interface for my device? The answer should be libplasma.
* How do I initialize some hardware or software asynchronously and report progress? The answer should be KJob.
* What can I use for asynchronous access to IMAP servers? The answer should be KIMAP and KJob.
* Are there classes available for advanced model-view, or rich text editing? Yes, in Kdeui/itemviews

If GNOME ever switches to Qt, but wants to keep their own platformy bits like configuration format etc, where will they get Qt based libraries to create functionality for their Qt based platform?

=== The problem ===

One reason kde libraries are not currently the answer to the issues that Qt developers face is that 'platform parts' of kdelibs are introduced early instead of late in the module. For example the use of kdecore introduces requirements for things like KGlobal, KStandardDirs, KComponentData, KLocale, KConfig. While all useful for a workspace and application suite like KDE provides, none of those should be needed to use an asynchronous job API or itemviews library. Many for many Qt applications, QSettings and QObject::tr are sufficient because the application is deployed by the software vendor with specific hardware in a limited number of languages for example.

The bundling of the functional libraries of kdelibs and the platform integration pieces of kdelibs makes encouraging the use by third parties of the libraries but not the platform (where the KDE platform is irrelevant) difficult, not least from a point of view of communicating it clearly.

Discussion on k-c-d: http://thread.gmane.org/gmane.comp.kde.devel.core/67458

=== An option ===

One way of making the functional libraries of KDElibs more easily available is to split the kdelibs module into two modules named KLibs and KPlatform here for clarity. KLibs would be a 3 tier module:

==== Tier 0: Interfaces. ====
Some low level modules need access to platform specific data. For example, KLocale uses KStandardDirs to locate gettext translation catalogs. This makes KLocale dependent on the KDE platformy bits. An alternative design is to introduce an interface to get the paths, and implement it trivially on the Qt level, and with KDE integration at the platform level.

The interfaces tier would contain all the interfaces needed (probably few) to access platform specific 'simple types' like strings, urls etc.

It is possible that very pervasive classes in the current KDE4 would need to be in this tier (such as KDateTime), but that would be highly undesirable.

==== Tier 1: Independent libraries ====

Libraries such as KJob, KLocale (in theory at least), KItemViews, KConfig etc which can (be made to) exist standalone and depend only whatever dependencies give them their functionality (eg gettext) belong in Tier 1. Tier 1 libraries can not depend on each other, but can use the Tier 0 interfaces. The Tier 1 module is not QtCore only, but individual libraries might be.

==== Tier 2: Dependent libraries ====

Libraries such as KIMAP, KMIME, KMBox, libakonadi-kde can have hard dependencies on Tier 1 libraries (such as KJob) and on other Tier 2 libraries (KIMAP can use KMIME). Dependencies on platformy libraries from Tier 1 such as KConfig should be discouraged where using Tier 0 interfaces produces the same effect.

==== Platforms ====

KPlatform depends on many but not all of the libraries in the Tiers of KLibs. It implements the interfaces from Tier 0 in terms of the platformy stuff, KConfig, KStandardDirs, KStandardAction etc and contains classes like KComponentData, which all 'applications from the KDE community' use.

Pieces like KDED, KLauncher, KDEinit, KSyCoCa etc are also here.

It should be possible for an integrator similar to MeeGo which defines their own configuration system etc and implement the interfaces to create their own coherent platform and use the functional libraries.

=== Definitions ===

With increasing modularity of kde libraries, we can more easily communicate what the benefits are and what is available. Today, kdelibs could be described as 'A platform and set of integrated libraries to support the development of applications written by the KDE community'.

A more modular architecture could be described as 'KLibs, a set of Free Software functional libraries for Qt based applications' and 'KPlatform, an integrated set of libraries for applications written by the KDE community'.

=== Tasks ===

{| cellspacing="0" cellpadding="5" border="1" class="sortable" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;"
|- 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
! Object
! Change description
! Responsible
{{FeatureTodo|kdelibs|Split platformy code from functional libraries||}}
{{FeatureTodo|kdelibs|Merge kdesupport(which is all functional libraries) into kdelibs||}}
{{FeatureTodo|kdelibs|Remove K-Classes where Q-Classes are available and sufficient||}}
{{FeatureTodo|kdelibs|Consider refactoring K-Classes where Q-Classes are available but insufficient. Rather than subclasses and wrappers (which other libraries must use, increasing interdependence), it may be possible to redesign to use Builder pattern in some cases. Eg http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/classKRichTextEdit.html does not really need to be a subclass of QTextEdit.||}}
{{FeatureTodo|kdelibs|Consider splitting kdecore and kdeui into smaller non-platformy libraries. Additional library loading may be detrimental on some platforms.||}}
{{FeatureTodo|kdelibs|Consider contributing to Qt parts of kdelibs that are eligable and would be better to have there.||}}
{{FeatureTodo|kdepimlibs|Merge kdepimlibs non-platformy bits into kdelibs. Be more explicit about dependencies. Eg, KIMAP and libakonadi do not depend on all of kdecore, but mostly just kjob.||}}
{{FeatureTodo|kdepimlibs|Turn the remaining bits of kdepimlibs into pim platformy stuff only (depending on the kde platformy stuff)||}}
|}

Schedules/KDE4/4.5 Feature Plan

2010-05-03T09:15:11Z

Steveire: /* kdelibs */

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

See also:

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

<br> Legend:

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

__TOC__

<br>

= 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}}

|}

<br>

= 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
|}

<br>

= 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|nspluginviewer|npruntime scripting support|maksim@kde.org|Maks Orlovich}}
{{FeatureTodo|Konqueror|Add speeddial/thumbnails-like start page|germain@ebooksfrance.org|Germain Garand}}
{{FeatureDone|Konsole|Finish implementing tab context menu|kurt.hindenburg@gmail.com|Kurt Hindenburg}}
{{FeatureDone|Konsole|Allow setting tab profile from file on command-line|kurt.hindenburg@gmail.com|Kurt Hindenburg}}
{{FeatureInProgress|Konsole|Adds support for SHELL_SESSION_ID|kurt.hindenburg@gmail.com|Kurt Hindenburg}}
{{FeatureInProgress|Konsole|Modernize menu layout|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureInProgress|Konsole|Move to KTabWidget|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureInProgress|print-manager|New Print manager KCM and applet replacement, using C++|dantti85-pk@yahoo.com.br|Daniel Nicoletti}}
{{FeatureDone|Dolphin|Drag and drop on tabs|toddrme2178@gmail.com|Todd}}
{{FeatureInProgress|Dolphin|Make view sub-menus available as toolbar buttons|toddrme2178@gmail.com|Todd}}
{{FeatureInProgress|Dolphin|Smooth scrolling|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Dolphin|Faceted browsing|peter.penz@gmx.at|Peter Penz}}
{{FeatureTodo|Dolphin|Make use of additional columns in KDirModel/KFileItemDelegate|frank78@googlemail.com|Frank Reininghaus}}
|}
<br>

= 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 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|Locale KCM|Add support for new KLocale and KCalendarSystem features (see kdelibs section) including Digit Groups, AM/PM, etc. Improvements to usability of existing money display options.|john@layt.net|John Layt}}
{{FeatureInProgress|network kioslave|Backend for UPnP|kossebau@kde.org|Friedrich Kossebau}}
{{FeatureTodo|network kioslave| Backend to discover bluetooth devices and they services |edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureInProgress|bluetooth kioslave|Backend to browse bluetooth devices|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureDone|Nepomuk|Monitor file system changes via inotify|trueg@kde.org|Sebastian Trueg}}
{{FeatureTodo|KNotify|Route solid errors via knotify to the device notifier|wilderkde@gmail.com|Jacopo De Simoi}}
|}

<br>

= 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|BlueDevil Wizard |Write a new Wizard to pair Bluetooth devices |alex@eyeos.org|Alex Fiestas}}
{{FeatureTodo|Bluetooth KCM|New KCM to manage all bluetooth configurations and devices|ereslibre@kde.org|Rafael Fernandez}}
{{FeatureTodo|Screenedges|Screenedges handling outside of kwin/plasma|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|Oxygen style|Move window using left-mouse button on windows' empty areas|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}
{{FeatureInProgress|Oxygen configuration|Oxygen style and decoration standalone expert configuration tool|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}
{{FeatureInProgress|Free Space Notifier Daemon|Small daemon that warns you when your home has almost no space left|knuckles@gmail.com|Ivo Anjo}}
{{FeatureInProgress|Activities Daemons|Daemons to handle info about activities (kded daemon and a nepomuk service)|ivan.cukic@kde.org|Ivan Cukic}}
{{FeatureInProgress|Systemsettings|driconf KCM|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|PowerDevil|Display brightness OSD|debfx-kde@fobos.de|Felix Geyer}}
|-
! style="text-align: center;" colspan="4" | Plasma
{{FeatureInProgress|systemtray/taskmanager|port the systray and tasks applet to windows|windows@kde.org|kde windows}}
{{FeatureInProgress|systemtray|monochrome statusnotifier based systray icons support|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|systemtray|sort icons by category|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|systemtray|put hidden icons in a popup menu|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|tasks dataengine|export all informations needed to build an applet comparable to the current one|matthieu_gallien@yahoo.fr|Matthieu Gallien}}
{{FeatureDone|notifications|split systemtray and notifications applet|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|notifications|new look and behaviour for notifications|notmart@gmail.com|Marco Martin}}
{{FeatureDone|notifications|support for remote applets for notifications|notmart@gmail.com|Marco Martin}}
{{FeatureDone|netbook/SAL|use QStandardModels|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|netbook/SAL|support for drag and drop of items|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|netbook/SAL|package manager invocation from the toolbox|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|netbook/Workspace KCM|New default options for KWin: tabbox as present windows, that will be set as regular grid|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|libplasma/extenders|put extendergroups in scrollwidgets|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|libplasma/extenders|possibility to detach exteneritems as standalone windows|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|libplasma/theme|more transparent dialogs when the blur effect is enabled|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|libplasma/desktop|Activity Manager UI|chani@kde.org|Chani}}
{{FeatureTodo|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|libplasma|Improvements to Calendar/Clock widgets. Improved config ui. Allow multiple holidays on same day. Allow multiple Holiday Regions. Weekends. etc.|john@layt.net|John Layt}}
{{FeatureTodo|folderview|"Open folder" icon to open folder into pop-up at request instead of automatically.|bigras.bruno@gmail.com|Bruno Bigras}}
{{FeatureTodo|folderview|Extend the configuration UI for nepomuksearch|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Extend Calendar DataEngine with Akonadi calendar incidents|Allows to query calendar events/todos from Akonadi in Plasma|gladhornKDEorg|Frederik Gladhorn}}
{{FeatureDone|calculator|Added optional libqalculate support in the calculator runner|agostinelli@gmail.com|Matteo Agostinelli}}
{{FeatureInProgress|KRunner|Add some advanced sorting to KRunner using Nepomuk|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureTodo|KRunner|Improve keyboard navigation & command history interaction|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureInProgress|device-notifier|Route all solid error notifications via knotify to the device notifier|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureInProgress|device-notifier|Detailed (HAL) error notifications in the device notifier|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureInProgress|Plasma::Theme|Themed CSS support|sebas@kde.org|Sebastian Kügler}}
{{FeatureTodo|battery|Weighted charge information for multiple batteries|sebas@kde.org|Sebastian Kügler}}
{{FeatureTodo|Plasma|Welcome plasmoid|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureInProgress|crystal|New desktop search widget|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|networkmanagement|Network management Plasmoid|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|quicklaunch|Improvements from Ingomar Wesp|l.appelhans@gmx.de|Lukas Appelhans}}

|-
! style="text-align: center;" colspan="4" | KWin
{{FeatureTodo|Tiling|Merge window tiling branch|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|KWin|New flag to exclude windows from switchers|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KCM Decoration|New decoration kcm with previews and GHNS|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|Aurorae|Port Aurorae to GraphicsView and KDecoration|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|Aurorae|Better themeing support|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|Aurorae|Window tabbing support|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|Aurorae|Decorations on window sides|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|Aurorae|Autohiding decoration for maximized windows|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|kwin|hide windows from other activities|chani@kde.org|Chani}}
{{FeatureTodo|Effects|Move features from present windows to libkwineffects to make them available in desktop grid|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|Effects|Add close window button to each window in present windows/desktop grid|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|Window Tabbing/libtaskmanager|Announce window groups to be used for grouping in tasks applet|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|KWin/plasma|New window type for Plasma dashboard|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|Effects|New blur effect|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Effects|High quality scaling shader for the taskbar thumbnails|fredrik@kde.org|Fredrik Höglund}}
{{FeatureTodo|KWin|Hint for defining the window snap rect|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Effects|Glide effect for opening and closing windows|iori.yagami.26979@gmail.com|Iori Yagami}}
|}

<br>

= 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}}
{{FeatureTodo|Kalzium|Port Kalzium to use QGV based periodic table widget|mhanwell@kde.org|Marcus D. Hanwell}}
{{FeatureTodo|Marble|Add proper support for GPX waypoints, tracks and routes display|anders@alweb.dk|Anders Lund}}
{{FeatureTodo|Marble|Export map to MxN pixel bitmap|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Map Contents translation|tackat@kde.org|Torsten Rahn}}
{{FeatureDone|Marble|Support OpenStreetMap Nominatim as search backend (MarbleRunner)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Generalized Animations with GeoDataLookAt support|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Online-Routing|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|GPS improvements|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Maemo Support|earthwings@gentoo.org|Bastian Holst, Dennis Nienhüser}}
{{FeatureInProgress|Marble|GeoGraphicsScene for Online Service Plugins|bastianholst@gmx.de|Bastian Holst}}
{{FeatureInProgress|Marble|Follow XDG Base Directory Specification|bastianholst@gmx.de|Bastian Holst}}
{{FeatureDone|Marble|Download region|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|Implement sun locator blendings as derived classes of Marble::Blending|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|Configurable texture layer blending|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|Import geonames city data|sonu.itbhu@gmail.com|Harshit Jain}}
{{FeatureInProgress|Marble|Add new icons for online services|gabrieljoel@gmail.com|Gabriel Joel Perez}}
{{FeatureInProgress|Marble|Download Progressbar in Qt-only version|akssps011@gmail.com|Siddharth Srivastava}}
{{FeatureInProgress|Marble|Bookmark support|anik.varshney@gmail.com|Kumar Anik Varshney}}
{{FeatureInProgress|Marble|Various Marble speed improvements|rahn@kde.org|Torsten Rahn, Ariya Hidayat}}
{{FeatureInProgress|Marble|Plugin to display APRS data|hardaker@users.sourceforge.net|Wes Hardaker}}
{{FeatureDone|KAlgebra|Type checker for expressions to statically detect errors|aleixpol@kde.org|Aleix Pol}}
{{FeatureInProgress|KAlgebra|Support for drawing implicit curves|percy.camilo.ta@gmail.com|Percy Camilo Triveño Aucahuasi}}
{{FeatureInProgress|Parley|Parley practice mode rewritten|gladhornKDEorg|Daniel Laidig, Frederik Gladhorn}}
{{FeatureTodo|Parley|LaTeX support|laidig_kde.org|Daniel Laidig}}
{{FeatureTodo|Parley|Better support for entering synonyms|laidig_kde.org|Benjamin Schleinzer, Daniel Laidig}}
{{FeatureTodo|Cantor|import and polish Qalculate! backend|mail@milianw.de|Milian Wolff}}
{{FeatureInProgress|KTurtle|Implement GHNS download support|nielsslot@gmail.com|Niels Slot}}
{{FeatureTodo|KTurtle|Implement GHNS upload support|nielsslot@gmail.com|Niels Slot}}
{{FeatureDone|Rocs|Node beautification in SVG|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|Threads for not blocking the UI|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|Redesigned the UI for better usability|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|Plugin System|wiglot@gmail.com|Wagner Reck}}
{{FeatureDone|Rocs|Small plugins as examples|wiglot@gmail.com|Wagner Reck}}
{{FeatureDone|Rocs|Multiple Script support|tcanabrava@kde.org|Tomaz Canabrava}}
|}
<br>

= 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|Granatier|Arena Editor|k.hias@gmx.de|Mathias Kraus}}
{{FeatureInProgress|Kajongg|New traditional Mahjongg for four players|wolfgang@rohdewald.de|Wolfang Rohdewald}}
{{FeatureTodo|Kajongg|Default voices for computer players|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureTodo|Kajongg|Make playing against computer suspendable/resumable|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|KBounce|Difficulty levels|ascherfy@gmail.com|Andreas Scherf}}
{{FeatureDone|KBounce|Random images as background|ascherfy@gmail.com|Andreas Scherf}}
{{FeatureTodo|KBreakOut|Level Sets|fela.kde@gmail.com|Fela Winkelmolen}} {{FeatureTodo|KBreakOut|Sound|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureTodo|KGoldrunner|Add the Demolition game (20 levels)|iandw.au@gmail.com|Ian Wadham}}
{{FeatureDone|Kigo|Load SGF games from command line and register to mimetype 'application/x-go-sgf'|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureInProgress|Kigo|Fix KNewStuff provider issues|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureInProgress|Kiriki|Hint|luizromario@gmail.com|Luiz Romário Santana Rios}}
{{FeatureTodo|Kolf|Replace with Kolf 2 (help on coding and artwork desired)|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|Konquest|Merge the patch by Sean D'Epagnier to implement many features like map editing|pinaraf@pinaraf.info|Pierre Ducroquet}}
{{FeatureInProgress|KPat|Add keyboard controls to allow playing without a mouse.|parker.coates@kdemail.net|Parker Coates}}
{{FeatureInProgress|KPat|Create a new LibKCardGame from KPat's card scene logic. Make it generic and friendly enough for use in other card games. Make the library public if sufficient quality has been reached before SC4.5 release.|parker.coates@kdemail.net|Parker Coates}}
{{FeatureTodo|KPat|Add support for drop shadows, via support in LibKCardGame.|parker.coates@kdemail.net|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|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}}
{{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}}
{{FeatureInProgress|KTuberling|A new "fast switch" between playgrounds|alex@eyeos.org|Alex Fiestas}}
{{FeatureTodo|LSkat|Port display and interaction code to LibKCardGame. Depends on LibKCardGame being made a public library.|parker.coates@kdemail.net|Parker Coates}}
{{FeatureDone|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}233784 Optimize size of puzzle files in default collection] (temporarily fixed for this release cycle with an awful hack)|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}211859 Recieve new puzzles over KNewStuff]|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}211861 Introduce handicap as a means to configure difficulty]|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}211866 Implement puzzle piles to organize pieces]|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}212814 Quick piece grouping]|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}213774 Add magnifying glass]|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|Palapeli|Rewrite puzzle table mouse interaction stack|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|Palapeli|Cleanup config dialog code|majewsky@gmx.net|Stefan Majewsky}}
|}

<br>

= 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|libkdcraw|Make color management options more flexible|marcel.wiesweg@gmx.de|Marcel Wiesweg}}
{{FeatureDone|libksane|Improve auto-selection|kare.sars@iki.fi|Kåre Särs}}
{{FeatureInProgress|libksane|Highlight scanned area|kare.sars@iki.fi|Kåre Särs}}
{{FeatureTodo|libksane|Add public API for available devices|kare.sars@iki.fi|Kåre Särs}}
{{FeatureTodo|gwenview|Show Nepomuk info in image meta info|agateau@kde.org|Aurelien Gateau}}
{{FeatureTodo|gwenview|Persistent changes|agateau@kde.org|Aurelien Gateau}}
{{FeatureTodo|okular|Thumb creators via Okular Core|harsh@harshj.com|Harsh J}}

|}

<br>

= 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 visual block mode and make the basic commands support it|ehambergαgmail.com|Erlend Hamberg}}
{{FeatureTodo|katepart|context dependent indenters|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|scripting configuration, esp. for indenters|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|list of available scripts and indenters|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|GHNS for scripts/indenters|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|easier writing of indenters, esp. by automatically reloading them when changed|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|extend list of available default styles for highlighting, remove hardcoded colors from existing XML files|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|improve AutoBrace plugin|mail@milianw.de|Milian Wolff}}
{{FeatureInProgress|katepart/ktexteditor|defaultvalues, regular expressions, mirroring master, scripting of templates|jowenn(you_know)kde(here_too)org|Joseph Wenninger}}
{{FeatureInProgress|ktexteditor plugin|InsaneHTML_LE (zencoding like selector input (light edition)|jowenn(you_know)kde(here_too)org|Joseph Wenninger}}
{{FeatureTodo|katepart|replace smart cursor/ranges API|cullmann@kde.org|Christoph Cullmann}}
{{FeatureTodo|kdeui|API to integrate KStatusNotifierItem and KNotification: both as class api and DBus specification API|davide.bettio@kdemail.net|Davide Bettio}}
{{FeatureDone|KCalendarSystem|Add support for Date Difference calculations.|john@layt.net|John Layt}}
{{FeatureInProgress|KCalendarSystem|Add support for era based calendar systems.|john@layt.net|John Layt}}
{{FeatureInProgress|KCalendarSystem|Add support for Unicode format strings for Qt and cross-platform compatability.|john@layt.net|John Layt}}
{{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, Chinese, Japanese Era, Buddhist, Thai, etc.|john@layt.net|John Layt}}
{{FeatureTodo|KCalendarSystem|Add support for traditional/USA week numbering.|john@layt.net|John Layt}}
{{FeatureTodo|kdecore|Group policy (Windows) backend for KAuth|drf@kde.org|Dario Freddi}}
{{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}}
{{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|kdeui|DBus interface in StatusNotifierItem to connect it with freedesktop notifications instances|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|khtml|Improvements in kwallet integration|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureInProgress|khtml|Basic audio/video tag support|germain@ebooksfrance.org|Michael Howell and Germain Garand}}
{{FeatureInProgress|khtml|DOM3 XPath/XPath1 support|maksim@kde.org|Maks Orlovich}}
{{FeatureDone|khtml|Selectors API1|maksim@kde.org|Maks Orlovich}}
{{FeatureTodo|khtml and kparts|More general KPart scripting interfaces|maksim@kde.org|Maks Orlovich}}
{{FeatureTodo|khtml|Implement more of DOM3's CSSOM View module|germain@ebooksfrance.org|Germain Garand}}
{{FeatureInProgress|khtml|Implement missing parts of DOM3's Background and Borders module|germain@ebooksfrance.org|Germain Garand}}
{{FeatureTodo|khtml|add new form widgets defined in HTML5 draft|germain@ebooksfrance.org|Germain Garand}}
{{FeatureDone|KNewStuff|Improved Download Dialog, multiple previews, better integration of details, changelog is displayed|gladhornKDEorg|Frederik Gladhorn}}
{{FeatureInProgress|KNewStuff|Icon view mode|gladhornKDEorg|Reza Shah, Frederik Gladhorn}}
{{FeatureDone|KNewStuff|Upload dialog rewritten: It now supports updating of old uploads, previews, most data that can be entered on the website and allows direct login to the account|gladhornKDEorg|Frederik Gladhorn}}
{{FeatureTodo|KNewStuff|Support more than one payload|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureTodo|kdeui|Social About Dialog|teo@kde.org|Téo Mrnjavac}}
{{FeatureTodo|kdeui|Generic find bar widget|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureTodo|kio|SSL client certificate support|ahartmetz@gmail.com|Andreas Hartmetz}}
{{FeatureTodo|kio|SSL root certificate list GUI + backend|ahartmetz@gmail.com|Andreas Hartmetz}}
{{FeatureDone|kio|Add "apply to all" checkbox in renamedialog and allow for automatic renaming|toddrme2178@gmail.com|Todd}}
{{FeatureInProgress|kio|Port renamedialog to KFileMetaDataWidget|toddrme2178@gmail.com|Todd}}
{{FeatureDone|kio|Don't select extension in renamedialog|toddrme2178@gmail.com|Todd}}
{{FeatureDone|kio|Better listing of applications in file "open with" context menu|toddrme2178@gmail.com|Todd}}
{{FeatureDone|kio|Context menu entry to open all files in their default applications|toddrme2178@gmail.com|Todd}}
{{FeatureTodo|kio|Add support for additional columns (e.g., smybolic link destination) in KDirModel/KFileItemDelegate|frank78ac@googlemail.com|Frank Reininghaus}}
{{FeatureDone|kfile|Scroll wheel support for breadcrumb bar|toddrme2178@gmail.com|Todd}}
{{FeatureDone|kfile|Show all sub-folders in breadcrumb bar|toddrme2178@gmail.com|Todd}}
{{FeatureInProgress|kfile|Middle-click on subfolder in the breadcrumb bar to open in a new tab|toddrme2178@gmail.com|Todd}}
{{FeatureInProgress|kfile|Easier access to protocols in breadcrumb bar|toddrme2178@gmail.com|Todd}}
{{FeatureTodo|kfile|Show sub-sub-folders (and so on) in breadcrumb bar|toddrme2178@gmail.com|Todd}}
{{FeatureInProgress|kdecore|Generic shared-memory cache|mpyne@kde.org|Michael Pyne}}
{{FeatureInProgress|kdeui|Redesigned icon cache|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|kdeui|Support alpha channel in KColor classes|christoph@maxiom.de|Christoph Feck}}
{{FeatureDone|nepomuk|Redesigned Nepomuk::TagWidget which can now actually be used by applications|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|kio|Remember downloads via Nepomuk|trueg@kde.org|Sebastian Trueg}}
{{FeatureDone|solid|Broadcast mount/unmount messages across processes|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureTodo|solid|Add parent matching to predicate parsing|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureDone|kdeui|Add the KRecursiveFilterProxyModel to kdeui/itemviews|steveire@gmail.com|Stephen Kelly}}
|}
<br>

= 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
{{FeatureInProgress|Video Thumbnailer|Add ffmpegthumbnailer for faster video thumbnailing|ascherfy@gmail.com|Andreas Scherf}}
{{FeatureTodo|JuK|Remove Qt/KDE3 support lib requirements -- will move to KDE 4.5 feature plan|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|JuK|Allow setting covers directly from URLs supported by KIO - drag/drop already allows this however -- will move to KDE 4.5 feature plan|mpyne.org|Michael Pyne}}

|}

<br>

= 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}}
{{FeatureDone|Kopete|Extended video controls|fschaefer.oss(at)googlemail.com|Frank Schaefer}}
{{FeatureTodo|Kopete|Akonadi History Plugin|roideuniverse@gmail.com|Kaushik Saurabh}}
{{FeatureTodo|Krdc|Connection status screen and reconnect|murraytony@gmail.com|Tony Murray}}
{{FeatureDone|Krdc|Much improved new connection screen: more info, sortable, interactive, and better use of space|murraytony@gmail.com|Tony Murray}}
{{FeatureInProgress|KGet|Use plasma notifications to show the progress|mat69@gmx.net|Matthias Fuchs}}
{{FeatureDone|KGet|Refaktor Torrent-Plugin to base on the newly created libktorrent from extragear|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureInProgress|KGet|Better error handling|l.appelhans@gmx.de|Lukas Appelhans}}
|}

<br>

= 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
{{FeatureTodo|KAlarm|Port to Akonadi|djarvie@kde.org|David Jarvie}}
{{FeatureInProgress|KMail|Port to Akonadi|kde-pim@kde.org|Thomas McGuire}}
{{FeatureInProgress|KOrganizer|Port to Akonadi|kde-pim@kde.org|Frank Osterfeld, Sebastian Sauer}}
{{FeatureInProgress|KJots|Port to Akonadi|kde-pim@kde.org|Stephen Kelly}}
{{FeatureInProgress|KHolidays|Add support for alternative calendar systems, advanced holiday calculations, and improved API.|john@layt.net|John Layt}}
|}

<br>

= 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
{{FeatureTodo|knowledgebase|port knowledgebase plasmoid to new engine|ewoerner@kde.org|Eckhart Wörner}}
{{FeatureTodo|knowledgebase|Add categories|ewoerner@kde.org|Eckhart Wörner}}
{{FeatureDone|Bookmarks widget|New|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Mandelbrot Wallpaper|Performance improvements|jacob.benoit.1@gmail.com|Benoit Jacob}}
{{FeatureDone|Mandelbrot Wallpaper|Rendering improvements (through dithering, extra iterations, and better/simpler formulas)|jacob.benoit.1@gmail.com|Benoit Jacob}}
{{FeatureDone|Mandelbrot Wallpaper|Allow to import/export parameters and to export to PNG images|jacob.benoit.1@gmail.com|Benoit Jacob}}
{{FeatureDone|Comic Applet|Add option to show "text", "icons" or both "text and icons" for tabs|mat69@gmx.net|Matthias Fuchs}}
{{FeatureDone|Comic Applet|Prefetch next and previous comic strip (thx to Miha Cancula)|mat69@gmx.net|Matthias Fuchs}}
{{FeatureDone|Character Runner|New|akreuzkamp@web.de|Anton Kreuzkamp}}
{{FeatureDone|KDE Observatory|Performance improvements, new data engine|sandroandrade@kde.org|Sandro Andrade}}
{{FeatureInProgress|Plasmaboard|Completly rework the current onscreen keyboard and add key layouts for tablets and mids|bjoern@ruberg-wegener.de|Björn Ruberg}}
|}

<br>

= 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}}
{{FeatureInProgress|Kate|Replace old snippet plugin through TNG plugin and enhance the usability of the new plugin|jowenn(you_know)kde(here_too)org|Joseph Wenninger}}
{{FeatureInProgress|Kate|Port the old XML completion plugin (xmltools)|tomastrnka@gmx.com|Tomáš Trnka}}
{{FeatureInProgress|Umbrello|Add a code importing wizzard|andi.fischer@NOSPAMhispeed.ch|Andi Fischer}}
|}

<br>

= 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|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|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|Ark|Add a "Preview with..." context menu item|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|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|KGpg|Make keyserver actions possible to use on multiple keyservers at once|kde@opensource.sf-tec.de|Rolf Eike Beer}}
{{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 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 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|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|Store bookmarks|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add view profiles, incl. editor/manager|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|printer-applet|Restore feature parity with KDEPrint3 where possible.||Jonathon Riddell, John Layt}}
{{FeatureDone|kdelirc/kremotecontrol|Transition from KDELirc to KRemoteControl|michael_zanetti@gmx.net|Michael Zanetti}}
{{FeatureInProgress|KGpg|Add "caff" mode for keysigning|kde@opensource.sf-tec.de|Rolf Eike Beer}}
{{FeatureInProgress|Okteta|Allow writing structure definitions in JavaScript|alex.richardson@gmx.de|Alex Richardson}}
{{FeatureInProgress|Okteta|Add KNewStuff support to the structures tool|alex.richardson@gmx.de|Alex Richardson}}
{{FeatureInProgress|Okteta|Allow pinning structure beginning to a specific offset|alex.richardson@gmx.de|Alex Richardson}}
{{FeatureInProgress|Okteta|Add possibility to set count of bytes per line/group|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|new export formats: S-Record, Intel Hex, Base32, Ascii85, Uuencoding, Xxencoding|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|add QIODevice for AbstractByteArrayModel and make mimetype detection use this instead of only filename |kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|Refactor mouse input to controllers for the bytearray widget|kossebau@kde.org|Friedrich W. H. Kossebau}}
|}

<br>

= kdetoys =

{| 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|kteatime|Port to KStatusNotifierItem|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureInProgress|kteatime|Port to KConfigXT|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureInProgress|kteatime|Support categories|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureInProgress|kteatime|Improved indicator icon painting|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|kteatime|Fork multiple instances for multiple timers|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|kteatime|Tea runner|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|kteatime|Improved command line|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|amor|Do some refactoring in amor|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|amor|Improve theme support|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|amor|Implement KNewStuff support|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|amor|Revamp configure dialog|kde@hilefoks.org|Stefan Böhmann}} {{FeatureTodo|amor|Sound support|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|amor|Add KStatusNotifierItem support|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureInProgress|ktux|Do some refactoring in ktux|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|ktux|Revamp configure dialog|kde@hilefoks.org|Stefan Böhmann}} {{FeatureTodo|ktux|Sound support|kde@hilefoks.org|Stefan Böhmann}}
|}

<br>

= 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

|}

Projects/MovetoGit

2010-05-02T14:08:10Z

Steveire: /* Requirements of KDEPIM and KDAB */ Update progress list

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 [http://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 want to be in this group, file a bugreport for sysadmin on bugs.kde.org. :)

The procedure to move a project from svn to gitorious.org can be found in [[Projects/MoveToGit/StepsToMove|Steps to follow for Moving]].

=Blockers=

Tasks that need to get done before we can migrate

==SLA for gitorious.org==
{{Progress bar|30}}
'''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.

: aseigo and Frank (and someone?) had a meeting with Shortcut people during tokamak. They asked for a rather large sum of money; negotiations are continuing, but we might want to consider hosting our own server...

==Write / update importing rules for svn2git==
{{Progress bar|5}}
'''Owner:''' see below - 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 [[Projects/MoveToGit/UsingSvn2Git|Using 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
|tnyblom
|25
|Basic rules in place, testing and tweaking pending.
|-
|SC/kdepim-runtime
|tnyblom
|25
|Basic rules in place, testing and tweaking pending.
|-
|SC/kdepimlibs
|tnyblom
|90
|Some minor history glitches, but mostly done.
|-
|SC/kdeplasma-addons
|
|0
|
|-
|SC/kdesdk
|
|0
|
|-
|SC/kdetoys
|
|0
|
|-
|SC/kdeutils
|
|0
|
|-
|SC/kdewebdev
|
|0
|
|-
|extragear/sdk/kdevelop
| apaku
| 95
| trunk and branches complete, need to cleanup tags from cvs days.
|-
|extragear/sdk/kdevplatform
| apaku
| 100
| done, all tags seem fine all branches are there
|-
|extragear/sdk/kdevelop-plugins
| nsams
| 100
| done
|-
|extragear/sdk/quanta
| nsams
| 99
| done
|-
|extragear/utils/krecipes
| santa
| 10
|
|-
|extragear/*/*
|
|xx
|expand the *'s later (let's focus on the base modules first)
|-
|kde-common
|mattr
|75
|analyzing import history
|-
|kdesupport
|
|0
|
|-
|koffice
|tzander
|85
|All but tags are done
|-
|promo
|
|0
|
|-
|quality
|
|0
|
|-
|tests
|
|0
|
|}

== Requirements of KDEPIM and KDAB ==

{{Progress bar|90}}
'''Owner:''' Stephen Kelly

'''Status:''' ''Proposed workflow identified. Partially depends on KDE policies regarding branches and merging. Gathering estimates for porting of tooling from svn to git. People unfamiliar with the tool are starting to learn to use it.''

'''Estimated completion date''': End of May.

'''Summary of issues'''

* Clean slate
** The existing backlog of commits which need to be merged or ported to trunk needs to be empty before the change to git so that nothing gets lost. This is a lot of work and will take time. ''Estimate'' 10 calendar weeks.
* Technical difficulties and limitations.
** Up to KDE 3.5 there was one kdepim module. For the KDE4 cycle, this was split into kdepimlibs and kdepim. For the above mentioned merging to be possible, it makes sense for both to be in the same git module. This poses extra difficulty to the svn2git script.

'''Email threads'''

* Mid-January thread on scm-interest: http://thread.gmane.org/gmane.comp.kde.devel.pim/26726
* Early March thread on kde-core-devel (Till email): http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=63970
* Early March thread on kde-core-devel (Till follow-up):
http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=64069

'''Resolved Issues'''

* Branch maintenance workflow '''Resolution: http://thread.gmane.org/gmane.comp.kde.scm-interest/1310'''
** KDAB maintains several branches of legacy versions of KDE for enterprise customer deployments. [http://websvn.kde.org:80/branches/kdepim/enterprise/ Enterprise 3.5] [http://websvn.kde.org:80/branches/kdepim/enterprise4/ Enterprise 4 (based on KDE 4.2)]. The current KDEPIM trunk known as Enterprise 5 and is Akonadi based.
** Periodically (weekly or so), tags are created from the enterprise branches with bugfixes. http://websvn.kde.org:80/tags/kdepim/ Customers can download the tagged versions with the latest updates. Fixes are merged from the Enterprise 3.5 branch, and into trunk (which sometimes involves a lot of work, as the fix must be ported to Akonadi). Additionally, fixes get merged in the other direction. From official KDE modules into the Enterprise branches.
** Some fixes from Enterprise 3.5 should not be merged into Enterprise 4 for reasons such as no longer being reproducible. Some fixes do not get merged for a long time because they require so much work that porting the fix or feature is deffered. There needs to be a list of commits which should never be merged (blocked commits), and commits which should be merged, but have not been merged yet. The tool [[Development/Tools/svnmerge.py|svnmerge]] is used to facilitate this. svnmerge uses svn properties to maintain lists of commits that are blocked and that have already been integrated. See for example the svn-blocked and svn-integrated properties here: http://websvn.kde.org:80/trunk/KDE/kdepim/. The lists of commits available to be merged into the various branches are here: http://www.kdab.com/~thomas/avail/
** There needs to be a way in git to keep track of what commits have been merged, what commits need to be merged, and what commits are blocked. There needs to be a way of merging only specific commits from a branch, but not all, and not blocked commits. Proposed solutions:
*** git cherry-pick allows 'merging' of individual commits, but does not record where the commits came from. Instead it creates a new commit without any reference to where it came from. This alone is unsuitable.
*** branch per fix. This would lead to an explosion of branches which is not a problem in git as all commits are branches. It may make gitk un-navigatable. There would need to be a naming convention such as komo-merge-<fixname> for branches which should be merged. The commands <tt>git checkout 4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout enterprise4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout master && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt>. That could of course be optimized, but gets the point across. If the code has changed so much that the branch is unmergable, but the fix still needs to be in trunk, the system breaks down.
*** Custom git command with flat text files representing the same information as svnmerge, that is lists of blocked and integrated commits. This is most likely to be a workable solution, possibly together with conventional branch naming.
* Internal Tools and external customer tools and workflows
** KDAB is a consumer of KDE software, but also has downstream customers fetching software from where it is developed. That is, KDE SVN. For example packages are created from the tags in tags/kdepim. Some of these downstreams are less close to KDE and depend on current workflows. If KDE SVN is not the place to get those updates anymore, this needs to be communicated to those downstreams, and the tools updated. ''Estimate'' 1 week to port the tools.
*** Internally used tools have been updated and are now being used to access git repos such as dbus.
* Other commitments
** Project deadlines and other commitments prevent the possibility of blocking off time to work on git migration when so many other things need to be done which have milestones separate to KDE cycles. The required work to convert to git can't be prioritized as highly, and so will take more time.
*** Most of the technical work regarding migration of kdepim repos has been completed by community member Torgny Nyblom.
* Tool knowledge
** People who don't currently know how to use git need to get familiar with it so that transitioning will be nearly seamless, and not result in too much development slowdown.
*** Workshops and use of git-svn have been used to bring developers up to speed on how to use git at some level.

=Nice to have before the migration=

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

'''Status:''' argonel had a 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.

-----------

This does not require help from gitorious.org until the script is actually written: it's just another pre-receive hook for them to install on their servers.
it *might* also be possible to run it as a post-receive hook (in which case we can do the whole thing ourselves).

if we self-host, then we won't need this.

==Script for downloading virtual KDE hierarchies==
{{Progress bar|0}}
'''Owner''':

'''Status:'''

:Let's start over on this.
what we already have: two build scripts for kde; kdesvn-build and build-tool.
what we want: an easy way for people to get large chunks of kde, without thinking about what urls the repos come from or having to look things up.

do kde-svnbuild and build-tool satisfy this well enough?
or do we want a computer-readable file listing all the repos too?

btw, scripty has its own list of repos already. it's just in a rather weird bash file.

'''Links'''
[http://kdesvn-build.kde.org/]
[[Projects/MovetoGit/MassCloneScript]]
[http://rubyforge.org/projects/build-tool/]

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

==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'''

: I think most people have made their own accounts by now. this isn't really needed.

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

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

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

:not possible with git, broken by design.

::

'''Discussion'''

Exists, but ignorable:
* kdesupport shared-desktop-ontologies (temporary)
* 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
* 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

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

==kde-common/accounts==

Someone said: KDE accounts file is no longer necessary---used for mapping svn ID -> email, but we have that now from Gitorious.
Answer from David Faure: I strongly disagree. We still need a KDE accounts file. This is very useful for finding people's email addresses, and having an overview on the number of active kde contributors; and if we keep it we can even have a kdepim resource again for filling an addressbook from it, for completion in kmail's composer (so you can write to any other kde contributor by just typing his/her name). It's also used for populating automatically the kde-cvs-announce mailing-list, for announcements. kde-common/accounts is our family tree (well, list), let's not get rid of it.

Here's my proposal for a kde-common/accounts replacement for the git era: We write a post-receive hook that looks at every commit and records all known email addresses for a given real name as well as the commit hash and date of when an address was last encountered. We can then present that data in the form of a file like kde-common/accounts, or write a web interface to query it (with nice links to the commits on Gitorious, etc.) --Eike (Sho_ on IRC)

To clear up possible confusion: The author information for a given commit is baked into the commit object itself, and comes from the configuration of the git repository it was created in. It is unrelated to any Gitorious account. Due to the distributed nature of Git, the one who uses his Gitorious account to push a commit need not be the same who created it. If Developer A creates a commit in his local clone and Developer B fetches it into his local clone directly from Developer A's machine and then pushes it into the public repo, the repo will only show a commit from Developer A. The Gitorious website will show that Developer B has pushed up a commit from Developer A, but that data is not contained in the repository. Thus collecting only Gitorious accounts and their mail addresses is insufficient. --Eike

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

Schedules/KDE4/4.5 Feature Plan

2010-04-26T17:25:49Z

Steveire: /* kdelibs */

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

See also:

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

<br> Legend:

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

__TOC__

<br>

= 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}}

|}

<br>

= 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
|}

<br>

= 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|nspluginviewer|npruntime scripting support|maksim@kde.org|Maks Orlovich}}
{{FeatureDone|Konsole|Finish implementing tab context menu|kurt.hindenburg@gmail.com|Kurt Hindenburg}}
{{FeatureInProgress|Konsole|Allow setting tab profile from file on command-line|kurt.hindenburg@gmail.com|Kurt Hindenburg}}
{{FeatureInProgress|Konsole|Adds support for SHELL_SESSION_ID|kurt.hindenburg@gmail.com|Kurt Hindenburg}}
{{FeatureInProgress|Konsole|Modernize menu layout|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureInProgress|Konsole|Move to KTabWidget|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureInProgress|print-manager|New Print manager KCM and applet replacement, using C++|dantti85-pk@yahoo.com.br|Daniel Nicoletti}}
{{FeatureDone|Dolphin|Drag and drop on tabs|toddrme2178@gmail.com|Todd}}
{{FeatureInProgress|Dolphin|Make view sub-menus available as toolbar buttons|toddrme2178@gmail.com|Todd}}
{{FeatureInProgress|Dolphin|Smooth scrolling|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Dolphin|Faceted browsing|peter.penz@gmx.at|Peter Penz}}
{{FeatureTodo|Dolphin|Make use of additional columns in KDirModel/KFileItemDelegate|frank78@googlemail.com|Frank Reininghaus}}
|}
<br>

= 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 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|Locale KCM|Add support for new KLocale features (see kdelibs section) including Digit Groups, AM/PM, etc. Improvements to usability of existing money display options.|john@layt.net|John Layt}}
{{FeatureInProgress|network kioslave|Backend for UPnP|kossebau@kde.org|Friedrich Kossebau}}
{{FeatureTodo|network kioslave| Backend to discover bluetooth devices and they services |edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureInProgress|bluetooth kioslave|Backend to browse bluetooth devices|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureDone|Nepomuk|Monitor file system changes via inotify|trueg@kde.org|Sebastian Trueg}}
{{FeatureTodo|KNotify|Route solid errors via knotify to the device notifier|wilderkde@gmail.com|Jacopo De Simoi}}
|}

<br>

= 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|BlueDevil Wizard |Write a new Wizard to pair Bluetooth devices |alex@eyeos.org|Alex Fiestas}}
{{FeatureTodo|Bluetooth KCM|New KCM to manage all bluetooth configurations and devices|ereslibre@kde.org|Rafael Fernandez}}
{{FeatureTodo|Screenedges|Screenedges handling outside of kwin/plasma|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|Oxygen style|Move window using left-mouse button on windows' empty areas|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}
{{FeatureInProgress|Oxygen configuration|Oxygen style and decoration standalone expert configuration tool|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}
{{FeatureInProgress|Free Space Notifier Daemon|Small daemon that warns you when your home has almost no space left|knuckles@gmail.com|Ivo Anjo}}
{{FeatureInProgress|Activities Daemons|Daemons to handle info about activities (kded daemon and a nepomuk service)|ivan.cukic@kde.org|Ivan Cukic}}
{{FeatureInProgress|Systemsettings|driconf KCM|fredrik@kde.org|Fredrik Höglund}}
|-
! style="text-align: center;" colspan="4" | Plasma
{{FeatureInProgress|systemtray/taskmanager|port the systray and tasks applet to windows|windows@kde.org|kde windows}}
{{FeatureInProgress|systemtray|monochrome statusnotifier based systray icons support|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|systemtray|sort icons by category|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|systemtray|put hidden icons in a popup menu|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|tasks dataengine|export all informations needed to build an applet comparable to the current one|matthieu_gallien@yahoo.fr|Matthieu Gallien}}
{{FeatureDone|notifications|split systemtray and notifications applet|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|notifications|new look and behaviour for notifications|notmart@gmail.com|Marco Martin}}
{{FeatureDone|notifications|support for remote applets for notifications|notmart@gmail.com|Marco Martin}}
{{FeatureDone|netbook/SAL|use QStandardModels|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|netbook/SAL|support for drag and drop of items|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|netbook/SAL|package manager invocation from the toolbox|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|netbook/Workspace KCM|New default options for KWin: tabbox as present windows, that will be set as regular grid|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|libplasma/extenders|put extendergroups in scrollwidgets|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|libplasma/extenders|possibility to detach exteneritems as standalone windows|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|libplasma/theme|more transparent dialogs when the blur effect is enabled|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|libplasma/desktop|Activity Manager UI|chani@kde.org|Chani}}
{{FeatureTodo|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|libplasma|Improvements to Calendar/Clock widgets. Improved config ui. Allow multiple holidays on same day. Allow multiple Holiday Regions. Weekends. etc.|john@layt.net|John Layt}}
{{FeatureTodo|folderview|"Open folder" icon to open folder into pop-up at request instead of automatically.|bigras.bruno@gmail.com|Bruno Bigras}}
{{FeatureTodo|folderview|Extend the configuration UI for nepomuksearch|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Extend Calendar DataEngine with Akonadi calendar incidents|Allows to query calendar events/todos from Akonadi in Plasma|gladhornKDEorg|Frederik Gladhorn}}
{{FeatureDone|calculator|Added optional libqalculate support in the calculator runner|agostinelli@gmail.com|Matteo Agostinelli}}
{{FeatureInProgress|KRunner|Add some advanced sorting to KRunner using Nepomuk|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureTodo|KRunner|Improve keyboard navigation & command history interaction|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureInProgress|device-notifier|Route all solid error notifications via knotify to the device notifier|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureInProgress|device-notifier|Detailed (HAL) error notifications in the device notifier|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureInProgress|Plasma::Theme|Themed CSS support|sebas@kde.org|Sebastian Kügler}}
{{FeatureTodo|battery|Weighted charge information for multiple batteries|sebas@kde.org|Sebastian Kügler}}
{{FeatureTodo|Plasma|Welcome plasmoid|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureInProgress|crystal|New desktop search widget|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|networkmanagement|Network management Plasmoid|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|quicklaunch|Improvements from Ingomar Wesp|l.appelhans@gmx.de|Lukas Appelhans}}

|-
! style="text-align: center;" colspan="4" | KWin
{{FeatureTodo|Tiling|Merge window tiling branch|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|KWin|New flag to exclude windows from switchers|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KCM Decoration|New decoration kcm with previews and GHNS|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|Aurorae|Port Aurorae to GraphicsView and KDecoration|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|Aurorae|Better themeing support|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|Aurorae|Window tabbing support|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|Aurorae|Decorations on window sides|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|Aurorae|Autohiding decoration for maximized windows|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|kwin|hide windows from other activities|chani@kde.org|Chani}}
{{FeatureTodo|Effects|Move features from present windows to libkwineffects to make them available in desktop grid|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|Effects|Add close window button to each window in present windows/desktop grid|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|Window Tabbing/libtaskmanager|Announce window groups to be used for grouping in tasks applet|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|KWin/plasma|New window type for Plasma dashboard|kde@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|Effects|New blur effect|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Effects|High quality scaling shader for the taskbar thumbnails|fredrik@kde.org|Fredrik Höglund}}
{{FeatureTodo|KWin|Hint for defining the window snap rect|fredrik@kde.org|Fredrik Höglund}}
|}

<br>

= 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}}
{{FeatureTodo|Marble|Add proper support for GPX waypoints, tracks and routes display|anders@alweb.dk|Anders Lund}}
{{FeatureTodo|Marble|Export map to MxN pixel bitmap|inge@lysator.liu.se|Inge Wallin}}
{{FeatureTodo|Marble|Map Contents translation|tackat@kde.org|Torsten Rahn}}
{{FeatureTodo|Kalzium|Port Kalzium to use QGV based periodic table widget|mhanwell@kde.org|Marcus D. Hanwell}}
{{FeatureDone|Marble|Support OpenStreetMap Nominatim as search backend (MarbleRunner)|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Generalized Animations with GeoDataLookAt support|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Online-Routing|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|GPS improvements|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Maemo Support|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|GeoGraphicsScene for Online Service Plugins|bastianholst@gmx.de|Bastian Holst}}
{{FeatureDone|Marble|Download region|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|Implement sun locator blendings as derived classes of Marble::Blending|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|Configurable texture layer blending|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureInProgress|Marble|Import geonames city data|sonu.itbhu@gmail.com|Harshit Jain}}
{{FeatureInProgress|Marble|Add new icons for online services|gabrieljoel@gmail.com|Gabriel Joel Perez}}
{{FeatureInProgress|Marble|Download Progressbar in Qt-only version|akssps011@gmail.com|Siddharth Srivastava}}
{{FeatureInProgress|Marble|Bookmark support|anik.varshney@gmail.com|Kumar Anik Varshney}}
{{FeatureInProgress|Marble|Various Marble speed improvements|rahn@kde.org|Torsten Rahn, Ariya Hidayat}}
{{FeatureDone|KAlgebra|Type checker for expressions to statically detect errors|aleixpol@kde.org|Aleix Pol}}
{{FeatureInProgress|KAlgebra|Support for drawing implicit curves|percy.camilo.ta@gmail.com|Percy Camilo Triveño Aucahuasi}}
{{FeatureInProgress|Parley|Parley practice mode rewritten|gladhornKDEorg|Daniel Laidig, Frederik Gladhorn}}
{{FeatureTodo|Parley|LaTeX support|laidig_kde.org|Daniel Laidig}}
{{FeatureTodo|Parley|Better support for entering synonyms|laidig_kde.org|Benjamin Schleinzer, Daniel Laidig}}
{{FeatureTodo|Cantor|import and polish Qalculate! backend|mail@milianw.de|Milian Wolff}}
{{FeatureInProgress|KTurtle|Implement GHNS download support|nielsslot@gmail.com|Niels Slot}}
{{FeatureTodo|KTurtle|Implement GHNS upload support|nielsslot@gmail.com|Niels Slot}}
{{FeatureDone|Rocs|Node beautification in SVG|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|Threads for not blocking the UI|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|Redesigned the UI for better usability|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|Plugin System|wiglot@gmail.com|Wagner Reck}}
{{FeatureDone|Rocs|Small plugins as examples|wiglot@gmail.com|Wagner Reck}}
{{FeatureDone|Rocs|Multiple Script support|tcanabrava@kde.org|Tomaz Canabrava}}
|}
<br>

= 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|Granatier|Arena Editor|k.hias@gmx.de|Mathias Kraus}}
{{FeatureDone|KBounce|Difficulty levels|ascherfy@gmail.com|Andreas Scherf}}
{{FeatureDone|KBounce|Random images as background|ascherfy@gmail.com|Andreas Scherf}}
{{FeatureTodo|KBreakOut|Level Sets|fela.kde@gmail.com|Fela Winkelmolen}} {{FeatureTodo|KBreakOut|Sound|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureTodo|KGoldrunner|Add the Demolition game (20 levels)|iandw.au@gmail.com|Ian Wadham}}
{{FeatureInProgress|Kiriki|Hint|luizromario@gmail.com|Luiz Romário Santana Rios}}
{{FeatureTodo|Kolf|Replace with Kolf 2 (help on coding and artwork desired)|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|Konquest|Merge the patch by Sean D'Epagnier to implement many features like map editing|pinaraf@pinaraf.info|Pierre Ducroquet}}
{{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}}
{{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}}
{{FeatureInProgress|Kajongg|New traditional Mahjongg for four players|wolfgang@rohdewald.de|Wolfang Rohdewald}}
{{FeatureTodo|Kajongg|Default voices for computer players|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureTodo|Kajongg|Make playing against computer suspendable/resumable|wolfgang@rohdewald.de|Wolfgang Rohdewald}}
{{FeatureDone|Kigo|Load SGF games from command line and register to mimetype 'application/x-go-sgf'|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureInProgress|Kigo|Fix KNewStuff provider issues|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureInProgress|KTuberling|A new "fast switch" between playgrounds|alex@eyeos.org|Alex Fiestas}}
{{FeatureTodo|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}233784 Optimize size of puzzle files in default collection]|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}211859 Recieve new puzzles over KNewStuff]|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}211861 Introduce handicap as a means to configure difficulty]|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}211866 Implement puzzle piles to organize pieces]|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}212814 Quick piece grouping]|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|Palapeli|[https://bugs.kde.org/show_bug.cgi?id{{=}}213774 Add magnifying glass]|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|Palapeli|Rewrite puzzle table mouse interaction stack|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|Palapeli|Cleanup config dialog code|majewsky@gmx.net|Stefan Majewsky}}
|}

<br>

= 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|libkdcraw|Make color management options more flexible|marcel.wiesweg@gmx.de|Marcel Wiesweg}}
{{FeatureDone|libksane|Improve auto-selection|kare.sars@iki.fi|Kåre Särs}}
{{FeatureInProgress|libksane|Highlight scanned area|kare.sars@iki.fi|Kåre Särs}}
{{FeatureTodo|libksane|Add public API for available devices|kare.sars@iki.fi|Kåre Särs}}
{{FeatureTodo|gwenview|Show Nepomuk info in image meta info|agateau@kde.org|Aurelien Gateau}}
{{FeatureTodo|gwenview|Persistent changes|agateau@kde.org|Aurelien Gateau}}
{{FeatureTodo|okular|Thumb creators via Okular Core|harsh@harshj.com|Harsh J}}

|}

<br>

= 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 visual block mode and make the basic commands support it|ehambergαgmail.com|Erlend Hamberg}}
{{FeatureTodo|katepart|context dependent indenters|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|scripting configuration, esp. for indenters|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|list of available scripts and indenters|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|GHNS for scripts/indenters|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|easier writing of indenters, esp. by automatically reloading them when changed|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|extend list of available default styles for highlighting, remove hardcoded colors from existing XML files|mail@milianw.de|Milian Wolff}}
{{FeatureTodo|katepart|improve AutoBrace plugin|mail@milianw.de|Milian Wolff}}
{{FeatureInProgress|katepart/ktexteditor|defaultvalues, regular expressions, mirroring master, scripting of templates|jowenn(you_know)kde(here_too)org|Joseph Wenninger}}
{{FeatureInProgress|ktexteditor plugin|InsaneHTML_LE (zencoding like selector input (light edition)|jowenn(you_know)kde(here_too)org|Joseph Wenninger}}
{{FeatureTodo|katepart|replace smart cursor/ranges API|cullmann@kde.org|Christoph Cullmann}}
{{FeatureTodo|kdeui|API to integrate KStatusNotifierItem and KNotification: both as class api and DBus specification API|davide.bettio@kdemail.net|Davide Bettio}}
{{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}}
{{FeatureTodo|kdecore|Group policy (Windows) backend for KAuth|drf@kde.org|Dario Freddi}}
{{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}}
{{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|kdeui|DBus interface in StatusNotifierItem to connect it with freedesktop notifications instances|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|khtml|Improvements in kwallet integration|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureInProgress|khtml|Basic audio/video tag support|germain@ebooksfrance.org|Michael Howell and Germain Garand}}
{{FeatureInProgress|khtml|DOM3 XPath/XPath1 support|maksim@kde.org|Maks Orlovich}}
{{FeatureTodo|khtml|Selectors API1|maksim@kde.org|Maks Orlovich}}
{{FeatureTodo|khtml and kparts|More general KPart scripting interfaces|maksim@kde.org|Maks Orlovich}}
{{FeatureTodo|khtml|Implement more of DOM3's CSSOM View module|germain@ebooksfrance.org|Germain Garand}}
{{FeatureDone|KNewStuff|Improved Download Dialog, multiple previews, better integration of details, changelog is displayed|gladhornKDEorg|Frederik Gladhorn}}
{{FeatureInProgress|KNewStuff|Icon view mode|gladhornKDEorg|Reza Shah, Frederik Gladhorn}}
{{FeatureDone|KNewStuff|Upload dialog rewritten: It now supports updating of old uploads, previews, most data that can be entered on the website and allows direct login to the account|gladhornKDEorg|Frederik Gladhorn}}
{{FeatureTodo|KNewStuff|Support more than one payload|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureTodo|kdeui|Social About Dialog|teo@kde.org|Téo Mrnjavac}}
{{FeatureTodo|kdeui|Generic find bar widget|sasch.pe@gmx.de|Sascha Peilicke}}
{{FeatureTodo|kio|SSL client certificate support|ahartmetz@gmail.com|Andreas Hartmetz}}
{{FeatureTodo|kio|SSL root certificate list GUI + backend|ahartmetz@gmail.com|Andreas Hartmetz}}
{{FeatureDone|kio|Add "apply to all" checkbox in renamedialog and allow for automatic renaming|toddrme2178@gmail.com|Todd}}
{{FeatureInProgress|kio|Port renamedialog to KFileMetaDataWidget|toddrme2178@gmail.com|Todd}}
{{FeatureInProgress|kio|Don't select extension in renamedialog|toddrme2178@gmail.com|Todd}}
{{FeatureDone|kio|Better listing of applications in file "open with" context menu|toddrme2178@gmail.com|Todd}}
{{FeatureInProgress|kio|Context menu entry to open all files in their default applications|toddrme2178@gmail.com|Todd}}
{{FeatureTodo|kio|Add support for additional columns (e.g., smybolic link destination) in KDirModel/KFileItemDelegate|frank78ac@googlemail.com|Frank Reininghaus}}
{{FeatureDone|kfile|Scroll wheel support for breadcrumb bar|toddrme2178@gmail.com|Todd}}
{{FeatureInProgress|kfile|Show all sub-folders in breadcrumb bar|toddrme2178@gmail.com|Todd}}
{{FeatureInProgress|kfile|Middle-click on subfolder in the breadcrumb bar to open in a new tab|toddrme2178@gmail.com|Todd}}
{{FeatureTodo|kfile|Easier access to protocols in breadcrumb bar|toddrme2178@gmail.com|Todd}}
{{FeatureTodo|kfile|Show sub-sub-folders (and so on) in breadcrumb bar|toddrme2178@gmail.com|Todd}}
{{FeatureInProgress|kdecore|Generic shared-memory cache|mpyne@kde.org|Michael Pyne}}
{{FeatureInProgress|kdeui|Redesigned icon cache|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|kdeui|Support alpha channel in KColor classes|christoph@maxiom.de|Christoph Feck}}
{{FeatureDone|nepomuk|Redesigned Nepomuk::TagWidget which can now actually be used by applications|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|kio|Remember downloads via Nepomuk|trueg@kde.org|Sebastian Trueg}}
{{FeatureDone|solid|Broadcast mount/unmount messages across processes|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureTodo|solid|Add parent matching to predicate parsing|wilderkde@gmail.com|Jacopo De Simoi}}
{{FeatureInProgress|kdeui|Add the KRecursiveFilterProxyModel to kdeui/itemviews|steveire@gmail.com|Stephen Kelly}}
|}
<br>

= 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
{{FeatureInProgress|Video Thumbnailer|Add ffmpegthumbnailer for faster video thumbnailing|ascherfy@gmail.com|Andreas Scherf}}
{{FeatureTodo|JuK|Remove Qt/KDE3 support lib requirements -- will move to KDE 4.5 feature plan|mpyne@kde.org|Michael Pyne}}
{{FeatureTodo|JuK|Allow setting covers directly from URLs supported by KIO - drag/drop already allows this however -- will move to KDE 4.5 feature plan|mpyne.org|Michael Pyne}}

|}

<br>

= 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}}
{{FeatureDone|Kopete|Extended video controls|fschaefer.oss(at)googlemail.com|Frank Schaefer}}
{{FeatureTodo|Kopete|Akonadi History Plugin|roideuniverse@gmail.com|Kaushik Saurabh}}
{{FeatureTodo|Krdc|Connection status screen and reconnect|murraytony@gmail.com|Tony Murray}}
{{FeatureDone|Krdc|Much improved new connection screen: more info, sortable, interactive, and better use of space|murraytony@gmail.com|Tony Murray}}
{{FeatureInProgress|KGet|Use plasma notifications to show the progress|mat69@gmx.net|Matthias Fuchs}}
{{FeatureDone|KGet|Refaktor Torrent-Plugin to base on the newly created libktorrent from extragear|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureInProgress|KGet|Better error handling|l.appelhans@gmx.de|Lukas Appelhans}}
|}

<br>

= 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
{{FeatureTodo|KAlarm|Port to Akonadi|djarvie@kde.org|David Jarvie}}
{{FeatureInProgress|KMail|Port to Akonadi|kde-pim@kde.org|Thomas McGuire}}
{{FeatureInProgress|KOrganizer|Port to Akonadi|kde-pim@kde.org|Frank Osterfeld, Sebastian Sauer}}
{{FeatureInProgress|KJots|Port to Akonadi|kde-pim@kde.org|Stephen Kelly}}
|}

<br>

= 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
{{FeatureTodo|knowledgebase|port knowledgebase plasmoid to new engine|ewoerner@kde.org|Eckhart Wörner}}
{{FeatureTodo|knowledgebase|Add categories|ewoerner@kde.org|Eckhart Wörner}}
{{FeatureDone|Bookmarks widget|New|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Mandelbrot Wallpaper|Performance improvements|jacob.benoit.1@gmail.com|Benoit Jacob}}
{{FeatureDone|Mandelbrot Wallpaper|Rendering improvements (through dithering, extra iterations, and better/simpler formulas)|jacob.benoit.1@gmail.com|Benoit Jacob}}
{{FeatureDone|Mandelbrot Wallpaper|Allow to import/export parameters and to export to PNG images|jacob.benoit.1@gmail.com|Benoit Jacob}}
{{FeatureDone|Comic Applet|Add option to show "text", "icons" or both "text and icons" for tabs|mat69@gmx.net|Matthias Fuchs}}
{{FeatureDone|Comic Applet|Prefetch next and previous comic strip (thx to Miha Cancula)|mat69@gmx.net|Matthias Fuchs}}
{{FeatureDone|Character Runner|New|akreuzkamp@web.de|Anton Kreuzkamp}}
{{FeatureDone|KDE Observatory|Performance improvements, new data engine|sandroandrade@kde.org|Sandro Andrade}}
{{FeatureInProgress|Plasmaboard|Completly rework the current onscreen keyboard and add key layouts for tablets and mids|bjoern@ruberg-wegener.de|Björn Ruberg}}
|}

<br>

= 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}}
{{FeatureInProgress|Kate|Replace old snippet plugin through TNG plugin and enhance the usability of the new plugin|jowenn(you_know)kde(here_too)org|Joseph Wenninger}}
{{FeatureInProgress|Kate|Port the old XML completion plugin (xmltools)|tomastrnka@gmx.com|Tomáš Trnka}}
{{FeatureInProgress|Umbrello|Add a code importing wizzard|andi.fischer@NOSPAMhispeed.ch|Andi Fischer}}
|}

<br>

= 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|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|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|Ark|Add a "Preview with..." context menu item|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|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|KGpg|Make keyserver actions possible to use on multiple keyservers at once|kde@opensource.sf-tec.de|Rolf Eike Beer}}
{{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 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 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|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|Store bookmarks|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add view profiles, incl. editor/manager|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add KNewStuff support to the structures tool|alex.richardson@gmx.de|Alex Richardson}}
{{FeatureTodo|Okteta|Allow pinning structure beginning to a specific offset|alex.richardson@gmx.de|Alex Richardson}}
{{FeatureTodo|printer-applet|Restore feature parity with KDEPrint3 where possible.||Jonathon Riddell, John Layt}}
{{FeatureDone|kdelirc/kremotecontrol|Transition from KDELirc to KRemoteControl|michael_zanetti@gmx.net|Michael Zanetti}}
{{FeatureInProgress|KGpg|Add "caff" mode for keysigning|kde@opensource.sf-tec.de|Rolf Eike Beer}}
{{FeatureInProgress|Okteta|Allow writing structure definitions in JavaScript|alex.richardson@gmx.de|Alex Richardson}}
{{FeatureInProgress|Okteta|Add possibility to set count of bytes per line/group|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|new export formats: S-Record, Intel Hex, Base32, Ascii85, Uuencoding, Xxencoding|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|add QIODevice for AbstractByteArrayModel and make mimetype detection use this instead of only filename |kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|Refactor mouse input to controllers for the bytearray widget|kossebau@kde.org|Friedrich W. H. Kossebau}}
|}

<br>

= kdetoys =

{| 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|kteatime|Port to KStatusNotifierItem|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureInProgress|kteatime|Port to KConfigXT|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureInProgress|kteatime|Support categories|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureInProgress|kteatime|Improved indicator icon painting|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|kteatime|Fork multiple instances for multiple timers|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|kteatime|Tea runner|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|kteatime|Improved command line|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|amor|Do some refactoring in amor|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|amor|Improve theme support|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|amor|Implement KNewStuff support|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|amor|Revamp configure dialog|kde@hilefoks.org|Stefan Böhmann}} {{FeatureTodo|amor|Sound support|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|amor|Add KStatusNotifierItem support|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureInProgress|ktux|Do some refactoring in ktux|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|ktux|Revamp configure dialog|kde@hilefoks.org|Stefan Böhmann}} {{FeatureTodo|ktux|Sound support|kde@hilefoks.org|Stefan Böhmann}}
|}

<br>

= 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

|}

Projects/MovetoGit

2010-04-06T16:33:42Z

Steveire: /* Requirements of KDEPIM and KDAB */ Update progress bar.

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 [http://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 want to be in this group, file a bugreport for sysadmin on bugs.kde.org. :)

The procedure to move a project from svn to gitorious.org can be found in [[Projects/MoveToGit/StepsToMove|Steps to follow for Moving]].

=Blockers=

Tasks that need to get done before we can migrate

==SLA for gitorious.org==
{{Progress bar|30}}
'''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.

: aseigo and Frank (and someone?) had a meeting with Shortcut people during tokamak. They asked for a rather large sum of money; negotiations are continuing, but we might want to consider hosting our own server...

==Write / update importing rules for svn2git==
{{Progress bar|5}}
'''Owner:''' see below - 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 [[Projects/MoveToGit/UsingSvn2Git|Using 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
|tnyblom
|25
|Basic rules in place, testing and tweaking pending.
|-
|SC/kdepim-runtime
|tnyblom
|25
|Basic rules in place, testing and tweaking pending.
|-
|SC/kdepimlibs
|tnyblom
|90
|Some minor history glitches, but mostly done.
|-
|SC/kdeplasma-addons
|
|0
|
|-
|SC/kdesdk
|
|0
|
|-
|SC/kdetoys
|
|0
|
|-
|SC/kdeutils
|
|0
|
|-
|SC/kdewebdev
|
|0
|
|-
|extragear/sdk/kdevelop
| apaku
| 95
| trunk and branches complete, need to cleanup tags from cvs days.
|-
|extragear/sdk/kdevplatform
| apaku
| 100
| done, all tags seem fine all branches are there
|-
|extragear/sdk/kdevelop-plugins
| nsams
| 100
| done
|-
|extragear/sdk/quanta
| nsams
| 99
| done
|-
|extragear/*/*
|
|xx
|expand the *'s later (let's focus on the base modules first)
|-
|kde-common
|mattr
|75
|analyzing import history
|-
|kdesupport
|
|0
|
|-
|koffice
|tzander
|85
|All but tags are done
|-
|promo
|
|0
|
|-
|quality
|
|0
|
|-
|tests
|
|0
|
|}

== Requirements of KDEPIM and KDAB ==

{{Progress bar|70}}
'''Owner:''' Stephen Kelly

'''Status:''' ''Proposed workflow identified. Partially depends on KDE policies regarding branches and merging. Gathering estimates for porting of tooling from svn to git. People unfamiliar with the tool are starting to learn to use it.''

'''Estimated completion date''': End of May.

'''Summary of issues'''

* Clean slate
** The existing backlog of commits which need to be merged or ported to trunk needs to be empty before the change to git so that nothing gets lost. This is a lot of work and will take time. ''Estimate'' 10 calendar weeks.
* Internal Tools and external customer tools and workflows
** KDAB is a consumer of KDE software, but also has downstream customers fetching software from where it is developed. That is, KDE SVN. For example packages are created from the tags in tags/kdepim. Some of these downstreams are less close to KDE and depend on current workflows. If KDE SVN is not the place to get those updates anymore, this needs to be communicated to those downstreams, and the tools updated. ''Estimate'' 1 week to port the tools.
** People who don't currently know how to use git need to get familiar with it so that transitioning will be nearly seamless, and not result in too much development slowdown.
* Other commitments
** Project deadlines and other commitments prevent the possibility of blocking off time to work on git migration when so many other things need to be done which have milestones separate to KDE cycles. The required work to convert to git can't be prioritized as highly, and so will take more time.
* Technical difficulties and limitations.
** Up to KDE 3.5 there was one kdepim module. For the KDE4 cycle, this was split into kdepimlibs and kdepim. For the above mentioned merging to be possible, it makes sense for both to be in the same git module. This poses extra difficulty to the svn2git script.

'''Email threads'''

* Mid-January thread on scm-interest: http://thread.gmane.org/gmane.comp.kde.devel.pim/26726
* Early March thread on kde-core-devel (Till email): http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=63970
* Early March thread on kde-core-devel (Till follow-up):
http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=64069

'''Resolved Issues'''

* Branch maintenance workflow '''Resolution: http://thread.gmane.org/gmane.comp.kde.scm-interest/1310'''
** KDAB maintains several branches of legacy versions of KDE for enterprise customer deployments. [http://websvn.kde.org:80/branches/kdepim/enterprise/ Enterprise 3.5] [http://websvn.kde.org:80/branches/kdepim/enterprise4/ Enterprise 4 (based on KDE 4.2)]. The current KDEPIM trunk known as Enterprise 5 and is Akonadi based.
** Periodically (weekly or so), tags are created from the enterprise branches with bugfixes. http://websvn.kde.org:80/tags/kdepim/ Customers can download the tagged versions with the latest updates. Fixes are merged from the Enterprise 3.5 branch, and into trunk (which sometimes involves a lot of work, as the fix must be ported to Akonadi). Additionally, fixes get merged in the other direction. From official KDE modules into the Enterprise branches.
** Some fixes from Enterprise 3.5 should not be merged into Enterprise 4 for reasons such as no longer being reproducible. Some fixes do not get merged for a long time because they require so much work that porting the fix or feature is deffered. There needs to be a list of commits which should never be merged (blocked commits), and commits which should be merged, but have not been merged yet. The tool [[Development/Tools/svnmerge.py|svnmerge]] is used to facilitate this. svnmerge uses svn properties to maintain lists of commits that are blocked and that have already been integrated. See for example the svn-blocked and svn-integrated properties here: http://websvn.kde.org:80/trunk/KDE/kdepim/. The lists of commits available to be merged into the various branches are here: http://www.kdab.com/~thomas/avail/
** There needs to be a way in git to keep track of what commits have been merged, what commits need to be merged, and what commits are blocked. There needs to be a way of merging only specific commits from a branch, but not all, and not blocked commits. Proposed solutions:
*** git cherry-pick allows 'merging' of individual commits, but does not record where the commits came from. Instead it creates a new commit without any reference to where it came from. This alone is unsuitable.
*** branch per fix. This would lead to an explosion of branches which is not a problem in git as all commits are branches. It may make gitk un-navigatable. There would need to be a naming convention such as komo-merge-<fixname> for branches which should be merged. The commands <tt>git checkout 4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout enterprise4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout master && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt>. That could of course be optimized, but gets the point across. If the code has changed so much that the branch is unmergable, but the fix still needs to be in trunk, the system breaks down.
*** Custom git command with flat text files representing the same information as svnmerge, that is lists of blocked and integrated commits. This is most likely to be a workable solution, possibly together with conventional branch naming.

=Nice to have before the migration=

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

'''Status:''' argonel had a 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.

-----------

This does not require help from gitorious.org until the script is actually written: it's just another pre-receive hook for them to install on their servers.
it *might* also be possible to run it as a post-receive hook (in which case we can do the whole thing ourselves).

if we self-host, then we won't need this.

==Script for downloading virtual KDE hierarchies==
{{Progress bar|0}}
'''Owner''':

'''Status:'''

:Let's start over on this.
what we already have: two build scripts for kde; kdesvn-build and build-tool.
what we want: an easy way for people to get large chunks of kde, without thinking about what urls the repos come from or having to look things up.

do kde-svnbuild and build-tool satisfy this well enough?
or do we want a computer-readable file listing all the repos too?

btw, scripty has its own list of repos already. it's just in a rather weird bash file.

'''Links'''
[http://kdesvn-build.kde.org/]
[[Projects/MovetoGit/MassCloneScript]]
[http://rubyforge.org/projects/build-tool/]

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

==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'''

: I think most people have made their own accounts by now. this isn't really needed.

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

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

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

:not possible with git, broken by design.

::

'''Discussion'''

Exists, but ignorable:
* kdesupport shared-desktop-ontologies (temporary)
* 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
* 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

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

==kde-common/accounts==

Someone said: KDE accounts file is no longer necessary---used for mapping svn ID -> email, but we have that now from Gitorious.
Answer from David Faure: I strongly disagree. We still need a KDE accounts file. This is very useful for finding people's email addresses, and having an overview on the number of active kde contributors; and if we keep it we can even have a kdepim resource again for filling an addressbook from it, for completion in kmail's composer (so you can write to any other kde contributor by just typing his/her name). It's also used for populating automatically the kde-cvs-announce mailing-list, for announcements. kde-common/accounts is our family tree (well, list), let's not get rid of it.

Here's my proposal for a kde-common/accounts replacement for the git era: We write a post-receive hook that looks at every commit and records all known email addresses for a given real name as well as the commit hash and date of when an address was last encountered. We can then present that data in the form of a file like kde-common/accounts, or write a web interface to query it (with nice links to the commits on Gitorious, etc.) --Eike (Sho_ on IRC)

To clear up possible confusion: The author information for a given commit is baked into the commit object itself, and comes from the configuration of the git repository it was created in. It is unrelated to any Gitorious account. Due to the distributed nature of Git, the one who uses his Gitorious account to push a commit need not be the same who created it. If Developer A creates a commit in his local clone and Developer B fetches it into his local clone directly from Developer A's machine and then pushes it into the public repo, the repo will only show a commit from Developer A. The Gitorious website will show that Developer B has pushed up a commit from Developer A, but that data is not contained in the repository. Thus collecting only Gitorious accounts and their mail addresses is insufficient. --Eike

==Random==
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/MoveToGit/UsingSvn2Git

2010-03-12T16:20:51Z

Steveire: /* Getting the tools */

This page documents how to go about getting a KDE module ready for the Great Git Migration of 2010.

=== Getting the tools ===

The necessary tools are hosted at [http://www.gitorious.org/svn2git http://www.gitorious.org/svn2git]. To get started do:

<code bash>
git clone git://gitorious.org/svn2git/svn2git.git
git clone git://gitorious.org/svn2git/kde-ruleset.git
</code>

And then install the libsvn-dev package.

This will get you the source code to build svn2git and the KDE ruleset files as they currently exist. Build the svn2git tool before moving on to the next step.

==== Building svn2git ====
Make sure you have Qt4 installed, then simply issue
<nowiki>qmake && make</nowiki> to build the executable called "svn-all-fast-export"

=== How rulesets work ===
The format for the svn2git rules is pretty simple. First and foremost you
have to declare some repositories:

<pre>
create repository kdelibs
end repository
</pre>

This tells svn2git that it should create a git repository called "kdelibs" that we can later on use to put commits into it.

The rest of the file are rules matching specific paths in Subversion, each rule
specifies what to do with the commits that appeared at the given path. The
possible actions are ignoring them or adding them to a particular branch in a particular repository. '''Note:''' Ignoring is done by simply leaving out the information about the repository and the branch.

As examples are more explanatory, the following rule would put all commits from 123453 to 456789 from the path /trunk/KDE/kdelibs into the master branch of
the kdelibs repository:
<pre>
match /trunk/KDE/kdelibs/
min revision 123453
max revision 456789
repository kdelibs
branch master
end match
</pre>

The min and max revision are useful in cases where the same path in SVN contains
code for different branches. An example would be KDevelop3, where KDevelop 3.3 was shipped with KDE 3.5 until 3.5.7, 3.5.8 contained KDevelop 3.4 and 3.5.9 contained KDevelop 3.5 and all of those kdevelop versions are now under /branches/KDE/3.5/kdevelop.

The two revision parameters are however not mandatory, if they're left out, then all commits that went to the given matching path in SVN are taken over into the specified branch.

To generate tags with git you use a special format for the branch parameter: refs/tag/<tagname>. So to put all commits from /tags/KDE/4.4.0/kdelibs into the v4.4.0 tag in the kdelibs git repository the rule would be like this:

<pre>
match /tags/KDE/4.4.0/kdelibs/
repository kdelibs
branch refs/tags/v4.4.0
end match
</pre>

For more examples see the svn2git/samples/ directory and the rules in the kde-ruleset repository.

The recurse action is a hack to tell svn2git to recurse into a directory it
has just copied or that existed because it is of interest. Example: if we are importing kdelibs, it exists in {{path|trunk/KDE/kdelibs}}. At branching, someone did: <code bash>svn cp $SVNROOT/trunk/KDE $SVNROOT/branches/KDE/4.4</code>

SVN recorded in that commit that branches/KDE/4.4 was the only path changed.
That means the rule <pre>branches/KDE/[^/]+/kdelibs/</pre> will not match.

We need to tell the tool that something interesting happened inside and it
should recurse. Then it will apply again all rules to the files that exist at
that point, at which point the rules will match.

==== Important Details ====

* All matching rules need to end with a '/', else the tool will crash at some point. This is a known bug. The only exception are the rules using the recurse-action.

* Matching rules can use Regular Expressions (according to the QRegExp syntax) in the match line and can use backreferences in the repository and branch parameters using \n (n=1,2,3,...) to reduce the amount of rules.

* The rules form an ordered list that the tool goes through while matching the changed paths for each commit. So if two rules match the same path and neither of the two has more matching criteria, then the rule that is written further up in the file wins. This is useful to exclude certain commits from the extraction process, if you look at the existing kde ruleset you'll notice that at the top some revisions are ignored.

=== Setting up your system ===

You will need ~60GB (is that correct?) of disk space to get started, as the process requires a copy of the KDE svn database. There is a script that will download this for you (and which can be used to update it periodically using rsync) in kde-ruleset/bin/startSync. By default the startSync script runs rsync in "dry run" mode, so before using it to actually get the svn database edit the startSync script and remove the -n from both rsync lines.

more stuff goes here ...

=== Step-by-Step on writing rules for a module ===

==== Analyzing Subversion history to write rules ====
First of all you should check wether there are already rules for this module in the kde-ruleset repository. If there are rules already please go down to "Running svn2git"

If there are no rules yet, lets start with the master (aka trunk) branch. The easiest way to find out history with svn is executing:
<pre>svn log -v --stop-on-copy file:///path/to/kde_svn/trunk/KDE/module</pre>

This will give you a history of the given module in trunk, it'll stop on the first commit that copied the code from somewhere else. The verbose output will allow you to see where this copy came from.

Now we have a starting point to write a rule, we want all commits from this path in our module repository in the master branch:
<pre>
match /trunk/KDE/module/
repository module
branch master
end match
</pre>
If the log stops at a commit that copied the module from somewhere, we need to
follow this to also get the history imported from the "old" place the module resided. The same svn command can be used with slightly different path argument:

<pre>svn log -v --stop-on-copy file:///path/to/kde_svn/some/other/path@revision</pre>
The @revision is important as the original path usually doesn't exist anymore. With this we can write the next rule to the rules file and repeat until we've finally reached the point where the code was initially imported into svn (or probably cvs in the old days)

Now we can take care of the branches, this is a bit more involved as there may be multiple branches scattered over the /branches directory in svn. You can use the same commands as before to find out the history of a branch if you know the path. This time however you can stop following the source of copy-operations once you've found a source that you've already matched in a rule. That way your branch will be connected to the branch it originated from (which is often trunk aka master) in git.

A useful help with finding branches is svn ls in combination with the path@revision syntax, that way you can view the content of a particular svn directory as it was in an older revision. With this you can even find branches that are not visible (have been deleted) in the current revision.

The rule for putting commits into a git branch in the final repository is only slightly different (the example is for a core module):
<pre>
match /branches/KDE/4.4/module
repository module
branch 4.4
end match
</pre>

And last are the tags, this works the same as branches and trunk, except for using branch refs/tags/v<tag-version> for the branch parameter.

==== Running svn2git ====
This is the easiest, but most time-consuming part. As example lets say that in our current working directory we have the kde rules repository in kde-ruleset subdir, the svn2git tool in the svn2git subdir and the KDE repository in the kde_svn subdir:
<pre>
svn2git/svn-all-fast-export --identity-map kde-ruleset/account-map --rules kde-ruleset/module kde_svn
</pre>

This will take a few hours usually, but it'll spit out the progress. The tool also writes a logfile to module.log, so in case something goes wrong you can find more details in there.

Once its done you should have a new "module" git repository in your current working directory.

==== Checking for proper history in the new git repository ====
A very easy way to check wether the history was imported properly is to use the gitk tool from git. It shows you a graphical representation of the history in the git repository which makes it easy to identify where something is wrong.

The tool should be run with the --all switch so it shows all branches.

You can now scroll through the history to check wether things have been imported correctly.

First and foremost there should be the master branch starting at the top with the most recent commit to trunk/ and ending in the oldest commit that imported the code into KDE's svn or cvs repository.

From the master branch there should be several branches going away for each branch you imported. And eventually also branches that start from another non-master branch.

Things that you should look out for are branches that start "nowhere", that is the first commit in the branch has no parent in another branch or master. This means that svn2git didn't see a commit that created this branch from another using a svn cp command. That can mean that you may have forgotton to add a match rule for some path or that the same path was used for different branches in different revisions. The same applies to tags which have a commit without any parent.

This can usually be fixed by using svn log and svn ls to follow the history of the branch. Eventually you might need to apply the min/max revision paramters.

You'll notice that some tags are looking like this:

<pre>
|
* * <v1.2.3>
| |
* *
| /
*
</pre>

Thats normal for our tags even if a bit ugly. The reason is that often compile-fixes are done in trunk/ after the tag has been created and then the commit has been merged over to the tag.

Another thing however are tags that are named vx.y.z_124321. These are tags that have been deleted and re-created later. You can usually see that in the svn log history, these tags can either be manually deleted after the repository creation using git tag or you can add rules that ignore certain revisions of the tag-path before the one putting the commits into the git repository:

<pre>
match /tags/KDE/3.3.2/kdelibs
min revision 424234
max revision 424236
end match
match /tags/KDE/3.3.2/kdelibs
repository kdelibs
branch refs/tags/3.3.2
end match
</pre>

If you choose to delete them manually please make sure to document this with a textfile or inside the rule file so if someone else does the conversion later again he'll know what manual steps you did.

Before publishing the newly created git repository make sure to repack it. This can greatly reduce it's size (i.e. Phonon's git repository could be shrunken from 18 MB to 5.2 MB)

==== Getting Help ====
If you run into strange things or can't find a rule for something you can reach the KDE Git migration team on IRC: irc.freenode.org, #kde-git or on the [https://mail.kde.org/mailman/listinfo/kde-scm-interest kde-scm-interest mailinglist]

Projects/MovetoGit

2010-03-12T16:03:06Z

Steveire: /* Requirements of KDEPIM and KDAB */

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 [http://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 want to be in this group, file a bugreport for sysadmin on bugs.kde.org. :)

The procedure to move a project from svn to gitorious.org can be found in [[Projects/MoveToGit/StepsToMove|Steps to follow for Moving]].

=Blockers=

Tasks that need to get done before we can migrate

==SLA for gitorious.org==
{{Progress bar|30}}
'''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.

: aseigo and Frank (and someone?) had a meeting with Shortcut people during tokamak. They asked for a rather large sum of money; negotiations are continuing, but we might want to consider hosting our own server...

==Write / update importing rules for svn2git==
{{Progress bar|0}}
'''Owner:''' see below - 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 [[Projects/MoveToGit/UsingSvn2Git|Using 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
|tnyblom
|0
|Just getting started Help needed.
|-
|SC/kdepimlibs
|tnyblom
|0
|Just getting started Help needed.
|-
|SC/kdeplasma-addons
|
|0
|
|-
|SC/kdesdk
|mattr
|0
|just starting
|-
|SC/kdetoys
|mattr
|0
|just starting
|-
|SC/kdeutils
|
|0
|
|-
|SC/kdewebdev
|
|0
|
|-
|extragear/sdk/kdevelop
| apaku
| 85
| Misses history from KDE3.3 and older (KDevelop3.2), probably something with layout-changes, might need recurse-action but don't know how to do it.
|-
|extragear/sdk/kdevplatform
| apaku
| 100
| done, all tags seem fine all branches are there
|-
|extragear/*/*
|
|xx
|expand the *'s later (let's focus on the base modules first)
|-
|kde-common
|mattr
|0
|just starting
|-
|kdesupport
|
|0
|
|-
|koffice
|tzander
|85
|All but tags are done
|-
|promo
|
|0
|
|-
|quality
|
|0
|
|-
|tests
|
|0
|
|}

== Requirements of KDEPIM and KDAB ==

{{Progress bar|30}}
'''Owner:''' Stephen Kelly

'''Status:''' ''Proposed workflow identified. Partially depends on KDE policies regarding branches and merging. Gathering estimates for porting of tooling from svn to git. People unfamiliar with the tool are starting to learn to use it.''

'''Estimated completion date''': End of May.

'''Summary of issues'''

* Clean slate
** The existing backlog of commits which need to be merged or ported to trunk needs to be empty before the change to git so that nothing gets lost. This is a lot of work and will take time. ''Estimate'' 10 calendar weeks.
* Internal Tools and external customer tools and workflows
** KDAB is a consumer of KDE software, but also has downstream customers fetching software from where it is developed. That is, KDE SVN. For example packages are created from the tags in tags/kdepim. Some of these downstreams are less close to KDE and depend on current workflows. If KDE SVN is not the place to get those updates anymore, this needs to be communicated to those downstreams, and the tools updated. ''Estimate'' 1 week to port the tools.
** People who don't currently know how to use git need to get familiar with it so that transitioning will be nearly seamless, and not result in too much development slowdown.
* Other commitments
** Project deadlines and other commitments prevent the possibility of blocking off time to work on git migration when so many other things need to be done which have milestones separate to KDE cycles. The required work to convert to git can't be prioritized as highly, and so will take more time.
* Technical difficulties and limitations.
** Up to KDE 3.5 there was one kdepim module. For the KDE4 cycle, this was split into kdepimlibs and kdepim. For the above mentioned merging to be possible, it makes sense for both to be in the same git module. This poses extra difficulty to the svn2git script.

'''Email threads'''

* Mid-January thread on scm-interest: http://thread.gmane.org/gmane.comp.kde.devel.pim/26726
* Early March thread on kde-core-devel (Till email): http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=63970
* Early March thread on kde-core-devel (Till follow-up):
http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=64069

'''Resolved Issues'''

* Branch maintenance workflow '''Resolution: http://thread.gmane.org/gmane.comp.kde.scm-interest/1310'''
** KDAB maintains several branches of legacy versions of KDE for enterprise customer deployments. [http://websvn.kde.org:80/branches/kdepim/enterprise/ Enterprise 3.5] [http://websvn.kde.org:80/branches/kdepim/enterprise4/ Enterprise 4 (based on KDE 4.2)]. The current KDEPIM trunk known as Enterprise 5 and is Akonadi based.
** Periodically (weekly or so), tags are created from the enterprise branches with bugfixes. http://websvn.kde.org:80/tags/kdepim/ Customers can download the tagged versions with the latest updates. Fixes are merged from the Enterprise 3.5 branch, and into trunk (which sometimes involves a lot of work, as the fix must be ported to Akonadi). Additionally, fixes get merged in the other direction. From official KDE modules into the Enterprise branches.
** Some fixes from Enterprise 3.5 should not be merged into Enterprise 4 for reasons such as no longer being reproducible. Some fixes do not get merged for a long time because they require so much work that porting the fix or feature is deffered. There needs to be a list of commits which should never be merged (blocked commits), and commits which should be merged, but have not been merged yet. The tool [[Development/Tools/svnmerge.py|svnmerge]] is used to facilitate this. svnmerge uses svn properties to maintain lists of commits that are blocked and that have already been integrated. See for example the svn-blocked and svn-integrated properties here: http://websvn.kde.org:80/trunk/KDE/kdepim/. The lists of commits available to be merged into the various branches are here: http://www.kdab.com/~thomas/avail/
** There needs to be a way in git to keep track of what commits have been merged, what commits need to be merged, and what commits are blocked. There needs to be a way of merging only specific commits from a branch, but not all, and not blocked commits. Proposed solutions:
*** git cherry-pick allows 'merging' of individual commits, but does not record where the commits came from. Instead it creates a new commit without any reference to where it came from. This alone is unsuitable.
*** branch per fix. This would lead to an explosion of branches which is not a problem in git as all commits are branches. It may make gitk un-navigatable. There would need to be a naming convention such as komo-merge-<fixname> for branches which should be merged. The commands <tt>git checkout 4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout enterprise4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout master && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt>. That could of course be optimized, but gets the point across. If the code has changed so much that the branch is unmergable, but the fix still needs to be in trunk, the system breaks down.
*** Custom git command with flat text files representing the same information as svnmerge, that is lists of blocked and integrated commits. This is most likely to be a workable solution, possibly together with conventional branch naming.

=Nice to have before the migration=

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

'''Status:''' argonel had a 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.

-----------

This does not require help from gitorious.org until the script is actually written: it's just another pre-receive hook for them to install on their servers.
it *might* also be possible to run it as a post-receive hook (in which case we can do the whole thing ourselves).

if we self-host, then we won't need this.

==Script for downloading virtual KDE hierarchies==
{{Progress bar|0}}
'''Owner''':

'''Status:'''

:Let's start over on this.
what we already have: two build scripts for kde; kdesvn-build and build-tool.
what we want: an easy way for people to get large chunks of kde, without thinking about what urls the repos come from or having to look things up.

do kde-svnbuild and build-tool satisfy this well enough?
or do we want a computer-readable file listing all the repos too?

btw, scripty has its own list of repos already. it's just in a rather weird bash file.

'''Links'''
[http://kdesvn-build.kde.org/]
[[Projects/MovetoGit/MassCloneScript]]
[http://rubyforge.org/projects/build-tool/]

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

==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'''

: I think most people have made their own accounts by now. this isn't really needed.

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

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

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

:not possible with git, broken by design.

::

'''Discussion'''

Exists, but ignorable:
* kdesupport shared-desktop-ontologies (temporary)
* 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
* 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

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

==kde-common/accounts==

Someone said: KDE accounts file is no longer necessary---used for mapping svn ID -> email, but we have that now from Gitorious.
Answer from David Faure: I strongly disagree. We still need a KDE accounts file. This is very useful for finding people's email addresses, and having an overview on the number of active kde contributors; and if we keep it we can even have a kdepim resource again for filling an addressbook from it, for completion in kmail's composer (so you can write to any other kde contributor by just typing his/her name). It's also used for populating automatically the kde-cvs-announce mailing-list, for announcements. kde-common/accounts is our family tree (well, list), let's not get rid of it.

Here's my proposal for a kde-common/accounts replacement for the git era: We write a post-receive hook that looks at every commit and records all known email addresses for a given real name as well as the commit hash and date of when an address was last encountered. We can then present that data in the form of a file like kde-common/accounts, or write a web interface to query it (with nice links to the commits on Gitorious, etc.) --Eike (Sho_ on IRC)

To clear up possible confusion: The author information for a given commit is baked into the commit object itself, and comes from the configuration of the git repository it was created in. It is unrelated to any Gitorious account. Due to the distributed nature of Git, the one who uses his Gitorious account to push a commit need not be the same who created it. If Developer A creates a commit in his local clone and Developer B fetches it into his local clone directly from Developer A's machine and then pushes it into the public repo, the repo will only show a commit from Developer A. The Gitorious website will show that Developer B has pushed up a commit from Developer A, but that data is not contained in the repository. Thus collecting only Gitorious accounts and their mail addresses is insufficient. --Eike

==Random==
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/MovetoGit

2010-03-08T12:15:34Z

Steveire: Restore accidental deletion of most content.

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 [http://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 want to be in this group, file a bugreport for sysadmin on bugs.kde.org. :)

The procedure to move a project from svn to gitorious.org can be found in [[Projects/MoveToGit/StepsToMove|Steps to follow for Moving]].

=Blockers=

Tasks that need to get done before we can migrate

==SLA for gitorious.org==
{{Progress bar|30}}
'''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.

: aseigo and Frank (and someone?) had a meeting with Shortcut people during tokamak. They asked for a rather large sum of money; negotiations are continuing, but we might want to consider hosting our own server...

==Write / update importing rules for svn2git==
{{Progress bar|0}}
'''Owner:''' see below - 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 [[Projects/MoveToGit/UsingSvn2Git|Using 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
|tnyblom
|0
|Just getting started Help needed.
|-
|SC/kdepimlibs
|tnyblom
|0
|Just getting started Help needed.
|-
|SC/kdeplasma-addons
|
|0
|
|-
|SC/kdesdk
|mattr
|0
|just starting
|-
|SC/kdetoys
|mattr
|0
|just starting
|-
|SC/kdeutils
|
|0
|
|-
|SC/kdewebdev
|
|0
|
|-
|extragear/sdk/kdevelop
| apaku
| 85
| Misses history from KDE3.3 and older (KDevelop3.2), probably something with layout-changes, might need recurse-action but don't know how to do it.
|-
|extragear/sdk/kdevplatform
| apaku
| 100
| done, all tags seem fine all branches are there
|-
|extragear/*/*
|
|xx
|expand the *'s later (let's focus on the base modules first)
|-
|kde-common
|mattr
|0
|just starting
|-
|kdesupport
|
|0
|
|-
|koffice
|tzander
|100
|
|-
|promo
|
|0
|
|-
|quality
|
|0
|
|-
|tests
|
|0
|
|}

== Requirements of KDEPIM and KDAB ==

{{Progress bar|10}}
'''Owner:''' till (To be reassigned)

'''Status:''' ''Requirements of tools and for workflow identified. Someone from KDAB will be nominated to co-ordinate and communicate specific requirements''

'''Summary of issues'''

* Branch maintenance workflow
** KDAB maintains several branches of legacy versions of KDE for enterprise customer deployments. [http://websvn.kde.org:80/branches/kdepim/enterprise/ Enterprise 3.5] [http://websvn.kde.org:80/branches/kdepim/enterprise4/ Enterprise 4 (based on KDE 4.2)]. The current KDEPIM trunk known as Enterprise 5 and is Akonadi based.
** Periodically (weekly or so), tags are created from the enterprise branches with bugfixes. http://websvn.kde.org:80/tags/kdepim/ Customers can download the tagged versions with the latest updates. Fixes are merged from the Enterprise 3.5 branch, and into trunk (which sometimes involves a lot of work, as the fix must be ported to Akonadi). Additionally, fixes get merged in the other direction. From official KDE modules into the Enterprise branches.
** Some fixes from Enterprise 3.5 should not be merged into Enterprise 4 for reasons such as no longer being reproducible. Some fixes do not get merged for a long time because they require so much work that porting the fix or feature is deffered. There needs to be a list of commits which should never be merged (blocked commits), and commits which should be merged, but have not been merged yet. The tool [[Development/Tools/svnmerge.py|svnmerge]] is used to facilitate this. svnmerge uses svn properties to maintain lists of commits that are blocked and that have already been integrated. See for example the svn-blocked and svn-integrated properties here: http://websvn.kde.org:80/trunk/KDE/kdepim/. The lists of commits available to be merged into the various branches are here: http://www.kdab.com/~thomas/avail/
** There needs to be a way in git to keep track of what commits have been merged, what commits need to be merged, and what commits are blocked. There needs to be a way of merging only specific commits from a branch, but not all, and not blocked commits. Proposed solutions:
*** git cherry-pick allows 'merging' of individual commits, but does not record where the commits came from. Instead it creates a new commit without any reference to where it came from. This alone is unsuitable.
*** branch per fix. This would lead to an explosion of branches which is not a problem in git as all commits are branches. It may make gitk un-navigatable. There would need to be a naming convention such as komo-merge-<fixname> for branches which should be merged. The commands <tt>git checkout 4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout enterprise4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout master && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt>. That could of course be optimized, but gets the point across. If the code has changed so much that the branch is unmergable, but the fix still needs to be in trunk, the system breaks down.
*** Custom git command with flat text files representing the same information as svnmerge, that is lists of blocked and integrated commits. This is most likely to be a workable solution, possibly together with conventional branch naming.
* Clean slate
** The existing backlog of commits which need to be merged or ported to trunk needs to be empty before the change to git so that nothing gets lost. This is a lot of work and will take time.
* Internal Tools and external customer tools and workflows
** KDAB is a consumer of KDE software, but also has downstream customers fetching software from where it is developed. That is, KDE SVN. For example packages are created from the tags in tags/kdepim. Some of these downstreams are less close to KDE and depend on current workflows. If KDE SVN is not the place to get those updates anymore, this needs to be communicated to those downstreams, and the tools updated.
** People who don't currently know how to use git need to get familiar with it so that transitioning will be nearly seamless, and not result in too much development slowdown.
* Other commitments
** Project deadlines and other commitments prevent the possiblity of blocking off time to work on git migration when so many other things need to be done which have milestones separate to KDE cycles. The required work to convert to git can't be prioritized as highly, and so will take more time.
* Technical difficulties and limitations.
** Up to KDE 3.5 there was one kdepim module. For the KDE4 cycle, this was split into kdepimlibs and kdepim. For the above mentioned merging to be possible, it makes sense for both to be in the same git module. This poses extra difficulty to the svn2git script.

'''Email threads'''

* Mid-January thread on scm-interest: http://thread.gmane.org/gmane.comp.kde.devel.pim/26726
* Early March thread on kde-core-devel (Till email): http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=63970
* Early March thread on kde-core-devel (Till follow-up):
http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=64069

=Nice to have before the migration=

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

'''Status:''' argonel had a 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.

-----------

This does not require help from gitorious.org until the script is actually written: it's just another pre-receive hook for them to install on their servers.
it *might* also be possible to run it as a post-receive hook (in which case we can do the whole thing ourselves).

if we self-host, then we won't need this.

==Script for downloading virtual KDE hierarchies==
{{Progress bar|0}}
'''Owner''':

'''Status:'''

:Let's start over on this.
what we already have: two build scripts for kde; kdesvn-build and build-tool.
what we want: an easy way for people to get large chunks of kde, without thinking about what urls the repos come from or having to look things up.

do kde-svnbuild and build-tool satisfy this well enough?
or do we want a computer-readable file listing all the repos too?

btw, scripty has its own list of repos already. it's just in a rather weird bash file.

'''Links'''
[http://kdesvn-build.kde.org/]
[[Projects/MovetoGit/MassCloneScript]]
[http://rubyforge.org/projects/build-tool/]

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

==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'''

: I think most people have made their own accounts by now. this isn't really needed.

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

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

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

:not possible with git, broken by design.

::

'''Discussion'''

Exists, but ignorable:
* kdesupport shared-desktop-ontologies (temporary)
* 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
* 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

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

==kde-common/accounts==

Someone said: KDE accounts file is no longer necessary---used for mapping svn ID -> email, but we have that now from Gitorious.
Answer from David Faure: I strongly disagree. We still need a KDE accounts file. This is very useful for finding people's email addresses, and having an overview on the number of active kde contributors; and if we keep it we can even have a kdepim resource again for filling an addressbook from it, for completion in kmail's composer (so you can write to any other kde contributor by just typing his/her name). It's also used for populating automatically the kde-cvs-announce mailing-list, for announcements. kde-common/accounts is our family tree (well, list), let's not get rid of it.

Here's my proposal for a kde-common/accounts replacement for the git era: We write a post-receive hook that looks at every commit and records all known email addresses for a given real name as well as the commit hash and date of when an address was last encountered. We can then present that data in the form of a file like kde-common/accounts, or write a web interface to query it (with nice links to the commits on Gitorious, etc.) --Eike (Sho_ on IRC)

To clear up possible confusion: The author information for a given commit is baked into the commit object itself, and comes from the configuration of the git repository it was created in. It is unrelated to any Gitorious account. Due to the distributed nature of Git, the one who uses his Gitorious account to push a commit need not be the same who created it. If Developer A creates a commit in his local clone and Developer B fetches it into his local clone directly from Developer A's machine and then pushes it into the public repo, the repo will only show a commit from Developer A. The Gitorious website will show that Developer B has pushed up a commit from Developer A, but that data is not contained in the repository. Thus collecting only Gitorious accounts and their mail addresses is insufficient. --Eike

==Random==
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/MovetoGit

2010-03-05T17:11:16Z

Steveire: /* Blockers */ Add info about KDE PIM blockers

=Blockers=

Tasks that need to get done before we can migrate

==SLA for gitorious.org==
{{Progress bar|30}}
'''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.

: aseigo and Frank (and someone?) had a meeting with Shortcut people during tokamak. They asked for a rather large sum of money; negotiations are continuing, but we might want to consider hosting our own server...

==Write / update importing rules for svn2git==
{{Progress bar|0}}
'''Owner:''' see below - 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 [[Projects/MoveToGit/UsingSvn2Git|Using 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
|tnyblom
|0
|Just getting started Help needed.
|-
|SC/kdepimlibs
|tnyblom
|0
|Just getting started Help needed.
|-
|SC/kdeplasma-addons
|
|0
|
|-
|SC/kdesdk
|mattr
|0
|just starting
|-
|SC/kdetoys
|mattr
|0
|just starting
|-
|SC/kdeutils
|
|0
|
|-
|SC/kdewebdev
|
|0
|
|-
|extragear/sdk/kdevelop
| apaku
| 85
| Misses history from KDE3.3 and older (KDevelop3.2), probably something with layout-changes, might need recurse-action but don't know how to do it.
|-
|extragear/sdk/kdevplatform
| apaku
| 100
| done, all tags seem fine all branches are there
|-
|extragear/*/*
|
|xx
|expand the *'s later (let's focus on the base modules first)
|-
|kde-common
|mattr
|0
|just starting
|-
|kdesupport
|
|0
|
|-
|koffice
|tzander
|100
|
|-
|promo
|
|0
|
|-
|quality
|
|0
|
|-
|tests
|
|0
|
|}

== Requirements of KDEPIM and KDAB ==

{{Progress bar|10}}
'''Owner:''' till (To be reassigned)

'''Status:''' ''Requirements of tools and for workflow identified. Someone from KDAB will be nominated to co-ordinate and communicate specific requirements''

'''Summary of issues'''

* Branch maintenance workflow
** KDAB maintains several branches of legacy versions of KDE for enterprise customer deployments. [http://websvn.kde.org:80/branches/kdepim/enterprise/ Enterprise 3.5] [http://websvn.kde.org:80/branches/kdepim/enterprise4/ Enterprise 4 (based on KDE 4.2)]. The current KDEPIM trunk known as Enterprise 5 and is Akonadi based.
** Periodically (weekly or so), tags are created from the enterprise branches with bugfixes. http://websvn.kde.org:80/tags/kdepim/ Customers can download the tagged versions with the latest updates. Fixes are merged from the Enterprise 3.5 branch, and into trunk (which sometimes involves a lot of work, as the fix must be ported to Akonadi). Additionally, fixes get merged in the other direction. From official KDE modules into the Enterprise branches.
** Some fixes from Enterprise 3.5 should not be merged into Enterprise 4 for reasons such as no longer being reproducible. Some fixes do not get merged for a long time because they require so much work that porting the fix or feature is deffered. There needs to be a list of commits which should never be merged (blocked commits), and commits which should be merged, but have not been merged yet. The tool [[Development/Tools/svnmerge.py|svnmerge]] is used to facilitate this. svnmerge uses svn properties to maintain lists of commits that are blocked and that have already been integrated. See for example the svn-blocked and svn-integrated properties here: http://websvn.kde.org:80/trunk/KDE/kdepim/. The lists of commits available to be merged into the various branches are here: http://www.kdab.com/~thomas/avail/
** There needs to be a way in git to keep track of what commits have been merged, what commits need to be merged, and what commits are blocked. There needs to be a way of merging only specific commits from a branch, but not all, and not blocked commits. Proposed solutions:
*** git cherry-pick allows 'merging' of individual commits, but does not record where the commits came from. Instead it creates a new commit without any reference to where it came from. This alone is unsuitable.
*** branch per fix. This would lead to an explosion of branches which is not a problem in git as all commits are branches. It may make gitk un-navigatable. There would need to be a naming convention such as komo-merge-<fixname> for branches which should be merged. The commands <tt>git checkout 4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout enterprise4.5 && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt> and <tt>git checkout master && git merge $(git branch -a | grep -E ^origin/komo-merge)</tt>. That could of course be optimized, but gets the point across. If the code has changed so much that the branch is unmergable, but the fix still needs to be in trunk, the system breaks down.
*** Custom git command with flat text files representing the same information as svnmerge, that is lists of blocked and integrated commits. This is most likely to be a workable solution, possibly together with conventional branch naming.
* Clean slate
** The existing backlog of commits which need to be merged or ported to trunk needs to be empty before the change to git so that nothing gets lost. This is a lot of work and will take time.
* Internal Tools and external customer tools and workflows
** KDAB is a consumer of KDE software, but also has downstream customers fetching software from where it is developed. That is, KDE SVN. For example packages are created from the tags in tags/kdepim. Some of these downstreams are less close to KDE and depend on current workflows. If KDE SVN is not the place to get those updates anymore, this needs to be communicated to those downstreams, and the tools updated.
** People who don't currently know how to use git need to get familiar with it so that transitioning will be nearly seamless, and not result in too much development slowdown.
* Other commitments
** Project deadlines and other commitments prevent the possiblity of blocking off time to work on git migration when so many other things need to be done which have milestones separate to KDE cycles. The required work to convert to git can't be prioritized as highly, and so will take more time.
* Technical difficulties and limitations.
** Up to KDE 3.5 there was one kdepim module. For the KDE4 cycle, this was split into kdepimlibs and kdepim. For the above mentioned merging to be possible, it makes sense for both to be in the same git module. This poses extra difficulty to the svn2git script.

'''Email threads'''

* Mid-January thread on scm-interest: http://thread.gmane.org/gmane.comp.kde.devel.pim/26726
* Early March thread on kde-core-devel (Till email): http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=63970
* Early March thread on kde-core-devel (Till follow-up):
http://thread.gmane.org/gmane.comp.kde.devel.core/63915/focus=64069

Schedules/KDE4/4.4 Feature Plan

2009-11-04T16:01:41Z

Steveire: /* kdepim */

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

<br> Legend:

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

__TOC__

<br>

= 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}}
|}

<br>

= 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}}

|}

<br>

= 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
|}

<br>

= 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}}

|}

= 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}} {{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}} {{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}}

|-
! 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}}

|}

<br>

= 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|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}}
|}

<br>

= 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|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}}
|}

= 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}}

|}

<br>

= 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}} {{FeatureInProgress|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}}

|}

<br>

= 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
|}

<br>

= 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}}
|}

<br>

= 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}}

|}

<br>

= 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-11-03T23:13:39Z

Steveire: /* kdepim */

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

<br> Legend:

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

__TOC__

<br>

= 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
|}

<br>

= 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}}

|}

<br>

= 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
|}

<br>

= 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}}

|}

= 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}} {{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}} {{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}}

|-
! 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|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}}
{{FeatureInProgress|libplasma|Show the PopupApplet's BusyWidget inside the popup|giuliocamuffo@gmail.com|Giulio Camuffo}}

|-
! 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}}

|-
! 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}}

|}

<br>

= 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|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}}

|}

<br>

= 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}}

|}

= 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}} {{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|kdeui|Finalize the api for the new systemtray: KStatusNotifierItem|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|kdeui|API to integrate KStatusNotifierItem and KNotification: both as class api and DBus specification API|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|kfile|Make status of file I/O display on file/folder icons("progress in icons").|shaun.reich@kdemail.net|Shaun Reich}}
|}

= 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}}

|}

<br>

= 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}} {{FeatureInProgress|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}}

|}

<br>

= 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}}
|}

= 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
|}

<br>

= 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}}
|}

<br>

= 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}}

|}

<br>

= 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}}
|}

Projects/PIM/Akonadi/Meeting2009-10

2009-10-17T15:03:59Z

Steveire: Add some notes from a Nepomuk related meeting.

This page is about the upcoming Akonadi Meeting in October 2009.

Date: October 16th (Friday) - October 18th (Sunday)

== Location / Travel Information ==

=== Office ===

<pre>
KDAB
Adalbertstrasse 7/8
10999 Berlin
Germany
Phone: +49-30-5213254-70
</pre>

Getting there from the hotel: takes about 15 minutes to walk, just follow the others, most have been here already ;-)

[http://maps.google.com/maps?f=d&source=s_d&saddr=An+der+Schillingbrucke+2,+10243+Berlin,+Germany&daddr=Adalbertstrasse+7%2F8,+10999+Berlin,Germany&hl=en&geocode=&mra=ls&dirflg=w&sll=37.0625,-95.677068&sspn=60.806372,49.130859&ie=UTF8&ll=52.504454,13.426173&spn=0.011611,0.032852&z=16 Hotel -> Office map]

Getting there directly: Take the subway line U8 to "Kottbusser Tor".

[http://www.bvg.de/index.php/de/Common/Document/field/file/id/2597/filename/S+U-Bahn_aktuell.pdf Subway and rail map of Berlin]

=== Hotel ===

<pre>
Hotel Ibis Berlin City Ost
An der Schillingbrucke 2
10243 Berlin
Germany
Phone: (+49)30/257600
Fax : (+49)30/25760333
</pre>

Easiest way to reach the hotel is by taking a train to Ostbahnhof (it's just across the street from the station). If your train doesn't stop there, take the S-Bahn from Hauptbahnhof, any east-bound line will do.

From TXL take the bus labeld 'TXL' to Hauptbahnhof or Alexanderplatz and switch to the S-Bahn there, any east-bound train will do.

In both cases you'll need a single 'AB' Ticket, which can be purchased on ticket machines and costs 2.10€.

== Attendees ==

Non-locals, please add yourself, your travel details and accommodation needs to the following table.

{| class="wikitable" border="1"
|-
! Name
! Travel
! Arrival
! Departure
! Accommodation needed
|-
| Tobias König
| train
| 16th, around 16:00
| 18th, around 17:30
| yes
|-
| Thomas McGuire
| train
| 14th, around 17:00
| 18th, around 15:00
| yes
|-
| Tom Albers
| train
| 16th, around 16:00
| 18th
| yes
|-
| Dmitry Ivanov
| plane
| 16th, around 12:00
| 18th, around 15:00
| no
|-
| Andras Mantia
| plane
| 14th, 17:05 TXL
| 19th, morning
| yes
|-
|-
| Sebastian Trueg
| train
| 16th afternoon
| 18th, ~ 18:00
| yes (prefer not to share a room and will pay myself)
|-
| Martin Koller
| plane
| 16th around 12:30
| 18th, ~ 18:00
| yes
|-
| Sascha Peilicke
| train
| 16th
| 20th
| no
|-
| Kevin Ottens
| plane
| 11th
| 18th
| yes
|-
|-
| Will Stephenson
| drive
| 16th pm
| 18th
| no
|-
| Brad Hards
| train in, flight out
| 16th around 13:30
| 19th, 11:05 TXL
| yes
|-
|}

Locals present anyway:
* Bertjan Broeksema
* Frank Osterfeld
* Steve Kelly
* Till Adam
* Volker Krause

== Agenda ==

Please collect stuff you want to do/discuss here.

* We have quite some new public API which needs to be reviewed, in the following libraries:
** Mailtransport [[http://deltatauchi.de/~vkrause/kde/mailtransport-kde-4.3-trunk.diff Diff]]
** MessageViewer
** KMime [[http://deltatauchi.de/~vkrause/kde/kmime-kde-4.3-trunk.diff Diff]]
** Akonadi Core [[http://deltatauchi.de/~vkrause/kde/akonadi-kde-4.3-trunk.diff Diff]]
** Akonadi Contact
** Akonadi KMime
** Kontact Interface

* Application porting status and planning, data and settings migration:
** KMail
** KOrganizer
** Akregator

* KDE PIM module organization
** Fix apps/runtime split again

* Nepomuk integration
** Fix the usage of non-Fast resources in the feeder agents
** Fix the feeders to behave according to Sebastian's email, and document the correct behavior somewhere
** Avoid ontology duplication, move them to kdelibs or soprano maybe?

* Extensions
** Free / busy management
** Mail Handling / Rules (Sieve, etc)

* StandardActionManager redesign (to support multiple views and extensibility)

* Do PIM applications still need to be KUniqueApplications?

=== Friday ===

* Hacking

* 18:00 Porting status and planning, module organization etc.

* 19:00 Dinner

* 22:00 API review Akonadi Core library

=== Saturday ===

* 08:15 Hacking

* 10:00 API review libakonadi and mailtransport

* 12:30 Lunch

* 13:00 Nepomuk integration

* 15:30 API review ETM, KMime

* Brad's extensions

* StandardActionMananger redesign

* Hacking

* 19:00 Dinner

* Hacking

=== Sunday ===

* 8:00 Begin

* Hacking

* 12:00 Lunch

* Hacking

== Meeting Notes ==

=== Akonadi/Nepomuk/Search and the future ===
Attending: Volker, Steve, Sebastian Trueg, Will Stephenson, Kevin Ervin

* Discussed future of desktop PIM and applications which are context or project specific rather than transport specific. Ie, beyond the concepts of "one application handles my email, another handles my contacts, another handles my notes." Instead these things should be grouped and available in applications which present them by project/task or person.
** Should be able to clear completed tasks by taking action on them. For any task, there may be multiple action paths to complete before the task is "complete", eg "The cat just threw up. Clean up the mess. Take the cat to the vet". Two action paths to handle the sick cat.
* Communicating with contacts independently of the transport mechanism in an application which can show history of communication with the person. Also, be able to configure notifications such as "Notify me the next time this person is online using the message 'Talk to Alice about the server backups'"
* Merging of contacts from multiple resources.
** Tricky because some resources have read-only access.
** Some resources rewrite fields, which could mean bugs like having to perform a merge operation again and again.
** Could be sensible to link Akonadi contacts to PIMO::Person objects in Nepomuk.
* Considering the implementation of how tags should be represented in PIM apps.
** Showing "All available tags from Nepomuk with linked items in the collections" would not scale because people could have thousands of, eg, emails, but only several would be relevant and contain tagged emails. It could be more sensible to configure individual simple searched such as "show me emails tagged with 'giraffe'" and use searches instead of explicitly using the tag resource.
** Nepomuk triples can be queried in interesting unrestricted and versatile ways. predicates can be variables and can have placeholders.
** Discussed the ideas brought out in Zeitgeist and how it can relate to Nepomuk and hooked into KIO.
* How can PIM relate to plasma activities, for example?
** Possible that PIM applications should not directly respond to changes in plasma activity, but plasma activity should map in some way to one or more 'PIMO::Project', and therefore change the most easily acceptible data related to the project.
* Storing search index of encrypted emails in a second, encrypted rdf store.
** Virtuoso has some useful stuff to make this possible, but it is preferable to create a model in the Soprano interface instead.
* Synching two Nepomuk stores.
** Possible to use a resource that represents remote nepomuk objects as akonadi Items and feed them into the local index.
** Soprano needs to get some more api for that.
* Separate but related is accessing a remote Akonadi server over ssh for example.

[[Category:Akonadi]]
[[Category:PIM]]

Projects/PIM/Akonadi

2009-04-21T11:06:20Z

Steveire: /* KResource Migration Status */ Add diagram of migration strategy.

== Akonadi TODO ==
The following list contains the things which need to be done for Akonadi.

Note: The person noted in the "Contact" column is not necessarily the one implementing that feature, but the one who can tell you what to do and how to help, i.e. you can also contribute to those tasks ;-)

=== Core ===

==== KDE 4.1 / Akonadi 1.0 ====

Urgent tasks that need to be finished for the KDE 4.1 release ('''May 19th'''):

{| 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 !! Item !! Description !! Contact
{{FeatureDone|Item streaming in ItemSync/ResourceBase|As discussed in Osnabrueck|Tom/Volker}}
{{FeatureDone|Payload serialization format versioning|see below
tokoe@kde.org|Tobias}}
{{FeatureDone|API for additional item parts|As discussed in Osnabruck|Volker/Tobias}}
{{FeatureDone|Infrastructure for showing additional dialogs from agents/resources|As discussed in Osnabrueck|Tom}}
{{FeatureDone|Allow to limit ItemFetchJob to current cache content|Prevents search index feeder agents from downloading all remote data|vkrause@kde.org|Volker}}
{{FeatureDone|Fix API for item/collection modifications|See Osnabrueck meeting notes for details|vkrause@kde.org|Volker}}
{{FeatureDone|Plugin Versioning|For serializer plugins, also check using Qt plugin stuff instead of the libkdepim plugin framework|tokoe@kde.org|Tobias}}
{{FeatureDone|Tray app|small app to control the server and have a something that can report errors|tomalbers@kde.nl|Toma}}
{{FeatureDone|Backup support|Dump & Restore database contents, also useful when upgrading to a newer database version|tomalbers@kde.nl}}
{{FeatureDone|Akonadi Artwork|Icon for the tray app|tomalbers@kde.nl|Toma}}
|}

==== KDE 4.2 / Akonadi 1.1 ====

That's the stuff we want to have in 4.2, very roughly ordered by priority. Releases are scheduled for early January 2009.

{| 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 !! Item !! Description !! Contact
{{FeatureDone|Server error reporting|Helpful error message when the server cannot be started or if there is some other problem communicating with it.|vkrause@kde.org|Volker}}
{{FeatureDone|KResource migration tool|For KABC and KCal resources, setting up Akonadi <-> KResource bridges where needed|Volker}}
{{FeatureDone|KResource bridges|Basically finished, needs more testing|Kevin}}
{{FeatureDone|Distribution Lists|Serializer Plugin and resource support|Tobias,Kevin}}
{{FeatureDone|Complete iCal resource|error handling, robustness, legacy formats, file montitoring|Volker}}
{{FeatureDone|Complete vCard resource|same as iCal + binary legacy format|Bertjan}}
{{FeatureDone|Item size|Needed by Mailody|toma@kde.org}}
{{FeatureDone|LINK/UNLINK commands|Managing item references in virtual collections|vkrause@kde.org|Volker}}
{{FeatureDone|Akonadi Testrunner|Running tests in a self contained Akonadi setup|igor_trindade@yahoo.com.br|Igor}}
{{FeatureDone|Remote file support for iCal/vCard resources|Replaces net/remote KRes resources|Bertjan}}
{{FeatureDone|Solid integration|Switch online/offline state in ResourceBase automatically|Bertjan}}
|}

==== Scheduled for KDE 4.3 / Akonadi 1.2 ====

Stuff we want to do for KDE 4.3, scheduled to be released in June 2009. The list is not completed yet, will be discussed during the [[Projects/PIM/Meetings/Osnabrueck_7|Osnabrueck 7]] meeting.

{| 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 !! Item !! Description !! Contact
{{FeatureDone|Fix unit tests|Make unittests work without destroying the production database|Igor/Volker}}
{{FeatureInProgress|Resource testing framework|Automated, shareable tests for resources|Igor/Volker}}
{{FeatureTodo|Review change notifications|See the various discussions about shortcomings in that area|}}
{{FeatureDone|Filesystem Backend|Store content data in files instead of the database, transfer filehandles instead of data to the client|Andras}}
{{FeatureInProgress|Port KOrganizer|Port from KResource to Akonadi|Frank/Sebastian}}
{{FeatureInProgress|Port KAddressBook|Replace with KContactManager|Tobias}}
{{FeatureInProgress|IMAP/Kolab resource||Kevin}}
{{FeatureInProgress|Port KNotes|File resource, serializer plugin, KNotes application, Kontact plugin|Jesper}}
{{FeatureInProgress|RID based operations|Item/collection retrieval and modification based on remote identifiers|Volker}}
{{FeatureDone|Microblog Support|Type library, serializer plugin, identi.ca/twitter resources|Tom}}
|}

==== Post KDE 4.3 / Akonadi 1.2 ====

This stuff is currently not considered for 4.3 due to lack of resources. Of course it will be added nevertheless if someone implements it. The list is completely unsorted.

{| 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 !! Item !! Description !! Contact
{{FeatureTodo|Error reporting|Akonadi::Job basically has only one error code: Unknown|Tobias}}
{{FeatureInProgress|Finish collection model/view|see below|thomas.mcguire@gmx.net}}
{{FeatureInProgress|Collection statistics for sub-trees|Provide a CollectionStatus object covering the full sub-tree in the model, allowing accumulated unread counts etc.|Thomas}}
{{FeatureTodo|Batch jobs for modifying/deleting collections/items|it would be great to have jobs which perform operations on several entities in one sitting (a use-case: mark all as read).|}}
{{FeatureTodo|Batch job to retrieve a set of items from Akonadi|Those items don't belong to the same collection, rather they are located in different collections|}}
{{FeatureTodo|CollectionFetchJob/ItemFetchJob should be able to retrieve entities by remote id/mimetype|
This is problematic with change notifications, as they have to know about the filtering with the \Seen flag as well.
This type of filtering would be possible with full Nepomuk interface though. We don't want yet another query language here. The plan is to fix the nepomuk agent and use that as semi-public interface for now.|}}
{{FeatureTodo|ResourceBase::collectionsRetrievalDone is missing|I'm working around by calling collectionsRetrievedIncremental() with empty collection lists|}}
{{FeatureTodo|Nepomuk integration|Generic Item tag/rate/comment, etc.|Tom}}
{{FeatureTodo|Account creation wizard|as discussed in Berlin, see below|}}
{{FeatureTodo|Sync collection tree after creating setting up a resource|see AgentInstanceCreateJob|}}
{{FeatureTodo|Support standard commands for QUndo framework||}}
{{FeatureTodo|Conflict detection in resources|See Osnabrueck meeting notes for details|}}
{{FeatureInProgress|Action framework|see below|vkrause@kde.org|Volker}}
{{FeatureInProgress|Fix API docs|The libakonadi move as well as the huge API changes following it broke lots of the docs technical and content-wise, see below|Tobias}}
{{FeatureTodo|Migration|Data and settings from pre-Akonadi times, see below|}}
{{FeatureTodo|Remote Search|Delegating searches to resources, see below|}}
{{FeatureTodo|Extended notifications|Item change notification do not yet include their source collections (real and virtual)|}}
{{FeatureTodo|Alternative for Akonadi::ResourceBase|Not using the scheduler to avoid the serialization of operations, see RSS resource. (This will get very complicated. Maybe use a proxy ResourceBase for this, which is thread-pooled?)|}}
{{FeatureTodo|Collection parameter for Monitor::itemChanged() and Monitor::itemRemoved()|
If the item resides in several collections (normal + virtual collections) then emit those signals for each collection. Adding this would mean changing it in many places (Monitor, Observer, ...), this is lots of work but probably the right thing to do.
Related to virtual collections, since with them, items can be in multiple collections. Better wait until the Nepomuk stuff is finished?|}}
|}

=== Supported Types ===

Overview on the current state of support for various types:

{|
|-
! Type !! Serializer !! Multipart Support !! Models !! Views !! Resources !! Notes
|-
|Email||yes||partial||MessageModel, MessageCollectionModel, threading proxy model||?||maildir, IMAP||threading agent
|-
|News||yes (1)||partial (1)||(1)||(1)||NNTP||
|-
|Contact||yes||no||ContactModel||-||vCard, facebook, KRes||
|-
|Events||yes||no||EventModel||-||iCal, KRes||
|-
|Notes||no||no||-||-||-||not started yet
|-
|Feeds||yes||no||Feeds, Items||?||OPML||GSoC in playground/pim
|-
|Bookmarks||yes||no||-||-||local bookmarks, del.icio.us||
|}

(1) see Email

=== Mail specific extensions ===

{| 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 !! Item !! Description !! Contact
{{FeatureTodo|Extend Message Model|Add all required columns, save/restore layout, flag delegate, configurable columns, etc.|}}
{{FeatureTodo|Share mail flag code|Standard actions, standard flag enum/constants, Nepomuk interaction|}}
{{FeatureTodo|Extend ENVELOPE|Add more information to the envelope payload part in the serializer plugin, eg. trheading information is missing|}}
{{FeatureTodo|Fix/finish threading||}}
|}

=== Event/Todo/Journal specific extensions ===

{| 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 !! Item !! Description !! Contact
{{FeatureTodo|Todo proxy model|See KOrganizers To-Do view|Bruno?}}
{{FeatureInProgress|Subtype identification|See discussion on kde-pim mailinglist|Kevin?}}
{{FeatureTodo|Agenda view|KOrganizer agenda view based on Akonadi|Bruno?}}
{{FeatureTodo|Month view|KOrganizer month view based on Akonadi|Bruno?}}
{{FeatureTodo|Timeline view|KOrganizer timeline view based on Akonadi|}}
|}

=== Resources, Agents and others ===

{| 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 !! Item !! Description !! Contact
{{FeatureDone|KResource Akonadi bridge|for applications using KCal or KABC|kevin.krammer@gmx.at|Kevin}}
{{FeatureDone|Akonadi KResource bridge|for data accessed through KCal or KABC resources|kevin.krammer@gmx.at|Kevin}}
{{FeatureTodo|Expire Agent||}}
{{FeatureInProgress|MBOX Resource||Bertjan}}
{{FeatureInProgress|Extend IMAP Resource||Kevin/Andras}}
{{FeatureInProgress|POP3 Resource||Thomas}}
{{FeatureInProgress|RSS Resource|GSoC in playground/pim ([[Projects/PIM/RSS_framework_for_Akonadi|Details]])|Dmitry/Frank}}
{{FeatureTodo|Filter Agent||}}
{{FeatureTodo|Search||}}
{{FeatureTodo| History resource||}}
{{FeatureTodo|Filter Rule GUI|Used by filters and searches|}}
|}

Resource status overview (this should list all resources existing in KDE3 or already under development for Akonadi):

{|
|-
! Resource !! Retrieve Collections !! Retrieve Items !! Change Collections !! Change Items !! Configuration !! Notes
|-
|iCal||yes (4)||yes (1) (2)||no||yes||yes||remote file support, file watching with conflict handling
|-
|vCard||yes (4)||yes (1) (2)||no||yes||yes||remote file support, file watching with conflict handling
|-
|maildir||yes (1) (4)||yes (1) (2)||?||?||yes||
|-
|mbox||no||no||no||no||no||not started yet, code exists in KMail
|-
|IMAP||yes (1) (4)?||yes (1) (2)||no||no||no||code exists in kio_imap4 and Mailody, support for extensions: quota, ACL, annotations missing, what about Kolab and Scalix?
|-
|POP3||no||no||no||no||no||not started yet,code exists in kio_pop3
|-
|NNTP||yes (4)||yes (2)||n/a||n/a||yes||Needs support for local collection names and collection hierarchy
|-
|Local Bookmarks||?||?||?||?||(3)||Code in akonadi/resources
|-
|OpenChange||?||?||?||?||?||Code in akonadi/resources
|-
|Facebook||?||?||?||?||?||Code in playground/pim
|-
|del.icio.us||?||?||?||yes||no||Code in playground/pim
|-
|KABC||yes(6)||yes||no||yes||yes||
|-
|KCal||yes(6)||yes||yes(7)||yes||yes||
|}

# only full sync supported currently, need optimization
# does not yet honor cache policy
# still relies on QSettings for configuration and/or doesn't provide configuration over D-Bus
# does not yet provide correct access control settings
# only adding new items, not changing existing ones
# availability of child collections depend on whether the KResource plugin has subresources
# child collections can be added or removed if the KCal plugin can have subresources

=== KResource Migration Status ===

Everything without migration support is implicitly converted to use the compat bridge currently.

[[Image:Akonadi-Kres.png]]

==== KABC migration status ====

{|
|-
! KResource !! Feature equivalent agent !! Migration support !! Notes
|-
|directory|| || ||vCard dir in development
|-
|file||vCard file||4.2||binary format no longer supported, migrated to compat bridge instead
|-
|groupdav||||||
|-
|groupwise||||||
|-
|kolab||||||
|-
|ldapkio||||||
|-
|net||vCard file||TODO||
|-
|scalix||||||
|-
|slox||||||
|-
|xmlrpc||||||
|}

==== KCal Migration Status ====

{|
|-
! KResource !! Feature equivalent agent !! Migration support !! Notes
|-
|blog||||||
|-
|bugzilla||||||
|-
|groupdav||||||
|-
|groupwise||||||
|-
|kabc (birthday)||birthdays||4.3||
|-
|kolab||||||
|-
|localdir||||||
|-
|local||iCal file||4.2||
|-
|remote||iCal file||TODO||remote supports different URLs for upload and download, the iCal file agent doesn't, is this needed at all?
|-
|featureplan||||||probably obsolete since we don't use the XML featureplan anymore
|-
|scalix||||||
|-
|slox||||||
|-
|xmlrpc||||||
|}

== Akonadi Braindump ==
Ideas/notes etc. on various open issues in Akonadi.

=== Akonadi Standard Actions ===

Idea: Have something like KStandardAction for Akonadi that not only includes the representation of the action but also its state management and the actual operations. Like libakonadi that should be splitted into a generic, type-independent part and be extensible for type-specific actions. This will enable code sharing among many applications and guarantee consistent actions everywhere.

State management: watch selection models of a collection and/or item model.

Use KXMLGUI for context menus in standard views to allow easy extensibility with custom actions.

Generic actions:
* new collection [done]
* new virtual collection
* delete collection [done for single selection]
* copy collection [done]
* cut collection
* paste collection [done]
* synchronize collection [done for single selection]
* synchronize resource
* synchronize everything
* show collection properties dialog [done]
* delete item(s) [done]
* copy item(s) [done]
* cut item(s)
* paste item(s) [done]
* paste native data
* tag item(s)
* comment item
* rate item(s)
* configure resource
* add resource? (would need a type parameter, etc.)
* delete resource
* manage local subscriptions [done]
* move to submenu
* copy to submenu

The list is definitely long enough to make this worthwhile.

=== Collection Model / Collection View ===

Ideas/missing features/bugs of the collection model/view:

* Enable/disable status columns
* Show status after the name (see KMail)
* Size column
* Save/restore layout
* <s>Custom collection icons (see KMail, also needed for resource defined special folders (eg. Inbox)</s>
* Status tooltips (see KMail in 3.5.9)
* Quick search
* Favorite folder view as proxy model on top of the normal collection model (FlatCollectionProxyModel might be helpful for there)
* Accumulated statistics (unread, total, size)
* Fix dnd: move/copy/cancel menu always shows up and never has any effect

=== Compatibility ===

Notes on how to keep long-term protocol, source and binary compatibility.

* <s>Detect server version in Akonadi::Session, might be useful in case of protocol extensions/changes</s>
* What about database server version updates?
* <s>Versioning or any other kind of serialization format meta data, we'll need that in case of changes in serialization formats (see eg. Robert's compression patch where this is needed)</s>
* <s>We currently use 32 bit ids, probably hard to change later on, is that enough?</s>
* <s>Plugin versioning</s>

=== Resource API issues ===

Notes/ideas/complaints about the Akonadi::ResourceBase API:

* Extremely error prone:
** Scheduler dead-locks when a requested operation is not correctly announced as finished, esp. a problem in error cases.
** Using the result methods multiple times or when not requested asserts
* <s>Item streaming is missing, requiring all data to be in memory at once</s>
* Non-incremental updates need to know the results of ItemSync to not have to provide all data, even for already existing/unchanged items.

=== API / BC issues ===

Smaller stuff that should be fixed before the ABI freeze and is not yet listed above:

* Cleanup the D-Bus format used by NotificationMessage
* No mentioning of "IMAP" in the public API, we are not using IMAP
* Naming and installed location of libraries, headers and executables (see discussion on kde-pim ML)
* <s>Payload part labels are QStrings, attribute types are QByteArray</s>

=== Deployment issues ===

* Multiple access: Should multiple Akonadi instances' mysqlds access a single set of data files the mysql will likely corrupt the data. This can happen in any NFS+YP installation where users can log onto any machine and access shared homes. MySQL relies on filesystem locking to prevent multiple access. [http://dev.mysql.com/doc/refman/6.0/en/multiple-servers.html MySQL multiple instance docu].
* [http://dev.mysql.com/doc/refman/6.0/en/innodb-restrictions.html InnoDB tables should not be used on NFS].
* NFS speed: MySQL documentation recommends against locating its data files on network shares.
* AppArmor: Distros' AppArmor profiles prevent MySQL from writing outside its defined data directory (usually /var/lib/mysql). This is a problem at least with *buntu and openSUSE. These will need to be adapted. It is possible to daisy-chain profiles so that MySQL started by Akonadi receives a different profile to MySQL running standalone. An empty profile has all rights. Another possibility is to adapt the general MySQL profile so it can write to ${XDG_DATA_HOME}/akonadi(usually ${HOME/}.local/share/akonadi). Both support for profile chaining and ${HOME} may depend on the version of AppArmor installed. What about SELinux?
* Backup: MySQL data files should not be backed up without telling the mysqld process, otherwise a corrupt backup will be made. LOCK TABLES and FLUSH TABLES at the least. A dump can be made or mysqlhotbackup may be used in some circumstances. We should consider sysadmins' backup techniques when planning/promoting Akonadi, as a simple rsync cronjob with running Akonadi will not work. [http://dev.mysql.com/doc/refman/6.0/en/backup.html MySQL backup advice].

=== Account Creation Wizard ===

Notes on the resource configuration wizard discussion.

* WizardBase class
* Wizard discovery via .desktop files
* A wizard can configure multiple resources (eg. IMAP + LDAP for Kolab) and non-resources (mailtransport)
* Optionally hide resources completely covered by wizards in the Add Account dialog
* List wizards in the Add Account dialog
* Store Account -> Resources information to offer deletion of depending resources

=== PostgreSQL datastore support ===

First review of the akonadi code reveals PGSQL Qt driver is already supported, but the code is not totally ready for it. Some first reading comments about where to patch for supporting PostgreSQL too:

==== akonadi/server/src/storage/dbinitializer.cpp ====

* line 201..., ALTER TABLE ADD [UNIQUE] INDEX syntax is MySQL only, better use the common one CREATE [UNIQUE] INDEX ... one [done with revision 789899]
* line 303, QString DbInitializer::sqlType(const QString & type), LONGBLOB is the MySQL type, PostgreSQL will use BYTEA.
* line 362, qFatal("Implement index support for your database!");
mysql: SHOW INDEXES FROM %1
pgsql: SELECT c2.relname, i.indisprimary, i.indisunique, i.indisclustered, i.indisvalid, pg_catalog.pg_get_indexdef(i.indexrelid, 0, true), c2.reltablespace
FROM pg_catalog.pg_class c, pg_catalog.pg_class c2, pg_catalog.pg_index i
WHERE c.oid = '16713' AND c.oid = i.indrelid AND i.indexrelid = c2.oid
ORDER BY i.indisprimary DESC, i.indisunique DESC, c2.relname

relname | indisprimary | indisunique | indisclustered | indisvalid | pg_get_indexdef | reltablespace
--------------+--------------+-------------+----------------+------------+--------------------------------------------------------------+---------------
foo_pkey | t | t | f | t | CREATE UNIQUE INDEX foo_pkey ON foo USING btree (id) | 0
foo_time_key | f | t | f | t | CREATE UNIQUE INDEX foo_time_key ON foo USING btree ("time") | 0
(2 lignes)

==== akonadi/server/src/storage/datastore.cpp ====

* line 700, qint64 DataStore::highestPimItemId() const, seems wrong for a concurrent program (SELECT MAX(col) FROM table; is not reliable if another thread is inserting at the same time) : check the callers
* line 794, qint64 DataStore::lastInsertId( const QSqlQuery & query ), PostgreSQL doesn't provide concurrent-bogus last_insert_id, but from 8.2 accepts the syntax INSERT INTO ... RETURNING col1, col2, ...;
* line 806, QString DataStore::dateTimeFromQDateTime( const QDateTime & dateTime ), use PostgreSQL to_char() formatting function for date rather than having Qt do it

=== Documentation ===

* Avoid examples using KJob::exec() due to its problematic side-effects.
* Examples in the ItemCreateJob docs (and maybe others) operate on items in the root collection which does not work at all
* Resurrect the server API docs
* Content of http://api.kde.org/4.x-api/kdepim-apidocs/akonadi/html/index.html should probably be moved to server or client lib docs

=== Migration of pre-Akonadi data and settings ===

* KCal/KABC
** switch KRes resources to Akonadi KRes compat resources, use KRes Akonadi compat resource, basically injecting Akonadi inbetween
** Replace Akonadi KRes compat resources with their ported equivalent
** Application side does not need migration code, "only" port to Akonadi
* KMail
** Should migrate to one resource per account + one for previous local folders
** Problem: local folders are mixed mbox/maildir
*** Dedicated KMail compat resource?
*** Convert everything to maildir first?
** Flags are stored in proprietary binary format
* KNode
** Migrate every account to NNTP resource
** Local flags should be preserved, stored in proprietary binary format
** Local subscription state should be preserved (where is that stored?)
** Local folders using MBOX format + proprietary binary index
* Akregator

=== Search ===

* Delegation to resources still completely missing
** Requires query transformation
** Requires management for live searches
** Requires the ability to report search results (needs protocol extension)
* Query language still undecided, current options: XESAM, SPARQL
* Backend still undecided, current options: XESAM, Nepomuk

== KMail Breakdown Plan ==
The current plan is to put some parts of KMail into a stand-alone
library, independent of KMail. This increases code reuse (for example, the message composer could be shared with Mailody) and makes the code a lot easier to maintain and to port to Akonadi.

{| 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 !! Item !! Description !! Contact
{{FeatureTodo|Bodypart formatters||}}
{{FeatureTodo|Reader Window||}}
{{FeatureTodo|Composer: Editor||}}
{{FeatureTodo|Composer: Message Composer||}}
{{FeatureTodo|Composer: GUI Window||}}
{{FeatureTodo|Queue Manager for mailtransport||}}
{{FeatureTodo|Templates: Core||}}
{{FeatureTodo|Templates: GUI||}}
{{FeatureTodo|Port KMCommands||}}
{{FeatureTodo|Port away from KMMessage and KMFolder* everywhere it is left|An idea might be: wrap KMMsgBase/KMMessage inside a reference counted Message class. Insulate everything else from it by wrapper functions. KMFolder should be easier...|}}
{{FeatureTodo|Migration application for index and other config||}}
{{FeatureTodo|Port MDNs||}}
|}

== The Road to World Domination ==

Sort of related so the stuff above but with a scope for all of KDE PIM and beyond.

{| 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 !! Item !! Description !! Contact
{{FeatureTodo|Share identity config GUI parts|eg. the signature configuration widget|}}
{{FeatureTodo|Mailtransport Agent|Global shared outbox, central mail sending instance|}}
{{FeatureTodo|Recently sent to support in mailtransport|related to above, based on Akonadi/Nepomuk|}}
{{FeatureTodo|Composer engine|Shared stuff for KMail/KNode/Mailody: Crypto, editor, editor actions, attachment model, message assembly, etc.|}}
|}

== Akonadi FAQ ==

This FAQ primarily deals with technical and design questions, if you have questions about using Akonadi (such as "I get error X when starting Akonadi"), please refer to [http://userbase.kde.org/Akonadi userbase.kde.org/Akonadi].

=== Where do I find the Akonadi config files? ===

''~/.config/akonadi/''

=== Where does Akonadi store my data? ===

Akonadi merely acts as a cache for your data, the actual content stays where it has always been, .ics/.vcf/MBOX files, local maildirs, IMAP- and groupware servers. There is only a limited amount of data stored exclusively in Akonadi:
* Data not supported by the corresponding backends, such as email flags in case of maildir/mbox. This is comparable to KMail's binary index files stored alongside these files in pre-Akonadi times.
* Internal meta-data used by application or resources, such as information about the last synchronization with a backend or translated folder names.
* Data that has been changed while the corresponding backend has been offline and has not yet been uploaded.

=== Where can I find the Akonadi database? ===

''~/.local/share/akonadi/''

=== Where can I find the source code? ===

There are three different parts of source code:
* The Akonadi server, which is KDE-independent. Currently, the code can be found at [http://websvn.kde.org/trunk/kdesupport/akonadi/ kdesupport/akonadi]. The server code will likely move to the [http://www.freedesktop.org/wiki/ freedesktop.org project] in the future, the move has already been [https://bugs.freedesktop.org/show_bug.cgi?id=15711 requested].
* The Akonadi KDE client libraries are in [http://websvn.kde.org/trunk/KDE/kdepimlibs/akonadi/ kdepimlibs/akonadi].
* Various agents, resources, the Akonadi console and much other misc stuff is in [http://websvn.kde.org/trunk/KDE/kdepim/akonadi/ kdepim/akonadi]

=== Where can I find documentation? ===

The documentation is mainly in the code itself, in the form of doxygen comments.
You can find the generated documentation on [api.kde.org api.kde.org], for example:

* General documentation, including a design overview, is [http://api.kde.org/4.x-api/kdepim-apidocs/akonadi/html/index.html here]

: Note that some links in the above documentation which point to the server or the KDE client libraries are currently broken, use the links below to access that documentation.
* Documentation for the KDE Akonadi client library is [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/index.html here]
* Documentation about the server is [http://api.kde.org/kdesupport-api/kdesupport-apidocs/akonadi/server/html/index.html here]

=== Which DBMS does Akonadi use? ===

So far only MySQL. There is some work on PostgreSQL support going on though. Basically, every database that is supported by QtSQL can be used, requiring minimal changes in the code at most. However, not all of them provide the features needed by Akonadi (see next two questions).

=== Why not use sqlite? ===

We tried. Really. It can't handle the concurrent access very well, in the best case this means ''very'' slow operations, but we've also seen deadlocks and failing transactions. Once that's fixed in sqlite, adjusting Akonadi to use it again instead of MySQL is no problem.

=== Why not use MySQL/Embedded? ===

We tried that as well, there are two reasons for not using it: No support for the InnoDB engine (which we need for transaction support) and poor availability (only OpenSUSE provided usable packages, needed a patched QSQL driver).

=== Do I need a running MySQL server? ===

No. Akonadi starts its own local MySQL server (unless configured otherwise, see next question). All you need is having the 'mysqld' binary installed at runtime (usually found in the mysql-server package of your distribution).

=== Can Akonadi use a normal MySQL server running on my system? ===

Yes, it can. You find the corresponding settings in ''~/.config/akonadi/akonadiserverrc''.

=== I don't like a database server because of backups/running on NFS/etc. ===

See section "Deployment Issues" above, we are aware of that and working on it. Some of these, like backup/restore are already implemented. But please be aware that most of this issues also existed before (eg. with KMail's custom binary indexes).

=== Can a single Akonadi instance be used by multiple users? ===

No. There has to be one Akonadi server instance per user. However, it is possible to use a shared database server.

=== Can I access the Akonadi server on a remote machine? ===
No. Akonadi is not a groupware server. It's a local cache only.

=== What's the differences between Akonadi and EDS? ===
EDS is limited to contacts and calendar data, Akonadi is type-independent. Especially, Akonadi is designed to also handle high-volume data such as email. Akonadi and EDS also differ largely in their access protocol on a technical level (Corba/D-Bus vs. local socket with IMAP-like protocol/D-Bus) and also on a protocol level (type specific vs. generic).

=== How do I create a collection? ===

From the developers point of view, there is Akonadi::CollectionCreateJob for that, from the users point of view, most applications allow that, eg. Mailody or akonadiconsole.

However, there is one limitation: Top-level collections can only be created by resources, not by normal applications. The reason for that is that every object (collection or item) is supposed to have an owning resource, that is a resource that is responsible for storing and retrieving that object. There is an ongoing discussion to remove this restriction though.

So, if you want to create a collection eg. for testing purposes, add a resource first. Most Akonadi applications offer an option to do that, a module for KControl is planned as well.

=== How do I disable automatic migration from KDE's traditional framework? ===

The migration tool is controlled by standard KDE configuration file called ''kres-migratorrc''.

Distributors or system administrators wanting to disable the automatism will probably want to that globally, e.g. by editing the installed default configuration file, or by using KDE's configuration hierachy and using a profile config between that and the user level.

The quickest way to deactivate it for one user account only is to use KDE's ''kwriteconfig'' tool to set the respective configration value with a simple copy&paste of the following command:

''kwriteconfig --file kres-migratorrc --group Migration --key Enabled --type bool false''

Please note that at some point KDE applications such as Kontact, KOrganizer, KMail, KAddressBook will be using Akonadi directly, at which point migration either has to be enabled or performed manually.

=== How do I completely disable Akonadi startup? ===

If you already have applications natively using Akonadi, you of course can't disable Akonadi startup. <i>Mailody</i> and <i>KPilot</i> are applications that are already based on Akonadi, for example.

Other applications, like <i>KAddressbook</i> and <i>KOrganizer</i>, are not based on Akonadi yet, at the time of writing. Instead, they use the old KResource framework for storing contacts, calendars and notes.
During the KDE 4.2 beta time, these KResources were automatically migrated to Akonadi-based KResources, the so-called Akonadi compatibility resources. Therefore, applications like KAddressbook and KOrganizer would use Akonadi indirectly through KResources, and therefore would start the Akonadi server when being started. Note that the same situation applies for KMail, which uses addressbook functionality also based on KResources.

If Akonadi doesn't start up correctly for you, the following should help you to disable Akonadi startup and use your old KResources again.

First, disable automatic migration like described in the above FAQ entry.
Then, open <i>System Settings</i>, go to the <i>Advanced</i> tab and open the <i>KDE Resources</i> config panel. There, you can configure which type of KResources are used for contacts, calendars and notes. If the migration to Akonadi was successful, you'll probably only see the <i>Akonadi Compatibility Resource</i> as an active resource, and all others disabled.

To disable Akonadi startup, enable your old resources again, then disable and delete the Akonadi compatibility resource.

=== What is the relation between Akonadi and OpenSync? ===

Akonadi and OpenSync focus on different aspects and complement each other. Akonadi provides a unified way to access PIM data for applications and a framework to implement powerful connectors to varies data sources. OpenSync focus is on syncing two sets of PIM data.

An Akonadi plugin for OpenSync is currently under development, allowing to sync PIM data available through Akonadi with any other system supported by OpenSync, especially mobile phones.

=== When should I use Akonadi? ===

More precisely, when should you use for your application specific data instead of eg. just using a local file directly.

Akonadi is especially useful when you need one the following:

* Different backends for your data, like eg. a local file and a remote server. Akonadi provides a unified interface for application developers to access your data independent of the actual backend.
* Caching and change replay of remote data. Akonadi has support for that built in, giving you free offline support for any remote backend.
* Desktop-wide sharing of your data. As soon as more than one application (say your main applications and a plasmoid) accesses the same data you need to deal with locking, conflict detection, change notifications, etc. - or let Akonadi do that for you.

However, if you are just looking for a simple way to store your application data without needing one of the above, using Akonadi usually means more implementation work for relatively little gain.

=== Akonadi needs too much space in my home directory! ===

An empty, unused Akonadi database needs about 100 Mb of disk space. This is due to the MySQL InnoDB log files which work similar to a journal in a modern file system. These files are constant in size and independent of the actual data stored in Akonadi. The default size is optimized for performance on average desktop hardware where the use of 100 Mb of disk space is no problem. In other cases, such as multi-user systems or embedded devices, this default might not be optimal though.

The default size can be configured, globally or per-user. The global configuration file can be found in $PREFIX/share/config/akonadi/mysql-global.conf, the per-user file is in ~/.config/akonadi/mysql-local.conf and overwrites settings of the global file. In any of these files, you can change the settings '''innodb_log_file_size''' and assign it a smaller value than the default (64M).

For this setting to take effect you need to restart Akonadi. With older Akonadi versions (<=1.1.1) you might need to manually remove the InnoDB log files from ~/.local/share/akonadi/db_data for this change to take effect. The log files do not contain data after a clean shutdown and thus can safely be removed while Akonadi is not running.

An alternative approach especially for multi-user systems might be the use of a single, global MySQL server instance.

[[Category:PIM]]

== Links ==

* [[Projects/PIM/Akonadi/Testing|Akonadi Testing Framework]]
* [[Projects/PIM/Akonadi/Development_Tools|Akonadi Development Tools]]
* Tutorials:
** [[Development/Tutorials/Akonadi/Application|Application Development]]
** [[Development/Tutorials/Akonadi/Resources|Resource Development]]
** [[Development/Tutorials/Akonadi/SerializerPlugin|Serializer Plugin Development]]
* [[Projects/PIM/Akonadi/Bookmarks|Bookmark support based on Akonadi]]
* [http://pim.kde.org/akonadi/ http://pim.kde.org/akonadi/]
* API docs
** [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/index.html Client library]
** [http://api.kde.org/kdesupport-api/kdesupport-apidocs/akonadi/html/ Server]
* #akonadi IRC channel on freenode
* Meetings
** [[Projects/PIM/Akonadi/Meeting2008-11|Halloween Sprint 2008]]
** [[Projects/PIM/Meetings/Osnabrueck_7|Osnabrueck 7]]
** [[Projects/PIM/Akonadi/Meeting2009-04|Akonadi April Sprint 2009]]
* [[Projects/Summer of Code/2009/Ideas#KDE_PIM|Google Summer of Code 2009 Ideas]]

File:Akonadi-Kres.png

2009-04-21T11:01:50Z

Steveire: Diagram of Akonadi bridge resource migration strategy.

Diagram of Akonadi bridge resource migration strategy.

Projects/PIM/Akonadi/Meeting2009-04

2009-04-03T12:21:25Z

Steveire: Add some more to the agenda

This page is about the Akonadi Meeting in April 2009.

Date: April 3rd (Friday) - April 5th (Sunday)

== Location/links: ==

* [http://tinyurl.com/cuojlo Hotel & Office on Google Maps]
* [http://www.bvg.de/index.php/de/Common/Document/field/file/id/2597/filename/S+U-Bahn_aktuell.pdf Subway and rail map of Berlin]

<pre>
KDAB
Adalbertstrasse 7/8
10999 Berlin
Germany
</pre>

== Agenda ==

{{improve}}

* GSoC selection
* KAddressbook vs. KContactManager
* Resolve the POP3 agent/resource design disagreement
* User feedback
* Investigate the Lionmail performance issue
* Mail part splitting
* Searching
* How should virtual collections/linking be handled? ([http://thread.gmane.org/gmane.comp.kde.devel.pim/23831 thread]) Open issues include
** whether it should be possible to have both real items and linked items in one collection. If it was allowed it could take away difficult tasks like determining if a collection is virtual (currently hardcoded with search resource identifier in collectionutils_p.h).
** how to determine if a user operation such as moves are permitted to/from the collection (possibly using collection rights).
** Should list jobs fetch linked items or should that be configurable in the job?
** Figure out use cases for virtual collections. Current ones include search collections, nepomuk tagging, 'single inbox'. The tagging and inbox idea are probably just specialized searches anyway.
** Should it be possible to link collections as well as items?
** Should it be possible to cascade virtual collections? (nepomuk tag trees say yes). This is possibly a non issue because there is actually nothing virtual about virtual collections. It could be a regular collection tree which happens to contain no real items and only links to items.
* Progress on implementing move support in akonadi. ([http://thread.gmane.org/gmane.comp.kde.devel.pim/23754 thread])
* Can we have a recursive version of contentMimeTypes? (needed by entityTreeModel and could make filtering more sensible)
* Do we need to set some standards of compliance for names of Payload parts? Considering not all resources from third parties will use our stuff (KABC etc) we need to make sure they use the same names for payload parts.
* Should Monitor be configurable to watch {un,}subscribed collections?
* How should statistics work and what information should they give? They should show counts of a particular mimetype in a collection, not just total count. Possibly also counts of items with a particular flag or attribute (new, watched important etc). eg, int CollectionStatistics::countMimetype(const QString &mimeType ), int CollectionStatistics::countAttribute(Akonadi::Attribute attr, const QString &mimeType= QString()), int countFlags(Akonadi::Item::Flags flags, const QString &mimeTypes), (etc?)
* Do we need a way to know what payload parts are available to an item (or is it possible) or a bool Item::hasFullPayload()?
* Group photo

== Meeting Notes ==

{{improve|}}

[[Category:Akonadi]]
[[Category:PIM]]

Projects/PIM/Akonadi/Meeting2009-04

2009-04-02T17:32:12Z

Steveire: Add some things to discuss.

This page is about the Akonadi Meeting in April 2009.

Date: April 3rd (Friday) - April 5th (Sunday)

== Location/links: ==

* [http://tinyurl.com/cuojlo Hotel & Office on Google Maps]
* [http://www.bvg.de/index.php/de/Common/Document/field/file/id/2597/filename/S+U-Bahn_aktuell.pdf Subway and rail map of Berlin]

<pre>
KDAB
Adalbertstrasse 7/8
10999 Berlin
Germany
</pre>

== Agenda ==

{{improve}}

* GSoC selection
* KAddressbook vs. KContactManager
* Resolve the POP3 agent/resource design disagreement
* User feedback
* Investigate the Lionmail performance issue
* Mail part splitting
* Searching
* How should virtual collections/linking be handled? ([http://thread.gmane.org/gmane.comp.kde.devel.pim/23831 thread]) Open issues include
** whether it should be possible to have both real items and linked items in one collection. If it was allowed it could take away difficult tasks like determining if a collection is virtual (currently hardcoded with search resource identifier in collectionutils_p.h).
** how to determine if a user operation such as moves are permitted to/from the collection (possibly using collection rights).
** Should list jobs fetch linked items or should that be configurable in the job?
** Figure out use cases for virtual collections. Current ones include search collections, nepomuk tagging, 'single inbox'. The tagging and inbox idea are probably just specialized searches anyway.
** Should it be possible to link collections as well as items?
** Should it be possible to cascade virtual collections? (nepomuk tag trees say yes). This is possibly a non issue because there is actually nothing virtual about virtual collections. It could be a regular collection tree which happens to contain no real items and only links to items.
* Progress on implementing move support in akonadi. ([http://thread.gmane.org/gmane.comp.kde.devel.pim/23754 thread])
* Can we have a recursive version of contentMimeTypes? (needed by entityTreeModel and could make filtering more sensible)
* Do we need to set some standards of compliance for names of Payload parts? Considering not all resources from third parties will use our stuff (KABC etc) we need to make sure they use the same names for payload parts.
* Should Monitor be configurable to watch {un,}subscribed collections?

== Meeting Notes ==

{{improve|}}

[[Category:Akonadi]]
[[Category:PIM]]

Paths/Translator

2009-01-18T14:23:45Z

Steveire: Add link to Lokalize video

This page is a guide to new contributors on how to translate for KDE.

===Dive in ===
* What are .po and .pot files?
* joining the mailing list for your language.
* using X-Test
* Starting a new translation team
* Using KBabel/Lokalize http://www.kde.org.br/index.php?title=Tutorial_i18n#Traduzindo_os_arquivos_com_KBabel
* [http://youonlylivetwice.info/lokalize/lokalize-first.htm Lokalize video tutorial]

===Resources===
* kde-i18n-doc@
* irc://freenode.net/kde-i18n
* i18n.kde.org
* http://l10n.kde.org/teams-list.php

Schedules

2009-01-16T14:20:13Z

Steveire: /* KDE4 */

__NOTOC__

During development, the KDE project sets goals in features and dates for upcoming releases. This way, the team knows when it would be a good time to add a new feature or when it's time to
focus on cleaning up any bugs in preparation for a release. Any plans are tentative schedules and the final dates are generally decided on the kde-core-devel mailing list.

Learn more about [[Schedules/Release Schedules Guide|release schedules]].

== KDE4 ==
* [[Schedules/KDE4/Goals|KDE 4 Goals]]
* [[Schedules/KDE4/Application Porting Status|Application Porting Status]]

*'''KDE 4.3'''
** [[Schedules/KDE4/4.3 Release Schedule|Release Schedule]]
** [[Schedules/KDE4/4.3 Release Goals|Release Goals]]
** [[Schedules/KDE4/4.3 Feature Plan|Feature Plan]]

*'''KDE 4.2'''
** [[Schedules/KDE4/4.2 Release Schedule|Release Schedule]]
** [[Schedules/KDE4/4.2 Release Goals|Release Goals]]
** [[Schedules/KDE4/4.2 Feature Plan|Feature Plan]]
** [[Schedules/Is KDE 4.2 for you?|Is KDE 4.2 for you?]]
** [[Schedules/KDE4/4.2 Upstream Issues|Release Critical Upstream Issues]]
** [[Schedules/KDE4/4.2 Requirements|Compilation Requirements]]

*'''KDE 4.1'''
** [[Schedules/KDE4/4.1 Release Schedule|Release Schedule]]
** [[Schedules/KDE4/4.1 Release Goals|Release Goals]]
** [[Schedules/KDE4/4.1 Feature Plan|Feature Plan]]
** [[Schedules/Is KDE 4.1 for you?|Is KDE 4.1 for you?]]

*'''KDE 4.0'''
** [[Schedules/KDE4/4.0 Release Schedule|Release Schedule]]
** [[Schedules/KDE4/4.0 Release Roadmap|Release Milestones]]
** [[Schedules/KDE4/4.0 Module_Status|Module Status and Pending Application Issues]]
** [[Schedules/KDE4/4.0 Upstream Issues|Release Critical Upstream Issues]]
** [[Schedules/KDE4/4.0 Announcements|Announcement Information]]
** [[Schedules/KDE4/4.0 Requirements|Compilation Requirements]]

== KDE3 ==

*'''KDE 3.5''' [[Schedules/KDE 3.5 Release Schedule|release schedule]], [[Schedules/KDE 3.5 Feature Plan|feature plan]]

=== Previous releases ===

*'''KDE 3.4''' [[Schedules/KDE 3.4 Release Schedule|release schedule]], [[Schedules/KDE 3.4 Feature Plan|feature plan]]
*'''KDE 3.3''' [[Schedules/KDE 3.3 Release Schedule|release schedule]], [[Schedules/KDE 3.3 Feature Plan|feature plan]]
*'''KDE 3.2''' [[Schedules/KDE 3.2 Release Schedule|release schedule]], [[Schedules/KDE 3.2 Feature Plan|feature plan]]
*'''KDE 3.1''' [[Schedules/KDE 3.1 Release Schedule|release schedule]], [[Schedules/KDE 3.1 Feature Plan|feature plan]]
*'''KDE 3.0''' [[Schedules/KDE 3.0 Release Schedule|release schedule]], [[Schedules/KDE 3.0 Feature Plan|feature plan]]

== KOffice ==

=== Current releases ===

*'''KOffice 2.0''' [[Schedules/KOffice 2.0 Release Schedule|release schedule]], [http://wiki.koffice.org/index.php?title=KOffice2/Goals feature plan]
*'''KOffice 1.6''' [[Schedules/KOffice 1.6 Release Schedule|release schedule]], [[Schedules/KOffice 1.6 Feature Plan|feature plan]]

=== Previous releases ===

*'''KOffice 1.5''' [[Schedules/KOffice 1.5 Release Schedule|release schedule]], [[Schedules/KOffice 1.5 Feature Plan|feature plan]]
*'''KOffice 1.4''' [[Schedules/KOffice 1.4 Release Schedule|release schedule]]
*'''KOffice 1.3''' [[Schedules/KOffice 1.3 Release Schedule|release schedule]]

== Extragear ==
* [[Schedules/Extragear|Overview of upcoming Extragear releases (WIP)]]

Schedules/Is KDE 4.2 for you?

2009-01-15T19:12:04Z

Steveire: Rendering and spelling

KDE 4.2 is due to be released at the end of January 2009. This is another
significant milestone in the ever improving and evolving KDE4 series. KDE
4.2 is the result of the hard work of hundreds of developers, artists,
documenters, translators, bug triagers and other technical experts.

Vision for the future computer interface remains the focus of the KDE4
series. KDE 4.2 brings new improvements and possibilities for interaction
with your computer and workspace that were never possible in the KDE 3.5
series.

For the most part, the workspace will behave as a user familiar with KDE3.5
expects. Improvements in that area since [[Schedules/Is KDE4.1 For You?|KDE4.1]] include:
* The panel can be resized easily.
* Panels support the autohide feature.
* Widgets can be moved on the panel, from the panel to the background, and from the background to the panel.
* The 'desktop background' can be used for icons in the same way as KDE3.5 behaved (that is, without a smaller folderview plasmoid, and with a background image).
* Icons on the desktop background or folderview can be freely moved around, and are no longer required to be arranged in a grid.
* Network manager will not be part of the official KDE 4.2 release, but will be available through [http://aseigo.blogspot.com/2008/11/on-my-other-perspective.html a collaboration with downstreams] at some point in the KDE4.2 cycle when distributions release their next stable versions (Spring/Summer 2009).
* Many rendering issues with nVidia cards are gone since a fixed NVidia driver has been [http://www.nvidia.com/object/unix.html released].

== Remaining Issues in KDE4 ==
Some issues still remain in KDE4 which will not be fixed in time for
KDE4.2. If these are still large issues for some users, KDE3 is still
available, usable and supported on some distributions.

* '''Printer Configuration''' KDE4 uses the Qt4 printer system directly.
It has not yet been extended to all of the functionality present in the
KDE3 print system.
* '''Systray rendering''' Some icons still do not render correctly on some
configurations. Updates to freedesktop.org systems, or porting those icons
to plasmoids will see this situation improve. Additionally, KDE supports a new window manager hint which will improve the situation when new versions of Qt and Gtk are released and distributed.

== Applications ==
All applications in the KDE official modules have seen many improvements,
bugfixes and new features. As in the case of KDE4.1, some applications familiar to users of KDE3.5 are not yet ported to KDE4 and some of these follow their own release schedules. Users should note however, that KDE3 versions of these applications do still work flawlessly alongside KDE4 applications and in a KDE4 workspace.

Since the release of KDE 4.1, [http://amarok.kde.org/en/releases/2.0.1.1 Amarok 2.0.1.1] has been released. Other notable and popular applications are under continuous development, and some of them may be released near the time of KDE4.2 release including Digikam and [http://www.koffice.org/announcements/announce-2.0beta5.php KOffice].

KDevelop is still under heavy development, and will not be ready for a
release in time for KDE4.2. However, a compromise of releasing a beta of
KDevelop with KDE4.2 has been reached. KDevelop is expected to see a full
KDE4 release several months after release of KDE4.2.

Other applications such as Konversation, Kaffeine and K3B do not yet have
KDE4 versions, but work is continuing on bringing them to KDE4.

'''Projects with a different release schedule than KDE4.'''

Project (Current Version - Final Release Date)
* [http://www.digikam.org/ digiKam] ([http://www.digikam.org/drupal/node/420 Beta 8] - Early 2009)
[http://www.digikam.org/drupal/about/releaseplan Digikam 0.10.0 Release Plan]

* [http://www.krusader.org Krusader 2.0] ([http://www.krusader.org/text.php?t=krusader-2.0.0-beta2.notes Beta 2] - Unknown)
Krusader is an advanced twin panel (commander style) file manager.

* [http://www.koffice.org/ KOffice 2.0] ([http://www.koffice.org/announcements/announce-2.0beta5.php Beta 5] - Spring 2009)
Binaries are available for all three major platforms. The developers are looking for volunteers to help put together screenshots for [http://www.kdedevelopers.org/node/3545 visual changelogs].

* [http://k3b.plainblack.com/ k3b 1.1] (Pre-Alpha - Unknown)
An alpha release of 1.1 (the KDE 4 port) is forthcoming, but not yet released.

* [http://kaffeine.kde.org/ Kaffeine] (Pre-Alpha - Unknown)
The KDE4 port is under way but requires major rewriting to support Phonon and other new features. No releases scheduled at this time.

* [http://kplayer.sourceforge.net/ KPlayer 0.7] (Released January 11 2008)
KPlayer 0.7 is the KDE4 port of KPlayer that was released on the same day as KDE 4.0. KPlayer 0.7.1 is planned for fall 2008 and will include a KDE4 port of its multimedia library which still used KDE3 compatibility layer in version 0.7.0.

* [http://basket.kde.org/ Basket] (1.0.3.1 (KDE3) - Released June 30 2008)
The KDE4 port of Basket is currently in a pre-alpha state.

* [http://konversation.kde.org/ Konversation 2.0] (Pre-Alpha - Unknown)
The KDE4 port will not be released to sometime after version 1.1, which will be the last KDE3 release.

*There are also several [http://games.kde.org/ KDE games] that do not have a KDE 4 port yet. Among these are kasteroids, kfouleggs.

* [http://www.kdevelop.org/ KDevelop 4.0] (Pre-Alpha - Unknown)
An alpha release of 4.0 (a rewritten from scratch version) [http://www.kdevelop.org/mediawiki/index.php/KDevelop_4/KDev3_KDev4_comparison_table is forthcoming], but not yet released. Normal users should continue to use the [http://www.kdevelop.org/index.html?filename=3.5/download.html stable KDevelop 3.5.2] version for the time being.

Schedules/Is KDE 4.2 for you?

2009-01-15T19:09:45Z

Steveire: Fix some rendering and link to nvidia page

KDE 4.2 is due to be released at the end of January 2009. This is another
significant milestone in the ever improving and evolving KDE4 series. KDE
4.2 is the result of the hard work of hundreds of developers, artists,
documenters, translators, bug triagers and other technical experts.

Vision for the future computer interface remains the focus of the KDE4
series. KDE 4.2 brings new improvements and possibilities for interaction
with your computer and workspace that were never possible in the KDE 3.5
series.

For the most part, the workspace will behave as a user familiar with KDE3.5
expects. Improvements in that area since [[Schedules/Is KDE4.1 For You?|KDE4.1]] include:
* The panel can be resized easily.
* Panels support the autohide feature.
* Widgets can be moved on the panel, from the panel to the background, and
from the background to the panel.
* The 'desktop background' can be used for icons in the same way as KDE3.5
behaved (that is, without a smaller folderview plasmoid, and with a
backround image).
* Icons on the desktop background or folderview can be freely moved
around, and are no longer required to be arranged in a grid.
* Network manager will not be part of the offical KDE 4.2 release, but
will be available through
[http://aseigo.blogspot.com/2008/11/on-my-other-perspective.html a
collaboration with downstreams] at some point in the KDE4.2 cycle when
distributions release their next stable versions (Spring/Summer 2009).
* Many rendering issues with nVidia cards are gone since a fixed NVidia driver has been [http://www.nvidia.com/object/unix.html released].

== Remaining Issues in KDE4 ==
Some issues still remain in KDE4 which will not be fixed in time for
KDE4.2. If these are still large issues for some users, KDE3 is still
available, usable and supported on some distributions.

* '''Printer Configuration''' KDE4 uses the Qt4 printer system directly.
It has not yet been extended to all of the functionality present in the
KDE3 print system.
* '''Systray rendering''' Some icons still do not render correctly on some
configurations. Updates to freedesktop.org systems, or porting those icons
to plasmoids will see this situation improve. Additionally, KDE supports a new window manager hint which will improve the situation when new versions of Qt and Gtk are released and distributed.

== Applications ==
All applications in the KDE official modules have seen many improvements,
bugfixes and new features. As in the case of KDE4.1, some applications familiar to users of KDE3.5 are not yet ported to KDE4 and some of these follow their own release schedules. Users should note however, that KDE3 versions of these applications do still work flawlessly alongside KDE4 applications and in a KDE4 workspace.

Since the release of KDE 4.1, [http://amarok.kde.org/en/releases/2.0.1.1 Amarok 2.0.1.1] has been released. Other notable and popular applications are under continuous development, and some of them may be released near the time of KDE4.2 release including Digikam and [http://www.koffice.org/announcements/announce-2.0beta5.php KOffice].

KDevelop is still under heavy development, and will not be ready for a
release in time for KDE4.2. However, a compromise of releasing a beta of
KDevelop with KDE4.2 has been reached. KDevelop is expected to see a full
KDE4 release several months after release of KDE4.2.

Other applications such as Konversation, Kaffeine and K3B do not yet have
KDE4 versions, but work is continuing on bringing them to KDE4.

'''Projects with a different release schedule than KDE4.'''

Project (Current Version - Final Release Date)
* [http://www.digikam.org/ digiKam] ([http://www.digikam.org/drupal/node/420 Beta 8] - Early 2009)
[http://www.digikam.org/drupal/about/releaseplan Digikam 0.10.0 Release Plan]

* [http://www.krusader.org Krusader 2.0] ([http://www.krusader.org/text.php?t=krusader-2.0.0-beta2.notes Beta 2] - Unknown)
Krusader is an advanced twin panel (commander style) file manager.

* [http://www.koffice.org/ KOffice 2.0] ([http://www.koffice.org/announcements/announce-2.0beta5.php Beta 5] - Spring 2009)
Binaries are available for all three major platforms. The developers are looking for volunteers to help put together screenshots for [http://www.kdedevelopers.org/node/3545 visual changelogs].

* [http://k3b.plainblack.com/ k3b 1.1] (Pre-Alpha - Unknown)
An alpha release of 1.1 (the KDE 4 port) is forthcoming, but not yet released.

* [http://kaffeine.kde.org/ Kaffeine] (Pre-Alpha - Unknown)
The KDE4 port is under way but requires major rewriting to support Phonon and other new features. No releases scheduled at this time.

* [http://kplayer.sourceforge.net/ KPlayer 0.7] (Released January 11 2008)
KPlayer 0.7 is the KDE4 port of KPlayer that was released on the same day as KDE 4.0. KPlayer 0.7.1 is planned for fall 2008 and will include a KDE4 port of its multimedia library which still used KDE3 compatibility layer in version 0.7.0.

* [http://basket.kde.org/ Basket] (1.0.3.1 (KDE3) - Released June 30 2008)
The KDE4 port of Basket is currently in a pre-alpha state.

* [http://konversation.kde.org/ Konversation 2.0] (Pre-Alpha - Unknown)
The KDE4 port will not be released to sometime after version 1.1, which will be the last KDE3 release.

*There are also several [http://games.kde.org/ KDE games] that do not have a KDE 4 port yet. Among these are kasteroids, kfouleggs.

* [http://www.kdevelop.org/ KDevelop 4.0] (Pre-Alpha - Unknown)
An alpha release of 4.0 (a rewritten from scratch version) [http://www.kdevelop.org/mediawiki/index.php/KDevelop_4/KDev3_KDev4_comparison_table is forthcoming], but not yet released. Normal users should continue to use the [http://www.kdevelop.org/index.html?filename=3.5/download.html stable KDevelop 3.5.2] version for the time being.

Schedules/Is KDE 4.2 for you?

2009-01-15T19:06:11Z

Steveire: Create initial page

KDE 4.2 is due to be released at the end of January 2009. This is another
significant milestone in the ever improving and evolving KDE4 series. KDE
4.2 is the result of the hard work of hundreds of developers, artists,
documenters, translators, bug triagers and other technical experts.

Vision for the future computer interface remains the focus of the KDE4
series. KDE 4.2 brings new improvements and possibilities for interaction
with your computer and workspace that were never possible in the KDE 3.5
series.

For the most part, the workspace will behave as a user familiar with KDE3.5
expects. Improvements in that area since [[Schedules/Is KDE4.1 For You?|KDE4.1]] include:
* The panel can be resized easily.
* Panels support the autohide feature.
* Widgets can be moved on the panel, from the panel to the background, and
from the background to the panel.
* The 'desktop background' can be used for icons in the same way as KDE3.5
behaved (that is, without a smaller folderview plasmoid, and with a
backround image).
* Icons on the desktop background or folderview can be freely moved
around, and are no longer required to be arranged in a grid.
* Network manager will not be part of the offical KDE 4.2 release, but
will be available through
[http://aseigo.blogspot.com/2008/11/on-my-other-perspective.html a
collaboration with downstreams] at some point in the KDE4.2 cycle when
distributions release their next stable versions (Spring/Summer 2009).
* Many rendering issues with nVidia cards are fixed.

== Remaining Issues in KDE4 ==
Some issues still remain in KDE4 which will not be fixed in time for
KDE4.2. If these are still large issues for some users, KDE3 is still
available, usable and supported on some distributions.

* '''Printer Configuration''' KDE4 uses the Qt4 printer system directly.
It has not yet been extended to all of the functionality present in the
KDE3 print system.
* '''Systray rendering''' Some icons still do not render correctly on some
configurations. Updates to freedesktop.org systems, or porting those icons
to plasmoids will see this situation improve. Additionally, KDE supports a new window manager hint which will improve the situation when new versions of Qt and Gtk are released and distributed.

== Applications ==
All applications in the KDE official modules have seen many improvements,
bugfixes and new features. As in the case of KDE4.1, some applications familiar to users of KDE3.5 are not yet ported to KDE4 and some of these follow their own release schedules. Users should note however, that KDE3 versions of these applications do still work flawlessly alongside KDE4 applications and in a KDE4 workspace.

Since the release of KDE 4.1, [http://amarok.kde.org/en/releases/2.0.1.1 Amarok 2.0.1.1] has been released. Other notable and popular applications are under continuous development, and some of them may be released near the time of KDE4.2 release including Digikam and [http://www.koffice.org/announcements/announce-2.0beta5.php KOffice].

KDevelop is still under heavy development, and will not be ready for a
release in time for KDE4.2. However, a compromise of releasing a beta of
KDevelop with KDE4.2 has been reached. KDevelop is expected to see a full
KDE4 release several months after release of KDE4.2.

Other applications such as Konversation, Kaffeine and K3B do not yet have
KDE4 versions, but work is continuing on bringing them to KDE4.

'''Projects with a different release schedule than KDE4.'''

Project (Current Version - Final Release Date)
* [http://www.digikam.org/ digiKam] ([http://www.digikam.org/drupal/node/420 Beta 8] - Early 2009)
[http://www.digikam.org/drupal/about/releaseplan Digikam 0.10.0 Release Plan]

* [http://www.krusader.org Krusader 2.0] ([http://www.krusader.org/text.php?t=krusader-2.0.0-beta2.notes Beta 2] - Unknown)
Krusader is an advanced twin panel (commander style) file manager.

* [http://www.koffice.org/ KOffice 2.0] ([http://www.koffice.org/announcements/announce-2.0beta5.php Beta 5] - Spring 2009)
Binaries are available for all three major platforms. The developers are looking for volunteers to help put together screenshots for [http://www.kdedevelopers.org/node/3545 visual changelogs].

* [http://k3b.plainblack.com/ k3b 1.1] (Pre-Alpha - Unknown)
An alpha release of 1.1 (the KDE 4 port) is forthcoming, but not yet released.

* [http://kaffeine.kde.org/ Kaffeine] (Pre-Alpha - Unknown)
The KDE4 port is under way but requires major rewriting to support Phonon and other new features. No releases scheduled at this time.

* [http://kplayer.sourceforge.net/ KPlayer 0.7] (Released January 11 2008)
KPlayer 0.7 is the KDE4 port of KPlayer that was released on the same day as KDE 4.0. KPlayer 0.7.1 is planned for fall 2008 and will include a KDE4 port of its multimedia library which still used KDE3 compatibility layer in version 0.7.0.

* [http://basket.kde.org/ Basket] (1.0.3.1 (KDE3) - Released June 30 2008)
The KDE4 port of Basket is currently in a pre-alpha state.

* [http://konversation.kde.org/ Konversation 2.0] (Pre-Alpha - Unknown)
The KDE4 port will not be released to sometime after version 1.1, which will be the last KDE3 release.

*There are also several [http://games.kde.org/ KDE games] that do not have a KDE 4 port yet. Among these are kasteroids, kfouleggs.

* [http://www.kdevelop.org/ KDevelop 4.0] (Pre-Alpha - Unknown)
An alpha release of 4.0 (a rewritten from scratch version) [http://www.kdevelop.org/mediawiki/index.php/KDevelop_4/KDev3_KDev4_comparison_table is forthcoming], but not yet released. Normal users should continue to use the [http://www.kdevelop.org/index.html?filename=3.5/download.html stable KDevelop 3.5.2] version for the time being.

Projects/PIM/Meetings/Osnabrueck 7

2009-01-09T21:36:04Z

Steveire: /* Agenda */ Add note to update datastore.cpp

Annual KDE PIM meeting in Osnabrueck 2009.

Date: Jan 09th (friday) to Jan 11th (sunday).

== Location/Travel ==

Location: <b>NEW</b> office of Intevation GmbH (Neuer Graben 17, 49074 Osnabrück, Germany), http://www.intevation.de/travel.en.html

Hotel: http://www.dom-hotel-osnabrueck.de/index_en.php (as usual)

== Agenda ==

Unscheduled topics and corresponding responsible persons (feel free to remove yourself there if you don't like what I assigned to you ;-) ):
* Porting strategy for KABC/KCal based resources and applications (Kevin, Tobias)
** Designing an Akonadi-based replacement for KABC::StdAddressbook
* Needed Akonadi developments for 4.3 (Volker)
** Free/Busy support (Brad, Will)
** Consideration of moving mail output (i.e. kdepim/mailtransport functionality) to Akonadi (Brad, Will also curious)
* Review Akonadi conflict detection (Stephen, Tobias, Volker)
** detecting backend induced conflicts on the resource side
** how to handle conflicts/GUI presentation
* Re-Redesigned KMime ContentStrategy stuff using KJobs (still to do) (Stephen)
* How to use Akonadi in your application/best practices/api dox review (Stephen)
* Review Akonadi extensions currently developed in playground/pim (Stephen, Volker)
* Review the distlist situation (Kevin, Tobias)
* Bugzilla organization for Akonadi/KDE PIM (all)
* Review of datastore.cpp in akonadi including possible refactoring and collectionMoved patch (Stephen, Volker)

<b>Put topics you would like to discuss here</b>

Tentative schedule:

=== Friday ===

All day: arrival

* Forcing Ingo to finally commit his Akonadi work from the last meeting (Volker) ;-)
* Evaluating the Akonadi migration in 4.2 or: the very last chance to stop Akonadi in 4.2 (Kevin, Volker)
* KDE PIM runtime/apps split (Tom)
* Discuss the fd.o situation (Cornelius)
* Review Akonadi change notification (Stephen, Volker, Kevin, Tobias)

19:00 - 22:00 Dinner at "Chows Garten", Große Hamkenstr. 19

=== Saturday ===

08:00 Breakfast

* Presentation of the Akonadi on N810 project (Karim, Cédric, Romain, Audrey, Guillermo)
* KMail porting strategy (Thomas, Till, Ingo, Volker, Stephen)
* Static code analysis in KDE PIM (Bertjan)

19:00 Dinner at "Rampendahl", Hasestr. 35, http://www.rampendahl.de

=== Sunday ===

08:00 Breakfast

All afternoon: departure

== BOFs ==

=== N810 ===
* David
* Thorsten

=== Static call graphs with egypt ===
* Thorsten

== Meeting Notes ==

* KResource -> Akonadi migration
** disable the creation of KRes client side bridges, but leave the migration enabled as such.
* Apps/Runtime split:
** we will create a runtime subdirectory in kdepim containing runtime dependencies (akoandi agents, plugins, etc) which should be buildable separately, cf. kdebase
* Akonadi MySQL dependency
** Distributions need to put MySQL on KDE based install/liveCDs. It's size means there is less room for other KDE apps and other distro tools and dependencies.
** The alternatives MySQL embedded and SQLite were rejected at proof of concept stage for different reasons: MySQL embedded does not handle transactions (doesn't have innoDB backend, which is the only one that supports real transactions), and is not as well supported by upstream for example the 64bit version is not well supported. SQLite is not fast enough for large amounts of data.
** It might be possible to use Akonadi server with SQLite for example, the default will remain MySQL, but distros will possibly be able to use SQLite for CDs.
** SQLite specific code still exists in <tt>kdesupport/akonadi/server</tt>, but needs to be updated as the schema may have changed since switching to use MySQL exclusively.
* Review Akonadi change notification:
** Adding ItemMoved and CollectionMoved and adding parent collection to {Collection,Item}Removed in a BC way.
** Adding parent Collections to the slots itemChanged and collectionChanged was also discussed. The problem is that using a full path in a filesystem as a remoteId can be problematic if a collection higher in the heirarchy is renamed or moved. As a resolution, Items and Collections will both get a QStringList of ancestor collections and only use the filename or dir name as a remoteId instead of a full path. This is only of interest to Resources. Even some resources (eg with only one collection) will ignore it and use a full path.
** If this gets built into Item and Collection, then this means that retrieveItem can remain BC and get this functionality anyway.
** CollectionSync and ItemSync: Currently compare remoteIds. Will possibly need to be changed to also compare the heirarchy also. Remove assumption that no longer hold like remoteIds being unique over whole collection tree.
** Ordering will remain in an attribute, and not be built into Collection. Ordering remains an application side configuration issue. Some aspects of this remain an open issue, such as ordering by applications before a remoteId gets generated for an item.
** Adding ResourceBase::clearCache() to allow the resources to remove any previous cache content in case there configuration changed in a drastic ways. While this should mostly work currently already with the Item/CollectionSync stuff, there might be tricky corner cases if some remoteIds are reused.

<b>Please complete by adding your notes!</b>

[[Category:PIM]]

Projects/PIM/Meetings/Osnabrueck 7

2009-01-09T21:26:14Z

Steveire: Add some notes about MySQL dependency

Annual KDE PIM meeting in Osnabrueck 2009.

Date: Jan 09th (friday) to Jan 11th (sunday).

== Location/Travel ==

Location: <b>NEW</b> office of Intevation GmbH (Neuer Graben 17, 49074 Osnabrück, Germany), http://www.intevation.de/travel.en.html

Hotel: http://www.dom-hotel-osnabrueck.de/index_en.php (as usual)

== Agenda ==

Unscheduled topics and corresponding responsible persons (feel free to remove yourself there if you don't like what I assigned to you ;-) ):
* Porting strategy for KABC/KCal based resources and applications (Kevin, Tobias)
** Designing an Akonadi-based replacement for KABC::StdAddressbook
* Needed Akonadi developments for 4.3 (Volker)
** Free/Busy support (Brad, Will)
** Consideration of moving mail output (i.e. kdepim/mailtransport functionality) to Akonadi (Brad, Will also curious)
* Review Akonadi conflict detection (Stephen, Tobias, Volker)
** detecting backend induced conflicts on the resource side
** how to handle conflicts/GUI presentation
* Re-Redesigned KMime ContentStrategy stuff using KJobs (still to do) (Stephen)
* How to use Akonadi in your application/best practices/api dox review (Stephen)
* Review Akonadi extensions currently developed in playground/pim (Stephen, Volker)
* Review the distlist situation (Kevin, Tobias)
* Bugzilla organization for Akonadi/KDE PIM (all)

<b>Put topics you would like to discuss here</b>

Tentative schedule:

=== Friday ===

All day: arrival

* Forcing Ingo to finally commit his Akonadi work from the last meeting (Volker) ;-)
* Evaluating the Akonadi migration in 4.2 or: the very last chance to stop Akonadi in 4.2 (Kevin, Volker)
* KDE PIM runtime/apps split (Tom)
* Discuss the fd.o situation (Cornelius)
* Review Akonadi change notification (Stephen, Volker, Kevin, Tobias)

19:00 - 22:00 Dinner at "Chows Garten", Große Hamkenstr. 19

=== Saturday ===

08:00 Breakfast

* Presentation of the Akonadi on N810 project (Karim, Cédric, Romain, Audrey, Guillermo)
* KMail porting strategy (Thomas, Till, Ingo, Volker, Stephen)
* Static code analysis in KDE PIM (Bertjan)

19:00 Dinner at "Rampendahl", Hasestr. 35, http://www.rampendahl.de

=== Sunday ===

08:00 Breakfast

All afternoon: departure

== BOFs ==

=== N810 ===
* David
* Thorsten

=== Static call graphs with egypt ===
* Thorsten

== Meeting Notes ==

* KResource -> Akonadi migration
** disable the creation of KRes client side bridges, but leave the migration enabled as such.
* Apps/Runtime split:
** we will create a runtime subdirectory in kdepim containing runtime dependencies (akoandi agents, plugins, etc) which should be buildable separately, cf. kdebase
* Akonadi MySQL dependency
** Distributions need to put MySQL on KDE based install/liveCDs. It's size means there is less room for other KDE apps and other distro tools and dependencies.
** The alternatives MySQL embedded and SQLite were rejected at proof of concept stage for different reasons: MySQL embedded does not handle transactions (doesn't have innoDB backend, which is the only one that supports real transactions), and is not as well supported by upstream for example the 64bit version is not well supported. SQLite is not fast enough for large amounts of data.
** It might be possible to use Akonadi server with SQLite for example, the default will remain MySQL, but distros will possibly be able to use SQLite for CDs.
** SQLite specific code still exists in <tt>kdesupport/akonadi/server</tt>, but needs to be updated as the schema may have changed since switching to use MySQL exclusively.
* Review Akonadi change notification:
** Adding ItemMoved and CollectionMoved and adding parent collection to {Collection,Item}Removed in a BC way.
** Adding parent Collections to the slots itemChanged and collectionChanged was also discussed. The problem is that using a full path in a filesystem as a remoteId can be problematic if a collection higher in the heirarchy is renamed or moved. As a resolution, Items and Collections will both get a QStringList of ancestor collections and only use the filename or dir name as a remoteId instead of a full path. This is only of interest to Resources. Even some resources (eg with only one collection) will ignore it and use a full path.
** If this gets built into Item and Collection, then this means that retrieveItem can remain BC and get this functionality anyway.
** CollectionSync and ItemSync: Currently compare remoteIds. Will possibly need to be changed to also compare the heirarchy also. Remove assumption that no longer hold like remoteIds being unique over whole collection tree.
** Ordering will remain in an attribute, and not be built into Collection. Ordering remains an application side configuration issue. Some aspects of this remain an open issue, such as ordering by applications before a remoteId gets generated for an item.
** Adding ResourceBase::clearCache() to allow the resources to remove any previous cache content in case there configuration changed in a drastic ways. While this should mostly work currently already with the Item/CollectionSync stuff, there might be tricky corner cases if some remoteIds are reused.

<b>Please complete by adding your notes!</b>

[[Category:PIM]]

Projects/PIM/Meetings/Osnabrueck 7

2009-01-09T17:41:41Z

Steveire: /* Agenda */ Add some resolution to some items

Annual KDE PIM meeting in Osnabrueck 2009.

Date: Jan 09th (friday) to Jan 11th (sunday).

== Location/Travel ==

Location: <b>NEW</b> office of Intevation GmbH (Neuer Graben 17, 49074 Osnabrück, Germany), http://www.intevation.de/travel.en.html

Hotel: http://www.dom-hotel-osnabrueck.de/index_en.php (as usual)

== Agenda ==

Unscheduled topics and corresponding responsible persons (feel free to remove yourself there if you don't like what I assigned to you ;-) ):
* Porting strategy for KABC/KCal based resources and applications (Kevin, Tobias)
** Designing an Akonadi-based replacement for KABC::StdAddressbook
* Needed Akonadi developments for 4.3 (Volker)
** Free/Busy support (Brad)
** Consideration of moving mail output (i.e. kdepim/mailtransport functionality) to Akonadi (Brad)
* Review Akonadi change notification (Stephen, Volker, Kevin, Tobias)
** Adding ItemMoved and CollectionMoved and adding parent collection to {Collection,Item}Removed in a BC way.
** Adding parent Collections to the slots itemChanged and collectionChanged was also discussed. The problem is that using a full path in a filesystem as a remoteId can be problematic if a collection higher in the heirarchy is renamed or moved. As a resolution, Items and Collections will both get a QStringList of ancestor collections and only use the filename or dir name as a remoteId instead of a full path. This is only of interest to Resources. Even some resources (eg with only one collection) will ignore it and use a full path.
** If this gets built into Item and Collection, then this means that retrieveItem can remain BC and get this functionality anyway.
** CollectionSync and ItemSync: Currently compare remoteIds. Will possibly need to be changed to also compare the heirarchy also. Remove assumption that no longer hold like remoteIds being unique over whole collection tree.
** Ordering will remain in an attribute, and not be built into Collection. Ordering remains an application side configuration issue. Some aspects of this remain an open issue, such as ordering by applications before a remoteId gets generated for an item.
* Review Akonadi conflict detection (Stephen, Tobias, Volker)
** detecting backend induced conflicts on the resource side
** how to handle conflicts/GUI presentation
* Re-Redesigned KMime ContentStrategy stuff using KJobs (still to do) (Stephen)
* How to use Akonadi in your application/best practices/api dox review (Stephen)
* Review Akonadi extensions currently developed in playground/pim (Stephen, Volker)
* Review the distlist situation (Kevin, Tobias)

<b>Put topics you would like to discuss here</b>

Tentative schedule:

=== Friday ===

All day: arrival

* Forcing Ingo to finally commit his Akonadi work from the last meeting (Volker) ;-)
* Evaluating the Akonadi migration in 4.2 or: the very last chance to stop Akonadi in 4.2 (Kevin, Volker)
* KDE PIM runtime/apps split (Tom)
* Discuss the fd.o situation (Cornelius)

19:00 Dinner at "Chows Garten", Große Hamkenstr. 19

=== Saturday ===

08:00 Breakfast

* Presentation of the Akonadi on N810 project (Karim, Cédric, Romain, Audrey, Guillermo)
* KMail porting strategy (Thomas, Till, Ingo, Volker, Stephen)
* Static code analysis in KDE PIM (Bertjan)

19:00 Dinner at "Rampendahl", Hasestr. 35, http://www.rampendahl.de

=== Sunday ===

08:00 Breakfast

All afternoon: departure

== BOFs ==

=== N810 ===
* David
* Thorsten

=== Static call graphs with egypt ===
* Thorsten

== Meeting Notes ==

* KResource -> Akonadi migration
** disable the creation of KRes client side bridges, but leave the migration enabled as such.
* Apps/Runtime split:
** we will create a runtime subdirectory in kdepim containing runtime dependencies (akoandi agents, plugins, etc) which should be buildable separately, cf. kdebase

<b>Please complete by adding your notes!</b>

[[Category:PIM]]

Getting Started

2009-01-05T19:37:58Z

Steveire: Add link to project neon page.

{{Template:I18n/Language Navigation Bar|Getting_Started}}
{{Box|Getting the Source|
[[Image:Action_down.svg|right|32px]]
* [[Getting_Started/Using Project Neon to contribute to KDE|Using Project Neon to contribute to KDE]]
* [[Getting_Started/Sources/Anonymous SVN|Anonymous SVN Quickstart Guide]]
* [[Getting_Started/Sources/Using Subversion with KDE|Using Subversion with KDE]] ''A more in depth look at accessing KDE source code with subversion, including the repository layout and working with revisions and patches.''
* [[Getting_Started/Sources/Snapshots|Daily Snapshots]]
* [http://websvn.kde.org/ Browse Code Online]
|100%}}

{{Box|Building KDE|
[[Image:Action_tool.svg|right|32px]]
There are different KDE branches. For production use, we recommend using a stable version of KDE.
* [[Getting_Started/Build/KDE4|KDE 4 (Development version, TRUNK)]]
* [[Getting_Started/Build/KDE4.x|KDE 4.x (Current 4.x Release or 4.x SVN BRANCH)]]
* [[Getting_Started/Build/Stable Version|KDE 3.5 (Stable version)]]
* [[Getting_Started/Build|Other versions and FAQ]] ''Including information for building on non-linux systems''
|100%}}

{{Box|Setting up the Environment|
[[Image:Action_pen.svg|right|32px]]
After KDE has been built, you'll want a good way to launch apps and perform your regular development tasks:
* [[Getting_Started/Increased Productivity in KDE4 with Scripts|Increased Productivity in KDE4 with Scripts]]
* [[Getting_Started/Set up KDE 4 for development|Set up KDE 4 for development]]
|100%}}
[[Category:Build KDE]]

Getting Started/Using Project Neon to contribute to KDE

2009-01-05T19:28:30Z

Steveire: Initial creation of page

[https://edge.launchpad.net/project-neon Project Neon] is a nightly build of the latest KDE trunk. It is an easy way for new contributors to KDE to get started without having to build the entire KDE-SVN tree and maintain the checkout. Additionally, dependencies are automatically handled and updated. This is suitable for new developers, translators, usability designers, documenters, promoters, bug triagers etc. This process makes the steps detailed on [[Getting_Started/Build/KDE4|this page]], including changes to your [[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|.bashrc]] unnecessary.

However, for developers, it may at some point become necessary to build more components from SVN as you become more involved in the project. The [[Getting_Started/Build/KDE4/kdesvn-build|kdesvn-build]] script is an easy way to build all or parts of KDE SVN.

== Requirements ==

Project neon always requires the latest stable Kubuntu release. As of January 2009, that is version 8.10. Previous versions of Kubuntu are not supported. It is possible to port Project Neon to other distributions, though there are currently no maintainers for other distributions working on the project. OpenSuse provides their own weekly build of KDE trunk. Find instructions on how to use it [[Getting Started/Using OpenSuse factory packages for development|here]].

== Installing Project Neon ==

To use Project Neon, add the following PPA (Personal Package Archive) to your sources.list using your preferred method:

<code bash>
# Project neon nightly KDE4 build
deb http://ppa.launchpad.net/project-neon/ubuntu intrepid main
</code>

After that, you can simply install the nightly package of whichever modules you want to work on. The following packages are available:

kde-nightly-kdebase
kde-nightly-kdeplasma-addons
kde-nightly-kdepim
kde-nightly-kdeedu
kde-nightly-kdenetwork
kde-nightly-kdeutils
kde-nightly-kdegraphics
kde-nightly-kdemultimedia

You can install all of the packages or just the ones you are interested in, depending on what you want to use them for. For example if you want to install the latest KDE Workspace (plasma, kwin etc), install the kde-nightly-kdebase package and kde-nightly-kdeplasma-addons package for extra plasmoids.

<code bash>
sudo aptitude install kde-nightly-kdebase kde-nightly-kdeplasma-addons
</code>

If you are only interested in application development in another module, you can install just the module package.

<code bash>
sudo aptitude install kde-nightly-kdepim
</code>

That command will also install the kdelibs, kdepimlibs and other dependencies too. In your regular (stable) kde session you can then run the nightly version of your chosen application by using the full path from the command line.

<code bash>
/opt/kde-nightly/bin/kmail
</code>

This will correctly use the nightly version of libraries instead of using the stable versions, so no other changes are necessary to your library path etc.

Alternatively, instead of using the full path to the executable, you could add the following to your .bashrc

<code bash>
_STABLE_PATH=$PATH
function switchtonightly {
export PATH=/opt/kde-nightly/bin:$_STABLE_PATH
}

function switchtostable {
export PATH=$_STABLE_PATH
}
</code>

This will allow you to optionally run unstable applications when you choose to in your session.

<code bash>
# Runs the stable version of kmail
kmail
switchtonightly
# runs the nightly version of kmail
kmail
# runs the nightly version of knode
knode
switchtostable
# runs the stable version of kmail
kmail
</code>

Note that settings for applications that you run from project neon do not conflict with your regular application settings and data. <tt>.kde-neon/</tt> is used instead of <tt>.kde/</tt>

== Using Project Neon for development ==

If you are joining one of the development teams in KDE, you will need a real svn checkout in order to contribute your code back to the project and create patches easily.

Some extra tools (neonmake) are provided for this purpose in the package amarok-nightly-tools. The packages come with development headers and debugging symbols built in.

<code bash>
sudo aptitude install amarok-nightly-tools
</code>

If you are already using a nightly package of the module you want to develop for, you should remove that, and checkout the development version. For example:

<code bash>
# Remove the packaged nightly version
sudo aptitude purge kde-nightly-kdepim
# Get the dependencies for building kdepim
sudo apt-get build-deps kde-nightly-kdepim
cd ~
# You may choose to do your development in a different folder.
cd Development
# Gets the latest version of the kdepim module.
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepim
# Shortcut provided by Project Neon to make the module
# and install it to the prefix /opt/kde-nightly/
neonmake
</code>

Note that you should usually checkout a module from kde, not an application. Most modules contain libraries shared within the module and which are necessary to build the applications in the module.

Also of note is the neonmake command. This is a shortcut which temporarily sets some environment variables like the LD_LIBRARY_PATH, the install prefix etc, then runs the equivalent of <tt>cmake && make && make install</tt>. It also runs rpath to configure the executable file to use the nightly libraries.

== Using Project Neon for translation ==

The Project Neon nightly packages include English language strings only. Translated packages are not available. However, if you are translating KDE applications, you can install the translations from KDE SVN in your normal workflow.

<code bash>
cd ~
cd Translations
# The -N switch checks out only the top level directory from svn.
svn co -N svn://anonsvn.kde.org/home/kde/trunk/l10n-kde4
cd l10n-kde4
# scripts neccessary to build translations.
svn co scripts
# Get the german translations
svn up de
# Generate the build files for the German language pack
./scripts/autogen.sh de
neonmake
</code>

After building the translations it is possible to either change the language in system settings, or run applications in another language using the environment variable KDE_LANG.

<code bash>
switchtonightly
KDE_LANG=de kmail
switchtostable
</code>

== Using Project Neon for documentation ==

The Project Neon nightly source packages include the offical KDE User Documentation in English.

TODO: How to build user docs from svn.

== Using Project Neon for promotion ==

If you are creating screenshots or screencasts of the latest version of KDE, project Neon is a simple and fast way of getting a default KDE4 session.

The KDE Promotion team recommends using the default background, theme, icons etc when preparing offical promotional materials (unless the feature you are showing is related to configuring KDE artwork). Project Neon uses the default artwork that comes with KDE4, so it is useful for creating promo materials.

Here is a shortcut to get all available modules from the PPA:

<code bash>
sudo aptitude install kde-nightly-kdebase kde-nightly-kdeplasma-addons \
kde-nightly-kdepim kde-nightly-kdeedu kde-nightly-kdenetwork \
kde-nightly-kdeutils kde-nightly-kdegraphics kde-nightly-kdemultimedia
</code>

The application [http://ariya.blogspot.com/2008/06/creating-fancy-screenshots-with.html screenie] is provided in Kubuntu 8.10 as <tt>screenie-qt</tt>.

<code bash>
sudo aptitude install screenie-qt
</code>

Template:UserbaseLink

2009-01-05T15:08:08Z

Steveire: New page: <noinclude> == How to use this template == If the userbase page has the same name as the techbase page, simply put <nowiki>{{UserbaseLink}}</nowiki> in the source of the page. </noinclud...

<noinclude>
== How to use this template ==

If the userbase page has the same name as the techbase page, simply put <nowiki>{{UserbaseLink}}</nowiki> in the source of the page.

</noinclude>
<includeonly>
The {{{1|{{PAGENAME}}}}} page on [http://userbase.kde.org/{{{1|{{PAGENAME}}}}} Userbase].
</includeonly>

User:Steveire/Games template

2009-01-05T15:07:12Z

Steveire: Mockup games template

{| border="1"
|-
| Arcade Games
| [[KBounce]] [[KGoldrunner]] [[KLines]] [[Kolf]] [[KSame]] [[KSpaceduel]]
|-
| Card games
| [[KPatience]] [[LsKat]]
|-
| Board Games
|-
| Card games
|-
| Dice Games
|-
| Logic Games
|-
| Tactic and Strategy
| [[Katomic]] [[KBattleship]] [[KJumpingCube]] [[KMines]] [[KNetWalk]] [[KolorLines]] [[Konquest]] [[KsirK]] [[SameGame]]
|-
| Toys
|}

Paths/Usability

2009-01-03T16:47:12Z

Steveire: Add mailing list

This page is for people who want to become usability designers in KDE.

== Dive in ==
* [[Tutorials/What is the HIG?]]
* [[Tutorials/Reviewing KDE apps for the HIG violations]]
* [[Tutorials/Using qt designer to fix HIG issues]]
* [[Tutorials/Writing use cases and scenarios]]
* [[Projects/Usability/HIG/SOU_Workspace/How_to_write_KDE4_Human_Interface_Guidelines]]

== Resources ==
* {{KDEML|kde-usability}}
* [[Projects/Usability]]
* [[Projects/Usability/HIG]]
* http://www.openusability.org/
* [[Projects/Usability/Project_User_Research_Template]]
* Existing User Research Profiles
** [[Projects/Gwenview/User_Research_Profile]]
** [[Projects/Kopete/User_Research_Profile]]
** [[Projects/Okular/User_Research_Profile]]
* Books (What books?)

Paths/Usability

2009-01-03T16:45:08Z

Steveire: Initial page

This page is for people who want to become usability designers in KDE.

== Dive in ==
* [[Tutorials/What is the HIG?]]
* [[Tutorials/Reviewing KDE apps for the HIG violations]]
* [[Tutorials/Using qt designer to fix HIG issues]]
* [[Tutorials/Writing use cases and scenarios]]
* [[Projects/Usability/HIG/SOU_Workspace/How_to_write_KDE4_Human_Interface_Guidelines]]

== Resources ==
* [[Projects/Usability]]
* [[Projects/Usability/HIG]]
* http://www.openusability.org/
* [[Projects/Usability/Project_User_Research_Template]]
* Existing User Research Profiles
** [[Projects/Gwenview/User_Research_Profile]]
** [[Projects/Kopete/User_Research_Profile]]
** [[Projects/Okular/User_Research_Profile]]
* Books (What books?)

Projects/Restructuring techbase and userbase

2009-01-03T15:20:26Z

Steveire: Remove some irrelevant stuff from the irc log.

The story so far:

* http://thread.gmane.org/gmane.comp.kde.devel.core/55248

* [[Projects/Contributor_Paths]]

* part of kde-devel thread starting from dhaumanns mail. http://thread.gmane.org/gmane.comp.kde.devel.general/56132/focus=56136

* IRC discussion:

<pre>

<dhaumann> steveire: I don't have much time, but maybe we can make
something out of it
<steveire> Hey, so currently there's a projects structure in techbase,
which shows some apps and stuff
<steveire> I think it would make more sense to use
techbase.kde.org/$MODULE or $APP etc. I mentioned it briefly earlier today
elsewhere:
http://thread.gmane.org/gmane.comp.kde.devel.pim/23239/focus=23259
<steveire> Since we don't have much time, I'll just quickly say what I'm
going to propose so you know. Modules and apps get top level urls. I don't
see much need to try to maintain a parent child relationship between pages
because none really exsits. Parents don't have a list of children and
children don't have a link to their parent (although I think that can be
turned on). And I don't think it would be chaos to allow apps and modules
have top level urls.
<dhaumann> steveire: it'll lead to people adding stuff to techbase that
doesn't belong there I fear.
<steveire> Also, we should probably think about what MW features we want
to use and be consistent about it. I mean there's the subpage feature
(which we're already pretty consistent about) and the categories feature
(which I don't think we're very constistent about yet.
<dhaumann> that's why we have the rather strict structure for now.
<steveire> dhaumann: Like what for example?
<dhaumann> steveire: see wiki.kde.org
<dhaumann> that's *the* example.
<dhaumann> steveire: meanwhile, I do think that e.g. a Plasma toplevel
item makes sense
<steveire> I've never really used it, but I'll have a look. What was put
there that doesn't belong?
<dhaumann> it's simply a *mess*
<dhaumann> :)
<steveire> Yes, but also, what is the focus of techbase.kde.org/plasma?
How to start contributing to it? Writing plasmoids? etc?
<dhaumann> on techbase aaron was also pretty much involved. Unfortunately
he's not here right now, but I would like to have his input.
<steveire> OK, well maybe I'll cc him too when I email kde-www about this
stuff.
<dhaumann> in Plasma/* could be all related to plasma. Contributing,
Tutorials, whatever
<dhaumann> steveire: can you CC me as well?
<steveire> Yes, sure
<dhaumann> steveire: did you look at userbase already?
<steveire> What do you mean look at?
<dhaumann> how it is organized.
<steveire> structure wise?
<steveire> Ah, yes, well a bit. I'll look a bit more.
<dhaumann> yes. they e.g. have Applications and Applicatins/Desktop
<dhaumann> but then they link to [[KWin]] etc. so they don't add a 3rd
level but rather link to a new toplevelitem.
<dhaumann> steveire: what I'd still like is to have subpages.
<steveire> Yeah, I see http://userbase.kde.org/Applications/Graphics and
then http://userbase.kde.org/Gwenview, apps get a top level.
<dhaumann> i.e. if we go to add [[$your_app]] then all related content to
this app should be in [[$your_app/*]]
<steveire> dhaumann: Yes. There I agree.
<dhaumann> that's something I'd agree with. Maybe the userbase people can
say something about it?
<steveire> Hopefully. What I'm really looking for is concensus, and
definitely not silence.
<dhaumann> yes :-)
<dhaumann> steveire: let's have a look at
http://techbase.kde.org/index.php?title=Projects
<dhaumann> what we see here are candidates for toplevel items. in fact,
maybe all
<dhaumann> I agree for the apps being toplevel. but for example should KDE
on Mac have a toplevel item as well?
<steveire> http://userbase.kde.org/KJots << This page {{includes}}
http://userbase.kde.org/KJots/Tips and it's also {{included}} in Tutorials.
I think we could do more with that kind of structure.
<dhaumann> steveire: about he {{:...} thing, how does it work exactly?
<steveire> It works the same way as templates, except the leading : makes
it use the top level instead of looking in the Template: namespace.
<steveire> {{Kjots/Tips}} would try to include {{Template:Kjots/Tips}},
but the leading : makes it not do that.
<dhaumann> steveire: is that maintainable?
<dhaumann> thinking about having a page that gets its content from lots of
other pages :)
<dhaumann> also it means duplication in several places. Is that desirable?
<dhaumann> or what are the benefits
<dhaumann> ?
<dhaumann> I can imagine that it would help to have Plasma/Tutorials +
Development/Tutorials and then a plasma section.
<dhaumann> is that it?
<steveire> userbase/tutorials might be one example which would be reduced
to a series of {{:APP/Tips}}. I think it's less duplication.
<dhaumann> what I meant is: you find the same content at different places,
which is duplication. :)
<steveire> Right, yes I suppose, but I think you want that in some cases.
Tutorials would be an index of tips for all apps, but if I go to
http://en.wikipedia.org/wiki/Special:Search?go=Go&search=KJots, there is
still a section of tips on that page too.
<dhaumann> steveire: e.g. if you search for KJots in the search edit
field, you will get the results KJots and KJots/Tips, which will then
display the same.
<steveire> Hehe, I wrote \[\[KJots\]\] there
<dhaumann> mh. not really problem maybe
<steveire> I don't think it's a problem. We can even <noinclude> a link on
the tips page back to the app page.
<dhaumann> I'm still not sure whether all this is a good idea :) but I'm
happy that people show interest
<dhaumann> maybe we can get more feedback on the mailing list, at least
that's what i hope
<steveire> Yes, sure. I just added a noinclude to
http://userbase.kde.org/KJots/Tips.
<steveire> I'll try to put a summary of sorts together and send an email
later or tomorrow.
<steveire> Thanks.
<dhaumann> hm. well, that gives you a message if you are on the page
directly.
<dhaumann> ok, cool.
<steveire> If you're not familiar, <includeonly> is analogous, but in the
other way.
<dhaumann> I know them
<dhaumann> What I meant is it gives you a notice now that there is more in
the KJots page, but no more.
<dhaumann> so it has no other effect wrt maintainability or structure.
<dhaumann> nevermind.
<dhaumann> have to leave :)
<dhaumann> I'm looking forward to find a good solution :)
<steveire> We could <includeonly>[[Category:Tips pages]]</includeonly> and
the tips pages would be in that category, but not the pages that
{{:include}} them
<steveire> Cool, later.
<annew> steveire: I've just come in and read this
<annew> I was wondering how the include works, so that's helped me, thanks
<steveire> annew: Hi, sure no problem.
<annew> steveire: I think we should try for consistency between userbase
and techbase
<annew> so could you keep me informed of discussions and decisions?
<steveire> Also regarging the kjots icon being too big, I think it should
only be shown once anyway, and not used as a list item as it is now
<steveire> annew: Are you on kde-www?
<annew> no - do you think I should be?
<annew> perhaps it makes sense
<steveire> I'd like to see it as a place to discuss *base.kde.org.
<steveire> I think it makes sense.
<annew> ok - I'll subscribe tonight
<steveire> jucato was involved in setting up userbase too wasn't he?
<steveire> Hmm, looks like userbase only allows openid, and not 'normal'
registration.
<annew> yes - danimo insisted on that
<annew> it makes creating a test account non-trivial

</pre>

Projects/Restructuring techbase and userbase

2009-01-03T15:14:11Z

Steveire: Initial creation of page

The story so far:

* http://thread.gmane.org/gmane.comp.kde.devel.core/55248

* [[Projects/Contributor_Paths]]

* part of kde-devel thread starting from dhaumanns mail. http://thread.gmane.org/gmane.comp.kde.devel.general/56132/focus=56136

* IRC discussion:

<pre>

<dhaumann> steveire: I don't have much time, but maybe we can make
something out of it
<steveire> Hey, so currently there's a projects structure in techbase,
which shows some apps and stuff
<steveire> I think it would make more sense to use
techbase.kde.org/$MODULE or $APP etc. I mentioned it briefly earlier today
elsewhere:
http://thread.gmane.org/gmane.comp.kde.devel.pim/23239/focus=23259
<steveire> Since we don't have much time, I'll just quickly say what I'm
going to propose so you know. Modules and apps get top level urls. I don't
see much need to try to maintain a parent child relationship between pages
because none really exsits. Parents don't have a list of children and
children don't have a link to their parent (although I think that can be
turned on). And I don't think it would be chaos to allow apps and modules
have top level urls.
<dhaumann> steveire: it'll lead to people adding stuff to techbase that
doesn't belong there I fear.
<steveire> Also, we should probably think about what MW features we want
to use and be consistent about it. I mean there's the subpage feature
(which we're already pretty consistent about) and the categories feature
(which I don't think we're very constistent about yet.
<dhaumann> that's why we have the rather strict structure for now.
<steveire> dhaumann: Like what for example?
<dhaumann> steveire: see wiki.kde.org
<dhaumann> that's *the* example.
<dhaumann> steveire: meanwhile, I do think that e.g. a Plasma toplevel
item makes sense
<steveire> I've never really used it, but I'll have a look. What was put
there that doesn't belong?
<dhaumann> it's simply a *mess*
<dhaumann> :)
<steveire> Yes, but also, what is the focus of techbase.kde.org/plasma?
How to start contributing to it? Writing plasmoids? etc?
<dhaumann> on techbase aaron was also pretty much involved. Unfortunately
he's not here right now, but I would like to have his input.
<steveire> OK, well maybe I'll cc him too when I email kde-www about this
stuff.
<dhaumann> in Plasma/* could be all related to plasma. Contributing,
Tutorials, whatever
<dhaumann> steveire: can you CC me as well?
<steveire> Yes, sure
<dhaumann> steveire: did you look at userbase already?
<steveire> What do you mean look at?
<dhaumann> how it is organized.
<steveire> structure wise?
<steveire> Ah, yes, well a bit. I'll look a bit more.
<dhaumann> yes. they e.g. have Applications and Applicatins/Desktop
<dhaumann> but then they link to [[KWin]] etc. so they don't add a 3rd
level but rather link to a new toplevelitem.
<dhaumann> steveire: what I'd still like is to have subpages.
<steveire> Yeah, I see http://userbase.kde.org/Applications/Graphics and
then http://userbase.kde.org/Gwenview, apps get a top level.
<dhaumann> i.e. if we go to add [[$your_app]] then all related content to
this app should be in [[$your_app/*]]
<steveire> dhaumann: Yes. There I agree.
<dhaumann> that's something I'd agree with. Maybe the userbase people can
say something about it?
<steveire> Hopefully. What I'm really looking for is concensus, and
definitely not silence.
<dhaumann> yes :-)
<dhaumann> steveire: let's have a look at
http://techbase.kde.org/index.php?title=Projects
<dhaumann> what we see here are candidates for toplevel items. in fact,
maybe all
<dhaumann> I agree for the apps being toplevel. but for example should KDE
on Mac have a toplevel item as well?
<steveire> http://userbase.kde.org/KJots << This page {{includes}}
http://userbase.kde.org/KJots/Tips and it's also {{included}} in Tutorials.
I think we could do more with that kind of structure. It looks like
userbase has section links turned off though, which makes editing it a
problem. Maybe we can get those back on.
<dhaumann> you have to log in, iirc
<steveire> dhaumann: Even logged in I don't see them. annew said the same
thing to me.
<dhaumann> hm ok.
<dhaumann> no idea then
<dhaumann> steveire: about he {{:...} thing, how does it work exactly?
<steveire> It works the same way as templates, except the leading : makes
it use the top level instead of looking in the Template: namespace.
<steveire> {{Kjots/Tips}} would try to include {{Template:Kjots/Tips}},
but the leading : makes it not do that.
Part Ingmar has left this channel.
<dhaumann> steveire: is that maintainable?
<dhaumann> thinking about having a page that gets its content from lots of
other pages :)
<dhaumann> also it means duplication in several places. Is that desirable?
<dhaumann> or what are the benefits
<dhaumann> ?
<dhaumann> I can imagine that it would help to have Plasma/Tutorials +
Development/Tutorials and then a plasma section.
<dhaumann> is that it?
<steveire> userbase/tutorials might be one example which would be reduced
to a series of {{:APP/Tips}}. I think it's less duplication.
<dhaumann> what I meant is: you find the same content at different places,
which is duplication. :)
<steveire> Right, yes I suppose, but I think you want that in some cases.
Tutorials would be an index of tips for all apps, but if I go to
http://en.wikipedia.org/wiki/Special:Search?go=Go&search=KJots, there is
still a section of tips on that page too.
<dhaumann> steveire: e.g. if you search for KJots in the search edit
field, you will get the results KJots and KJots/Tips, which will then
display the same.
<steveire> Hehe, I wrote \[\[KJots\]\] there
<dhaumann> mh. not really problem maybe
<steveire> I don't think it's a problem. We can even <noinclude> a link on
the tips page back to the app page.
<dhaumann> I'm still not sure whether all this is a good idea :) but I'm
happy that people show interest
<dhaumann> maybe we can get more feedback on the mailing list, at least
that's what i hope
<steveire> Yes, sure. I just added a noinclude to
http://userbase.kde.org/KJots/Tips.
<steveire> I'll try to put a summary of sorts together and send an email
later or tomorrow.
<steveire> Thanks.
<dhaumann> hm. well, that gives you a message if you are on the page
directly.
<dhaumann> ok, cool.
<steveire> If you're not familiar, <includeonly> is analogous, but in the
other way.
<dhaumann> I know them
<dhaumann> What I meant is it gives you a notice now that there is more in
the KJots page, but no more.
<dhaumann> so it has no other effect wrt maintainability or structure.
<dhaumann> nevermind.
<dhaumann> have to leave :)
<dhaumann> I'm looking forward to find a good solution :)
<steveire> We could <includeonly>[[Category:Tips pages]]</includeonly> and
the tips pages would be in that category, but not the pages that
{{:include}} them
<steveire> Cool, later.
<annew> steveire: I've just come in and read this
<annew> I was wondering how the include works, so that's helped me, thanks
<steveire> annew: Hi, sure no problem.
<annew> steveire: I think we should try for consistency between userbase
and techbase
<annew> so could you keep me informed of discussions and decisions?
<steveire> Also regarging the kjots icon being too big, I think it should
only be shown once anyway, and not used as a list item as it is now
<steveire> annew: Are you on kde-www?
<annew> no - do you think I should be?
<annew> perhaps it makes sense
<steveire> I'd like to see it as a place to discuss *base.kde.org.
<steveire> I think it makes sense.
<annew> ok - I'll subscribe tonight
<steveire> jucato was involved in setting up userbase too wasn't he?
<annew> I'm wondering about those section Edits -
<annew> I don't think all pages have them
<annew> I wonder whether there is something in the structure of the page
that decides that
<steveire> Well, for example on http://userbase.kde.org/KJots, There
should be edit links beside Tips, like there's edit links by all the
secions here: http://techbase.kde.org/Projects/PIM/KJots
<annew> steveire: it looks as though it's tied to heading levels
<steveire> Oh?
<annew> which page did you look at when you couldn't see them? can you
remember?
<steveire> http://userbase.kde.org/KJots
<annew> I see an [edit] against Features and against Tips
<steveire> Really? Maybe it's a user-side configuration issue...
<steveire> Yep: http://userbase.kde.org/Special:Preferences
<annew> strange
<steveire> We should check if that's the default for new accounts. Maybe I
changed it and don't remember
<annew> I don't know enough about this to check?
<steveire> It's probably part of localsettings.php- You probably can't
check.
<steveire> Except by creating a new account.
<annew> do we have to get danimo or tstaerk to do this, or can you?
<steveire> Nah, I'll create a test account and see what happens.
<steveire> Hmm, looks like userbase only allows openid, and not 'normal'
registration.
<annew> yes - danimo insisted on that
<annew> it makes creating a test account non-trivial

</pre>

Projects/PIM/Meetings/Osnabrueck 7

2009-01-02T18:31:34Z

Steveire: /* Agenda */ Add some stuff.

Kdepim

2009-01-02T13:44:41Z

Steveire: Redirecting to Projects/PIM

#redirect [[Projects/PIM]]

Paths/Translator

2008-12-30T16:44:00Z

Steveire:

This page is a guide to new contributors on how to translate for KDE.

===Dive in ===
* What are .po and .pot files?
* joining the mailing list for your language.
* using X-Test
* Starting a new translation team
* Using KBabel/Lokalize http://www.kde.org.br/index.php?title=Tutorial_i18n#Traduzindo_os_arquivos_com_KBabel

===Resources===
* kde-i18n-doc@
* irc://freenode.net/kde-i18n
* i18n.kde.org
* http://l10n.kde.org/teams-list.php

Paths/Translator

2008-12-30T16:40:56Z

Steveire: New page: This page is a guide to new contributors on how to translate for KDE. ===Dive in === * What are .po and .pot files? * joining the mailing list for your language. * using X-Test * Starting...

Kdepim

2008-12-30T16:31:57Z

Steveire:

Personal information Management suite from the KDE project.

The KDEPIM team develops applications such as Kontact, KMail, KNode, KOrganizer, KAddressbook, Akregator, KJots and others.

To join the team, simply email the {{KDEML|kdepim}} mailing list, and join the irc://freenode.net/kontact irc channel.

== Development ==
Current development focus as of January 2009 is on the Akonadi service and porting existing applications to Akonadi and KMime and other frameworks in KDE4.

== Documentation ==
(Someone is rewriting kmail docs, right?)

== Artwork ==
* (How's our icons)
* Custom email css templates etc

== Resources ==

* http://doc.trolltech.com/4.4/richtext.html - Used for the kmail composer. See also [http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/classKRichTextWidget.html KRichTextWidget].
* http://doc.trolltech.com/4.4/model-view-programming.html - Used throughout kdepim including kmail tree views etc.

* Relevant RFCs?

Paths/Artist

2008-12-30T16:24:06Z

Steveire:

This page is a guide to new contributors on how to create artwork for KDE.

===Dive in ===
* [[Paths/Artist/Creating desktop backgrounds]] - What sizes to make etc?
* [[Paths/Artist/Creating themes]]
* [[Paths/Artist/Creating KDE website designs]] - Are there standard css files somewhere?
* [[Paths/Artist/Creating icons]]
* [[Paths/Artist/Creating sounds]]
* [[Paths/Artist/Creating cursors]]
* [[Paths/Artist/Creating logos]]
* [[Paths/Artist/Creating plasma themes]]
* [[Paths/Artist/Submitting your artwork]] - kde-look (available through GHNS I think?), svn (kdeartwork/kdebase?), other?
* [[Paths/Artist/Naming icons correctly]]
* [[Paths/Artist/Using scripts to simplify icon management in SVN]]

===Resources===
* {{KDEML|kde-artists}}
* IRC: oxygen/kde-artists
* Oxygen palette?
* Useful inkscape tutorials?
* icon naming standard
* xdg mailing list
* etc?

Paths/Artist

2008-12-30T16:21:23Z

Steveire: New page: This page is a guide to new contributors on how to create artwork for KDE. ===Dive in === * Paths/Artist/Creating desktop backgrounds * Paths/Artist/Creating themes * [[Paths/Arti...

This page is a guide to new contributors on how to create artwork for KDE.

===Dive in ===
* [[Paths/Artist/Creating desktop backgrounds]]
* [[Paths/Artist/Creating themes]]
* [[Paths/Artist/Creating KDE website designs]]
* [[Paths/Artist/Creating icons]]
* [[Paths/Artist/Creating sounds]]
* [[Paths/Artist/Creating cursors]]
* [[Paths/Artist/Creating logos]]
* [[Paths/Artist/Creating plasma themes]]
* [[Paths/Artist/Putting your art on kde-look]]
* [[Paths/Artist/Finalizing icon SVGZ files]]
* [[Paths/Artist/Using scripts to simplify icon management in SVN]]

===Resources===
* {{KDEML|kde-artists}}
* IRC: oxygen/kde-artists
* Oxygen palette?
* Useful inkscape tutorials?
* icon naming standard
* xdg mailing list
* etc?

Paths/Developer/Development tools and tips

2008-12-30T16:10:49Z

Steveire: New page: == Tools == These should be guides on how to get started with the tools. * Qt Assistant. Run <tt>assistant</tt> from the command line. * [[Development/Tutorials/Debugging/Debugging_with_GD...

== Tools ==
These should be guides on how to get started with the tools.
* Qt Assistant. Run <tt>assistant</tt> from the command line.
* [[Development/Tutorials/Debugging/Debugging_with_GDB|GDB]].
* [[Development/Tools/Valgrind]]

== Tips ==
* Use konqueror shortcuts to navigate to qt and kde classes. For example, type <tt>qt:qtextedit</tt> or <tt>kde:kdialog</tt> into konquerors address bar.

Kdepim

2008-12-30T16:02:38Z

Steveire: Add some resources

Personal information Management suite from the KDE project.

The KDEPIM team develops applications such as Kontact, KMail, KNode, KOrganizer, KAddressbook, Akregator, KJots and others.

To join the team, simply email the {{KDEML|kdepim}} mailing list, and join the irc://freenode.net/kontact irc channel.

Current development focus as of January 2009 is on the Akonadi service and porting existing applications to Akonadi and KMime and other frameworks in KDE4.

=== Resources ===

* http://doc.trolltech.com/4.4/richtext.html - Used for the kmail composer. See also [http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/classKRichTextWidget.html KRichTextWidget].
* http://doc.trolltech.com/4.4/model-view-programming.html - Used throughout kdepim including kmail tree views etc.

* Relevant RFCs?

Paths/Developer/Tour of Qt and KDE frameworks

2008-12-30T15:57:59Z

Steveire:

A knowledge of some of the Qt framework is necessary to understand the KDE framework and design.

Start by exploring the 'Core features' section in the documentation.
http://doc.trolltech.com/4.4/ and the associated [http://doc.trolltech.com/4.4/examples.html Examples].

It is important to note that some of the features of Qt are not used in KDE applications.

* The Qt resource system is not used.
* CMake is used instead of QMake.
* KDE uses the gettext system for translations instead of the Qt tr() system.
* Many Qt classes have KDE subclasses or equivalents which should be used instead. (KFileDialog instead of QFileDialog, KTextEdit instead of QTextEdit). The KDE classes provide greater system integration.
* The KIO system should be used instead of QHttp or QNetworkAccessManager (see also Policies/API_to_Avoid)

[[Development/Architecture/KDE4]]

Paths/Developer/Tour of Qt and KDE frameworks

2008-12-30T15:56:30Z

Steveire: New page: A knowledge of some of the Qt framework is necessary to understand the KDE framework and design. Start by exploring the 'Core features' section in the documentation. http://doc.trolltech....

Paths/Developer/Basics of KDE applications

2008-12-30T15:50:18Z

Steveire: Add more links to material

This series of tutorials introduces the basics of KDE applications in C++. A simple application is built up step by step.

[[Development/Tutorials#Introduction_To_KDE_4_Programming]]

TODO: Find a better way of including these tutorials here.

Also follow the Qt tutorials:
http://doc.trolltech.com/4.4/tutorials.html

Also read up to Chapter 2 in the book [http://www.mindview.net/Books/TICPP/ThinkingInCPP2e.html thinking in c++].

Paths/Developer/How to use CMake

2008-12-30T15:43:49Z

Steveire: New page: Development/Tutorials/CMake Development/CMake

[[Development/Tutorials/CMake]]

[[Development/CMake]]

Kdepim

2008-12-30T15:40:15Z

Steveire: New page: Personal information Management suite from the KDE project. The KDEPIM team develops applications such as Kontact, KMail, KNode, KOrganizer, KAddressbook, Akregator, KJots and others. To...

Paths/Developer/Join a team

2008-12-30T15:35:07Z

Steveire: New page: One of the main benefits of creating software within the KDE community is having a team of other contributors with goals and achievements to work with. The KDE Software Distribution has ma...

One of the main benefits of creating software within the KDE community is having a team of other contributors with goals and achievements to work with.
The KDE Software Distribution has many teams of developers working together to create the applications and workspaces you are familiar with. Joining one of the teams will improve your own skills quicker and make visible improvements in the next KDE release.

[[Build/KDE4]] May be necessary

[[Plasma]]

[[Kdegames]]

[[Kdeedu]]

[[Kdepim]]

[[KOffice]]

[[Amarok]]

[[Kdenetwork]]

[[Kdegraphics]]

[[Kdeutils]]

[[KDevelop]]

Add More?

Others:
Kile etc?

Paths/Developer/Fixing bugs and sending patches

2008-12-30T15:29:36Z

Steveire: New page: Once you have simple kde4 applications compiling, you know you have your development environment set up correctly and you can start fixing bugs. The [https://bugs.kde.org/buglist.cgi?keyw...

Once you have simple kde4 applications compiling, you know you have your development environment set up correctly and you can start fixing bugs.

The [https://bugs.kde.org/buglist.cgi?keywords=junior-jobs&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Junior Jobs] page on bugzilla is a list of bugs that other developers marked as suitable for junior developers to fix. It could make a good starting point for finding bugs to fix. Alternatively you could pick your favorite application and start fixing bugs in it.

The first step is to get the source of the application you need to fix.

TODO:
Rest of instructions

[[Contribute/Send_Patches]]

Paths/Developer/Basics of KDE applications

2008-12-30T15:21:17Z

Steveire: New page: This series of tutorials introduces the basics of KDE applications in C++. A simple application is built up step by step. Development/Tutorials#Introduction_To_KDE_4_Programming TODO...

Contributor Paths

2008-12-30T15:11:20Z

Steveire: New page: This page is a starting point for people who want to become KDE contributors. {{Box|Become a KDE Developer| Start on the Developer path }} {{Box|Become a KDE Artist...

This page is a starting point for people who want to become KDE contributors.

{{Box|Become a KDE Developer|
Start on the [[Paths/Developer|Developer path]]
}}

{{Box|Become a KDE Artist|
Start on the [[Paths/Artist|Artist path]]
}}

{{Box|Become a KDE Documenter|
Start on the [[Paths/Documenter|Documenter path]]
}}

{{Box|Become a KDE Translator|
Start on the [[Paths/Translator|Translator path]]
}}

{{Box|Join the KDE Bugsquad|
Start on the [[Paths/Bugsquad|Bugsquad path]]
}}

{{Box|Join the KDE Usability Team|
Start on the [[Paths/Usability|Usability path]]
}}

{{Box|Join the KDE Promotion Team|
Start on the [[Paths/Promotion|Promotion path]]
}}

{{Box|Join the KDE Websites Team|
Start on the [[Paths/Websites|Websites path]]
}}

Paths

2008-12-30T15:10:48Z

Steveire: Redirecting to Contributor Paths

#REDIRECT [[Contributor Paths]]

Paths/Developer

2008-12-30T15:09:46Z

Steveire: New page: This page is a guide to new KDE contributors who want to create software. There are several entry points to this path. If you are not an experienced developer, but are willing to give it...

This page is a guide to new KDE contributors who want to create software.

There are several entry points to this path. If you are not an experienced
developer, but are willing to give it a try, start at the top. A more
experienced developer could start with the introductory Qt or KDE
tutorials, whereas an experienced C++/Qt developer could skip up to
learning about the Pillars of KDE.

== Dive in ==

:: '''[[Paths/Developer/Creating plasmoids with scripts|Creating plasmoids with scripts]]''' Learn how to create simple plasmoids with QtScript and python. No compiling required.

:: '''[[Paths/Developer/Creating application plugins and scripts|Creating Application plugins and scripts]]''' Learn to create plugins for Kig, koffice, and other KDE applications. No compiling required.

:: '''[[Paths/Developer/Basics of KDE applications|Basics of KDE applications]]''' Learn to create a simple KDE application in C++. This series introduces several aspects of the KDE framework, so would be useful even for seasoned C++ developers to read.

:: '''[[Paths/Developer/Fixing bugs and sending patches|Fixing bugs and sending patches]]''' Once you understand the basics of how kde applications are built, it's time to start improving it.

:: '''[[Paths/Developer/Join a team|Join a team]]''' Work together with other KDE developers. Join the Plasma team! Or the KDE-PIM team! Or the KDE EDU team! Or the KDE Games team! Or ...

:: '''[[Paths/Developer/How to use CMake|How to use CMake]]''' Get to understand the KDE build system and the layout of the KDE Software Distribution and buildsystem

:: '''[[Paths/Developer/Tour of Qt and KDE frameworks|Tour of Qt and KDE frameworks]]''' For greater integration, KDE uses replacements for some Qt modules and classes.

:: '''[[Paths/Developer/Development tools and tips|Development Tools and tips]]''' Learn to use the tools to create KDE software.

:: '''[[Paths/Developer/Writing translatable code|Writing translatable code]]'''

:: '''[[Paths/Developer/Writing API documentation|Writing API documentation]]'''

:: '''[[Paths/Developer/Writing portable Code|Writing portable Code]]'''

:: '''[[Paths/Developer/Getting your application to the users|Getting your application to the users]]''' Put your application on kde-apps.org, or in the official KDE modules.

:: '''[[Paths/Developer/Design patterns|Design patterns]]''' Understanding some of the patterns found in Qt and KDE.

== Resources ==

This is a list of resources to help you along the way to making valuable
contributions to KDE. This is not required reading, or mailing lists you
must subscribe to, but just a list of where to go for help.

=== Links and Documentation ===
* irc://freenode.net/kde-devel - Chat to kde developers in real time.
* {{KDEML|kde-devel}} KDE developers mailing list. This list is for development of KDE applications, while {{KDEML|kde-core-devel}} is for development of the KDE libraries.
* http://doc.trolltech.com/latest/ - Qt API documentation. As all KDE applications use Qt classes, these will become familiar quickly.
* http://api.kde.org - KDE API documentation.
* http://www.qtcentre.org/ - Unofficial website of Qt developers. This is not a KDE website, but another resource for relevant tutorials, [http://www.qtcentre.org/forum/ forum] and [http://wiki.qtcentre.org/ wiki]
* [http://doc.trolltech.com/qq/ Qt Quarterly] - Regularly published usage tips from the Engineers who create Qt.
* [http://lists.trolltech.com/qt-interest/ Qt interest] - Mailing list for the Qt community. Helpful for Qt related issues.
* [http://doc.trolltech.com/4.4/demos.html Qt demos] - Simple uses of individual parts of the Qt framework.
* [http://doc.trolltech.com/4.4/examples.html Qt examples] - Somewhat more complex example uses of Qt.

=== Books ===
* [http://cartan.cas.suffolk.edu/oopdocbook/opensource/ Design patterns in Qt] Free licenced complete book on Qt
* [Foundations of Qt development] By KDE contributor Johan Thelin.
* [http://www.mindview.net/Books/TICPP/ThinkingInCPP2e.html Thinking in c++]
Free licenced book on fundamentals of C++
* [Design Patterns] Gang of Four book describing many object orientated
patterns found in qt/kde
* [Programming pearls] Gain understanding of algorithms
* [[Development/Further_Information]]

Paths/Developer/Creating plasmoids with scripts

2008-12-30T15:09:25Z

Steveire: New page: No tutorials exist here yet. Existing plasma tutorials are c++ focussed. Plasma http://chani.wordpress.com/2008/12/29/adventures-in-plasmaland-part-1/ TODO: Write a series of tutor...

No tutorials exist here yet. Existing plasma tutorials are c++ focussed.

[[Plasma]]

http://chani.wordpress.com/2008/12/29/adventures-in-plasmaland-part-1/

TODO:
Write a series of tutorials using an interpreted language from a hello world label to something more useful.

Apparently there's a plasma clock written in python somewhere. Turn it into a tutorial

Paths/Developer/Creating application plugins and scripts

2008-12-30T15:09:14Z

Steveire: New page: {{:KOffice/Plugin Tutorials}} TODO: Get tutorials together for other applications which support scripting. kig etc.

{{:KOffice/Plugin Tutorials}}

TODO:
Get tutorials together for other applications which support scripting. kig etc.

Development/Tutorials

2008-12-30T15:08:11Z

Steveire:

{{Template:I18n/Language Navigation Bar|Development/Tutorials}}

Tutorials are the fastest way of finding out what KDE will do for you, and how to do it. Here is a list of currently available tutorials '''for KDE4'''. Material for KDE3 and KDE2 is available on the bottom of this page.

== Introduction To KDE 4 Programming ==
Are you interested in writing applications with KDE 4? This tutorial series is aimed at those completely new to KDE programming.
;[[Development/Tutorials/First program|Hello World]]
:''A preliminary introduction to the very basics of KDE4 programming''

;[[Development/Tutorials/Using KXmlGuiWindow|Creating the Main Window]]
:''This tutorial shows you the magic of an application's most important thing: The main window.''

;[[Development/Tutorials/Using KActions|Using KActions]]
:''How to add actions to the menus and toolbars.''

;[[Development/Tutorials/Saving and loading|Saving and Loading]]
:''Introduces the KIO library while adding loading and saving support to our application.''

;[[Development/Tutorials/KCmdLineArgs|Command line arguments]]
:''Adds the ability to specify which file to open from the command line to our text editor.''

== Basics ==
;[[Development/Tutorials/KDE4 Porting Guide|Porting Your Application]]
:''Help Porting Applications from Qt3/KDE3 to Qt4/KDE4''

;[[Development/Tutorials/CMake|Introduction to CMake]]
:''How to use the CMake build system used by KDE4.''

;[[Development/Tutorials/Common Programming Mistakes|Common Programming Mistakes]]
:''Various common mistakes made while developing Qt and KDE applications and how to avoid them.''

;[[Development/Tutorials/Using Qt Designer|Using Qt Designer to build user interfaces]]
:''How to create UI files with designer, and how to integrate them into a KDE program.''

;[[Development/Tutorials/Creating Libraries|Creating Libraries to share code]]
:''How to add the library to the buildsystem and how to prepare the source code.''

== Testing And Debugging ==

;[[Development/Tutorials/Debugging|Debugging your application]]
:''Tips, tools and techniques to apply when debugging your KDE application''

;[[Development/Tutorials/Unittests|Writing Unittests for Qt4 and KDE4 with QTestLib]] ([http://developer.kde.org/documentation/tutorials/writingunittests/writingunittests.html Original link])
:''Tutorial by [mailto:bradh@frogmouth.net Brad Hards] that describes how to write unit tests using the QTestLib framework. It is presented as an example based tutorial, and is still under development.''

;[[Development/Tutorials/Code_Checking|Semi-automatic ways to detect code errors]]
:''Techniques you can use to detect errors in KDE code''

== Managing Configuration Data With KConfig ==
;[[Development/Tutorials/KConfig|Introduction To KConfig]]
:''An overview of the KConfig classes and how to use them in your application code''

;[[Development/Tutorials/Using KConfig XT|Using KConfig XT]]
:''Tutorial on how to efficiently use the KConfig XT framework.''

;[[Development/Tutorials/Updating KConfig Files|Updating KConfig Files]]
:''Tutorial on how to write an update script to keep changes in your application's config file format in sync with the user's already existing config file''

== Services: Applications and Plugins ==
;[[Development/Tutorials/Services/Introduction|Introduction to the Services Framework]]
:''An overview of the services framework in KDE and what it provides the application developer. Covers the system configuration cache (SyCoCa), the source data files and what the indexed information can be used for.''

;[[Development/Tutorials/Services/Traders|Finding Services Using Trader Queries]]
:''How to find services, such as plugins or mimetypes, that are indexed in the SyCoCa using Trader Query Syntax''

;[[Development/Tutorials/Services/Plugins|Creating and Loading Plugins Using KService]]
:''Learn how to define custom plugin types, find installed plugins (including 3rd party plugins) and load them in an easy and portable fashion using KService.''

== Localization ==
See also [[Localization|Localization portal]].

;[[Development/Tutorials/Localization/Unicode|Introduction To Unicode]]
:''An introduction to what Unicode is as well as how to handle Unicode data in KDE applications.''

; [[Development/Tutorials/Localization/i18n|Writing Applications With Localization In Mind]]
:''This tutorial covers what localization is, why it's important and how to ensure your application is ready to be localized. A must read for all application developers.''

; [[Development/Tutorials/Localization/i18n Mistakes|Avoiding Common Localization Pitfalls]]
:''There are several common mistakes that prevent applications from being properly localized. Find out what they are and how to easily avoid them in this tutorial.''

; [[Development/Tutorials/Localization/Building KDE's l10n Module|Building KDE's Localization Module]]
:''Building and installing language support from KDE's localization (l10n) module is a good idea for those working on applications in the main KDE repository. Doing so will allow you to test your application in another language and spot problem areas. Learn how to do just that in this tutorial.''

; [[Development/Tutorials/Localization/i18n Build Systems|Incorporating i18n Into the Build System]]
:''Once your application is ready to be localized, the next step is to ensure that translation files are built automatically and kept up to date. This tutorial covers the necessary CMakeFiles.txt additions as well the process of distributing the resulting message catalogs with your application.''

; [[Development/Tutorials/Localization/i18n Challenges|Common i18n Challenges and Solutions]]
:''This tutorial covers challenges that you may eventually run into such as translating handbooks and other data that exists outside of the source code, merging and handling obsolete .po files, dealing with freezes, coding in languages other than English and creating independent releases of or moving applications between KDE modules.''

; [[Development/Tutorials/Localization/i18n_Semantics|Semantic Markup of Messages]]
:''To ensure consistent presentation and more meaningful representations of messages in applications, semantic markup can be applied to messages marked for translation using the KUIT system. This tutorial describes how this system works.''

; [[Development/Tutorials/Localization/i18n Krazy|Automated i18n Code Checking]]
:''The Krazy code checker scans KDE's code and reports common i18n mistakes.''

== Documentation ==

;[[Development/Tutorials/API_Documentation|API Documentation]]
:''This tutorial explains how to document your APIs properly.''

;[[Development/Tutorials/Man_Pages|Man Pages]]
:''Writing and Generating Reference Manual Pages.''

== Application Automation and Scripting ==

=== D-Bus ===
; [[Development/Tutorials/D-Bus/Introduction|Introduction to D-Bus]]
:''A straight-forward introduction to the core concepts in D-Bus from an application developer's perspective, this tutorial covers what D-Bus is and how it can be used by applications.''
; [[Development/Tutorials/D-Bus/Accessing Interfaces|Accessing D-Bus Interfaces]]
:''A step-by-step guide to calling D-Bus methods and connecting to D-Bus signals using QtDBus.''
; [[Development/Tutorials/D-Bus/Intermediate_D-Bus|Intermediate D-Bus]]
:''Tips to make use of QtDBus when faced with problematic real-world interfaces.''
; [[Development/Tutorials/D-Bus/Creating Interfaces|Creating D-Bus Interfaces]]
:''Learn how to expose functionality in your application by creating and using custom D-Bus interfaces. Covers generating the XML descriptions, instantiating interfaces at run time and setting up the build system with CMake.''
; [[Development/Tutorials/D-Bus/Autostart Services|D-Bus Autostart Services]]
:''Turn your application into a D-Bus autostart service with this tutorial. This D-Bus feature, also known as "D-Bus service activation", will ensure that even when your application isn't running that D-Bus calls made to it will work by relying on the D-Bus daemon itself to start your app if and when needed.''
; [[Development/Tutorials/Porting_to_D-Bus|Porting from DCOP to D-Bus]]
: ''Port your applications from DCOP to D-Bus with this handy guide.''

=== Konqueror ===
; [[Development/Tutorials/Creating Konqueror Service Menus|Creating Konqueror Service Menus]]
:''This tutorial shows you how to create mimetype-specific actions in Konqueror's context menu (aka "servicemenus").''

=== Kross ===
; [[Development/Tutorials/Kross/Introduction|Introduction to Kross]]
:''An introduction to the Kross Scripting Framework.''

; [[Development/Tutorials/Kross/Hello_World|Hello World]]
:''A first application with working kross code.''

; [[Development/Tutorials/Kross/Call_Functions_in_Kross|Calling Functions in Kross]]
:''Simple demonstration of calling scripting functions''

; [[Development/Tutorials/Kross/Connecting_Signals_and_slots_in_Kross|Connecting Signals and Slots in Kross]]
:''Simple demonstration of connecting object signals with script slots''

; [[Development/Tutorials/Kross/Scripts-as-Plugins|Scripts as Plugins with Kross]]
:''This tutorial provides a step-by-step introduction how to integrate scripts as plugins into a KDE application.''

; [[Development/Tutorials/Kross/Scripts-as-KPlugins|Load Kross Scripts as KPlugins]]
:''This tutorial provides a step-by-step introduction how to load scripts as KPlugins.''

; [[Development/Tutorials/Kross/Script-Actions|Placing script actions in your application menus ]]
:''Simple demonstration on how to extend you application menus to execute script files.''

{{:KOffice/Plugin Tutorials}}

=== SuperKaramba ===
; [[Development/Tutorials/SuperKaramba|SuperKaramba Tutorial]]
:''This tutorial provides an overview of SuperKaramba, theme files and scripting with Python, Ruby and JavaScript.''

== Plugins and KParts ==

; [[Development/Tutorials/Writing kontact plugins|Writing kontact plugins]]:''Kontact plugins are KParts. This tutorial describes how you can write one.''

; [[Development/Tutorials/Using KParts|Using KParts]]:''Learn how to load a KPart into an application window.''

== Search and Metadata ==

=== Strigi ===

; [[Development/Tutorials/Writing file analyzers|Writing file analyzers]]
:''File analyzers extract data from files to display in the file dialogs and file managers. The data gathered this way is also used to search for files. KDE4 allows the use of multiple analyzers per file type. This tutorial describes how you can write new analyzers.''

=== [http://nepomuk.kde.org Nepomuk] ===

; [[Development/Tutorials/Metadata/Nepomuk/Quickstart|Nepomuk Quickstart]]
:''How to use Nepomuk resources in a quick and painless way without much fuss.''

; [[Development/Tutorials/Metadata/Nepomuk/RDFIntroduction|RDF and Ontologies in Nepomuk]]
:''An introduction to RDF and the usage of ontologies in Nepomuk.''

; [[Development/Tutorials/Metadata/Nepomuk/Resources|Handling Resources with Nepomuk]]
:''Nepomuk is the KDE library which provides easy access to metadata in the Nepomuk system. Learn how to make your application create and read metadata using the Nepomuk system.''

; [[Development/Tutorials/Metadata/Nepomuk/ResourceGenerator|Using the Nepomuk Resource Generator]]
:''Nepomuk includes a resource generator which creates convenience classes for handling metadata.''

; [[Development/Tutorials/Metadata/Nepomuk/AdvancedQueries|Advanced Queries]]
:''The real power of Nepomuk can only be exposed when performing fancy queries on the data repository. This tutorial provides an introduction to semantic and full text queries in Nepomuk.''

; [[Development/Tutorials/Metadata/Nepomuk/NepomukServer|The Nepomuk Server and the Architecture of the Nepomuk subsystem]]
:''The Nepomuk Server hosts the main Nepomuk data repository and can be accessed directly via a Soprano API.''

; [[Development/Tutorials/Metadata/Nepomuk/NepomukServices|Nepomuk Services]]
:''The Nepomuk Server manages a set of Nepomuk services.''
:* [[Development/Tutorials/Metadata/Nepomuk/StorageService|Storage Service]] ''The probably most important service hosts the Nepomuk data repository using [http://soprano.sourceforge.net Soprano].''
:* [[Development/Tutorials/Metadata/Nepomuk/OntologyLoaderService|Ontology Loader]] ''Makes sure installed ontologies such as RDF, RDFS, NRL, or Xesam are loaded into the storage repository.''
:* [[Development/Tutorials/Metadata/Nepomuk/FileWatchService|File Watch Service]] ''Monitors the file system for changes and updates the file resource paths and URIs in Nepomuk.''
:* [[Development/Tutorials/Metadata/Nepomuk/StrigiService|Strigi Service]] ''Controls Strigi, the file indexing tool which extracts metadata from files and stores it into the storage repository.''
:* [[Development/Tutorials/Metadata/Nepomuk/QueryService|Query Service]] ''Provides persistant query folders.''

== Hardware Awareness (Solid) ==

;[[Development/Tutorials/Solid_Tutorials|Introduction to Solid]]
:''An introduction to using the Solid hardware discovery and interaction system in KDE applications.''

;[[Development/Tutorials/Solid_Network_Tutorial|Accessing Network Information]]
:''How to use the Solid system to get information about the network''

== Multimedia (Phonon) ==

;[[Development/Tutorials/Phonon/Introduction|Phonon]]
:''How to start with the multimedia API''

:''How to compile and use Phonon and its GStreamer backend on Linux using Qt 4.3.x''
::''This article gives you a quick brief of how you can use checkout, compile Phonon and its GStreamer backend on GNU/Linux with just Qt 4.3.x. Towards the end, the article also describes how a developer can make use of Phonon to create simple audio and video players. You can read the article [http://www.vcreatelogic.com/oss/docs/CompilingPhononOnLinux.pdf here]. You can download the editable OpenDocumentText file from [http://www.prashanthudupa.com/phonon/CompilingPhononOnLinux.odt here].''

== Plasma ==

;[[Development/Tutorials/Plasma/GettingStarted|Getting Started With Plasmoids]]
:''Creating your first Plasma widget, or Plasmoid, in C++ with an SVG background, an icon and some text''

;[[Development/Tutorials/Plasma/DataEngines|Writing A DataEngine]]
:''DataEngines provide a [http://api.kde.org/4.x-api/kdebase-workspace-apidocs/plasma/html/classPlasma_1_1DataEngine.html standardized interface] to various data sources for visualizations to use. Learn what a DataEngine is and how to write one of your own.''

;[[Development/Tutorials/Plasma/UsingDataEngines|Using DataEngines in Plasmoids]]
:''With a DataEngine, it is possible to retrieve data for display in a simple and standard way. This tutorial covers the topic of how to use DataEngines for this purpose in Plasmoids.''

;[[Development/Tutorials/Plasma/AbstractRunner|Creating Runners]]
:''Runners are plugins that provide action-based search functionality in the Plasma workspace "run command" dialog. These plugins can be used by any application that links again libplasma.''

;[[Development/Tutorials/Plasma/Theme|Creating a Plasma Theme]]
:''Guide to creating your first Plasma theme.''

;[[Development/Tutorials/Plasma/UsingExtenders|Using Extenders]]
:''This guide shows you how to create a simple applet (a stripped down kuiserver applet) that uses extenders.''

== Communication (Decibel) ==

;[[Development/Tutorials/Decibel/GettingStarted|Getting started with Decibel]]
:''This tutorial describes how to set up Decibel.''

;[[Development/Tutorials/Decibel/Handling_TextChannels|Handling TextChannels]]
:''This tutorial introduces the basics of handling incoming TextChannels by guiding you through building a simple text chat application.''

== Personal Information Management (Akonadi) ==

;[[Development/Tutorials/Akonadi/Resources|Developing Akonadi Resources]]
:''Akonadi Resources are agent programs which transport PIM data between Akonadi and a backend (files, servers, etc)''

== Kate / Kwrite ==

;[[Development/Tutorials/Kate/KTextEditor Plugins|Getting started with KTextEditor plugins]]
:''Creating your first KTextEditor plugin''

;[[Development/Tutorials/Kate/KTextEditor_Plugins_Advanced|Developing a plugin with configuration dialog]]
:''Adding a configuration dialog to the Time & Date example''

;[[Development/Tutorials/Kate/KTextEditor_Example|A small Editor]]
:''Create a small application using KTextEditor''

==Printing==

;[[Development/Tutorials/Printing Hello World|Hello World]]
:''Introduction to the KDE printing system''

;[[Development/Tutorials/Printing Print Dialog|Print Dialog]]
:''Using the KDE print dialog''

== kioslaves ==
* [[Development/Tutorials/KIO Slaves/Using KIO Slaves in your Program|Using kioslaves in your Program]]
* [[Development/Tutorials/KIO Slaves/Hello World|Creating a Hello-World kioslave]]

== Get Hot New Stuff ==
; [[Development/Tutorials/K_Hot_New_Stuff2|New introduction to Get Hot New Stuff 2]]
:''A short tutorial about how to use KHotNewStuff2 in your application.''

* old links for KNS1 content:
; [[Development/Tutorials/Introduction to Get Hot New Stuff|Introduction to Get Hot New Stuff]]
:''An introduction to the developer-friendly network update system that allows KDE applications to fetch new application data at runtime in a user friendly manner.''

;[[Development/Tutorials/KNewStuffSecure|KNewStuff Secure]] ([http://developer.kde.org/documentation/tutorials/knewstuffsecure/index.html Original Link])
:''Tutorial showing how to share resources in a secured way (KDE 3.4 and later).'' By András Mantia <amantia@kde.org>.

== Goya ==
; [[Development/Tutorials/Introduction to Goya usage|Introduction to Goya usage]]
:''An introduction for the Goya subsystem usage, which allows you to easily add widgets to your itemviews and connect their signals to your code, as they were real widgets.''

; [[Development/Tutorials/Introduction to Goya usage 2|Introduction to Goya usage (part 2)]]
:''The second part of the tutorial, with a slightly more complex example than the first part.''

== Other programming languages ==

=== Python ===

;[[Development/Tutorials/Python introduction to signals and slots|101 Introduction to signals and slots]]
:''A simple introduction to Qt's signal and slot architecture.''

;[[Development/Languages/Python/PyKDE_WebKit_Tutorial|PyKDE WebKit Tutorial]]
:''A simple web browser application in PyKDE''

=== Ruby ===

;[http://developer.kde.org/language-bindings/ruby/kde3tutorial/index.html KDE Ruby Korundum tutorial]
:''A ruby version of Antonio Larrosa Jiménez's KDE tutorial by Richard Dale. See the [http://developer.kde.org/language-bindings/ruby/index.html Ruby Developers Corner] for Qt tutorials and other info.''

;[[Development/Tutorials/Qt4_Ruby_Tutorial|Qt4 Ruby Tutorial]]
:''Trolltech's fabulous introductory tutorial to Qt, translated to Ruby.''

;[[Development/Tutorials/Plasma/RubyApplet|Creating a Plasma Widget in Ruby]]
:''Tutorial that shows how to create your first Plasma Applet using the Ruby language.''

=== Shell ===

;[[Development/Tutorials/Shell_Scripting_with_KDE_Dialogs|Shell Scripting with KDE dialogs]] ([http://developer.kde.org/documentation/tutorials/kdialog/t1.html Original Link])
:''Tutorial by [mailto:bradh@frogmouth.net Brad Hards] that describes how to use KDE dialogs in shell scripts with kdialog. It is presented as an example based tutorial.''

== Graphics Programming ==

;[[Development/Tutorials/Graphics/Performance|QPainter Perfomance]]
:''Hints on avoiding common mistakes leading to poor performance when using QPainter''

== Using the KDE Games Libraries ==
;[[Development/Tutorials/Games/KStandardGameAction| KStandardGameAction]]
:''Using libkdegames to make your game fit the kdegames standard''
;[[Development/Tutorials/Games/Highscores| Highscores]]
:''Implementing a simple highscore table into your game''
;[[Development/Tutorials/Games/Theme Selector| Theme Selector]]
:''Using the libkdegames theme selection dialog''
;[[Development/Tutorials/Games/Palapeli Patterns| Palapeli Patterns]]
:''Creating a pattern for Palapeli''
;[[Development/Tutorials/Games/KGLEngine2d| KGLEngine2d]]
:''Using KGLEngine2d for 2D games development''

== Using the KDE PIM Libraries ==
;[[Development/Tutorials/PIM/ical| iCalendar functionality]]
:''Using kcal to manage iCalendar files''

== Other tutorials ==

=== 2D Plotting (KPlotWidget) ===
;[[Development/Tutorials/KPlotWidget|Using the KDE data-plotting widget]]
:''This tutorial introduces KPlotWidget, which is used for 2-D data plotting. It includes information on simple usage of the widget (including adding and modifying data sets, and customizing the plot axes and labels), and advanced customization (including extending the widget through sub-classing).''

=== Spelling and Grammar Checking (Sonnet) ===
;[[Development/Tutorials/Sonnet/SonnetTutorial|Adding spell-checking or grammar-checking to KDE applications]]
:''This tutorial introduces Sonnet and how one may use it to add language correction to your KDE application. Sonnet's auxiliary features shall be described in a separate tutorial.''

=== Pixmap cache (KPixmapCache) ===
;[[Development/Tutorials/KPixmapCache|Using the KDE pixmap cache]]
:''This tutorial shows how to use KPixmapCache to cache e.g. pixmaps generated from SVGs or some data.''

=== Using MarbleWidget (Marble) ===
;[[Development/Tutorials/MarbleWidget|Using MarbleWidget]]
:''This short tutorial describes how to use the MarbleWidget in your project''

=== Using local SCM for KDE development ===
;[[Development/Tutorials/Git|Using Git to develop for KDE]]
:''This tutorial shows how to use Git to develop for KDE''

=== Implementing KSysGuard sensors and adding them ===
;[[Development/Tutorials/Sensors]]
:''This tutorial shows how to write and KSysGuard sensor and connect it to the systray.''

== KDE2 and KDE3 Materials ==

;[[Development/Tutorials/KDE3|KDE3 Tutorials]]
:''These tutorials cover topics related to KDE3.''

;[[Development/Tutorials/KDE2|KDE2 Tutorials]]
:''These tutorials cover topics related to KDE2.''

[[Category:KDE4]]

Projects/KOffice

2008-12-30T15:06:54Z

Steveire: New page: KOffice is the document processing suite from the KDE project. http://koffice.org/ {{:KOffice/Plugin Tutorials}}

KOffice is the document processing suite from the KDE project.

http://koffice.org/

{{:KOffice/Plugin Tutorials}}

Projects/KOffice/Plugin Tutorials

2008-12-30T15:06:35Z

Steveire: KOffice/Development Tutorials moved to KOffice/Plugin Tutorials

=== KOffice Plugin Tutorials ===

; [[Development/Tutorials/KOffice Overview|KOffice Overview]]
:''This document shows an overview of the different KOffice plugin types and tells you what each of their purpose and strengths are.'' If you are new with KOffice plugins, this is the place to start.

; [[Development/Tutorials/Write a Flake Plugin|Creating KOffice Flake Plugins]]
:''This tutorial shows you how you can build a plugin for KOffice applications to allow you embed content in ODF documents using Flake.''

; [[Development/Tutorials/KWord Scripting|KWord Scripting]]
:''This tutorial shows how to script KWord with Python, Ruby or JavaScript using Kross.''

; [[Development/Tutorials/KSpread Scripting|KSpread Scripting]]
:''This tutorial shows how to script KSpread with Python, Ruby or JavaScript using Kross.''

; [[Development/Tutorials/Krita Scripting|Krita Scripting]]
:''This tutorial shows how to script Krita with Python, Ruby or JavaScript using Kross.''

Projects/KOffice/Development Tutorials

2008-12-30T15:06:35Z

Steveire: KOffice/Development Tutorials moved to KOffice/Plugin Tutorials

#REDIRECT [[KOffice/Plugin Tutorials]]

Projects/KOffice/Plugin Tutorials

2008-12-30T15:06:15Z

Steveire: New page: === KOffice Plugin Tutorials === ; KOffice Overview :''This document shows an overview of the different KOffice plugin types and tells you what ...

Projects/Contributor Paths

2008-12-29T15:27:44Z

Steveire: Add some boxes.

This is a temporary page to hold information about creating techbase pages for contributor paths. The idea is to reorganize the tutorials already present on techbase into categories to teach new people to contribute. The focus is on lowering the barrier to entry, and identifying gaps in the techbase tutorials.

The original thread is here:
http://thread.gmane.org/gmane.comp.kde.devel.core/55248

What I'm looking for is
* '''Consensus''' - Is this a good idea and something we want?
* '''Correctness''' - As I know nothing about artists work, I don't know if creating icons is harder than creating themes, and I don't know if the steps in the path are correct. Similar for the others (docs, translation, etc)
* '''Collaboration''' - Will you help fill the gaps in the techbase documentation?

== Followups here ==
* [http://thread.gmane.org/gmane.comp.kde.devel.general/56132 Developer]
* [http://thread.gmane.org/gmane.comp.kde.artists/5582 Artist]
* [http://thread.gmane.org/gmane.comp.kde.devel.internationalization-and-documentation/15942 Documenter]
* [http://thread.gmane.org/gmane.comp.kde.devel.internationalization-and-documentation/15941 Translator]
* Bugsquad - [ link]
* [http://lists.kde.org/?l=kde-usability&m=123056383919172&w=2 Usability Team]
* [http://lists.kde.org/?l=kde-promo&m=123056251917223&w=2 Promotion Team]
* [http://thread.gmane.org/gmane.comp.kde.www/355 Websites Team]

== Draft of 'root' page ==
Box is a bad template to use for this stuff. We can do a lot better, but you get the idea

***********

This page is a starting point for people who want to become KDE contributors.

{{Box|Become a KDE Developer|
Start on the [[:/Paths/Developer|Developer path]]
}}

{{Box|Become a KDE Artist|
Start on the [[:/Paths/Artist|Artist path]]
}}

{{Box|Become a KDE Documenter|
Start on the [[:/Paths/Documenter|Documenter path]]
}}

{{Box|Become a KDE Translator|
Start on the [[:/Paths/Translator|Translator path]]
}}

{{Box|Join the KDE Bugsquad|
Start on the [[:/Paths/Bugsquad|Bugsquad path]]
}}

{{Box|Join the KDE Usability Team|
Start on the [[:/Paths/Usability|Usability path]]
}}

{{Box|Join the KDE Promotion Team|
Start on the [[:/Paths/Promotion|Promotion path]]
}}

{{Box|Join the KDE Websites Team|
Start on the [[:/Paths/Websites|Websites path]]
}}

Projects/Contributor Paths

2008-12-29T15:24:13Z

Steveire:

Projects/Contributor Paths

2008-12-29T15:12:58Z

Steveire: Update with some links

Projects/Contributor Paths

2008-12-29T14:26:11Z

Steveire: New page: This is a temporary page to hold information about creating techbase pages for contributor paths. The idea is to reorganize the tutorials already present on techbase into categories to tea...

Schedules/KDE4/4.2 Feature Plan

2008-11-09T16:33:56Z

Steveire: /* kdepim */ Import knowit files for KJots done.

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

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

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|System Settings|add Administrator mode button|alediaferia@gmail.com|Alessandro Diaferia}}
{{FeatureTodo|PolicyKit integration|Add PolicyKit support for KDE|drf54321@gmail.com|Dario Freddi}}
{{FeatureTodo|KPackageKit|Pushing in KPackageKit (dependant on PolicyKit integration)|dantti85-dev@yahoo.com.br|Daniel}}
{{FeatureDone|Eigen|Make Eigen 2 ready for KDE, and move it to kdesupport|jacob@math.jussieu.fr|Benoît Jacob}}
{{FeatureInProgress|Eigen|Port all Eigen-using code in KDE and KOffice to Eigen 2.0|jacob@math.jussieu.fr|Benoît Jacob}}
{{FeatureInProgress|KNotify|Create OSD based replacement for current KPassivePopup|ben()eclipse.endoftheinternet.org|Ben Cooksley}}
{{FeatureTodo|Dikku Context Framework|Create a context framework with working activities|harikrishna.anandhan@gmail.com|Harikrishna Anandhan}}
{{FeatureDone|kwrited|Use knotify in kwrited|gkiagiad@csd.uoc.gr|George Kiagiadakis}}
{{FeatureInProgress|Akonadi|Various Akonadi related items can be found here http://techbase.kde.org/Projects/PIM/Akonadi#Scheduled_for_4.2|kde-pim@kde.org|Akonadi Developers}}
{{FeatureTodo|Printer Admin|KDEPrint is dead, long live system-config-printer-kde (kdeadmin) and printer-applet (kdeutils)! Thanks to jriddell for these. Restore feature parity in user interfaces where possible.|john@layt.net|john Layt}}
|}

= 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
{{FeatureInProgress|kross|Extend QtScript integration.|mail@dipe.org|Sebastian Sauer}}
{{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|KDEPrint|*Defer to 4.3* Migrate FilePrinter class from Okular to enable file printing for all apps via QPrinter, modify to utilise new Qt4.4 features. To be discussed on k-c-d first.|john@layt.net|John Layt}}
{{FeatureTodo|KCalenderSystem|*Defer to 4.3* Add new calendar systems: Indian Civil (Saka), Ethiopean, Chinese, Pure Julian, Pure Gregorian. (Note, not all may live in kdelibs or be available as a global calendar system)|john@layt.net|John Layt}}
{{FeatureInProgress|KLocale|Implement KLocale based methods to return working week start and end days and day of religious observance. Currently KCalendarSystem provides dayOfPray(), but for Gregorian this is not correct in all locales where it is used. Currently KDatePicker hardcodes Saturday and dayOfPray() as weekend days which may not be correct in all locales. To be discussed first on k-c-d and with kdepim.|john@layt.net|John Layt}}
{{FeatureTodo|Phonon|add Port class for fine grained control over data flow between Phonon objects|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|make AbstractMediaStream/StreamInterface threadsafe|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|"low-level" PCM I/O with at least an ALSA implementation|kretz@kde.org|Matthias Kretz and Ian Monroe}}
{{FeatureInProgress|Phonon|VideoWidget snapshot function|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|KConfig|API review and export KConfigBackend|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|KConfig|Make KConfigSkeleton KConfigGroup aware|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|KConfig|Make KConfigDialog work nicer with KConfigSkeleton + manually managed widgets|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|KUrlNavigator|Provide an option to always show the full path in the breadcrumb mode.|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|Katepart|Make a Vi input mode for Katepart|ehamberg@gmail.com|Erlend Hamberg}}
{{FeatureTodo|KIO::Global|Make KDynamicJobTracker do the checking if the kuiserver service is registered or not, for full implementation of "Progress in the same window"|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureTodo|KJS|Further performance improvements, in particular variable access (Blizzard stage 2), calling convention (FrostByte stage 2) and object property model improvements|maksim@kde.org|Maksim Orlovich}}
{{FeatureInProgress|KJS and KHTML|Support for transparent reindenting of standalone sources in debugger, debug info management improvements, DOM/CSS inspection|maksim@kde.org|Maksim Orlovich}}
{{FeatureInProgress|KHTML|SVG support in KHTML (port from WebKit)|tsjoker@gmail.com|Vyacheslav Tokarev}}
{{FeatureDone|KHTML|Use of IDString (hashed strings) for local names, prefixes and namespaces in DOM core instead of document-related ids, in particular for better API compatibility with WebCore|tsjoker@gmail.com|Vyacheslav Tokarev}}
{{FeatureInProgress|KHTML|String optimizations. Class style selector performance improvement. DOMString API extension.|tsjoker@gmail.com|Vyacheslav Tokarev}}
{{FeatureTodo|KHTML|More automation in JS/C++ bindings generation|maksim@kde.org|Maksim Orlovich and Vyacheslav Tokarev}}
{{FeatureTodo|KHTML|XPath level 1|maksim@kde.org|Maksim Orlovich}}
{{FeatureTodo|KHTML|Scriptable extension plug-ins|porten@kde.org|Harri}}
{{FeatureTodo|KHTML|Gaussian SVG filter|fredrik@kde.org|Fredrik Höglund}}
{{FeatureTodo|KHTML|Support for CSS3 border-* properties|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|KHTML|Finish support of Video/Audio elements|germain@ebooksfrance.org|Germain Garand}}
{{FeatureInProgress|KHTML|Early domain name resolution (prefetch)|germain@ebooksfrance.org|Germain Garand}}
{{FeatureInProgress|KHTML|KHTMLFindBar - an embedded search/find-as-you-type bar|bbeschow@cs.tu-berlin.de|Bernhard Beschow}}
{{FeatureTodo|KHTML|Faster page cache|germain@ebooksfrance.org|Germain Garand}}
{{FeatureDone|kwallet|Move kwalletd to kdebase-runtime|dfaure@kde.org|David Faure}}
{{FeatureInProgress|kdeui|Rich text builders for KTextEdit, including BBCode, html, plain text markup, mediawiki and markdown output.|steveire@gmail.com| Stephen Kelly}}
{{FeatureDone|i18n|proper filenames decoding for FAT mounting, in KUrls and content-disposition|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureDone|Kross|expose KAssistantDialog as part of forms module|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureTodo|KLocale|Method to strip accelerator marker from UI strings; needs to take into account CJK-style markers too.|caslav.ilic@gmx.net|Chusslove Illich}}
{{FeatureInProgress|KStyle|New branch style for treeviews|fredrik@kde.org|Fredrik Höglund}}
{{FeatureTodo|kdeui|entries to help menu and aboutdata pointing to UserBase entry and forum.kde.org|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureInProgress|CMake|Reduced library link interface|neundorf@kde.org|Alexander Neundorf}}
{{FeatureTodo|CMake|Exporting and importing (library) targets|neundorf@kde.org|Alexander Neundorf}}
|}

= 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
{{FeatureTodo|Color KCM|Add 'smart setting' of extended colors|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|Color KCM|Add KDE3 scheme import|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|Color KCM|Query kwin for supported colors; add full set of kwin colors|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureDone|Power Manager|import PowerDevil|drf@kdemod.ath.cx|Dario Freddi}}
{{FeatureTodo|Font Installer KCM|Use PolicyKit for installtion of system-wide fonts.|craig@kde.org|Craig Drummond}}
{{FeatureInProgress|Kephal|Import kephal for better xrandr-support.|dev@aikesommer.name|Aike Sommer}}
{{FeatureInProgress|ConsoleKit support|Add ConsoleKit support to kdm.|kkofler@fedoraproject.org|Kevin Kofler}}
|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |KRunner
{{FeatureInProgress|Krunner|Configuration options for blacklisting, user ranking, runner ranking, learning|mumismo@gmail.com|Jordi Polo}}
{{FeatureInProgress|Krunner|SearchMatch configuration|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Krunner|Simple learning|mumismo@gmail.com|Jordi Polo}}
{{FeatureTodo|Krunner|Simple GUI for above options|mumismo@gmail.com|Jordi Polo}}
{{FeatureTodo|Krunner|Runners able to share parsing|mumismo@gmail.com|Jordi Polo}}
{{FeatureTodo|Krunner|Noun-Verb support|ryan.bitanga@gmail.com|Ryan P. Bitanga}}
{{FeatureTodo|Krunner|Implement Nuno's UI polishings|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Krunner|Runtime syntax documentation|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Krunner|Runner configuration|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Krunner|Search set paging|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|KRunner|runner for the plasma dbus interface|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|KRunner|Konqueror history runner|sebas@kde.org|Sebastian Kügler}}
{{FeatureDone|KRunner|Kate sessions runner|sebas@kde.org|Sebastian Kügler}}
{{FeatureDone|KRunner|Recent Documents runner|sebas@kde.org|Sebastian Kügler}}
|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |Plasma - Priority Features
{{FeatureTodo|Plasma|Welcome plasmoid|aseigo@kde.org|Aaron Seigo}}{{FeatureInProgress|Plasma|JOLIE Integration|ervin@kde.org|Kevin Ottens}}
{{FeatureInProgress|Plasma|Notification plasmoid|dimsuzkde@gmail.com|Dmitry Suzdalev}}
{{FeatureInProgress|Plasma|Kuiserver plasmoid|r.scheepmaker@student.utwente.nl|Rob Scheepmaker}}
{{FeatureTodo|KWin|Make it possible to focus plasma panels|chanika@gmail.com|Chani}}
{{FeatureTodo|Plasma|panel->desktop dragging|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Expand cashew to full action bar when zoomed out|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|Plasmagik packaging (and package classes)|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureDone|Plasma|Improved Battery applet for Powerdevil|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|Plasma|Networkmanager Plasmoid and DataEngine|cblauvelt@gmail.com|Christopher Blauvelt}}
{{FeatureInProgress|Plasma|New ECMA Script Scriptengines|richmoore44@gmail.com|Richard Moore}}
{{FeatureDone|Plasma|Extenders|r.scheepmaker@student.utwente.nl|Rob Scheepmaker}}
{{FeatureDone|Plasma|Wallpaper plugins|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|Separate Desktop Settings from DesktopContainment|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Script Security Framework|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|Python support|simon@simonzone.com|Simon Edwards}}
|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |Plasma
{{FeatureDone|Plasma|Plasma Popup Tips|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|Collapsing Applet convenience class|aseigo@kde.org|Aaron Seigo}}

{{FeatureInProgress|Plasma|Taskbar grouping|hrigi_1@hotmail.com|Christian Mollekopf}}
{{FeatureInProgress|Plasma|Weather plasmoid|shawn.starr@rogers.com|Shawn Starr}}
{{FeatureInProgress|Plasma|Small Form Factors|m.kruisselbrink@student.tue.nl|Marijn Kruisselbrink}}
{{FeatureDone|Plasma|Plasma On Screensaver|chanika@gmail.com|Chani Armitage}}
{{FeatureInProgress|Plasma|Website update|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|Grid applet|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|Plasma|Techbase Tutorials|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Context menu plugins|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Add New Widgets: Pluggable widget browser|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Activity<->Virtual Desktop Affinity|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Optional Per-Virtual Desktop DesktopView|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Make non-SVG painting in Plasma low-color and non-anim friendly|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Runtime DataEngine documentation (sources, usage, etc)|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|Panel Autohide|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Keyboard Shortcut Config UI|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Systray++ Spec|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|Save icon positioning in folderview|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|New wallpapers|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|Import Raptor|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureInProgress|Plasma|Quicklaunch Plasmoid|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureTodo|Plasma|Preserve wallpaper choice by copying user paper to home dir|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|New way of handling wallpapers and different sizes (package format, and so on...)|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|Top-level windows plasmoids|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|drop indicator in panel|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|improve usability of appletbrowser delete button|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|adding containments from the appletbrowser (and remove the "add panel" from DefaultDeskrop)|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|highlight the applet with active keyboard shortcuts|chanika@gmail.com|Chani}}
{{FeatureTodo|Plasma|dbus interface|chanika@gmail.com|Chani}}
{{FeatureDone|Plasma|make the panel controller a bit more usable|notmart@gmail.com|Marco Martin}}
{{FeatureDone|Plasma|nicely draw the desktop toolbox when it's moved because of a panel|notmart@gmail.com|Marco Martin}}
{{FeatureDone|Plasma|theme Plasma::PushButton with svg|notmart@gmail.com|Marco Martin}}
{{FeatureDone|Plasma|Tabbar widget derived from QTabBar and themed with svg|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|Complete the panel size sliders feature: an applet can ask the panel to resize|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|New theming capabilities by expanding the lower level theming classes (Theme and PanelSvg)|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|Activitybar: an applet to quickly switch between activities|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|A new plasmoid that implements the functionality of a simple web browser|notmart@gmail.com|Marco Martin}}
{{FeatureTodo|Plasma|Visual clue when dragging applets from applet browser to the panel|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|Wallpaper plugin: Mandelbrot fractal explorer|jacob@math.jussieu.fr|Benoît Jacob}}
{{FeatureDone|Plasma|Google Gadgets support|idlecat511@gmail.com|Tiger Dong}}
{{FeatureDone|Plasma|Add Google Gadgets from Internet through AppletBrowser|idlecat511@gmail.com|Tiger Dong}}
{{FeatureTodo|Plasma|Panel form factor support in the folderview applet|fredrik@kde.org|Fredrik Höglund}}
{{FeatureTodo|Plasma|Support for creating applets for dropped URLs in the folderview applet when it's acting as a containment|fredrik@kde.org|Fredrik Höglund}}
{{FeatureInProgress|Plasma|Add a places combo box to the location page in the folderview config dialog|fredrik@kde.org|Fredrik Höglund}}
|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |KWin - Core
{{FeatureDone|KWin|New window snapping zones; screen center and window corners|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureDone|KWin|Move maximized windows between Xinerama screens|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureDone|KWin|Support for decoration shadows|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureTodo|KWin|Implement [http://standards.freedesktop.org/wm-spec/wm-spec-latest.html#id2552578 _NET_WM_FULLSCREEN_MONITORS] EWMH spec hint|vR@movingparts.net|Jason 'vanRijn' Kasper}}
|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |KWin - Desktop Effects
{{FeatureDone|KWin|Compositing self-check|l.lunak@kde.org|Luboš Luňák}}
{{FeatureDone|KWin|Global animation speed setting|l.lunak@kde.org|Luboš Luňák}}
{{FeatureDone|KWin|Motion dynamics|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureDone|KWin|Improved UI for selecting window/desktop switcher|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KWin|UI for assigning effects to screen edges|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KWin|Cube/cylinder/sphere effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KWin|Magic lamp minimize effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KWin|Animation in box switch effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|KWin|Mouse interaction for cover switch Effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|KWin|Thumbnail bar in the cover switch effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KWin|Improved snow effect; Different sizes, better randomness and different directions|torgny.johansson@gmail.com|Torgny Johansson}}
{{FeatureTodo|KWin|Shader for snow effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KWin|Improved desktop grid|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureDone|KWin|New present window layout modes|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureDone|KWin|Invert only selected windows|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
{{FeatureDone|KCal Library|Make the KCal library dependent on the external libical package (from freeassocation) rather than our own old, forked version.|winter@kde.org|Allen Winter}}
|}

= 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|MSNP15 implementation for MSN|mattr@kde.org|Matt Rogers}}
{{FeatureInProgress|Kopete|UPnp Support|mattr@kde.org|Matt Rogers}}
{{FeatureInProgress|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}}
{{FeatureInProgress|Kopete|Contacts plasmoid|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Kopete|Move file transfer request into chat window|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureDone|Kopete|Message delivery notifications|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureDone|Kopete|Improve file transfer progress dialog|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureInProgress|Kopete|Jabber Jingle Audio support|detlev.casanova@gmail.com|Detlev Casanova}}
{{FeatureInProgress|KGet|MultiSource-Downloading|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureInProgress|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|Plasma|Network Manager Applet|cblauvelt@gmail.com|Christopher Blauvelt}}
{{FeatureInProgress|KRDC|NX support|gdavid.devel@gmail.com|David Gross}}
{{FeatureDone|KRDC|Greatly improve experience for LDAP (e.g. MS Active Directory) administrators|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|KRDC|Improve per-host settings (remember scaling mode and other options) |gpothier@gmail.com|Guillaume Pothier}}
{{FeatureTodo|KRDC|Minimal-clutter mode to optimize screen real estate usage|gpothier@gmail.com|Guillaume Pothier}}
|}

= 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
{{FeatureDone|KonsoleKalendar|Add an option to support resources that might need a GUI (i.e. all resources)|kevin.krammer@gmx.at|Kevin Krammer}}
{{FeatureInProgress|Akregator|Support for syncing the feed list with Google Reader |osterfeld@kde.org|Frank Osterfeld}}
{{FeatureInProgress|KAlarm|Improve alarm edit and preferences dialog layouts|djarvie@kde.org|David Jarvie}}
{{FeatureInProgress|KAlarm|Add holidays support|djarvie@kde.org|David Jarvie}}
{{FeatureInProgress|Kleopatra|OpenPGP support|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureInProgress|KNotes|Zeroconf support for sending notes on LAN|qbast@go2.pl|Jakub Stachowski}}
{{FeatureDone|Kontact|New Planner summary; combines Appointment+To-do+SpecialDates into 1 pretty summary|o_timocin@gmx.de|Oral Timocin}}
{{FeatureDone|Akregator|Basic support for enclosures (Displaying links, mimetype and size)|osterfeld@kde.org|Frank Osterfeld}}
{{FeatureTodo|[http://kblogger.pwsp.net KBlogger]|KBlogger, a blogging application|christian_weilbach@.web.de|Christian Weilbach}}
{{FeatureTodo|Kleopatra|Konqueror and Dolphin Kleopatra plugins|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureDone|KMail|Aggregated attachment view in the mail header area of the reader window|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Merge the new message list from the SoC branch|mcguire@kde.org|Thomas McGuire}}
{{FeatureTodo|KMail|Save metadata about attachments to Nepomuk when saving them|onurf@su.sabanciuniv.edu|Ismail Onur Filiz}}
{{FeatureTodo|Kontact|Support for Kontact wide profiles|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Drag and drop in the free-busy view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Support for comments in replies to invitations|kdepim@kdab.net|Kolab Konsortium}}
{{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}}
{{FeatureTodo|KBlogger|Port to use KRichTextEdit (Or KMEditor)|steveire@gmail.com|Stephen Kelly}}
{{FeatureTodo|KNode|Port to use KRichTextEdit (Or KMEditor)|steveire@gmail.com|Stephen Kelly}}
{{FeatureDone|Kjots| Import notes from KnowIt as KJots pages. |steveire@gmail.com|Stephen Kelly}}
{{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}}
{{FeatureTodo|Kontact|Tip-of-the-Day summary|molkentin@kde.org|Daniel Molkentin}}
{{FeatureInProgress|Akonadi|Migration of contacts and calendar data from KResource to Akonadi ([http://techbase.kde.org/Projects/PIM/Akonadi#Scheduled_for_4.2 Details])||Volker Krause, Kevin Krammer, Tobias Koenig}}
|}

= 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
{{FeatureDone|Okteta|rework Decoding table, add int64 and UTF-8|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|refactor KByteArrayView and add a row-oriented view|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{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|work on Tabs: add remove button, make Tab buddy of view, accept drop of url as load command|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|parameter dialog for "Copy as..."|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 a document info tool(view)|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|Add option to expand selection in Goto dialog|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureInProgress|Ark|Implement proper drag/drop between Ark/dolphin|haraldhv((at))stud(dot)ntnu.no|Harald Hvaal}}
{{FeatureDone|Ark|Make the service menu work (possibly doing it as a KonqPopupPlugin|haraldhv((at))stud(dot)ntnu.no|Harald Hvaal}}
{{FeatureDone|Ark|Proper password support|haraldhv((at))stud(dot)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((at))stud(dot)ntnu.no|Harald Hvaal}}
{{FeatureInProgress|Ark|Implement a plugin for .gz files|haraldhv((at))stud(dot)ntnu.no|Harald Hvaal}}
{{FeatureTodo|Ark|Add an options dialog (maybe)|haraldhv((at))stud(dot)ntnu.no|Harald Hvaal}}
{{FeatureInProgress|kwalletmanager|Move kwalletmanager to the Model/View architecture and redesign the UI|lemma@confuego.org|Michael Leupold}}
|}

= 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
{{FeatureDone|krosspython and krossruby|Support custom types via handlers|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|krosspython and krossruby|Support QList<CustomType*> constructs|mail@dipe.org|Sebastian Sauer}}
{{FeatureInProgress|Smoke|Wrap some more APIs (at least Akanodi for all languages and Plasma for C#)|kde-bindings@kde.org|KDE-bindings developers}}
{{FeatureInProgress|PyKDE|KCM support and other plugins|simon@simonzone.com|Simon Edwards}}
{{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|Unittests++|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
{{FeatureInProgress|libkdegames|New highscore management system|milliams|Matt Williams}}
{{FeatureDone|kdiamond|Drag jewels|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|kdiamond|Optional OpenGL rendering|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|ksirk|Map scrolling arrows|kleag@free.fr|Gaël de Chalendar}}
{{FeatureDone|ksirk|KHotNewStuff skins|kleag@free.fr|Gaël de Chalendar}}
{{FeatureInProgress|ksirk|Jabber based net game finding|kleag@free.fr|Gaël de Chalendar}}
{{FeatureDone|ksirk|Use only names in skins instead of numeric ids|kleag@free.fr|Gaël de Chalendar}}
{{FeatureDone|ksirk|Skins editor|kleag@free.fr|Gaël de Chalendar}}
{{FeatureInProgress|ktron|Port and remake the KTron game for KDE 4.2|legolas@legolasweb.nl|Stas Verberkt}}
{{FeatureInProgress|KBreakOut|(Optional) fire on mouse click|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureTodo|KBreakOut|Sounds|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureTodo|KBreakOut|Custom levelsets|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureTodo|KBreakOut|KHotNewStuff support for themes|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureTodo|KNetWalk|Support for custom and non-square board sizes|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureTodo|KGoldrunner|Improvement to sound support and themes|mikelima@cirulla.net}}
{{FeatureTodo|KBlocks|Support for sounds|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureTodo|KMahjongg|Support for sounds|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureDone|Killbots|New app for 4.2|parker.coates@gmail.com|Parker Coates}}
{{FeatureTodo|KSudoku|Port of "print game" feature from old version|paulo.cattai@ltia.fc.unesp.br|Paulo Roberto Cattai}}
{{FeatureTodo|KSudoku|Redesign of symbol themes|paulo.cattai@ltia.fc.unesp.br|Paulo Roberto Cattai}}
{{FeatureTodo|KSudoku|Replace the core engine with a new version that will solve most bugs related to gameplay|johannes.bergmeier@gmx.net|Johannes Bergmeier}}
|}

= 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
{{FeatureDone|Kate|Port and reenable the Snippets plugin.|jpetso@gmx.at|Jakob Petsovits}}
{{FeatureDone|perldoc KIOSlave|Add KIOSlave to allow reading Perldoc documentation.|michael.pyne@kdemail.net|Michael Pyne}}
{{FeatureInProgress|Lokalize|XLIFF support|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Lokalize|various Translation Memory enhancements|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureDone|Lokalize|wrap all windows belonging to one project into one MDI window|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Kross-based scripting|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|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|Port code generation wizard to QWizard and replace all q3 widgets|andi.fischer@hispeed.ch|Andi Fischer}}
{{FeatureInProgress|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@gm ail.com|Gopala Krishna A}}
{{FeatureDone|Kate|Move the kate-ctags plugin to kdesdk.|kare.sars@iki.fi|Kåre Särs}}
{{FeatureDone|Kate|Replace the make-plugin with katebuild-plugin.|kare.sars@iki.fi|Kåre Särs}}
|}

= 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
{{FeatureInProgress|KEduca|Rewrite of the classic test writing/taking application|matt@milliams.com|Matt Williams}}
{{FeatureTodo|KLettres|Number support|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KLettres|Theme manager|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureInProgress|KHangMan|Add a Open File action|annma@kde.org|Anne-Marie Mahfouf}}
{{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|KLettres|Visual Indicator when letter is wrong|annma@kde.org|Anne-Marie Mahfouf}}
{{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}}
{{FeatureInProgress|Kalzium|Plasmoid to access Kalzium database|cniehaus@kde.org|Carsten Niehaus}}
{{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}}
{{FeatureDone|KAlgebra|New parser (using QLALR) and new lexer|aleixpol@gmail.com|Aleix Pol}}
{{FeatureDone|KAlgebra|Import capability for MathML Presentation Markup in libanalitza|aleixpol@gmail.com|Aleix Pol}}
{{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|Parley|Declensions|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureInProgress|Parley|Rework main window infrastructure|d.laidig@gmx.de|Daniel Laidig}}
{{FeatureDone|KStars|Display millions of stars|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureDone|KStars|Tool to predict Conjunctions|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureInProgress|KStars|Earth Satellites|kstars@30doradus.org|Jason Harris}}
{{FeatureInProgress|KStars|Sky Calendar Tool|kstars@30doradus.org|Jason Harris}}
{{FeatureInProgress|KStars|Support of Non-western Constellations|jsid@emor3j.fr.eu.org|Jérôme Sonrier}}
{{FeatureDone|KStars|Include HD Catalog Numbers (in search, in display)|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|Separate INDI From KStars|mutlaqja@ikarustech.com|Jasem Mutlaq}}
{{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|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|Python bindings to the Marble widget and classes|simon@simonzone.com|Simon Edwards}}
{{FeatureInProgress|Marble|Network plugins|pino@kde.org|Pino Toscano}}
{{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}}
{{FeatureDone|KTurtle|Export canvas as image|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureTodo|KTurtle|Optional rulers/grid for canvas units|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureDone|KTurtle|Add command line|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureDone|KTurtle|Add a color picker|nielsslot@gmail.com|Niels Slot}}
{{FeatureInProgress|KBruch|Usability Improvements|tiago.porangaba@ltia.fc.unesp.br|Tiago Porangaba}}
{{FeatureInProgress|KBruch|Merging KPercentage functionalities into KBruch|tiago.porangaba@ltia.fc.unesp.br|Tiago Porangaba}}
{{FeatureTodo|Kalzium|Visualization of Schemes and Gradients at same time|tiago.porangaba@ltia.fc.unesp.br|Tiago Porangaba}}
|}

= 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
{{FeatureInProgress|KsCD|Dbus Connection for Now Playing plasmoid|bouchikhi.amine@gmail.com|Amine Bouchikhi}}
{{FeatureInProgress|Dragon Player|Make Dragon indipendent from Xine|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|File Manager|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|play media dialog|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|slider changes|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|show info while playing audio files|ian.monroe@gmail.com|Ian Monroe}}
{{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}}
{{FeatureTodo|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
{{FeatureTodo|KMagnifier|Refactor color menu, re-add invert, break current color blindness code into "daltonize" and "simulate"|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|KMagnifier|Add color-shift modes to help people with color blindness|mw_triad@users.sourceforge.net|Matthew Woehlke}}
|}

= 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|KSnapshot|Add support for grabbing a single screen in multihead|rich@kde.org|Richard Moore}}
{{FeatureDone|KSnapshot|Increase jpeg image quality from 75% to 85%|rich@kde.org|Richard Moore}}
{{FeatureDone|KSnapshot|If we're saving the window decorations then record the window title and class in the image (if the format supports it) to play nice with indexers like strigi|rich@kde.org|Richard Moore}}
{{FeatureTodo|Okular|Sound annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Link annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Improve annotation support: for existing types (rubber stamps, line, note, etc), and for the way they are constructed and handled.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Caret annotations.|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Okular|Support for videos & movie annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Support .snp and .emf file formats|bradh@kde.org|Brad Hards}}
{{FeatureDone|Gwenview|Support for animated images (.gif and .mng)|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureInProgress|Gwenview|Red Eye Reduction|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureInProgress|Gwenview|Nepomuk integration|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Dolphin-like single-click selection|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Optional tree view|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureInProgress|Okular|Usable inverse search.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Synctex support.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|"Okular document package" for import/export a document with metadata (eg annotations).|pino@kde.org|Pino Toscano}}
{{FeatureDone|Okular|New backend for fax documents.|tokoe@kde.org|Tobias Koenig}}
{{FeatureTodo|Okular|Usability improvements.|pino@kde.org|Pino Toscano}}
|}

= 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
{{FeatureDone|kio_bookmarks|A new konqueror home page displaying user bookmarks. See [[http://kde-apps.org/content/show.php?content=86516 description]]|xavier.vello@gmail.com|Xavier Vello}}
{{FeatureInProgress|kuiserver|KUiServer Goya port. General improvements for usability improvements|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureInProgress|kio fish/sftp|port fish and sftp to windows|brandon.ml@gmail.com|Carlo Segato}}
|}

= 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
{{FeatureTodo|konqueror|A new konqueror recover-dialog replacement|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureTodo|konqueror|Rework bookmarks using Akonadi|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureInProgress|dolphin|Add zoom slider into the status bar and general zooming improvments|peter.penz@gmx.at|Peter Penz}}
{{FeatureDone|dolphin|Tooltip previews|peter.penz@gmx.at|Peter Penz}}
{{FeatureTodo|dolphin|ui to select preferred default settings for directory view|loic.marteau@gmail.com|Loic Marteau}}
{{FeatureInProgress|konqueror|Tagging and rating of webpages using Nepomuk - Already finished in playground.|trueg@kde.org|Sebastian Trueg}}
|}

= 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
{{FeatureTodo|PoTD engine|Import from playground|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Frame plasmoid|Honor EXIF rotation - see bug 164605|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Frame plasmoid|Previous, Pause and Next buttons - see bug 164704|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureDone|Comic dataengine|Port all comics to QScript and offer them through GHNS|mat69@gmx.net|Matthias Fuchs}}
{{FeatureInProgress|Comic dataengine|Finish script support|mat69@gmx.net|Matthias Fuchs}}
{{FeatureInProgress|Eyes applet|xeyes clone applet|ogoffart%kde.org|Olivier Goffart}}|}

Development/Software Engineering Framework

2008-10-31T18:50:23Z

Steveire: /* Marketing and Expectations */ Add community website link

This page is intended to be a summary of the tools and processes used by the KDE
project for Software Engineering tasks, i.e. everything around coding
work. This includes bugfixing, review, testing, documentation,
requirements etc.

The current tool used by KDE should be listed along with the extent of
its use, known alternatives, and advantages/disadvantages.

== Development Tools ==
{{SEFBox
| name=Source Control
| currentState=
* [http://websvn.kde.org/ Subversion 1.4]
| people=
The kde sysadmin team:
* [http://wire.dattitu.de/authors/2-Dirk Dirk Müller]
* [http://www.kdab.net/~dfaure/ David Faure]
| getInvolved=
* {{KDEML|kde-scm-interest}}
| altTools=
* [http://git.or.cz/ git], repo
* [http://bazaar-vcs.org/ bazaar]
* [http://www.selenic.com/mercurial/ mercurial]
* [[Projects/GitoriousKDE|Gitorious]]
}}

Subversion 1.4 is currently used for source control management in KDE on
a server hosted in Frankfurt. A separate server is used for access to
the read-only mirror anonsvn.kde.org.

There is interest in migrating to a distributed source control
management tool, such as GIT. Discussion of this is taking place on the
{{KDEML|kde-scm-interest}}
mailing list. It is likely git will be used along with a tool such as repo.

{{SEFBox
| name=Build System
| currentState=
* [http://www.cmake.org/ CMake 2.6.0]
* [http://api.kde.org/cmake/modules.html Custom CMake module documentation]
| getInvolved=
* {{KDEML|kde-buildsystem}}
| people=
* [http://www.kdedevelopers.org/blog/531 Alexander Neundorf]
}}

CMake is the build tool currently used by KDE. It is Free Software
developed by [http://www.kitware.com/ kitware inc] and available on
multiple platforms supported by KDE.

This tool was chosen as the buildsystem for the KDE4 series, and there
are no plans currently to migrate away from it. CMake version 2.6.2 will be required to build KDE 4.2 final.

{{SEFBox
| name=Identifier search
| currentState=
http://lxr.kde.org
| people=
The kde sysadmin team:
* [http://wire.dattitu.de/authors/2-Dirk Dirk Müller]
* [http://www.kdab.net/~dfaure/ David Faure]
}}

[http://en.wikipedia.org/wiki/LXR_Cross_Referencer LXR] indexes classes and methods used in KDE. This can be useful for finding examples of how to use a class, and finding all uses of a class while refactoring or updating API.

== Review ==
{{SEFBox
| name=Patch review (pre commit)
| currentState=
* [http://reviewboard.vidsolbach.de/ Review-board] used by plasma project.
* trunk/kdereview
| people=
* David Solbach and the kde sysadmin team maintain the Plasma review-board installation.
| getInvolved=
* {{KDEML|kde-core-devel}}: Discuss KDE patch review and tools
| altTools=
* Launchpad.net offers merge review/approval pre-merge [https://code.launchpad.net/~thumper/pqm/test-bzr-home/+merge/296/] [http://news.launchpad.net/cool-new-stuff/review-branch-merge-proposals-in-launchpad] [http://news.launchpad.net/cool-new-stuff/email-interface-to-code-review]
}}

In general KDE does not have a formal patch review policy for individual
patches. Some patches do get reviewed prior to committing to svn by the
relevant mailing lists. This is the case for particularly large patches
or patches by new developers.

As an official policy kdereview is used to review new applications and
new classes for kdelibs prior to inclusion in KDE trunk. A drawback of
this system is that not all reviewers report that they have reviewed the
new content. It may make sense to have a checklist for reviewers to use,
eg,

* All new classes documented [x]
* Private classes and d-pointers used where appropriate [x]
* Passes all krazy checks [ ]
* No obvious security concerns [ ]
* Designed well/maintainable [ ]
* etc...

This was discussed to some extent [http://thread.gmane.org/gmane.comp.kde.devel.core/54213 here], but has not yet been refined into a techbase page.

{{SEFBox
| name=Commit review (after commit)
| currentState=
* {{KDEML|kde-commits}} mailing list records all commits to KDE svn.
* The [http://commit-filter.org commit filter] is used to filter relevant commits based on path of the commit.
* SVN <tt>CCMAIL:</tt> feature used to notify relevant mailing lists or individuals of specific commits.
* SVN <tt>BUG:</tt> feature used to close bugs, and also notifies all bug subscribers of the commit.
* SVN <tt>CCBUG:</tt> feature used to notify closed bugs of updates. Commonly used when porting fixes between branches. Also notifies all bug subscribers of the commit.
| getInvolved=
* {{KDEML|kde-commits}}
| altTools=
* Unknown
}}

The commit filter is used by several projects to forward all commits to the relevant mailing list.

{{SEFBox
| name=Design Review
| currentState=
Design review takes place on
* mailing lists
* project wikis
* face-to-face/BOF sessions and sprints
* kdereview
| getInvolved=
* {{KDEML|kde-core-devel}} is used to announce new additions to kdereview.
}}

KDE does not have an offical design review process. Some design review takes place as part of the kdereview process. It may be possible to further formalise this or encourage design documentation.

== Documentation ==

{{SEFBox
| name=Technical documentation
| currentState=
* http://techbase.kde.org
* http://wiki.kde.org
* http://wiki.koffice.org
| getInvolved=
* {{KDEML|kde-www}}
| people=
* [[User:Danimo|Danimo]] is the MediaWiki admin for techbase.kde.org.
| futureWork=
}}

techbase.kde.org is a [http://www.mediawiki.org MediaWiki] powered site used for collaborating on technical tasks such as tutorials, schedules, and project information. wiki.kde.org is a tiki-wiki site with the same function. Both are actively used. It might make sense to merge the two sites.

{{SEFBox
| name=API documentation
| currentState=
* [http://www.stack.nl/~dimitri/doxygen/ Doxygen] is used to generate api documentation from documentation strings in code.
| getInvolved=
* [[Development/Tutorials/API_Documentation|APIDOX tutorials]] Make KDE API docs better.
| people=
* [http://www.kdedevelopers.org/blog/1451 Allen Winter] administers api.kde.org.
| altTools=
* [http://labs.trolltech.com/blogs/2008/06/20/introducing-doxygen2qthelp-create-qch-files-from-doxygen-finally/ doxygen2qthelp] used by trolltech to create qt documentation.
}}

KDE API documentation is generated nightly and hosted on http://api.kde.org. It is also possible to generate the same documentation locally for use in an IDE for example.

It is possible to create [http://www.kdedevelopers.org/node/3010 man pages] and [http://thread.gmane.org/gmane.comp.kde.devel.core/55578 qthelp documentation] from kde sources.

{{SEFBox
| name=User documentation
| currentState=
* http://userbase.kde.org
* [http://i18n.kde.org/docs/doc-primer/check-docs.html meinproc] is used to generate user documentation.
* {{KDEML|kde-docbook}} Records all SVN commits with the <tt>GUI</tt> magic word.
| getInvolved=
* http://userbase.kde.org Create tutorials and tips.
* {{KDEML|kde-doc-english}} Used to coordinate user documentation.
* {{KDEML|kde-docbook}} Help update documentation after GUI changes.
}}

User documentation is generated from module doc/ folders and hosted on http://docs.kde.org.

meinproc is a KDE tool (written by Stephen Kulow which uses libxslt to transform docbook into (bzipped) html. At runtime kio_help opens that bzipped html and displays it to the user in khelpcenter.

http://userbase.kde.org is intended to be the primary source of user documentation on the web. Content will possibly be packaged for offline use in the future.

== Testing and Quality ==

{{SEFBox
| name=Bug tracking
| currentState=
* [http://bugs.kde.org/ Bugzilla 3.0.x].
* KBugBuster
| people=
* [http://mattr.info:8080/blog/?s=bugzilla Matt Rogers] and the KDE sysadmin team maintain the KDE bugzilla installation.
| getInvolved=
* {{KDEML|kde-core-devel}} Discuss alternative bug trackers for KDE.
* {{KDEML|kde-bugs-dist}} Records all updates on bugs.kde.org.
* {{KDEML|kdelibs-bugs}} Records all updates to kdelibs bugs.
* {{KDEML|konq-bugs}} Records all updates to konqueror bugs.
* {{KDEML|kdevelop-bugs}} Records all updates to kdevelop bugs.
* {{KDEML|amarok-bugs-dist}} Records all updates to amarok bugs.
| altTools=
* https://bugs.launchpad.net, [http://www.sourcecode.de/content/leonov-launchpad-desktop-client-first-coming Leonev]
* [http://trac.edgewall.org/ trac]
* [http://www.redmine.org/ Redmine] - kind of "Trac on Rails"
}}

Bug tracking in KDE currently is managed using Bugzilla 3.0. Work was recently merged on a transition to Bugzilla 3.0 from Bugzilla 2.16. There is still cleanup work going on but most features of the previous Bugzilla installation already work.

Bugzilla can be difficult to use and daunting to newbies.

{{SEFBox
| name=Static code analysis
| currentState=
* [http://www.englishbreakfastnetwork.org/krazy/ Krazy] hosted at EnglishBreakfastNetwork (EBN).
* [http://www.coverity.com/ Coverity] is used to find possible sources of defects and suggested optimizations. Results are displayed per module as part of [http://ktown.kde.org/~dirk/dashboard/ Dirks Dashboard builds].
| people=
* [http://people.fruitsalad.org/adridg/bobulate/ Adriaan de Groot]
* [http://www.kdedevelopers.org/blog/1451 Allen Winter]
| getInvolved=
*
}}

Additional checks are always welcome for adding to Krazy. See http://websvn.kde.org/trunk/quality/.

{{SEFBox
| name=Build testing
| currentState=
* [http://developer.kde.org/~dirk/dashboard/ Continuous build server] reports broken builds on linux.
* [http://www.cdash.org/CDash/index.php?project=kdelibs CDash build server] stores results of non-linux builds for kdelibs.
| getInvolved=
* {{KDEML|kde-core-devel}} Find out how to submit test build results.
| people=
* [http://wire.dattitu.de/authors/2-Dirk Dirk Mueller] maintains the dashboard
* Bill Hoffman is involved with the kitware CDash service.
* http://www.cdash.org/mailinglist.html
}}

There is interest in more build testing for KDE especially on non-linux platforms. Improvements include some standard ctest scripts that can be used to build and submit a dashboard result for kdelibs to CDash. This would be run on a cronjob for simplicity.

Builds are planned for the following platforms:

* Windows
* MacOS
* FreeBSD 6 (gcc)
* FreeBSD 7 (gcc)
* Solaris (S10, S11) on SPARC and amd64

{{SEFBox
| name=Unit testing
| currentState=
[[Development/Tutorials/Unittests|Unit tests]] may be written with the QTest framework. Tests can be run with the command '<tt>make test</tt>'.
| getInvolved=
* [[Development/Tutorials/Unittests|Techbase Unit tests tutorial]]
}}

It may be possible run run these tests automatically possibly on EBN or on Dirks dashboard.

{{SEFBox
| name=Quality testing
| currentState=
* The early adopter/user community
* [http://www.sqo-oss.eu/news/coverage/sqo-oss-project-launched-with-kde SQO-OSS]
| people=
* [http://people.fruitsalad.org/adridg/bobulate/ Adriaan de Groot]
* [http://hemswell.lincoln.ac.uk/~padams/index.php Paul Adams]
| getInvolved=
}}

It may be possible to obtain metrics such as bugs per kloc, defect injection rate etc.

{{SEFBox
| name=Profiling and Optimizations
| currentState=
* {{KDEML|kde-optimize}} mailing list coordinates optimizations in KDE.
* Krazy and Coverity tools also include some optimization checks.
* KDE macros for optimization of common algorithms.
| getInvolved=
* {{KDEML|kde-optimize}}
* [http://ktown.kde.org/~dirk/dashboard/4.1/i386/kdelibs.html Coverity report for KDE libs].
}}

Tutorials may be provided in the future to help developers optimize their code.

{{SEFBox
| name=Accessibility and Usability
| currentState=
* http://usability.kde.org/
* http://openusability.org/projects.php
* Season of usability
| people=
* [http://weblog.obso1337.org/ Celeste Lyn Paul]
* [http://ellen.reitmayr.net/index.php/blog Ellen Reitmayr]
| getInvolved=
* {{KDEML|kde-usability}}
* [[Projects/Usability/HIG KDE Human interaction Guidelines]].
}}

{{SEFBox
| name=Research
| currentState=
* http://research.kde.org
* [http://www.sqo-oss.eu/news/coverage/sqo-oss-project-launched-with-kde SQO-OSS]
* http://nepomuk.kde.org/ Semantic desktop project funded by the EU.
| people=
* [http://people.fruitsalad.org/adridg/bobulate/ Adriaan de Groot]
* [http://www.kdedevelopers.org/blog/2904 Sebastian Trueg] leads the kde-nepomuk project.
| getInvolved=
* [http://lists.semanticdesktop.org/mailman/listinfo/nepomuk-kde Nepomuk KDE mailing list]
}}

== Marketing and Expectations ==

{{SEFBox
| name=Requirements Gathering
| currentState=
* Requirements come from user feedback on http://bugs.kde.org and from commercial interests.
* Developers may do some research into requirements for applications based on User Research Profiles.
| getInvolved=
* http://bugs.kde.org Fill new wishlist items.
* {{KDEML|kde-core-devel}} Discuss new ways for kde to gather requirements.
}}

{{SEFBox
| name=Promotion
| currentState=
* The {{KDEML|kde-promo|KDE marketing team}} manage marketing and promotion from official kde sources.
* http://dot.kde.org is the community forum around promotional announcements.
* http://www.kde.org/announcements is the official source of promotional announcements regarding KDE.
* Design and maintenance of KDE websites is organised on the [https://mail.kde.org/mailman/listinfo/kde-www kde-www mailing list]
* The [http://ev.kde.org/workinggroups/mwg.php Marketing working group] coordinates several marketing efforts such as promoting planning and branding.
* KDE e.v provides a booth box for conference booths containing posters, leaftlets and other information needed at a conference stand.
| people=
* [http://wadejolson.wordpress.com/ Wade Olsen]
* [http://troy-at-kde.livejournal.com/ Troy Unrau]
* [http://nowwhatthe.blogspot.com/ Jos Poortvliet]
| getInvolved=
* {{KDEML|kde-promo}}
* [http://dot.kde.org/addPostingForm Submit dot articles]
}}

{{SEFBox
| name=Community management
| currentState=
* The Community Working Group helps with community advice when needed
* [http://www.kde.org/code-of-conduct/ Code of Conduct] Based on the Ubuntu Code of Conduct, documents guidelines for acceptable behaviour within the community. Can be summarized as 'Be Excellent to Eachother'.
* http://community.kde.org. In development website.
| people=
* Anne Willson
* [http://jucato.org Juan Carlos Torres]
* [http://lydiapintscher.de Lydia Pintscher]
* Martin Fitzpatrick
* [http://omat.nl Tom Albers]
| getInvolved=
* Send an e-mail to community-wg@kde.org
}}

{{SEFBox
| name=Communication
| currentState=
Developers communicate with each other through
* [http://lists.kde.org/ mailing lists]
* [http://searchirc.com/irc-kde-1 IRC]
* [http://planetkde.org Blogs]
* Conferences
Developers communicate with users though
* [http://planetkde.org Blogs] to some extent (mainly early adopting users).
* [http://forum.kde.org Forums] to some extent where the developer chooses to.
* [http://dot.kde.org News announcements]
Users communicate with each other and developers through
* [http://forum.kde.org Forums]
* {{KDEML|kde}} mailing list
* #kde irc channel.
| people=
* [http://c133.org/blog/ Chris Lee] administers planetkde.org
| getInvolved=
* Add your blog to planet kde if you contribute to KDE in some way, including development, testing, advocacy, translation, documentation etc.
}}

== Release ==

{{SEFBox
| name=Release Scheduling
| currentState=
* Maintained at [[Schedules]].
| people=
*
* [http://cyrilleberger.blogspot.com/ Cyrill Berger] - KOffice release coordinator.
* [http://www.kdedevelopers.org/blog/1451 Allen Winter] - KDEPIM release coordinator.
| getInvolved=
* {{KDEML|release-team}}
}}

{{SEFBox
| name=Feature planning
| currentState=
* [[Schedules/KDE4/4.1_Feature_Plan]]
* [[Schedules/KDE4/4.2_Feature_Plan]]
| people=
[https://mail.kde.org/mailman/listinfo/release-team The KDE release team]
| altTools=
* Launchpad.net offers a blueprints system.
* [http://wiki.pentaho.com/display/OpenScrum/Home Scrum in Open Source Projects]
| getInvolved=
* {{KDEML|kde-core-devel}} - Discuss the KDE approach to feature planning.
}}

Currently techbase is used for feature planning but there may be better alternatives.

{{SEFBox
| name=Downstream packagers and contributions
| currentState=
* Many distributions package KDE3 & KDE4.
| getInvolved=
* {{KDEML|kde-packagers}} - Private mailing list for packagers. Includes information relating to security releases.
}}

== Theming and Translations ==

{{SEFBox
| name=Artwork
| currentState=
* The {{KDEML|kde-artists|kde-artists team}} creates offical artwork for KDE.
* kde-look.org for non-offical artwork.
| people=
* [http://pinheiro-kde.blogspot.com/ Nuno Pinheiro]
| getInvolved=
* {{KDEML|kde-artists}}
}}

Additional contributed artwork is available on http://kde-look.org.

There may be a need to create tutorials on how to create artwork for kde.

{{SEFBox
| name=Translation
| currentState=
* http://i18n.kde.org/ is used for level of completion of translations in KDE.
* GNU gettext is used for translation in KDE.
* <tt>.po</tt> files are edited directly in KDE svn to update translations.
* A kde4 based translation client (lokalize) is being developed in kdesdk/.
* Krazy includes sanity checks/plurals checking for translation.
| altTools=
launchpad.net features a web-based tool called rosetta, which allows for easier fly-by translations. This is considered not to be useful as fly-by translators often do not follow guidelines or consistency rules when translating.
| getInvolved=
* {{KDEML|kde-i18n-doc}}
}}

== Legal And Support ==
{{SEFBox
| name=KDE e.v. - Representative Legal Entity
| currentState=
* [http://ev.kde.org KDE e.v] is a registered non-profit organization that represents the KDE Project in legal and financial matters.
| altTools= N/A
| getInvolved=
* [http://ev.kde.org/getinvolved/ KDE e.v. membership]
}}

{{SEFBox
| name=Resolving licencing issues.
| currentState=
* A [http://ev.kde.org/announcements/2008-08-22-fsfe-welcomes-fla.php Fiduicary Licence Agreement] is available, which will allow KDE developers to optionally assign copyright of their contributions to KDE e.v. This would allow easier relicencing of contributors content in the event that KDE needs to move to another licence. It also allows the e.v. to more easily represent the work in the unlikely event of a court dispute involving KDE code.
* [[Policies/Licensing_Policy|KDE licencing policy]] allows commercial and non-commercial development and proprietry and non-proprietry development.
* [[Projects/KDE_Relicensing|Projects/KDE_Relicensing]] Effort to relicence KDE code to use version 3 of GNU GPL and LGPL. This work is unfinished but not still being performed. Many contributors are no longer contactable.
| altTools= N/A
}}

{{SEFBox
| name=Sponsorship and Patronship
| currentState=
* [http://ev.kde.org/supporting-members.php Supporters of KDE] contribute sponsorship money to KDE e.v.
* http://ev.kde.org/getinvolved/supporting-members.php
| altTools= N/A
}}

Policies/Suggested Review Criteria

2008-10-30T13:34:51Z

Steveire: /* Security */ Small note about sql injection.

Code review should be constructive and specific. These criteria are a
guideline for what reviewers should consider when reviewing new code. This is '''not''' a strict prerequisite to be completed before review. They are just for information purposes to be aware of what aspects of new code have actually been reviewed, and what has not. It is a list of suggestions for reviewers to record the criteria they're reviewing, rather than another barrier for developers of new applications and libraries to worry about. For example a reviewer does not have to test the new code on all platforms or compilers, but can say which ones were tested if more than the most common linux/gcc. See origins [http://thread.gmane.org/gmane.comp.kde.devel.core/54213 here].

All criteria do not all have to be completed, and additional criteria can optionally be defined by the reviewer. The desired result of a review is that the reviewer states whether the code is of enough quality as it is now, or whether changes are necessary, and what criteria were considered in making
that assessment.

== Library And Application Code ==

=== General ===
* The application / library works and performs the expected function.
* The library / application uses existing kdelibs classes where appropriate instead of reinventing the wheel.
* The application includes all necessary cmake checks for locating dependencies.
* Qt classes are not used where a KDE class is more appropriate (KFileDialog vs QDFileDialog, QHttp vs KIO etc).

=== Maintainability ===
* The application / library is designed for maintainability and is consistent with KDE standards and norms.
* Complex algorithms and optimizations are sufficiently commented to be understandable.
* Methods are public, protected, virtual and const as appropriate.
* Dependencies are still in active development

=== Security ===
* The application / library has no obvious security flaws.
* html entities ('<', '>', '"', '&') accepted from external sources are encoded.
* All places where the application launches external programs should be checked.
* Any SQL queries processing untrusted data should be checked. Queries need to be escaped appropriately to avoid sql injection.

=== Quality ===
* The application / library passes all krazy tests. All exceptions in a .krazy file are justified.
* Exception handling is done right.
* Classes are threadsafe where appropriate.
* Appropriate data structures are used ( eg, QMap or QHash etc)

=== Portability ===
* The new code has no unnecessary platform specific code, such as reading /proc etc. This does not apply to new code which is relevant only on specific platforms.
* The new code uses syntax which compiles on all supported compilers, free from gcc-isms etc.
* The application compiles and runs on Windows, Mac, BSD, Solaris.

=== Documentation and comments ===
* Comments in the code are appropriate and not excessive.
* Application user documentation is written.

=== Style ===
* Coding style in consistent with the rest of the library / module. Some modules (kdepim, kdelibs) have style rules to conform to, but most do not.
* Variable names are consistent with the target module or library module. (m or m_ prefix, camel casing, descriptive variable names instead of a, b and c2 etc)
* There are no excessively large methods. Methods longer than 40 lines can be broken into multiple methods if possible.
* There are no excessively long lines. for lines greater than 80 characters it might be possible to use intermediate variables more.

=== i18n and i10n ===
* One word strings use context for translation
* Strings are free from word puzzles (see [[Development/Tutorials/Localization/i18n_Mistakes]])
* The KUIT system is used [[Development/Tutorials/Localization/i18n_Semantics]].

== Libraries Only ==
=== Maintainability ===
* All public classes use a private d-pointer class.

=== Documentation ===
* All public methods are documented.
* Private methods and classes are documented where necessary and marked as @internal.

Policies/Application Lifecycle

2008-10-30T13:30:39Z

Steveire: /* Stage 2: Stable */ Add link to Suggested_Review_Criteria page.

When you want to start a new application (or remove an old application), you want to know where you should place it in the Subversion repository. This document describes where to go in which stage of your application.

See [[#Stage 3: The end]] for instructions on how to deal with old, unmaintained applications.

In a diagram it all comes down to:

[[Image:svnguidelines.png]]

=== Stage 1: The start ===
The start of a new application can take place on a local disk, in a local repository or any other way. Another option is provided by KDE in the special {{path|/trunk/playground}} folder in the repository where everyone is free to commit ones own application. You can [[Contribute/Get_a_SVN_Account | request an SVN account]] and after that you can import your project in the subfolder of your choice. Applications in playground are organized in folders like KDE is itself. For example, games are in {{path|/trunk/playground/games}}. In each of these folders, there is a {{path|doc}} folder where you should put the docbook documentation of your application.

It is not meant as a backup area, so you should not develop your application somewhere else and only sync the changes now and then to KDE's repository.

As soon as you start releasing your software and match the criteria for the next stage, you should consider moving your application folder to the next stage. When doing this move, don't forget to move also its documentation folder.

Because playground is something like an 'experimental' area, there is only a small amount of applications that make it to the next stage. To keep the playground area accessible and a bit organized, we have created a {{path|/tag/unmaintained/N}} (where 'N' is the KDE major version the application was written for; e.g. 4 for KDE4 applications). If you do not want to continue your application, move it to that place in the repository. If you do not know how, contact the current contactperson which is mentioned at the bottom of this document.

Whenever an application has not received a commit for one complete year, you will be contacted via email to discuss if you want to continue the application or if it has died. In the latter case or when the email bounces, it will be moved to {{path|/tag/unmaintained/N/}}.

=== Stage 2: Stable ===
When you have made one of more releases and want to continue to develop it, the term 'playground' does no longer apply to you. That is the right time to move out of here. There are two options to move to: extragear and one of the KDE main modules. If you want to move to one of the KDE main modules, you will get released with KDE. That also means you have to respect that release schedule. The fact you want your program in KDE main modules is not enough and others have to agree is valuable to have it.
In extragear you are on your own. You make the releases whenever you want and you have to talk to the translators about your release schedule. In the future it might be possible to be released together with the KDE main modules. But at this moment this is not possible.

Whatever you choose, there are some rules to follow before you are allowed to move to either location:
* There should be user documentation in docbook format. If you need help, you can ask for help to the KDE Documentation team: [https://mail.kde.org/mailman/listinfo/kde-doc-english kde-doc-english@kde.org].
* There should be developers documentation in the form of apidox for libraries you can check this at [http://www.englishbreakfastnetwork.org/ ebn]
* There should be no krazy code checker issues reported. Again, you can check that at [http://www.englishbreakfastnetwork.org/ ebn]. There is also a [[Development/Tutorials/Code_Checking|tutorial on using Krazy]] available here on TechBase.
* If possible, there should have been a basic usability review of your application. Usability people are hard to get, so this is not crucial.
* You should have checked for basic problems with a profiler. I hope we will get a tutorial on how to do this soon
* Your application should be [[Development/Tutorials/Localization/i18n|completely translatable]].

When you decide you want to move to this second stage, move your application to {{path|/trunk/kdereview}} and announce the move on '''kde-core-devel@kde.org'''. In the announcement address the above issues and state where you want your application to move to (which KDE main module or extragear). Extragear only requires general approval on kde-core-devel. A main module requires approval from the community who manages that module (e.g. the kdepim module requires approval from the kdepim community). Don't forget to move the documentation of your application to {{path|/trunk/kdereview/doc}}. Some suggestions for reviewers to consider when reviewing new applications and library code are on [[Policies/Suggested_Review_Criteria]].

The move to kdereview starts a two week review period during which the community can object to your proposal or request additional changes. If there are no objections or requested changes after this two week period, you are allowed to move your application to the place you requested. If your intention is to move to a main module you must additionally get approval from the [[Projects/Release_Team#Module_Coordinators|module coordinator(s)]] who manage that module.

If changes are requested, you can leave your application in kdereview while you are actively working on those issues. If you lack the time to work on the changes, move your application back to playground. Once the requested changes are completed, announce to kde-core-devel that you have completed the requested changes and wait for another week for objections.

Kdereview is only meant as a transitional place from playground to the main modules or extrager. In no case can kdereview be a permanent place to develop your application.

=== Stage 3: The end ===
Whenever you decide to stop developing the application and that leaves the application without developers, please announce that to kde-core-devel. If nobody stands up to take over maintainership within two weeks, the application has to be moved to the {{path|/trunk/unmaintained/N/}} area as every application in the KDE main modules and in extragear needs to have a maintainer to stay there.

=== Translations ===
For each move in subversion, the translation files of each language need to move as well. Because this requires a complete checkout of the l10n folder and some knowledge about the structure, you can ask the release-team ('''release-team@kde.org''') to move them. Send a simple mail with the information required to do the move, for example: 'move {{path|/playground/somewhere/someapp}} to {{path|/kdereview/someapp}}'.
If you want to help out with these kinds of moves, please send a mail! You are welcome to help out.

=== Contact ===
If you need any help regarding this, please contact Tom Albers ('''tomalbers@kde.nl''')

[[Category:Policies]]

Policies/Suggested Review Criteria

2008-10-30T13:28:27Z

Steveire: Suggested criteria to consider when reviewing new code for KDE.

Code review should be constructive and specific. These criteria are a
guideline for what reviewers should consider when reviewing new code. This is '''not''' a strict prerequisite to be completed before review. They are just for information purposes to be aware of what aspects of new code have actually been reviewed, and what has not. It is a list of suggestions for reviewers to record the criteria they're reviewing, rather than another barrier for developers of new applications and libraries to worry about. For example a reviewer does not have to test the new code on all platforms or compilers, but can say which ones were tested if more than the most common linux/gcc. See origins [http://thread.gmane.org/gmane.comp.kde.devel.core/54213 here].

All criteria do not all have to be completed, and additional criteria can optionally be defined by the reviewer. The desired result of a review is that the reviewer states whether the code is of enough quality as it is now, or whether changes are necessary, and what criteria were considered in making
that assessment.

== Library And Application Code ==

=== General ===
* The application / library works and performs the expected function.
* The library / application uses existing kdelibs classes where appropriate instead of reinventing the wheel.
* The application includes all necessary cmake checks for locating dependencies.
* Qt classes are not used where a KDE class is more appropriate (KFileDialog vs QDFileDialog, QHttp vs KIO etc).

=== Maintainability ===
* The application / library is designed for maintainability and is consistent with KDE standards and norms.
* Complex algorithms and optimizations are sufficiently commented to be understandable.
* Methods are public, protected, virtual and const as appropriate.
* Dependencies are still in active development

=== Security ===
* The application / library has no obvious security flaws.
* html entities ('<', '>', '"', '&') accepted from external sources are encoded.
* All places where the application launches external programs should be checked.
* Any SQL queries processing untrusted data should be checked.

=== Quality ===
* The application / library passes all krazy tests. All exceptions in a .krazy file are justified.
* Exception handling is done right.
* Classes are threadsafe where appropriate.
* Appropriate data structures are used ( eg, QMap or QHash etc)

=== Portability ===
* The new code has no unnecessary platform specific code, such as reading /proc etc. This does not apply to new code which is relevant only on specific platforms.
* The new code uses syntax which compiles on all supported compilers, free from gcc-isms etc.
* The application compiles and runs on Windows, Mac, BSD, Solaris.

=== Documentation and comments ===
* Comments in the code are appropriate and not excessive.
* Application user documentation is written.

=== Style ===
* Coding style in consistent with the rest of the library / module. Some modules (kdepim, kdelibs) have style rules to conform to, but most do not.
* Variable names are consistent with the target module or library module. (m or m_ prefix, camel casing, descriptive variable names instead of a, b and c2 etc)
* There are no excessively large methods. Methods longer than 40 lines can be broken into multiple methods if possible.
* There are no excessively long lines. for lines greater than 80 characters it might be possible to use intermediate variables more.

=== i18n and i10n ===
* One word strings use context for translation
* Strings are free from word puzzles (see [[Development/Tutorials/Localization/i18n_Mistakes]])
* The KUIT system is used [[Development/Tutorials/Localization/i18n_Semantics]].

== Libraries Only ==
=== Maintainability ===
* All public classes use a private d-pointer class.

=== Documentation ===
* All public methods are documented.
* Private methods and classes are documented where necessary and marked as @internal.

Development/Software Engineering Framework

2008-10-29T20:34:24Z

Steveire: Many changes and updates

This page is intended to be a summary of the tools and processes used by the KDE
project for Software Engineering tasks, i.e. everything around coding
work. This includes bugfixing, review, testing, documentation,
requirements etc.

The current tool used by KDE should be listed along with the extent of
its use, known alternatives, and advantages/disadvantages.

== Development Tools ==
{{SEFBox
| name=Source Control
| currentState=
* [http://websvn.kde.org/ Subversion 1.4]
| people=
The kde sysadmin team:
* [http://wire.dattitu.de/authors/2-Dirk Dirk Müller]
* [http://www.kdab.net/~dfaure/ David Faure]
| getInvolved=
* {{KDEML|kde-scm-interest}}
| altTools=
* [http://git.or.cz/ git], repo
* [http://bazaar-vcs.org/ bazaar]
* [http://www.selenic.com/mercurial/ mercurial]
* [[Projects/GitoriousKDE|Gitorious]]
}}

Subversion 1.4 is currently used for source control management in KDE on
a server hosted in Frankfurt. A separate server is used for access to
the read-only mirror anonsvn.kde.org.

There is interest in migrating to a distributed source control
management tool, such as GIT. Discussion of this is taking place on the
{{KDEML|kde-scm-interest}}
mailing list. It is likely git will be used along with a tool such as repo.

{{SEFBox
| name=Build System
| currentState=
* [http://www.cmake.org/ CMake 2.6.0]
* [http://api.kde.org/cmake/modules.html Custom CMake module documentation]
| getInvolved=
* {{KDEML|kde-buildsystem}}
| people=
* [http://www.kdedevelopers.org/blog/531 Alexander Neundorf]
}}

CMake is the build tool currently used by KDE. It is Free Software
developed by [http://www.kitware.com/ kitware inc] and available on
multiple platforms supported by KDE.

This tool was chosen as the buildsystem for the KDE4 series, and there
are no plans currently to migrate away from it. CMake version 2.6.2 will be required to build KDE 4.2 final.

{{SEFBox
| name=Identifier search
| currentState=
http://lxr.kde.org
| people=
The kde sysadmin team:
* [http://wire.dattitu.de/authors/2-Dirk Dirk Müller]
* [http://www.kdab.net/~dfaure/ David Faure]
}}

[http://en.wikipedia.org/wiki/LXR_Cross_Referencer LXR] indexes classes and methods used in KDE. This can be useful for finding examples of how to use a class, and finding all uses of a class while refactoring or updating API.

== Review ==
{{SEFBox
| name=Patch review (pre commit)
| currentState=
* [http://reviewboard.vidsolbach.de/ Review-board] used by plasma project.
* trunk/kdereview
| people=
* David Solbach and the kde sysadmin team maintain the Plasma review-board installation.
| getInvolved=
* {{KDEML|kde-core-devel}}: Discuss KDE patch review and tools
| altTools=
* Launchpad.net offers merge review/approval pre-merge [https://code.launchpad.net/~thumper/pqm/test-bzr-home/+merge/296/] [http://news.launchpad.net/cool-new-stuff/review-branch-merge-proposals-in-launchpad] [http://news.launchpad.net/cool-new-stuff/email-interface-to-code-review]
}}

In general KDE does not have a formal patch review policy for individual
patches. Some patches do get reviewed prior to committing to svn by the
relevant mailing lists. This is the case for particularly large patches
or patches by new developers.

As an official policy kdereview is used to review new applications and
new classes for kdelibs prior to inclusion in KDE trunk. A drawback of
this system is that not all reviewers report that they have reviewed the
new content. It may make sense to have a checklist for reviewers to use,
eg,

* All new classes documented [x]
* Private classes and d-pointers used where appropriate [x]
* Passes all krazy checks [ ]
* No obvious security concerns [ ]
* Designed well/maintainable [ ]
* etc...

This was discussed to some extent [http://thread.gmane.org/gmane.comp.kde.devel.core/54213 here], but has not yet been refined into a techbase page.

{{SEFBox
| name=Commit review (after commit)
| currentState=
* {{KDEML|kde-commits}} mailing list records all commits to KDE svn.
* The [http://commit-filter.org commit filter] is used to filter relevant commits based on path of the commit.
* SVN <tt>CCMAIL:</tt> feature used to notify relevant mailing lists or individuals of specific commits.
* SVN <tt>BUG:</tt> feature used to close bugs, and also notifies all bug subscribers of the commit.
* SVN <tt>CCBUG:</tt> feature used to notify closed bugs of updates. Commonly used when porting fixes between branches. Also notifies all bug subscribers of the commit.
| getInvolved=
* {{KDEML|kde-commits}}
| altTools=
* Unknown
}}

The commit filter is used by several projects to forward all commits to the relevant mailing list.

{{SEFBox
| name=Design Review
| currentState=
Design review takes place on
* mailing lists
* project wikis
* face-to-face/BOF sessions and sprints
* kdereview
| getInvolved=
* {{KDEML|kde-core-devel}} is used to announce new additions to kdereview.
}}

KDE does not have an offical design review process. Some design review takes place as part of the kdereview process. It may be possible to further formalise this or encourage design documentation.

== Documentation ==

{{SEFBox
| name=Technical documentation
| currentState=
* http://techbase.kde.org
* http://wiki.kde.org
* http://wiki.koffice.org
| getInvolved=
* {{KDEML|kde-www}}
| people=
* [[User:Danimo|Danimo]] is the MediaWiki admin for techbase.kde.org.
| futureWork=
}}

techbase.kde.org is a [http://www.mediawiki.org MediaWiki] powered site used for collaborating on technical tasks such as tutorials, schedules, and project information. wiki.kde.org is a tiki-wiki site with the same function. Both are actively used. It might make sense to merge the two sites.

{{SEFBox
| name=API documentation
| currentState=
* [http://www.stack.nl/~dimitri/doxygen/ Doxygen] is used to generate api documentation from documentation strings in code.
| getInvolved=
* [[Development/Tutorials/API_Documentation|APIDOX tutorials]] Make KDE API docs better.
| people=
* [http://www.kdedevelopers.org/blog/1451 Allen Winter] administers api.kde.org.
| altTools=
* [http://labs.trolltech.com/blogs/2008/06/20/introducing-doxygen2qthelp-create-qch-files-from-doxygen-finally/ doxygen2qthelp] used by trolltech to create qt documentation.
}}

KDE API documentation is generated nightly and hosted on http://api.kde.org. It is also possible to generate the same documentation locally for use in an IDE for example.

It is possible to create [http://www.kdedevelopers.org/node/3010 man pages] and [http://thread.gmane.org/gmane.comp.kde.devel.core/55578 qthelp documentation] from kde sources.

{{SEFBox
| name=User documentation
| currentState=
* http://userbase.kde.org
* [http://i18n.kde.org/docs/doc-primer/check-docs.html meinproc] is used to generate user documentation.
* {{KDEML|kde-docbook}} Records all SVN commits with the <tt>GUI</tt> magic word.
| getInvolved=
* http://userbase.kde.org Create tutorials and tips.
* {{KDEML|kde-doc-english}} Used to coordinate user documentation.
* {{KDEML|kde-docbook}} Help update documentation after GUI changes.
}}

User documentation is generated from module doc/ folders and hosted on http://docs.kde.org.

meinproc is a KDE tool (written by Stephen Kulow which uses libxslt to transform docbook into (bzipped) html. At runtime kio_help opens that bzipped html and displays it to the user in khelpcenter.

http://userbase.kde.org is intended to be the primary source of user documentation on the web. Content will possibly be packaged for offline use in the future.

== Testing and Quality ==

{{SEFBox
| name=Bug tracking
| currentState=
* [http://bugs.kde.org/ Bugzilla 3.0.x].
* KBugBuster
| people=
* [http://mattr.info:8080/blog/?s=bugzilla Matt Rogers] and the KDE sysadmin team maintain the KDE bugzilla installation.
| getInvolved=
* {{KDEML|kde-core-devel}} Discuss alternative bug trackers for KDE.
* {{KDEML|kde-bugs-dist}} Records all updates on bugs.kde.org.
* {{KDEML|kdelibs-bugs}} Records all updates to kdelibs bugs.
* {{KDEML|konq-bugs}} Records all updates to konqueror bugs.
* {{KDEML|kdevelop-bugs}} Records all updates to kdevelop bugs.
* {{KDEML|amarok-bugs-dist}} Records all updates to amarok bugs.
| altTools=
* https://bugs.launchpad.net, [http://www.sourcecode.de/content/leonov-launchpad-desktop-client-first-coming Leonev]
* [http://trac.edgewall.org/ trac]
* [http://www.redmine.org/ Redmine] - kind of "Trac on Rails"
}}

Bug tracking in KDE currently is managed using Bugzilla 3.0. Work was recently merged on a transition to Bugzilla 3.0 from Bugzilla 2.16. There is still cleanup work going on but most features of the previous Bugzilla installation already work.

Bugzilla can be difficult to use and daunting to newbies.

{{SEFBox
| name=Static code analysis
| currentState=
* [http://www.englishbreakfastnetwork.org/krazy/ Krazy] hosted at EnglishBreakfastNetwork (EBN).
* [http://www.coverity.com/ Coverity] is used to find possible sources of defects and suggested optimizations. Results are displayed per module as part of [http://ktown.kde.org/~dirk/dashboard/ Dirks Dashboard builds].
| people=
* [http://people.fruitsalad.org/adridg/bobulate/ Adriaan de Groot]
* [http://www.kdedevelopers.org/blog/1451 Allen Winter]
| getInvolved=
*
}}

Additional checks are always welcome for adding to Krazy. See http://websvn.kde.org/trunk/quality/.

{{SEFBox
| name=Build testing
| currentState=
* [http://developer.kde.org/~dirk/dashboard/ Continuous build server] reports broken builds on linux.
* [http://www.cdash.org/CDash/index.php?project=kdelibs CDash build server] stores results of non-linux builds for kdelibs.
| getInvolved=
* {{KDEML|kde-core-devel}} Find out how to submit test build results.
| people=
* [http://wire.dattitu.de/authors/2-Dirk Dirk Mueller] maintains the dashboard
* Bill Hoffman is involved with the kitware CDash service.
* http://www.cdash.org/mailinglist.html
}}

There is interest in more build testing for KDE especially on non-linux platforms. Improvements include some standard ctest scripts that can be used to build and submit a dashboard result for kdelibs to CDash. This would be run on a cronjob for simplicity.

Builds are planned for the following platforms:

* Windows
* MacOS
* FreeBSD 6 (gcc)
* FreeBSD 7 (gcc)
* Solaris (S10, S11) on SPARC and amd64

{{SEFBox
| name=Unit testing
| currentState=
[[Development/Tutorials/Unittests|Unit tests]] may be written with the QTest framework. Tests can be run with the command '<tt>make test</tt>'.
| getInvolved=
* [[Development/Tutorials/Unittests|Techbase Unit tests tutorial]]
}}

It may be possible run run these tests automatically possibly on EBN or on Dirks dashboard.

{{SEFBox
| name=Quality testing
| currentState=
* The early adopter/user community
* [http://www.sqo-oss.eu/news/coverage/sqo-oss-project-launched-with-kde SQO-OSS]
| people=
* [http://people.fruitsalad.org/adridg/bobulate/ Adriaan de Groot]
* [http://hemswell.lincoln.ac.uk/~padams/index.php Paul Adams]
| getInvolved=
}}

It may be possible to obtain metrics such as bugs per kloc, defect injection rate etc.

{{SEFBox
| name=Profiling and Optimizations
| currentState=
* {{KDEML|kde-optimize}} mailing list coordinates optimizations in KDE.
* Krazy and Coverity tools also include some optimization checks.
* KDE macros for optimization of common algorithms.
| getInvolved=
* {{KDEML|kde-optimize}}
* [http://ktown.kde.org/~dirk/dashboard/4.1/i386/kdelibs.html Coverity report for KDE libs].
}}

Tutorials may be provided in the future to help developers optimize their code.

{{SEFBox
| name=Accessibility and Usability
| currentState=
* http://usability.kde.org/
* http://openusability.org/projects.php
* Season of usability
| people=
* [http://weblog.obso1337.org/ Celeste Lyn Paul]
* [http://ellen.reitmayr.net/index.php/blog Ellen Reitmayr]
| getInvolved=
* {{KDEML|kde-usability}}
* [[Projects/Usability/HIG KDE Human interaction Guidelines]].
}}

{{SEFBox
| name=Research
| currentState=
* http://research.kde.org
* [http://www.sqo-oss.eu/news/coverage/sqo-oss-project-launched-with-kde SQO-OSS]
* http://nepomuk.kde.org/ Semantic desktop project funded by the EU.
| people=
* [http://people.fruitsalad.org/adridg/bobulate/ Adriaan de Groot]
* [http://www.kdedevelopers.org/blog/2904 Sebastian Trueg] leads the kde-nepomuk project.
| getInvolved=
* [http://lists.semanticdesktop.org/mailman/listinfo/nepomuk-kde Nepomuk KDE mailing list]
}}

== Marketing and Expectations ==

{{SEFBox
| name=Requirements Gathering
| currentState=
* Requirements come from user feedback on http://bugs.kde.org and from commercial interests.
* Developers may do some research into requirements for applications based on User Research Profiles.
| getInvolved=
* http://bugs.kde.org Fill new wishlist items.
* {{KDEML|kde-core-devel}} Discuss new ways for kde to gather requirements.
}}

{{SEFBox
| name=Promotion
| currentState=
* The {{KDEML|kde-promo|KDE marketing team}} manage marketing and promotion from official kde sources.
* http://dot.kde.org is the community forum around promotional announcements.
* http://www.kde.org/announcements is the official source of promotional announcements regarding KDE.
* Design and maintenance of KDE websites is organised on the [https://mail.kde.org/mailman/listinfo/kde-www kde-www mailing list]
* The [http://ev.kde.org/workinggroups/mwg.php Marketing working group] coordinates several marketing efforts such as promoting planning and branding.
* KDE e.v provides a booth box for conference booths containing posters, leaftlets and other information needed at a conference stand.
| people=
* [http://wadejolson.wordpress.com/ Wade Olsen]
* [http://troy-at-kde.livejournal.com/ Troy Unrau]
* [http://nowwhatthe.blogspot.com/ Jos Poortvliet]
| getInvolved=
* {{KDEML|kde-promo}}
* [http://dot.kde.org/addPostingForm Submit dot articles]
}}

{{SEFBox
| name=Community management
| currentState=
* The Community Working Group helps with community advice when needed
* [http://www.kde.org/code-of-conduct/ Code of Conduct] Based on the Ubuntu Code of Conduct, documents guidelines for acceptable behaviour within the community. Can be summarized as 'Be Excellent to Eachother'.
| people=
* Anne Willson
* [http://jucato.org Juan Carlos Torres]
* [http://lydiapintscher.de Lydia Pintscher]
* Martin Fitzpatrick
* [http://omat.nl Tom Albers]
| getInvolved=
* Send an e-mail to community-wg@kde.org
}}

{{SEFBox
| name=Communication
| currentState=
Developers communicate with each other through
* [http://lists.kde.org/ mailing lists]
* [http://searchirc.com/irc-kde-1 IRC]
* [http://planetkde.org Blogs]
* Conferences
Developers communicate with users though
* [http://planetkde.org Blogs] to some extent (mainly early adopting users).
* [http://forum.kde.org Forums] to some extent where the developer chooses to.
* [http://dot.kde.org News announcements]
Users communicate with each other and developers through
* [http://forum.kde.org Forums]
* {{KDEML|kde}} mailing list
* #kde irc channel.
| people=
* [http://c133.org/blog/ Chris Lee] administers planetkde.org
| getInvolved=
* Add your blog to planet kde if you contribute to KDE in some way, including development, testing, advocacy, translation, documentation etc.
}}

== Release ==

{{SEFBox
| name=Release Scheduling
| currentState=
* Maintained at [[Schedules]].
| people=
*
* [http://cyrilleberger.blogspot.com/ Cyrill Berger] - KOffice release coordinator.
* [http://www.kdedevelopers.org/blog/1451 Allen Winter] - KDEPIM release coordinator.
| getInvolved=
* {{KDEML|release-team}}
}}

{{SEFBox
| name=Feature planning
| currentState=
* [[Schedules/KDE4/4.1_Feature_Plan]]
* [[Schedules/KDE4/4.2_Feature_Plan]]
| people=
[https://mail.kde.org/mailman/listinfo/release-team The KDE release team]
| altTools=
* Launchpad.net offers a blueprints system.
* [http://wiki.pentaho.com/display/OpenScrum/Home Scrum in Open Source Projects]
| getInvolved=
* {{KDEML|kde-core-devel}} - Discuss the KDE approach to feature planning.
}}

Currently techbase is used for feature planning but there may be better alternatives.

{{SEFBox
| name=Downstream packagers and contributions
| currentState=
* Many distributions package KDE3 & KDE4.
| getInvolved=
* {{KDEML|kde-packagers}} - Private mailing list for packagers. Includes information relating to security releases.
}}

== Theming and Translations ==

{{SEFBox
| name=Artwork
| currentState=
* The {{KDEML|kde-artists|kde-artists team}} creates offical artwork for KDE.
* kde-look.org for non-offical artwork.
| people=
* [http://pinheiro-kde.blogspot.com/ Nuno Pinheiro]
| getInvolved=
* {{KDEML|kde-artists}}
}}

Additional contributed artwork is available on http://kde-look.org.

There may be a need to create tutorials on how to create artwork for kde.

{{SEFBox
| name=Translation
| currentState=
* http://i18n.kde.org/ is used for level of completion of translations in KDE.
* GNU gettext is used for translation in KDE.
* <tt>.po</tt> files are edited directly in KDE svn to update translations.
* A kde4 based translation client (lokalize) is being developed in kdesdk/.
* Krazy includes sanity checks/plurals checking for translation.
| altTools=
launchpad.net features a web-based tool called rosetta, which allows for easier fly-by translations. This is considered not to be useful as fly-by translators often do not follow guidelines or consistency rules when translating.
| getInvolved=
* {{KDEML|kde-i18n-doc}}
}}

== Legal And Support ==
{{SEFBox
| name=KDE e.v. - Representative Legal Entity
| currentState=
* [http://ev.kde.org KDE e.v] is a registered non-profit organization that represents the KDE Project in legal and financial matters.
| altTools= N/A
| getInvolved=
* [http://ev.kde.org/getinvolved/ KDE e.v. membership]
}}

{{SEFBox
| name=Resolving licencing issues.
| currentState=
* A [http://ev.kde.org/announcements/2008-08-22-fsfe-welcomes-fla.php Fiduicary Licence Agreement] is available, which will allow KDE developers to optionally assign copyright of their contributions to KDE e.v. This would allow easier relicencing of contributors content in the event that KDE needs to move to another licence. It also allows the e.v. to more easily represent the work in the unlikely event of a court dispute involving KDE code.
* [[Policies/Licensing_Policy|KDE licencing policy]] allows commercial and non-commercial development and proprietry and non-proprietry development.
* [[Projects/KDE_Relicensing|Projects/KDE_Relicensing]] Effort to relicence KDE code to use version 3 of GNU GPL and LGPL. This work is unfinished but not still being performed. Many contributors are no longer contactable.
| altTools= N/A
}}

{{SEFBox
| name=Sponsorship and Patronship
| currentState=
* [http://ev.kde.org/supporting-members.php Supporters of KDE] contribute sponsorship money to KDE e.v.
* http://ev.kde.org/getinvolved/supporting-members.php
| altTools= N/A
}}

Projects/PIM/Akonadi/Meeting2008-11

2008-10-20T10:00:20Z

Steveire: /* Attendees */ Add myself.

This page is all about the Akonadi Meeting.

Date: Oct 31th (friday) to Nov 2nd (sunday).

== Location/links: ==
* http://www.linuxhotel.de/
* http://www.linuxhotel.de/community.html (community prices / rules)
* http://www.linuxhotel.de/community.en.html (limited info in eng)
* http://www.linuxhotel.de/anreise.html (how to get there)

== Attendees ==

{| class="wikitable"
|-
! Name
! Travel
! Arrival
! Departure
! Roomtype
|-
| Volker Krause
| train
| 31
| 2
| single
|-
| Till Adam
| train
| 31
| 2
| single
|-
| Tom Albers
| car
| 31 (m)
| 2 (e)
| single
|-
| Thomas McGuire
| train
| 31
| 2
| single
|-
| Kevin Krammer
| plane
| 31 (m)
| 2 (e)
| shared with Will
|-
| Will Stephenson
| train
| 31
| 2
| shared with Kevin
|-
| Bertjan Broeksema
| car (toma)
| 31 (m)
| 2 (e)
| shared with ingo
|-
| Ingo Klöcker
| train
| 31 (m)
| 2 (e)
| shared with Bertjan
|-
| Igor Trindade Oliveira
| plain/car (toma)
| 31 (m)
| 2 (e)
| shared with Dmitry if needed
|-
| Stephen Kelly
| plane/train
| 31 (m)
| 2 (e)
| shared
|-
|}

m = morning
e = evening

- Room reservations are out for these 7 rooms ( 4 single and 3 shared).
- This reservation is confirmed by LinuxHotel.

== Costs ==

Per person for the location:
* 5 euro per person per day for the conference room -> 3 days * 5 euro = 15 euro
* 15 euro per person per night for a double room -> 2 nights * 15 euro = 30 euro
* or 30 euro per person per night for a single room -> 2 nights * 30 euro = 60 euro
* 5 euro per person per day for the breakfast -> 2 (sat, sun) * 5 = 10 euro
* 5 euro per person for the cleaning -> 5 euro
These costs are payed by the eV directly.

You need to pay for all the food and drinks not included in the price above. Rumors say beer is included ;-) All those payments are not refundable.

Travel costs are refundable, by filling out the form from: http://ev.kde.org/resources/expense_report.pdf

For Igor there has been made a special arrangement.

== Arrange / Todo list ==
If you want to do any of the items on the list, add your sig to it!
* some webcams so people can join the event remotely. At least Brad and Tobias want to join in. (I can bring webcams. Functioning software is another matter - don't expect kopete webcam to work... [[User:Bille|Bille]])

== Agenda ==
* Presentation about Akonadi Test framework

Schedules/KDE4/4.2 Feature Plan

2008-10-10T19:40:51Z

Steveire: /* kdepim */ Some KJots items

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

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

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|System Settings|add Administrator mode button|alediaferia@gmail.com|Alessandro Diaferia}}
{{FeatureDone|Eigen|Make Eigen 2 ready for KDE, and move it to kdesupport|jacob@math.jussieu.fr|Benoît Jacob}}
{{FeatureInProgress|Eigen|Port all Eigen-using code in KDE and KOffice to Eigen 2.0|jacob@math.jussieu.fr|Benoît Jacob}}
{{FeatureInProgress|KNotify|Create OSD based replacement for current KPassivePopup|ben()eclipse.endoftheinternet.org|Ben Cooksley}}
{{FeatureTodo|Dikku Context Framework|Create a context framework with working activities|harikrishna.anandhan@gmail.com|Harikrishna Anandhan}}
|}

= 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
{{FeatureInProgress|kross|Extend QtScript integration.|mail@dipe.org|Sebastian Sauer}}
{{FeatureInProgress|KDEPrint|Reintroduce KDEPrint in some form, depending on what Qt4.4 delivers.|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|KDEPrint|Migrate FilePrinter class from Okular to enable file printing for all apps via QPrinter, modify to utilise new Qt4.4 features. To be discussed on k-c-d first.|john@layt.net|John Layt}}
{{FeatureTodo|KCalenderSystem|Add new calendar systems: Indian Civil (Saka), Ethiopean, Chinese, Pure Julian, Pure Gregorian. (Note, not all may live in kdelibs or be available as a global calendar system)|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Implement KLocale based methods to return weekend days and day of religious observance. Currently KCalendarSystem provides dayOfPray(), but for Gregorian this is not correct in all locales where it is used. Currently KDatePicker hardcodes Saturday and dayOfPray() as weekend days which may not be correct in all locales. To be discussed first on k-c-d and with kdepim.|john@layt.net|John Layt}}
{{FeatureTodo|Phonon|add Port class for fine grained control over data flow between Phonon objects|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|make AbstractMediaStream/StreamInterface threadsafe|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|"low-level" PCM I/O with at least an ALSA implementation|kretz@kde.org|Matthias Kretz and Ian Monroe}}
{{FeatureInProgress|Phonon|VideoWidget snapshot function|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|KConfig|API review and export KConfigBackend|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|KConfig|Make KConfigSkeleton KConfigGroup aware|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|KConfig|Make KConfigDialog work nicer with KConfigSkeleton + manually managed widgets|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|KUrlNavigator|Provide an option to always show the full path in the breadcrumb mode.|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|Katepart|Make a Vi input mode for Katepart|ehamberg@gmail.com|Erlend Hamberg}}
{{FeatureTodo|KIO::Global|Make KDynamicJobTracker do the checking if the kuiserver service is registered or not, for full implementation of "Progress in the same window"|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureTodo|KJS|Further performance improvements, in particular variable access (Blizzard stage 2), and calling convention (FrostByte stage 2)|maksim@kde.org|Maksim Orlovich}}
{{FeatureInProgress|KJS and KHTML|Support for transparent reindenting of standalone sources in debugger, debug info management improvements|maksim@kde.org|Maksim Orlovich}}
{{FeatureInProgress|KHTML|SVG support in KHTML (port from WebKit)|tsjoker@gmail.com|Vyacheslav Tokarev}}
{{FeatureInProgress|KHTML|Use of IDString (hashed strings) for local names, prefixes and namespaces in DOM core instead of document-related ids, in particular for better API compatibility with WebCore|tsjoker@gmail.com|Vyacheslav Tokarev}}
{{FeatureTodo|KHTML|Scriptable extension plug-ins|porten@kde.org|Harri}}
{{FeatureDone|kwallet|Move kwalletd to kdebase-runtime|dfaure@kde.org|David Faure}}
{{FeatureInProgress|kdeui|Rich text builders for KTextEdit, including BBCode, html, plain text markup, mediawiki and markdown output.|steveire@gmail.com| Stephen Kelly}}
{{FeatureDone|i18n|proper filenames decoding for FAT mounting, in KUrls and content-disposition|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureDone|Kross|expose KAssistantDialog as part of forms module|shafff-at-ukr.net|Nick Shaforostoff}}
|}

= 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
{{FeatureTodo|Color KCM|Add 'smart setting' of extended colors|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|Color KCM|Add KDE3 scheme import|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|Color KCM|Query kwin for supported colors; add full set of kwin colors|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|KDEPrint|reintroduce KDEPrint Print Management tools, e.g. KCM, kprinter, kjobviewer, etc. Depends upon progress of kdelibs side of KDEPrint and Qt4.4 feature set.|john@layt.net|john Layt}}
{{FeatureDone|Power Manager|import PowerDevil|drf@kdemod.ath.cx|Dario Freddi}}
|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |KRunner
{{FeatureInProgress|Krunner|Configuration options for blacklisting, user ranking, runner ranking, learning|mumismo@gmail.com|Jordi Polo}}
{{FeatureInProgress|Krunner|SearchMatch configuration|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Krunner|Simple learning|mumismo@gmail.com|Jordi Polo}}
{{FeatureTodo|Krunner|Simple GUI for above options|mumismo@gmail.com|Jordi Polo}}
{{FeatureTodo|Krunner|Runners able to share parsing|mumismo@gmail.com|Jordi Polo}}
{{FeatureTodo|Krunner|Noun-Verb support|ryan.bitanga@gmail.com|Ryan P. Bitanga}}
{{FeatureTodo|Krunner|Implement Nuno's UI polishings|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Krunner|Runtime syntax documentation|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Krunner|Runner configuration|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Krunner|Search set paging|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|KRunner|runner for the plasma dbus interface|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|KRunner|Konqueror history runner|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|KRunner|Kate sessions runner|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|KRunner|Recent Documents runner|sebas@kde.org|Sebastian Kügler}}
|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |Plasma - Priority Features
{{FeatureTodo|Plasma|Welcome plasmoid|aseigo@kde.org|Aaron Seigo}}{{FeatureInProgress|Plasma|JOLIE Integration|ervin@kde.org|Kevin Ottens}}
{{FeatureInProgress|Plasma|Notification plasmoid|dimsuzkde@gmail.com|Dmitry Suzdalev}}
{{FeatureInProgress|Plasma|Kuiserver plasmoid|r.scheepmaker@student.utwente.nl|Rob Scheepmaker}}
{{FeatureTodo|KWin|Make it possible to focus plasma panels|chanika@gmail.com|Chani}}
{{FeatureTodo|Plasma|panel->desktop dragging|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Expand cashew to full action bar when zoomed out|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|Plasmagik packaging (and package classes)|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureInProgress|Plasma|Networkmanager Plasmoid and DataEngine|cblauvelt@gmail.com|Christopher Blauvelt}}
{{FeatureInProgress|Plasma|New ECMA Script Scriptengines|richmoore44@gmail.com|Richard Moore}}
{{FeatureDone|Plasma|Extenders|r.scheepmaker@student.utwente.nl|Rob Scheepmaker}}
{{FeatureDone|Plasma|Wallpaper plugins|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|Separate Desktop Settings from DesktopContainment|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Script Security Framework|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|Python support|simon@simonzone.com|Simon Edwards}}
|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |Plasma
{{FeatureDone|Plasma|Plasma Popup Tips|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|Collapsing Applet convenience class|aseigo@kde.org|Aaron Seigo}}

{{FeatureInProgress|Plasma|Taskbar grouping|hrigi_1@hotmail.com|Christian Mollekopf}}
{{FeatureInProgress|Plasma|Weather plasmoid|shawn.starr@rogers.com|Shawn Starr}}
{{FeatureInProgress|Plasma|Small Form Factors|m.kruisselbrink@student.tue.nl|Marijn Kruisselbrink}}
{{FeatureDone|Plasma|Plasma On Screensaver|chanika@gmail.com|Chani Armitage}}
{{FeatureInProgress|Plasma|Website update|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|Grid applet|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|Plasma|Techbase Tutorials|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Context menu plugins|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Add New Widgets: Pluggable widget browser|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Activity<->Virtual Desktop Affinity|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Optional Per-Virtual Desktop DesktopView|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Make non-SVG painting in Plasma low-color and non-anim friendly|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Runtime DataEngine documentation (sources, usage, etc)|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|Panel Autohide|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Keyboard Shortcut Config UI|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Systray++ Spec|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|Save icon positioning in folderview|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|New wallpapers|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|Import Raptor|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|Preserve wallpaper choice by copying user paper to home dir|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|New way of handling wallpapers and different sizes (package format, and so on...)|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|Top-level windows plasmoids|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|drop indicator in panel|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|improve usability of appletbrowser delete button|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|adding containments from the appletbrowser (and remove the "add panel" from DefaultDeskrop)|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|highlight the applet with active keyboard shortcuts|chanika@gmail.com|Chani}}
{{FeatureTodo|Plasma|dbus interface|chanika@gmail.com|Chani}}
{{FeatureDone|Plasma|make the panel controller a bit more usable|notmart@gmail.com|Marco Martin}}
{{FeatureDone|Plasma|nicely draw the desktop toolbox when it's moved because of a panel|notmart@gmail.com|Marco Martin}}
{{FeatureDone|Plasma|theme Plasma::PushButton with svg|notmart@gmail.com|Marco Martin}}
{{FeatureDone|Plasma|Tabbar widget derived from QTabBar and themed with svg|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|Complete the panel size sliders feature: an applet can ask the panel to resize|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|New theming capabilities by expanding the lower level theming classes (Theme and PanelSvg)|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|Activitybar: an applet to quickly switch between activities|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|A new plasmoid that implements the functionality of a simple web browser|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|Wallpaper plugin: Mandelbrot fractal explorer|jacob@math.jussieu.fr|Benoît Jacob}}
{{FeatureDone|Plasma|Google Gadgets support|idlecat511@gmail.com|Tiger Dong}}
{{FeatureTodo|Plasma|Add Google Gadgets from Internet through AppletBrowser|idlecat511@gmail.com|Tiger Dong}}
|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |KWin - Core
{{FeatureDone|KWin|New window snapping zones; screen center and window corners|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureDone|KWin|Move maximized windows between Xinerama screens|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureInProgress|KWin|Basic window tiling|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureInProgress|KWin|Compositing decoration API additions|lmurray@undefinedfire.com|Lucas Murray}}
|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |KWin - Desktop Effects
{{FeatureInProgress|KWin|Compositing self-check|l.lunak@kde.org|Luboš Luňák}}
{{FeatureDone|KWin|Global animation speed setting|l.lunak@kde.org|Luboš Luňák}}
{{FeatureDone|KWin|Motion dynamics|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureInProgress|KWin|New shadow handling by decorations|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureDone|KWin|Improved UI for selecting window/desktop switcher|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|KWin|UI for assigning effects to screen edges|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KWin|Cube/Cylinder/Sphere Effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KWin|Magic Lamp minimize Effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KWin|Animation in BoxSwitch Effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|KWin|Mouse interaction for CoverSwitch Effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|KWin|Additional thumbnails for CoverSwitch Effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|KWin|Improved Snow Effect; different sizes, better randomness and different directions|torgny.johansson@gmail.com|Torgny Johansson}}
{{FeatureTodo|KWin|Shader for Snow Effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KWin|Improved desktop grid|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureDone|KWin|New present window layout modes|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureDone|KWin|Invert only selected windows|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureInProgress|KWin|Improved mouse mark/scribble 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
{{FeatureInProgress|KCal Library|Make the KCal library dependent on the external libical package (from freeassocation) rather than our own old, forked version.|winter@kde.org|Allen Winter}}
|}

= 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|MSNP15 implementation for MSN|mattr@kde.org|Matt Rogers}}
{{FeatureInProgress|Kopete|UPnp Support|mattr@kde.org|Matt Rogers}}
{{FeatureInProgress|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}}
{{FeatureInProgress|Kopete|Contacts plasmoid|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Kopete|Move file transfer request into chat window|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureInProgress|Kopete|Message delivery notifications|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureTodo|Kopete|Improve file transfer progress dialog|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureInProgress|KGet|MultiSource-Downloading|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureInProgress|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|Plasma|Network Manager Applet|cblauvelt@gmail.com|Christopher Blauvelt}}
{{FeatureInProgress|KRDC|NX support|gdavid.devel@gmail.com|David Gross}}
{{FeatureDone|KRDC|Greatly improve experience for LDAP (e.g. MS Active Directory) administrators|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|KRDC|Improve per-host settings (remember scaling mode and other options) |gpothier@gmail.com|Guillaume Pothier}}
{{FeatureTodo|KRDC|Minimal-clutter mode to optimize screen real estate usage|gpothier@gmail.com|Guillaume Pothier}}
|}

= 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
{{FeatureDone|KonsoleKalendar|Add an option to support resources that might need a GUI (i.e. all resources)|kevin.krammer@gmx.at|Kevin Krammer}}
{{FeatureInProgress|Akregator|Support for syncing the feed list with Google Reader |osterfeld@kde.org|Frank Osterfeld}}
{{FeatureInProgress|KAlarm|Improve alarm edit and preferences dialog layouts|djarvie@kde.org|David Jarvie}}
{{FeatureInProgress|KAlarm|Add holidays support|djarvie@kde.org|David Jarvie}}
{{FeatureInProgress|Kleopatra|OpenPGP support|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureInProgress|KNotes|Zeroconf support for sending notes on LAN|qbast@go2.pl|Jakub Stachowski}}
{{FeatureDone|Kontact|New Planner summary; combines Appointment+To-do+SpecialDates into 1 pretty summary|o_timocin@gmx.de|Oral Timocin}}
{{FeatureInProgress|KPilot|Finish Keyring conduit, base conduit code and test cases, category syncing|jkasper@kde.org|Jason 'vanRijn' Kasper}}
{{FeatureTodo|Akregator|Basic support for enclosures (Displaying links, mimetype and size)|osterfeld@kde.org|Frank Osterfeld}}
{{FeatureTodo|[http://kblogger.pwsp.net KBlogger]|KBlogger, a blogging application| christian_weilbach@.web.de|Christian Weilbach}}
{{FeatureTodo|Kleopatra|Konqueror and Dolphin Kleopatra plugins|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureDone|KMail|Aggregated attachment view in the mail header area of the reader window|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KMail|Merge the new message list from the SoC branch|mcguire@kde.org|Thomas McGuire}}
{{FeatureTodo|Kontact|Support for Kontact wide profiles|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Drag and drop in the free-busy view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Support for comments in replies to invitations|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Support for extended free-busy lists|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KPilot|Port old conduits to new base conduit architecture and KDE4/Qt4|jkasper@kde.org|Jason 'vanRijn' Kasper}}
{{FeatureTodo|KBlogger|Port to use KRichTextEdit (Or KMEditor)|steveire@gmail.com|Stephen Kelly}}
{{FeatureTodo|KNode|Port to use KRichTextEdit (Or KMEditor)|steveire@gmail.com|Stephen Kelly}}
{{FeatureInProgress|Kjots| Import notes from KnowIt as KJots pages. |steveire@gmail.com|Stephen Kelly}}
{{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}}
{{FeatureTodo|Kontact|Tip-of-the-Day summary|molkentin@kde.org|Daniel Molkentin}}
|}

= 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|Okteta|add Kate-like search tool|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|refactor KByteArrayView|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|parameter dialog for "Copy as..."|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}}
{{FeatureInProgress|Ark|Implement proper drag/drop between Ark/dolphin|harald((at))stud(dot)ntnu.no|Harald Hvaal}}
{{FeatureInProgress|Ark|Make the service menu work (possibly doing it as a KonqPopupPlugin|harald((at))stud(dot)ntnu.no|Harald Hvaal}}
{{FeatureInProgress|Ark|Proper password support|harald((at))stud(dot)ntnu.no|Harald Hvaal}}
{{FeatureTodo|Ark|Support for custom options from the compression interface (eg. a slider for selecting compression level for rar files)|harald((at))stud(dot)ntnu.no|Harald Hvaal}}
{{FeatureTodo|Ark|Add an options dialog (maybe)|harald((at))stud(dot)ntnu.no|Harald Hvaal}}
{{FeatureInProgress|kwalletmanager|Move kwalletmanager to the Model/View architecture and redesign the UI|lemma@confuego.org|Michael Leupold}}
|}

= 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
{{FeatureDone|krosspython and krossruby|Support custom types via handlers|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|krosspython and krossruby|Support QList<CustomType*> constructs|mail@dipe.org|Sebastian Sauer}}
{{FeatureInProgress|Smoke|Wrap some more APIs (at least Akanodi for all languages and Plasma for C#)|kde-bindings@kde.org|KDE-bindings developers}}
{{FeatureInProgress|PyKDE|KCM support and other plugins|simon@simonzone.com|Simon Edwards}}
{{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|Unittests++|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
{{FeatureInProgress|libkdegames|New highscore management system|milliams|Matt Williams}}
{{FeatureDone|kdiamond|Drag jewels|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|kdiamond|Optional OpenGL rendering|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|ksirk|Map scrolling arrows|kleag@free.fr|Gaël de Chalendar}}
{{FeatureDone|ksirk|KHotNewStuff skins|kleag@free.fr|Gaël de Chalendar}}
{{FeatureInProgress|ksirk|Jabber based net game finding|kleag@free.fr|Gaël de Chalendar}}
{{FeatureDone|ksirk|Use only names in skins instead of numeric ids|kleag@free.fr|Gaël de Chalendar}}
{{FeatureDone|ksirk|Skins editor|kleag@free.fr|Gaël de Chalendar}}
{{FeatureInProgress|ktron|Port and remake the KTron game for KDE 4.2|legolas@legolasweb.nl|Stas Verberkt}}
{{FeatureTodo|KNetWalk|Support for custom and non-square board sizes|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureTodo|KGoldrunner|Improvement to sound support and themes|mikelima@cirulla.net}}
{{FeatureTodo|KBlocks|Support for sounds|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureTodo|KMahjongg|Support for sounds|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureInProgress|Killbots|New app for 4.2|parker.coates@gmail.com|Parker Coates}}
|}

= 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
{{FeatureDone|Kate|Port and reenable the Snippets plugin.|jpetso@gmx.at|Jakob Petsovits}}
{{FeatureDone|perldoc KIOSlave|Add KIOSlave to allow reading Perldoc documentation.|michael.pyne@kdemail.net|Michael Pyne}}
{{FeatureInProgress|Lokalize|XLIFF support|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Lokalize|various Translation Memory enhancements|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureDone|Lokalize|wrap all windows belonging to one project into one MDI window|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Kross-based scripting|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|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|Port code generation wizard to QWizard and replace all q3 widgets|andi.fischer@hispeed.ch|Andi Fischer}}
{{FeatureInProgress|Umbrello|Replace all q3 widgets in the refactoring assistant|andi.fischer@hispeed.ch|Andi Fischer}}
|}

= 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
{{FeatureInProgress|KEduca|Rewrite of the classic test writing/taking application|matt@milliams.com|Matt Williams}}
{{FeatureTodo|KLettres|Number support|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KLettres|Theme manager|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureInProgress|KHangMan|Add a Open File action|annma@kde.org|Anne-Marie Mahfouf}}
{{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|KLettres|Visual indicator when letter is wrong|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Kalzium|Port Kalzium's periodic table to use new QGraphicsView.|marcus@cryos.org|Marcus D. Hanwell}}
{{FeatureInProgress|Kalzium|Plasmoid to access Kalzium database|cniehaus@kde.org|Carsten Niehaus}}
{{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}}
{{FeatureDone|KAlgebra|New parser (using QLALR) and new lexer|aleixpol@gmail.com|Aleix Pol}}
{{FeatureDone|KAlgebra|Import capability for MathML Presentation Markup in libanalitza|aleixpol@gmail.com|Aleix Pol}}
{{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|Parley|Declensions|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureInProgress|Parley|Rework main window infrastructure|d.laidig@gmx.de|Daniel Laidig}}
{{FeatureDone|KStars|Display millions of stars|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureDone|KStars|Tool to predict Conjunctions|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureInProgress|KStars|Earth Satellites|kstars@30doradus.org|Jason Harris}}
{{FeatureInProgress|KStars|Sky Calendar Tool|kstars@30doradus.org|Jason Harris}}
{{FeatureDone|KStars|Include HD Catalog Numbers (in search, in display)|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|Separate INDI From KStars|mutlaqja@ikarustech.com|Jasem Mutlaq}}
{{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|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|Harry de Valence}}
{{FeatureInProgress|Marble|Marble Plasmoid|hdevalence@gmail.com|Harry de Valence}}
{{FeatureInProgress|Marble|Qt-Version settings dialog|hdevalence@gmail.com|Harry de Valence}}
{{FeatureInProgress|Marble|Panoramio Support||Shashank Singh}}
{{FeatureInProgress|Marble|Twitter Plugin||Shashank Singh}}

{{FeatureInProgress|Marble|DGML2 Support|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Support for imperial units|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}}
{{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}}
{{FeatureDone|KTurtle|Export canvas as image|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureTodo|KTurtle|Optional rulers/grid for canvas units|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureDone|KTurtle|Add command line|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureDone|KTurtle|Add a color picker|nielsslot@gmail.com|Niels Slot}}
{{FeatureInProgress|KBruch|Usability Improvements|tiago.porangaba@ltia.fc.unesp.br|Tiago Porangaba}}
{{FeatureInProgress|KBruch|Merging KPercentage functionalities into KBruch|tiago.porangaba@ltia.fc.unesp.br|Tiago Porangaba}}
{{FeatureTodo|Kalzium|Visualization of Schemes and Gradients at same time|tiago.porangaba@ltia.fc.unesp.br|Tiago Porangaba}}
|}

= 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
{{FeatureInProgress|Dragon Player|Make Dragon indipendent from Xine|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|File Manager|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|play media dialog|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|slider changes|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|show info while playing audio files|ian.monroe@gmail.com|Ian Monroe}}
{{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}}
{{FeatureTodo|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
{{FeatureTodo|KMagnifier|Refactor color menu, re-add invert, break current color blindness code into "daltonize" and "simulate"|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|KMagnifier|Add color-shift modes to help people with color blindness|mw_triad@users.sourceforge.net|Matthew Woehlke}}
|}

= 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|KSnapshot|Add support for grabbing a single screen in multihead|rich@kde.org|Richard Moore}}
{{FeatureDone|KSnapshot|Increase jpeg image quality from 75% to 85%|rich@kde.org|Richard Moore}}
{{FeatureDone|KSnapshot|If we're saving the window decorations then record the window title and class in the image (if the format supports it) to play nice with indexers like strigi|rich@kde.org|Richard Moore}}
{{FeatureTodo|Okular|Sound annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Link annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Improve annotation support: for existing types (rubber stamps, line, note, etc), and for the way they are constructed and handled.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Caret annotations.|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Okular|Support for videos & movie annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Support .snp and .emf file formats|bradh@kde.org|Brad Hards}}
{{FeatureDone|Gwenview|Support for animated images (.gif and .mng)|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureInProgress|Gwenview|Red Eye Reduction|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureInProgress|Gwenview|Nepomuk integration|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Dolphin-like single-click selection|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Optional tree view|aurelien.gateau@free.fr|Aurélien Gâteau}}
|}

= 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
{{FeatureDone|kio_bookmarks|A new konqueror home page displaying user bookmarks. See [[http://kde-apps.org/content/show.php?content=86516 description]]|xavier.vello@gmail.com|Xavier Vello}}
{{FeatureInProgress|kuiserver|KUiServer Goya port. General improvements for usability improvements|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureInProgress|kio fish/sftp|port fish and sftp to windows|brandon.ml@gmail.com|Carlo Segato}}
|}

= 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
{{FeatureTodo|konqueror|A new konqueror recover-dialog replacement|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureTodo|konqueror|Rework bookmarks using Akonadi|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureInProgress|dolphin|Add zoom slider into the status bar and general zooming improvments|peter.penz@gmx.at|Peter Penz}}
{{FeatureDone|dolphin|Tooltip previews|peter.penz@gmx.at|Peter Penz}}
|}

= 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
{{FeatureTodo|PoTD engine|Import from playground|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Frame plasmoid|Honor EXIF rotation - see bug 164605|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Frame plasmoid|Previous, Pause and Next buttons - see bug 164704|annma@kde.org|Anne-Marie Mahfouf}}
|}

Schedules/KDE4/4.2 Feature Plan

2008-10-10T19:36:45Z

Steveire: /* kdelibs */ Add rich text builders plan.

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

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

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|System Settings|add Administrator mode button|alediaferia@gmail.com|Alessandro Diaferia}}
{{FeatureDone|Eigen|Make Eigen 2 ready for KDE, and move it to kdesupport|jacob@math.jussieu.fr|Benoît Jacob}}
{{FeatureInProgress|Eigen|Port all Eigen-using code in KDE and KOffice to Eigen 2.0|jacob@math.jussieu.fr|Benoît Jacob}}
{{FeatureInProgress|KNotify|Create OSD based replacement for current KPassivePopup|ben()eclipse.endoftheinternet.org|Ben Cooksley}}
{{FeatureTodo|Dikku Context Framework|Create a context framework with working activities|harikrishna.anandhan@gmail.com|Harikrishna Anandhan}}
|}

= 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
{{FeatureInProgress|kross|Extend QtScript integration.|mail@dipe.org|Sebastian Sauer}}
{{FeatureInProgress|KDEPrint|Reintroduce KDEPrint in some form, depending on what Qt4.4 delivers.|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|KDEPrint|Migrate FilePrinter class from Okular to enable file printing for all apps via QPrinter, modify to utilise new Qt4.4 features. To be discussed on k-c-d first.|john@layt.net|John Layt}}
{{FeatureTodo|KCalenderSystem|Add new calendar systems: Indian Civil (Saka), Ethiopean, Chinese, Pure Julian, Pure Gregorian. (Note, not all may live in kdelibs or be available as a global calendar system)|john@layt.net|John Layt}}
{{FeatureTodo|KLocale|Implement KLocale based methods to return weekend days and day of religious observance. Currently KCalendarSystem provides dayOfPray(), but for Gregorian this is not correct in all locales where it is used. Currently KDatePicker hardcodes Saturday and dayOfPray() as weekend days which may not be correct in all locales. To be discussed first on k-c-d and with kdepim.|john@layt.net|John Layt}}
{{FeatureTodo|Phonon|add Port class for fine grained control over data flow between Phonon objects|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|make AbstractMediaStream/StreamInterface threadsafe|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|"low-level" PCM I/O with at least an ALSA implementation|kretz@kde.org|Matthias Kretz and Ian Monroe}}
{{FeatureInProgress|Phonon|VideoWidget snapshot function|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|KConfig|API review and export KConfigBackend|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|KConfig|Make KConfigSkeleton KConfigGroup aware|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|KConfig|Make KConfigDialog work nicer with KConfigSkeleton + manually managed widgets|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|KUrlNavigator|Provide an option to always show the full path in the breadcrumb mode.|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|Katepart|Make a Vi input mode for Katepart|ehamberg@gmail.com|Erlend Hamberg}}
{{FeatureTodo|KIO::Global|Make KDynamicJobTracker do the checking if the kuiserver service is registered or not, for full implementation of "Progress in the same window"|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureTodo|KJS|Further performance improvements, in particular variable access (Blizzard stage 2), and calling convention (FrostByte stage 2)|maksim@kde.org|Maksim Orlovich}}
{{FeatureInProgress|KJS and KHTML|Support for transparent reindenting of standalone sources in debugger, debug info management improvements|maksim@kde.org|Maksim Orlovich}}
{{FeatureInProgress|KHTML|SVG support in KHTML (port from WebKit)|tsjoker@gmail.com|Vyacheslav Tokarev}}
{{FeatureInProgress|KHTML|Use of IDString (hashed strings) for local names, prefixes and namespaces in DOM core instead of document-related ids, in particular for better API compatibility with WebCore|tsjoker@gmail.com|Vyacheslav Tokarev}}
{{FeatureTodo|KHTML|Scriptable extension plug-ins|porten@kde.org|Harri}}
{{FeatureDone|kwallet|Move kwalletd to kdebase-runtime|dfaure@kde.org|David Faure}}
{{FeatureInProgress|kdeui|Rich text builders for KTextEdit, including BBCode, html, plain text markup, mediawiki and markdown output.|steveire@gmail.com| Stephen Kelly}}
{{FeatureDone|i18n|proper filenames decoding for FAT mounting, in KUrls and content-disposition|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureDone|Kross|expose KAssistantDialog as part of forms module|shafff-at-ukr.net|Nick Shaforostoff}}
|}

= 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
{{FeatureTodo|Color KCM|Add 'smart setting' of extended colors|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|Color KCM|Add KDE3 scheme import|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|Color KCM|Query kwin for supported colors; add full set of kwin colors|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|KDEPrint|reintroduce KDEPrint Print Management tools, e.g. KCM, kprinter, kjobviewer, etc. Depends upon progress of kdelibs side of KDEPrint and Qt4.4 feature set.|john@layt.net|john Layt}}
{{FeatureDone|Power Manager|import PowerDevil|drf@kdemod.ath.cx|Dario Freddi}}
|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |KRunner
{{FeatureInProgress|Krunner|Configuration options for blacklisting, user ranking, runner ranking, learning|mumismo@gmail.com|Jordi Polo}}
{{FeatureInProgress|Krunner|SearchMatch configuration|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Krunner|Simple learning|mumismo@gmail.com|Jordi Polo}}
{{FeatureTodo|Krunner|Simple GUI for above options|mumismo@gmail.com|Jordi Polo}}
{{FeatureTodo|Krunner|Runners able to share parsing|mumismo@gmail.com|Jordi Polo}}
{{FeatureTodo|Krunner|Noun-Verb support|ryan.bitanga@gmail.com|Ryan P. Bitanga}}
{{FeatureTodo|Krunner|Implement Nuno's UI polishings|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Krunner|Runtime syntax documentation|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Krunner|Runner configuration|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Krunner|Search set paging|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|KRunner|runner for the plasma dbus interface|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|KRunner|Konqueror history runner|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|KRunner|Kate sessions runner|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|KRunner|Recent Documents runner|sebas@kde.org|Sebastian Kügler}}
|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |Plasma - Priority Features
{{FeatureTodo|Plasma|Welcome plasmoid|aseigo@kde.org|Aaron Seigo}}{{FeatureInProgress|Plasma|JOLIE Integration|ervin@kde.org|Kevin Ottens}}
{{FeatureInProgress|Plasma|Notification plasmoid|dimsuzkde@gmail.com|Dmitry Suzdalev}}
{{FeatureInProgress|Plasma|Kuiserver plasmoid|r.scheepmaker@student.utwente.nl|Rob Scheepmaker}}
{{FeatureTodo|KWin|Make it possible to focus plasma panels|chanika@gmail.com|Chani}}
{{FeatureTodo|Plasma|panel->desktop dragging|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Expand cashew to full action bar when zoomed out|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|Plasmagik packaging (and package classes)|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureInProgress|Plasma|Networkmanager Plasmoid and DataEngine|cblauvelt@gmail.com|Christopher Blauvelt}}
{{FeatureInProgress|Plasma|New ECMA Script Scriptengines|richmoore44@gmail.com|Richard Moore}}
{{FeatureDone|Plasma|Extenders|r.scheepmaker@student.utwente.nl|Rob Scheepmaker}}
{{FeatureDone|Plasma|Wallpaper plugins|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|Separate Desktop Settings from DesktopContainment|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Script Security Framework|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|Python support|simon@simonzone.com|Simon Edwards}}
|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |Plasma
{{FeatureDone|Plasma|Plasma Popup Tips|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|Collapsing Applet convenience class|aseigo@kde.org|Aaron Seigo}}

{{FeatureInProgress|Plasma|Taskbar grouping|hrigi_1@hotmail.com|Christian Mollekopf}}
{{FeatureInProgress|Plasma|Weather plasmoid|shawn.starr@rogers.com|Shawn Starr}}
{{FeatureInProgress|Plasma|Small Form Factors|m.kruisselbrink@student.tue.nl|Marijn Kruisselbrink}}
{{FeatureDone|Plasma|Plasma On Screensaver|chanika@gmail.com|Chani Armitage}}
{{FeatureInProgress|Plasma|Website update|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|Grid applet|sebas@kde.org|Sebastian Kügler}}
{{FeatureInProgress|Plasma|Techbase Tutorials|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Context menu plugins|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Add New Widgets: Pluggable widget browser|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Activity<->Virtual Desktop Affinity|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Optional Per-Virtual Desktop DesktopView|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Make non-SVG painting in Plasma low-color and non-anim friendly|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Runtime DataEngine documentation (sources, usage, etc)|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|Panel Autohide|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Keyboard Shortcut Config UI|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|Systray++ Spec|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|Save icon positioning in folderview|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|New wallpapers|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|Import Raptor|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|Preserve wallpaper choice by copying user paper to home dir|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|New way of handling wallpapers and different sizes (package format, and so on...)|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|Top-level windows plasmoids|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureTodo|Plasma|drop indicator in panel|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|improve usability of appletbrowser delete button|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|adding containments from the appletbrowser (and remove the "add panel" from DefaultDeskrop)|aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|highlight the applet with active keyboard shortcuts|chanika@gmail.com|Chani}}
{{FeatureTodo|Plasma|dbus interface|chanika@gmail.com|Chani}}
{{FeatureDone|Plasma|make the panel controller a bit more usable|notmart@gmail.com|Marco Martin}}
{{FeatureDone|Plasma|nicely draw the desktop toolbox when it's moved because of a panel|notmart@gmail.com|Marco Martin}}
{{FeatureDone|Plasma|theme Plasma::PushButton with svg|notmart@gmail.com|Marco Martin}}
{{FeatureDone|Plasma|Tabbar widget derived from QTabBar and themed with svg|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|Complete the panel size sliders feature: an applet can ask the panel to resize|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|New theming capabilities by expanding the lower level theming classes (Theme and PanelSvg)|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|Activitybar: an applet to quickly switch between activities|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|A new plasmoid that implements the functionality of a simple web browser|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|Wallpaper plugin: Mandelbrot fractal explorer|jacob@math.jussieu.fr|Benoît Jacob}}
{{FeatureDone|Plasma|Google Gadgets support|idlecat511@gmail.com|Tiger Dong}}
{{FeatureTodo|Plasma|Add Google Gadgets from Internet through AppletBrowser|idlecat511@gmail.com|Tiger Dong}}
|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |KWin - Core
{{FeatureDone|KWin|New window snapping zones; screen center and window corners|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureDone|KWin|Move maximized windows between Xinerama screens|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureInProgress|KWin|Basic window tiling|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureInProgress|KWin|Compositing decoration API additions|lmurray@undefinedfire.com|Lucas Murray}}
|- border="1" cellpadding="5" cellspacing="0" style="border
! colspan="4" style="text-align: center" |KWin - Desktop Effects
{{FeatureInProgress|KWin|Compositing self-check|l.lunak@kde.org|Luboš Luňák}}
{{FeatureDone|KWin|Global animation speed setting|l.lunak@kde.org|Luboš Luňák}}
{{FeatureDone|KWin|Motion dynamics|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureInProgress|KWin|New shadow handling by decorations|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureDone|KWin|Improved UI for selecting window/desktop switcher|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|KWin|UI for assigning effects to screen edges|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KWin|Cube/Cylinder/Sphere Effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KWin|Magic Lamp minimize Effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KWin|Animation in BoxSwitch Effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|KWin|Mouse interaction for CoverSwitch Effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureTodo|KWin|Additional thumbnails for CoverSwitch Effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureInProgress|KWin|Improved Snow Effect; different sizes, better randomness and different directions|torgny.johansson@gmail.com|Torgny Johansson}}
{{FeatureTodo|KWin|Shader for Snow Effect|ubuntu@martin-graesslin.com|Martin Gräßlin}}
{{FeatureDone|KWin|Improved desktop grid|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureDone|KWin|New present window layout modes|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureDone|KWin|Invert only selected windows|lmurray@undefinedfire.com|Lucas Murray}}
{{FeatureInProgress|KWin|Improved mouse mark/scribble 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
{{FeatureInProgress|KCal Library|Make the KCal library dependent on the external libical package (from freeassocation) rather than our own old, forked version.|winter@kde.org|Allen Winter}}
|}

= 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|MSNP15 implementation for MSN|mattr@kde.org|Matt Rogers}}
{{FeatureInProgress|Kopete|UPnp Support|mattr@kde.org|Matt Rogers}}
{{FeatureInProgress|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}}
{{FeatureInProgress|Kopete|Contacts plasmoid|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Kopete|Move file transfer request into chat window|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureInProgress|Kopete|Message delivery notifications|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureTodo|Kopete|Improve file transfer progress dialog|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureInProgress|KGet|MultiSource-Downloading|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureInProgress|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|Plasma|Network Manager Applet|cblauvelt@gmail.com|Christopher Blauvelt}}
{{FeatureInProgress|KRDC|NX support|gdavid.devel@gmail.com|David Gross}}
{{FeatureDone|KRDC|Greatly improve experience for LDAP (e.g. MS Active Directory) administrators|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|KRDC|Improve per-host settings (remember scaling mode and other options) |gpothier@gmail.com|Guillaume Pothier}}
{{FeatureTodo|KRDC|Minimal-clutter mode to optimize screen real estate usage|gpothier@gmail.com|Guillaume Pothier}}
|}

= 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
{{FeatureDone|KonsoleKalendar|Add an option to support resources that might need a GUI (i.e. all resources)|kevin.krammer@gmx.at|Kevin Krammer}}
{{FeatureInProgress|Akregator|Support for syncing the feed list with Google Reader |osterfeld@kde.org|Frank Osterfeld}}
{{FeatureInProgress|KAlarm|Improve alarm edit and preferences dialog layouts|djarvie@kde.org|David Jarvie}}
{{FeatureInProgress|KAlarm|Add holidays support|djarvie@kde.org|David Jarvie}}
{{FeatureInProgress|Kleopatra|OpenPGP support|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureInProgress|KNotes|Zeroconf support for sending notes on LAN|qbast@go2.pl|Jakub Stachowski}}
{{FeatureDone|Kontact|New Planner summary; combines Appointment+To-do+SpecialDates into 1 pretty summary|o_timocin@gmx.de|Oral Timocin}}
{{FeatureInProgress|KPilot|Finish Keyring conduit, base conduit code and test cases, category syncing|jkasper@kde.org|Jason 'vanRijn' Kasper}}
{{FeatureTodo|Akregator|Basic support for enclosures (Displaying links, mimetype and size)|osterfeld@kde.org|Frank Osterfeld}}
{{FeatureTodo|[http://kblogger.pwsp.net KBlogger]|KBlogger, a blogging application| christian_weilbach@.web.de|Christian Weilbach}}
{{FeatureTodo|Kleopatra|Konqueror and Dolphin Kleopatra plugins|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureDone|KMail|Aggregated attachment view in the mail header area of the reader window|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KMail|Merge the new message list from the SoC branch|mcguire@kde.org|Thomas McGuire}}
{{FeatureTodo|Kontact|Support for Kontact wide profiles|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Drag and drop in the free-busy view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Support for comments in replies to invitations|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KOrganizer|Support for extended free-busy lists|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureTodo|KPilot|Port old conduits to new base conduit architecture and KDE4/Qt4|jkasper@kde.org|Jason 'vanRijn' Kasper}}
{{FeatureTodo|KBlogger|Port to use KRichTextEdit (Or KMEditor)|steveire@gmail.com|Stephen Kelly}}
{{FeatureTodo|KNode|Port to use KRichTextEdit (Or KMEditor)|steveire@gmail.com|Stephen Kelly}}

{{FeatureTodo|Kjots| Import notes from KNotes as KJots pages. |steveire@gmail.com|Stephen Kelly}}
{{FeatureTodo|Kjots| Email KJots pages using default mail client ({{bug|124509}}. |steveire@gmail.com|Stephen Kelly}}
{{FeatureTodo|Kontact|Tip-of-the-Day summary|molkentin@kde.org|Daniel Molkentin}}
|}

= 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|Okteta|add Kate-like search tool|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|Okteta|refactor KByteArrayView|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|parameter dialog for "Copy as..."|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}}
{{FeatureInProgress|Ark|Implement proper drag/drop between Ark/dolphin|harald((at))stud(dot)ntnu.no|Harald Hvaal}}
{{FeatureInProgress|Ark|Make the service menu work (possibly doing it as a KonqPopupPlugin|harald((at))stud(dot)ntnu.no|Harald Hvaal}}
{{FeatureInProgress|Ark|Proper password support|harald((at))stud(dot)ntnu.no|Harald Hvaal}}
{{FeatureTodo|Ark|Support for custom options from the compression interface (eg. a slider for selecting compression level for rar files)|harald((at))stud(dot)ntnu.no|Harald Hvaal}}
{{FeatureTodo|Ark|Add an options dialog (maybe)|harald((at))stud(dot)ntnu.no|Harald Hvaal}}
{{FeatureInProgress|kwalletmanager|Move kwalletmanager to the Model/View architecture and redesign the UI|lemma@confuego.org|Michael Leupold}}
|}

= 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
{{FeatureDone|krosspython and krossruby|Support custom types via handlers|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|krosspython and krossruby|Support QList<CustomType*> constructs|mail@dipe.org|Sebastian Sauer}}
{{FeatureInProgress|Smoke|Wrap some more APIs (at least Akanodi for all languages and Plasma for C#)|kde-bindings@kde.org|KDE-bindings developers}}
{{FeatureInProgress|PyKDE|KCM support and other plugins|simon@simonzone.com|Simon Edwards}}
{{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|Unittests++|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
{{FeatureInProgress|libkdegames|New highscore management system|milliams|Matt Williams}}
{{FeatureDone|kdiamond|Drag jewels|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|kdiamond|Optional OpenGL rendering|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|ksirk|Map scrolling arrows|kleag@free.fr|Gaël de Chalendar}}
{{FeatureDone|ksirk|KHotNewStuff skins|kleag@free.fr|Gaël de Chalendar}}
{{FeatureInProgress|ksirk|Jabber based net game finding|kleag@free.fr|Gaël de Chalendar}}
{{FeatureDone|ksirk|Use only names in skins instead of numeric ids|kleag@free.fr|Gaël de Chalendar}}
{{FeatureDone|ksirk|Skins editor|kleag@free.fr|Gaël de Chalendar}}
{{FeatureInProgress|ktron|Port and remake the KTron game for KDE 4.2|legolas@legolasweb.nl|Stas Verberkt}}
{{FeatureTodo|KNetWalk|Support for custom and non-square board sizes|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureTodo|KGoldrunner|Improvement to sound support and themes|mikelima@cirulla.net}}
{{FeatureTodo|KBlocks|Support for sounds|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureTodo|KMahjongg|Support for sounds|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureInProgress|Killbots|New app for 4.2|parker.coates@gmail.com|Parker Coates}}
|}

= 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
{{FeatureDone|Kate|Port and reenable the Snippets plugin.|jpetso@gmx.at|Jakob Petsovits}}
{{FeatureDone|perldoc KIOSlave|Add KIOSlave to allow reading Perldoc documentation.|michael.pyne@kdemail.net|Michael Pyne}}
{{FeatureInProgress|Lokalize|XLIFF support|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Lokalize|various Translation Memory enhancements|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureDone|Lokalize|wrap all windows belonging to one project into one MDI window|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Kross-based scripting|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|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|Port code generation wizard to QWizard and replace all q3 widgets|andi.fischer@hispeed.ch|Andi Fischer}}
{{FeatureInProgress|Umbrello|Replace all q3 widgets in the refactoring assistant|andi.fischer@hispeed.ch|Andi Fischer}}
|}

= 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
{{FeatureInProgress|KEduca|Rewrite of the classic test writing/taking application|matt@milliams.com|Matt Williams}}
{{FeatureTodo|KLettres|Number support|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KLettres|Theme manager|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureInProgress|KHangMan|Add a Open File action|annma@kde.org|Anne-Marie Mahfouf}}
{{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|KLettres|Visual indicator when letter is wrong|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Kalzium|Port Kalzium's periodic table to use new QGraphicsView.|marcus@cryos.org|Marcus D. Hanwell}}
{{FeatureInProgress|Kalzium|Plasmoid to access Kalzium database|cniehaus@kde.org|Carsten Niehaus}}
{{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}}
{{FeatureDone|KAlgebra|New parser (using QLALR) and new lexer|aleixpol@gmail.com|Aleix Pol}}
{{FeatureDone|KAlgebra|Import capability for MathML Presentation Markup in libanalitza|aleixpol@gmail.com|Aleix Pol}}
{{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|Parley|Declensions|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureInProgress|Parley|Rework main window infrastructure|d.laidig@gmx.de|Daniel Laidig}}
{{FeatureDone|KStars|Display millions of stars|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureDone|KStars|Tool to predict Conjunctions|akarshsimha@gmail.com|Akarsh Simha}}
{{FeatureInProgress|KStars|Earth Satellites|kstars@30doradus.org|Jason Harris}}
{{FeatureInProgress|KStars|Sky Calendar Tool|kstars@30doradus.org|Jason Harris}}
{{FeatureDone|KStars|Include HD Catalog Numbers (in search, in display)|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|Separate INDI From KStars|mutlaqja@ikarustech.com|Jasem Mutlaq}}
{{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|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|Harry de Valence}}
{{FeatureInProgress|Marble|Marble Plasmoid|hdevalence@gmail.com|Harry de Valence}}
{{FeatureInProgress|Marble|Qt-Version settings dialog|hdevalence@gmail.com|Harry de Valence}}
{{FeatureInProgress|Marble|Panoramio Support||Shashank Singh}}
{{FeatureInProgress|Marble|Twitter Plugin||Shashank Singh}}

{{FeatureInProgress|Marble|DGML2 Support|tackat@kde.org|Torsten Rahn}}
{{FeatureInProgress|Marble|Support for imperial units|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}}
{{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}}
{{FeatureDone|KTurtle|Export canvas as image|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureTodo|KTurtle|Optional rulers/grid for canvas units|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureDone|KTurtle|Add command line|piacentini@kde.org|Mauricio Piacentini}}
{{FeatureDone|KTurtle|Add a color picker|nielsslot@gmail.com|Niels Slot}}
{{FeatureInProgress|KBruch|Usability Improvements|tiago.porangaba@ltia.fc.unesp.br|Tiago Porangaba}}
{{FeatureInProgress|KBruch|Merging KPercentage functionalities into KBruch|tiago.porangaba@ltia.fc.unesp.br|Tiago Porangaba}}
{{FeatureTodo|Kalzium|Visualization of Schemes and Gradients at same time|tiago.porangaba@ltia.fc.unesp.br|Tiago Porangaba}}
|}

= 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
{{FeatureInProgress|Dragon Player|Make Dragon indipendent from Xine|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|File Manager|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|play media dialog|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|slider changes|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|show info while playing audio files|ian.monroe@gmail.com|Ian Monroe}}
{{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}}
{{FeatureTodo|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
{{FeatureTodo|KMagnifier|Refactor color menu, re-add invert, break current color blindness code into "daltonize" and "simulate"|mw_triad@users.sourceforge.net|Matthew Woehlke}}
{{FeatureTodo|KMagnifier|Add color-shift modes to help people with color blindness|mw_triad@users.sourceforge.net|Matthew Woehlke}}
|}

= 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|KSnapshot|Add support for grabbing a single screen in multihead|rich@kde.org|Richard Moore}}
{{FeatureDone|KSnapshot|Increase jpeg image quality from 75% to 85%|rich@kde.org|Richard Moore}}
{{FeatureDone|KSnapshot|If we're saving the window decorations then record the window title and class in the image (if the format supports it) to play nice with indexers like strigi|rich@kde.org|Richard Moore}}
{{FeatureTodo|Okular|Sound annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Link annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Improve annotation support: for existing types (rubber stamps, line, note, etc), and for the way they are constructed and handled.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Caret annotations.|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Okular|Support for videos & movie annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Support .snp and .emf file formats|bradh@kde.org|Brad Hards}}
{{FeatureDone|Gwenview|Support for animated images (.gif and .mng)|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureInProgress|Gwenview|Red Eye Reduction|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureInProgress|Gwenview|Nepomuk integration|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Dolphin-like single-click selection|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Optional tree view|aurelien.gateau@free.fr|Aurélien Gâteau}}
|}

= 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
{{FeatureDone|kio_bookmarks|A new konqueror home page displaying user bookmarks. See [[http://kde-apps.org/content/show.php?content=86516 description]]|xavier.vello@gmail.com|Xavier Vello}}
{{FeatureInProgress|kuiserver|KUiServer Goya port. General improvements for usability improvements|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureInProgress|kio fish/sftp|port fish and sftp to windows|brandon.ml@gmail.com|Carlo Segato}}
|}

= 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
{{FeatureTodo|konqueror|A new konqueror recover-dialog replacement|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureTodo|konqueror|Rework bookmarks using Akonadi|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureInProgress|dolphin|Add zoom slider into the status bar and general zooming improvments|peter.penz@gmx.at|Peter Penz}}
{{FeatureDone|dolphin|Tooltip previews|peter.penz@gmx.at|Peter Penz}}
|}

= 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
{{FeatureTodo|PoTD engine|Import from playground|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Frame plasmoid|Honor EXIF rotation - see bug 164605|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|Frame plasmoid|Previous, Pause and Next buttons - see bug 164704|annma@kde.org|Anne-Marie Mahfouf}}
|}

Projects/PIM/Akonadi

2008-09-27T14:29:18Z

Steveire: /* I have an unknown error 255 when running akonadictl */

== Akonadi TODO ==
The following list contains the things which need to be done for Akonadi.

Note: The person noted in the "Contact" column is not necessarily the one implementing that feature, but the one who can tell you what to do and how to help, i.e. you can also contribute to those tasks ;-)

=== Core ===

==== 4.1 ====

Urgent tasks that need to be finished for the KDE 4.1 release ('''May 19th'''):

{| 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 !! Item !! Description !! Contact
{{FeatureDone|Item streaming in ItemSync/ResourceBase|As discussed in Osnabrueck|Tom/Volker}}
{{FeatureDone|Payload serialization format versioning|see below
tokoe@kde.org|Tobias}}
{{FeatureDone|API for additional item parts|As discussed in Osnabruck|Volker/Tobias}}
{{FeatureDone|Infrastructure for showing additional dialogs from agents/resources|As discussed in Osnabrueck|Tom}}
{{FeatureDone|Allow to limit ItemFetchJob to current cache content|Prevents search index feeder agents from downloading all remote data|vkrause@kde.org|Volker}}
{{FeatureDone|Fix API for item/collection modifications|See Osnabrueck meeting notes for details|vkrause@kde.org|Volker}}
{{FeatureDone|Plugin Versioning|For serializer plugins, also check using Qt plugin stuff instead of the libkdepim plugin framework|tokoe@kde.org|Tobias}}
{{FeatureDone|Tray app|small app to control the server and have a something that can report errors|tomalbers@kde.nl|Toma}}
{{FeatureDone|Backup support|Dump & Restore database contents, also useful when upgrading to a newer database version|tomalbers@kde.nl}}
|}

==== Scheduled for 4.2 ====

That's the stuff we want to have in 4.2, very roughly ordered by priority.

{| 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 !! Item !! Description !! Contact
{{FeatureDone|Server error reporting|Helpful error message when the server cannot be started or if there is some other problem communicating with it.|vkrause@kde.org|Volker}}
{{FeatureInProgress|KResource migration tool|For KABC and KCal resources, setting up Akonadi <-> KResource bridges where needed|Volker}}
{{FeatureInProgress|KResource bridges|Subresource support still has to be done|Kevin}}
{{FeatureTodo|Complete iCal resource|error handling, robustness, legacy formats, etc.|}}
{{FeatureInProgress|Complete vCard resource|same as iCal|Bertjan}}
{{FeatureInProgress|Item size|Needed by Mailody|thomas.mcguire@gmx.net}}
{{FeatureInProgress|Finish collection model/view|see below|thomas.mcguire@gmx.net}}
{{FeatureInProgress|Collection statistics for sub-trees|Provide a CollectionStatus object covering the full sub-tree in the model, allowing accumulated unread counts etc.|Thomas}}
{{FeatureTodo|Batch jobs for modifying/deleting collections/items|it would be great to have jobs which perform operations on several entities in one sitting (a use-case: mark all as read).|}}
{{FeatureTodo|Batch job to retrieve a set of items from Akonadi|Those items don't belong to the same collection, rather they are located in different collections|}}
{{FeatureTodo|CollectionFetchJob/ItemFetchJob should be able to retrieve entities by remote id/mimetype|
This is problematic with change notifications, as they have to know about the filtering with the \Seen flag as well.
This type of filtering would be possible with full Nepomuk interface though. We don't want yet another query language here. The plan is to fix the nepomuk agent and use that as semi-public interface for now.|}}
{{FeatureTodo|ResourceBase::collectionsRetrievalDone is missing|I'm working around by calling collectionsRetrievedIncremental() with empty collection lists|}}
{{FeatureInProgress|LINK/UNLINK commands|Managing item references in virtual collections|vkrause@kde.org|Volker}}
|}

==== Post 4.2 ====

This stuff is currently not considered for 4.2 due to lack of resources. Of course it will be added nevertheless if someone implements it. The list is completely unsorted.

{| 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 !! Item !! Description !! Contact
{{FeatureTodo|Error reporting|Akonadi::Job basically has only one error code: Unknown|Tobias}}
{{FeatureInProgress|Akonadi Artwork|Icon for the tray app|tomalbers@kde.nl|Toma}}
{{FeatureTodo|Nepomuk integration|Generic Item tag/rate/comment, etc.|Tom}}
{{FeatureTodo|Account creation wizard|as discussed in Berlin, see below|}}
{{FeatureTodo|Sync collection tree after creating setting up a resource|see AgentInstanceCreateJob|}}
{{FeatureTodo|Support standard commands for QUndo framework||}}
{{FeatureTodo|Conflict detection in resources|See Osnabrueck meeting notes for details|}}
{{FeatureInProgress|Action framework|see below|vkrause@kde.org|Volker}}
{{FeatureTodo|Solid integration|Switch online/offline state in ResourceBase automatically|}}
{{FeatureTodo|Make unittests work without destroying the production database||}}
{{FeatureInProgress|Fix API docs|The libakonadi move as well as the huge API changes following it broke lots of the docs technical and content-wise, see below|Tobias}}
{{FeatureTodo|Filesystem Backend|Store content data in files instead of the database, transfer filehandles instead of data to the client|}}
{{FeatureTodo|Migration|Data and settings from pre-Akonadi times, see below|}}
{{FeatureTodo|Remote Search|Delegating searches to resources, see below|}}
{{FeatureTodo|Extended notifications|Item change notification do not yet include their source collections (real and virtual)|}}
{{FeatureTodo|Alternative for Akonadi::ResourceBase|Not using the scheduler to avoid the serialization of operations, see RSS resource. (This will get very complicated. Maybe use a proxy ResourceBase for this, which is thread-pooled?)|}}
{{FeatureTodo|Collection parameter for Monitor::itemChanged() and Monitor::itemRemoved()|
If the item resides in several collections (normal + virtual collections) then emit those signals for each collection. Adding this would mean changing it in many places (Monitor, Observer, ...), this is lots of work but probably the right thing to do.
Related to virtual collections, since with them, items can be in multiple collections. Better wait until the Nepomuk stuff is finished?|}}
|}

=== Supported Types ===

Overview on the current state of support for various types:

{|
|-
! Type !! Serializer !! Multipart Support !! Models !! Views !! Resources !! Notes
|-
|Email||yes||partial||MessageModel, MessageCollectionModel, threading proxy model||?||maildir, IMAP||threading agent
|-
|News||yes (1)||partial (1)||(1)||(1)||NNTP||
|-
|Contact||yes||no||ContactModel||-||vCard, facebook, KRes||
|-
|Events||yes||no||EventModel||-||iCal, KRes||
|-
|Notes||no||no||-||-||-||not started yet
|-
|Feeds||yes||no||Feeds, Items||?||OPML||GSoC in playground/pim
|-
|Bookmarks||yes||no||-||-||local bookmarks, del.icio.us||
|}

(1) see Email

=== Mail specific extensions ===

{| 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 !! Item !! Description !! Contact
{{FeatureTodo|Extend Message Model|Add all required columns, save/restore layout, flag delegate, configurable columns, etc.|}}
{{FeatureTodo|Share mail flag code|Standard actions, standard flag enum/constants, Nepomuk interaction|}}
{{FeatureTodo|Extend ENVELOPE|Add more information to the envelope payload part in the serializer plugin, eg. trheading information is missing|}}
{{FeatureTodo|Fix/finish threading||}}
|}

=== Event/Todo/Journal specific extensions ===

{| 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 !! Item !! Description !! Contact
{{FeatureTodo|Todo proxy model|See KOrganizers To-Do view|Bruno?}}
{{FeatureInProgress|Subtype identification|See discussion on kde-pim mailinglist|Kevin?}}
{{FeatureTodo|Agenda view|KOrganizer agenda view based on Akonadi|Bruno?}}
{{FeatureTodo|Month view|KOrganizer month view based on Akonadi|Bruno?}}
{{FeatureTodo|Timeline view|KOrganizer timeline view based on Akonadi|}}
|}

=== Resources, Agents and others ===

{| 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 !! Item !! Description !! Contact
{{FeatureInProgress|KResource Akonadi bridge|for applications using KCal or KABC|kevin.krammer@gmx.at|Kevin}}
{{FeatureInProgress|Akonadi KResource bridge|for data accessed through KCal or KABC resources|kevin.krammer@gmx.at|Kevin}}
{{FeatureTodo|Expire Agent||}}
{{FeatureTodo|MBOX Resource||Thomas}}
{{FeatureTodo|Extend IMAP Resource||}}
{{FeatureTodo|POP3 Resource||Thomas}}
{{FeatureInProgress|RSS Resource|GSoC in playground/pim ([[Projects/PIM/RSS_framework_for_Akonadi|Details]])|Dmitry}}
{{FeatureTodo|Filter Agent||}}
{{FeatureTodo|Search||}}
{{FeatureTodo|Filter Rule GUI|Used by filters and searches|}}
|}

Resource status overview (this should list all resources existing in KDE3 or already under development for Akonadi):

{|
|-
! Resource !! Retrieve Collections !! Retrieve Items !! Change Collections !! Change Items !! Configuration !! Notes
|-
|iCal||yes (4)||yes (1) (2)||no||yes (5)||yes||does not yet watch for file changes
|-
|vCard||yes (4)||yes (1) (2)||no||?||yes||does not yet watch for file changes
|-
|maildir||yes (1) (4)||yes (1) (2)||?||?||yes||
|-
|mbox||no||no||no||no||no||not started yet, code exists in KMail
|-
|IMAP||yes (1) (4)?||yes (1) (2)||no||no||no||code exists in kio_imap4 and Mailody, support for extensions: quota, ACL, annotations missing, what about Kolab and Scalix?
|-
|POP3||no||no||no||no||no||not started yet,code exists in kio_pop3
|-
|NNTP||yes (4)||yes (2)||n/a||n/a||yes||Needs support for local collection names and collection hierarchy
|-
|Local Bookmarks||?||?||?||?||(3)||Code in akonadi/resources
|-
|OpenChange||?||?||?||?||?||Code in akonadi/resources
|-
|Facebook||?||?||?||?||?||Code in playground/pim
|-
|del.icio.us||?||?||?||yes||no||Code in playground/pim
|-
|KABC||yes(6)||yes||no||yes||yes||
|-
|KCal||yes(6)||yes||yes(7)||yes||yes||
|}

# only full sync supported currently, need optimization
# does not yet honor cache policy
# still relies on QSettings for configuration and/or doesn't provide configuration over D-Bus
# does not yet provide correct access control settings
# only adding new items, not changing existing ones
# availability of child collections depend on whether the KResource plugin has subresources
# child collections can be added or removed if the KCal plugin can have subresources

== Akonadi Braindump ==
Ideas/notes etc. on various open issues in Akonadi.

=== Akonadi Standard Actions ===

Idea: Have something like KStandardAction for Akonadi that not only includes the representation of the action but also its state management and the actual operations. Like libakonadi that should be splitted into a generic, type-independent part and be extensible for type-specific actions. This will enable code sharing among many applications and guarantee consistent actions everywhere.

State management: watch selection models of a collection and/or item model.

Use KXMLGUI for context menus in standard views to allow easy extensibility with custom actions.

Generic actions:
* new collection [done]
* new virtual collection
* delete collection [done for single selection]
* copy collection [done]
* cut collection
* paste collection [done]
* synchronize collection [done for single selection]
* synchronize resource
* synchronize everything
* show collection properties dialog [done]
* delete item(s) [done]
* copy item(s) [done]
* cut item(s)
* paste item(s) [done]
* paste native data
* tag item(s)
* comment item
* rate item(s)
* configure resource
* add resource? (would need a type parameter, etc.)
* delete resource
* manage local subscriptions [done]
* move to submenu
* copy to submenu

The list is definitely long enough to make this worthwhile.

=== Collection Model / Collection View ===

Ideas/missing features/bugs of the collection model/view:

* Enable/disable status columns
* Show status after the name (see KMail)
* Size column
* Save/restore layout
* Custom collection icons (see KMail, also needed for resource defined special folders (eg. Inbox)
* Status tooltips (see KMail in 3.5.9)
* Quick search
* Favorite folder view as proxy model on top of the normal collection model (FlatCollectionProxyModel might be helpful for there)
* Accumulated statistics (unread, total, size)
* Fix dnd: move/copy/cancel menu always shows up and never has any effect

=== Compatibility ===

Notes on how to keep long-term protocol, source and binary compatibility.

* <s>Detect server version in Akonadi::Session, might be useful in case of protocol extensions/changes</s>
* What about database server version updates?
* <s>Versioning or any other kind of serialization format meta data, we'll need that in case of changes in serialization formats (see eg. Robert's compression patch where this is needed)</s>
* <s>We currently use 32 bit ids, probably hard to change later on, is that enough?</s>
* <s>Plugin versioning</s>

=== Resource API issues ===

Notes/ideas/complaints about the Akonadi::ResourceBase API:

* Extremely error prone:
** Scheduler dead-locks when a requested operation is not correctly announced as finished, esp. a problem in error cases.
** Using the result methods multiple times or when not requested asserts
* <s>Item streaming is missing, requiring all data to be in memory at once</s>
* Non-incremental updates need to know the results of ItemSync to not have to provide all data, even for already existing/unchanged items.

=== API / BC issues ===

Smaller stuff that should be fixed before the ABI freeze and is not yet listed above:

* Cleanup the D-Bus format used by NotificationMessage
* No mentioning of "IMAP" in the public API, we are not using IMAP
* Naming and installed location of libraries, headers and executables (see discussion on kde-pim ML)
* <s>Payload part labels are QStrings, attribute types are QByteArray</s>

=== Deployment issues ===

* Multiple access: Should multiple Akonadi instances' mysqlds access a single set of data files the mysql will likely corrupt the data. This can happen in any NFS+YP installation where users can log onto any machine and access shared homes. MySQL relies on filesystem locking to prevent multiple access. [http://dev.mysql.com/doc/refman/6.0/en/multiple-servers.html MySQL multiple instance docu].
* [http://dev.mysql.com/doc/refman/6.0/en/innodb-restrictions.html InnoDB tables should not be used on NFS].
* NFS speed: MySQL documentation recommends against locating its data files on network shares.
* AppArmor: Distros' AppArmor profiles prevent MySQL from writing outside its defined data directory (usually /var/lib/mysql). This is a problem at least with *buntu and openSUSE. These will need to be adapted. It is possible to daisy-chain profiles so that MySQL started by Akonadi receives a different profile to MySQL running standalone. An empty profile has all rights. Another possibility is to adapt the general MySQL profile so it can write to ${XDG_DATA_HOME}/akonadi(usually ${HOME/}.local/share/akonadi). Both support for profile chaining and ${HOME} may depend on the version of AppArmor installed. What about SELinux?
* Backup: MySQL data files should not be backed up without telling the mysqld process, otherwise a corrupt backup will be made. LOCK TABLES and FLUSH TABLES at the least. A dump can be made or mysqlhotbackup may be used in some circumstances. We should consider sysadmins' backup techniques when planning/promoting Akonadi, as a simple rsync cronjob with running Akonadi will not work. [http://dev.mysql.com/doc/refman/6.0/en/backup.html MySQL backup advice].

=== Account Creation Wizard ===

Notes on the resource configuration wizard discussion.

* WizardBase class
* Wizard discovery via .desktop files
* A wizard can configure multiple resources (eg. IMAP + LDAP for Kolab) and non-resources (mailtransport)
* Optionally hide resources completely covered by wizards in the Add Account dialog
* List wizards in the Add Account dialog
* Store Account -> Resources information to offer deletion of depending resources

=== PostgreSQL datastore support ===

First review of the akonadi code reveals PGSQL Qt driver is already supported, but the code is not totally ready for it. Some first reading comments about where to patch for supporting PostgreSQL too:

==== akonadi/server/src/storage/dbinitializer.cpp ====

* line 201..., ALTER TABLE ADD [UNIQUE] INDEX syntax is MySQL only, better use the common one CREATE [UNIQUE] INDEX ... one [done with revision 789899]
* line 303, QString DbInitializer::sqlType(const QString & type), LONGBLOB is the MySQL type, PostgreSQL will use BYTEA.
* line 362, qFatal("Implement index support for your database!");
mysql: SHOW INDEXES FROM %1
pgsql: SELECT c2.relname, i.indisprimary, i.indisunique, i.indisclustered, i.indisvalid, pg_catalog.pg_get_indexdef(i.indexrelid, 0, true), c2.reltablespace
FROM pg_catalog.pg_class c, pg_catalog.pg_class c2, pg_catalog.pg_index i
WHERE c.oid = '16713' AND c.oid = i.indrelid AND i.indexrelid = c2.oid
ORDER BY i.indisprimary DESC, i.indisunique DESC, c2.relname

relname | indisprimary | indisunique | indisclustered | indisvalid | pg_get_indexdef | reltablespace
--------------+--------------+-------------+----------------+------------+--------------------------------------------------------------+---------------
foo_pkey | t | t | f | t | CREATE UNIQUE INDEX foo_pkey ON foo USING btree (id) | 0
foo_time_key | f | t | f | t | CREATE UNIQUE INDEX foo_time_key ON foo USING btree ("time") | 0
(2 lignes)

==== akonadi/server/src/storage/datastore.cpp ====

* line 700, qint64 DataStore::highestPimItemId() const, seems wrong for a concurrent program (SELECT MAX(col) FROM table; is not reliable if another thread is inserting at the same time) : check the callers
* line 794, qint64 DataStore::lastInsertId( const QSqlQuery & query ), PostgreSQL doesn't provide concurrent-bogus last_insert_id, but from 8.2 accepts the syntax INSERT INTO ... RETURNING col1, col2, ...;
* line 806, QString DataStore::dateTimeFromQDateTime( const QDateTime & dateTime ), use PostgreSQL to_char() formatting function for date rather than having Qt do it

=== Documentation ===

* Avoid examples using KJob::exec() due to its problematic side-effects.
* Examples in the ItemCreateJob docs (and maybe others) operate on items in the root collection which does not work at all
* Resurrect the server API docs
* Content of http://api.kde.org/4.x-api/kdepim-apidocs/akonadi/html/index.html should probably be moved to server or client lib docs

=== Migration of pre-Akonadi data and settings ===

* KCal/KABC
** switch KRes resources to Akonadi KRes compat resources, use KRes Akonadi compat resource, basically injecting Akonadi inbetween
** Replace Akonadi KRes compat resources with their ported equivalent
** Application side does not need migration code, "only" port to Akonadi
* KMail
** Should migrate to one resource per account + one for previous local folders
** Problem: local folders are mixed mbox/maildir
*** Dedicated KMail compat resource?
*** Convert everything to maildir first?
** Flags are stored in proprietary binary format
* KNode
** Migrate every account to NNTP resource
** Local flags should be preserved, stored in proprietary binary format
** Local subscription state should be preserved (where is that stored?)
** Local folders using MBOX format + proprietary binary index
* Akregator

=== Search ===

* Delegation to resources still completely missing
** Requires query transformation
** Requires management for live searches
** Requires the ability to report search results (needs protocol extension)
* Query language still undecided, current options: XESAM, SPARQL
* Backend still undecided, current options: XESAM, Nepomuk

== KMail Breakdown Plan ==
The current plan is to put some parts of KMail into a stand-alone
library, independent of KMail. This increases code reuse (for example, the message composer could be shared with Mailody) and makes the code a lot easier to maintain and to port to Akonadi.

{| 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 !! Item !! Description !! Contact
{{FeatureTodo|Bodypart formatters||}}
{{FeatureTodo|Reader Window||}}
{{FeatureTodo|Composer: Editor||}}
{{FeatureTodo|Composer: Message Composer||}}
{{FeatureTodo|Composer: GUI Window||}}
{{FeatureTodo|Queue Manager for mailtransport||}}
{{FeatureTodo|Templates: Core||}}
{{FeatureTodo|Templates: GUI||}}
{{FeatureTodo|Port KMCommands||}}
{{FeatureTodo|Port away from KMMessage and KMFolder* everywhere it is left|An idea might be: wrap KMMsgBase/KMMessage inside a reference counted Message class. Insulate everything else from it by wrapper functions. KMFolder should be easier...|}}
{{FeatureTodo|Migration application for index and other config||}}
{{FeatureTodo|Port MDNs||}}
|}

== The Road to World Domination ==

Sort of related so the stuff above but with a scope for all of KDE PIM and beyond.

{| 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 !! Item !! Description !! Contact
{{FeatureTodo|Share identity config GUI parts|eg. the signature configuration widget|}}
{{FeatureTodo|Mailtransport Agent|Global shared outbox, central mail sending instance|}}
{{FeatureTodo|Recently sent to support in mailtransport|related to above, based on Akonadi/Nepomuk|}}
{{FeatureTodo|Composer engine|Shared stuff for KMail/KNode/Mailody: Crypto, editor, editor actions, attachment model, message assembly, etc.|}}
|}

== Akonadi FAQ ==

=== Where do I find the Akonadi config files? ===

''~/.config/akonadi/''

=== Where does Akonadi store my data? ===

''~/.local/share/akonadi/''

=== Where can I find the source code? ===

There are three different parts of source code:
* The Akonadi server, which is KDE-independent. Currently, the code can be found at [http://websvn.kde.org/trunk/kdesupport/akonadi/ kdesupport/akonadi]. The server code will likely move to the [http://www.freedesktop.org/wiki/ freedesktop.org project] in the future, the move has already been [https://bugs.freedesktop.org/show_bug.cgi?id=15711 requested].
* The Akonadi KDE client libraries are in [http://websvn.kde.org/trunk/KDE/kdepimlibs/akonadi/ kdepimlibs/akonadi].
* Various agents, resources, the Akonadi console and much other misc stuff is in [http://websvn.kde.org/trunk/KDE/kdepim/akonadi/ kdepim/akonadi]

=== Where can I find documentation? ===

The documentation is mainly in the code itself, in the form of doxygen comments.
You can find the generated documentation on [api.kde.org api.kde.org], for example:

* General documentation, including a design overview, is [http://api.kde.org/4.x-api/kdepim-apidocs/akonadi/html/index.html here]

: Note that some links in the above documentation which point to the server or the KDE client libraries are currently broken, use the links below to access that documentation.
* Documentation for the KDE Akonadi client library is [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/index.html here]
* Documentation about the server is [http://api.kde.org/kdesupport-api/kdesupport-apidocs/akonadi/server/html/index.html here]

=== Which DBMS does Akonadi use? ===

So far only MySQL. There is some work on PostgreSQL support going on though. Basically, every database that is supported by QtSQL can be used, requiring minimal changes in the code at most. However, not all of them provide the features needed by Akonadi (see next two questions).

=== Why not use sqlite? ===

We tried. Really. It can't handle the concurrent access very well, in the best case this means ''very'' slow operations, but we've also seen deadlocks and failing transactions. Once that's fixed in sqlite, adjusting Akonadi to use it again instead of MySQL is no problem.

=== Why not use MySQL/Embedded? ===

We tried that as well, there are two reasons for not using it: No support for the InnoDB engine (which we need for transaction support) and poor availability (only OpenSUSE provided usable packages, needed a patched QSQL driver).

=== Do I need a running MySQL server? ===

No. Akonadi starts its own local MySQL server (unless configured otherwise, see next question). All you need is having the 'mysqld' binary installed at runtime (usually found in the mysql-server package of your distribution).

=== Can Akonadi use a normal MySQL server running on my system? ===

Yes, it can. You find the corresponding settings in ''~/.config/akonadi/akonadiserverrc''.

=== I don't like a database server because of backups/running on NFS/etc. ===

See section "Deployment Issues" above, we are aware of that and working on it. Some of these, like backup/restore are already implemented. But please be aware that most of this issues also existed before (eg. with KMail's custom binary indexes).

=== Can a single Akonadi instance be used by multiple users? ===

No. There has to be one Akonadi server instance per user. However, it is possible to use a shared database server.

=== Can I access the Akonadi server on a remote machine? ===
No. Akonadi is not a groupware server. It's a local cache only.

=== I have an unknown error 255 when running akonadictl ===
Distributions using Apparmor require you to run '''aa-complain mysqld''' with root privileges then reload apparmor.

On kubuntu this is:

sudo aa-complain mysqld
sudo /etc/init.d/apparmor reload

=== I get a "DB error: 'Could not open required defaults file: /home/$username/.local/share/akonadi//mysql.conf" ===
Although you probably don't have an apparmor in your processlist, you are still using it, run '''aa-complain mysqld''' and try again.

=== What's the difference to EDS? ===
EDS is limited to contacts and calendar data, Akonadi is type-independent. Especially, Akonadi is designed to also handle high-volume data such as email. Akonadi and EDS also differ largely in their access protocol on the technical level (Corba/D-Bus vs. local socket with IMAP-like protocol/D-Bus) as well as one the protocol level (type specific vs. generic).

=== How do I create a collection? ===

From the developers point of view, there is Akonadi::CollectionCreateJob for that, from the users point of view, most applications allow that, eg. Mailody or akonadiconsole.

However, there is one limitation: Top-level collections can only be created by resources, not by normal applications. The reason for that is that every object (collection or item) is supposed to have an owning resource, that is a resource that is responsible for storing and retrieving that object. There is an ongoing discussion to remove this restriction though.

So, if you want to create a collection eg. for testing purposes, add a resource first. Most Akonadi applications offer an option to do that, a module for KControl is planned as well.

[[Category:PIM]]

== Links ==

* [http://pim.kde.org/akonadi/ http://pim.kde.org/akonadi/]
* #akonadi IRC channel on freenode

Projects/PIM/KJots

2008-09-26T18:25:21Z

Steveire: /* Books and Pages */ Fix second option description re books

For KDE 4.2, KJots will undergo several changes to integrate more with some pillars of KDE- Akonadi, Nepomuk, and Plasma.

This will involve changes in how user data is stored and represented.

== Current state ==

Currently, KJots books and pages are subclasses of QAbstractModelItem (see http://websvn.kde.org/trunk/KDE/kdepim/kjots/kjotsentry.h?view=markup)
Those classes are responsible for saving and loading data etc. Data is saved to .book files in the AppData directory. These .books files contain top-level books including any nested books.

The books are organized in a bookshelf, which is a QTreeWidget (http://websvn.kde.org/trunk/KDE/kdepim/kjots/bookshelf.h?view=markup).

== Current plan for 4.2 ==

The plan is to create some new representations of these objects to integrate with akonadi and nepomuk. This will allow multiple plasmoids to allow interaction with multiple or the same books. Additionally, nepomuk will give the possiblility to represent pages in a heirarchy of tags.

* http://thread.gmane.org/gmane.comp.kde.nepomuk/147
* http://thread.gmane.org/gmane.comp.kde.devel.pim/22743
* http://mail.kde.org/pipermail/plasma-devel/2008-September/001256.html

=== Plasmoid ===

Plasmoids would have a root index set as the root of the bookshelf, or rooted in one book or tag collection. For example, if you have a structure like:

* Book 1
** Page 1
** Page 2
** Page 3
** Sub-Book 1
*** Page 1
*** Page 2
* Book 2
** Page 1
** Page 2

Then it will be possible to show a plasmoid which displays only Book1 (including Sub-Book1), only Book2, only Sub-Book1, or all books in the bookshelf. Additionally, it will be possible to show only pages with the same tag.

Drag and drop between plasmoids will be possible as well as dragging books from the kjots application or kjots plasmoids onto the plasma workspace to create a new kjots plasmoid rooted at that book.

=== Mimetypes ===

The above drag and drop behaviour requires that a mimetype be registered for kjots books.
Additionally, akonadi requires that kjots books and pages have mimetypes set to facilitate item retrieval.
The mimetypes application/x-app-kde-kjots-book and application/x-app-kde-kjots-page will be used for these features.

=== Books and Pages ===

For akonadi support, KJotsBooks and KJotsPages wil be represented by simple structs and books will serialized/deserialized with a
[http://api.kde.org/4.1-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1ItemSerializerPlugin.html Akonadi::ItemSerializerPlugin]. This will allow syncronization of pages being displayed in different plasmoids and the kjots application.

There are two options for what to serialize. The current state could be preserved, and top-level books would be [http://api.kde.org/4.1-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1Item.html Akonadi::Item]s and would be serialized. The payload would be the pages and nested books within the top-level book.

Alternatively, the system could be changed to represent each book and page as a distinct file. Each page would be a [http://api.kde.org/4.1-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1Item.html Akonadi::Item] and could be serialized/deserialized individually. The payload would be the page content. Books would be Akonadi::Collection objects.

For tagging, nepomuk requires that either books/pages be saved in individual files, or custom book and page classes exist (or both). An ontology will be defined which describes how books and pages relate to each other, and tag capable classes will be generated from that.

I'm not sure if the same class can be used for serialization/deserialization and nepomuk tags. I will probably need AkonadiNoteBook, AkonadiNotePage, and NepomukNoteBook, NepomukNotePage.

=== Bookshelf ===

The kjots bookshelf will be replaced with an [http://api.kde.org/4.1-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1CollectionModel.html Akonadi::CollectionModel]. Each book in the application will be a collection (which can be nested).
Page data will be retrieved with the [http://api.kde.org/4.1-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1CollectionModel.html#489f28b6acb4d13e1237765f85b4c120 Akonadi::CollectionModel::Roles::CollectionRole]. An [[Development/Tutorials/Akonadi/Resources|akonadi resource]] will be used to retrieve the collections, add/remove/modifiy items etc.

Using nepomuk types, a proxy model can represent the tags on a particular page, so that pages can be grouped by tag on the left tree. Dragging items around on the tree would change the tags on the item.

Projects/PIM/KJots

2008-09-26T17:36:12Z

Steveire: Plan for using some pillars of kde in kjots.

For KDE 4.2, KJots will undergo several changes to integrate more with some pillars of KDE- Akonadi, Nepomuk, and Plasma.

This will involve changes in how user data is stored and represented.

== Current state ==

Currently, KJots books and pages are subclasses of QAbstractModelItem (see http://websvn.kde.org/trunk/KDE/kdepim/kjots/kjotsentry.h?view=markup)
Those classes are responsible for saving and loading data etc. Data is saved to .book files in the AppData directory. These .books files contain top-level books including any nested books.

The books are organized in a bookshelf, which is a QTreeWidget (http://websvn.kde.org/trunk/KDE/kdepim/kjots/bookshelf.h?view=markup).

== Current plan for 4.2 ==

The plan is to create some new representations of these objects to integrate with akonadi and nepomuk. This will allow multiple plasmoids to allow interaction with multiple or the same books. Additionally, nepomuk will give the possiblility to represent pages in a heirarchy of tags.

* http://thread.gmane.org/gmane.comp.kde.nepomuk/147
* http://thread.gmane.org/gmane.comp.kde.devel.pim/22743
* http://mail.kde.org/pipermail/plasma-devel/2008-September/001256.html

=== Plasmoid ===

Plasmoids would have a root index set as the root of the bookshelf, or rooted in one book or tag collection. For example, if you have a structure like:

* Book 1
** Page 1
** Page 2
** Page 3
** Sub-Book 1
*** Page 1
*** Page 2
* Book 2
** Page 1
** Page 2

Then it will be possible to show a plasmoid which displays only Book1 (including Sub-Book1), only Book2, only Sub-Book1, or all books in the bookshelf. Additionally, it will be possible to show only pages with the same tag.

Drag and drop between plasmoids will be possible as well as dragging books from the kjots application or kjots plasmoids onto the plasma workspace to create a new kjots plasmoid rooted at that book.

=== Mimetypes ===

The above drag and drop behaviour requires that a mimetype be registered for kjots books.
Additionally, akonadi requires that kjots books and pages have mimetypes set to facilitate item retrieval.
The mimetypes application/x-app-kde-kjots-book and application/x-app-kde-kjots-page will be used for these features.

=== Books and Pages ===

For akonadi support, KJotsBooks and KJotsPages wil be represented by simple structs and books will serialized/deserialized with a
[http://api.kde.org/4.1-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1ItemSerializerPlugin.html Akonadi::ItemSerializerPlugin]. This will allow syncronization of pages being displayed in different plasmoids and the kjots application.

There are two options for what to serialize. The current state could be preserved, and top-level books would be [http://api.kde.org/4.1-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1Item.html Akonadi::Item]s and would be serialized. The payload would be the pages and nested books within the top-level book.

Alternatively, the system could be changed to represent each book and page as a distinct file. Each page/book would be a [http://api.kde.org/4.1-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1Item.html Akonadi::Item] and could be serialized/deserialized individually. The payload would be the page content or the list of pages and nested books in the book.

For tagging, nepomuk requires that either books/pages be saved in individual files, or custom book and page classes exist (or both). An ontology will be defined which describes how books and pages relate to each other, and tag capable classes will be generated from that.

I'm not sure if the same class can be used for serialization/deserialization and nepomuk tags. I will probably need AkonadiNoteBook, AkonadiNotePage, and NepomukNoteBook, NepomukNotePage.

=== Bookshelf ===

The kjots bookshelf will be replaced with an [http://api.kde.org/4.1-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1CollectionModel.html Akonadi::CollectionModel]. Each book in the application will be a collection (which can be nested).
Page data will be retrieved with the [http://api.kde.org/4.1-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1CollectionModel.html#489f28b6acb4d13e1237765f85b4c120 Akonadi::CollectionModel::Roles::CollectionRole]. An [[Development/Tutorials/Akonadi/Resources|akonadi resource]] will be used to retrieve the collections, add/remove/modifiy items etc.

Using nepomuk types, a proxy model can represent the tags on a particular page, so that pages can be grouped by tag on the left tree. Dragging items around on the tree would change the tags on the item.

Schedules/Is KDE 4.1 for you?

2008-07-29T10:22:58Z

Steveire: Add info re KDE 3.5.10

KDE 4.1 is scheduled for release at the end of July 2008. This is a significant milestone for the KDE 4 series and for KDE in general, but as an early
release in the KDE 4 cycle, it does have some known issues which will not be fixed in KDE 4.1. Huge progress has been made in KDE 4.1 which is listed in the [[Schedules/KDE4/4.1_Feature_Plan|KDE 4.1 Feature Plan]].

Some of the more obvious issues are listed below. If these issues are important to you, you should stay with KDE 3.5 (KDE 3.5.10 is scheduled for release in [[Schedules/KDE_3.5_Release_Schedule#August_2008:_Expected_release_date_of_KDE_3.5.10|August]]) or KDE 4.0 until KDE 4.2 when most of these issues are scheduled to be resolved.

It is possible that distributions will work around some of these issues before distributing to users. KDE 4.2 is currently scheduled for release
in February 2009.

== The Desktop ==

The desktop in KDE 4.1 will mark the start of some significant user interface changes. This is a step away from the way the KDE 3 desktop was
designed, but everything possible on your KDE 3.5.9 desktop will also be possible on your KDE 4 desktop. For KDE 4.1, however, some features
are not yet complete, but should be ready for KDE 4.2.

=== FolderView ===

{{Box|Under Construction|2=[[Image:Action_configure.svg|noframe|left|40px]]
'''This page is under construction'''. This section could really do with some screenshots on the page. You can help by [{{fullurl:{{PAGENAME}}|action=edit}} editing this page].
<div class="clear"></div> }}

FolderView is a new technology on the KDE 4 desktop which allows more than one collection of icons on your "desktop" and discourages using it as
dumping ground for miscellaneous files. However, it can still be configured to behave just like KDE 3 did. See [http://blog.lydiapintscher.de/2008/06/14/folderview-is-the-awesome/ this blog entry by Lydia Pintscher] for some more information on FolderView.

The following issues are known and are scheduled to be resolved in KDE 4.2 next February:
* Icons do not need to be in a grid. You can drag them to any point within the FolderView. However, the location you leave them in is not saved, so they will be in a grid again the next time you start the desktop.
* You can have a full screen "desktop with icons", but if you do, you can not have a desktop background. See also: http://www.youtube.com/watch?v=RhYinDOKbE8
* You can have a desktop background, but then you must use the FolderView in regular, not entire screen mode (as shown in Lydia's blog above).

=== Panels and workspaces ===

Some panel issues can be resolved before KDE 4.2. Because of the modular design of Plasma, a new panel could be quite easily written with autohide functionality. This would likely be written by a distribution team or a developer on kde-apps.org.

* Autohiding of panels is not yet configurable.
* It is not possible to set different desktop wallpapers for different virtual desktops.
* The Mac-style menu bar is not available.




== Applications ==

=== New and missing applications ===
Some KDE 3 applications have not yet been ported to KDE 4. Most distributions still package KDE 3 versions of these applications with their KDE 4 desktop. Some notable applications which will not be included in KDE 4.1 are listed below:

* KOffice has a different release schedule than KDE 4. KOffice 2.0 will likely be released late in 2008. [http://www.koffice.org/news.php#itemKOffice20alpha9released Alpha 9] has been released with binaries for all three major platforms. The developers are looking for volunteers to help put together screenshots for [http://www.kdedevelopers.org/node/3545 visual changelogs].
* Amarok has a different release schedule than KDE 4. The Amarok team is currently aiming for a first release in October 2008 for the 2.0 series. Amarok does have their first Alpha release out entitled [http://amarok.kde.org/en/node/523 Malina]. Nightly builds are available through [http://amarok.kde.org/wiki/User:Apachelogger/Project_Neon Project Neon].
* Konversation has a different release schedule than KDE 4. Konversation 2.0 does not yet have a release schedule.
* digiKam has a different release schedule than KDE 4. They have a [http://www.digikam.org/drupal/node/356 beta release] of the KDE 4 port, with many new features.
* k3b has a different release schedule than KDE 4. An alpha release of 1.1 (the KDE 4 port) is forthcoming, but not yet released.
* [http://kaffeine.kde.org/ Kaffeine] has a different release schedule than KDE 4. The KDE 4 port does not yet have a release schedule.
* Several [http://games.kde.org/ KDE games] do not have a KDE 4 port yet. Among these are kasteroids, kfouleggs, ksirtet.
* [http://www.krusader.org Krusader] has a different release schedule than KDE 4. There is a [http://krusader.org/down.php#development beta release] available.

Schedules/Is KDE 4.1 for you?

2008-07-29T10:19:25Z

Steveire: Clarify a panel autohide issue.

KDE 4.1 is scheduled for release at the end of July 2008. This is a significant milestone for the KDE 4 series and for KDE in general, but as an early
release in the KDE 4 cycle, it does have some known issues which will not be fixed in KDE 4.1. Huge progress has been made in KDE 4.1 which is listed in the [[Schedules/KDE4/4.1_Feature_Plan|KDE 4.1 Feature Plan]].

Some of the more obvious issues are listed below. If these issues are important to you, you should stay with KDE 3.5 or KDE 4.0 until KDE 4.2 when most of these issues are scheduled to be resolved.

It is possible that distributions will work around some of these issues before distributing to users. KDE 4.2 is currently scheduled for release
in February 2009.

== The Desktop ==

The desktop in KDE 4.1 will mark the start of some significant user interface changes. This is a step away from the way the KDE 3 desktop was
designed, but everything possible on your KDE 3.5.9 desktop will also be possible on your KDE 4 desktop. For KDE 4.1, however, some features
are not yet complete, but should be ready for KDE 4.2.

=== FolderView ===

{{Box|Under Construction|2=[[Image:Action_configure.svg|noframe|left|40px]]
'''This page is under construction'''. This section could really do with some screenshots on the page. You can help by [{{fullurl:{{PAGENAME}}|action=edit}} editing this page].
<div class="clear"></div> }}

FolderView is a new technology on the KDE 4 desktop which allows more than one collection of icons on your "desktop" and discourages using it as
dumping ground for miscellaneous files. However, it can still be configured to behave just like KDE 3 did. See [http://blog.lydiapintscher.de/2008/06/14/folderview-is-the-awesome/ this blog entry by Lydia Pintscher] for some more information on FolderView.

The following issues are known and are scheduled to be resolved in KDE 4.2 next February:
* Icons do not need to be in a grid. You can drag them to any point within the FolderView. However, the location you leave them in is not saved, so they will be in a grid again the next time you start the desktop.
* You can have a full screen "desktop with icons", but if you do, you can not have a desktop background. See also: http://www.youtube.com/watch?v=RhYinDOKbE8
* You can have a desktop background, but then you must use the FolderView in regular, not entire screen mode (as shown in Lydia's blog above).

=== Panels and workspaces ===

Some panel issues can be resolved before KDE 4.2. Because of the modular design of Plasma, a new panel could be quite easily written with autohide functionality. This would likely be written by a distribution team or a developer on kde-apps.org.

* Autohiding of panels is not yet configurable.
* It is not possible to set different desktop wallpapers for different virtual desktops.
* The Mac-style menu bar is not available.




== Applications ==

=== New and missing applications ===
Some KDE 3 applications have not yet been ported to KDE 4. Most distributions still package KDE 3 versions of these applications with their KDE 4 desktop. Some notable applications which will not be included in KDE 4.1 are listed below:

* KOffice has a different release schedule than KDE 4. KOffice 2.0 will likely be released late in 2008. [http://www.koffice.org/news.php#itemKOffice20alpha9released Alpha 9] has been released with binaries for all three major platforms. The developers are looking for volunteers to help put together screenshots for [http://www.kdedevelopers.org/node/3545 visual changelogs].
* Amarok has a different release schedule than KDE 4. The Amarok team is currently aiming for a first release in October 2008 for the 2.0 series. Amarok does have their first Alpha release out entitled [http://amarok.kde.org/en/node/523 Malina]. Nightly builds are available through [http://amarok.kde.org/wiki/User:Apachelogger/Project_Neon Project Neon].
* Konversation has a different release schedule than KDE 4. Konversation 2.0 does not yet have a release schedule.
* digiKam has a different release schedule than KDE 4. They have a [http://www.digikam.org/drupal/node/356 beta release] of the KDE 4 port, with many new features.
* k3b has a different release schedule than KDE 4. An alpha release of 1.1 (the KDE 4 port) is forthcoming, but not yet released.
* [http://kaffeine.kde.org/ Kaffeine] has a different release schedule than KDE 4. The KDE 4 port does not yet have a release schedule.
* Several [http://games.kde.org/ KDE games] do not have a KDE 4 port yet. Among these are kasteroids, kfouleggs, ksirtet.
* [http://www.krusader.org Krusader] has a different release schedule than KDE 4. There is a [http://krusader.org/down.php#development beta release] available.

Schedules/KDE4/4.2 Feature Plan

2008-07-23T18:43:11Z

Steveire: /* kdepim */ Move anything not green from KDEPIM 4.1 features to 4.2.

Schedules/KDE4/4.1 Feature Plan

2008-07-23T18:42:25Z

Steveire: /* kdepim */ Move anything not green from KDEPIM 4.1 features to 4.2.

This is a list of planned features for KDE 4.1. '''The deadline for adding entries to this page has already passed'''.

Any features which are not mentioned on this page must be rescheduled for 4.2 and added to the list at [[Schedules/KDE4/4.2 Feature Plan]].

Please ensure that any entries you have on this page are kept up to date with respect to their status (''todo'', ''in-progress'' or ''done'').

Legend:
* todo => not started yet
* in-progress => started, but not completed yet
* done => completed
__TOC__
= 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|various|[[Projects/Widgets_and_Classes | Classes and Widgets]] that should be moved from others modules up into kdelibs|kde-core-devel@kde.org|The Core Developers}}
{{FeatureDone|kdeui|Add KFadeWidgetEffect to easily add fading UI transitions to KDE applications|kretz@kde.org|Matthias Kretz}}
{{FeatureDone|kdeui|Make icon naming spec compliant 3rd party icon themes like Tango or gnome-icon-theme work correctly.|jpetso@gmx.at|Jakob Petsovits}}
{{FeatureDone|kross|Add QtScript support|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KHTML|Support CSS3 Media Queries|germain@ebooksfrance.org|Germain Garand}}
{{FeatureDone|KHTML|Efficient smooth scrolling|germain@ebooksfrance.org|Germain Garand}}
{{FeatureDone|Phonon KCM|More UI feedback|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|better integration of pulseaudio|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|Phonon|allow backend switching on the fly|kretz@kde.org|Matthias Kretz}}
{{FeatureDone|Phonon|subtitle, audio track selection|kretz@kde.org|Matthias Kretz and Ian Monroe}}
{{FeatureTodo|Phonon|DVD menu selection support|imonroe@kde.org|Ian Monroe}}
{{FeatureInProgress|Phonon|update device preference on the fly|kretz@kde.org|Matthias Kretz}}
{{FeatureDone|kdeui|Goya, a framework for inserting controls into itemviews in a really easy and fast way|ereslibre@kde.org|Rafael Fernández López}}
{{FeatureDone | kdeui | Rich textedit widget supporting most rich text features. | steveire@gmail.com | Stephen Kelly }}
{{FeatureInProgress|kdeui|Shortcut schemes for KDE applications|adymo@kdevelop.org|Alexander Dymo}}
{{FeatureDone|kmimetypetrader/kbuildsycoca|Replace use of profilerc for ordering applications with new mimeapps.list standard|faure@kde.org|David Faure}}
{{FeatureDone|knewstuff|Support caching, and speed up the interface through use of Models/Views and goya|jeremy@scitools.com|Jeremy Whiting}}
{{FeatureInProgress|Phonon KCM|Handle advanced devices|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|KDEPrint|Add CUPS Options tabs to QPrintDialog to support n-up, page borders, banner pages, page labels, mirror pages, job scheduling, and manual CUPS options.|john@layt.net|John Layt}}
{{FeatureInProgress|KIO|speed limits on KIO Transfers|nolis71cu@gmail.com|Manolo Valdes}}
{{FeatureInProgress|kdeui|Printing of shortcuts from the shortcut dialog|apaku@gmx.de|Andreas Pakulat}}
{{FeatureDone|Kate Part|Annotation framework for the editor|apaku@gmx.de|Andreas Pakulat}}
{{FeatureInProgress|KJS|Bytecode interpreter and performance improvements|maksim@kde.org|Maks Orlovich}}
{{FeatureInProgress|KHTML|Sync class and file structure with WebKit to prepare merging|porten@kde.org|Harri Porten}}
{{FeatureInProgress|KHTML|contentEditable/designMode implementation|germain@ebooksfrance.org|Germain Garand}}
{{FeatureInProgress|KCalenderSystem|Complete migration of Jalali, Hijri, and Hebrew calendars to new code base.|john@layt.net|John Layt}}
{{FeatureDone|dnssd|Models for service browser and domain browser.|qbast@go2.pl|Jakub Stachowski}}
{{FeatureTodo|KHTML|Adaptable/Scriptable workarounds for broken websites.|maksim@kde.org|Maks Orlovich}}
{{FeatureTodo|KHTML|support for borders-* properties from the CSS3 Background and Borders Module|germain@ebooksfrance.org|Germain Garand}}
{{FeatureInProgress|KHTML|support for Audio/Video tags from the HTML5 draft specification|germain@ebooksfrance.org|Germain Garand}}
{{FeatureDone|KHTML|prospective loading of other network resources while waiting for arrival of blocking scripts|germain@ebooksfrance.org|Germain Garand}}
{{FeatureInProgress|KJS|Public API for extensions. Possibly analog to JavaScriptCore's C API.|porten@kde.org|Harri Porten}}
{{FeatureTodo|KTextEditor|Several interface extensions (e.g. open/save filter)|kwrite-devel@kde.org|Kate Developers}}
{{FeatureTodo|KTextEditor|Plugin for basic collaborative editing|kwrite-devel@kde.org|Kate Developers}}
{{FeatureInProgress|Kate Part|Scripting support for indentation and little helpers|kwrite-devel@kde.org|Kate Developers}}
{{FeatureTodo|Kate Part|Input modes to allow e.g. vim-like editing|kwrite-devel@kde.org|Kate Developers}}
{{FeatureDone|KIO|Implement support for inline editing in KFileItemDelegate|fredrik@kde.org|Fredrik Höglund}}
{{FeatureDone|KIO|Add support for drawing text shadows in KFileItemDelegate|fredrik@kde.org|Fredrik Höglund}}
{{FeatureDone|Emoticons lib|An emoticons library so each applications doesn't have to implement the same things over and over again |brandon.ml@gmail.com|Carlo Segato}}
{{FeatureDone|KFile|Implement fd.o desktop-bookmark-spec for KFilePlacesModel|nf2@scheinwelt.at|Norbert Frese}}
{{FeatureTodo|kdeui| Support for About Data of libs and modules used by a program |kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|kdeui|Drop-in replacement for QFontComboBox, with more informative previews in non-Latin1 locales|caslav.ilic@gmx.net|Chusslove Illich}}
{{FeatureDone|KAboutLicense|Select licenses by keyword, to centralize license info texts for frequent licenses.|caslav.ilic@gmx.net|Chusslove Illich}}
{{FeatureDone|KIO|KIO::AuthInfo and PasswordDialog: optional fields (like "domain"); optional anonymous switch and flag to suppress KIO's password caching|nf2@scheinwelt.at|Norbert Frese}}
{{FeatureTodo|kdeui|Support for KConfigGroup in KConfigSkeleton|aseigo@kde.org|Aaron Seigo}}
|}

= 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
{{FeatureDone|Akonadi|Move the Akonadi development library from kdepim.|vkrause@kde.org|Volker Krause}}
{{FeatureDone|Akonadi|Item streaming in ItemSync/ResourceBase ([[Projects/PIM/Akonadi#Core|details]])|tomalbers@kde.nl|Tom Albers}}
{{FeatureDone|Akonadi|Payload serialization format versioning ([[Projects/PIM/Akonadi#Core|details]])|tokoe@kde.org|Tobias Koenig}}
{{FeatureDone|Akonadi|API for additional item parts ([[Projects/PIM/Akonadi#Core|details]])|tokoe@kde.org|Tobias Koenig}}
{{FeatureDone|Akonadi|Infrastructure for showing additional dialogs from agents/resources ([[Projects/PIM/Akonadi#Core|details]])|tomalbers@kde.nl|Tom Albers}}
{{FeatureDone|Akonadi|Allow to limit ItemFetchJob to current cache content ([[Projects/PIM/Akonadi#Core|details]])|vkrause@kde.org|Volker Krause}}
{{FeatureDone|Akonadi|Fix API for item/collection modifications ([[Projects/PIM/Akonadi#Core|details]])|vkrause@kde.org|Volker Krause}}
{{FeatureDone|Akonadi|Plugin Versioning ([[Projects/PIM/Akonadi#Core|details]])|tokoe@kde.org|Tobias Koenig}}
{{FeatureDone|Akonadi|Tray app ([[Projects/PIM/Akonadi#Core|details]])|tomalbers@kde.nl|Tom Albers}}
{{FeatureDone|Akonadi|Backup support ([[Projects/PIM/Akonadi#Core|details]])|tomalbers@kde.nl|Tom Albers}}
{{FeatureTodo|gpgme++2|newly designed gpgme++ (multithreaded, exceptions, less event loop integration: better for Windows)|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureDone|kpimutils|Change linklocator to use the new emoticon lib|brandon.ml@gmail.com|Carlo Segato}}
|}

= 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
{{FeatureDone|Dolphin|Details-view: Allow to open folders as tree (turned off per default).|peter.penz@gmx.at|Peter Penz}}
{{FeatureDone|Dolphin|Refactor view-action handling to a DolphinViewActionHandler to share more code with DolphinPart|faure@kde.org|David Faure}}
{{FeatureDone|Konqueror|Re-implement Copy To / Move To in the popup menu|faure@kde.org|David Faure}}
{{FeatureDone|Konqueror|Separate Home URL settings in konquerorrc and kfmrc; save toolbar settings into the profile automatically|faure@kde.org|David Faure}}
{{FeatureDone|Dolphin|Simplify selecting of files in the single-click mode (based on http://aseigo.blogspot.com/2006/04/icons.html).|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|Raptor|The KDE4-Application-Menu}}
{{FeatureDone|Dolphin|Provide optional tooltips for files and directories.|peter.penz@gmx.at|Peter Penz}}
{{FeatureDone|Dolphin|Tabs|peter.penz@gmx.at|Peter Penz}}
{{FeatureInProgress|Konqueror|Bring back the large tooltip like in kde3|faure@kde.org|David Faure}}
{{FeatureDone|Konqueror|Session management (save/restore session/restore from crash).|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureDone|Konqueror|Support for undo closed window.|edulix@gmail.com|Eduardo Robles Elvira}}
{{FeatureDone|Konqueror|Allow to configure the Dolphin KPart within the Konquerors settings dialog.|peter.penz@gmx.at|Peter Penz}}
{{FeatureDone|KInfocenter|Improve code and usability.|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureDone|KInfocenter|Reimplement partitions list.|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureDone|KInfocenter|Reimplement memory module.|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureDone|KInfocenter|Reimplement PCI module.|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureTodo|KInfocenter|Reimplement Network module.|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
|}

= 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
{{FeatureDone|Plasma|Kickoff orientation dependent layout|wstephenson@kde.org|Will Stephenson}}
{{FeatureDone|kmenuedit|Restore menu system|montel@kde.org|Laurent Montel}}
{{FeatureDone|KCM autostart|Configure autostart desktop file|montel@kde.org|Laurent Montel}}
{{FeatureDone|Plasma|improve fail to launch and needs
config|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|ksmserver|UI for selecting WMs|l.lunak@kde.org|Luboš Luňák}}
{{FeatureDone|Plasma|polish kickoff|wstephenson@kde.org|Will Stephenson}}
{{FeatureDone|Plasma|toolbox improvements |aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|GHNS2 plasma themes|jeremy@scitools.com|Jeremy Whiting}}
{{FeatureDone|Plasma|Resizable, relocatable panel|binner@kde.org|Stephan Binner}}
{{FeatureInProgress|Solid|Refactor Solid::Control networking|wstephenson@kde.org|Will Stephenson}}
{{FeatureInProgress|Solid|Backend for NetworkManager 0.7|wstephenson@kde.org|Will Stephenson}}
{{FeatureInProgress|System Settings|Filtering/Lazy load category modules|wstephenson@kde.org|Will Stephenson}}
{{FeatureInProgress|KSysGuard|Monitor process I/O|tapsell@kde.org|John Tapsell}}
{{FeatureInProgress|Plasma|Mac-like menu bar plasmoid|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureTodo|System Settings|Administrator mode support|wstephenson@kde.org|Will Stephenson}}
{{FeatureInProgress|krunner|Revamp GUI.|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureDone|Plasma|keyboard shortcuts|Chani Armitage|chanika@gmail.com}}
{{FeatureDone|Plasma|webkit widget|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|dashboard widget support|aseigo@kde.org|Aaron Seigo}}
{{FeatureInProgress|Plasma|QtScript scriptengine|richmoore44@gmail.com|Richard Moore}}
{{FeatureInProgress|Plasma|Improve QtScript support|richmoore44@gmail.com|Richard Moore}}
{{FeatureInProgress|Plasma|Zooming User Interface|chanika@gmail.com|Chani Armitage}}
{{FeatureDone|Plasma|Multiple Desktop Containments|chanika@gmail.com|Chani Armitage}}
{{FeatureDone|Plasma|API changes [[Projects/Plasma/Tokamak1]]|panel-devel@kde.org|Plasma team }}
{{FeatureDone|Plasma|Panel Toolbox|notmart@gmail.com|Marco Martin}}
{{FeatureDone|Plasma|Panel changes to make it work with the new default theme|notmart@gmail.com|Marco Martin}}
{{FeatureInProgress|Plasma|Generic folder view applet/containment, that can also be used as the desktop background (showing the desktop folder).|fredrik@kde.org|Fredrik Höglund}}
{{FeatureDone|Krunner|Configuration dialog for KRunner|ryan.bitanga@gmail.com|Ryan P. Bitanga}}
{{FeatureDone|Plasma|Temperature sensing in the device engine|cblauvelt@gmail.com|Christopher Blauvelt}}
{{FeatureDone|Plasma|Video data in the device engine|cblauvelt@gmail.com|Christopher Blauvelt}}
{{FeatureTodo|Plasma|New plasma themes|nuno@oxygen-icons.org|Nuno Pinheiro}}
{{FeatureDone|Plasma|change showConfigurationInterfaction to createConfigurationInterface|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|Plasma|Plasma::Service |aseigo@kde.org|Aaron Seigo}}
{{FeatureTodo|Plasma|panel hiding |aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|KWin|non-linear animations also for KWin|sebas@kde.org|Sebastian Kuegler}}
{{FeatureDone|KWin|Compiz's wobbly like effect for KWin|cedric.borgese@gmail.com|Cédric Borgese}}
{{FeatureDone|KDM|Theme KDM (login manager) by default|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|Splash screen|New default splashscreen|riccardo@kde.org|Riccardo Iaconelli}}
{{FeatureInProgress|Nepomuk|Simple Desktop Search client based on Nepomuk search|trueg@kde.org|Sebastian Trueg}}
{{FeatureInProgress|Plasma|Add a dataengine that implements Notifications DBus interface plasmoid which provides cute visualization of notifications along with nice and easy way to interact with them|dimsuz@gmail.com|Dmitry Suzdalev}}
{{FeatureDone|Plasma|loadDefaultSetup from a file, not hardcoded|aseigo@kde.org|Aaron Seigo}}
{{FeatureDone|ksmserver|Make the fade-to-gray logout effect work even when composite is disabled|fredrik@kde.org|Fredrik Höglund}}
|}

= 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|nepomuk|Service that monitors file rename and delete operations and updates the metadata accordingly. kded module already exists in playground. problem: depends on inotify.|trueg@kde.org|Sebastian Trueg}}
{{FeatureDone|KCM emoticons|Adding/editing/removing emoticons theme|brandon.ml@gmail.com|Carlo Segato}}
{{FeatureDone|KCM splash screen|Be able to install splash screen themes via GHNS2|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|KCM icons|Be able to install icon themes via GHNS2|mail@dipe.org|Sebastian Sauer}}
{{FeatureInProgress|phonon-xine|snapshots in video widget|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|phonon-xine|try to make VideoWidget work on GraphicsView|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|phonon-xine|make states compatible to other backends|kretz@kde.org|Matthias Kretz}}
{{FeatureTodo|phonon-xine|better support for pulseaudio (most work possibly in kdelibs)|kretz@kde.org|Matthias Kretz}}
{{FeatureInProgress|phonon-gstreamer|Make phonon-gstreamer as released with Qt 4.4 fully integrate into KDE and add the features added to libphonon after libphonon 4.1|kretz@kde.org|Matthias Kretz}}
{{FeatureDone|desktop ioslave|Add an ioslave that lists the contents of the desktop folder, and reports the names in the .desktop files instead of the actual file names.|fredrik@kde.org|Fredrik Höglund}}
{{FeatureDone|knotify|Add support for galago-like desktop notifications spec - if knotify will find a certain DBus service on session bus, it'll forward its popup notification events to this service |dimsuz@gmail.com|Dmitry Suzdalev}}
{{FeatureDone|Oxygen cursors|Oxygen cursor set|riccardo@kde.org|Riccardo Iaconelli}}
|}

= 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
{{FeatureDone|KMagnifier|Add color blindness simulation|mw_triad@users.sourceforge.net|Matthew Woehlke}}
|}

= 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
{{FeatureDone|KSystemLog|KSystemLog, a Log Viewer Tool. Move from kde-apps|nicolas.ternisien@gmail.com}}
{{FeatureDone|KCron|Do some refactoring in KCron|nicolas.ternisien@gmail.com}}
{{FeatureDone|KCron|Improve ergonomy and general interface|nicolas.ternisien@gmail.com}}
{{FeatureDone|KCron|Fix all existing bugs in KCron|nicolas.ternisien@gmail.com}}
{{FeatureDone|KCron|Convert KCron into a KCM Module, to use it in System Settings|nicolas.ternisien@gmail.com}}
{{FeatureInProgress|Environment Variables|Create a environment variables KCM Module|nicolas.ternisien@gmail.com}}
|}

= kdeartwork =
{| 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
|}

= 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
{{FeatureDone|Smoke2|Move modular Smoke2 to kdebindings-trunk.|kde-bindings@kde.org|KDE-bindings developers}}
{{FeatureDone|PHP-Qt|Move PHP-Qt to kdebindings-trunk.|kde-bindings@kde.org|KDE-bindings developers}}
{{FeatureDone|krossjava|Move krossjava to kdebindings-trunk.|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|krosspython|Implicit convert PyQt/PyKDE QObject/QWidget instances.|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|krossruby|Implicit convert QtRuby/Korundum QObject/QWidget instances.|mail@dipe.org|Sebastian Sauer}}
{{FeatureDone|Qyoto|Add delegate support for signal/slot connections.|kde-bindings@kde.org|KDE-bindings developers}}
|}

= 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
{{FeatureDone|Kalzium|Clean up the database. I am syncing with the BlueObelisk data repository again. There we decided to remove the density (not a element property but a compound property. I also removed the mean weight. We think it is better to provide correct data than a lot (but partly wrong) data.|cniehaus@kde.org|Carsten Niehaus}}
{{FeatureDone|KAlgebra|Calculator Plasmoid|aleixpol@gmail.com|Aleix Pol}}
{{FeatureDone|KAlgebra|Vector support|aleixpol@gmail.com|Aleix Pol}}
{{FeatureDone|KAlgebra|2D Function support improved|aleixpol@gmail.com|Aleix Pol}}
{{FeatureDone|Step|A physics simulator, move from playground to kdeedu module |ks.vladimir@gmail.com|Vladimir Kuznetsov}}
{{FeatureDone|Kalzium|Update the snapshot of libavogadro to 0.6.1. This introduces a gazillion new possibilities for the 3D renderer and fixes many issues.|cniehaus@kde.org|Carsten Niehaus}}
{{FeatureDone|Kalzium|Make use of the new libavogadro-version.|cniehaus@kde.org|Carsten Niehaus}}
{{FeatureDone|Kalzium|Expose molecular editing features of libavogadro.|marcus@cryos.org|Marcus D. Hanwell}}
{{FeatureDone|Marble|Copy position to clipboard|tackat@kde.org|Torsten Rahn}}
{{FeatureDone|Marble|Create Tiles on compile time|tackat@kde.org|Torsten Rahn}}
{{FeatureDone|Parley|Redesigned main window|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureDone|Parley|Vocabulary Plasmoid|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureDone|Step|Improve GUI for creating gas|ksvladimir@gmail.com|Vladimir Kuznetsov}}
{{FeatureDone|KAlgebra|Variables share between 2D and Console|aleixpol@gmail.com|Aleix Pol}}
{{FeatureDone|Parley|Export as HTML support|frederik.gladhorn@kdemail.net|Frederik Gladhorn}}
{{FeatureDone|Kiten|Link radselect with kiten|jkerian@gmail.com|Joe Kerian}}
{{FeatureDone|Kiten|Sort output by dictionary/user selected sorting values|jkerian@gmail.com|Joe Kerian}}
{{FeatureDone|Kig|Cubic-line intersection in case two of the three intersection points are already present|paolini@dmf.unicatt.it|Maurizio Paolini}}
|}

= 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|KBreakout|New game|fela.kde@gmail.com}}
{{FeatureDone|KDiamond|New game|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|Kollision|New game|p.capriotti@gmail.com|Paolo Capriotti}}
{{FeatureDone|KsirK|New game|kleag@free.fr|Gaël de Chalendar}}
{{FeatureDone|Kubrick|New game|ianw}}
{{FeatureDone|KBattleship|Bring back Zeroconf support for network games|qbast@go2.pl}}
{{FeatureDone|KBlocks|Finish display of points and level|piacentini@kde.org}}
{{FeatureDone|KBlocks|Implement KNewStuff support|piacentini@kde.org}}
{{FeatureDone|KBlocks|Implement key/action/shortcut configuration|piacentini@kde.org}}
{{FeatureDone|KBlocks|Docbook|piacentini@kde.org}}
{{FeatureDone|KMines|Add pause actions|eike.lange@kdemail.net}}
{{FeatureDone|KNetWalk|Better scoring system|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureDone|KNetWalk|Add support for loading new themes|fela.kde@gmail.com|Fela Winkelmolen}}
{{FeatureDone|KNetWalk|Configurable keyboard support|eike.lange@kdemail.net}}
{{FeatureInProgress|KGoldRunner|Improved theming and animation|mikelima@cirulla.net}}
{{FeatureInProgress|KGoldRunner|Sound support and theming|mikelima@cirulla.net}}
{{FeatureInProgress|KSquares|Multiplayer support|josef}}
{{FeatureInProgress|KGGZ|Add kggzcore and kggzdmod libraries|josef}}
{{FeatureTodo|KBlocks|Add additional themes|piacentini@kde.org}}
{{FeatureTodo|KGGZ|Add new Qt4-based core client as successor to the old KDE3-based KGGZ|josef (now SoC proposal)}}
{{FeatureTodo|KGGZ|Fire-and-forget highscore submission for single-player games and client-to-client multiplayer games|josef)}}
{{FeatureTodo|KGoldRunner|Also see kdegames/kgoldrunner/TODO|ianw}}
{{FeatureTodo|KGoldRunner|Hot new stuff support for themes and levels|mikelima@cirulla.net}}
{{FeatureTodo|KGoldRunner|Startup screen|mikelima@cirulla.net}}
{{FeatureTodo|KMahjongg|Reimplement the Board Editor|piacentini@kde.org}}
{{FeatureTodo|KShisen|Port to KScoreDialog|piacentini@kde.org}}
|}

= 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|Gwenview|Undo system|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureDone|Gwenview|Fullscreen meta information|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureDone|Gwenview|Ability to open an image with another application|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureDone|Okular|Better Text-To-Speech integration: speech the whole document, the current page or the selection.|pino@kde.org|Pino Toscano}}
{{FeatureDone|Okular|Encryption support for ODF generator|bradh@kde.org}}
{{FeatureDone|Okular|Backward direction for text search.|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Okular|Centralized text & graphics antialias configuration.|pino@kde.org|Pino Toscano}}
{{FeatureDone|Okular|EPub backend.|elylevy@cs.huji.ac.il|Ely Levy}}
{{FeatureInProgress|Okular|Improved form support (add missing types, handle the fields better).|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Gwenview|Support for tagging with Nepomuk|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureInProgress|Gwenview|Thumbnail bar in view and fullscreen modes|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureDone|Gwenview|Crop ratio|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|KIPI support|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Red eye correction|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Start page|aurelien.gateau@free.fr|Aurélien Gâteau}}
{{FeatureInProgress|Okular|JavaScript support (mostly for PDF documents).|pino@kde.org|Pino Toscano}}
{{FeatureDone|Okular|Improved placement and sizing of the presentation mode: choose the screen to use, adapt to screen size changes.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Caret annotations.|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Okular|File attachment annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Sound annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Link annotations.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Improve annotation support: for existing types (rubber stamps, line, note, etc), and for the way they are constructed and handled.|pino@kde.org|Pino Toscano}}
{{FeatureInProgress|Okular|Separate the "view properties" out of the Document, in a View class. Use it for the page view and the presentation mode.|pino@kde.org|Pino Toscano}}
{{FeatureTodo|Okular|Per-document zoom level.|pino@kde.org|Pino Toscano}}
{{FeatureDone|libksane|Move libksane to kdegraphics|kare.sars@kolumbus.fi|Kåre Särs}}
{{FeatureDone|ksaneplugin|Replase libkscan with ksaneplugin|kare.sars@kolumbus.fi|Kåre Särs}}
|}

= 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
{{FeatureDone|Dragon Player|A simple Phonon-based videoplayer application|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|Make Dragon indipendent from Xine|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|File Manager|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|play media dialog|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|slider changes|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureInProgress|Dragon Player|show info while playing audio files|ian.monroe@gmail.com|Ian Monroe}}
{{FeatureDone|JuK|Show cover art from more sources|michael.pyne@kdemail.net|Michael Pyne}}
|}

= 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
{{FeatureDone|KGet|Group-Settings|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Torrent-Support|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Transfer-Settings|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Webinterface|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|Kopete|AIM offline messages|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureDone|Kopete|OTR Encryption support|michael_zanetti@gmx.net|Michael Zanetti}}
{{FeatureDone|Kopete|Status manager|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureDone|Kopete|Non-intrusive notification system|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureDone|Kopete|Bring back chat style selection via knewstuff2|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Kopete|ICQ 6 status icons|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureInProgress|Kopete|Use notebook lid for auto away|kedgedev@centrum.cz|Roman Jarosz}}
{{FeatureDone|Kopete|use the new emoticons library|brandon.ml@gmail.com|Carlo Segato}}
{{FeatureDone|KGet|Nepomuk-Integration|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Global Speedlimits|l.appelhans@gmx.de|Lukas Appelhans}}
{{FeatureDone|KGet|Setup libbtcore from KTorrent in KGet (to avoid dependency to extragear)|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|KGet|Extend the TransferHistory to use SQLite and XML-Backends and display the information inside a kcategorizedview|jgoday@gmail.com|Javier Goday}}
{{FeatureTodo|Kopete|GroupWise chatroom support|wstephenson@kde.org|Will Stephenson}}
{{FeatureTodo|[http://decibel.kde.org Decibel]|Decibel, a framework for real time communication services. Move from playground/pim|info@basyskom.de|Tobias Hunger}}
{{FeatureDone|KRDC|Optional system tray icon (with quick access to bookmarks)|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|KRDC|Improved behavior of entering special keys for better workflow|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|KRDC|Zeroconf support (detecting remote desktop services in local network)|romnes@stud.ntnu.no|Magnus Romnes}}
{{FeatureDone|KRDC|Bookmark dock widget for quick access to bookmarks|uwolfer@kde.org|Urs Wolfer}}
{{FeatureDone|KRDC|Support for up- and downscaling VNC remote desktop|uwolfer@kde.org|Urs Wolfer}}
|}

= 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
{{FeatureDone|KAddressbook|Ability to add LDAP search results to distribution lists|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KAddressbook|Indication of which resource folder a contact belongs to|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KAddressbook|Read-only view for contacts in read-only folders|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KAddressbook|copy/cut/paste context menu items|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KAlarm|Allow use of multiple calendar resources|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Handle time zones and seasonal time changes properly|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Abolish alarm daemon and make kalarm trigger alarms itself|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Replace simple repetitions by recurrence sub-repetitions to reduce confusion|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|New option for display alarm text to be generated by a command|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Option to display alarm only if pre-alarm command succeeded|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|New option to specify reminder times in minutes|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|New option to restrict alarms to working hours|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Prevent multiple identical error messages accumulating for the same alarm|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Provide "don't show again for this alarm" option for command error messages|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Remember main window show/hide options used when KAlarm closed instead of setting them in Preferences dialog|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Simplification and improvements to alarm edit dialog|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Option to display alarms in centre of screen, with enable delay on buttons to avoid accidental acknowledgement|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KJots|Support more rich text features like text formatting, hyperlinks and ordered/unordered lists.|steveire@gmail.com|Stephen Kelly}}
{{FeatureDone|KJots|Add checkmarks to pages.|steveire@gmail.com|Stephen Kelly}}
{{FeatureDone|KJots|Port to KRichText widget.|steveire@gmail.com|Stephen Kelly}}
{{FeatureDone|KJots|Create a Kontact::Plugin to integrate kjots into Kontact.|steveire@gmail.com|Stephen Kelly}}
{{FeatureDone|Kleopatra|Ability to search in internal and external certificates at the same time|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|Kleopatra|General UI Server|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureDone|Kleopatra|New, tabbed, mainwindow design|marc@kdab.net|Marc Mutz (Gpg4win)}}
{{FeatureDone|KMail|Ability to create hyperlinks in HTML messages|steveire@gmail.com|Stephen Kelly}}
{{FeatureDone|KMail|Ability to easily create todos with reminders from emails|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Ability to open messages from search results when the reader is hidden|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Better invitation update emails showing what changed|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Better reminder visualization in very small events|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Better, natural language search criteria names|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Clickable status columns|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Client side configurability of warnings in shared folders|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Colored ribbons for indication of signing and encryption status in the composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Configuration option for whether invitation emails are automatically deleted or not when having been acted upon|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Copy/paste and drag and drop from/to the mail composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Decryption on demand in reader window|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Display of quota information in foldertree tooltips|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Drag and drop and copy and paste support in the search result viewer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Drag and drop from the mail reader window and mime-tree viewer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Drag and drop of folders|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Editing of attachments from the composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Export and import of filters|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Favorites Folder|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Folder quicksearch|m.koller@surfeu.at|Martin Koller}}
{{FeatureDone|KMail|Harmonization of actions in main and standalone mail reader windows|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|IMAP Server storage of non-standard flags|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Improved TNEF attachment handling|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Improved quota warnings|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Initialize full search from quicksearch on request|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Override font and fontsize for standalone message viewers|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Per-folder identity configurability|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Recursive IMAP cache troubleshooting|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Resizable recipients area in composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Support for creating new mails based on received mails (Resend)|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Support for immediate sync of resource folders|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Support for soft line breaking|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Tab navigation through groups in the address completion|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Text snippets with shortcuts and variable expansion in the composer|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Warning about active out-of-office scripts|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|lost+found recovery of locally changed folders that lose access rights|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KMail|Port to use KRichTextEdit||Thomas McGuire}}
{{FeatureDone|KNotes|Ability to print notes|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KonsoleKalendar|Support "file" and "localdir" resources|winter@kde.org|Allen Winter}}
{{FeatureDone|Kontact|Config option to close despite system tray|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|Kontact|Harmonization of component naming in sidebar, configuration, summary view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|Kontact|Right-aligned component navigation toolbar|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|Kontact|Ubiquitous sync actions|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Ability to have both distribution lists and addresbook extension visible|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Aggregated reminders view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Better default resource colors|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Drag and drop of attachments|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Faster initial loading of kolab resources|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Forwarding and delegation of invitations|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Improved coloring of agenda view items|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Improved event printing|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Merge of the attachment view in into the main page|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Merge of the free-busy and attendee views for easier scheduling|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Month view scrolling, paging, mouse-wheeling|tom_t@gmx.at|Thomas Thrainer}}
{{FeatureDone|KOrganizer|More readable Kolab resource folder labels|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Redesigned incidence editor UI|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Side-by-side calendar view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Support for by-value attachments|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Timeline calendar view|kdepim@kdab.net|Kolab Konsortium}}
{{FeatureDone|KOrganizer|Rich text incidence editor|mike@mikearthur.co.uk|Mike Arthur}}
{{FeatureDone|KOrganizer|Hide/Show reminder daemon icon in the systeay|winter@kde.org|Allen Winter}}
{{FeatureDone|KOrganizer|New To-do View (model/view)|tom_t@gmx.at|Thomas Thrainer}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Column-specific whatsthis-help| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Combined search and add task widget| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Drag&Drop| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|File management (file->load)| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Managing history| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Tracking tasks by active applications| |Thorsten Stärk}}
{{FeatureDone|[http://wiki.kde.org/ktimetracker ktimetracker]|Whatsthis-help dependent on if a task has been created| |Thorsten Stärk}}

{{FeatureDone|KMail|HTML Signatures|yez@familieschepers.nl|Edwin Schepers}}

{{FeatureDone|KOrganizer|New Month View (qgraphicsitem)|bvirlet@kdemail.net|Bruno Virlet}}
{{FeatureDone|KMail|Improved error messages and audit log for cryptographic operations|kdepim@kdab.net|Kolab Konsortium}}

{{FeatureDone|KOrganizer|Ability to jump to the right day in the agenda from invitation mails|kdepim@kdab.net|Kolab Konsortium}}

|}

= 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
{{FeatureDone|Cervisia|New context menu entry "Add to Ignore List"|christian.loose@hamburg.de|Christian Loose}}
{{FeatureDone|Lokalize|Move this application (formerly known as Kaider) from extragear|shafff-at-ukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Cervisia|A file view based on KDirModel|christian.loose@hamburg.de|Christian Loose}}
{{FeatureInProgress|KBugBuster|Make it work|fabiolocati@gmail.com|Fabio Locati}}
{{FeatureInProgress|KCachegrind|Everything working again|josef.weidendorfer@gmx.de|Josef Weidendorfer}}
{{FeatureInProgress|Kate|Session plasmoid|montel@kde.org|Laurent Montel}}
{{FeatureDone|KAppTemplate|Make a GUI for it |annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureDone|KAppTemplate|Add a PyQt4 template|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureDone|KAppTemplate|Add a Ruby template|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureDone|KAppTemplate|Add a Plasmoid template|annma@kde.org|Anne-Marie Mahfouf}}
{{FeatureTodo|KCachegrind|Better handling of huge symbols|josef.weidendorfer@gmx.de|Josef Weidendorfer}}
{{FeatureTodo|kioslave svn|Add Export/Import feature|montel@kde.org|Laurent Montel}}
{{FeatureTodo|Kate App|Improved session management|kwrite-devel@kde.org|Kate Developers}}
|}

= kdetoys =
{| 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
|}

= 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
{{FeatureDone|printer-applet|Add printer applet for viewing print jobs and printer auto-configuration.|jriddell@ubuntuFIXMEcom|Jonathan Riddell}}
{{FeatureDone|Okteta|binary/hex editor (successor to KHexEdit). Move from playground/utils.|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|enable extract-strings tool and add copy|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|add "Export as"|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|make printing support only selection|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureInProgress|Okteta|ask artists for own icon|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Okteta|more explicit titels for undo/redo actions, also from filters|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureInProgress|KDiskFree|Use Solid API|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureTodo|KwikDisk|Replace it by a Plasmoid (in the desktop bar and on the desktop|nicolas.ternisien@gmail.com|Nicolas Ternisien}}
{{FeatureDone|SuperKaramba|Integrate Kross and be able to write Karambas using Python, Ruby and JavaScript||The SuperKaramba Team}}
{{FeatureDone|SuperKaramba|Integrate into Plasma||The SuperKaramba Team}}
|}

= kdevelop =
{| 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
|}

= kdevplatform =
{| 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
|}

= kdewebdev =
{| 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|Kommander|Port the executor to KDE4.|amantia@kde.org|Andras Mantia}}
{{FeatureTodo|Kommander|Create Qt Designer plugins for the editor.|amantia@kde.org|Andras Mantia}}
{{FeatureInProgress|Quanta Plus|Create an upload plugin.| niko.sams@gmail.com|Niko Sams}}
{{FeatureInProgress|Quanta Plus|Create a new, state machine based parser.| amantia@kde.org|Andras Mantia}}
{{FeatureInProgress|Quanta Plus|Port existing functionality to KDevPlatform plugins. Only text mode is targeted.|amantia@kde.org|Andras Mantia}}
{{FeatureDone|KXslDbg|Port to KDE4.|keith@kdewebdev.org |
Keith Isdale}}
{{FeatureTodo|KLinkStatus|Aided correction of broken links||}}
{{FeatureDone|KLinkStatus|Site check automation|moura@kdewebdev.org|Paulo Moura Guedes}}
{{FeatureInProgress|KLinkStatus|D-Bus/Scripting interfaces|moura@kdewebdev.org|Paulo Moura Guedes}}
{{FeatureInProgress|KLinkStatus|HTML validation|thesquib@gmail.com|Sam Ryan}}
{{FeatureDone|KLinkStatus|Ability to export only broken links|moura@kdewebdev.org|Paulo Moura Guedes}}
{{FeatureDone|KLinkStatus|Ability to do background search which only update the GUI when finished (much faster))|moura@kdewebdev.org|Paulo Moura Guedes}}
{{FeatureDone|KLinkStatus|Tray Icon and KUniqueApplication|Paulo Moura Guedes}}
{{FeatureDone|KLinkStatus|Scripting Plugin|Paulo Moura Guedes}}
{{FeatureDone|KLinkStatus|Get Hot New Stuff for HTML result stylesheets|Paulo Moura Guedes}}
|}

Template:SEFBox

2008-07-23T16:46:35Z

Steveire: Add some padding between the top and bottom rows.

<div style="visibility:hidden;" >
=== {{{name}}} ===
</div>
<div class="rbroundbox" style="width:100%;">
<div class="rbtopwrap">
<div class="rbtop"><div></div></div>{{{name}}}</div>
<div class="rbcontent">
{|style="width:100%; background:#dadde0"
|-
| width=50% align=center valign=top | '''Current State'''  
| width=50% align=center valign=top | '''People'''  
|-
| style="padding-right:10pt" valign=top |
{{{currentState|n/a}}}
| valign=top |
{{{people|Unknown}}}
|-
| style="padding-top:10pt" width=50% align=center valign=top | '''Get Involved'''  
| style="padding-top:10pt" width=50% align=center valign=top | '''Alternative Tools'''  
|-
| style="padding-right:10pt" valign=top |
{{{getInvolved|n/a}}}
| valign=top |
{{{altTools|n/a}}}
|}
</div>
<div class="rbbot"><div></div></div>
</div>

Development/Further Information

2008-07-19T13:09:23Z

Steveire: (spam) Undo revision 30190 by 61.19.54.164 (Talk)

{{Template:I18n/Language Navigation Bar|Development/Further Information}}
== Web Sites ==
* [http://www.KDE.org KDE Home]
* [http://dot.kde.org KDE Dot News]
* [http://www.planetkde.org Planet KDE]

==Blogs==

== Books ==
Below are a list of books associated with KDE 4 development. These may be specific to applications, using the Qt Toolkit, or specifically KDE 4 books.

===KDE 4 Development Books===

[mailto:manishchaks@gmail.com Manish Chakravarty ] from [http://kde.in KDE India] is working on a KDE 4 programming book.
The scheduled release date is the the 15th of August 2007

===Qt 4 Development Books===

==== English ====

'''[http://www.qt4-book.com/ The Book of Qt 4: The Art of Building Qt Applications] by Daniel Molkentin'''

Daniel Molkentin, author of this book, is a core developer of KDE. He uses practical examples to explain Qt characteristics like the signal slot concept and its event system. He guides the reader through developing applications both with and without Qt's graphical GUI builder "Qt Designer." Topics covered include: tools needed to create dialog boxes; steps to follow when developing a GUI-based application; layout; how to visualize data using Qt's "model-view concept"; the QtSql model; the graphics library; as well as how to work with XML, databases, threads, and debugging. The book also includes lots of useful hints on how to use Qt's own datatypes, containers and algorithms and how to develop user-friendly applications.

Available via: [http://www.amazon.com/Book-Qt-Art-Building-Applications/dp/1593271476 Amazon]

'''[http://www.apress.com/book/view/1590598318 Foundations of Qt Development] by Johan Thelin'''

Foundations of Qt Development is based on Qt 4.2, and is aimed at C++ programmers who want to become proficient using this excellent toolkit to create graphical applications that can be ported to all major platforms. The book is focused on teaching you to write your own code in addition to using existing code. And common areas of confusion are identified, addressed, and answered. Youll learn everything you need to know to get up and running fast.

'''[http://www.informit.com/store/product.aspx?isbn=0131879057 An Introduction to Design Patterns in C++ with Qt 4] by Alan Ezust, Paul Ezust'''

Now, with the help of An Introduction to Design Patterns in C++ with Qt 4.1, you can master C++ and design patterns together, using the world's #1 open source framework for cross-platform development: Qt 4.1. This complete tutorial and reference assumes no previous knowledge of C, C++, objects, or patterns. You'll walk through every core concept, one step at a time, learning through an extensive collection of Qt 4.1-tested examples and exercises. Learn objects fast: classes, inheritance, polymorphism, and more. Master powerful design patterns, from Iterator and Visitor to Abstract Factory and Facade. Discover efficient high-level programming techniques utilizing libraries, generics, and containers. Build graphical applications using Qt widgets, models, and views.

Available via: [http://www.amazon.com/gp/product/0131879057 Amazon]<br />

Available on-line at [http://cartan.cas.suffolk.edu/moin/OopDocbook?page=index.html Suffolk University]

'''[http://www.informit.com/store/product.aspx?isbn=0131872494 C++ GUI Programming with Qt 4] by Jasmin Blanchette, Mark Summerfield'''

The only official best-practice guide to Qt 4.1 Programming. Using C++ GUI Programming with Qt 4 you'll discover the most effective Qt 4 programming patterns and techniques as you master key technologies ranging from Qt's model/view architecture to Qt's powerful new 2D paint engine. The authors provide readers with unparalleled insight into Qt's event model and layout system. Then, using realistic examples, they introduce superior techniques for everything from basic GUI development to advanced database and XML integration.

Available via: [http://www.amazon.com/gp/product/0131872494 Amazon]

Free download is available from [http://www.qtrac.eu/C++-GUI-Programming-with-Qt-4-1st-ed.zip Mark Summerfield's web page] (ZIP with PDF, 5.5 MiB)

'''Note''': the 2nd edition is now available which was updated for Qt 4.3 and is available from [http://www.amazon.com/Programming-Prentice-Source-Software-Development/dp/0132354160 Amazon]

'''[http://www.informit.com/store/product.aspx?isbn=0131240722 C++ GUI Programming with Qt 3]'''

The first official Trolltech guide to Qt 3.2 programming written by Trolltech software engineer Jasmin Blanchette and Trolltech's documentation manager Mark Summerfield, with a foreword by Matthias Ettrich, Trolltech lead developer and founder of the KDE project. The book teaches every facet of Qt 3 programming, ranging from basic user interfaces and layout managers to 2D/3D graphics, drag-and-drop, signaling, networking, XML, database integration, even internationalization and multithreading. The book in PDF format and sources can be downloaded from linked publisher's page.

Available via: [http://www.amazon.com/gp/product/0131240722 Amazon]<br />

Available on-line at: [http://www.phptr.com/content/images/0131240722/downloads/blanchette_book.pdf Prentice-Hall] (free PDF download)

'''[http://www.pragmaticprogrammer.com/titles/ctrubyqt/ Rapid GUI Development with QtRuby]'''

See how to use the powerful Qt3 library to create cross-platform GUI applications for Linux and OS X in Ruby. Covers installation, basic and advanced programming, event models, and Korundum. A must if you want to develop software with QtRuby/Korundum.

'''[http://www.charlesriver.com/Books/BookDetail.aspx?productID=114877 Open Source Game Development: Qt Games for KDE, PDA's, and Windows]'''

This book provides beginning and intermediate game programmers with a step-by-step resource to desktop game programming. The reader is introdcuded into the development of a desktop game application using Qt3/Qt4/Qtopia/KDE as development platform. Desktop game relevant topics such as pathfinding, AI, sound, 2D and 3D graphics and network programming are introduced in the scope of Qt and KDE. All topics are accompanied by plenty of source code examples in the book and on the companion CD-ROM.

Available via: [http://www.amazon.com/gp/product/1584504064 Amazon]

==== German ====

[https://www.opensourcepress.de/index.php?26&backPID=15&tt_products=23 Qt 4: Einführung in die Applikationsentwicklung von Daniel Molkentin]

===C++ Programming Books===

==== English ====

'''A Complete Guide to Programming in C++'''

Suited for both complete novices and advanced users of C++. Takes a clear and logical approach using uncluttered English and purposeful examples. With examples and website content, it represents great value for the money and is highly recommended as both a tutorial for students and newcomers to C++ and a dip-in guide for more advanced practitioners. This book teaches you the C++ STL in a natural way while learning C++, while many others relegate the STL to an appendix.

Available via: [http://www.amazon.com/gp/product/0763718173 Amazon]

'''Problem Solving, Abstraction, and Design Using C++'''

This book presents introductory programming material. Only the features of C++ that are appropriate to introductory concepts are introduced. Object-oriented concepts are presented. Abstraction is stressed throughout the book and pointers are presented in a gradual and gentle fashion for easier learning.

Available via: [http://www.amazon.com/exec/obidos/ASIN/0201612771/ Amazon]

'''[http://www.mindview.net/Books/TICPP/ThinkingInCPP2e.html Thinking in C++]'''

The effective presentation, along with dozens of helpful code examples, make this book a standout. The text first sets the stage for using C++ with a tour of what object-oriented programming is all about, as well as the software design life cycle. The author then delves into every aspect of C++, from basic keywords and programming principles to more advanced topics, like function and operator overloading, virtual inheritance, exception handling, namespaces, and templates. C++ is a complex language, and the author covers a lot of ground using today's Standard C++, but without getting bogged down in excessive detail.

Available via: [http://www.amazon.com/exec/obidos/ISBN=0139798099/ Amazon]<br />
Available via: [http://www1.fatbrain.com/FindItNow/Services/home.cl?from=YGY567&store=1 Fatbrain]

'''Accelerated C++: Practical Programming by Example'''

If you don't have a lot of time, but still want to learn the latest in C++, you don't have to learn C first. You might learn more by digging into current language features and classes from the very beginning. That's the approach that's offered by Accelerated C++, a text that delves into more advanced C++ features like templates and Standard Template Library (STL) collection classes early on. This book arguably can get a motivated beginning programmer into C++ more quickly than other available tutorials.

Available via: [http://www.amazon.com/exec/obidos/ASIN/020170353X/ Amazon]

'''Effective C++: 50 Specific Ways to Improve Your Programs and Design'''

Highly recommended by KDE core developers! It is not a book on syntax, so this should not be the 1st C++ book that you read -- but it should *definitely* be the 2nd! An absolutely terrific book focusing on basic C++ and object-oriented programming techniques. A crucial book for anyone new to C++ to read.

2nd Edition Available via: [http://www.amazon.com/exec/obidos/ASIN/0201924889/ Amazon]<br />
3rd Edition Available via: [http://www.amazon.com/exec/obidos/ASIN/0321334876/ Amazon]

'''More Effective C++: 35 New Ways to Improve Your Programs and Designs'''

From the author of the indispensable Effective C++, here are 35 new ways to improve your programs and designs. Drawing on years of experience, Meyers explains how to write software that is more effective: more efficient, more robust, more consistent, more portable, and more reusable. In short, how to write C++ software that's just plain better. For programmers at the intermediate level and above.

Available via: [http://www.amazon.com/exec/obidos/ASIN/020163371X/ Amazon]

'''C++ FAQs'''

This book answers all the questions one can imagine about C++. The author explains the reasoning and principals behind good OO design in a simple and well informed manner. See also the free online [http://www.parashift.com/c++-faq-lite/ C++ FAQ LITE]. If you like the online lite version, you will be ecstatic about the printed book version because it covers much more.

Available via: [http://www.amazon.com/exec/obidos/ASIN/0201589583/ Amazon]

'''[http://www.icce.rug.nl/documents/cplusplus/cplusplus.html C++ Annotations]'''

This online book is intended for knowledgeable users of C who would like to make the transition to C++. It is a guide for C++ programming courses given at the University of Groningen, Netherlands. As such, the book is not a complete C++ handbook. Rather, it serves as an addition to other documentation sources.

Available via: [http://www.amazon.com/exec/obidos/ASIN/020163371X/ Amazon]

'''The C++ Programming Language'''

By Bjarne Stroustrup, the creator of C++. This book is not for people who do not have programming experience in C++ already. This is not a ground up tutorial on how to program in C++, and it is not a fast read. What this book is, however, is probably the best reference book on C++ in existance.

Available via: [http://www.amazon.com/exec/obidos/ASIN/0201700735/ Amazon]

===Other Books===

'''[http://doc.trolltech.com/guibooks.html Books on GUI design]'''

Trolltech's recommendations of books about GUI design.

===Historic===
'''[http://developer.kde.org/documentation/books/kde-2.0-development/index.html KDE 2.0 Development]'''

A 540 page book available online and in print. Covers KParts, DCOP, aRts, KDevelop, licensing, introductory programming, and other topics. The [http://kde20development.andamooka.org support site] has the full text in various formats along with community annotation and discussion of KDE development. This book is as close to an Official Book by the KDE Project as possible. All authors and technical editors are KDE developers.

== IRC Channels ==
In general, IRC channels mentioned here are available on FreeNode. Connect to irc.kde.org, and check these channels out for further information.

*KDE User Channel - [irc://irc.kde.org:6667/kde #kde]
*KDE Development - [irc://irc.kde.org:6667/kde-devel #kde-devel]
*Phonon - [irc://irc.kde.org:6667/phonon #phonon]
*Decibel - [irc://irc.kde.org:6667/decibel #decibel]
*Solid - [irc://irc.kde.org:6667/solid #solid]
*Plasma - [irc://irc.kde.org:6667/plasma #plasma]
*KDE EDU - [irc://irc.kde.org:6667/kdeedu #kdeedu]
*KDE Games - [irc://irc.kde.org:6667/kdegames #kdegames]
*KDE PIM - [irc://irc.kde.org:6667/kontact #kontact]
*KDevelop IDE - [irc://irc.kde.org:6667/kdevelop #kdevelop]
*Amarok - [irc://irc.kde.org:6667/kdevelop #amarok]

== Newsgroups ==
== Forums ==
== Events ==
== Courses and Certifications ==
== Audio and Video Casts ==
== Source Code Repositories ==

Schedules/Is KDE 4.1 for you?

2008-07-07T09:50:08Z

Steveire: Applets can now be dragged on the panel

KDE 4.1 is scheduled for release at the end of July 2008. This is a significant milestone for the KDE 4 series and for KDE in general, but as an early
release in the KDE 4 cycle, it does have some known issues which will not be fixed in KDE 4.1. Huge progress has been made in KDE 4.1 which is listed in the [[Schedules/KDE4/4.1_Feature_Plan|KDE 4.1 Feature Plan]].

Some of the more obvious issues are listed below. If these issues are important to you, you should stay with KDE 3.5 or KDE 4.0 until KDE 4.2 when most of these issues are scheduled to be resolved.

It is possible that distributions will work around some of these issues before distributing to users. KDE 4.2 is currently scheduled for release
in February 2009.

== The Desktop ==

The desktop in KDE 4.1 will mark the start of some significant user interface changes. This is a step away from the way the KDE 3 desktop was
designed, but everything possible on your KDE 3.5.9 desktop will also be possible on your KDE 4 desktop. For KDE 4.1, however, some features
are not yet complete, but should be ready for KDE 4.2.

=== FolderView ===

{{Box|Under Construction|2=[[Image:Action_configure.svg|noframe|left|40px]]
'''This page is under construction'''. This section could really do with some screenshots on the page. You can help by [{{fullurl:{{PAGENAME}}|action=edit}} editing this page].
<div class="clear"></div> }}

FolderView is a new technology on the KDE 4 desktop which allows more than one collection of icons on your "desktop" and discourages making it the
dumping ground for miscellaneous files (though that is also possible, like in KDE 3). See [http://blog.lydiapintscher.de/2008/06/14/folderview-is-the-awesome/ this blog entry by Lydia Pintscher] for some infomation on FolderView.

The following issues are known are scheduled to be resolved in KDE 4.2 next February:
* Icons do not need to be in a grid. You can drag them to any point within the FolderView. However, the location you leave them in is not saved, so they will be a grid again the next time you start the desktop.
* You can have a full screen "desktop with icons", but if you do, you can not have a desktop background. See also: http://www.youtube.com/watch?v=RhYinDOKbE8
* You can have a desktop background, but then you must use the FolderView in regular, not entire screen mode (as shown in Lydia's blog above).

=== Panels and workspaces ===

* Autohiding of panels is not yet configurable.
* It is not possible to set different desktop wallpapers for different virtual desktops.
* The Mac-style menu bar is not available.




== Applications ==

=== New and missing applications ===
Some KDE 3 applications have not yet been ported to KDE 4. Most distributions still package KDE 3 versions of these applications with their KDE 4 desktops. Some notable applications which will not be included in KDE 4.1 are listed below:

* KOffice has a different release schedule than KDE 4. KOffice 2.0 will likely be released late in 2008.
* Amarok has a different release schedule than KDE 4. The Amarok team is currently aiming for a first release in September 2008 for the 2.0 series.
* Konversation has a different release schedule than KDE 4. Konversation 2.0 does not yet have a release schedule.