Repository: beam-site Updated Branches: refs/heads/asf-site b647ca562 -> bbe028320
[BEAM-325] Add Slack details to website Project: http://git-wip-us.apache.org/repos/asf/beam-site/repo Commit: http://git-wip-us.apache.org/repos/asf/beam-site/commit/447118d9 Tree: http://git-wip-us.apache.org/repos/asf/beam-site/tree/447118d9 Diff: http://git-wip-us.apache.org/repos/asf/beam-site/diff/447118d9 Branch: refs/heads/asf-site Commit: 447118d993e863fd702da9f3ff543d6618ab8315 Parents: b647ca5 Author: Ismaël MejÃa <[email protected]> Authored: Thu Mar 2 07:12:21 2017 +0100 Committer: Ismaël MejÃa <[email protected]> Committed: Thu Mar 2 07:12:21 2017 +0100 ---------------------------------------------------------------------- src/contribute/contribution-guide.md | 5 +++++ 1 file changed, 5 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/beam-site/blob/447118d9/src/contribute/contribution-guide.md ---------------------------------------------------------------------- diff --git a/src/contribute/contribution-guide.md b/src/contribute/contribution-guide.md index a959feb..3bff89e 100644 --- a/src/contribute/contribution-guide.md +++ b/src/contribute/contribution-guide.md @@ -47,6 +47,11 @@ If thereâs an existing JIRA issue for your intended contribution, please comme For moderate or large contributions, you should not start coding or writing a design document unless there is a corresponding JIRA issue assigned to you for that work. Simple changes, like fixing typos, do not require an associated issue. +### Online discussions +We don't have an official IRC channel. Most of the online discussions happen in the [Apache Beam Slack channel](https://apachebeam.slack.com/). If you want access, you need to send an email to the user mailing list to [request access](mailto:[email protected]?subject=Regarding Beam Slack Channel&body=Hello%0D%0A%0ACan someone please add me to the Beam slack channel?%0D%0A%0AThanks.). + +Chat rooms are great for quick questions or discussions on specialized topics. Remember that we strongly encourage communication via the mailing lists, and we prefer to discuss more complex subjects by email. Developers should be careful to move or duplicate all the official or useful discussions to the issue tracking system and/or the dev mailing list. + ## Design To avoid potential frustration during the code review cycle, we encourage you to clearly scope and design non-trivial contributions with the Beam community before you start coding.
