Bug report

Jacques B. jjrboucher at gmail.com
Fri Oct 26 13:13:50 UTC 2007

On 10/25/07, Karl Larsen <k5di at zianet.com> wrote:
>     I said that a bug report would be sent regarding the new F7 moving
> partition designators. This is it:
> https://bugzilla.redhat.com/show_bug.cgi?id=352181
>         Karl F. Larsen, AKA K5DI

As predicted it has already been closed and marked as "Not a bug".
The lesson here Karl is that:
1 - Just because software doesn't do what you want it to do or expect
it to do doesn't automatically make it a bug.  If the software is
doing what it was designed to do then it is not a bug.  Thus your
"bug" is rather a "feature request" or feedback on user experience.
But not a bug
2 - If you are going to file a bug report (providing #1 does not
apply) you have to provide sufficient details if you want any action
taken.  The amount of effort you put into filing the bug report will
likely be reflected in the amount of effort they put into assessing if
it is a bug or not.

More times than not when someone points out a problem with something
you've posted you become defensive.  Instead you should be
appreciative that so many people are taking the time to read what
you've posted and are providing input based on their knowledge and
experience.  Even if in the end you don't agree with them or their
advice has a flaw in it (which if the case someone else will usually
pick up on that and post a follow-up identifying that error).  This
bug report is but the latest example.  Several of us pointed out that
it was not a bug, and that when reporting one you need to provide more
details and classify it a bit better.  As was pointed out you stood in
your hole and dug it deeper instead of learning from what others
shared with you and react accordingly.

At the end of the day none of this has any real impact on me and the
others on the list.  If we don't like a particular person's postings
we can simply ignore them as some choose to do.  But in the spirit of
fostering a better online community and recognizing that everybody has
some knowledge and experience to bring to the table many of us don't
easily resort to  censoring a user from our INBOX.  So at the end of
the day the only person who is truly impacted is the individual in
question because it is their support group within the online community
that diminishes.

It's pretty easy.  Don't be afraid to admit to a mistake. Don't be
afraid to apologize if warranted.  And don't be afraid to say "I don't

Jacques B.

More information about the users mailing list