Repository: commons-compress Updated Branches: refs/heads/master cf1362e36 -> c1e73721b
CONTRIBUTING.md: replace references to commons-text with references to commons-compress Project: http://git-wip-us.apache.org/repos/asf/commons-compress/repo Commit: http://git-wip-us.apache.org/repos/asf/commons-compress/commit/c1e73721 Tree: http://git-wip-us.apache.org/repos/asf/commons-compress/tree/c1e73721 Diff: http://git-wip-us.apache.org/repos/asf/commons-compress/diff/c1e73721 Branch: refs/heads/master Commit: c1e73721b32f8abb39a180f5b7f225b5be30ddef Parents: cf1362e Author: pascalschumacher <pascalschumac...@gmx.net> Authored: Wed Nov 16 18:54:26 2016 +0100 Committer: pascalschumacher <pascalschumac...@gmx.net> Committed: Wed Nov 16 18:54:26 2016 +0100 ---------------------------------------------------------------------- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/commons-compress/blob/c1e73721/CONTRIBUTING.md ---------------------------------------------------------------------- diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c7e932a..d78171e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -38,7 +38,7 @@ | | +======================================================================+ ---> -Contributing to Apache Commons Text +Contributing to Apache Commons Compress ====================== You have found a bug or you have an idea for a cool new feature? Contributing code is a great way to give something back to @@ -50,7 +50,7 @@ Getting Started + Make sure you have a [JIRA account](https://issues.apache.org/jira/). + Make sure you have a [GitHub account](https://github.com/signup/free). -+ If you're planning to implement a new feature it makes sense to discuss you're changes on the [dev list](https://commons.apache.org/mail-lists.html) first. This way you can make sure you're not wasting your time on something that isn't considered to be in Apache Commons Text's scope. ++ If you're planning to implement a new feature it makes sense to discuss you're changes on the [dev list](https://commons.apache.org/mail-lists.html) first. This way you can make sure you're not wasting your time on something that isn't considered to be in Apache Commons Compress's scope. + Submit a ticket for your issue, assuming one does not already exist. + Clearly describe the issue including steps to reproduce when it is a bug. + Make sure you fill in the earliest version that you know has the issue.
