svn commit: r45003 - head/en_US.ISO8859-1/articles/problem-reports
Warren Block
wblock at FreeBSD.org
Tue Jun 3 23:21:49 UTC 2014
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 at 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.</para>
+
+ <para>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.</para>
+
+ <para>There are a few ways to do so, ideally in the following
+ order, with a few days between attempting each communication
+ channel:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Find the relevant &os; mailing list for the problem
+ report from the <link
+ xlink:href="&url.books.handbook;/eresources.html#ERESOURCES-MAIL">list
+ in the Handbook</link> and send a message to that list
+ asking about assistance or comments on the problem
+ report.</para>
+ </listitem>
+
+ <listitem>
+ <para>Join the relevant <acronym>IRC</acronym> channels.
+ A partial listing is here: <link
+ xlink:href="https://wiki.freebsd.org/IrcChannels"></link>.
+ 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.</para>
+ </listitem>
+
+ <listitem>
+ <para>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 <link
+ xlink:href="http://svnweb.FreeBSD.org">SVN
+ Repository</link>. Locate the last few committers who
+ made substantive changes to the file, and try to reach them
+ via <acronym>IRC</acronym> or email. A list of committers
+ and their emails can be found in the <link
+ xlink:href="&url.articles.contributors.en;">Contributors
+ to &os;</link> article.</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>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.</para>
</section>
<section xml:id="pr-problems">
More information about the svn-doc-head
mailing list