summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorMarc Cornellà <marc.cornella@live.com>2014-08-04 23:04:53 +0200
committerMarc Cornellà <marc.cornella@live.com>2014-08-29 00:38:12 +0200
commit1e2abe5d4e1cbf29b1630292ec3eb32cb993f49e (patch)
treebe63bd427814bb273e8f41b0daec554ad7dc7fdc /CONTRIBUTING.md
parent1aadd63cfc98987c42033aeb4d7b826abf1f49ef (diff)
downloadzsh-1e2abe5d4e1cbf29b1630292ec3eb32cb993f49e.tar.gz
zsh-1e2abe5d4e1cbf29b1630292ec3eb32cb993f49e.tar.bz2
zsh-1e2abe5d4e1cbf29b1630292ec3eb32cb993f49e.zip
Categories of issues in oh-my-zsh (work-in-progress)
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md18
1 files changed, 17 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index ae8865b35..9964c380d 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -23,4 +23,20 @@ See point 1, then go ahead (unless your solution is yet another theme)
## YOU HAVE FREE TIME TO VOLUNTEER
-Cool!
+Cool! Please have a look at the list below to understand how oh-my-zsh categorizes its issues.
+
+Classification of issues and
+
+- Bugs, which may be:
+ - Specific of zsh \*
+ - Regressions, in which we should summon the author of the offending commit once it is located
+
+- Feature requests
+
+- Helpdesk, which may be:
+ - Specific of zsh \*
+ - Everything else
+
+\* In the case of bugs, I see the benefit in going through the trouble of responding to that. After all, oh-my-zsh should be the missing link that makes zsh perfect, and hunting down an upstream bug can lead to a submitted PR.
+In the case of helpdesk, minimal response should be done. That is, provide a link to the wiki with the relevant information, or
+add it to the FAQ of the wiki and point to it afterwards.