[Asterisk-Dev] Patches, Tweaks and Features....

[brian]

Ok as a bug Marshal, people come crying to me about X or Y.... I don't mind
it but when it's about the same things over and over again I think I must
say something about it.

1. If a patch is submitted and you think it's not the right way and you
offer up "It can be done better" offer an example of some sort, code it or
shut up.  Don't say it can be done better and run off and hide.

2. If a new feature is posted and it has the HELL NO chance of getting in
CVS lets either say that or offer feedback on how to get it in CVS.  There
are a lot of talented people on the -dev list that can do a damn fine job of
bringing new features/tweaks to asterisk.  I thank each and everyone of you!
Good Job!

3. House keeping on the bug tracker.  I'm sorry but we had to do this over
the weekend just way too much clutter, outdated patches.  If something was
closed that you would like to see then code it, comment on it or speak up
about it.  We are happy to reopen them (#asterisk-bugs if you need one
reopened).

4. When you post a bug be ready to respond within 24 hours of each contact.
Taking up to 7 days to respond is silly.

5. We now have #asterisk-bugs where the bug marshals hang out you can come
in here and find us if you think you found a bug.  Posting a bug with
something like "It don't work!" or "X or Y isn't compliant" be ready to back
up those clams with steps to reproduce the problem or quote an RFC section
that tells us the way it should be.

Again I Thank each and everyone that helps make Asterisk a kick ass
platform.

Thanks,
Brian