If this suite’s a success, why is it so buggy?

Thursday, December 8th, 2005

Of OpenOffice, Andrew Brown asks, If this suite’s a success, why is it so buggy?:

Of all the myths that have grown up around open source software, perhaps the most pervasive is Eric Raymond’s aphorism that ‘Many eyes make bugs shallow’, suggesting that if lots of people can view a program’s source code, they will find and fix its errors more quickly than commercial products whose code is jealously guarded. The only problem with this is that it’s not true — certainly not in one of the flagship projects of open source, OpenOffice.

[...]

The myth of open source rests on two improbable assumptions. The first is that a significant proportion of users can fix bugs. That is true at the Massachusetts Institute of Technology, where the concept of open source was first formalised in the 1980s by Richard Stallman and others, and it is true in some of the geekier corners of the internet. But on programs intended for use by the non-programming public, it’s a very different story.

This is important because of the second crucial false assumption: that even if not all users can fix a bug, they can help find them. They can’t. Most users just think: “The computer isn’t doing what I want.”

[...]

More than 50,000 bugs have been reported. And how many have been fixed by open source’s uniquely efficient processes? According to the (public) bugs database, at last count, there were more than 6,000 unfixed bugs, and more than 5,000 feature requests. While the number of bugs discovered seems to rise with the number of users, the number of fixes doesn’t, and the number of fixers certainly doesn’t. Only about 500 people have signed the legalese that would enable them to submit code to the project; since you need to do this even to make changes to the website, that will translate to far fewer than 500 volunteers submitting real code. A reasonable guess would be 50, or even five.

Leave a Reply