doc: update repository boilerplate and README

Use the revised boilerplate frmo new empty repository:
	https://upspin.googlesource.com/empty

Change-Id: I83facca7bd0c9aea968c6ba1e4bad964c805f8cb
diff --git a/AUTHORS b/AUTHORS
index fef38b6..2c1c9c9 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -1,13 +1,3 @@
-# This is the official list of Upspin authors for copyright purposes.
-# This file is distinct from the CONTRIBUTORS files.
-# See the latter for an explanation.
-
-# Names should be added to this file as one of
-#     Organization's name
-#     Individual's name <submission email address>
-#     Individual's name <submission email address> <email2> <emailN>
-# See CONTRIBUTORS for the meaning of multiple email addresses.
-
-# Please keep the list sorted.
-
-Google Inc.
+# This source code refers to The Upspin Authors for copyright purposes.
+# The master list of authors is in the main Upspin distribution,
+# visible at https://upspin.googlesource.com/upspin/+/master/AUTHORS.
diff --git a/CONDUCT.md b/CONDUCT.md
new file mode 100644
index 0000000..bd83c7e
--- /dev/null
+++ b/CONDUCT.md
@@ -0,0 +1,75 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [upspin@googlegroups.com](mailto:upspin@googlegroups.com).
+All complaints will be reviewed and investigated and will result in a response
+that is deemed necessary and appropriate to the circumstances. The project team
+is obligated to maintain confidentiality with regard to the reporter of an
+incident. Further details of specific enforcement policies may be posted
+separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index cec73cc..f6ed4ee 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -15,17 +15,33 @@
 4. What did you expect to see?
 5. What did you see instead?
 
-Sensitive security-related issues should be reported to [upspin-security@googlegroups.com](mailto:upspin-security@googlegroups.com).
+Sensitive security-related issues should be reported to the private
+[upspin-security@googlegroups.com](mailto:upspin-security@googlegroups.com)
+mailing list.
+
 
 ## Contributing code
 
