Updated README, added CONTRIBUTING page.

	Change on 2014/02/05 by tball <[email protected]>
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=61072846

Author: tomball

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

README

@@ -0,0 +1,39 @@
+# J2ObjC: Java to Objective-C Translator and Runtime #
+
+**Project site:** <http://j2objc.org>
+**J2ObjC blog:** <http://j2objc.blogspot.com>
+**Questions and discussion:** <http://groups.google.com/group/j2objc-discuss>
+
+### What J2ObjC Is ###
+J2ObjC is an open-source command-line tool from Google that translates
+Java code to Objective-C for the iOS (iPhone/iPad) platform. This tool
+enables Java code to be part of an iOS application's build, as no editing
+of the generated files is necessary. The goal is to write an app's non-UI
+code (such as data access, or application logic) in Java, which is then
+shared by web apps (using GWT), Android apps, and iOS apps.
+
+J2ObjC supports most Java language and runtime features required by
+client-side application developers, including exceptions, inner and
+anonymous classes, generic types, threads and reflection. JUnit test
+translation and execution is also supported.
+
+J2ObjC is currently between alpha and beta quality. Several Google projects
+rely on it, but when new projects first start working with it, they usually
+find new bugs to be fixed.
+
+### What J2ObjC isn't ###
+J2ObjC does not provide any sort of platform-independent UI toolkit, nor are
+there any plans to do so in the future. We believe that iOS UI code needs to
+be written in Objective-C or Objective-C++ using Apple's iOS SDK (Android UIs
+using Android's API, web app UIs using GWT, etc.).
+
+## Requirements ##
+
+* JDK 1.6 or higher
+* Xcode 4 or higher
+* Mac OS X 10.7 or higher
+
+## License ##
+
+This library is distributed under the Apache 2.0 license found in the
+[LICENSE](./LICENSE) file.