Sorry! I cannot tell you when KDE 4.4 will be uploaded to unstable. I am not working on that. My initial plan was writing about other tasks I am planning to work on and asking for your help. But I realized people would be more interested in knowing about KDE 4.4 packages. Once you know about this, I might trick you into helping in others areas ;)

Debian packages for KDE 4.4 are being worked on, just slowly and of course, keeping on with the quality you are used to. There will be also some changes that have been in some people's TODO for long time.

The goal is having them in very good shape for Squeeze, that will ship with some point release of 4.4. The doubt is which point release will be: 4.4.2? 4.4.3 ? The schedule for the point releases has not been made yet, so it makes a bit harder trying to predict it. In the same lines, I can not tell you when Squeeze will be released neither, it needs to be frozen first!

If you want to know about the reasons of this delay, it is simple math: KDE has been growing a lot of more than the number of people working in Debian packages of KDE. I am not talking about size in lines of code in KDE, it is more the number of new dependencies that the KDE team have to take care now too: soprano, libutempter, ... Have you wondered why some are under the name of Debian Krap maintainers? :) And there are releases much more often than in the KDE 3 times. You might have notice not only 4.3.5 have been skipped, it also was the case with 4.2.3 or 4.1.4.

This is not good or bad, it is just the same number of maintainers (or less) with more work. And what is worse... with more bugs open in the Debian BTS! I think reiterated calls for not to file upstream bugs in the Debian BTS and directly in KDE bugzilla (see my blog post about this here) have helped but still we have a large amount of bugs piled through the years. This graph could give you an estimate how we tried in the past fighting against without too much success:

Olivier Vitrat, we miss you :)

One of the most heavy (and boring) talks that needs to be done for the KDE 4.4 packages is the copyright checking. I am not sure a total newbie can help with this, but if you have knowledge about licenses and you want to try helping, we are waiting for you.

About other areas of the packaging maintenance, if you are interested in start learning and helping with future releases, you are welcome to start lurking in the #debian-qt-kde channel in OFTC and in the mailing lists.

Update February 21th: 4.4.0 is for sure not being uploaded into the archive. Probably KDE SC 4.4.1 to be released 2nd March will be uploaded to unstable or experimental.

The news is out (link in Spanish). We will have this year the third edition of the DudesConf a.k.a. the Spanish DebConf.

Special thanks to GPUL for hosting us another year!

Imagine you have found a bug in your Debian running KDE, a nasty one, and you want to get it resolved. What you should do?

This is centered on KDE and Debian but most of it is useful in general.

First Case: You have a problem and you have no idea whether it is a bug or not. Even worse, you don't know which package to report it to.

This happens more often than you might believe; it even happens to experienced people. Your first step should be to checking user forums and mailing lists [0] to see if someone else has encountered the same issue. You might find that your problem is already known (and maybe easy to solve).

In the case that you do not find your problem there, then you can ask for help and post a mail or message explaining your problem. Pick one mailing list or forum board, the one you think is more appropriate, then post your issue there. The most detailed you are about your problem, the bigger is the likelihood of you obtaining help.

It could happen that:

• you are told how to solve your problem. yay \o/
• your problem is not a real bug in Debian/KDE and you learn why.
• your problem is not solved, but you are at least pointed to the software that is causing it.
• you do not get any answer.

If you do not get any answer it might be that nobody got into the same problem and they do not how to help you. But it is also possible you were not clear about your problem. Also, you need to be patient; it is unlikely someone will answer your question 2 minutes after you posted it.

If you find out more about your problem, it is a good idea to send another email or post updating your first message. If after 5-7 days you do not get any answer, you can try asking for help in another forum or mailing list.

If you are given pointers to what software is causing the problem you can go to the second case.

[0]
Mailing lists:

• Debian: See overview of users' mailing list at: http://lists.debian.org/users.html
  There are currently mailing lists in 22 languages.
  There is a users' mailing list dedicated to KDE: http://lists.debian.org/debian-kde/
• KDE: See the general user lists: http://www.kde.org/mailinglists/

Forums:

• Debian: http://forums.debian.net/
• KDE: http://forum.kde.org/

Second case: You know where the problem is. Where you should report your bug?

First, you should check in both the Debian and the KDE bug tracking systems [1] to see if the bug is already reported. If that is the case, and you are able to give more information about it, update the bug report.

If the bug is not reported, then report it in the KDE bug tracking system if you think it is a problem in the application or in the Debian BTS if it is a packaging problem. If you're not sure what kind of bug it is, you can go to the first case (in the beginning of this post) and ask in the users forums and mailing lists [0].

However, you won't always get it right, and in some cases you will be pointed to the other bug tracking system. Do not take it personally; KDE developers can not help you with packaging problems and Debian packagers can't always help you with the application bugs.

It might be that your problem is solved in the development version, so if possible check what is going on in the development version before report.

When reporting the problem, give all the details you can about your problem. If you can detail the steps to reproduce the bug, even better. Also, if you are asked for more information, reply the best you can. Somebody is trying to help you. Be nice !:)

Also, remember to be patient when reporting bugs or being asked for more information: both KDE and Debian are big projects with a lot of traffic on their respective bug reporting systems (esp. KDE), so sometimes there is not a quick reply from the developers.

[1]

• Debian: http://bugs.debian.org/<softwarename>
• KDE: https://bugs.kde.org/ and use the search box.

In Debian, a lot of people report upstream issues in the bug tracking system and they think it is good and what they have to do. The truth is that in a very few cases, such as security bugs or data loss bugs, this is a good idea. But most of the time it is not useful to report problems to the people who can not solve them. Do not expect Debian/KDE maintainers to forward your problem upstream (a problem which they may well not be able to reproduce), then back to you when upstream ask for more information, then back with the information to upstream... it is time consuming and we have big (wo)manpower problems.

In any case, if you think the bug is very important and should be in the Debian BTS, you can report it in Debian as well as reporting it to KDE. Make sure you mention the KDE bug in the Debian bug.

Third case: your problem is not a bug, just a feature request.

Until now, I have talked about bugs, when you find something that is clearly not working right in your system. But what about when you want to ask for a new feature in a piece of software?

In very few cases this belongs in a Debian wish list. Most feature requests apply upstream and you should tell the about your idea. If you do not tell them, it is unlikely they will implement it. Still, after reporting, you should accept it if upstream thinks it is not a good idea or it is not interested enough to implement it.

Post updated on the 30th September, thanks to Rupert Swarbrick for grammar fixes.