Clone URL (Committers only):
https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apache.org/getting_involved%2Findex.mdtext



Index: trunk/content/getting_involved/index.mdtext
===================================================================
--- trunk/content/getting_involved/index.mdtext (revision 1655891)
+++ trunk/content/getting_involved/index.mdtext (working copy)
@@ -3,16 +3,15 @@
 We welcome your contribution towards making Jena a better platform for 
semantic web and linked data applications.
 We appreciate feature suggestions, bug reports and patches for code or 
documentation.
 
-If you need help using Jena: please see our [getting 
help](../help_and_support) page.
+If you need help using Jena, please see our [getting 
help](../help_and_support) page.
 
 ### How to contribute
 
-You can help us sending your suggestions, feature requests and bug reports (as 
well as patches) using the Jena issue tracker:
-[https://issues.apache.org/jira/browse/JENA](https://issues.apache.org/jira/browse/JENA).
+You can help us sending your suggestions, feature requests and bug reports (as 
well as patches) using the [Jena issue 
tracker](https://issues.apache.org/jira/browse/JENA).
 
 You can discuss your contribution, before or after adding it to Jira, on the 
[`dev@jena.apache.org`](mailto:dev@jena.apache.org) mailing list.
-Or, you can help other users answering to their question on the 
[`us...@jena.apache.org`](mailto:us...@jena.apache.org) mailing list.
-Subscription instructions [here](../help_and_support).
+You can also help other users by answering their questions on the 
[`us...@jena.apache.org`](mailto:us...@jena.apache.org) mailing list.
+See the [subscription instructions](../help_and_support) for details.
 
 Please see the [Reviewing Contributions](reviewing_contributions.html) page 
for details of what committers will be looking for when reviewing contributions.
 
@@ -25,12 +24,12 @@
 improvements to the project website as patches (because everything at Apache 
lives in SVN) and helps the wider community. 
 Contributions to documentation are always welcome and considered just as 
valuable as code contributions.
 
-You can click the [Improve this 
Page](javascript:improveThisPage(location.href\);) button on any page to 
instantly open the web based CMS editor.  If prompted you 
-will need to use the username `anonymous` and a blank password to log in.
+You can click the <span class="glyphicon glyphicon-pencil"></span>*Improve 
this Page* button (top-right) on any page to instantly open the web based CMS 
editor.  If prompted you 
+will need to use the username `anonymous` and a blank password to log in. Use 
the *[Diff]* and *[Mail Email]* links to submit your proposed changes to the 
Apache Jena committers.
 
 ### SNAPSHOTs
 
-If you use Apache Maven and you are not afraid of being on the bleeding-edge, 
you can help us testing our SNAPSHOTs which you can find on the Apache Maven 
repository here: 
[https://repository.apache.org/content/repositories/snapshots/org/apache/jena/](https://repository.apache.org/content/repositories/snapshots/org/apache/jena/).
+If you use Apache Maven and you are not afraid of being on the bleeding-edge, 
you can help us by testing our SNAPSHOTs which you can find in the [Apache 
Maven 
repository](https://repository.apache.org/content/repositories/snapshots/org/apache/jena/).
 
 Here is, for example, how you can add TDB version X.Y.Z-SNAPSHOT to your 
project (please ask if you are unsure what the latest snapshot version number 
currently is):
 
@@ -40,13 +39,12 @@
         <version>X.Y.Z-SNAPSHOT</version>
     </dependency>
 
-General help on how to use Jena with Maven is [here](../download/maven.html).
+See also how to [use Jena with Maven](/download/maven.html).
 
-If you have problems with any of our SNAPSHOTs, let us know.
+If you have problems with any of our SNAPSHOTs, [let us 
know](/help_and_support/).
 
-You can also check the state of each Jena development builds
-on the Apache Jenkins continuous integration server: 
-[Jenkins - Jena](https://builds.apache.org/pview/?match=Jena_.*).
+You can check the state of each Jena development builds
+on the [Apache Jenkins continuous integration 
server](https://builds.apache.org/pview/?match=Jena_.*).
 
 
 
@@ -55,14 +53,14 @@
 You can find the Jena source code in the Apache git repository: 
 
[https://git-wip-us.apache.org/repos/asf/jena.git](https://git-wip-us.apache.org/repos/asf/jena.git)
 
-There is also a read-only mirror on github: 
-[https://github.com/apache/jena](https://github.com/apache/jena).
+There is also a read-only mirror of [Jena on 
GitHub](https://github.com/apache/jena):
 
-    git clone https://github.com/apache/jena
+    git clone https://github.com/apache/jena.git
     cd jena
     mvn clean install
 
-You can fork Jena on github and also submit github pull requests to the 
project.
+You can [fork Jena on GitHub](https://github.com/apache/jena/fork) and also 
submit [pull requests](https://github.com/apache/jena/pulls) to 
+contribute your suggested changes to the code.
 
 ### Open issues
 
@@ -72,13 +70,18 @@
 ### Submit your patches
 
 You can develop new contributions and work on patches using either the
-Apache-hosted git repsoitory of the mirror on github.  Git pull requests
-made to the github mirror are routed back to the project.
+Apache-hosted git repository or the [mirror on 
GitHub](https://github.com/apache/jena
+).  
 
+[GitHub pull requests](https://github.com/apache/jena/pulls) are forwarded to 
the
+[dev@jira mailing list](/help_and_support/) for review by the Jena committers. 
+You should subscribe to dev@jira to follow the feedback on your pull request. 
+
+
 Alternatively, patches can be attached directly to issues in Jira 
 (click on `More Actions > Attach Files`).
 
-Please, inspect your continution patch and make sure it includes all (and
+Please, inspect your contribution/patch and make sure it includes all (and
 only) the relevant changes for a single issue. Don't forget tests!
 
 If you want to test if a patch applies cleanly you can use:

Reply via email to