Bug and todo tracking system brainstorming

hi all

here are some brainstorming about how we could use gjallar to manage  
bugs fix and todo for smalltalk applications. We need inputs
since we would like that the community takes benefit of it.


Here is a draft of Compass (you can also propose a better name)

A group of people (everybody but would be good that people register  
first) can declare bugs or todo = we should give them a name
Bugfinders
       
A group of people (the same) can comment give feedback, tests, fix
Bugfinder

A different group of people (the dispatchers)
        - can assign bugs to project
        - discard them
        - filter them
        - change the bugs status

A group of people
        - can register to a bug to get notified when it is fixed (may be rss  
is enough)
        - can assign the bug to himself

A bugfinder can close its own bugs since it may be a mistake

A package responsible/image
        - is a dispatcher that can
                - close bugs
                - reissue them


Stef

Stéphane Ducasse a écrit : 'Project' seems to be new for me... may be Bugfinders are members of one
or several projects? after the dispatch the bugs are assigned by 1
bugFinder to himself ?

1 bug => 1 bugFinder or * bugFinders?

> A group of people
>     - ...
>     - can assign the bug to himself
this kind of people become bugFinder in this case?
>
> A bugfinder can close its own bugs since it may be a mistake
>
> A package responsible/image
>     - is a dispatcher that can
>         - close bugs
>         - reissue them
So the dispatchers can move bugs inside the workflow but there are
particular jumps that only the package responsible can induce ?
>
>
> Stef
>
>