Update the project for github migration

Add README.md/License/Contributing info to be up to spec.

CONTRIBUTING.md

@@ -0,0 +1,54 @@
+# How to contribute #
+
+We'd love to accept your patches and contributions to this project.  There are
+a just a few small guidelines you need to follow.
+
+
+## Contributor License Agreement ##
+
+Contributions to any Google project must be accompanied by a Contributor
+License Agreement.  This is not a copyright **assignment**, it simply gives
+Google permission to use and redistribute your contributions as part of the
+project.
+
+  * If you are an individual writing original source code and you're sure you
+    own the intellectual property, then you'll need to sign an [individual
+    CLA][].
+
+  * If you work for a company that wants to allow you to contribute your work,
+    then you'll need to sign a [corporate CLA][].
+
+You generally only need to submit a CLA once, so if you've already submitted
+one (even if it was for a different project), you probably don't need to do it
+again.
+
+[individual CLA]: https://developers.google.com/open-source/cla/individual
+[corporate CLA]: https://developers.google.com/open-source/cla/corporate
+
+
+## Submitting a patch ##
+
+  1. It's generally best to start by opening a new issue describing the bug or
+     feature you're intending to fix.  Even if you think it's relatively minor,
+     it's helpful to know what people are working on.  Mention in the initial
+     issue that you are planning to work on that bug or feature so that it can
+     be assigned to you.
+
+  1. Follow the normal process of [forking][] the project, and setup a new
+     branch to work in.  It's important that each group of changes be done in
+     separate branches in order to ensure that a pull request only includes the
+     commits related to that bug or feature.
+
+  1. Any significant changes should almost always be accompanied by tests.  The
+     project already has good test coverage, so look at some of the existing
+     tests if you're unsure how to go about it.
+
+  1. Do your best to have [well-formed commit messages][] for each change.
+     This provides consistency throughout the project, and ensures that commit
+     messages are able to be formatted properly by various git tools.
+
+  1. Finally, push the commits to your fork and submit a [pull request][].
+
+[forking]: https://help.github.com/articles/fork-a-repo
+[well-formed commit messages]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
+[pull request]: https://help.github.com/articles/creating-a-pull-request

LICENSE

@@ -1,9 +1,3 @@
-Copyright 2014 Google Inc. All rights reserved.
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-
-
 
                                  Apache License
                            Version 2.0, January 2004

README.md

@@ -0,0 +1,21 @@
+# Google Toolbox for Mac - Session Fetcher #
+
+**Project site** <https://github.com/google/gtm-session-fetcher><br>
+**Discussion group** <http://groups.google.com/group/google-toolbox-for-mac>
+
+GTMSessionFetcher makes it easy for Cocoa applications to perform http
+operations. The fetcher is implemented as a wrapper on NSURLSession, so its
+behavior is asynchronous and uses operating-system settings on iOS and Mac OS X.
+
+Features include:
+- Simple to build; only one source/header file pair is required
+- Simple to use: takes just two lines of code to fetch a request
+- Supports upload and download sessions
+- Flexible cookie storage
+- Automatic retry on errors, with exponential backoff
+- Support for generating multipart MIME upload streams
+- Easy, convenient logging of http requests and responses
+- Supports plug-in authentication such as with gtm-oauth2
+- Easily testable; self-mocking
+- Automatic rate limiting when created by the GTMSessionFetcherService factory class
+- Fully independent of other projects