You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by an...@apache.org on 2016/10/06 14:43:50 UTC
[3/4] jena git commit: Fix mistakes noted in review comments
Fix mistakes noted in review comments
Project: http://git-wip-us.apache.org/repos/asf/jena/repo
Commit: http://git-wip-us.apache.org/repos/asf/jena/commit/03092e6d
Tree: http://git-wip-us.apache.org/repos/asf/jena/tree/03092e6d
Diff: http://git-wip-us.apache.org/repos/asf/jena/diff/03092e6d
Branch: refs/heads/master
Commit: 03092e6d6d2e6220a33f27a2bbec13633fa55d73
Parents: c12b574
Author: Andy Seaborne <an...@apache.org>
Authored: Thu Oct 6 15:33:22 2016 +0100
Committer: Andy Seaborne <an...@apache.org>
Committed: Thu Oct 6 15:33:22 2016 +0100
----------------------------------------------------------------------
CONTRIBUTING.md | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/jena/blob/03092e6d/CONTRIBUTING.md
----------------------------------------------------------------------
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 4eb447f..8b6ae89 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -31,27 +31,27 @@ Documentation is kept and published with Apache's svnpubsub system:
### JIRA
-The project uses a JIRA instance to track work. Please create a JITA so
+The project uses a JIRA instance to track work. Please create a JIRA so
that we can track a contribution.
https://issues.apache.org/jira/browse/JENA
### Github
-It is useful to create a JIRA then use teh JIRA number (e.g. JENA-9999)
+It is useful to create a JIRA then use the JIRA number (e.g. JENA-9999)
in the Pull Request title. This activates the automated mirroring of
discussions onto the project developers mailing list.
To make a contribution:
* On github, fork http://github.com/apache/jena into you github account.
-* Create a branch in your fork for hthe contribution.
+* Create a branch in your fork for the contribution.
* Make your changes. Include the Apache source header at the top of each file.
* Generate a pull request via github. Further changes to your branch will automatically
show up in the pull request
The project development mailing list is automatically notified of new pull
-requests and JIRA ia also automatically updated if the JIRA id is in the pull request
+requests and JIRA is also automatically updated if the JIRA id is in the pull request
title.
### Discussion and Merging
@@ -100,18 +100,18 @@ to review.
### Legal
All contributions are understood to be made as contributions to the
-Apache Software Foundation by the person makign the pull request. These
-are then incorporated into the project codebase and licnesed under the
+Apache Software Foundation by the person making the pull request. These
+are then incorporated into the project codebase and licensed under the
Apache License 2.0.
You, as an individual, must be entitled to make the contribution to the
-project. If the contrbution is part of your employment, please arrange
+project. If the contribution is part of your employment, please arrange
this before making the contribution.
For a large contribution, the project may ask for a specific Software
Grant from the contributor.
-If in doubt, or you have any questions, ask on the dev@jena.apache.org
+If in doubt, or if you have any questions, ask on the dev@jena.apache.org
mailing list. Legal issues are easier to deal with if done before
contributing, rather than after.