-Please read the [Contribution Guidelines](https://golang.org/doc/contribute.html)
-before sending patches.
-
-**We do not accept GitHub pull requests**
+We do not use GitHub pull requests
 (we use [an instance](https://upspin-review.googlesource.com/) of the
 [Gerrit](https://www.gerritcodereview.com/) code review system instead).
 
+Our code review process is the same as that used by the Go project.
+Please read the Code Review section of
+[Go's Contribution Guidelines](https://golang.org/doc/contribute.html#Code_review)
+to learn how to send patches to Upspin.
+That document covers registering with
+[our Gerrit instance]((https://upspin-review.googlesource.com/)),
+configuring the `git-codereview` tool,
+signing a Contributor License Agreement,
+and the process of creating, reviewing, and submitting changes.
+
 Unless otherwise noted, the Upspin source files are distributed under
 the BSD-style license found in the LICENSE file.
 
+
+## Code of Conduct
+
+Please note that this project is released with a [Contributor Code of Conduct](CONDUCT.md).
+By participating in this project you agree to abide by its terms.
+
diff --git a/CONTRIBUTORS b/CONTRIBUTORS
index 740310c..9722e67 100644
--- a/CONTRIBUTORS
+++ b/CONTRIBUTORS
@@ -1,39 +1,3 @@
-# This is the official list of people who can contribute
-# (and typically have contributed) code to the Upspin repository.
-# The AUTHORS file lists the copyright holders; this file
-# lists people.  For example, Google employees are listed here
-# but not in AUTHORS, because Google holds the copyright.
-#
-# The submission process automatically checks to make sure
-# that people submitting code are listed in this file (by email address).
-#
-# Names should be added to this file only after verifying that
-# the individual or the individual's organization has agreed to
-# the appropriate Contributor License Agreement, found here:
-#
-#     http://code.google.com/legal/individual-cla-v1.0.html
-#     http://code.google.com/legal/corporate-cla-v1.0.html
-#
-# The agreement for individuals can be filled out on the web.
-#
-# When adding J Random Contributor's name to this file,
-# either J's name or J's organization's name should be
-# added to the AUTHORS file, depending on whether the
-# individual or corporate CLA was used.
-
-# Names should be added to this file like so:
-#     Individual's name <submission email address>
-#     Individual's name <submission email address> <email2> <emailN>
-#
-# An entry with multiple email addresses specifies that the
-# first address should be used in the submit logs and
-# that the other addresses should be recognized as the
-# same person when interacting with Gerrit.
-
-# Please keep the list sorted.
-
-Andrew Gerrand <adg@golang.org>
-David Presotto <presotto@gmail.com>
-Eduardo Pinheiro <edpin@edpin.com>
-Eric Grosse <grosse@gmail.com>
-Rob Pike <r@golang.org>
+# This source code was written by the Upspin contributors.
+# The master list of contributors is in the main Upspin distribution,
+# visible at https://upspin.googlesource.com/upspin/+/master/CONTRIBUTORS.
diff --git a/README b/README
deleted file mode 100644
index 45640e5..0000000
--- a/README
+++ /dev/null
@@ -1,41 +0,0 @@
-To build a new APK:
-
-- Download and install Android Studio:
-https://developer.android.com/studio/index.html
-
-- Launch Android Studio (<installation_dir>/bin/studio.sh)
-
-- On the main screen, select Import Project (Eclipse, Gradle, etc)
-  + Select this project. You should see an Android Studio icon close to it.
-
-- Install an updated Android SDK from within Android Studio.
-  + Tools > Android > SDK Manager
-
-- Build go bindings for Android:
-  + cd $GOPATH/src/upspin.io/exp/client/gobind
-  + go generate
-
-- Import the .aar created in the step above:
-  + File > New > New Module > Import .JAR/.AAR Package
-  + Enter the path above, expanding the GOPATH var.
-  + It should find gobind.aar.
-  + Your project window now should have app and gobind.
-
-- Set gobind as a dependency:
-  + File > Project Structure
-  + Click on "app".
-  + Select the Dependencies tab.
-  + Click + on the top right margin.
-  + Select gobind.
-  + Click Ok.
-
-- Build the project
-  + Build > Rebuild project
-
-- Plug a phone in Developer Mode and launch the app:
-  + Run > Run (or click on the green "play" icon near menu item Run)
-
-- Follow configuration instructions on the phone.
-
-
-
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..8c90795
--- /dev/null
+++ b/README.md
@@ -0,0 +1,46 @@
+# Upspin `android` repository
+
+This repository contains experimental support for Upspin on Android.
+
+See the [master repository](https://github.com/upspin/upspin#readme) for more information.
+
+## Building
+
+To build a new APK:
+
+- Download and install Android Studio:
+https://developer.android.com/studio/index.html
+
+- Launch Android Studio (<installation_dir>/bin/studio.sh)
+
+- On the main screen, select Import Project (Eclipse, Gradle, etc)
+  - Select this project. You should see an Android Studio icon close to it.
+
+- Install an updated Android SDK from within Android Studio.
+  - Tools > Android > SDK Manager
+
+- Build go bindings for Android:
+  - cd $GOPATH/src/upspin.io/exp/client/gobind
+  - go generate
+
+- Import the .aar created in the step above:
+  - File > New > New Module > Import .JAR/.AAR Package
+  - Enter the path above, expanding the GOPATH var.
+  - It should find gobind.aar.
+  - Your project window now should have app and gobind.
+
+- Set gobind as a dependency:
+  - File > Project Structure
+  - Click on "app".
+  - Select the Dependencies tab.
+  - Click + on the top right margin.
+  - Select gobind.
+  - Click Ok.
+
+- Build the project
+  - Build > Rebuild project
+
+- Plug a phone in Developer Mode and launch the app:
+  - Run > Run (or click on the green "play" icon near menu item Run)
+
+- Follow configuration instructions on the phone.