1e2abe5d4e1cbf29b1630292ec3eb32cb993f49e

Author
Marc Cornellà <marc.cornella@live.com>
Committer
Marc Cornellà <marc.cornella@live.com>
Date

Message

Categories of issues in oh-my-zsh (work-in-progress)

Diff

 1diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
 2index ae8865b353e53561a8a28a066f44fa81469486e1..9964c380d34d87b1e2bfbdaf99f8d1292dfdf3fc 100644
 3--- a/CONTRIBUTING.md
 4+++ b/CONTRIBUTING.md
 5@@ -23,4 +23,20 @@ See point 1, then go ahead (unless your solution is yet another theme)
 6 
 7 ## YOU HAVE FREE TIME TO VOLUNTEER
 8 
 9-Cool!
10+Cool! Please have a look at the list below to understand how oh-my-zsh categorizes its issues.
11+
12+Classification of issues and
13+
14+- Bugs, which may be:
15+  - Specific of zsh \*
16+  - Regressions, in which we should summon the author of the offending commit once it is located
17+
18+- Feature requests
19+
20+- Helpdesk, which may be:
21+  - Specific of zsh \*
22+  - Everything else
23+
24+\* 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.
25+In the case of helpdesk, minimal response should be done. That is, provide a link to the wiki with the relevant information, or
26+add it to the FAQ of the wiki and point to it afterwards.