[incubator-heron] branch master updated: Update mailing list informtion in contributing.md (#3110)

[nl...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

nlu90 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-heron.git


The following commit(s) were added to refs/heads/master by this push:
     new cbf7e51  Update mailing list informtion in contributing.md (#3110)
cbf7e51 is described below

commit cbf7e51f260995c9915b1a53bcee6ae3b4d790be
Author: Ning Wang <nw...@twitter.com>
AuthorDate: Mon Nov 19 11:30:34 2018 -0800

    Update mailing list informtion in contributing.md (#3110)
---
 website/content/docs/contributors/community.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/content/docs/contributors/community.md b/website/content/docs/contributors/community.md
index 7d77859..25c4097 100644
--- a/website/content/docs/contributors/community.md
+++ b/website/content/docs/contributors/community.md
@@ -8,7 +8,7 @@ title: Community
 Discussion about Heron happens on GitHub and over mailing list.
 
 * GitHub: [apache/incubator-heron](https://github.com/apache/incubator-heron)
-* Heron User Google Group: [heron-users@googlegroups.com](https://groups.google.com/forum/#!forum/heron-users)
+* Heron User Group: [user@heron.incubator.apache.org](https://mail-archives.apache.org/mod_mbox/heron-user/)
 * Heron on Twitter: [@heronstreaming](https://twitter.com/heronstreaming)
 
 Community is critical to Heron. Contributions are welcomed!
@@ -33,18 +33,18 @@ $ ./scripts/setup-intellij.sh
 In general, contributions that fix bugs or add features (as opposed to stylistic, refactoring, or
 "cleanup" changes) are preferred. If you're looking for places to contribute, issues with label
 [help-wanted](https://github.com/apache/incubator-heron/issues?q=is%3Aopen+is%3Aissue+label%3Ahelp-wanted)
-are good candidates. Please check with [mailing list](https://groups.google.com/forum/#!forum/heron-users)
+are good candidates. Please check with [mailing list](https://mail-archives.apache.org/mod_mbox/heron-dev/)
 if your patch involves lots of changes.
 
 **If you have any question or issues about troubleshooting,
-you should post on [mailing list](https://groups.google.com/forum/#!forum/heron-users) instead
+you should post on [mailing list](https://mail-archives.apache.org/mod_mbox/heron-user/) instead
 of opening GitHub issues.**
 
 ### Submitting a Patch
 1. Read the Heron [governance plan](../governance).
 
 2. Discuss your plan and design, and get agreement on
-[mailing list](https://groups.google.com/forum/#!forum/heron-users).
+[mailing list](https://mail-archives.apache.org/mod_mbox/heron-dev/).
 
 3. Implement proper unit tests along with your change. Verify that all tests can pass.