Sponsored Links

Why Open Bug Tracking Fails

Unlike proprietary platforms, Ubuntu allows end users to interact directly with developers through Launchpad’s bug-reporting system. In some cases, this approach allows bugs to be discovered and resolved quickly. In most situations, however, open bug tracking is a fiasco that Ubuntu would be better off without. Here’s why.

Open bug reporting policies, which allow anyone to file bug reports that developers are expected to address, operate under the principle, famously decreed by Eric S. Raymond, that “Given enough eyeballs, all bugs are shallow.” In other words, the more people you have searching for and reporting problems, the faster they can be fixed.

In the best of all possible worlds, where end users are also professional programmers, Raymond’s logic may hold true. But in real life, only a fraction of the people using a given software product have any idea how to read code or troubleshoot problems.

Read more at WorksWithU

2 comments to Why Open Bug Tracking Fails

  • Timothy

    Ubuntu does not have good arangement of tools which suit the various levels of skill in the community.

    Not all bug reporters are equal. Bug reporting tools which don’t cater to the skilled as well as the unskilled report will disenchant the hightly skilled.

    One key element missing from ubuntu bug track system is associating the package version THROUGHT the but reporting process. This is required for bug regression monitoring and safe deployment.

    We have bug reporting tools, which don’t allow for the easy addtion of bug reporter comments and don’t help the bug reporter to perform a quick look up of possibly related bugs.

    In these two aspects debian bts is var superior to ubuntu’s.

    We also need bug capturing tools. A good way to illustrate a bug is to capture the previous version of the package without the bug. And again capture the buggy version of the package with the bug.

  • Timothy

    typo fixes

    package tracking version throughout the bug reporting process