Add some instructions for committers that need to ask questions.

Adapted from mail sent by bz@ to an internal list.

en_US.ISO8859-1/articles/committers-guide/article.xml

@@ -2346,6 +2346,45 @@ ControlPersist yes</screen>
       will review code.</para>
   </sect1>
 
+  <sect1 id="if-in-doubt">
+    <title>If in doubt...</title>
+
+    <para>When you are not sure about something, whether it be a
+      technical issue or a project convention be sure to ask.  If you
+      stay silent you will never make progress.</para>
+
+    <para>If it relates to a technical issue ask on the public
+      mailing lists.  Avoid the temptation to email the individual
+      person that knows the answer.  This way everyone will be able to
+      learn from the question and the answer.</para>
+
+    <para>For project specific or administrative questions you should
+      ask, in order: </para>
+
+    <itemizedlist>
+      <listitem>
+	<para>Your mentor or former mentor.</para>
+      </listitem>
+
+      <listitem>
+	<para>An experienced committer on IRC, email, etc.</para>
+      </listitem>
+
+      <listitem>
+	<para>Any team with a "hat", as they should give you a
+	  definitive answer.</para>
+      </listitem>
+
+      <listitem>
+	<para>If still not sure, ask on &a.developers;.</para>
+      </listitem>
+    </itemizedlist>
+
+    <para>Once your question is answered, if no one pointed you to
+      documentation that spelled out the answer to your question,
+      document it, as others will have the same question.</para>
+  </sect1>
+
   <sect1 id="gnats">
     <title>GNATS</title>