Please have a look at http://bugs.kde.org/expired.cgi - I would like to give the listed wishlists a WONTFIX automatically after having the link online on dot.kde.org for a while. What do you think?

The current limits are ID < 64000 (roughly 15 months old) and less than 60 votes (remember at 80 they become auto-confirmed for most products).

If you a developer feels like reviewing and thinks some wishes make sense (for more than one user), he can confirm them and they will be removed from the list.

I tell you now that I will do this not earlier than start of december.

Adding a product black list is no problem. I just need to know.

if we don't use the bug database, it doesn't matter what happens; if we do use the bug database, then we can clean these old items up by marking the appropriate ones as New and leave the rest behind.

Follow the masses into the braindamage that's called RFC1738

I saw some commits regarding this, so I'm just asking for confirmation and reasoning. Is it desired from now on to see things like file:///home/andris/Desktop in Konqueror's location bar when browsing local directories or similar strings in Kate, etc. for files (file:///somedirectory/foo.txt)? I can understand that this is more correct, but I think many users will complain and this change might break some applications that check if an url starts with "file:" and remove that string from the url.

If this the new desired behavior, what is the exact reasoning behind it, taking in account that file:/somedir was enough until now? A link to some bug report or other document is enough.

Here you go:
http://freedesktop.org/Standards/file-uri-spec

In particular: "Some current apps generate URIs of the form "file:/". These are not correct according to RFC1738, so they should not be generated."

See also the thread starting here: http://freedesktop.org/pipermail/xdg/2004-November/005327.html

I agree that 'file:///' looks silly and has no meaning, but we still agreed to follow a standard that says that it should look like that. The only sane way to change it is to work on getting the standard changed.

digiKam is a digital photo management application for KDE, which makes importing and organizing digital photos a "snap". The photos can be organized in albums which can be sorted chronologically, by directory layout or by custom collections. An easy to use interface is provided that enables you to connect to your camera and preview, download and/or delete your images.

The tarballs can be downloaded from
http://sourceforge.net/projects/digikamKey New features

• Reliable and fast database (sqlite) backend for saving metadata
• Tagging support for photos.
• Tags are grouped together as virtual folders shown similar to albums.
• Extensive drag and drop support for tagging and moving/copying photos
• Enhanced camera interface with support for automatic photo rotation and renaming of photos while downloading.
• EXIF support with optional oriented display of thumbnails and photos using camera provided information
• Customizable thumbnails for albums and tags
• Support for nested albums
• Tooltips providing detailed photo information
• Themeing support for digiKam
• KIPI support for enhanced plugin support. KIPI is an initiative between various KDE image management applications to provide a common architecture for implementing image based plugins. Currently implemented plugins and other details can be found at: http://extragear.kde.org/apps/kipi.php
• New fast image viewer and editor which uses its own plugin architecture to provide various additional functionalities in addition to the usual gamma/contrast/brightness adjustments, rotation, resize functions. Some of the plugins supplied with digiKam are:
  • Histogram Viewer
  • Red Eye correction
  • Black & White and Sepia conversion
  • Blurring and sharpening
  • RGB color correction
  • Hue/Saturation/Lightness correction
  • Normalize and Equalize
  Highly improved thumbnail loading speed.
• Lots more... visit this link to see a more detailed list of changes http://digikam.sourceforge.net/Digikam-SPIP/rubrique.php3?id_rubrique=12