John Bailey from the Pidgin team decided to post some raw numbers of their bug tracker in which is clear their MSN component is lacking some love. He even goes further into excusing their neglect: “Our time is a precious resource, and in many cases we simply have better things to do”. His post ends up accepting that they need help; IOW MSN is currently under-maintained.
However I think the situation is even worst than that; not only MSN has more bugs open than other protocols; the ones that have been closed haven’t actually been fixed. I took some time to generate some hard numbers and the results are undeniable.
Here’s a graph showing the status of all the bugs:
Notice the huge amount of bugs that have been automatically closed. This means it’s not clear what happened to the bug. One possibility is that the bugs are still present.
The only bugs that we actually know have been fixed are: ‘fixed’ and ‘out of date’. The ones we know are not fixed are: ‘cantfix’, ‘wontfix’, and ‘worksforme’. I will also include ‘autoclose’ because although we don’t know if the bug is still present, we know it wasn’t verified as fixed. ‘duplicate’ and ‘invalid’ should stay out of the picture because for all purposes they are not valid.
If we take this into consideration then 24% were fixed, and 25% not fixed, so there you go; there are more bugs closed as not fixed than fixed.
Why aren’t the Pidgin developers worried about this? Well, most probably they are not even aware of these numbers because their tracker doesn’t provide them. I had to manually download the web page of each one of the MSN bugs, and then parse the changes for resolution, and if the bug was automatically closed or not (automatically closed bugs are not marked in any way).
Add the bug tracker to another component of Pidgin that needs some work.
Here’s the graph for msn-pecan:
update: I decided to add a new “Incomplete” state in order to differentiate the bugs closed due to lack of feedback
In this case 52% of the bugs have actually been fixed, 15% are still open, so regardless of how we consider the remaining 22% (disregarding duplicates), the vast majority of bugs are fixed.
Now, unlike Pidgin, we don’t automatically close bugs after 14 days. Depending on the priority it might make sense to keep reminding the reporter(s) that further information is needed. If it’s clear the bug is not going to go forward then it’s manually marked as Incomplete, but it’s clearly distinguishable for other invalid bugs.
Also, unlike Pidgin, our bug tracker is crystal clear about the status of the bugs, priority, popularity, and target milestone; just take a look.
You should ask yourself this question; Where do I have better chances of getting my bug fixed? I hope this post has made it clear: msn-pecan by a large margin.
If the Pidgin team has problems maintaining MSN, why don’t they help themselves and start using msn-pecan?
Note: Also, unlike John Bailey’s, my blog is happy to receive comments 🙂