Index: en_US.ISO8859-1/articles/committers-guide/article.xml
===================================================================
--- en_US.ISO8859-1/articles/committers-guide/article.xml
+++ en_US.ISO8859-1/articles/committers-guide/article.xml
@@ -3175,6 +3175,10 @@
 	  <emphasis>explicit</emphasis> approval from the respective
 	  maintainers.</para>
       </listitem>
+
+      <listitem>
+	<para>Avoid private technical discussions.</para>
+      </listitem>
     </orderedlist>
 
     <para>As noted, breaking some of these rules can be grounds for
@@ -3513,6 +3517,31 @@
 	  <para>Contact the &a.core; if you wish to take up
 	    maintainership of an unmaintained part of the tree.</para>
 	</listitem>
+
+	<listitem>
+	  <para>Avoid private technical discussions.</para>
+
+	  <para>Discussing technical topics in public is almost always
+	    better than not.  &os; is an Open Source project for which
+	    <emphasis>Open</emphasis> is as important as writing
+	    source code.  Default to public unless there is an
+	    explicit and clear reason for it to be private.</para>
+
+	  <para>People who are not a part of the immediate convertion
+	    will be interested in both the result, and the motivation
+	    for how that decision was made.</para>
+
+	  <para>This default applies to both private emails between
+	    developers, and the internal adminstrative lists (such as
+	    &a.developers;.)  This does not provide the right to
+	    reveal private conversations without permission, but you
+	    encouraged to withhold a reply until the requestor asks in
+	    a more public forum.</para>
+
+	  <para>It is worth reading the section of
+	    <link xlink:href="https://producingoss.com/en/setting-tone.html#avoid-private-discussions">Producing Open Source</link> on this topic.</para>
+
+	</listitem>
       </orderedlist>
     </sect2>