From owner-svn-doc-head@freebsd.org Wed Jan 13 00:53:30 2016 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B0248A8094D; Wed, 13 Jan 2016 00:53:30 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7061C1322; Wed, 13 Jan 2016 00:53:30 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u0D0rTmd038232; Wed, 13 Jan 2016 00:53:29 GMT (envelope-from bjk@FreeBSD.org) Received: (from bjk@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u0D0rTst038231; Wed, 13 Jan 2016 00:53:29 GMT (envelope-from bjk@FreeBSD.org) Message-Id: <201601130053.u0D0rTst038231@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bjk set sender to bjk@FreeBSD.org using -f From: Benjamin Kaduk Date: Wed, 13 Jan 2016 00:53:29 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48005 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jan 2016 00:53:30 -0000 Author: bjk Date: Wed Jan 13 00:53:29 2016 New Revision: 48005 URL: https://svnweb.freebsd.org/changeset/doc/48005 Log: Add entry on the new issue triage team, from Vladimir Krstulja Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Tue Jan 12 23:07:44 2016 (r48004) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Wed Jan 13 00:53:29 2016 (r48005) @@ -2021,4 +2021,124 @@ archive or see the Phabricator review.

+ + + The &os; Issue Triage Team + + + + Bugmeister + bugmeister@FreeBSD.org + + + + + Kubilay + Kocak + + koobs@FreeBSD.org + + + + + Vladimir + Krstulja + + vlad-fbsd@acheronmedia.com + + + + + Rodrigo N. + Hernandez + + rodrigo.FreeBSD@minasambiente.com.br + + + + + Issue Triage Team's Brainstorming Pad + + + +

By the end of the Q4 2015 period, &a.koobs; (koobs@) + started an initiative to form an experimental Bugzilla Triage + Team. The main goals of the team are to increase community + involvement (addition/training of new triagers) and enhance + current procedures and tools, among others. This experiment was + started with the 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 &os; Project. This experimental pilot project + has the task of setting up procedures for enhanced Issue (Problem + Report) management that include better + classification/prioritization, eventually leading to faster + resolution of the issues.

+ +

We are now happy to report on the progress of this + experimental team:

+ +
    +
  • We have set up the #FreeBSD-bugs 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.
    • + +
  • We have identified the primary role of an 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 assignment, which is making sure that the + reported issues are explained well, contain all the appropriate + information (or as much of it as possible), and are brought to + attention of the people who can act upon them.
    • + +
  • Vladimir and Rodrigo are successfully training in bug + triage as well as porting processes (Vladimir is also taking + maintainership of some ports).
    • + +
  • This experiment is benefiting from the introduction of + newcomers to issue tracking. It naturally resulted in a entire + review of the tracking proccess from its very elementary aspects. + This "fresh eyes" participation spotted minor details + along the proccess, giving the opportunity to scrutinize actual + procedures on a number of smaller points, followed by proposals on + how to improve the overall Issue Tracking and Management. The new + ideas include both organizational and technical ideas and + solutions, such as new or modified keywords or flags for better + classification, the triage workflow, and Bugzilla technical + improvements among others.
    • + +
  • An important goal is producing documentation not only + aimed at people directly engaged on issue triage tasks, but also + documentation aimed at general users, about best practices for + using Bugzilla and the 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 &os;'s needs, and development of new features (please see + Mahdi "Magic" Mokhtari's report on "Bugzilla + improvements").
    • + +
  • We are still collating ideas in preparation of setting + up a Wiki namespace 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.
+ +

Since the Issue Triage Team is very young, we expect more + information be available and more actions be reported upon in the + next Status report.

+ + + + +

Set up the Wiki namespace and organize the brainstorm + document into a meaningful set of documents.

+ + + +

Recruit more suitable triagers into the team.

+ + +