Basically look through REPORTING-BUGS for a laundry list of helpful info.
> The other main thing was to define some sort of structure to the
> bug report and try and get the use to categorize if they could.
> In an ideal world, we would use the maintainers file and the
> stack traceback to cc the bug to the maintainer. I think we want
> to explore this a bit. I'm not sure that the maintainer file is
> the way to go, what if we divided it up into much broader chunks
> like "fs", "vm", "network drivers", and had a mail forwarder
> for each area. That could fan out to the maintainers.
One thing people have talked about in the past is updating MAINTAINERS
to actually reflect real life... some of the active maintainers
don't have maintainer entries. That may be intentional, maybe not...
For drivers at least, bugs -should- be mailed to the driver
maintainer where possible, which is not always the same as the
> Jens wants there to be a queue of
> new bugs and a mechanism where people can come in the morning, pull
> a pile of bugs off of the queue, sort them, sending some to the real
> database. This idea has a lot of merit, it needs some pondering as
> DaveM would say, to get to the point that we have a workable mechanism
> which works in a distributed fashion.
Back when I was hacking GNOME, various janitors (to use the now-popular
term) would go through and clean the bug database, sorting through a lot
of the noise.
Newbies are finding the Kernel Janitors project as an excellent way to
begin to contribute to the kernel. There are definitely interested,
smart people willing to help, that at present don't know a lot about the
kernel. Such volunteers, like the GNOMEs mentioned above, could be a
vast benefit to this particular step of the bug tracking process. You
> Past experiences
> This is a catch all for sound bytes that we don't want to forget...
> - one key observation: let bugs "expire" much like news expires. If
> nobody has been whining enough that it gets into the high signal
> bug db then it probably isn't real. We really want a way where no
> activity means let it expire.
Agreed, with a caveat: some bugs should stay around but not expire.
There is a class of bugs that shouldn't go away from the "less noise"
bug database when there is no activity. ie. hard problems we want to
remember, but solve in a later version.
1) An e-mail interface.
For sorting through massive amounts of bugs, NNTP is far more useful.
Maybe as a query interface as well, NNTP is useful. But for getting
into the nitty-gritty details of handling a bug, e-mail is generally the
primary medium of communication between developer and user.
debian-bugs assigns each bug a unique e-mail address, and all e-mail
that arrives in that mailbox is appended to the bug's comments.
2) Support for binary attachments from users
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/