From c2c021455a2bec6a9bb4b492934272a38f195995 Mon Sep 17 00:00:00 2001 From: Christopher Baines Date: Mon, 9 Mar 2015 23:23:21 +0000 Subject: Add dist-bugs post --- posts/dist-bugs.mdwn | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 posts/dist-bugs.mdwn diff --git a/posts/dist-bugs.mdwn b/posts/dist-bugs.mdwn new file mode 100644 index 0000000..d433ce6 --- /dev/null +++ b/posts/dist-bugs.mdwn @@ -0,0 +1,24 @@ +[[!meta title="Distributed Bug/Issue Tracking Systems"]] + +I had a dive in to the rather absent world of distributed issue/bug tracking +systems on Saturday, and they are still on my mind... + +This was triggered by discussions around the [impending shutdown of +Gitorious](https://about.gitlab.com/2015/03/03/gitlab-acquires-gitorious/). + +I started by improving the +[dist-bugs](http://dist-bugs.branchable.com/software/) wiki, and have narrowed +down the ones that interest me to four: + +* [TicGit-ng](https://github.com/jeffWelling/ticgit) +* [Bugs Everywhere](http://bugseverywhere.org/) +* [Nitpick](http://travisbrown.ca/projects/nitpick/docs/nitpick.html) +* [Ditz](http://ditz.rubyforge.org/) + +I am going to give each a go, one by one, and will hopefully post my thoughts +online over the next few weeks. + +My current dream of a distributed bug/issue tracking system, has plain text, +editable, YAML files, with a web server, and command line utility for editing. +Hopefully I will find that one of the tools above is like this, or just good +enough/better... -- cgit v1.2.3