[Asterisk-Dev] Bug Tracker / Feature Requests (my take)

[Michael Giagnocavo]

>So, generally I guess, my overall feeling is that the bug tracker should 
>primarily be focused around things which are active -- primarily bugs and 
>feature requests with patches.  It also seems like a good starting place 
>for features even without patches in case they're very easy....

But does that help Asterisk respond to end-user needs? Some of the people
who might most need features (and be willing to buy hardware, services,
whatever) might not even know what C is.

>At some point though, there needs to be a way to both get them out of the 
>way of myself and the other bug marshals when trying to work on higher 
>priority bugs and features with patches and retain high S/N.  Likewise 
>feature requests with bounties should be centralized so that people 
>looking to add to asterisk but get a bounty in return can find them 
>easily.

Do you think having the community at large vote on issues would help then?
This would somewhat spread out the responsibility of the bug marshals to
each and every person in the community.

I think Asterisk needs to have a system that's designed for *community*, not
just a bug tracker (which are usually designed for a development team).

-Michael