[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070429221502.GA714@one.firstfloor.org>
Date: Mon, 30 Apr 2007 00:15:02 +0200
From: Andi Kleen <andi@...stfloor.org>
To: David Miller <davem@...emloft.net>
Cc: andi@...stfloor.org, torvalds@...ux-foundation.org, bunk@...sta.de,
diegocg@...il.com, cebbert@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: Linux 2.6.21
> BECAUSE EMAIL ENGAGES PEOPLE AND BUGZILLA DOES NOT!
>
> Nobody looks at the bugzilla because there is too much junk in there
> to make the signal any useful to search for, there's simply too much
> noise.
That means just x.org doesn't have a working bugmaster setup.
Again a technical solution doesn't fix misorganization or missing people;
it just pushes some work humans are at to computers if you have the right structure
The normal bugzilla workflow is that some people categorize the bugs,
ask the necessary questions and then figure out which developer
to assign it to. Then the developer doesn't end up with "too much noise"
but just a limited set of bugs to look at.
And the responsible developer then gets an email and looks at the bug.
This already happens to some limited fashion in kernel.org bugzilla:
I get bugs assigned occasionally and while it's slow I tend to look
at (near) all of them and try to improve things there.
If a single developer ends up with too many bugs this way or there
is nobody to assign a bug to or nobody processes the incoming bugs
then the project has a problem. Yes bugzilla doesn't work then
if the project is not well organized.
But that's in no way different from what would happen with your
email sent to a mailing list if it had the same problem.
-Andi (who finds it a bit bizarre he has to explain the concept
of "things can get easier when some work is pushed to computers"
concept to a hacker)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists