Attachment 143346 Details for Bug 190593 – problem-reports-article-xml.diff

[patch] problem-reports-article-xml.diff

problem-reports-article-xml.diff (text/plain), 2.63 KB, created by Bartek Rutkowski on 2014-06-03 22:18:34 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Bartek Rutkowski

Created: 2014-06-03 22:18:34 UTC

Size: 2.63 KB

patch

obsolete

>Index: article.xml
>===================================================================
>--- article.xml	(revision 44999)
>+++ article.xml	(working copy)
>@@ -1242,6 +1242,55 @@
>       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>In case the PR stays untouched (not assigned or commented
>+      on by anyone) after a week or two, which may happen in certain
>+      circumstances, such as when there is an increased PR backlog
>+      or during a holiday season, it is worth trying to find a
>+      committer particularly interested in working on the PR.</para>
>+
>+    <para>There are a few ways to do so, ideally in the following
>+      order, with a few days between each communication
>+      channel:</para>
>+
>+    <itemizedlist>
>+      <listitem>
>+	<para>Find out what the relevant FreeBSD mailing list for
>+	  the problem report is (a full list is here: <link
>+	  xlink:href="https://lists.freebsd.org/mailman/listinfo"></link>)
>+	  and send a message informing it about the PR and asking
>+	  for assistance and/or comments</para>
>+      </listitem>
>+
>+      <listitem>
>+	<para>Join the relevant IRC channels (a partial listing is
>+	  here: <link
>+	    xlink:href="https://wiki.freebsd.org/IrcChannels"></link>)
>+	  and inform the people who are in that channel about the
>+	  PR and asking for assistance and/or comments - make sure
>+	  to be patient and stay in the channel after posting, so
>+	  that the people from different timezones around the
>+	  world have a chance to catch up</para>
>+      </listitem>
>+
>+      <listitem>
>+	<para>Find the committers interested in the problem that
>+	  was reported - if it exists in a particular tool, binary,
>+	  port or source file, check who were the last few
>+	  committers making substantive changes to it, and try to
>+	  reach them via IRC or email (the list of committers and
>+	  their emails can be find here: <link
>+	    xlink:href="https://www.freebsd.org/doc/en/articles/contributors/staff-committers.html"></link>)</para>
>+      </listitem>
>+    </itemizedlist>
>+
>+    <para>Remember that the people you'll be trying to get help from
>+      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 PR is
>+      just a matter of time.</para>
>   </section>
> 
>   <section xml:id="pr-problems">

Actions: View | Diff

Attachments on bug 190593: 143346