From owner-svn-doc-head@FreeBSD.ORG Tue Jun 3 23:21:49 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 681DADE; Tue, 3 Jun 2014 23:21:49 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::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 54AE32638; Tue, 3 Jun 2014 23:21:49 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s53NLnCm060470; Tue, 3 Jun 2014 23:21:49 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s53NLnmr060469; Tue, 3 Jun 2014 23:21:49 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201406032321.s53NLnmr060469@svn.freebsd.org> From: Warren Block Date: Tue, 3 Jun 2014 23:21:49 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45003 - head/en_US.ISO8859-1/articles/problem-reports 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.18 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: Tue, 03 Jun 2014 23:21:49 -0000 Author: wblock Date: Tue Jun 3 23:21:48 2014 New Revision: 45003 URL: http://svnweb.freebsd.org/changeset/doc/45003 Log: Update the Problem Reports article, adding techniques for followup when a PR has been untouched for a while. Modified version of patch included with PR. PR: docs/190593 Submitted by: ports@robakdesign.com Modified: head/en_US.ISO8859-1/articles/problem-reports/article.xml Modified: head/en_US.ISO8859-1/articles/problem-reports/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/problem-reports/article.xml Tue Jun 3 22:29:10 2014 (r45002) +++ head/en_US.ISO8859-1/articles/problem-reports/article.xml Tue Jun 3 23:21:48 2014 (r45003) @@ -1242,6 +1242,60 @@ gone away, just send a follow-up (in the manner prescribed above) saying that the problem report can be closed, and, if possible, explaining how or when the problem was fixed. + + Sometimes there is a delay of a week or two where the + problem report remains untouched, not assigned or commented on + by anyone. This can happen when there is an increased problem + report backlog or during a holiday season. When a problem + report has not received attention after several weeks, it is + worth finding a committer particularly interested in working on + it. + + There are a few ways to do so, ideally in the following + order, with a few days between attempting each communication + channel: + + + + Find the relevant &os; mailing list for the problem + report from the list + in the Handbook and send a message to that list + asking about assistance or comments on the problem + report. + + + + Join the relevant IRC channels. + A partial listing is here: . + Inform the people in that channel about the problem report + and ask for assistance. Be patient and stay in the channel + after posting, so that the people from different time zones + around the world have a chance to catch up. + + + + Find committers interested in the problem that was + reported. If the problem was in a particular tool, binary, + port, document, or source file, check the SVN + Repository. Locate the last few committers who + made substantive changes to the file, and try to reach them + via IRC or email. A list of committers + and their emails can be found in the Contributors + to &os; article. + + + + Remember that these people are volunteers, just like + maintainers and users, so they might not be immediately + available to assist with the problem report. Patience and + consistency in the follow-ups is highly advised and appreciated. + With enough care and effort dedicated to that follow-up process, + finding a committer to take care of the problem report is just a + matter of time.