[Insight-developers] Bug categories in Mantis

[David Doria]

On Thu, Jun 9, 2011 at 9:32 AM, Cory Quammen <cquammen at cs.unc.edu> wrote:
> Pertaining to this bug
>
> http://public.kitware.com/Bug/view.php?id=9541
>
> about the use of categories in Mantis, I have some suggestions.
>
> In my local projects, I typically have four categories:
>
> Code
> Build
> Install
> Documentation
>
> For a project as large as ITK, it might make sense to have
> subcategories of at least the Code category, such as:
>
> Code - Bridge
> Code - Core
> Code - Filtering
> Code - GPU
> ...
>
> and so on for the various groups. Individual module names might be too
> much. Unfortunately, Mantis doesn't provide subcategories by default,
> hence my naming convention of "Code - ModuleGroup".
>
> We might consider categories for initiatives, such as the various
> refactoring projects going on:
>
> ITKv4 - DICOM
> ITKv4 - Registration Refactoring
> ITKv4 A2D2 - Deconvolution
> ...
>
> But we may not want those to persist in the bug tracker 10 years from
> now. Perhaps those would be better as tags?
>
> - Cory

Including the module name in or as the category seems reasonable. I
think so many of the issues would fall under Code (out of Code, Build,
Install, Documentation) that those probably wouldn't help anything. My
original concern when reporting that issue was that it just seemed
silly to have a required field with no options to select from - I was
not intending/suggesting to change the ITK Mantis workflow :)

I agree that names relevant to particular efforts will not make sense
if the issues persist after the effort ends.

David