Page Menu
Home
FreeBSD
Search
Configure Global Search
Log In
Files
F147193303
D16092.id44746.diff
No One
Temporary
Actions
View File
Edit File
Delete File
View Transforms
Subscribe
Mute Notifications
Flag For Later
Award Token
Size
2 KB
Referenced Files
None
Subscribers
None
D16092.id44746.diff
View Options
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,11 @@
<emphasis>explicit</emphasis> approval from the respective
maintainers.</para>
</listitem>
+
+ <listitem>
+ <para>Conduct discussions in public or report the results of
+ discussions to public forums</para>
+ </listitem>
</orderedlist>
<para>As noted, breaking some of these rules can be grounds for
@@ -3513,6 +3518,39 @@
<para>Contact the &a.core; if you wish to take up
maintainership of an unmaintained part of the tree.</para>
</listitem>
+
+ <listitem>
+ <para>Conduct discussions in public or report the results of
+ discussions to public forums.</para>
+
+ <para>&os; is a trusted Open Source project because of its
+ emphasis on transparency and disclosure. Where
+ reasonable, conducting discussions in public forums is
+ encouraged (notably because there is no effort required
+ to summarize the outcome for the public). Where this is
+ not possible, due to subject mater expertise or
+ timeliness, the results of technical discussions and
+ topics should be made public so the project's working
+ memory can be enriched through a shared understanding of
+ the outcome from subject matter experts. The trade-off
+ of productivity from focused conversations vs the cost
+ of summarizing the outcome of a discussion is left to
+ the best judgement of the participants.</para>
+
+ <para>If you think something should be discussed in public,
+ suggest to the other participants to have the discussion
+ in public, or to make the summary available of a
+ discussion available so the community at large may benefit
+ from the rationale that lead up to a decision. Reminder:
+ it is not acceptable to unilaterally make a discussion or
+ summary available in a public forum without consent (e.g.
+ &a.developers; or private correspondence). In the end,
+ use good judgement to facilitate productive communication
+ practices between individuals and be mindful of our open
+ source community writ-large (including but not limited to:
+ commercial users, appliance vendors, open source
+ enthusiasts, students, and service providers).</para>
+ </listitem>
</orderedlist>
</sect2>
File Metadata
Details
Attached
Mime Type
text/plain
Expires
Tue, Mar 10, 12:23 AM (15 h, 13 m)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
29465579
Default Alt Text
D16092.id44746.diff (2 KB)
Attached To
Mode
D16092: Committer guide: add note about private discussions
Attached
Detach File
Event Timeline
Log In to Comment