• Subscribe

    Subscribe to This Week In Panospace by eMail.
    Subscribe in a reader
  • License

    Creative Commons License
    This work is © 2008-2012
    by Yuval Levy
    and licensed under a
    Creative Commons License.
  • Entries

    August 2008
    M T W T F S S
    « Jul   Sep »
     123
    45678910
    11121314151617
    18192021222324
    25262728293031
  • Archives

Anonymous Bug Reports Suck


Hugin is becoming more popular by the day. With an average of more than 150 downloads per day and an estimated install base of more than 15.000 for my latest Windows installer alone.

With popularity comes mass, and we need critical mass. It is in the mass that we’ll find the next generation of tester, builders, coder. That’s what Open Source is about.

Many new users have become active and when they find the inevitable bugs, they give feedback. Good. Most of them post the bug reports to the bug tracker. Very good. Often these bugs are specific to the use case and can not be identified without user help.

But we need user’s help beyond simply stating “hey, there’s a bug!”. We need some basic information pertaining the environment in which hugin is used, and also which version of hugin and helper applications. Everything evolves so fast. And sometimes we need specific information, such as the camera make and model, the pre-process through which the images have gone, the project files, etc. Without this information, the developers can’t really do much about the bug report, because the often don’t have enough indication where to look at. And when they need more information, they need to contact the bug reporter.

Unfortunately some bug reporters omit the critically important step to register with Sourceforge and post their bug reports anonymously. 26 such bug reports in Hugin’s bug tracker are anonymous. How can the developers contact them to get more information about the bug?

Please, do the things right – register with Sourceforge – it is free and in ten years I have not had a single instance of spam. Or at least, write in the bug report how we can contact you. Thanks.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s