summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorit33 <iantien@gmail.com>2015-11-22 02:12:52 -0800
committerit33 <iantien@gmail.com>2015-11-22 02:12:52 -0800
commit795b60ddbf413bdc5c0c19d8ed5fb92c8d826e6a (patch)
tree04977f6f3c380f7e478063d79c53d4a98db83f9c
parentfe46201b3892871bee7d8cdbe77bc5cedb711496 (diff)
downloadchat-795b60ddbf413bdc5c0c19d8ed5fb92c8d826e6a.tar.gz
chat-795b60ddbf413bdc5c0c19d8ed5fb92c8d826e6a.tar.bz2
chat-795b60ddbf413bdc5c0c19d8ed5fb92c8d826e6a.zip
Explaining why we use different systems
-rw-r--r--doc/process/overview.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/process/overview.md b/doc/process/overview.md
index 53a701784..a383831b3 100644
--- a/doc/process/overview.md
+++ b/doc/process/overview.md
@@ -14,7 +14,9 @@ See [Mattermost scope statement](http://www.mattermost.org/vision/#mattermost-te
## Community Systems
-Feedback from the Mattermost community comes from a range of systems, which are monitored using automation by the core team and key contributors in their Mattermost team site. Systems include:
+The process for managing bugs, feature ideas, troubleshooting, and general discussions are different, so different systems are used to best support each process. Each system ties into Mattermost through notifications to internal channels, so the core team and key contributors can keep up-to-date with community feedback throughout the day.
+
+Systems include:
### Feature Idea Forum