(doc) Preparing for initial release

- Updated README.md
- Added Contributing and Committers documents
- Added icon from Noun Project

Author: gep13

COMMITTERS.md

@@ -0,0 +1,48 @@
+Committing
+==========
+
+We like to see folks contributing to GitHubReleaseManager. If you are a committer, we'd like to see you help from time to time with triage and the pull request process.
+
+In all cases politeness goes a long way. Please thank folks for contributions - they are going out of their way to help make the code base better, or adding something they may personally feel is necessary for the code base.
+
+Please be VERY familiar with [CONTRIBUTING](https://github.com/gep13/GitHubReleaseManager/blob/develop/CONTRIBUTING.md) and follow the process as well.
+
+## Terminology
+
+**contributor** - A person who makes a change to the code base and submits a change set in the form of a pull request.
+
+**change set** - A set of discrete commits which combined together form a contribution.  A change set takes the form of git commits and is submitted in the form of a pull request. Used interchangeably with "pull request".
+
+**committer** - A person responsible for reviewing a pull request and then making the decision what base branch to merge the change set into.
+
+## Review Process
+
+#### Receive new PR (pull request)
+
+ * A contributor sends a pull request (usually against master).
+ * A committer typically reviews it within a week or less to determine the feasibility of the changes.
+
+#### Initial PR Review
+
+ * Did the user create a branch with these changes? If it is on their master, please ask them to review [CONTRIBUTING](https://github.com/gep13/GitHubReleaseManager/blob/develop/CONTRIBUTING.md).
+ * Did the user reformat files and they should not have? Was is just white-space? You can try adding [?w=1](https://github.com/blog/967-github-secrets) to the URL on GitHub.
+ * Are there tests? We really want any new contributions to contain tests so unless the committer believes this code really needs to be in the code base and is willing to write the tests, then we need to ask the contributor to make a good faith effort in adding test cases. Ask them to review the [contributing document](https://github.com/gep13/GitHubReleaseManager/blob/develop/CONTRIBUTING.md) and provide tests. **Note:** Some commits may be refactoring which wouldn't necessarily add additional test sets.
+ * Is the code documented properly? Does this additional set of changes require changes to the [documentation](http://ghrm.readme.io/)?
+ * Was this code warranted? Did the contributor follow the process of gaining approval for big change sets? If not please have them review the [contributing document](https://github.com/gep13/GitHubReleaseManager/blob/develop/CONTRIBUTING.md) and ask them to follow up in the Chat Room.
+
+#### Review the Code
+  * Does the code meet the naming conventions and formatting (need link)?
+  * Is the code sound? Does it read well? Can you understand what it is doing without having to execute it? Principal of no clever hacks (need link).
+  * Does the code do what the purpose of the pull request is for?
+
+#### Accepting a PR
+
+Once you have reviewed the initial items, and are not waiting for additional feedback or work by the contributor, give the thumbs up that it is ready for the next part of the process (merging).
+
+Unless there is something wrong with the code, we don't ask contributors to rebase against develop. They did the work to create the patch in the first place, asking them to unnecessarily come back and try to keep their code synced up with master is not an acceptable process.
+
+## Merging
+
+Once you have reviewed the change set and determined it is ready for merge, the next steps are to bring it local and evaluate the code further by actually working with it, running the tests locally and adding any additional commits or fix-ups that are necessary in a local branch.
+
+When merging the user's contribution, it should be done with `git merge --log --no-ff` to create a merge commit so that in case there is an issue it becomes easier to revert later, and so that we can see where the code came from should we ever need to go find it later (more information on this can be found [here](https://www.kernel.org/pub/software/scm/git/docs/git-merge.html) and also a discussion on why this is a good idea [here](http://differential.io/blog/best-way-to-merge-a-github-pull-request)).

CONTRIBUTING.md

@@ -0,0 +1,100 @@
+Contributors
+============
+
+## Contributing Process
+
+### Get Buyoff Or Find Open Community Issues/Features
+
+ * Through GitHub, or through the [Chat Room](https://gitter.im/gep13/GitHubReleaseManager) (preferred), you talk about a feature you would like to see (or a bug), and why it should be in GitHubReleaseManager.
+   * If approved through the Chat Room, ensure the accompanying GitHub issue is created with information and a link back to the Chat Room discussion.
+ * Once you get a nod you can start on the feature.
+ * Alternatively, if a feature is on the issues list with the [community tag](https://github.com/gep13/GitHubReleaseManager/labels/Community), it is open for a patch. You should comment that you are signing up for it on the issue so someone else doesn't also sign up for the work.
+
+### Set Up Your Environment
+
+ * You create, or update, a fork of gep13/GitHubReleaseManager under your GitHub account.
+ * From there you create a branch named specific to the feature.
+ * In the branch you do work specific to the feature.
+ * Please also observe the following:
+    * No reformatting
+    * No changing files that are not specific to the feature
+    * More covered below in the **Prepare commits** section.
+ * Test your changes and please help us out by updating and implementing some automated tests. It is recommended that all contributors spend some time looking over the tests in the source code. You can't go wrong emulating one of the existing tests and then changing it specific to the behavior you are testing.
+ * Please do not update your branch from the master unless we ask you to. See the responding to feedback section below.
+
+### Prepare Commits
+
+This section serves to help you understand what makes a good commit.
+
+A commit should observe the following:
+
+ * A commit is a small logical unit that represents a change.
+ * Should include new or changed tests relevant to the changes you are making.
+ * No unnecessary whitespace. Check for whitespace with `git diff --check` and `git diff --cached --check` before commit.
+ * You can stage parts of a file for commit.
+
+A commit message should observe the following:
+
+  * The first line of the commit message should be a short description around 50 characters in length and be prefixed with the GitHub issue it refers to with parentheses surrounding that. If the GitHub issue is #25, you should have `(GH-25)` prefixed to the message.
+  * If the commit is about documentation, the message should be prefixed with `(doc)`.
+  * If it is a trivial commit or one of formatting/spaces fixes, it should be prefixed with `(maint)`.
+  * After the subject, skip one line and fill out a body if the subject line is not informative enough.
+  * The body:
+    * Should indent at `72` characters.
+    * Explains more fully the reason(s) for the change and contrasts with previous behavior.
+    * Uses present tense. "Fix" versus "Fixed".
+
+A good example of a commit message is as follows:
+
+```
+(GH-7) Installation Adds All Required Folders
+
+Previously the installation script worked for the older version of
+Chocolatey. It does not work similarly for the newer version of choco
+due to location changes for the newer folders. Update the install
+script to ensure all folder paths exist.
+
+Without this change the install script will not fully install the new
+choco client properly.
+```
+
+### Submit Pull Request (PR)
+
+Prerequisites:
+
+ * You are making commits in a feature branch.
+ * All specs should be passing.
+
+Submitting PR:
+
+ * Once you feel it is ready, submit the pull request to the `gep13/GitHubReleaseManager` repository against the ````develop```` branch ([more information on this can be found here](https://help.github.com/articles/creating-a-pull-request)).
+ * In the pull request, outline what you did and point to specific conversations (as in URLs) and issues that you are are resolving. This is a tremendous help for us in evaluation and acceptance.
+ * Once the pull request is in, please do not delete the branch or close the pull request (unless something is wrong with it).
+ * One of the Team members, or one of the committers, will evaluate it within a reasonable time period (which is to say usually within 2-4 weeks). Some things get evaluated faster or fast tracked. We are human and we have active lives outside of open source so don't fret if you haven't seen any activity on your pull request within a month or two. We don't have a Service Level Agreement (SLA) for pull requests. Just know that we will evaluate your pull request.
+
+### Respond to Feedback on Pull Request
+
+We may have feedback for you to fix or change some things. We generally like to see that pushed against the same topic branch (it will automatically update the Pull Request). You can also fix/squash/rebase commits and push the same topic branch with `--force` (it's generally acceptable to do this on topic branches not in the main repository, it is generally unacceptable and should be avoided at all costs against the main repository).
+
+If we have comments or questions when we do evaluate it and receive no response, it will probably lessen the chance of getting accepted. Eventually this means it will be closed if it is not accepted. Please know this doesn't mean we don't value your contribution, just that things go stale. If in the future you want to pick it back up, feel free to address our concerns/questions/feedback and reopen the issue/open a new PR (referencing old one).
+
+Sometimes we may need you to rebase your commit against the latest code before we can review it further. If this happens, you can do the following:
+
+ * `git fetch upstream` (upstream would be the mainstream repo or `gep13/GitHubReleaseManager` in this case)
+ * `git checkout develop`
+ * `git rebase upstream/develop`
+ * `git checkout your-branch`
+ * `git rebase develop`
+ * Fix any merge conflicts
+ * `git push origin your-branch` (origin would be your GitHub repo or `your-github-username/GitHubReleaseManager` in this case). You may need to `git push origin your-branch --force` to get the commits pushed. This is generally acceptable with topic branches not in the mainstream repository.
+
+The only reasons a pull request should be closed and resubmitted are as follows:
+
+  * When the pull request is targeting the wrong branch (this doesn't happen as often).
+  * When there are updates made to the original by someone other than the original contributor. Then the old branch is closed with a note on the newer branch this supersedes #github_number.
+
+## Other General Information
+
+If you reformat code or hit core functionality without an approval from a person on the Team, it's likely that no matter how awesome it looks afterwards, it will probably not get accepted. Reformatting code makes it harder for us to evaluate exactly what was changed.
+
+If you do these things, it will be make evaluation and acceptance easy. Now if you stray outside of the guidelines we have above, it doesn't mean we are going to ignore your pull request. It will just make things harder for us.  Harder for us roughly translates to a longer SLA for your pull request.

Documentation/Legal/CREDITS.md

@@ -0,0 +1,44 @@
+GitHubReleaseManager has been the thoughts and work of the following people:
+
+## Committers & Contributors
+
+### Committers
+
+These are the committers to gep13/GitHubReleaseManager repository:
+
+ * [Gary Ewan Park](https://github.com/gep13) - Creater of GitHubReleaseManager, committer, vision, direction
+ 
+### Contributors
+
+ * [Particular Software](http://www.particular.net/) created the original [GitHubReleaseNotes](https://github.com/Particular/GitHubReleaseNotes) project, which GitHubReleaseManager is based on.
+
+#### Other Contributors
+
+ * [GitHubReleaseManager](https://github.com/gep13/GitHubReleaseManager/graphs/contributors)
+
+## Frameworks
+
+GitHubReleaseManager uses the following awesome frameworks (in no particular order):
+
+ * [Octokit.net](https://github.com/octokit/octokit.net)
+ * [YamlDotNet](http://aaubry.net/pages/yamldotnet.html)
+ * [Costura](https://github.com/Fody/Costura)
+
+GitHubReleaseManager is built, with the following fantastic frameworks and services (in no particular order):
+
+ * [psake](https://github.com/psake/psake)
+ * [NuGet.exe](https://www.nuget.org/)
+ * [AppVeyor](http://www.appveyor.com/)
+ * [MyGet](http://www.myget.org/)
+
+GitHubReleaseManager is tested and analyzed with the following rockstar frameworks (in no particular order):
+
+ * [FxCop](https://msdn.microsoft.com/en-us/library/bb429476(v=vs.80).aspx)
+ * [StyleCop](http://stylecop.codeplex.com/)
+ * [InspectCode](https://confluence.jetbrains.com/display/NETCOM/Introducing+InspectCode)
+ * [DupFinder](https://confluence.jetbrains.com/display/NETCOM/Introducing+dupFinder)
+
+We would like to credit other super sweet tools/frameworks that aid in the development of GitHubReleaseManager:
+
+ * [ReSharper](https://www.jetbrains.com/resharper/)
+ * [NuGet Framework](https://www.nuget.org/)