MarkLinimon has gathered together a large number of emails and IRC conversations during January 2008 (and some previously) and needs to edit them up and present them. However, as of 20080121 this isn't in a state that is ready to present. Here's some things we need to do to start.

• [wiki:self:BugBusting/Volunteers sign up new volunteers ]. We have had a great deal of interest from people wanting to know “how can I help”. To start with, we should gather information about levels of expertise and interests.

• PRs in the 'patched' state. These represent code changes that have already been committed to whatever represented -CURRENT at the time, and have been flagged as needing merges to a release branch. Many of these have probably already been merged. Someone who is interested can look through [http://www.freebsd.org/cgi/cvsweb.cgi/src/ cvsweb ] and determine whether or not this is the case. For ones that have, they can be closed; for ones that have not, whoever committed the change should be notified. (Usually they have the PR already assigned to them, but not always.)

Note: it is too late in the 7.0 release cycle for anything to be merged to it; however, it's reasonable to think we can merge things to RELENG_7.

• Start thinking about more categories for PRs.

Right now the kern PRs are far too monolithic. At the very least we need to break that up.

Originally, MarkLinimon was of the opinion that we should wait to break up the categories until we had a really clear idea of all the ones that we wanted. However, this was probably a bad idea: we should try some experiments and see if we can make something better than what we have. (This would also carry over to any future bugtracking system.)

If we think about breaking them up by existing mailing list as a first approximation, you get:

• fs → freebsd-fs
• geom → freebsd-geom
• etc.

Note: we already did this for usb some time back.

MarkLinimon will take the action item to figure out how to push the changes we make out to everyone's systems.