[4/5] airavata-site git commit: (AIRAVATA-1977) This page needs to be transferred from the old site. For now I am pointing to the old site for this link.

[mp...@apache.org]

(AIRAVATA-1977) This page needs to be transferred from the old site. For now I am pointing to the old site for this link.


Project: http://git-wip-us.apache.org/repos/asf/airavata-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/airavata-site/commit/5ce3749f
Tree: http://git-wip-us.apache.org/repos/asf/airavata-site/tree/5ce3749f
Diff: http://git-wip-us.apache.org/repos/asf/airavata-site/diff/5ce3749f

Branch: refs/heads/asf-site
Commit: 5ce3749f3e168165cda2e5bf99fbf349ede279b8
Parents: ad36bd7
Author: marpierc <ma...@iu.edu>
Authored: Tue May 17 16:13:35 2016 -0400
Committer: marpierc <ma...@iu.edu>
Committed: Tue May 17 16:13:35 2016 -0400

----------------------------------------------------------------------
 source/get-involved.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/airavata-site/blob/5ce3749f/source/get-involved.md
----------------------------------------------------------------------
diff --git a/source/get-involved.md b/source/get-involved.md
index c171db7..8b87a27 100644
--- a/source/get-involved.md
+++ b/source/get-involved.md
@@ -100,7 +100,7 @@ id: get-involved
         <p>During the review process you may be asked to make some changes to your submission. While working through feedback, it can be beneficial to create new commits so the incremental change is obvious. This can also lead to a complex set of commits, and having an atomic change per commit is preferred in the end. Use your best judgement and work with your reviewer as to when you should revise a commit or create a new one.</p>
         <p>A pull request is considered ready to be merged once it gets at lease one +1 from a reviewer. Once all the changes have been completed and the pull request is accepted, it must be rebased to the latest upstream version. It is also a good idea to squash all the commits into a single one, since this will allow us to generate a clean patch and merge it properly.</p>
         <h4 id="accepting-contributions">Accepting Contributions</h4>
-        <p>Developers with Airavata Commit access should read <a href="how-to-commit-contributed-code.html">Accepting Contribtions</a> on steps to accept the contributed code</p>
+        <p>Developers with Airavata Commit access should read <a href="http://airavata.staging.apache.org/community/how-to-commit-contributed-code.html">Accepting Contribtions</a> on steps to accept the contributed code</p>
 
     </div>
   </div>