[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH v2] governance: communication channels



Clarify that xen-devel is the only official communication channel.

Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxx>

---
Changes in v2:
- remove mentions of #xendevel on OFTC

diff --git a/source/communication-practice.rst 
b/source/communication-practice.rst
index 70f5b8c..2ce2a4e 100644
--- a/source/communication-practice.rst
+++ b/source/communication-practice.rst
@@ -9,6 +9,20 @@ This guide provides communication Best Practice that helps you 
in
 * Being aware of your own and counterpart’s communication style and culture
 * Show empathy towards other community members
 
+Communication Channels
+======================
+
+All important communications and messages should be sent to the
+`xen-devel <10_>`_ mailing list, which is the only official channel for
+code submissions, acks, code reviews, and decision-making.
+
+In the modern connected world there are several other communication
+channels available at any given time, including online meetings and IRC.
+However, discussions on media other than the xen-devel mailing list
+should be summarized and sent to xen-devel to reach a wider audience,
+for record-keeping, and to make code submissions, acks, and code reviews
+official.
+
 Code reviews for **reviewers** and **patch authors**
 ====================================================
 
@@ -576,3 +590,4 @@ how to avoid and resolve issues.
 .. _6: https://xenproject.org/help/irc/
 .. _8: https://en.wikipedia.org/wiki/Erin_Meyer
 .. _9: 
https://www.nsf.gov/attachments/134059/public/15LFW_WorkingWithMulticulturalTeams_LarsonC.pdf
+.. _10: https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.