github: add mailing list!

.github/CONTRIBUTING.md

@@ -1,25 +1,23 @@
 # How to Contribute
 
-CoreOS projects are [Apache 2.0 licensed](LICENSE) and accept contributions via
-GitHub pull requests. This document outlines some of the conventions on
-development workflow, commit message formatting, contact points and other
-resources to make it easier to get your contribution accepted.
+CoreOS projects are [Apache 2.0 licensed](LICENSE) and accept contributions via GitHub pull requests.
+This document outlines some of the conventions on development workflow, commit message formatting, contact points and other resources to make it easier to get your contribution accepted.
 
 # Certificate of Origin
 
-By contributing to this project you agree to the Developer Certificate of
-Origin (DCO). This document was created by the Linux Kernel community and is a
-simple statement that you, as a contributor, have the legal right to make the
-contribution. See the [DCO](DCO) file for details.
+By contributing to this project you agree to the Developer Certificate of Origin (DCO).
+This document was created by the Linux Kernel community and is a simple statement that you, as a contributor, have the legal right to make the contribution.
+See the [DCO](DCO) file for details.
 
 # Email and Chat
 
-The project currently uses the general CoreOS email list and IRC channel:
-- Email: [coreos-dev](https://groups.google.com/forum/#!forum/coreos-dev)
-- IRC: #[coreos](irc://irc.freenode.org:6667/#coreos) IRC channel on freenode.org
+The project currently uses a mailing list and IRC channel:
 
-Please avoid emailing maintainers found in the MAINTAINERS file directly. They
-are very busy and read the mailing lists.
+- Email: [clair-dev@googlegroups.com](https://groups.google.com/forum/#!forum/clair-dev)
+- IRC: #[coreos](irc://irc.freenode.org:6667/#clair) IRC channel on freenode.org
+
+Please avoid emailing maintainers directly.
+They are very busy and read the mailing lists.
 
 ## Getting Started
 
@@ -42,9 +40,8 @@ Thanks for your contributions!
 
 ### Format of the Commit Message
 
-We follow a rough convention for commit messages that is designed to answer two
-questions: what changed and why. The subject line should feature the what and
-the body of the commit should describe the why.
+We follow a rough convention for commit messages that is designed to answer two questions: what changed and why.
+The subject line should feature the what and the body of the commit should describe the why.
 
 ```
 scripts: add the test-cluster command
@@ -65,7 +62,5 @@ The format can be described more formally as follows:
 <footer>
 ```
 
-The first line is the subject and should be no longer than 70 characters, the
-second line is always blank, and other lines should be wrapped at 80 characters.
-This allows the message to be easier to read on GitHub as well as in various
-git tools.
+The first line is the subject and should be no longer than 70 characters, the second line is always blank, and other lines should be wrapped at 80 characters.
+This allows the message to be easier to read on GitHub as well as in various git tools.

.github/ISSUE_TEMPLATE.md

@@ -1,16 +1,13 @@
 <!--
 
-The Clair developers only support the Clair API.
-They do not support or operate any third party client (e.g. clairctl, klar, harbor).
-If you are using a third party client, please create issues on their respective repositories.
+Project discussion and other meta topics should be discussed on the mailing list.
+
+GitHub issues are ONLY for bugs and features for the Clair API.
+Please first create an issue on your client's repository before opening one here.
 
 Are you using a development build of Clair (e.g. quay.io/coreos/clair-git)?
 Your problem might be solved by switching to a stable release (e.g. quay.io/coreos/clair).
 
-Issues that do not contain the Environment section will be automatically closed.
-If you're making a feature request, please specify "N/A" under the environment section.
-Nobody can help you without context.
-
 -->
 
 ### Description of Problem / Feature Request
@@ -27,6 +24,13 @@ Nobody can help you without context.
 
 ### Environment
 
+<!--
+
+Issues that do not contain the Environment section are AUTOMATICALLY CLOSED.
+If you're making a feature request, please specify "N/A" under the environment section.
+
+-->
+
 - Clair version/image: 
 - Clair client name/version: 
 - Host OS: 

README.md

@@ -44,8 +44,9 @@ Thus, the project was named `Clair` after the French term which translates to *c
 [CoreOS website]: https://coreos.com/clair/docs/latest/
 [Documentation directory]: /Documentation
 
-## Contact
+## Community
 
+- Mailing List: [clair-dev@googlegroups.com](https://groups.google.com/forum/#!forum/clair-dev)
 - IRC: #[clair](irc://irc.freenode.org:6667/#clair) on freenode.org
 - Bugs: [issues](https://github.com/coreos/clair/issues)