[2/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/7aa8f2d0
Tree: http://git-wip-us.apache.org/repos/asf/airavata-site/tree/7aa8f2d0
Diff: http://git-wip-us.apache.org/repos/asf/airavata-site/diff/7aa8f2d0

Branch: refs/heads/asf-site
Commit: 7aa8f2d00b1ca2b7d50ba34e5af86e6b0522cf5d
Parents: 07efd2d
Author: marpierc <ma...@iu.edu>
Authored: Tue May 17 16:10:43 2016 -0400
Committer: marpierc <ma...@iu.edu>
Committed: Tue May 17 16:10:43 2016 -0400

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


http://git-wip-us.apache.org/repos/asf/airavata-site/blob/7aa8f2d0/content/get-involved.html
----------------------------------------------------------------------
diff --git a/content/get-involved.html b/content/get-involved.html
index 2bad9e8..5f4ec07 100644
--- a/content/get-involved.html
+++ b/content/get-involved.html
@@ -169,7 +169,7 @@
         <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>