nlu90 closed pull request #3110: Update mailing list informtion in contributing.md URL: https://github.com/apache/incubator-heron/pull/3110
This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/website/content/docs/contributors/community.md b/website/content/docs/contributors/community.md index 7d7785963e..25c409700d 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: [[email protected]](https://groups.google.com/forum/#!forum/heron-users) +* Heron User Group: [[email protected]](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. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
