Merge pull request #1646 from castrojo/community-expectations

Moving and revising community expectations

2 files changed, 69 insertions, 10 deletions

diff --git a/contributors/guide/README.md b/contributors/guide/README.md
index a66c3aa0..341e9fca 100644
--- a/contributors/guide/README.md
+++ b/contributors/guide/README.md
@@ -43,24 +43,21 @@ Welcome to Kubernetes! This document is the single source of truth for how to co
 
 Before you can contribute, you will need to sign the [Contributor License Agreement](/CLA.md).
 
-## Setting up your development environment
+## Code of Conduct
+
+Please make sure to read and observe our [Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
 
-If you haven’t set up your environment, please find resources [here](/contributors/devel). These resources are not well organized currently; please have patience as we are working on it.
+## Setting up your development environment
 
+If you haven’t set up your environment, please find resources [here](/contributors/devel).
 
 ## Community Expectations
 
 Kubernetes is a community project. Consequently, it is wholly dependent on its community to provide a productive, friendly and collaborative environment.
 
-The first and foremost goal of the Kubernetes community to develop orchestration technology that radically simplifies the process of creating reliable distributed systems. However a second, equally important goal is the creation of a community that fosters easy, agile development of such orchestration systems.
-
-We therefore describe the expectations for members of the Kubernetes community. This document is intended to be a living one that evolves as the community evolves via the same pull request and code review process that shapes the rest of the project. It currently covers the expectations of conduct that govern all members of the community as well as the expectations around code review that govern all active contributors to Kubernetes.
-
-### Code of Conduct
-
-Please make sure to read and observe our [Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md)
+Read and review the [Community Expectations](/community-expectations.md) for an understand of code and review expectations. 
 
-### Thanks
+## Thanks
 
 Many thanks in advance to everyone who contributes their time and effort to making Kubernetes both a successful system as well as a successful community. The strength of our software shines in the strengths of each individual community member. Thanks!
 
diff --git a/contributors/guide/community-expectations.md b/contributors/guide/community-expectations.md
new file mode 100644
index 00000000..fa4f951f
--- /dev/null
+++ b/contributors/guide/community-expectations.md
@@ -0,0 +1,62 @@
+# Community Expectations
+
+Kubernetes is a community project. Consequently, it is wholly dependent on
+its community to provide a productive, friendly and collaborative environment.
+
+The first and foremost goal of the Kubernetes community to develop orchestration
+technology that radically simplifies the process of creating reliable
+distributed systems. However a second, equally important goal is the creation
+of a community that fosters easy, agile development of such orchestration
+systems.
+
+We therefore describe the expectations for
+members of the Kubernetes community.  This document is intended to be a living one
+that evolves as the community evolves via the same PR and code review process
+that shapes the rest of the project.  It currently covers the expectations
+of conduct that govern all members of the community as well as the expectations
+around code review that govern all active contributors to Kubernetes.
+
+## Code review
+
+As a community we believe in the value of code review for all contributions.
+Code review increases both the quality and readability of our codebase, which
+in turn produces high quality software.
+
+See the [pull request documentation](/contributors/devel/pull-requests.md) for more information
+on code review.
+
+Consequently, as a community we expect that all active participants in the
+community will also be active reviewers. The 
+[community membership](/community-membership.md) outlines the responsibilities
+of the different contributor roles. 
+
+Expect reviewers to request that you avoid [common go style
+mistakes](https://github.com/golang/go/wiki/CodeReviewComments) in your PRs.
+
+## Expectations of reviewers: Review comments
+
+Because reviewers are often the first points of contact between new members of
+the community and can significantly impact the first impression of the
+Kubernetes community, reviewers are especially important in shaping the
+Kubernetes community.  Reviewers are highly encouraged to review the
+[code of conduct](/governance.md#code-of-conduct) and are strongly 
+encouraged to go above and beyond the code of conduct to promote a collaborative, 
+respectful Kubernetes community.
+
+## Expectations of reviewers: Review latency
+
+Reviewers are expected to respond in a timely fashion to PRs that are assigned
+to them.  Reviewers are expected to respond to an *active* PRs with reasonable
+latency, and if reviewers fail to respond, those PRs may be assigned to other
+reviewers.
+
+*Active* PRs are considered those which have a proper CLA (`cla:yes`) label
+and do not need rebase to be merged.  PRs that do not have a proper CLA, or
+require a rebase are not considered active PRs.
+
+## Thanks
+
+Many thanks in advance to everyone who contributes their time and effort to
+making Kubernetes both a successful system as well as a successful community.
+The strength of our software shines in the strengths of each individual
+community member.  Thanks!