I think the issue of triage deserves a more clear explanation of just how huge a task this really is.
A team with members who are well familiar with each architecture and having access to the actual models/devices showing the problem. Even a "fix" might break other models within the same architecture! So, access to a ton of hardware is a must have. Knowing who is working in the area needed and if they actually want to work on the bug at all. Look at the hackathon reports: "I had planned on working on issue X, but I found myself working instead on issue Y with so and so". Why not? Who doesn't want to enjoy themself? They need to have members who know enough OpenBSD internals to at least be able to make reasonable guesses about where the problem is probably at, else how can they figure out who might be able to work on it. OK, this is starting to sound like forming a team of developers. Dedicated enough to really keep at it. This is starting to sound like a team getting paid money to really keep at it! Do you really want to spend 4 hours every night after going to work and coming home tired to do rather difficult work? So, at the very least, a mountain of hardware, expertise and probably money too. I think Theo's comment about hitting 'd' on many bug reports is realistic reality. It's a shame, but I occasionally (always?) see 'submit a diff' more often than I see diff's submitted. One new talented developer is worth more than trying to create a bug tracker. Chris Bennett
