Adding the COMMUNICATION.md to the Standard Base Documentation pattern (InnerSourceCommons#589)

* Added COMMUNICATION.md and ADI instance to base-documentation.md.
* Adding COMMUNICATION template to the sidebar of the book (en only)0

Author: kschueths

book/en/toc_template.md

@@ -27,6 +27,7 @@ Instead edit toc_template.md
 * Extras
   * [README Template](../../patterns/2-structured/project-setup/templates/README-template.md)
   * [CONTRIBUTING Template](../../patterns/2-structured/project-setup/templates/CONTRIBUTING-template.md)
+  * [COMMUNICATION Template](../../patterns/2-structured/project-setup/templates/COMMUNICATION-template.md)
   * [RFC Template](../../patterns/2-structured/templates/rfc.md)
 
 ## Resources

patterns/2-structured/project-setup/base-documentation.md

@@ -6,7 +6,7 @@ Standard Base Documentation
 
 New contributors to an InnerSource project have a hard time figuring out who
 maintains the project, what to work on, and how to contribute. Providing
-documentation in standard files like `README.md`/`CONTRIBUTING.md` enables a
+documentation in standard files like `README.md`/`CONTRIBUTING.md`/`COMMUNICATION.md` enables a
 self service process for new contributors, so that they can find the answers to
 the most common questions on their own.
 
@@ -81,23 +81,44 @@ topics:
 
 ![CONTRIBUTING.md](../../../assets/img/standard-base-documentation/CONTRIBUTING-for-contributors.png)
 
+### COMMUNICATION.md
+
+Create a separate `COMMUNICATION.md` document. Link this document to your `README.md` so comprehensive contact information can be provided and not take up the extra space in your README. This document should answer frequently
+asked questions about communicating with your team that contributors need to know. The goal is to streamline communications so users and contributors reach out to the correct person through a single channel. This reduces unnecessary distractions for team members and organizes communications so they do not get lost.
+
+Sections in the `COMMUNICATION.md` include points of contact for incoming communications and information about outgoing communications from the project's ownership team. See some examples below.
+
+Points of contact for incoming communication and how to contact those users:
+
+* Reporting a bug
+* Following up on a PR
+* Feature requests
+* Questions about documentation
+* Escalations
+
+How and when the team communicates outbound with users and how to get added to those communications:
+
+* Planned and unplanned outages
+* Feature releases
+* Code freezes
+* Breaking changes
+
 There are many of good examples for how to write a `README.md` and what kind
 of information to include in a `CONTRIBUTING.md` file in various open source projects.
 Pages like [how to write a readme that rocks](https://m.dotdev.co/how-to-write-a-readme-that-rocks-bc29f279611a),
 [Open Source Guide from GitHub](https://opensource.guide/) as well as
 the book [Producing Open Source](https://producingoss.com/en/producingoss.html)
 all have valuable information on what kind of information to provide. While
 Producing Open Source does not have a chapter on writing a good README per se,
-the [Getting Started
-chapter](https://producingoss.com/en/producingoss.html#starting-from-what-you-have)
+the [Getting Started chapter](https://producingoss.com/en/producingoss.html#starting-from-what-you-have)
 does provide a fairly extensive list of things that fellow host team members,
 users and contributors will need. InnerSource projects likely will not cover all
 of those aspects right from the start, the list itself is helpful for
 inspiration for what one could cover.
 
-In addition to that, this pattern comes with two very basic templates to get you
-started right away: [README-template.md](templates/README-template.md) and
-[CONTRIBUTING-template.md](templates/CONTRIBUTING-template.md)
+In addition to that, this pattern comes with three very basic templates to get you
+started right away: [README-template.md](templates/README-template.md),
+[CONTRIBUTING-template.md](templates/CONTRIBUTING-template.md), and [COMMUNICATION-template.md](templates/COMMUNICATION-template.md).
 
 ## Resulting Context
 
@@ -110,11 +131,16 @@ started right away: [README-template.md](templates/README-template.md) and
 * Europace AG - See blog post [InnerSource: Adding base documentation](https://tech.europace.de/post/innersource-base-documentation/)
 * Paypal Inc.
 * Mercado Libre - create a documentation site that contains how to get started with InnerSource and also define the basic artifacts that a repository must have to be InnerSource (README, CONTRIBUTING, CODING_GUIDELINES, etc).
+* Analog Devices Inc.
 
 ## Authors
 
 * Isabel Drost-Fromm
 
+## Acknowledgments
+
+* Katie Schueths - for adding the `COMMUNICATION.md` concept
+
 ## Alias
 
 Provide standard base documentation through a README