new issue templates

README.org

@@ -134,6 +134,14 @@ markdown wasn't created to deal with todo list, etc...
 Org-mode file can handle meta-datas, can be presented with columns, sorted,
 can provide agenda views, etc...
 
+Org mode is a format that is extremely flexible and battle tested.
+It is text only, readable, easy to parse.
+
+It will adapt easily between the beginning and the end of your project life.
+Starting with only basic features (TODO / INPROGRESS / DONE)
+
+Then, priority, multiple users, tags, many meta infos by task.
+Task organized as tree of tasks and subtasks.
 
 * Why is this important?
   It is very important to put all those meta-data about your project inside the

src/GPM.hs

@@ -76,6 +76,8 @@ initIssues :: IO ()
 initIssues = do
   echo "* issue.org"
   output "issues.org" $(embedStringFile "templates/issues.org")
+  mktree "templates"
+  output ("templates" </> "new-issue.tpl") $(embedStringFile "templates/new-issue.tpl")
   debug "git add issues.org"
 
 initDocs :: IO ()

templates/issues.org

@@ -68,7 +68,6 @@ The contributor will then be able to copy the content of =reviews/= into
 =~/.reviews/=, switch to the branch to be merged, read the review, make fixes,
 add comment to the review files, etc...
 
-
 *** ACCEPTED Review finished
     :PROPERTIES:
     :REVIEWER: shubby

templates/new-issue.org

@@ -0,0 +1,8 @@
+**** {{priority}} {{status}} {{title}}                                      :{{#tags}}{{tag}}:{{/tags}}
+   :PROPERTIES:
+   :CREATOR:  {{user}}
+   {{#branch}}:BRANCH:   {{branch}}{{/branch}}
+   {{#assignee}}:ASSIGNEE: {{assignee}}{{/assignee}}
+   {{#reviewers}}:REQUESTED_REVIEWERS:{{#reviewers}} {{reviewer}}{{/reviewers}}{{/reviewers}}
+   :END:
+{{description}}