On Wed, Nov 18, 2015 at 6:58 AM, Olle E. Johansson <[email protected]> wrote:
> Yay! > > I notice in a bug report that the response talks about a Bug Marshal. I > am very happy that we have bug marshals back in the process. Is there a > document somewhere outlining the process of becoming one and what they do > nowadays? > > Cheers, > /O > > Hey Olle! I don't think the term bug marshal ever went away. If that was unclear, then I'm sorry about that. As long as I've been around, there's always been special settings set up for JIRA users who are in the "Asterisk Developers" group (such as the ability to see reported security vulnerabilities, etc.). People who generally help solve problems in JIRA are always put in that group. The Asterisk wiki documents what a Bug Marshal does in the Issue Tracker Workflow page: https://wiki.asterisk.org/wiki/display/AST/Issue+Tracker+Workflow Additional guidelines for what constitutes a "good" bug report can be found on the Asterisk Issue Guidelines page (which is linked from the previously mentioned page as well): https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines Let me know if there's anything you think might be missing on those wiki pages - we're always trying to improve the documentation of the project! Thanks - Matt -- Matthew Jordan Digium, Inc. | Director of Technology 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
