update readme, add coc, add governane

Signed-off-by: Bassam Tabbara <bassam@upbound.io>

CODE_OF_CONDUCT.md

@@ -0,0 +1,3 @@
+## Community Code of Conduct
+
+This project follows the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).

CONTRIBUTING.md

@@ -88,9 +88,10 @@ questions: what changed and why. The subject line should feature the what and
 the body of the commit should describe the why.
 
 ```
-ceph: update MON to use rocksdb
+aws: add support for replication to RDS
 
-this enables us to remove leveldb from the codebase.
+this commit enables fail-over logic for RDS, across multiple zones. it
+enables setting up replication between databases across zones.
 ```
 
 The format can be described more formally as follows:

GOVERNANCE.md

@@ -0,0 +1,133 @@
+# Crossplane Governance
+
+This document defines governance policies for the Crossplane project.
+
+## Roles
+
+Crossplane uses a two-tiered system of maintainer roles:
+
+* Senior Maintainers
+  * Have the most experience with the Crossplane project and are expected to have the knowledge and insight to lead the project's growth and improvement
+  * Represent their organization within the Crossplane community
+  * Oversee the process for adding new maintainers and provides guidance for the standard maintainers
+  * Receive **two votes** in the [conflict resolution and voting process](#conflict-resolution-and-voting) described below
+* Standard Maintainers
+  * Have less experience with the Crossplane project than senior maintainers, but are also expected to provide significant value to the project, helping it grow and improve
+  * Receive **one vote** in the voting process
+
+## Becoming a maintainer
+
+The current list of maintainers is published and updated in [OWNERS.md](OWNERS.md).
+
+### Maintainer Pre-requisites
+
+To become a maintainer you need to demonstrate the following:
+
+* A strong commitment to the project
+  * Participate in design and technical discussions
+  * Contribute non-trivial pull requests
+  * Perform code reviews on other's pull requests
+  * Answer user questions and troubleshoot issues in the field
+* Ability to write good solid code
+* Ability to collaborate with the team
+* Understanding of how the team works (policies, processes for testing and code review, etc.)
+* Understanding of the project's code base and coding style
+
+### Your organization is not yet a maintainer
+
+* Express interest to the [senior maintainers](OWNERS.md#senior-maintainers) directly that your
+  organization is interested in becoming a maintainer. Becoming a maintainer generally means that
+  you are going to be spending substantial time (>25%) on Crossplane for the foreseeable future. You
+  should have domain expertise and be extremely proficient with Kubernetes and Golang.  Ultimately
+  your goal is to become a senior maintainer that will represent your organization.
+* You should likely have already been commenting on pull requests and issues with the intent of solving
+  user problems and improving the overall quality of the project.
+* We will expect you to start contributing increasingly complicated PRs, under the guidance
+  of the existing senior maintainers.
+* We may ask you to do some PRs from our backlog.
+* As you gain experience with the code base and our standards, we will ask you to do code reviews
+  for incoming PRs (i.e., all maintainers are expected to shoulder a proportional share of
+  community reviews).
+* After a period of approximately 2-3 months of working together and making sure we see eye to eye,
+  the existing senior maintainers will confer and decide whether to grant maintainer status or not.
+  We make no guarantees on the length of time this will take, but 2-3 months is the approximate
+  goal.
+
+### Your organization is currently a maintainer
+
+* First decide whether your organization really needs more people with maintainer access. Valid
+  reasons are "blast radius", a large organization that is working on multiple unrelated projects,
+  etc.
+* Contact a senior maintainer for your organization and express interest.
+* Start doing PRs and code reviews under the guidance of your senior maintainer.
+* After a period of 1-2 months the existing senior maintainers will discuss granting "standard"
+  maintainer access.
+* "Standard" maintainer access can be upgraded to "senior" maintainer access after another 1-2
+  months of work and another conference of the existing senior committers.
+
+## Removing a maintainer
+
+If a maintainer is no longer interested or cannot perform the maintainer duties listed above, they
+should volunteer to be moved to emeritus status. In extreme cases this can also occur by a vote of
+the maintainers per the voting process below.
+
+## Maintainer responsibilities
+
+* Monitor email aliases.
+* Monitor Slack (delayed response is perfectly acceptable).
+* Attend the regularly recurring [community meetings](README.md#community-meeting).
+* Triage GitHub issues and perform pull request reviews for other maintainers and the community.
+  The areas of specialization listed in [OWNERS.md](OWNERS.md) can be used to help with routing
+  an issue/question to the right person.
+* During GitHub issue triage, apply all applicable [labels](https://github.com/crossplaneio/crossplane/labels)
+  to each new issue. Labels are extremely useful for future issue follow up. Which labels to apply
+  is somewhat subjective so just use your best judgment. A few of the most important labels that are
+  not self explanatory are:
+  * **beginner**: Mark any issue that can reasonably be accomplished by a new contributor with
+    this label.
+  * **help wanted**: Unless it is immediately obvious that someone is going to work on an issue (and
+    if so assign it), mark it help wanted.
+  * **question**: If it's unclear if an issue is immediately actionable, mark it with the
+    question label. Questions are easy to search for and close out at a later time. Questions
+    can be promoted to other issue types once it's clear they are actionable (at which point the
+    question label should be removed).
+* Make sure that ongoing PRs are moving forward at the right pace or closing them.
+* In general continue to be willing to spend at least 25% of ones time working on Crossplane (~1.25
+  business days per week).
+
+### Approving PRs
+
+PRs may be merged after receiving at least **1 approval from a maintainer** (either senior or standard)
+that is **not the author** of the PR, and preferably from a **different organization** than the PR author.
+As complexity of a PR increases, such as design changes or major PRs, the need for an approval from
+a different organization also increases.  This should be a judgement call from the maintainers,
+and it is expected that all maintainers act in good faith to seek approval from a different
+organization when appropriate.
+
+### Github Project Administration
+
+Maintainers will be added to the Crossplane GitHub organization (if they are not already) and added to
+the GitHub Maintainers team.
+
+After 6 months, **senior** maintainers will be made an "owner" of the Crossplane GitHub organization.
+
+## Conflict resolution and voting
+
+As previously mentioned, senior maintainers receive **2 votes** each and standard maintainers
+receive 1 vote each.
+
+In general, we prefer that technical issues and maintainer membership are amicably worked out
+between the persons involved. If a dispute cannot be decided independently, the maintainers can be
+called in to decide an issue. If the maintainers themselves cannot decide an issue, the issue will
+be resolved by voting. The voting process is a simple majority (except for maintainer changes,
+which require 2/3 majority as described below) in which each senior maintainer receives two votes
+and each standard maintainer receives one vote.
+
+For formal votes, a specific statement of what is being voted on should be added to the relevant
+GitHub issue or PR. Maintainers should indicate their yes/no vote on that issue or PR, and after a
+suitable period of time (goal is by 5 business days), the votes will be tallied and the outcome
+noted. If any maintainers are unreachable during the voting period, postponing the completion of
+the voting process should be considered.
+
+Additions and removals of maintainers require a **2/3 majority**, while other decisions and changes
+require only a simple majority.

INSTALL.md

@@ -1,7 +1,6 @@
 # Building and Installing Crossplane
 
-Crossplane is composed of golang project and can be built directly with standard `golang` tools. We currently support
-two different platforms for building:
+Crossplane is composed of golang project and can be built directly with standard `golang` tools. We currently support two different platforms for building:
 
   * Linux: most modern distros should work although most testing has been done on Ubuntu
   * Mac: macOS 10.6+ is supported
@@ -28,8 +27,7 @@ First ensure that you have the build submodule synced and updated:
 git submodule sync && git submodule update --init --recursive
 ```
 
-You can then build the Crossplane binaries and all container images for the host platform by simply running the
-command below. Building in parallel with the `-j` option is recommended.
+You can then build the Crossplane binaries and all container images for the host platform by simply running the command below. Building in parallel with the `-j` option is recommended.
 
 ```
 make -j4
@@ -45,13 +43,11 @@ Official Crossplane builds are done inside a build container. This ensures that
 > build/run make -j4
 ```
 
-The first run of `build/run` will build the container itself and could take a few
-minutes to complete.
+The first run of `build/run` will build the container itself and could take a few minutes to complete, but subsequent builds should go much faster.
 
 ### Resetting the build container
 
-If you're running the build container on the Mac using Docker for Mac, the build
-container will rely on rsync to copy source to and from the host. To reset the build container and it's persistent volumes, you can run the below command. You should not have to do this often unless something is broken or stale with your build container:
+If you're running the build container on macOS using Docker for Mac, the build container will rely on rsync to copy source to and from the host. To reset the build container and it's persistent volumes, you can run the below command. You should not have to do this often unless something is broken or stale with your build container:
 
 ```
 build/reset
@@ -130,13 +126,13 @@ systemctl enable update-binfmt.service
 # Install
 
 ## Local
-Please refer to [Local Build & Install](/cluster/local/README.md) documentation on how to deploy locally built Crossplane image onto Kubernetes cluster running on Minikube 
+Please refer to [Local Build & Install](/cluster/local/README.md) documentation on how to deploy locally built Crossplane image onto Kubernetes cluster running on minikube or using docker for mac.
 
 # Improving Build Speed
 
 ## Image Caching and Pruning
 
-Doing a complete build of Crossplane and the dependent packages can take a long time (more than an hour on a typical macbook). To speed things up we rely heavily on image caching in docker. Docker support content-addressable images by default and we use that effectively when building images. Images are factored to increase reusability across builds. We also tag and timestamp images that should remain in the cache to help future builds.
+Doing a complete build of Crossplane and the dependent packages can take a long time. To speed things up we rely heavily on image caching in docker. Docker support content-addressable images by default and we use that effectively when building images. Images are factored to increase reusability across builds. We also tag and timestamp images that should remain in the cache to help future builds.
 
 ### Pruning the cache
 
@@ -146,8 +142,12 @@ To prune the number of cached images run `make prune`. There are two options tha
 - `PRUNE_KEEP` - the minimum number of cached images to keep in the cache. Default is 24 images.
 
 ## CI workflow and options
-Every PR and every merge to master triggers the CI process in [TBD](http://TBD).
-The Jenkins CI will build, run unit tests, run integration tests and Publish artifacts- On every commit to PR and master.
-If any of the CI stages fail, then the process is aborted and no artifacts are published.
-On every successful build Artifacts are pushed to a [s3 bucket](https://release.crossplane.io/). On every successful master build,
-images are uploaded to docker hub in addition.
+
+Every PR and every merge to master triggers the CI process in [Jenkins](https://jenkinsci.upbound.io/blue).
+The Jenkins CI will build, run unit tests, run integration tests and Publish artifacts- On every commit to PR and master. If any of the CI stages fail, then the process is aborted and no artifacts are published.
+
+On every successful build Artifacts are pushed to a [s3 bucket](https://releases.crossplane.io/). On every successful master build, images are uploaded to docker hub in addition.
+
+Based on nature of the PR, it may not be required to run full regression or users may want to skip build all together for trivial changes like documentation changes. Based on the PR body text, Jenkins will skip the build or skip some tests:
+
+  * [skip ci] - if this text is found in the body of PR, then Jenkins will skip the build process and accept the commit

OWNERS.md

@@ -0,0 +1,31 @@
+# Crossplane Maintainers
+
+This page lists all active maintainers and their areas of expertise. This can be used for routing PRs, questions, etc. to the right place.
+
+* See [CONTRIBUTING.md](CONTRIBUTING.md) for general contribution guidelines.
+* See [GOVERNANCE.md](GOVERNANCE.md) for governance guidelines and maintainer responsibilities.
+
+## Senior maintainers
+
+Here's the current list of senior maintainers:
+
+* Bassam Tabbara <bassam@upbound.io> ([bassam](https://github.com/bassam))
+  * Catch-all, architecture, strategy, build and packaging
+* Illya Chekrygin <illya@upbound.io> ([ichekrygin](https://github.com/ichekrygin))
+  * Core, Controllers, GCP, AWS, Azure
+* Jared Watts <jared@upbound.io> ([jbw976](https://github.com/jbw976))
+  * Core, Controllers, GCP, AWS, Azure
+
+## Maintainers
+
+There are currently no maintainers. Maintainers will be added according to the [process for adding a maintainer](GOVERNANCE.md#becoming-a-maintainer) in the [governance](GOVERNANCE.md).
+
+## Emeritus maintainers
+
+There are currently no emeritus maintainers.  This list will be updated according to the [process for removing a maintainer](GOVERNANCE.md#removing-a-maintainer) in the [governance](GOVERNANCE.md).
+
+## Friends of Crossplane
+
+This section lists people that are not currently maintainers but have demonstrated value to the community.
+They typically help out with technical, code and design reviews and also with support and troubleshooting.
+Feel free to loop them in as needed.