How much does KDE care for its bugs?

Good question. Let’s reveal some stats.

All time top commenters
Name Number of Posts
Dario Andres 34082
Myriam Schweingruber 23019
Christoph Feck 16342
Gilles Caulier 14737
David Faure 13684
FiNeX 12637
Stephan Kulow 12174
Aaron J. Seigo 11648
Christophe Giboudeaux 11289
Thiago Macieira 10167

Impressive activity there, i would say. But one more, the activity for only this year:

Top Commenters 2013
Name Number of Posts
Jekyll Wu 1062
Thomas Lübking 684
Christoph Feck 654
Myriam Schweingruber 503
Martin Gräßlin 495
Alex Fiestas 443
Frank Reininghaus 309
Laurent Montel 234
David Edmundson 227
Gilles Caulier 225

It is up to you to decide on a conclusion. But to me, this seems like someone really does care.

7 thoughts on “How much does KDE care for its bugs?”

  1. I don’t understand what “number of posts” mean. Seeing the huge numbers, I’m pretty sure it’s not “posts on planet KDE”.

    And, anyway, I don’t see the point of throwing numbers without any context. Absolute numbers are meaningless, ratio are interesting. I mean, we probably would get very impressive numbers by counting the # of bugs in bugs.kde.org, the # of open bugs untouched for >12 months, the # of bugs “confirmed” untouched for >12 months, and so on.

    The only thing that huge numbers show is that KDE is a big project. Everybody agreees on that.

    1. Number of posts = comments, be it intial ones or followups on bugs.kde.org = activity

      And this is not meant to be compulsory stats table, it shows shows what is stated, the top 10 of the most posts all time and this year.

      If you want to have more in depth non fun statistics, you can easily grab them yourself on the bugtracker, e.g. https://bugs.kde.org/weekly-bug-summary.cgi

      Such things were also already posted a lot on planetkde, so i see no need to repeat something like that. This one was never shown though.

  2. What really surprises how KDE finesse to break things that worked for years.
    And what it happens for… Tabbed windows, KDED & power etc etc…

    There are really exhaustive demands on error reporting at bugs.kde same time inet is full of recreating scenarios 🙁

    Its really sad to see how KDE goes bloatware 🙁

  3. In my opinions these raw numbers don’t say much. What matters is the _content_ of the comments, and how bugs are fixed. With 4.10 there have been some rather crucial bugs (crashes, non-working kio-slaves, …) and a few of them are, despite having plenty of duplicate reports and votes and being confirmed, still present in 4.10.1. Also there are quite a few bugs with plenty of comments, but them being “no, I don’t see this as a bug” (see the skype one in kmail) or “no, this is how it is, this won’t be fixed” (battery plasmoid), and I don’t really know if they should be, from a user point of view, counted as a good thing.

    Other bugs, such as the demanding attention taskbar entries, are present since a few releases.

    Don’t get me wrong, there are a few people who care a lot about bugs and getting them triaged and fixed, but just using raw numbers such as comments are, especially given the recent discussions due to the plasma-desktop crash, not really a good indication on how things are in bugland.

  4. Usually I would agree with the previous commentators and ask for “context.” But I think in this case it’s quite fine without context. Ingo Malchow posted the numbers with the suggestion that many thousands of comments or several hundred comments in one year on bugs.kde.org is an indication of the degree to which a developer cares. Surely, having less made comments does not mean someone cares less (someone might simply fix, but not comment much), but: given the time these developers spend reading bug reports, thinking about them and commenting on them; often also writing code to fix the bugs means that they DO care. Even if a developer thinks a certain feature does not need to be added or a certain behavior should not be changed: spending a significant part of your life reading and commenting (and often fixing) bug reports should be honored by the community of users, no matter one’s position on how one silly plasmoid should behave. If I were a developer and spent hundreds of hours on bugs.kde.org related stuff, I would surely NOT like to hear users suggesting that I don’t care, because they have been bitten by one certain bug or because they want to battery monitor to fly and glitter.

    So, here is my part: THANK YOU, DEVELOPERS, FOR YOUR TIME AND FOR CARING. THE SILENT MAJORITY IS THANKFUL. PLEASE DISREGARD THE FEW WHO CANNOT DISTINGUISH BETWEEN THEM SEEING A BUG AND ALL THE OTHERS HAVING A WORKING DE.

  5. Numbers do look good, it is heartening to know that developers are posting a lot . I can infer a great deal of postive things like devs are actually looking into bugs, reviewing them , marking them as dusplicates, commenting to elicit information (logs, etc), suggesitng workarounds, maybe including small patches, etc.

    On a lighter note, Mark Twain propagated that “There are 3 kind of lies, Lies , Damned Lies and Statisctics”. 😉

    1. I worked in marketing research a long time, and another saying there was “don’t trust any statistics you didn’t fake yourself”. 😀
      However, in this case it is done with some simple mysql queries and copy n paste. And there is no need to fake this.

Comments are closed.