From e6317e681f2fe93482937203f89a0123641c44d6 Mon Sep 17 00:00:00 2001
From: Sam Ritchie <samritchie@google.com>
Date: Mon, 10 Aug 2020 09:46:21 -0400
Subject: [PATCH] add contributor info

---
 COMMITTERS.md   | 15 +++++++++++++++
 CONTRIBUTING.md | 29 +++++++++++++++++++++++++++--
 README.md       | 28 +++++++++++++++++++++++++---
 3 files changed, 67 insertions(+), 5 deletions(-)
 create mode 100644 COMMITTERS.md

diff --git a/COMMITTERS.md b/COMMITTERS.md
new file mode 100644
index 0000000..7eec27b
--- /dev/null
+++ b/COMMITTERS.md
@@ -0,0 +1,15 @@
+# Committers
+
+These are the folks who can +1 a pull request and approve it for merge.
+
+## Active
+
+| Name            | Handle                                               |
+|-----------------|------------------------------------------------------|
+| Sam Ritchie     | [@isnotinvain](https://github.com/sritchie)          |
+| Ambrose Slone   | [@ajslone](https://github.com/ajslone)               |
+| Guy Gur-Ari     | [@guygurari](https://github.com/guygurari)           |
+| Vinay Ramasesh  | [@ramasesh](https://github.com/ramasesh)             |
+
+
+## Emeritus
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index aeccf1d..c8b4389 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,7 +1,32 @@
 # How to Contribute
 
-So you want to add some code to Caliban. Excellent! This page details ways that
-you can contribute.
+So you want to add some code to Caliban. Excellent!
+
+Pull requests and bug reports are always welcome! Check out our [Contributor's
+Guide](CONTRIBUTING.md) for information on how to get started contributing to
+Caliban.
+
+The TL;DR; is:
+
+- send us a pull request,
+- iterate on the feedback + discussion, and
+- get a +1 from a [Committer](COMMITTERS.md)
+
+in order to get your PR accepted.
+
+Issues should be reported on the [GitHub issue
+tracker](https://github.com/google/caliban/issues).
+
+If you want to discuss an idea for a new feature or ask us a question,
+discussion occurs primarily in the body of [Github
+Issues](https://github.com/google/caliban/issues), though the project is growing
+large enough that we may start a Gitter channel soon.
+
+The current list of active committers (who can +1 a pull request) can be found
+here: [COMMITTERS.md](COMMITTERS.md)
+
+A list of contributors to the project can be found at the project's
+[Contributors](https://github.com/google/caliban/graphs/contributors) page.
 
 ## Contributor License Agreement
 
diff --git a/README.md b/README.md
index 5f5b8f9..572331e 100644
--- a/README.md
+++ b/README.md
@@ -464,10 +464,32 @@ sharp edges. Please help by trying out Caliban, [reporting
 bugs](https://github.com/google/caliban/issues), and letting us know what you
 think!
 
-## Contributing
+## Get Involved + Code of Conduct
 
-Please refer to our [Contributor's Guide](CONTRIBUTING.md) for information on
-how to get started contributing to Caliban.
+Pull requests and bug reports are always welcome! Check out our [Contributor's
+Guide](CONTRIBUTING.md) for information on how to get started contributing to
+Caliban.
+
+The TL;DR; is:
+
+- send us a pull request,
+- iterate on the feedback + discussion, and
+- get a +1 from a [Committer](COMMITTERS.md)
+
+in order to get your PR accepted.
+
+Issues should be reported on the [GitHub issue
+tracker](https://github.com/google/caliban/issues).
+
+Discussion occurs primarily in the body of [Github
+Issues](https://github.com/google/caliban/issues), though the project is growing
+large enough that we may start a Gitter channel soon.
+
+The current list of active committers (who can +1 a pull request) can be found
+here: [COMMITTERS.md](COMMITTERS.md)
+
+A list of contributors to the project can be found at the project's
+[Contributors](https://github.com/google/caliban/graphs/contributors) page.
 
 ## Citing Caliban