Added reference to contributing from readme

Author: aashish24

CONTRIBUTING.md

@@ -87,7 +87,8 @@ local repository and GitHub.
 You may want to fork UV-CDAT to work on the code if you have access to the repository,
 then just create a branch there instead. If you don't then follow these guidelines
 for forking UV-CDAT. Go to the [UV-CDAT project page](https://github.com/UV-CDAT/uvcdat)
-and hit the *fork* button. You will want to clone your fork to your machine:
+and hit the *fork* button. You will want to clone your fork to your machine: (HTTPS
+or SSH is preferred to git:// for security reasons).
 
     git clone git://github.com/UV-CDAT/uvcdat.git UV-CDAT-yourname
     cd UV-CDAT-yourname
@@ -96,10 +97,9 @@ and hit the *fork* button. You will want to clone your fork to your machine:
 This creates the directory UV-CDAT-yourname and connects your repository
 to the upstream (main project) *UV-CDAT* repository.
 
-You will also need to hook up Travis-CI to your GitHub repository so the
-suite is automatically run when a Pull Request is submitted.
-Instructions are
-[here](http://about.travis-ci.org/docs/user/getting-started/).
+You will also need to hook up Travis-CI to your GitHub (if you have forked)
+repository so the suite is automatically run when a Pull Request is submitted.
+Instructions are [here](http://about.travis-ci.org/docs/user/getting-started/).
 
 ### Creating a Branch
 
@@ -128,9 +128,6 @@ using default settings:
         cmake uvcdat-path-to-source
         make -jN
 
-    If you startup the Python interpreter in the *UV-CDAT* source
-    directory you will call the built C extensions
-
 Contributing to the documentation
 ---------------------------------
 
@@ -266,13 +263,15 @@ The following defines how a commit message should be structured. Please
 reference the relevant GitHub issues in your commit message using GH1234
 or \#1234. Either style is fine, but the former is generally preferred:
 
-> -   a subject line with \< 80 chars.
+> -   a subject line with \< 80 chars (50-char subject, 72-char rest).
 > -   One blank line.
-> -   Optionally, a commit message body.
+> -   Optionally, a commit message body (72-char).
 
 Now you can commit your changes in your local repository:
 
-    git commit -m
+    git commit -a
+or
+    git commit -a -m "Message..Here"
 
 If you have multiple commits, it is common to want to combine them into
 one commit, often referred to as "squashing" or "rebasing". This is a

README.md

@@ -9,3 +9,9 @@ uvcdat
 Developed by partnering with ESGF and the community to create a larger problem-solving environment, UV-CDAT is an open source, easy-to-use application that links together disparate software subsystems and packages to form an integrated environment for analysis and visualization. This project seeks to advance climate science by fulfilling computational and diagnostic/visualization capabilities needed for DOE's climate research.
 
 Led by Lawrence Livermore National Laboratory (LLNL), the consortium consists of four DOE laboratories (Los Alamos, Lawrence Berkeley, LLNL, and Oak Ridge), two universities (University of Utah and the Polytechnic Institute of New York University), NASA, and two private companies (Kitware and tech-X) that will develop reusable software and workflow analysis and visualization applications for large-scale DOE climate modeling and measurements archives. The UV-CDAT concept is simple and flexible enough to interchange parts to expand for future DOE activities.
+
+Developing and Contributing
+------
+We'd love to get contributions from you! Please take a look at the
+[Contribution Documents](CONTRIBUTING.md) to see how to get your changes merged
+in.