lkml.org 
[lkml]   [2007]   [Apr]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    Subjectirks with bugzilla (was Re: Linux 2.6.21)
    Russell King wrote:
    > On Sat, Apr 28, 2007 at 09:53:20PM +0200, Adrian Bunk wrote:
    >> We are already quite good at ignoring bug reports that come through
    >> linux-kernel, and it's an _advantage_ of the kernel Bugzilla to see more
    >> than 1600 open bugs because this tells how bad we are at handling bugs.
    >> How many thousand bug reports have been ignored during the same time on
    >> linux-kernel?
    >
    > However, look at this bug:
    >
    > http://bugme.osdl.org/show_bug.cgi?id=7760
    >
    > It's outside my knowledge to be able to fix for various reasons:
    [...]

    http://bugzilla.kernel.org/faq.cgi says, although it doesn't make a lot
    of sense:

    "Q. If a bug has an owner does that mean they are working on it?

    A. No. If it is not in the ASSIGNED state then no one is working
    on it. The owner defaults to the subsytem maintainer. However,
    anyone who wants to submit a patch or add more info to a bug can
    do so. If the bug is reassigned to someone then the owner field
    will reflect that change."

    So the "owner" field is bogus per default. It would be better if the
    bugzilla admins used only meta-addresses instead of a person's address
    for any automatically filled-in "owner" field, unless a person
    specifically wants to assume this automatic owner role.

    I for example am not automatic owner of IEEE 1394 bugs;
    drivers_ieee1394@kernel-bugs.osdl.org is. And I am watching this pseudo
    owner.

    So in fact, the "owner" field should be replaced by
    - a mail exploder for each component which can be watched by
    interested people,
    - an "assignee" field which is filled in when a bug is assigned to a
    person.

    Now that I am at it, another quote from http://bugzilla.kernel.org/faq.cgi :

    "Q. What does a subsystem maintainer do?

    A. He or She will track new bugs and assign them to people or
    reject it for various reasons. They periodically check to make
    sure things are getting worked on and review fixes to make sure
    they are well written."

    A maintainer in the project called linux kernel will almost never assign
    bugs to people (besides to himself). He could if he employed or
    otherwise supervised people to assign bugs to.

    This especially applies to so-called "subsystem maintainers in kernel
    tracker", which are not what many people think "subsystem maintainers" are:

    "Q. Why are the subsystem maintainers in kernel tracker
    sometimes different than the person listed in the MAINTAINER
    file?

    A. The subsystem maintainers in kernel tracker are volunteers to
    help track bugs in an area they are interested in. Sometimes
    they are the same person as on kernel.org sometimes they are
    not. There are still some categories with no maintainers so more
    volunteers are needed."

    Another quibble: This FAQ I'm quoting can be reached from the cover
    page of bugzilla.kernel.org, i.e. from http://bugzilla.kernel.org/.
    However, none of the other web pages of this site link to
    http://bugzilla.kernel.org/. Same for the bugme-admin contact.

    Because I find bugzilla.kernel.org quite useful for myself, I filed
    these complaints of mine under
    http://bugzilla.kernel.org/show_bug.cgi?id=8396
    http://bugzilla.kernel.org/show_bug.cgi?id=8397
    http://bugzilla.kernel.org/show_bug.cgi?id=8394
    in hope that they are taken into consideration by those who maintain the
    site.
    --
    Stefan Richter
    -=====-=-=== -=-- ===--
    http://arcgraph.de/sr/
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-04-28 23:47    [W:4.724 / U:0.700 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site