You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by me...@apache.org on 2018/04/26 04:41:01 UTC

[beam-site] 02/03: Further refinement.

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

mergebot-role pushed a commit to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git

commit 265088ec44da4dceab24c9ce0b6570eda1984488
Author: Robert Bradshaw <ro...@gmail.com>
AuthorDate: Wed Apr 25 09:45:19 2018 -0700

    Further refinement.
---
 src/contribute/contribution-guide.md | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/src/contribute/contribution-guide.md b/src/contribute/contribution-guide.md
index 21cd434..3c16092 100644
--- a/src/contribute/contribution-guide.md
+++ b/src/contribute/contribution-guide.md
@@ -66,6 +66,7 @@ mailing list, which is archived
 [here](https://lists.apache.org/list.html?dev@beam.apache.org). Join by
 emailing
 [`dev-subscribe@beam.apache.org`](mailto:dev-subscribe@beam.apache.org).
+Anyone is welcome to join, and we'd love to hear what you're interested in.
 
 If interested, you can also join the other [mailing lists]({{ site.baseurl
 }}/get-started/support/).
@@ -74,9 +75,7 @@ If interested, you can also join the other [mailing lists]({{ site.baseurl
 
 We use the Apache Software Foundation's
 [JIRA](https://issues.apache.org/jira/browse/BEAM) as an issue tracking and
-project management tool, as well as a way to communicate among a very diverse
-and distributed set of contributors. To avoid duplicated efforts,
-significant Beam-related work should be tracked there.
+project management tool.
 
 If you do not already have an Apache JIRA account, sign up
 [here](https://issues.apache.org/jira/).
@@ -84,9 +83,7 @@ If you do not already have an Apache JIRA account, sign up
 If a quick
 [search](https://issues.apache.org/jira/issues/?jql=project%3DBEAM%20AND%20text%20~%20%22the%20thing%20I%20want%20to%20contribute%22)
 doesn’t turn up an existing JIRA issue for the work you want to contribute,
-feel free to create one. Please discuss your idea with a committer or the [component
-lead](https://issues.apache.org/jira/browse/BEAM/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel)
-in JIRA or, alternatively, on the developer mailing list.
+feel free to create one.
 
 If there’s an existing JIRA issue for your intended contribution, please
 comment about your intended work. A committer can
@@ -303,7 +300,7 @@ $ python setup.py sdist > /dev/null && \
 ## Review
 
 Once the initial code is complete and the tests pass, it’s time to start the
-code review process. We review and discuss all code, no matter who authors it.
+code review process. All code is peer reviewed, no matter who authors it.
 It’s a great way to build community, since you can learn from other developers,
 and they become familiar with your contribution. It also builds a strong
 project by encouraging a high quality bar and keeping code consistent

-- 
To stop receiving notification emails like this one, please contact
mergebot-role@apache.org.