This is an old revision of the document!
The Problem
Currently we are not doing as well at handling Problem Reports as we could. So, how can we fix this?
The main problem is that we have more PRs coming in than we have volunteers working on fixing them. This is due to several reasons:
- We have no “culture” of bugbusting.
- Bugbusting is not as much fun as adding new features.
- We have never figured out a way to let our non-committers help us.
- We have not done a good job of managing our users' expectations of what the developers can reasonably accomplish.
Our current status
- The ports PRs have automated systems written to both assign them to committers (when possible), to notify maintainers, and to remind maintainers if they have not responded. In addition, a 2-week timeout period has been adopted. Thus, the ports PRs tend to have fairly good clearance rate, and are in relatively reasonable shape.
- The other PRs (in particular bin/ and i386/) tend to have a much lower clearance rate, and are not in good shape.
What has been done recently
- We have created a way for non-committers to get access to GNATS. While this is reserved for the most persistent volunteers, it has produced good results.
- We have done some [“Bugathons”] to try to get more people involved.
- We have advocated more active use of the #freebsd-bugbusters IRC channel.
- We have started closing some of the PRs that have little hope of being addressed (in particular, the “how do I make XYZ work” type), and recommending that they instead ask questions on the mailing lists. This will help us focus more on actual bugs.
- Several people have been contacting PR submitters and asking whether the problems still exist. (For problems in bin/, this is more often true than you might expect). A large number of obsolete PRs have been closed.
- We have been eliminating duplicate PRs.
None of these has been a complete success yet.
What we still need to do
- Get more committers looking at the recommended PRs, and getting them committed.
- Figuring out more ways for non-committers to help us.
- Attract more attention to the mailing list and IRC channel, to try to create more of a “culture”.
Resources
- The bugmeister team, bugmeister@FreeBSD.org (responsible for the maintenance of the database and associated code)
- Weekly postings of bug summaries to freebsd-bugs@FreeBSD.org (including overall, PRs by tag, PRs with patches)
- Weekly posting of “PRs recommended for committer evaluation” to freebsd-bugs@FreeBSD.org
- Weekly reminders of assigned PRs, to each assignee
- Auto-assignment of ports PRs (run by EdwinGroothuis)
- freebsd-bugbusters# IRC channel on EFNet
- Information about [“Debugging”] with FreeBSD