From 656cbd9234c905fe070a51a7f385fafeca46d226 Mon Sep 17 00:00:00 2001 From: Joshua Levy Date: Thu, 18 Aug 2016 21:11:56 -0700 Subject: [PATCH] Add a private form to collect questions. --- CONTRIBUTING.md | 8 +++++--- README.md | 6 +++++- 2 files changed, 10 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2ff7081..9024687 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -3,11 +3,13 @@ Contributing Contributions of all kinds, including discussion, corrections, additions, and improvements, are welcome! We hope you'll join and help, in small ways or large. We gladly credit all contributors and authors. Here are few notes before you jump in. -**Questions and discussion**: [File issues](https://github.com/open-guides/og-aws/issues) liberally. Don’t be shy about creating issues — they are the only way to discuss things here. Just tag it as a question or discussion. We or others can answer, and it may lead to improvements to the guide. ++[![Ask a Question](https://img.shields.io/badge/%3f-Ask%20a%20Question-ff69b4.svg)](https://airtable.com/shrXZ61VrovWfXYBg) if you don’t see your question here, and we’ll work to include it. -**Corrections and improvements**: [File issues](https://github.com/open-guides/og-aws/issues) describing the problem. Use them to discuss topics, ask questions, identify issues, or suggest improvements. [Pull requests](https://github.com/open-guides/og-aws/pulls) with changes are even better. Please keep them small and focused, so we can add items individually, and review the conventions below. +[**File issues**](https://github.com/open-guides/og-aws/issues) liberally. Don’t be shy about creating issues. Use them to discuss topics, ask questions, identify issues, or suggest improvements. -Please review current issues and pull requests to avoid duplication. Finally, if an issue isn't appropriate, please shoot an e-mail to [@jlevy](https://github.com/jlevy). +[**Pull requests**](https://github.com/open-guides/og-aws/pulls) with changes are even better. Please keep them small and focused, so we can add items individually, and review the conventions below. + +Please review current issues and pull requests to avoid duplication. Finally, for other concerns, you can shoot an e-mail to [@jlevy](https://github.com/jlevy). ### Conventions diff --git a/README.md b/README.md index 50d7ddc..d405454 100644 --- a/README.md +++ b/README.md @@ -41,7 +41,11 @@ A lot of information on AWS is already written. Most people learn AWS by reading This guide is by and for engineers who use AWS. It aims to be a useful, living reference that consolidates links, tips, gotchas, and best practices. It arose from discussion and editing over beers by [several engineers](AUTHORS.md) who have used AWS extensively. -**July 2016: This is an early in-progress draft!** It’s our first attempt at assembling this information, so is certain to have omissions and errors. [**Please contribute**](CONTRIBUTING.md) by filing issues or PRs to comment, expand, correct, or otherwise improve it. This guide is *open to contributions*, so unlike a blog, it can keep improving. Like any open source effort, we combine efforts but also review ensure high quality. +**This is an early in-progress draft!** It’s our first attempt at assembling this information, so is far from comprehensive still, and likely to have omissions or errors. + +[![Ask a Question](https://img.shields.io/badge/%3f-Ask%20a%20Question-ff69b4.svg)](https://airtable.com/shrXZ61VrovWfXYBg) if you don’t see your question here, and we’ll work to include it. + +[**Please contribute**](CONTRIBUTING.md) by filing issues or PRs to comment, expand, correct, or otherwise improve it. This guide is *open to contributions*, so unlike a blog, it can keep improving. Like any open source effort, we combine efforts but also review ensure high quality. Before using the guide, please read the [**license**](#license) and [**disclaimer**](#disclaimer).