Workflow: Categorization

The current categories do not work well.

  • 'kern' is too all-inclusive (kernel + drivers + libraries + ...)
  • no one knows what '<arch>' is for
  • need something for infrastructure ('build'?)
  • users, lacking guidance, just drop things in 'misc'

Our first workaround has been to introduce the concept of a 'tag'. (Examples: [ata], [nfs], and so forth.) These are just strings added into the Synopsis fields by hand. This has allowed the creation of the current problem reports sorted by tag email. However, it is far too much data to read.