&os; Issue Triage Team

From owner-svn-doc-all@freebsd.org Sat Jul 9 14:00:32 2016 Return-Path: Delivered-To: svn-doc-all@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 EA91AB831E7; Sat, 9 Jul 2016 14:00:32 +0000 (UTC) (envelope-from dru@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 AA2171DAE; Sat, 9 Jul 2016 14:00:32 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u69E0VMA044231; Sat, 9 Jul 2016 14:00:31 GMT (envelope-from dru@FreeBSD.org) Received: (from dru@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u69E0VQn044230; Sat, 9 Jul 2016 14:00:31 GMT (envelope-from dru@FreeBSD.org) Message-Id: <201607091400.u69E0VQn044230@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: dru set sender to dru@FreeBSD.org using -f From: Dru Lavigne Date: Sat, 9 Jul 2016 14:00:31 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r49082 - 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-all@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jul 2016 14:00:33 -0000 Author: dru Date: Sat Jul 9 14:00:31 2016 New Revision: 49082 URL: https://svnweb.freebsd.org/changeset/doc/49082 Log: Add the issue triage team's report submitted by vlad-fbsd@acheronmedia.com. Reviewed by: wblock Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-04-2016-06.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-04-2016-06.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2016-04-2016-06.xml Sat Jul 9 13:11:12 2016 (r49081) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2016-04-2016-06.xml Sat Jul 9 14:00:31 2016 (r49082) @@ -1444,4 +1444,131 @@ Implementation of the 4.3BSD UNIX Operating System.

+ + + &os; Issue Triage Team + + + + + Vladimir + Krstulja + + vlad-fbsd@acheronmedia.com + + + + + Kubilay + Kocak + + koobs@freebsd.org + + + + Bugmeister + bugmeister@freebsd.org + + + + +

Since the Triage Team was introduced in the October-December + 2015 report, it has been working on the following three major + aspects of issue triage:

+ +

Recruiting and educating more users to assist in issue + triage.
Identifying problem areas, especially from the fresh eyes + perspective, revealing issues not immediately obvious to + contributors with experience.
Proposing changes to improve the issue triage + process.

+ +

Our efforts have almost exclusively focused on issues in the + "Ports & Packages" component as that is the easiest + starting point. Other categories like "Base System" require + more knowledge and experience with problem content and + workflow.

+ +

During this time, Rodrigo was inactive due to lack of + available time and Vladimir was unable to commit enough time + during the first quarter of the year, but provided active + contribution during the second. It became obvious that the + Issue Triage Team must concentrate on additional recruitment + in the coming quarter.

+ +

In the last two quarters, several problems were identified + and the formulated solutions will be published on our upcoming + Wiki page. A summary of those issues is given here:

+ +

Issue triage, defined as "ensure an issue is summarized, + classified, and assigned to appropriate people", is too time + consuming. Bugzilla automation through auto-assign helps, + but is insufficient. If the triage process is extended to + include "track the issue through its entire life to + resolution", the time and effort required grows + exponentially. Fortunately, there are many things the + community can do, with minimum effort, that help greatly. + Part of the recruitment and education process is educating + users on how to properly treat their own issues and issues + they interact with in order to maximize the efficiency of + issue tracking and problem resolution.
Various timeouts are inadequate. For example, the + maintainer timeout is too long and does not differentiate + between classes of issues, such as a non-security and a + security timeout. Other timeouts are not covered, such as + assignee timeouts, when an issue has been assigned with no + follow-up activity. Another example is a timeout where + additional information was requested but never provided. + We will be recommending several changes and documenting + these in our Wiki.
Partially as a consequence of inadequate timeouts and + inadequate ability to efficiently track issues through their + entire lifecycle, a great number of issues are open for too + long. We have identified several classes of those issues + and will document the solutions to each in the near + future.
Bugzilla is not perfect and at times it can hinder the + ability to properly track issues clearly and accurately, in + order to resolve them quickly. However, changing bug + tracking software is a tremendous effort, so we will instead + recommend technical and workflow improvements in order to + improve the user experience as much as possible. For + example, we identified additional saved searches to help + track and quickly find issue categories and, more + importantly, their states. Another example + is ensuring that various flags and keywords are unambiguous + and well understood. For instance, "patch" and + "patch-ready", can often be misunderstood or + misapplied.
Issue statistics are lacking and for the next quarter we + intend to change that. Statistics help to provide insight + into potential bottlenecks and inform the priority of + improvements to the issue tracker and workflows.

+ + + + Recruit more suitable triagers into the team, both + committers and community members. + + Gather and present some interesting statistics for the + next report. + + Set up the Wiki page with identified problems and + recommended guidelines and policies. + + Find common use patterns and add more saved searches to + Bugzilla. + +