In this week's KDE Commit-Digest:
- Okular now supports searching for words with ligatures
- Work on new NetworkManager 0.9 branch in NetworkManagement and PEAP-GTC wireless authentication suppport
- A new plugin which provides a rating and an annotation menu action for files and folders (Dolphin/Konqueror) from Nepomuk
- A new dataengine in Plasma that returns Activities thumbnails
- Support for newer Linux kernels and extended support for terabytes and petabytes in KSysGuard along with many bugfixes
- New multithreaded puzzle class put to work in Palapeli, removing the first-run assistant and adding puzzle list sorting
- Proof-of-concept implementation of games as plugins for Tagaro
- Automatic updating of comics added to the Comic Strip plasmoid
- Fixes for S/FTP connections in Dolphin and other applications using the FTP KIO Slave
- Work on improved table layout in Calligra, improved DOC support, and many bugfixes
- Bugfixing in Amarok including fixes for IPod Classic detection
- Bugfixing throughout Rekonq in preparation for the next release
- Bugfixing in KDevelop, Digikam, Kst, and KTorrent.
This week's champion is Camila Boemann for fixing bug 127571 which is more than 6 years old!
Camila is a newbie wrt Dawit: he fixed bug #34578 dating back to KDE 2.2, gcc 2.95, Linux 2.4 times, which is nearly 10 years old!
I think it's pretty sad that bugs are allowed to live that long. 6 years to fix a bug?
It's pretty annoying actually, even more so when bugs are reported that aren't even acknowledged - like this one of mine:
do you propose to disallow bugs living on for this long?
Make sure to provide a detailed, feasible plan within the next ten days that includes an implementation timeline with detailed fallbacks in case your implementation does not reach its milestones.
Just delete all bugs that are older than 365 days. This way there won't be any bugs that are older than one year ;-)
Or, instead of sarcasm, how about having 4.6.4 or 4.6.5 "bug killed" versions where bugs older than 365 days are either fixed, or marked "Can't Fix / By Design" or similar?
My other point was that I filed an accurate, reproducible bug with a screenshot and it hasn't even been assigned to anyone.
You could start learning how a volunteer-driven open source project like KDE actually works. You complain that your bug hasn't been assigned to anyone. Big surprise for you, perhaps, but there isn't anyone who can assign your bug to someone else. There are no managers. Generally, developers pick the bugs they want to work on themselves. And there might be nobody who can fix your bug, and even nobody who can try to reproduce and change the status from unconfirmed to new.
Sure, we could handle bug reports better. But the sad fact is that the libraries have a very low number of developers working on it and it's impossible for them to triage all bug reports and do some useful work, like fixing issues or implementing new features. So now it's up to you again: try and help out, for instance by triaging bugs as they come in, or even helping to fix them.
Interested in adding this as a part of the regular Commit-Digest? Apply here: http://enzyme.commit-digest.org/
You can find the source code at the Enzyme homepage: http://enzyme-project.org/
If you really mean https://bugs.kde.org/show_bug.cgi?id=127571 (new feature: split the image), that wasn't Camila, but Srikanth Tiyyagura, a new Krita hacker from Andra Pradesh!