You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by fr...@apache.org on 2016/10/19 04:06:34 UTC
[5/8] incubator-beam-site git commit: Updated Contribution Guide &
added Work In Progress * Added section on feature branches. * Revamped
website section. * Standardized code formatting. * Added a "work in progress"
page to help make new and ongoing work
Updated Contribution Guide & added Work In Progress
* Added section on feature branches.
* Revamped website section.
* Standardized code formatting.
* Added a "work in progress" page to help make new and ongoing work more visible to the community.
Project: http://git-wip-us.apache.org/repos/asf/incubator-beam-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-beam-site/commit/c765b7ed
Tree: http://git-wip-us.apache.org/repos/asf/incubator-beam-site/tree/c765b7ed
Diff: http://git-wip-us.apache.org/repos/asf/incubator-beam-site/diff/c765b7ed
Branch: refs/heads/asf-site
Commit: c765b7edfcee3044ed21517a244b74ea8d8eded9
Parents: 229020c
Author: Frances Perry <fj...@google.com>
Authored: Mon Oct 3 20:57:24 2016 -0700
Committer: Frances Perry <fj...@google.com>
Committed: Tue Oct 18 21:03:25 2016 -0700
----------------------------------------------------------------------
README.md | 1 -
_includes/header.html | 3 +-
contribute/contribution-guide.md | 166 ++++++++++++++++++++++++----------
contribute/work-in-progress.md | 32 +++++++
4 files changed, 150 insertions(+), 52 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/c765b7ed/README.md
----------------------------------------------------------------------
diff --git a/README.md b/README.md
index 80819e2..40172ac 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,3 @@
-
# Apache Beam (incubating) website
This is the website for [Apache Beam](http://beam.incubator.apache.org)
http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/c765b7ed/_includes/header.html
----------------------------------------------------------------------
diff --git a/_includes/header.html b/_includes/header.html
index 67631a9..99d59eb 100644
--- a/_includes/header.html
+++ b/_includes/header.html
@@ -63,11 +63,12 @@
<li role="separator" class="divider"></li>
<li class="dropdown-header">Basics</li>
<li><a href="{{ site.baseurl }}/contribute/contribution-guide/">Contribution Guide</a></li>
+ <li><a href="{{ site.baseurl }}/contribute/work-in-progress/">Work In Progress</a></li>
<li><a href="{{ site.baseurl }}/use/mailing-lists/">Mailing Lists</a></li>
<li><a href="{{ site.baseurl }}/contribute/source-repository/">Source Repository</a></li>
<li><a href="{{ site.baseurl }}/use/issue-tracking/">Issue Tracking</a></li>
<li role="separator" class="divider"></li>
- <li class="dropdown-header">Technical References</list>
+ <li class="dropdown-header">Technical References</li>
<li><a href="{{ site.baseurl }}/contribute/testing/">Testing</a></li>
<li><a href="{{ site.baseurl }}/contribute/design-principles/">Design Principles</a></li>
<li><a href="https://goo.gl/nk5OM0">Technical Vision</a></li>
http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/c765b7ed/contribute/contribution-guide.md
----------------------------------------------------------------------
diff --git a/contribute/contribution-guide.md b/contribute/contribution-guide.md
index a0dcb50..61c762b 100644
--- a/contribute/contribution-guide.md
+++ b/contribute/contribution-guide.md
@@ -18,7 +18,7 @@ We use a review-then-commit workflow in Beam for all contributions.
**For larger contributions or those that affect multiple components:**
-1. **Engage**: We encourage you to work with the Beam community on the [Apache JIRA issue tracker](https://issues.apache.org/jira/browse/BEAM) and [developer\u2019s mailing list](http://beam.incubator.apache.org/mailing_lists/) to identify good areas for contribution.
+1. **Engage**: We encourage you to work with the Beam community on the [Apache JIRA issue tracker](https://issues.apache.org/jira/browse/BEAM) and [developer\u2019s mailing list](http://beam.incubator.apache.org/use/mailing-lists/) to identify good areas for contribution.
1. **Design:** More complicated contributions will likely benefit from some early discussion in order to scope and design them well.
**For all contributions:**
@@ -32,27 +32,28 @@ We look forward to working with you!
## Engage
### Mailing list(s)
-We discuss design and implementation issues on dev@beam.incubator.apache.org mailing list, which is archived [here](http://mail-archives.apache.org/mod_mbox/incubator-beam-dev/). Join by emailing [`dev-subscribe@beam.incubator.apache.org`](mailto:dev-subscribe@beam.incubator.apache.org).
+We discuss design and implementation issues on dev@beam.incubator.apache.org mailing list, which is archived [here](https://lists.apache.org/list.html?dev@beam.apache.org). Join by emailing [`dev-subscribe@beam.incubator.apache.org`](mailto:dev-subscribe@beam.incubator.apache.org).
-If interested, you can also join [`user@beam.incubator.apache.org`](http://mail-archives.apache.org/mod_mbox/incubator-beam-user/) and [`commits@beam.incubator.apache.org`](http://mail-archives.apache.org/mod_mbox/incubator-beam-commits/) too.
+If interested, you can also join the other [mailing lists](http://beam.incubator.apache.org/use/mailing-lists/) too.
### Apache JIRA
We use [Apache 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 be able to gather feedback, avoid frustration, and avoid duplicated efforts all Beam-related work should be tracked there.
If you do not already have an Apache JIRA account, sign up [here](https://issues.apache.org/jira/).
-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\u2019t turn up an existing JIRA issue for the work you want to contribute, create it. Please discuss your proposal 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.
+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\u2019t turn up an existing JIRA issue for the work you want to contribute, create it. 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.
If there\u2019s an existing JIRA issue for your intended contribution, please comment about your intended work. Once the work is understood, a committer will assign the issue to you. (If you don\u2019t have a JIRA role yet, you\u2019ll be added to the \u201ccontributor\u201d role.) If an issue is currently assigned, please check with the current assignee before reassigning.
-For moderate or large contributions, you should not start coding or writing a design doc unless there is a corresponding JIRA issue assigned to you for that work. Simple changes, like fixing typos, do not require an associated issue.
+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.
## 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.
Generally, the JIRA issue is the best place to gather relevant design docs, comments, or references. It\u2019s great to explicitly include relevant stakeholders early in the conversation. For designs that may be generally interesting, we also encourage conversations on the developer\u2019s mailing list.
-We suggest using [Google Docs](https://docs.google.com/) for sharing designs that may benefit from diagrams or comments. Please remember to make the document world-commentable and add a link to it from the relevant JIRA issue. We also track Beam-related documents in [this shared folder](https://drive.google.com/folderview?id=0B-IhJZh9Ab52OFBVZHpsNjc4eXc&usp=sharing).
+We suggest using [Google Docs](https://docs.google.com/) for sharing designs that may benefit from diagrams or comments. Please remember to make the document world-commentable and add a link to it from the relevant JIRA issue. You may want to start from this [template](https://docs.google.com/document/d/1qYQPGtabN5-E4MjHsecqqC7PXvJtXvZukPfLXQ8rHJs/edit?usp=sharing).
## Code
To contribute code to Apache Beam, you\u2019ll have to do a few administrative steps once, and then follow a few guidelines for each contribution.
@@ -86,15 +87,15 @@ Clone Beam\u2019s read-only GitHub mirror.
Add your forked repository as an additional Git remote, where you\u2019ll push your changes.
-<pre><code>$ git remote add <b><GitHub_user></b> git@github.com:<b><GitHub_user></b>/incubator-beam.git</code></pre>
+ $ git remote add <GitHub_user> git@github.com:<GitHub_user>/incubator-beam.git
You are now ready to start developing!
### Create a branch in your fork
You\u2019ll work on your contribution in a branch in your own (forked) repository. Create a local branch, initialized with the state of the branch you expect your changes to be merged into. Keep in mind that we use several branches, including `master`, feature-specific, and release-specific branches. If you are unsure, initialize with the state of the `master` branch.
-<pre><code>$ git fetch --all
-$ git checkout -b <b><my-branch></b> origin/master</code></pre>
+ $ git fetch --all
+ $ git checkout -b <my-branch> origin/master
At this point, you can start making and committing changes to this branch in a standard way.
@@ -107,7 +108,7 @@ Remember to always use `--rebase` parameter to avoid extraneous merge commits.
To push your local, committed changes to your (forked) repository on GitHub, run:
-<pre><code>$ git push <b><GitHub_user> <my-branch></b></code></pre>
+ $ git push <GitHub_user> <my-branch>
### Testing
All code should have appropriate unit testing coverage. New code should have new tests in the same contribution. Bug fixes should include a regression test to prevent the issue from reoccurring.
@@ -126,15 +127,15 @@ Organize your commits to make your reviewer\u2019s job easier. Use the following co
Navigate to the [Beam GitHub mirror](https://github.com/apache/incubator-beam) to create a pull request. The title of the pull request should be strictly in the following format:
-<pre><code>[BEAM-<b><JIRA-issue-#></b>] Title of the pull request</code></pre>
+ [BEAM-<JIRA-issue-#>] <Title of the pull request>
Please include a descriptive pull request message to help make the reviewer\u2019s job easier. It\u2019s fine to refer to existing design docs or the contents of the associated JIRA as appropriate.
If you know a good committer to review your pull request, please make a comment like the following. If not, don\u2019t worry -- a committer will pick it up.
-<pre><code>Hi @<b><GitHub-reviewer-username></b>, can you please take a look?</code></pre>
+ Hi @<GitHub-reviewer-username>, can you please take a look?
-When choosing a reviewer, think about who is the expert on the relevant code, who the stakeholders are for this change, and who else would benefit from becoming familiar with the code. If you\u2019d appreciate comments from additional folks but already have a main reviewer, you can explicitly cc them using <code>@<b><GitHub-reviewer-username></b></code>.
+When choosing a reviewer, think about who is the expert on the relevant code, who the stakeholders are for this change, and who else would benefit from becoming familiar with the code. If you\u2019d appreciate comments from additional folks but already have a main reviewer, you can explicitly cc them using `@<GitHub-reviewer-username>`.
### Code Review and Revision
During the code review process, don\u2019t rebase your branch or otherwise modify published commits, since this can remove existing comment history and be confusing to the reviewer. When you make a revision, always push it in a new commit.
@@ -153,9 +154,9 @@ Once the pull request is merged into the Beam repository, you can safely delete
From another local branch, run:
-<pre><code>$ git fetch --all
-$ git branch -d <b><my-branch></b>
-$ git push <b><GitHub_user></b> --delete <b><my-branch></b></code></pre>
+ $ git fetch --all
+ $ git branch -d <my-branch>
+ $ git push <GitHub_user> --delete <my-branch>
## Commit (committers only)
Once the code has been peer reviewed by a committer, the next step is for the committer to merge it into the [authoritative Apache repository](https://git-wip-us.apache.org/repos/asf/incubator-beam.git), not the read-only GitHub mirror. (In the case that the author is also a committer, it is acceptable for either the author or reviewer to do the merge. Just be explicit about whose job it is!)
@@ -182,13 +183,13 @@ For the `github` remote, add an additional fetch reference, which will cause eve
You can confirm your configuration by running the following command.
-<pre><code>$ git remote -v
-apache https://git-wip-us.apache.org/repos/asf/incubator-beam.git (fetch)
-apache https://git-wip-us.apache.org/repos/asf/incubator-beam.git (push)
-github https://github.com/apache/incubator-beam.git (fetch)
-github https://github.com/apache/incubator-beam.git (push)
-<b><username></b> git@github.com:<b><username></b>/beam.git (fetch)
-<b><username></b> git@github.com:<b><username></b>/beam.git (push)</code></pre>
+ $ git remote -v
+ apache https://git-wip-us.apache.org/repos/asf/incubator-beam.git (fetch)
+ apache https://git-wip-us.apache.org/repos/asf/incubator-beam.git (push)
+ github https://github.com/apache/incubator-beam.git (fetch)
+ github https://github.com/apache/incubator-beam.git (push)
+ <username> git@github.com:<username>/beam.git (fetch)
+ <username> git@github.com:<username>/beam.git (push)
### Contributor License Agreement
If you are merging a larger contribution, please make sure that the contributor has an ICLA on file with the Apache Secretary. You can view the list of committers [here](http://home.apache.org/phonebook.html?unix=committers), as well as [ICLA-signers who aren\u2019t yet committers](http://home.apache.org/unlistedclas.html).
@@ -203,9 +204,8 @@ At some point in the review process, you should take the pull request over and c
Fetch references from all remote repositories, and checkout the specific pull request branch.
-<pre>
-</code>$ git fetch --all
-$ git checkout -b finish-pr-<b><pull-request-#></b> github/pr/<b><pull-request-#></b></code></pre>
+ $ git fetch --all
+ $ git checkout -b finish-pr-<pull-request-#> github/pr/<pull-request-#>
At this point, you can commit any final touches to the pull request. For example, you should:
@@ -222,43 +222,109 @@ Please make sure to retain authorship of original commits to give proper credit
### Merge process
Once you are ready to merge, fetch all remotes, checkout the destination branch and merge the changes.
-<pre><code>$ git fetch --all
-$ git checkout apache/master
-$ git merge --no-ff \
- -m $'[BEAM-<b><JIRA-issue-#></b>] <b><Title></b>\n\nThis closes #<b><pull-request-#></b>' \
- finish-pr-<b><pull-request-#></b></code></pre>
+ $ git fetch --all
+ $ git checkout apache/master
+ $ git merge --no-ff \
+ -m $'[BEAM-<JIRA-issue-#&>;</b>] <Title>\n\nThis closes #<pull-request-#>' \
+ finish-pr-<pull-request-#>
-Always use `--no-ff` option and the specific commit message "This closes #<b><pull request #></b>"" -- it ensures proper marking in the tooling. It would be nice to include additional information in the merge commit message, such as the title and summary of the pull request.
+Always use `--no-ff` option and the specific commit message "This closes #<pull request #>"" -- it ensures proper marking in the tooling. It would be nice to include additional information in the merge commit message, such as the title and summary of the pull request.
At this point, you want to ensure everything is right. Test it with `mvn verify`. Run `gitk` or `git log --graph,` etc. When you are happy with how it looks, push it. This is the point of no return -- proceed with caution.
$ git push apache HEAD:master
-Done. You can delete the local <code>finish-pr-<b><pull-request-#></b></code> branch if you like.
+Done. You can delete the local <code>finish-pr-<pull-request-#></code> branch if you like.
+
+## Special Cases
+
+The directions above assume you are submitting code to the `incubator-beam` repository's `master` branch. In addition, there are a few other locations where code is maintained. Generally these follow the same *engage*-*design*-**code**-**review**-**commit** process as above, with some minor adjustments to commands.
+
+### Feature Branches
+
+Some larger features are developed on a feature branch before being merged into `master`. In particular, this is often used for initial development of new components like SDKs or runners.
+
+#### Developing
+
+To contribute code on a feature branch, use the same process as above, but replace `master` with the [name of the branch](/contribute/work-in-progress/#feature-branches).
+
+In additional, you'll want to frequently merge in changes from `master` in order to prevent life on the branch from deviating too far from reality.
+
+Since feature branches are often used for new components, you may find that there is no [committer](/project/team/) familiar with all the details of the new language or runner. In that case, consider asking someone else familiar with the technology to do an initial review before looping in a committer for a final review and merge.
+
+#### Merging into Master
+
+In order for a feature branch to be merged into `master`, new components and major features should aim to meet the following guidelines.
+
+1. Have at least 2 contributors interested in maintaining it, and 1 committer interested in supporting it
+1. Provide both end-user and developer-facing documentation
+1. Have at least a basic level of unit test coverage
+1. Run all existing applicable integration tests with other Beam components and create additional tests as appropriate
+
+Additionally, ...
+
+A new runner should:
+
+1. Be able to handle a subset of the model that address a significant set of use cases (aka. \u2018traditional batch\u2019 or \u2018processing time streaming\u2019)
+1. Update the capability matrix with the current status
+1. Add a webpage under `learn/runners`
+
+A new SDK should:
+
+1. Provide the ability to construct graphs with all the basic building blocks of the model (ParDo, GroupByKey, Window, Trigger, etc)
+1. Begin fleshing out the common composite transforms (Count, Join, etc) and IO connectors (Text, Kafka, etc)
+1. Have at least one runner that can execute the complete model (may be a direct runner)
+1. Provide integration tests for executing against current and future runners
+1. Add a webpage under `learn/sdks`
-## Additional Projects
### Website
-We use the same general review-then-commit process for changes to the Beam website, which uses [this GitHub Mirror](https://github.com/apache/incubator-beam-site). The website uses the [Jekyll](http://jekyllrb.com) framework to make website development easier. The [README file](https://github.com/apache/incubator-beam-site/blob/asf-site/README.md) in the website repository has more information on how to:
-* Install Jekyll
-* Make changes to the website
-* Test your changes
+The Beam website is in the [Beam Site GitHub mirror](https://github.com/apache/incubator-beam-site) repository in the `asf-site` branch (_not_ `master`).
+
+The repository contains:
+
+1. `_<directory>`: the infrastructure for building, testing, and styling the website
+1. `_posts`: blog post entries
+2. `use/`, `learn/`, and `contribute/`: markdown files containing the bulk of the content
+3. `content/`: html generated from the markdown by jekyll (which is what is actually hosted on the website)
+
+Issues are tracked in the [website](https://issues.apache.org/jira/browse/BEAM/component/12328906) component in JIRA.
+
+#### One-time Setup
+
+The website uses [Jekyll](http://jekyllrb.com), a ruby-based development framework. The [README file](https://github.com/apache/incubator-beam-site/blob/asf-site/README.md) in the website repository has more information on how to set up the required dependencies for your development environment.
+
+The general guidelines for cloning a repository can be adjusted to use the `asf-site` branch of `incubator-beam-site`:
+
+ $ git clone -b asf-site https://github.com/apache/incubator-beam-site.git
+ $ cd incubator-beam-site
+ $ git remote add <GitHub_user> git@github.com:<GitHub_user>/incubator-beam-site.git
+ $ git fetch --all
+ $ git checkout -b <my-branch> origin/asf-site
+
+#### Working on your change
+
+While you are working on your pull request, you can test and develop live by running the following command in the root folder of the website:
+
+ $ jekyll serve
+
+Jekyll will start a webserver on port 4000. As you make changes to the content, Jekyll will rebuild it automatically.
+
+In addition, you can run the tests to valid your links using:
+
+ $ rake test
+
+Both of these commands will cause the `content/` directory to be generated. Merging autogenerated content can get tricky, so please leave this directory out of your commits and pull request by doing:
+
+ $ git checkout -- content
-#### Editing the website
-You can checkout the website repository with the following commands. This will allow you to edit the website in a local environment provided you have installed [Jekyll](http://jekyllrb.com) and understand how to use it.
+When you are ready, submit a pull request using the [Beam Site GitHub mirror](https://github.com/apache/incubator-beam-site), including the JIRA issue as usual.
-<pre><code>git clone -b asf-site https://github.com/apache/incubator-beam-site.git
-cd incubator-beam-site
-git remote add <b><GitHub_user></b> git@github.com:<b><GitHub_user></b>/incubator-beam-site.git
-git fetch --all
-git checkout -b <b><my-branch></b> origin/asf-site</code></pre>
+During review, committers will patch in your PR, generate the static `content/`, and review the changes.
#### Committing website changes
-Committers can commit website changes with the following commands. **Changes to the website must follow the same process outlined above** for changes to the Apache Beam code base.
+Follow the same committer process as above, but using `incubator-beam-site` and `asf-site`.
-<pre><code>git remote add apache https://git-wip-us.apache.org/repos/asf/incubator-beam-site.git
-git remote rename origin github
-git config --local --add remote.github.fetch \
- '+refs/pull/*/head:refs/remotes/github/pr/*'</code></pre>
+In addition, the committer is responsible for doing the final `jekyll build` to generate the static content, so follow the instructions above to install jekyll.
http://git-wip-us.apache.org/repos/asf/incubator-beam-site/blob/c765b7ed/contribute/work-in-progress.md
----------------------------------------------------------------------
diff --git a/contribute/work-in-progress.md b/contribute/work-in-progress.md
new file mode 100644
index 0000000..d1b6361
--- /dev/null
+++ b/contribute/work-in-progress.md
@@ -0,0 +1,32 @@
+---
+layout: default
+title: 'In Progress Work in Beam'
+permalink: /contribute/work-in-progress/
+---
+
+# Work In Progress in the Apache Beam Project
+
+As mentioned in the [Contribution Guide](/contribute/contribution-guide/), all work in Beam is tracked in our [Apache JIRA](https://issues.apache.org/jira/browse/BEAM). In addition, the following types of work may be of particular interest to the Beam community.
+
+* TOC
+{:toc}
+
+
+## Starter Tasks
+
+The community regular tags good getting started tasks with the label `starter`. Use a quick [JIRA search](https://issues.apache.org/jira/issues?jql=project%20%3D%20BEAM%20AND%20status%20%3D%20Open%20AND%20labels%20%3D%20starter) to identify ways you can get started [contributing](/contribute/contribution-guide/) to Beam.
+
+## Feature Branches
+
+Larger features with multiple active developers may be developed on a [feature branch](/contribute/contribution-guide/#feature-branches) before being merged in the master branch. In particular, this is often used for initial development of new components like SDKs or runners.
+
+Current branches include:
+
+| Feature | Branch | JIRA Component | More Info |
+| ---- | ---- | ---- | ---- |
+| Apache Apex Runner | [apex-runner](https://github.com/apache/incubator-beam/tree/apex-runner) | [runner-apex](https://issues.apache.org/jira/browse/BEAM/component/12331007) | - |
+| Apache Gearpump Runner | [gearpump-runner](https://github.com/apache/incubator-beam/tree/gearpump-runner) | [runner-gearpump](https://issues.apache.org/jira/browse/BEAM/component/12330829) | [README](https://github.com/apache/incubator-beam/blob/gearpump-runner/runners/gearpump/README.md) |
+| Python SDK | [python-sdk](https://github.com/apache/incubator-beam/tree/python-sdk) | [sdk-py](https://issues.apache.org/jira/browse/BEAM/component/12328910) | [README](https://github.com/apache/incubator-beam/blob/python-sdk/sdks/python/README.md) |
+| Apache Spark 2.0 Runner | [runners-spark2](https://github.com/apache/incubator-beam/tree/runners-spark2) | - | [thread](https://lists.apache.org/thread.html/e38ac4e4914a6cb1b865b1f32a6ca06c2be28ea4aa0f6b18393de66f@%3Cdev.beam.apache.org%3E) |
+{:.table}
+