diff options
authorJohn MacFarlane <>2015-01-03 15:59:50 -0800
committerJohn MacFarlane <>2015-01-03 15:59:50 -0800
commita6d469afdccd84a91c4bfb297ef1eb6d04cc4fa3 (patch)
parente7187fa3bb5e704b8a4a96f8de952636de4eee3e (diff)
parent47b8256635c250254340ea9af3d3fb89ae88c09c (diff)
Merge pull request #1853 from mpickering/contrib
Updated with information about issue tags
1 files changed, 37 insertions, 0 deletions
diff --git a/ b/
index 824d1465e..cf6ea7bef 100644
--- a/
+++ b/
@@ -25,6 +25,33 @@ including
A small test case (just a few lines) is ideal. If your input is large,
try to whittle it down to the minimum necessary to illustrate the problem.
+Fixing bugs from the issue tracker
+Almost all the bugs on the issue tracker have one or more associated tags. These
+are used to indicate the *difficulty* and *nature* of a bug. There is not yet a
+way to indicate priority. An up to date summary of issues can be found
+* [Enhancement] -- A feature which would be desirable.
+* [Bug] -- A problem which needs to be fixed.
+* [Minor] -- The fix should only be a couple of lines.
+* [Major] -- The fix might require structural changes or in depth knowledge of
+the code base.
+* [Reader] -- A request to add a new input format.
+* [Writer] -- A request to add a new output format.
+* [docs] -- A discrepency or ambiguity in the documentation.
+* [inprogress] -- Someone is actively working on or planning to work on the
+* [More discussion needed] -- It is unclear what the correct approach to solving
+the ticket is. Before starting on tickets such as this it would be advisable to
+post on the ticket.
+* [More info needed] -- We require more information from a user before we can
+classify a report properly.
Have an idea for a new feature?
@@ -182,3 +209,13 @@ The library is structured as follows:
[Haskell platform]:
+[More discussion needed]:
+[More info needed]: