add better templates/info files

Author: cal-smith

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,34 @@
+## Carbon Code of Conduct
+
+This is a place to ask questions, work through any challenges, and share ideas and best practices. The following suggestions and guidelines are intended to make the community easier and more enjoyable to use.
+
+### TLDR;
+
+* **Be respectful & understanding.** Not all of us will agree all the time, but disagreement is no excuse for poor behavior or poor manners. It is important that we resolve disagreements and differing views constructively.
+
+- **Be welcoming.** We strive to be a community that welcomes and supports people of all backgrounds and identities.
+
+### General
+
+Communication through any of Carbon's channels (GitHub, emails, Twitter, Slack) must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.
+
+We promise to extend courtesy and respect to everyone involved in this project, regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to Carbon to do the same.
+
+If any member of the community violates this Code of Conduct, the maintainers of Carbon may take action, including removing issues, comments, and PRs or blocking accounts, as deemed appropriate.
+
+If you are subjected to or witness unacceptable behavior, or have any other concerns, please communicate with us directly via [email protected].
+
+### Slack
+
+1. Please, no `@here` or `@channel` unless it is a bug that is **breaking production code.** We have communities in many different time zones, and we would hate to disrupt someone not at the office.
+2. There's no need to notify the Carbon team that you have made an issue in Carbon's GitHub repositories. We check these several times a day, so we promise we'll address your issue as soon as we can.
+3. Reserve direct messages for sensitive discussions, such as privacy, legal, or HR reasons. Otherwise, we encourage posting in public channels so people with the same questions can benefit.
+4. If you have a pressing bug fix, it is best to make a PR directly to get your issues addressed.
+5. `#carbon-components`: This channel is for questions about Carbon Components only. It is not the place to ask general coding questions. Instead, use a dev community like [StackOverflow](https://stackoverflow.com/).
+6. `#carbon-design-system`: Please post any design questions with an in-context screen shot (i.e. screen shot of the whole UI you are designing) with background as to what you are trying to accomplish in this flow. We welcome in-progress work to get community design feedback as well.
+
+<hr>
+
+If you have suggestions to improve this Code of Conduct, please submit an issue or PR.
+
+This Code of Conduct was adopted from the [Angular Project](https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md) and [Todo Open Code of Conduct](http://todogroup.org/opencodeofconduct/).

.github/CONTRIBUTING.md

@@ -0,0 +1,150 @@
+# Contribution Guidelines
+
+Want to contribute to this repository? Please read below first:
+
+* [Issues and Bugs](#issues-and-bugs)
+* [Feature Requests](#feature-requests)
+* [Doc Fixes](#doc-fixes)
+* [Submission Guidelines](#submission-guidelines)
+* [Coding Standards](#coding-standards)
+* [Commit Message Guidelines](#commit-message-guidlines)
+* [Testing](#testing)
+
+## Issues and Bugs
+
+If you find a bug in the source code or a mistake in the documentation, you can help us by
+submitting an issue to this repo. Even better you can submit a Pull Request with a fix.
+
+**Please see the Submission Guidelines below**.
+
+## Feature Requests
+
+You can request a new feature by submitting an issue to this repo. Proposed features (with suitable design documentation and reasoning) can be crafted and submitted to this repo as a Pull Request.
+
+**Please see the Submission Guidelines below**.
+
+## Doc Fixes
+
+If you want to help improve the docs, it's a good idea to let others know what you're working on to minimize duplication of effort. Comment on an issue to let others know what you're working on, or create a new issue if your work doesn't fit within the scope of any of the existing doc fix projects.
+
+**Please see the Submission Guidelines below**.
+
+## Submission Guidelines
+
+### Setup
+
+1. Fork the project by navigating to the main [repository](https://github.com/IBM/carbon-components-angular) and clicking the **Fork** button on the top-right corner.
+
+2. Navigate to your forked repository and copy the **SSH url**. Clone your fork by running the following in your terminal:
+
+   ```
+   $ git clone [email protected]:{ YOUR_USERNAME }/carbon-components-angular.git
+   $ cd carbon-components-angular
+   ```
+
+   See [GitHub docs](https://help.github.com/articles/fork-a-repo/) for more details on forking a repository.
+
+3. Once cloned, you will see `origin` as your default remote, pointing to your personal forked repository. Add a remote named `upstream` pointing to the main `carbon-components-angular`:
+
+   ```
+   $ git remote add upstream [email protected]:IBM/carbon-components-angular.git
+   $ git remote -v
+   ```
+
+### Submitting an Issue
+
+Before you submit your issue, search the repository. Maybe your question was already answered.
+
+If your issue appears to be a bug, and hasn't been reported, open a new issue. Help us to maximize the effort we can spend fixing issues and adding new features, by not reporting duplicate issues.
+
+### Submitting a Pull Request
+
+1. Search this repository for an open or closed Pull Request that relates to your submission. You don't want to duplicate effort.
+
+2. Pull the latest master branch from `upstream`:
+
+   ```
+   $ git pull upstream master
+   ```
+
+3. Always work and submit pull requests from a branch. _Do not submit pull requests from the `master` branch of your fork_.
+
+   ```
+   $ git checkout -b { YOUR_BRANCH_NAME } master
+   ```
+
+4. Create your patch or feature following our [development guidelines](/README.md#development). Make sure to also follow our [coding standards](#coding-standards).
+
+5. Test your branch and add new test cases where appropriate per the [testing guidelines](#testing).
+
+6. Commit your changes using a descriptive commit message.
+
+   ```
+   $ git commit -a -m "chore: Update header with newest designs, resolves #123"
+   ```
+
+   **Note:** the optional commit -a command line option will automatically "add" and "rm" edited files. See [Close a commit via commit message](https://help.github.com/articles/closing-issues-via-commit-messages/) and [writing good commit messages](https://github.com/erlang/otp/wiki/Writing-good-commit-messages) for more details on commit messages.
+
+7. Once ready for feedback from other contributors and maintainers, **push your commits to your fork** (be sure to run `yarn ci-check` before pushing, to make sure your code passes linting and unit tests):
+
+   ```
+   $ git push origin { YOUR_BRANCH_NAME }
+   ```
+
+8. In Github, navigate to [IBM/carbon-components-react](https://github.com/IBM/carbon-components-react) and click the button that reads "Compare & pull request".
+
+9. Write a title and description, the click "Create pull request".
+
+   See [how to write the perfect pull request](https://github.com/blog/1943-how-to-write-the-perfect-pull-request) for more details on writing good PRs.
+
+10. Stay up to date with the activity in your pull request. Maintainers will be reviewing your work and making comments, asking questions and suggesting changes to be made before they merge your code. When you need to make a change, add, commit and push to your branch normally.
+
+    Once all revisions to your pull request are complete, a maintainer will squash and merge your commits for you.
+
+**That's it! Thank you for your contribution!**
+
+## Coding Standards
+
+To ensure consistency throughout the source code, keep these rules in mind as you are working:
+
+### Style Guide
+
+For a set of basic rules and guidelines for developing React components, see [here](https://github.com/airbnb/javascript/tree/master/react#basic-rules).
+
+Feel free to edit/write components in your own style but be wary that we may ask you to make changes while reviewing your pull request.
+
+### Linting
+
+We enforce some style rules for code in this repository using [eslint](http://eslint.org/). You can install a linting addon to a lot of editors and IDEs that will follow our linting rules.
+
+If you decide to not install a linter addon, or cannot, you can run `yarn lint` to get a report of any style issues. Any issues not fixed will be caught during CI, and will prevent merging.
+
+## Commit Message Guidelines
+
+We use commit message guidelines based on the [Angular Commit Conventions](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit).
+
+After the commit message has been submitted, it is checked by [`husky`](https://www.npmjs.com/package/husky) and [`validate-commit-msg`](https://www.npmjs.com/package/validate-commit-msg) to ensure it is syntactically correct.
+
+## Testing
+
+If you add any features to our code, make sure to add tests so that your changes are covered. Tests are written using Jasmine and Karma.
+
+Test your changes by running our test commands:
+
+* Run linting:
+
+  ```
+  npm run lint
+  ```
+
+* Run unit tests:
+
+  ```
+  npm run  test
+  ```
+
+* Watching unit tests:
+
+  ```
+  npm run test:watch
+  ```

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,44 @@
+<!-- Feel free to remove sections that aren't relevant.
+
+## Title line template: [Title]: Brief description
+
+-->
+
+## Detailed description
+
+> Describe in detail the issue you're having.
+
+> Is this a feature request (new component, new icon), a bug, or a general issue?
+
+> Is this issue related to a specific component?
+
+> What did you expect to happen? What happened instead? What would you like to see changed?
+
+> What browser are you working in?
+
+> What version of the Carbon Design System are you using?
+
+> What offering/product do you work on? Any pressing ship or release dates we should be aware of?
+
+## Steps to reproduce the issue
+
+<!--
+Please try to re-create the issue using our Codesandbox template available here:
+https://codesandbox.io/s/x2mjypo6pp
+
+This helps reduce the issue to an isolated case that helps us out when debugging.
+If you're able to reproduce using the codesandbox link above, please include the
+link in addition to the steps to reproduce. Thanks so much!
+-->
+
+<!-- [Codesandbox](<url>) -->
+
+1. Step one
+2. Step two
+3. Step three
+4. etc.
+
+## Additional information
+
+* Screenshots or code
+* Notes

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,17 @@
+Closes IBM/carbon-components-angular#
+
+{{short description}}
+
+#### Changelog
+
+**New**
+
+* {{new thing}}
+
+**Changed**
+
+* {{change thing}}
+
+**Removed**
+
+* {{removed thing}}

.github/SUPPORT.md

@@ -0,0 +1,7 @@
+# Support
+
+If you run into an issue, sorry about that! We definitely want to make sure that
+your experience using the Carbon Design System is the best that it can be.
+
+When this happens, just create an issue on GitHub by filling out the template
+and we'll try our best to respond in a reasonable time.