<project cat='team'>
  <title>The FreeBSD Issue Triage Team</title>

  <contact>
    <person><name>Bugmeister</name><email>bugmeister@freebsd.org</email></person>
    <person><name><given>Kubilay</given><common>Kocak</common></name><email>koobs@freebsd.org</email></person>
    <person><name><given>Vladimir</given><common>Krstulja</common></name><email>vlad-fbsd@acheronmedia.com</email></person>
    <person><name><given>Rodrigo N.</given><common>Hernandez</common></name><email>rodrigo.freebsd@minasambiente.com.br</email></person>
  </contact>

  <links>
    <url href="https://pad.riseup.net/p/freebsd-triage-brainstorming">Issue Triage Team's Brainstorming Pad</url>
  </links>

  <body>
    <p>
        By the end of the Q4 2015 period, Kubilay Kocak (koobs@), started an
        initiative to form an experimental Bugzilla Triage Team. The main goals
        of it are increasing community involvement (addition/training of new
        triagers) and enhancing current procedures and tools among
        others. This experiment was started with participation of Vladimir
        (blackflow on irc/freenode) and Rodrigo (DanDare on irc/freenode), who
        approached koobs@ with a desire to contribute and get more involved
        with the FreeBSD Project. This experimental pilot project has the
        importance of setting up procedures for enhanced Issue (Problem
        Report), management that includes better classification/prioritization
        which eventually leads to faster resolution of the issues.
    </p>
    <p>
        We are now happy to report on the progress of this experimental team:
        <ul>
            <li>
                We have set up <strong>#freebsd-bugs</strong> IRC channel on
                Freenode and we are successfully using it to exchange
                information about triage processes, ask for help, propose
                changes and discuss related topics.
            </li>
            <li>
                We have identified the primary role of a Issue Triage Team to
                be that of classification of problem reports of all kinds
                (currently limited mostly to ports and obvious src issues) and
                facilitation of issue <strong>assignment</strong>, which is
                making sure the reported issues are explained well containing
                all the appropriate information (or as much of it as possible),
                and brought to attention of the people who can act upon them.
            </li>
            <li>
                Vladimir and Rodrigo are successfully training in bug triage as
                well as porting processes (Vladimir, who is also taking maintainership
                of some ports).
            </li>
            <li>
                This experiment is benefiting from the introduction of
                newcomers to issue tracking. It naturally resulted in a entire
                review of the tracking proccess from it's very elementary
                aspects. This <strong>"fresh eyes"</strong> participation
                permitted spotting minor details along the proccess, bringing
                opportunity to scrutinize actual procedures on a number of
                smaller points followed by proposal of several suggestion on
                how to improve the overall Issue Tracking and Management, from
                organizational through technical ideas and solutions such as
                new or modified keywords or flags for better classification,
                triage workflow, Bugzilla technical improvements among others.
            </li>
            <li>
                An important goal is producing documentation not only aimed at
                people directly engaged on the issue triage tasks but also
                aimed at general users, about best practices using Bugzilla and
                issue management workflow. Another relevant point is that
                feedback from triage team can be used to improve Bugzilla in
                terms of adjusting existing features to best fit FreeBSD needs
                and development of new features (please see Mahdi "Magic"
                Mokhtari's report on "Bugzilla improvements").
            </li>
            <li>
                We are still collating ideas in preparation of setting up a
                <strong>Wiki namespace</strong> for the overall topic of issue
                management, containing information for all the parties involved
                in issue tracking: from users (reporters) to maintainers and
                committers. The unorganized brainstorming document is linked in
                this report.
            </li>
        </ul>
    </p>
    <p>
        Since the Issue Triage Team is very young, we expect more information be
        available as well as more actions be done in time by next Status report.
    </p>
  </body>

  <help>
    <task>Set up the Wiki namespace and organize the brainstorm doc into a meaningful set of documents</task>
    <task>Recruit more suitable triagers into the team</task>
  </help>

</project>

